EM-HCP-01 · Subject model · W-IND
Patient record at a care provider
The provider's record of a person as a patient: local record numbers, identity matching, contacts for care, and merge and unmerge of duplicate records. The person, legal capacity and clinical content are separate.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- PatientRecord
- PatientIdentifier
- IdentityMatch
- RecordMerge
- CareContact
Deep research questions
- Which identifiers are local, which are national and which belong to an insurer?
- How is a merge of two patient records reversed without losing clinical history?
- Which contact and representative details are needed for care and which are not?
Verifiable invariants
- A patient record belongs to exactly one person, and a merge keeps both source records
- Each identifier states its issuing system
- A representative is recorded with the basis of authority
End-to-end acceptance scenario
On synthetic records, detect a probable duplicate, merge it with human confirmation, then unmerge it after a mistake is found, keeping every encounter and order in the right record.
Negative case
Two patients with the same name and birth date are merged automatically, and a test result is filed in the wrong record.
Approaches to compare
- HL7 FHIR: Patient resource
- IHE PIX and PDQ: patient identifier cross-referencing and demographics query
- National patient identifier and health insurance identifier practice
Candidates in the live catalogue
- WM-PER-001 · Person · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-PER-007 · Personal Health · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.