AWS Entity Resolution vs Open Client Registry (OpenCR)

AWS Entity Resolution links records that may describe the same customer, product, business, or healthcare entity across applications, channels, and data stores. It offers rule-based, machine learning, and data service provider matching. Rule-based users can adjust input fields, priorities, and rules; the preconfigured machine learning model compares consumer fields such as names, email addresses, phone numbers, addresses, and birth dates, then assigns match groups confidence scores from 0.0 to 1.0. Inputs come from AWS Glue, with a limit of 20. Rule-based matching can process new Amazon S3 data incrementally, and the GetMatchId API can synchronously look up an existing match ID while hashing personally identifiable attributes. Access is through the AWS console and API. Personally identifiable data is encrypted at rest by default with AWS-owned keys, with customer-managed symmetric AWS KMS keys also supported. Provider matching includes LiveRamp, TransUnion, and Unified ID 2.0 identifiers, subject to a provider license agreement. AWS states that the service meets PCI DSS and SOC 1, SOC 2, and SOC 3 measures. Pricing is paid, from $0.10; there is no free plan.

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.