Warning |
---|
THIS PAGE IS UNDER CONSTRUCTION |
Overview
Accurate and efficient unique identification of patients is an essential function for a fully realized eHealth architecture. A client registry (CR) is designed to support patient identity management. The OpenHIE CR community seeks to foster innovative technology that provides accurate, reliable and stable identification and de-duplication of individuals and other entities in a variety of contexts, particularly resource-constrained settings.
Standards and Workflows
A core principle of the OpenHIE architecture is to allow the various infrastructure services (such as the CR) to be interchangeable. To support this, the OpenHIE Standards and Profiles use by the Client Registry are outlined in the workflows below.
To be OHIE the system must support one or more of the CR component, the CR application must be able to support the OHIE workflows listed below. Implementations may support only the workflows needed to support their use case:
A core principle of the OpenHIE architecture is to allow the various infrastructure services (such as the CR) to be interchangeable. See: OpenHIE Standards and Profiles.
Recommended Functional Requirements
...