HL7 Terminology
2.1.0 - Publication

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: hl7VS-appointmentReasonCodes


Defining URL:http://terminology.hl7.org/ValueSet/v2-0276
Status:Active as of 2019-12-01

Value Set of codes that describe the kind of appointment or the reason why an appointment has been scheduled.

Publisher:HL7, Inc

Copyright HL7. Licensed under creative commons public domain

OID:2.16.840.1.113883.21.181 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle


Logical Definition (CLD)



This value set contains 5 concepts

Expansion based on appointmentReason v2.1.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v2-0276

ROUTINERoutine appointment - default if not valuedRoutine appointment - default if not valued
WALKINA previously unscheduled walk-in visitA previously unscheduled walk-in visit
CHECKUPA routine check-up, such as an annual physicalA routine check-up, such as an annual physical
FOLLOWUPA follow up visit from a previous appointmentA follow up visit from a previous appointment
EMERGENCYEmergency appointmentEmergency appointment

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
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)
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


2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.