EM-HCP-03 · Subject model · W-IND
Patient encounter
An interaction between a patient and a provider: an outpatient visit, an admission, a stay or a remote contact, with its period, location, participants, reason and discharge. Clinical findings and orders are linked, not stored in the encounter.
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
- Encounter
- EncounterLocation
- EncounterParticipant
- Admission
- Discharge
- EncounterReason
Deep research questions
- When does a transfer between wards create a new encounter and when only a location change?
- How are the encounter class and service type kept apart from billing categories?
- Which participant roles are needed for accountability?
Verifiable invariants
- Every encounter belongs to exactly one patient record
- Location periods within one encounter do not overlap
- A finished encounter has an end time and a discharge disposition
End-to-end acceptance scenario
For a synthetic emergency visit that becomes an admission with one ward transfer, record locations, participants and discharge, and link the orders and documents created during the stay.
Negative case
A billing case is treated as the encounter, so two clinically separate stays merged for billing appear as one visit.
Approaches to compare
- HL7 FHIR: Encounter resource
- openEHR: composition context and care setting
- Admission, discharge and transfer practice
Candidates in the live catalogue
- WM-ACT-018 · Encounter · 1.0.0 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-014 · Health Care Delivery · 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.