Skip to content

Appointment Response Profile

Canonical../StructureDefinition/nexus-appointment-response
Statusdraft · 1.26.0
BaseAppointmentResponse (constraint)
SourceFSH · 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.

Elements / Key elements

The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.

Element Flags Card. Type Description & Constraints
AppointmentResponse 0..* A participant's answer to a booking
Invariants: apr-1, dom-2, dom-3, dom-4, dom-5, dom-6
meta 0..1 Meta Metadata about the resource
Invariants: ele-1
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
Invariants: ele-1
implicitRules ?! 0..1 uri A set of rules under which this content was created i
Invariants: ele-1
text S 0..1 Narrative Narrative i
Invariants: ele-1
identifier S 0..* Identifier Business identifier(s) for the answer i
Invariants: ele-1
appointment S 1..1 Reference(Appointment Profile) The appointment this answers
Invariants: ele-1
actor S 0..1 Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location) The party whose answer this is i
Invariants: ele-1
participantStatus S ?! 1..1 code accepted | declined | tentative | needs-action i
Binding: participationstatus (required)
Invariants: ele-1