Appointment
Readiness: In review.
Open Appointment profile on Simplifier
Profile base: no-basis-Appointment. Reusing the national profile keeps dental bookings within the Norwegian appointment model.
Design choices
DigiDOT shares the booking needed to coordinate care while the EHR remains responsible for its calendar. A booking can exist before a clinician or room is assigned. It can also be cancelled without any clinical contact taking place.
The dental service category identifies the domain. A specialty describes particular competence needed for the visit; it is not a substitute for the assigned practitioner. The specialty selection reuses SNOMED CT concepts from FHIR's practice-setting terminology.
Use in practice
In the recall-to-treatment scenario, the recall request explains why a visit is due, Appointment schedules it, and Encounter records the actual contact. One cancellation or no-show does not automatically end the underlying recall or care responsibility.
When mapping an EHR calendar, establish what its statuses mean. A past booking date does not prove attendance; a listed clinician does not prove acceptance. Planned appointment times must not supply missing actual contact times. An unassigned booking should remain unassigned rather than acquire an invented practitioner.
For references inside a transaction, validate the complete Bundle so that a Patient referenced by a UUID can be resolved. See References and identifiers.
EHDS and later FHIR versions
An appointment supplies planning context; it does not establish that the care described in an EHDS encounter or procedure record occurred. An exchange mapping must preserve that distinction rather than turn calendar entries into clinical events.
FHIR R5 Appointment adds recurrence templates and virtual-service information, and changes how reasons are represented. A future migration should assess whether these features help exchange actual booking series. Calendar recurrence still does not replace the clinical decision represented by a DigiDOT recall request. See the shared EHDS and migration assessment.
Examples
| Example | Scenario |
|---|---|
| Fulfilled booking | A visit linked to its request and care responsibility. |
| Endodontic specialty | A booking requiring particular competence. |
| No-show / cancelled | Attendance and cancellation without inventing delivered care. |
| Proposed / waiting list | Scheduling before a visit time is allocated. |
| UUID reference | Patient resolution within a Bundle. |