← Back to catalogue
Published

Patient record at a care provider

EM-HCP-01 · em-hcp-01

Make sure every clinical record, order and document is filed against the right person, and that identity errors can be found and corrected.

Enterprise profiles Enterprise subject EnterpriseHCP
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 8 questions

Patient identity Who the record belongs to.

Identifiers and matching

Identifiers, demographic matching and duplicates.

Identifiers

Identifiers with their issuing systems.

  1. Which identifiers does this patient record hold, and which system issued each one?
  2. Which demographic details were used to match this patient record?

Duplicates

Merges and unmerges of records.

  1. Which records were merged into this patient record, by whom and when?
  2. Was this patient record ever unmerged, and which entries were moved?
Contacts and representation How the patient is reached and who may act for them.

Care contacts

Contact details, representatives and disclosure limits.

Contacts

Contact details and stated preferences.

  1. Which contact details are recorded for care communication, and has the patient stated preferences?

Representatives

Legal representatives, emergency contacts and restrictions.

  1. Who is recorded as legal representative or emergency contact of this patient, and on what basis?
  2. Which restrictions on disclosure apply to this patient record?
  3. Which other providers or systems share this patient's identifiers through cross-referencing?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseHCP
Industry
Healthcare provider
Tags
EM-HCP-01W-INDsubjectPatientRecordPatientIdentifierIdentityMatchRecordMergeCareContact

What it is Filled

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.

Why it exists Filled

Make sure every clinical record, order and document is filed against the right person, and that identity errors can be found and corrected.

Distinguishing features Filled

  • A patient record is the provider's role record of a person, not the person itself.
  • Identifiers always state their issuing system.
  • Merges can be reversed and keep the source records.
  • Clinical content lives in the encounter, order and document contours.

What robots and AI may and may not do Filled

Must not

  • Merge or unmerge patient records without human confirmation.
  • Disclose a patient's identity or contacts outside the care purpose.
  • Infer clinical information from identity data.

Only with a human decision

  • A trained registration or data quality staff member must confirm merges and unmerges.
  • Changes of a legal representative require verification by staff.

May

  • Flag probable duplicate records for review.
  • Check that identifiers have an issuing system.
  • Prepare a merge proposal with its evidence.

Moral aspects Filled

  • Identity errors can cause harm through wrong treatment or wrong results.
  • Patient identity data is sensitive and must be limited to the care purpose.

Who is affected

  • Patients
  • Legal representatives and relatives
  • Clinical and registration staff

Owners Filled

Steward

The head of patient registration who answers for the accuracy of patient identity.

Master systems

  • Patient administration system
  • Electronic health record system
  • Master patient index

Links to other meta-models Filled

neighbor

  • EM-PEO-01
  • EM-XCT-01
  • EM-LEG-06
  • EM-HCP-03
  • EM-HCP-08

references

  • WM-PER-001 - conceptual-candidate
  • WM-PER-007 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A patient record has a local record number unique within the provider.
  • Other identifiers are held together with the system or authority that issued them.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Filled

  • Records show identifiers, demographic details and care contacts of one patient.
  • A patient record must be distinguished from a person profile in HR or customer systems.

Capabilities and actions required Filled

  • The contour supports registration, duplicate detection, merge and unmerge, and identifier cross-referencing.

Hazards and failure modes required Filled

  • A wrong merge can file results or prescriptions in the wrong patient's record.
  • Excess identity data increases the harm from a breach.

Standards and interfaces optional Filled

  • HL7 International publishes the FHIR Patient resource for patient demographics.
  • IHE publishes the PIXm and PDQm profiles for patient identifier cross-referencing and demographics query.

Context of use required Filled

  • The contour is used by hospitals, clinics, laboratories and other care providers.
  • The health data protection rules of each jurisdiction apply to the record.

Sources Filled

  1. HL7 FHIR: Patient resource
  2. IHE PIX and PDQ: patient identifier cross-referencing and demographics query
  3. National patient identifier and health insurance identifier practice
  4. HL7 FHIR R4 Patient resource - Checked live (HTTP 200) on 2026-10-21.
  5. IHE Patient Identifier Cross-referencing for Mobile (PIXm) - Checked live (HTTP 200) on 2026-10-21.
  6. IHE Patient Demographics Query for Mobile (PDQm) - Checked live (HTTP 200) on 2026-10-21.

Open 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?
  • Settle the boundary and the reuse, extend or new decision against the current specifications.
  • Confirm the semantic crosswalk, rights and source mastership.
  • Choose immutable references and run fixture checks before claiming publication readiness.

Machine files

Card as JSON Source Card backlog vercy.card/1

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-hcp-01/brief.json, ver-cy/world-models/card-supplements/em-hcp-01.json