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
  1. PATHWAY 2: Architecture
  2. Pathway 2.1 - Governance, Value, and Scope

Establish or Define Governance Structures

Architecture Level Project

PreviousDetermine and Document Roles and ResponsibilitiesNextDetermine Project Scope

Last updated 3 years ago

Establish or Define Governance Structures

There is often a tendency to consult stakeholders and governance structures at the beginning and end discussions there. Be careful to manage this pitfall as success of the project is often due to communication and buy-in from stakeholders and governance structures. If governance structures are already defined, clearly establish how the project team and stakeholders align and report to established governance groups. If governance structures are not already in place, the team will need to begin to establish some governance structure that will support definitions and maintain the health architecture. Depending upon the scope of the architecture and the goals for getting started, the governance structure may need to consider engaging the following types of groups or groups that support these services:

  • Government and / or Ministry of health ICT

  • Government and / or Ministry of health internet and technical infrastructure

  • Country standards groups boards or bodies

  • Government and / or Ministry of health cloud services or hosting services teams.

  • Private healthcare stakeholders or research organizations that may need to interact with MOH services and data

  • Privacy and security officers or advisers

  • Country or regional identity managers

  • Civil registries

  • Health supply chains

References:

  • (Chapter 6: Digital Health Architecture)

  • Nsaghurwe, A., Dwivedi, V., Ndesanjo, W. et al.

Digital Implementation Investment Guide
One country's journey to interoperability: Tanzania's experience developing and implementing a national health information exchange. BMC Med Inform Decis Mak 21, 139 (2021).