Encounter

Readiness: In review.

Open Encounter profile on Simplifier

Profile base: FHIR R4 Encounter. The selected no-basis 2.2.2 package has no Encounter profile.

Design choices

Encounter provides a shared contact context for findings, measurements, procedures and notes. Appointment remains the booking, and EpisodeOfCare represents a longer period of organisational responsibility. A contact need not have either planning record when care occurs without prior planning.

Care setting and contact purpose are separate: class describes where or how the contact takes place, while type can distinguish a check-up, follow-up or other primary purpose. The contact-type selection reuses SNOMED CT concepts also used in US Core Encounter Type; it does not adopt the US profile, its full selection or CPT codes. The exact codes are maintained in the DigiDOT ValueSet.

Use in practice

The recall-to-treatment scenario has separate contacts for examination and restoration. Both can address the same continuing responsibility. The original caries finding keeps its originating contact when later treatment refers to it.

Situation Interpretation
Recall examination Link the applicable request. A check-up classification alone does not establish recall enrolment.
Several purposes in one visit Use the source's primary contact type when established; do not invent a precedence rule or split the contact merely to classify it.
Urgent care in an ordinary clinic Urgency alone does not make it a dedicated emergency-service encounter.
Home or virtual visit Preserve the actual setting without creating an artificial clinic location.
Cancelled booking or no-show Do not create an actual-care Encounter merely because the Appointment exists.

An Encounter that was initiated and then cancelled is distinct from a booking cancelled before any contact. Arrival, clinical activity and note finalisation can also happen at different times. Map these events from the source rather than derive them from the appointment date.

The health-group value preserves the classification applicable to this contact. Today's Patient classification must not silently rewrite earlier care. See Health groups for the dated selection and correction rules, including the earlier and later contact examples.

EHDS and later FHIR versions

In the EHDS Encounter model, the element named type includes inpatient, ambulatory and teleconsultation. That is closer to FHIR Encounter's care-setting classification than to the DigiDOT contact-purpose selection. Mapping by identical field names would be misleading. EHDS also covers broader admission and discharge information than this dental-contact profile.

FHIR R5 Encounter changes the status model, makes class a repeating CodeableConcept, renames period to actualPeriod and changes participant and reason structures. The R6 development model adds business-status information. Migration therefore needs explicit lifecycle and context mapping; it is not just a profile-version update. See the shared assessment.

Examples

Examples Scenario
Clinic contact / emergency service Different care settings.
Recall / follow-up Different contact purposes.
Problem-focused / treatment consultation / new patient Purpose does not itself specify the treatment delivered.
Home visit / video follow-up Care outside a clinic setting.