> For the complete documentation index, see [llms.txt](https://guides.ohie.org/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.ohie.org/getting-started/dev/pathway-2-architecture/phase-2-requirements-and-design/document-the-architecture.md).

# Document the Architecture

## <img src="/files/-MeQFKJY93qQnWxH0Zk9" alt="" data-size="line"> Document the Architecture

### Content to Consider&#x20;

When developing your health architecture, you may want to consider including the following content: &#x20;

* Information about the health system context&#x20;
  * You may want to include linkages to key health system documents or priorities
* [Architecture principles](/getting-started/dev/pathway-2-architecture/phase-2-requirements-and-design/establish-architecture-principles.md)
* Architecture diagram / components&#x20;
  * you may want to reference the OpenHIE Architecture here. &#x20;
* [Standards](/getting-started/dev/pathway-2-architecture/phase-2-requirements-and-design/establish-processes.md) or a reference to standards&#x20;
  * Consider of the data exchange standards and / or terminology standards are stored in the Architecture document, an appendix or a separate standards document. &#x20;
* Guidelines for application may be included in the architecture or other documentation for health information teams to follow.  These may include expectations such as: &#x20;
  1. Project teams must create documentation of system assets (for example, requirements, design, installation process)
  2. Applications that share data must/should have APIs
  3. Application purchases or selection must be done via an evaluation process where the criteria and decision are documented
  4. Applications should be designed in a way that support data standards&#x20;
  5. Any source code developed specifically for MOH should be stored in the MOH source code repository
  6. &#x20;Interoperability layer should be used for data exchange (No new point-to-Point)
  7. Project teams must complete an HIS project Alignment (processes outlined in this document)&#x20;
  8. Additional guidelines...

The following are some examples of how the architecture has been documented. &#x20;

{% hint style="success" %} <img src="/files/-Me6G6QqCYm4wLGJYCDm" alt="" data-size="line"> **References:**

* [Kenya Health Architecture ](https://www.data4sdgs.org/sites/default/files/services_files/Kenya%20Health%20Information%20Systems%20Interoperability%20Framework.pdf)
* [Tanzania 2012-2018 Strategy](https://www.who.int/goe/policies/countries/tza_ehealth.pdf)
* [Uganda](https://health.go.ug/sites/default/files/National%20e_Health%20Strategy_0.pdf)
  {% endhint %}