Revision [126]
Last edited on 2010-05-01 03:39:46 by MartinWehlouAdditions:
=====Bottle neck interfaces=====
No iotaMed project should force any other iotaMed module to pass data or functionality through a narrow interface that limits the functionality to a lower level than otherwise possible. Examples would be a single data store (as described above) or a web service interface mandated by an organization as the single point of communication, unless the individual iotaMed projects can add their own APIs to that interface.
=====Minimal reliance on standards=====
The iotaMed projects should always strive to reduce the reliance on standards to an absolute minimum. We all know that if a project depends on an extensive standards effort, that it is severely handicapped from the start. There is an ever increasing number of techniques to allow full interoperability of IT systems with very lightweight standards, and utilizing these methods to the fullest is essential to the iotaMed project.
No iotaMed project should force any other iotaMed module to pass data or functionality through a narrow interface that limits the functionality to a lower level than otherwise possible. Examples would be a single data store (as described above) or a web service interface mandated by an organization as the single point of communication, unless the individual iotaMed projects can add their own APIs to that interface.
=====Minimal reliance on standards=====
The iotaMed projects should always strive to reduce the reliance on standards to an absolute minimum. We all know that if a project depends on an extensive standards effort, that it is severely handicapped from the start. There is an ever increasing number of techniques to allow full interoperability of IT systems with very lightweight standards, and utilizing these methods to the fullest is essential to the iotaMed project.
