Page History

Purpose of this Page

The purpose of this document is to provide resources for those in MOHs or implementer institutions who may be creating tenders or RFPs for HIE or HIE component requirements.  

Overview of Resources 

One of the key goals of the OpenHIE Architecture Specification is to articulate the requirements for the typical HIE components.  The following content can be used as a foundation for creating content for tender requests or requests for proposals. 

Content to Consider 

Use Cases 

Consider noting the key use cases or business use of the intended solution. 
Examples might be: 

• Describing the creation of a shared patient-level repository that can inform a longitudinal view of a patient's care even if that care was received at multiple facilities.  
• Describing the creation of a health exchange for better case reporting and analysis across facilities.  

Architecture

You may want to consider providing an overview of the HIE and the components needed to support your use case(s).  You may refer to the OpenHIE documentation or refer to country specific architecture documentation.  

Reference:  Overview of the OpenHIE Architecture as an example.  

Project Principles  

You may want to consider outline key principles such as use of data exchange standards.  

Data Exchange Standards

Consider documenting the standards that you would like to use.  These are the current standards that OpenHIE recommends.  

HIE Component Descriptions and Requirements

If you are creating a tender for a comprehensive HIE, consider these references as you describe each component and outline the high-level requirements.  For a tender for a specific component, consider the Non-functional Requirements and the description of the specific component that is being requested.