UnifyEMPI documentation

FHIR R4HL7v2 ADTMulti-tenantDemo live

UnifyEMPI links source Patient records into governed enterprise identities while preserving source provenance. Matching decisions remain bounded, explainable and reviewable.

Engineering foundation

UnifyEMPI is not a certified clinical product. Use only synthetic data in demos. Production NHS use requires independent clinical-safety, privacy, security, operational and contractual assurance.

Choose your route

Run it

Bring up the API, operations portal and HL7v2 listener with the ten-minute quick start.

Develop it

Map the projects, follow a feature, debug a host and run the test and benchmark suites with the developer guide.

Understand it

Start with the identity model and the NHS Wales source model.

Tune matching

Read the normative matching and blocking rules before changing candidate discovery, weights or thresholds.

Integrate existing FHIR

Use the existing FHIR integration guide to design a side-by-side store, bootstrap and synchronisation path.

Operate it

Use the configuration reference and production-readiness guide.

What the platform owns

flowchart LR
    SOURCES["Health boards, WDS, Velindre<br/>and other source systems"]
    INGEST["FHIR R4 API<br/>or HL7v2 MLLP"]
    EMPI["UnifyEMPI<br/>normalise · block · score · resolve"]
    REVIEW["Governed review<br/>merge · reject · split"]
    CONSUMERS["Canonical Patient<br/>and Person links"]

    SOURCES --> INGEST --> EMPI
    EMPI -->|"Probable or conflicting"| REVIEW
    REVIEW --> EMPI
    EMPI --> CONSUMERS

Source systems remain authoritative for their own Patient snapshots. UnifyEMPI owns enterprise UUIDv7 identities, links, candidate indexes, canonical views, review cases, receipts and audit evidence.

View implementationBrowse the UnifyEMPI repository on GitHub.

Inspect FHIR capabilitiesOpen the live demo API CapabilityStatement.