Epsilon COREid vs Open Client Registry (OpenCR)
Epsilon COREid
epsilon.comOpen Client Registry (OpenCR)
openclientregistry.orgSide by side
| Figure | Epsilon COREid | Open Client Registry (OpenCR) |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 0 |
| Spec score · Identity Resolution Software | 7.4 (#12) | 7.4 (#13) |
| Integrations | Epsilon says COREid powers its customer data platform, which can activate audiences through owned channels such as email and SMS and paid channels such as digital media, CTV and online video. | The documentation describes FHIR R4, HAPI FHIR, OpenHIM, and OpenSearch or Elasticsearch as components or connections in an OpenCR deployment. |
| Purpose | COREid services provide identity resolution to recognize and reach more than 200 million U.S. consumers in a privacy-safe way. | OpenCR links patient identities across information systems to support clinical safety, continuity of care, and accurate reporting. |
| Security | Epsilon’s privacy notice says it uses firewalls, intrusion detection software and manual security procedures to help protect data against loss, damage, unauthorized access or improper use. | The documentation says the registry should communicate only with known, trusted clients using TLS certificates, and that standalone mode runs TLS by default and requires signed certificates. |
In their own words
Epsilon COREid
Epsilon COREid has no write-up on Specifiction yet; its figures are above.
Open Client Registry (OpenCR)
Open Client Registry (OpenCR) links patient identities across information systems to support care coordination, continuity of care and reporting. It offers configurable matching using probabilistic and deterministic methods, and can assign or look up unique identifiers and accept FHIR messages from point-of-service systems such as labs and EMRs. Its interface lets users inspect records and break matches. A deployment uses the OpenCR Service and HAPI FHIR Server with OpenSearch or Elasticsearch; OpenHIM is optional. Transactions, including queries, are stored as audit events in HAPI FHIR and can be viewed in the UI. OpenCR is open source and is listed for API, Linux, macOS, self-hosted, web and Windows environments. It is not a shared health record and does not contain patient clinical data. The production installation guide expects Linux, command-line familiarity and Linux administration expertise; HAPI FHIR needs a production database backend such as PostgreSQL or MySQL. JWT and other user authentication solutions are not provided out of the box and can be added for a deployment. The project describes itself as a community project intended for adaptation to different use cases.