Appointment Response Profile¶
| Canonical | ../StructureDefinition/nexus-appointment-response |
|---|---|
| Status | draft · 1.26.0 |
| Base | AppointmentResponse (constraint) |
| Source | FSH · JSON |
A participant's answer to a booking: whether the person an appointment is for has accepted it, is still deciding, or has declined. Written by an integrating system outside the EMR and read wherever a booking's confirmation state is displayed, which is derived from participantStatus rather than from Appointment.status. An answer supersedes an earlier answer rather than amending it, and the latest one describes where the booking stands.
Examples
Conforming instances (each opens inside this tab):
- Answer Stored Without a Status — An answer that arrived carrying neither a participantStatus nor an actor. The element is mandatory in R4, so it is filled in as tentative rather than the resource being rejected a…
- Booking Confirmed by the Patient — The answer a day sheet reads to show a booking as Confirmed. The confirmation lives here and not on the appointment, whose status is still booked -- a consumer reading only Appoin…