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
| Advanced Tables - Table Plus |
|---|
| Resource | Description |
|---|
| Non-functional Requirements | This 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. |
|
- Thoughts on overall considerations for HIE solutions