Open Client Registry (OpenCR)

6.5easy start · #8 of 25
in Identity Resolution Software

Free to practise onnot on record
Free trialnot on record
Well documentedyes
Runs where you workyes

Runs on api, Linux, Mac, self-hosted, Web, Windows.

Open Client Registry (OpenCR) is ranked #8 of 25 in identity resolution software on The Geeks Club. It runs on API, Linux, macOS, Self-hosted, Web, Windows.

Compared on identity resolution software

Matching approach: hybrid
Real-time API: Yes
Batch file import: Yes

Best Open Client Registry (OpenCR) alternatives

See all 20

InterSystems IRIS 0 of 4 in the starter kit Lesson 18.0 Hightouch 0 of 4 in the starter kit Lesson 27.1 Senzing Entity Resolution 0 of 4 in the starter kit Lesson 37.1 Zingg 0 of 4 in the starter kit Lesson 47.0 Splink 0 of 4 in the starter kit Lesson 56.9 Data Ladder 0 of 4 in the starter kit Lesson 66.6

The record

Purpose: OpenCR links patient identities across information systems to support care coordination, continuity of care, and reporting.
Matching: It supports configurable patient matching using probabilistic and deterministic methods and multiple algorithm variations.
Identifiers and messages: OpenCR can assign and look up unique identifiers and accept FHIR messages from point-of-service systems such as labs and EMRs.
Manual review: Its UI lets users view records and break matches between records.
Architecture: The documented stack includes the OpenCR Service, HAPI FHIR Server, and either OpenSearch or Elasticsearch; OpenHIM is optional.
Integrations: The documentation describes FHIR R4, HAPI FHIR, OpenHIM, and OpenSearch or Elasticsearch as components or connections in an OpenCR deployment.
Security: The security guidance recommends restricting the UI and services, using TLS, changing default passwords, and securing access with user and node authentication.
Auditing: Transactions, including queries, are stored as audit events in HAPI FHIR and can be viewed in the OpenCR UI.
Authentication limitation: The documentation says JWT and other user authentication solutions are not provided out of the box and can be added for a deployment.
Data limitation: OpenCR is not a shared health record and does not contain patient clinical data.
Deployment: The production installation guide expects Linux and says production deployment requires command-line familiarity and Linux administration expertise.
Production storage: HAPI FHIR requires a database backend in production, with PostgreSQL or MySQL given as examples.
Support: The About page directs inquiries to [email protected] and invites users to join the OpenCR Slack channel.
Maker: The About page says OpenCR was developed by IntraHealth International with USAID support through the MEASURE Evaluation project.

Where it ranks on The Geeks Club

Best Identity Resolution Software in 2026#8 of 25

Is Open Client Registry (OpenCR) yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote Open Client Registry (OpenCR)

Sources

openclientregistry.org· checked 4 Oct 2026
intrahealth.github.io/client-registry/· checked 4 Oct 2026
intrahealth.github.io/client-registry/admin/architecture/· checked 4 Oct 2026
intrahealth.github.io/client-registry/admin/configuration/· checked 4 Oct 2026
intrahealth.github.io/client-registry/admin/security/· checked 4 Oct 2026
intrahealth.github.io/client-registry/admin/installation_full· checked 4 Oct 2026
openclientregistry.org/about· checked 4 Oct 2026