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 1: Component and Data Exchange Projects
  2. Pathway 1.2 - Requirements and Design

Identify System Constraints

Component Level Project and Exchange Level Project

PreviousAnalyze the Environment and ContextNextDocument Requirements

Last updated 3 years ago

Identify System Constraints

Identify System Constraints

Identifying the high-level system constraints will help implementers understand the factors that need to be addressed in order to design a system that fits the unique context. Identify known constraints such as:

  • Data Capacity - For example, the following types of questions might be asked about a client registry or a shared health record; What is the country’s population? How many of those people will the registry need to support? How many patients are already stored in point-of-care applications? For other projects, the questions may be about how many facilities or products need to be supported.

  • Data Quality - How complete and accurate is the patient demographic data captured in the existing point-of-care and/or national identifier systems? Which existing records are paper and which are electronic?

  • Network Capacity and Reliability - Are there constraints on the network reliability or capacity? Are secure network connections between organizations already established?

  • Power Constraints- Are there any constraints on electricity or power? If so, what are they?

  • Data Privacy Laws and Regulations– Are there any local or regional data privacy laws that apply to the client’s demographic data?

  • Other healthcare software laws or regulations – Are there applicable guidelines for managing healthcare records or for validating healthcare software?

Based upon the country’s unique context, there may be additional constraints that need to be documented.