Core entity relationships

Organization id · name · type Facility id · orgId · name · city Practitioner id · name · role · facilityId Patient Blue Care Health ID · Omang name · DOB · sex · matchStatus registeredAt (Facility) registers at MPI candidate match patientA · patientB · score · band Encounter id · patientId · facilityId · practitionerId · date AllergyIntolerance substance · criticality · reaction MedicationStatement medication · dosage · status Consent patientId · grantedToOrg · status AuditEvent actor · action · resource · outcome every write is logged

Blue Care Health ID format

BW-BCH-#######

MPI matching — how a candidate match is scored

A deterministic pass runs first; anything not resolved there falls through to weighted probabilistic scoring. This is exactly the mechanism shown live on the MPI review screen — the rule table below is the same configuration that screen renders against.

1 · Deterministic passes (auto-link, no review)

2 · Probabilistic weights

3 · Outcome bands

Data-quality notes handled explicitly in the model: estimated date of birth is a flag on the Patient record (reduces DOB match confidence rather than excluding the field), and previous / preferred names are stored as an array so a name change doesn't read as a mismatch against history.