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

Determine Project Scope

Architecture Level Project

PreviousEstablish or Define Governance StructuresNextDefine Value of Health System Architecture

Last updated 3 years ago

Determine Project Scope

The scope of the architecture can be a bit challenging. One perspective is to think about the systems and data sharing transactions that are in the purview of the ministry of health. However, there may be other health data and health transactions that are in the jurisdiction of other ministries. Examples of this may include the health supply chain and / or health medications and insurance coverage practices may be important even if these are not directly in the purview of the MOH. To help move forward, you can begin with the architecture under a specific jurisdiction. However, you may want to include other branches as appropriate in the stakeholders. You may want to use any existing health strategy documentation, examples from other countries and / or the OpenHIE Architecture Specification and Diagram to help think about scope of the architecture. Ultimately, you will need to understand the systems that are needed to support the data sharing goals of the country. To begin to identify these needs, use the DIIG (Chapter 3).

References:

  • : (Chapter 3: Identify Health System Challenges and Needs)

  • OpenHIE Architecture Specification

Digital Implementation Investment Guide