1. Introduction
2. Why OpenHIE?

• Views
  • Ministry and Partner Views??
  • Country Implementers View
  • Domain Experts View
  • Developers View
• What is OpenHIE?
• The Architecture
• Design Principles
• Client Registry (CR)
• Facilities Registry (FR)
• Health Worker / Provider Registry (HWR / PR)
• Shared Health Record (SHR)
• Terminology Service (TS)
• Interoperability Layer
• Standards (existing standards and future standards in OHIE)
• The Tools (e.g. MIRTH Connect, OpenHIM, etc.)
• The Community
• General
• Regional Forums
• National Forums
• Client Registry Community
• Facilities Registry Community
• Health Management Information Systems Community
• Health Worker Registry Community
• Interoperability Layer Community
• PEPFAR Data Exchange Community
• Shared Health Record Community
• Terminology Services Community

• What it’s NOT
• Not an EHR
• Not a Laboratory Information System
• Not a Pharmacy Information System
• Not a…more ideas?
• Getting Engaged

• Designing based on OpenHIE
• A fit for purpose architecture
• Implementation / architecture pattern (something like this)

• How to Implement OpenHIE
• Minimum requirements
• Mine existing Implementation Guides
• Implementation patterns
• Rapid HIE Solution - “I need to implement HIE end-to-end but I only have 40 hours, what can I accomplish?”
• HIE-in-a-Box / Turnkey / Sandbox Solutions

• Virtual machines representing the core components of HIE pre-configured to be accessible out of the box. Using open source systems (e.g. OpenMRS, OpenHIM, OpenLIMS, OpenLMIS, MIRTH Connect, DHIS2, etc.)
• Use environments: Dev / Test / Training / Conferences
• Enterprise Solutions
• Microsoft Windows based platforms
• Not-necessarily-open-source
• MSSQL and Oracle-based SQL servers
• Commercial HL7 / FHIR tools
• Commercial EHRs

• HIE Capability Model (reduced or expanded based upon requirements)
• Core Functional Capabilities
• Clinical Enabling Capabilities
• Technical Enabling Capabilities
• Minimum Enabling Capabilities

• OpenHIE and Health Systems Mapping
• Potentially a foundation model of OpenHIE systems / components and which open source systems implement the OpenHIE architecture (i.e. Facilities Registry can be located in DHIS2).
• Designs of OpenHIE and mapping of systems for each particular country.
• Interface development
• Messaging framework (e.g. HL7, FHIR, etc.)

• Governance
• Privacy
• Security
• Owners / Sponsors
• eHealth Framework
• Regulatory Framework
• Systems Framework
• Data Standards

• Maintenance and Lifecycle Management
• Software Updates
• Hardware Upgrades and Maintenance
• Deprecation
• Licensing (in the case of Enterprise Solutions)

• Networks & Connectivity
• Satellite
• WiFi
• Cellular Data (e.g. 3G, LTE, etc.)
• Shared Networks
• Partner Networks
• Community Networks
• ‘Sneaker-Net’

• Resources
• Consulting Services
• Logistics Management Services
• Program Development Services
• Software and Program Development Services

• References
• OpenMRS
• OpenHIM
• DATIM

• Support
• IT Support
• Contact Centre and Help Desk

• Document Management (e.g. Architecture and PMO Repositories, CMDB) 

 

• Knowledge Management (e.g. Case Studies, Clinical guidelines, Use Cases, Workflows, etc.)

• Training
• Certifications / Qualifications (i.e. lists and purpose)
• Curriculum development
• Offline / Online Training
• Workshops
• Train-the-Trainer

• Case Studies (Existing Implementations)
• Implementer Documented Implementations
• RHIE
• Etc 

• Glossary of terms