OpenHIE Architecture Specification
4.0
4.0
  • Specification Overview
  • How to use the Specification
  • Architecture Specification
    • Architecture
    • Architectural Principles
    • Standards and Profiles
  • OpenHIE Component Specifications
    • Non-Functional Requirements
    • Client Registry (CR)
    • OpenHIE Facility Registry (FR)
    • OpenHIE Finance and Insurance Service (FIS)
    • OpenHIE Health Management Information System (HMIS)
    • OpenHIE Health Worker Registry (HWR)
    • OpenHIE Interoperability Layer (IOL)
    • OpenHIE Logistics Management Information System (LMIS)
    • OpenHIE Product Catalogue (PC)
    • OpenHIE Shared Health Record (SHR)
    • OpenHIE Terminology Service (TS)
    • Point-Of-Care Systems
  • Workflow (Exchange) Specification
    • Aggregate Reporting Workflows
      • Export Aggregate Data
      • Validate and Save Aggregate Data
    • Alerting / Sending Reminders or Information
      • Send Client Alert Workflow
      • Send Health Worker Alert Workflow
    • Care Services Discovery
      • Query Health Worker and/or Facility Records Workflow
      • Query Care Services Records Workflow
      • Search Care Services Workflow
      • Request Care Services Updates Workflow
    • Laboratory Work Flows
      • Order Laboratory Test
      • Report Lab Results
    • Patient Identity Management Workflows
      • Create Patient Demographic Record Workflow
      • Update Patient Demographic Record Workflow
      • Query Patient Demographic Records by Identifier Workflow
      • Query Patient Demographic Records by Demographics Workflow
    • Shared Health Record
      • Save Patient-level Clinical Data Workflow
      • Query Patient-level Clinical Data Workflow
    • Terminology Service Workflows
      • Expand Value Set
      • Translate Code
      • Verify Code Existence
      • Verify Code Membership
      • Query Value Set
      • Query Code Systems
      • Query Concept Maps
      • Lookup Code
    • Vaccine Workflows
  • How to Provide Feedback and Input
  • Change Log and Versioning
Powered by GitBook
On this page
  • Standards-Based
  • Adaptable / Implementable
  • Interchangeability / Swappable
  • Additional Principles
  1. Architecture Specification

Architectural Principles

Guiding principles that inform the OpenHIE decision-making process.

PreviousArchitectureNextStandards and Profiles

Last updated 3 years ago

Standards-Based

OpenHIE preferentially seeks to leverage consensus-based, international interoperability specifications that support countries' health information exchange needs. We are committed to engaging in the IHE interoperability specification development process. To the extent possible we will leverage the IHE process to identify, evaluate and implement pre-existing IHE specifications and will also advocate for the development of future solutions.

Adaptable / Implementable

Because health information exchange functional requirements vary among countries and evolve over time, we recognize that existing standards and interoperability specifications may not fully support a country's HIE needs. Consequently, OpenHIE seeks an architecture that supports -- does not on necessarily constrain -- effective implementation of country-driven workflows that extend beyond current interoperability specifications. To the extent possible, we anticipate that such workflow extensions would be incorporated into future consensus-based standardized interoperability specifications. (It has alternatively been suggested we call this principle "user driven". We seek to make architectural decisions based on implementations expressed needs and choose standards that best support the HIE user's needs.)

Interchangeability / Swappable

OpenHIE seeks to support a robust and diverse software component ecosystem where implementing and support organizations may leverage different software products for the OpenHIE components. To enable effective and efficient "swap-ability" of components, we seek an architecture that clearly defines and reinforces standardized interfaces for each of these components. We seek to ensure that the reference components of OpenHIE support standardized interfaces.

Additional Principles

The following additional principles have been suggested: Performant / Scalable; "Monitor-able" / "Surveil-able" / "Inspect-able" / Observable / "Audit-able" have been suggested.

References:

Principles for Digital Development