Document the Architecture
Architecture Level Project
Content to Consider
When developing your health architecture, you may want to consider including the following content:
Information about the health system context
You may want to include linkages to key health system documents or priorities
Architecture diagram / components
you may want to reference the OpenHIE Architecture here.
Standards or a reference to standards
Consider of the data exchange standards and / or terminology standards are stored in the Architecture document, an appendix or a separate standards document.
Guidelines for application may be included in the architecture or other documentation for health information teams to follow. These may include expectations such as:
Project teams must create documentation of system assets (for example, requirements, design, installation process)
Applications that share data must/should have APIs
Application purchases or selection must be done via an evaluation process where the criteria and decision are documented
Applications should be designed in a way that support data standards
Any source code developed specifically for MOH should be stored in the MOH source code repository
Interoperability layer should be used for data exchange (No new point-to-Point)
Project teams must complete an HIS project Alignment (processes outlined in this document)
Additional guidelines...
The following are some examples of how the architecture has been documented.
Last updated
