You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Page under construction

The following information is under construction.  For full content see the OpenHIE Specification.  

Purpose

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

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 first draft for tender or requests for proposals. 

Content that can be used to advise a tender document 

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.  

ResourceDescription 
Non-functional RequirementsThis page contains recommended non-functional requirements for any OpenHIE component software.  These requirements should be considered as people create requests for proposals and tenders.  
Client Registry This page contains a description of the Client or Patient Registry architecture component and outlines high-level requirements that are expected of this component.  
Facility Registry This page contains a description of the Facility Registry architecture component and outlines high-level requirements that are expected of this component. 



  • No labels