LiveRamp RampID vs Open Client Registry (OpenCR)

LiveRamp RampID has no write-up on Specifiction yet; its figures are above.

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.