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.

Access

What the endpoint offers

Declared for AppointmentResponse by the capability statements this IG publishes. One row per statement; follow it for the rest of what that statement says about this type.

Capability statement	Interactions	Search parameters
Server Capability Statement	read vread history-instance search-type create update	none declared

A cell reading none declared means that statement declares none, which is not the same as the endpoint having none. See how to read a capability statement for what a declared interaction and a declared search parameter do -- and do not -- promise.

SMART on FHIR scopes

AppointmentResponse is reachable by a SMART on FHIR app. These are the scopes an app can request, and the platform permission each one resolves to.

Request this scope	Grants	Permission required
user/AppointmentResponse.rs	Read and search	appointmentresponse:read
user/AppointmentResponse.cu	Create and update	appointmentresponse:write

AppointmentResponse is in the FHIR patient compartment, so every suffix above also works with the patient context (patient/AppointmentResponse.rs), which narrows the grant to the launch patient's records. The permission required is the same either way.

Narrowed exposure

AppointmentResponse declares no delete permission, so an app cannot delete it however the scope is written.

Reading the suffix

A clinical scope is <context>/<ResourceType>.<interactions>.

• Context is patient (the launch patient's data only, and only for resource types in the FHIR patient compartment) or user (everything the authenticated user may see, valid for any type). There is no system context.
• Interactions are the letters c create, r read, u update, d delete, s search, written in cruds order. Order does not matter on the way in: AppointmentResponse.sr and AppointmentResponse.rs are the same scope.
• The older SMART v1 suffixes still work and fold on arrival: .read becomes .rs, .write becomes .cud, and .* becomes .cruds.
• Wildcards (patient/*.rs) expand over the SMART-exposed resource types only, never over everything this IG profiles.

Ask for a whole permission, or none of it

The platform has one read permission covering both r and s, and one write permission covering both c and u. A scope asking for half of either could only be granted by handing over more than it asked for, so it is refused rather than quietly widened: request AppointmentResponse.rs, not AppointmentResponse.r.

An unrecognised or ungrantable scope is rejected outright. It never silently resolves to an empty grant, which a caller could mistake for "no narrowing needed".