Demo Videos
SigDep3 Patient Import and OpenCR AutoMatching
OpenCR Decision Rules Configuration and Matching
Zimbabwe HIE MPI Workflow
When information is distributed across independent databases and systems, client registries (CRs), also called Master Patient Indexes (MPIs), are an essential tool for linking a single patient’s identity across disparate systems. In many cases, point-of-care systems like EMRs and Laboratory systems, and payer systems generate a unique id for each patient within the individual computer system system. However, without a centralized ID, the patient’s data is challenging to link across systems. CRs utilize algorithms to review patient demographic data across systems or within a single system and link the diverse identities for a unique patient.
This capability is foundational for combining a patient’s information across systems and enabling a provider to see a holistic picture of health, accurate calculation of health system metrics, and reporting of sentinel health events
Key considerations for Patient Identity Management
Record Matching
Record Linkage
Unique Identification
Client Registry Components
The Client Registry was configured using the following components:
The OpenCR Service (MPI): The API for managing queries, routing traffic to the components, and overall entrypoint.
The HAPI FHIR Server (Data Store): HAPI is the reference FHIR server
ElasticSearch (Search Engine): Powerful search engine that is highly performant.
OpenCR UI : To view and break matches between records, and view matching histories (audit events).
OpenHIM Core (Open Health Information Mediator): The OpenHIM is the entrypoint for POS systems. The 6. Client Registry was configured to use the mainstream mediator
Patient Identity Management Work Flow
Create Patient Demographic Record Workflow
Update Patient Demographic Record Workflow
Query Patient Demographic Records by Demographics Workflow
