Getting Started Guide
OHIE.orgDiscourseWikiAcademy
1.0-Beta
1.0-Beta
  • Getting Started Guide: Paths to Data Exchange
  • Select a Pathway
  • PATHWAY 1: Component and Data Exchange Projects
    • Pathway 1.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Document the Expected Value of the Project
      • Establish a Project Plan
    • Pathway 1.2 - Requirements and Design
      • Establish Training Programs
      • Determine Resources and Identify Constraints and Environmental Factors
      • Analyze the Environment and Context
      • Identify System Constraints
      • Document Requirements
      • Select Software/Component(s)
      • Testing
    • Pathway 1.3 - Implement, Support, and Scale
      • Establish a Support Plan
      • Implement a Scalability Plan
      • Communication and Roll Out
  • PATHWAY 2: Architecture
    • Pathway 2.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Define Value of Health System Architecture
      • Establish a Project Plan
    • Pathway 2.2 - Requirements and Design
      • Inventory Existing Tools
      • Document Use Cases
      • Establish Architecture Principles
      • Document the Architecture
      • Establish Architecture Processes
      • Establish Standards
    • Pathway 2.3 - Implement, Support, and Scale
      • Communication and Roll Out
  • How to Provide Feedback / Input
  • Change Log
Powered by GitBook
On this page
  • Document the Architecture
  • Content to Consider
  1. PATHWAY 2: Architecture
  2. Pathway 2.2 - Requirements and Design

Document the Architecture

Architecture Level Project

PreviousEstablish Architecture PrinciplesNextEstablish Architecture Processes

Last updated 3 years ago

Document the Architecture

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.

  • 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:

    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

    5. Any source code developed specifically for MOH should be stored in the MOH source code repository

    6. 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)

    8. Additional guidelines...

The following are some examples of how the architecture has been documented.

References:

Kenya Health Architecture
Tanzania 2012-2018 Strategy
Uganda
Architecture principles
Standards