Client Registry Community

The OHIE Client Registry Community (OHIE-CR) is a free and open initiative built and supported by individuals, implementing bodies, and funders with an interest in developing and deploying client registry standards and software. The community provides an open forum for users (experts to novice) to share best practices, current events, and future plans. The Client Registry is designed to assist in uniquely identifying individuals who receive healthcare services seeking to leverage client registries to improve health outcomes in resource limited settings.

Benefits of a Client Registry


Flexibility approach to patient matching based on system and location constraints.

Accurate Identities

Accurately matches patient records to allow aggregation of historical medical data from multiple institutions for centralized storage.

Informed Care

Access to accurate historical patient data across multiple institutions is essential to provide quality care.


I’m a Developer I’m an ImplementorConnect with US

Why We Do What We Do?

Increasingly health care information is distributed across many independent databases and systems, both within and among organizations as separate islands with different patient identifiers. This is the case for data collected within an institution where there may be multiple identifiers, or for data collected about the same patient at different health care institutions, different pharmacy systems, different payers, and so on. This situation interferes with the aggregation of information about individuals across such databases as needed for public health reporting, clinical research, outcomes management, etc. Aggregation is important not only to determine a patient’s health care status, but also for population based studies. Record linkage is the process of combining information about an individual, family, or entity residing in one or more databases.

Technical Resources


Meet other developers and learn from their experiences and work on common goals.  Join Our Community Group 

Learn about best practices and access expertise, technologies and standards around client registries.  Visit Our Wiki Page

Implementation Guide

A Client Registry environment assessment is an analysis of a health system’s ‘current state.’ The assessment supports the identification of problems to be solved, stakeholders, what success will look like in a specific environment, and challenges/barriers. This process will lay the groundwork for the implementation of a client registry.

Stakeholder leadership is essential for supporting the successful implementation of a client registry. Effective leaders should be identified and join together to form a stakeholder leadership group (SLG) for the development and implementation of a Client Registry. The SLG should be the authority under which the Client Registry operates and accepts responsibility to define scope, vet and prioritize use cases/user stories, and ensure agreement on the data specifications used in the Client Registry.

A client registry should be responsive to users’ needs and the local context. User stories and data specifications are two ways to describe: “What will the client registry achieve and How should it operate?” A primary objective of this guide is to promote and facilitate a country driven and user requirements based process. The ideal solution will be responsive to users’ needs and their context.

Using the draft specifications and user stories developed in Step 3 as a foundation to move forward, the next step is to determine resources and develop the project plan to support the implementation process of the client registry. This step will include selection of software, determining hardware needs, defining the patient matching algorithm (for specified use case), and validation/testing.

It should be expected that requirements and requests for the registry data feeds will evolve over time. For this reason support strategies should be developed and should remain in place to triage requests for data, system enhancements, integrations, operations support or general troubleshooting among users.

Post production, it is important to capture lessons learned. Once the system is running and stabilized, the iterative development process can begin again with an expanded scope. New interfaces, user stories or workflows may need to be added.

Community Resources


Participate in the discussion group and join our routine meetings to ask questions and get feedback.  Join Our Community Group 

Learn about best practices and access expertise, technologies and standards around client registries.  Visit Our Wiki Page

Meet other implementers and learn from their experiences.  Also use our Implementation Guide


Community Meetings