Skip to content

Schedule Code CodeSystem Code system

Canonicalhttps://fhir.apps.health/CodeSystem/schedule-code
Statusdraft · 1.33.0
Contentcomplete
SourceFSH · JSON

How the appointments on a schedule are delivered.

Carried on Slot.serviceType and Slot.appointmentType, and on Schedule.serviceType for the schedule those slots belong to -- the same elements a converted schedule uses for the source EMR's own template code.

R4's bindings on those elements are example-strength and name which service, not how it is delivered, so this concept has no standard system to draw from and is declared locally.

The list is complete: it is reconciled onto every deployment from one platform-side definition, so a deployment holds these three codes and no others. The value set a client expands (https://fhir.apps.health/ValueSet/schedule-code) is a per-deployment artifact held in each deployment's own store, not an artifact of this specification.

CodeDisplayDefinitionProperties
status
routineRoutineDEPRECATED -- write `ROUTINE` from HL7 v2-0276 instead. Ordinary booked appointments, with no delivery qualification. THE PUBLISHED CODE IS THE ONE THE BINDING ASKS FOR: `Slot.appointmentType` binds `http://terminology.hl7.org/ValueSet/v2-0276` at PREFERRED strength in base R4, and that value set contains `ROUTINE` with the same meaning. A preferred binding is FHIR saying which vocabulary to reach for first, so minting a local synonym of a code inside it is the case the binding exists to prevent. Retained because stored schedules carry this code and it must stay representable.deprecated
clinicClinicDEPRECATED -- write the appointment modality vocabulary instead. Appointments delivered in person at the clinic site the schedule names. THIS DUPLICATES THIS GUIDE'S OWN VOCABULARY, which is the sharper objection: `nexus-emr-appointment-modality-cs` already carries in-person and remote delivery, so one package published two local vocabularies for one axis. Where a schedule needs to state delivery, state it in the modality system; where an appointment states it, the modality extension is already the declared home. Retained because stored schedules carry this code.deprecated
telehealthTelehealthDEPRECATED -- write the appointment modality vocabulary instead. Appointments delivered remotely, by video or telephone, rather than at a site. Same objection as `clinic`: this axis is already modelled in `nexus-emr-appointment-modality-cs`, and this guide should not carry two answers to one question. Retained because stored schedules carry this code.deprecated

Properties

What each property column means, and how many of the 3 concepts carry it.

Property Type Group Concepts Description
status code Properties 3 of 3 Concept lifecycle status (active | deprecated | retired).