Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3 R2

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.4.1.123 4.4.1.150 Value Set ValueSet http://hl7.org/fhir/ValueSet/appointmentstatus

  Maturity Level : 3
Responsible Owner: Patient Administration icon Work Group Trial Use Normative Use Context : Any Country: World
This is a value set defined by the FHIR project. Summary Committee:
Official URL : Title: http://hl7.org/fhir/ValueSet/appointmentstatus AppointmentStatus Definition: The free/busy status of an appointment. Version : 6.0.0-ballot3
active as of 2020-12-28 Patient Administration Computable Name : AppointmentStatus Work Group
OID: Flags : Immutable 2.16.840.1.113883.4.642.3.484 (for OID based terminology systems) Source Resource XML / JSON : 2.16.840.1.113883.4.642.3.484

This value set is used in the following places:

4.4.1.123.1 4.4.1.150.1 Definition

The free/busy status of an appointment.

4.4.1.150.2 Content Logical Definition

Generated Narrative: ValueSet appointmentstatus This value set includes codes from the following code systems:

Last updated: 2025-11-24T20:46:00.1Z

 

4.4.1.123.2 4.4.1.150.3 Expansion

This expansion generated 01 24 Nov 2019 2025

ValueSet This value set contains 10 concepts

Expansion performed internally based on http://hl7.org/fhir/appointmentstatus version 4.0.1 All codes from system http://hl7.org/fhir/appointmentstatus codesystem Appointment Status v6.0.0-ballot3 (CodeSystem)

This value set contains 10 concepts

System Code Display Definition Canonical Status Mapping for "Appointment Status"
http://hl7.org/fhir/appointmentstatus    proposed Proposed

None of the participant(s) have finalized their acceptance of the appointment request, and the start/end time might not be set yet.

~ proposed
http://hl7.org/fhir/appointmentstatus    pending Pending

Some or all of the participant(s) have not finalized their acceptance of the appointment request.

~ draft
http://hl7.org/fhir/appointmentstatus    booked Booked

All participant(s) have been considered and the appointment is confirmed to go ahead at the date/times specified.

~ accepted
http://hl7.org/fhir/appointmentstatus    arrived Arrived

The patient/patients has/have arrived and is/are waiting to be seen.

~ arrived
http://hl7.org/fhir/appointmentstatus    fulfilled Fulfilled

The planning stages of the appointment are now complete, the encounter resource will exist and will track further status changes. Note that an encounter may exist before the appointment status is fulfilled for many reasons.

~ complete
http://hl7.org/fhir/appointmentstatus    cancelled Cancelled

The appointment has been cancelled.

~ abandoned
http://hl7.org/fhir/appointmentstatus    noshow No Show

Some or all of the participant(s) have not/did not appear for the appointment (usually the patient).

~ suspended
http://hl7.org/fhir/appointmentstatus    entered-in-error Entered in error

This instance should not have been part of this patient's medical record.

~ error
http://hl7.org/fhir/appointmentstatus    checked-in Checked In

When checked in, all pre-encounter administrative work is complete, and the encounter may begin. (where multiple patients are involved, they are all present).

~ partial
http://hl7.org/fhir/appointmentstatus    waitlist Waitlisted

The appointment has been placed on a waitlist, to be scheduled/confirmed in the future when a slot/service is available. A specific time might or might not be pre-allocated.

~ proposed

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code