0.1.4 - draft
0.1.4 - draft
NabotoImplementationGuide - Local Development build (v0.1.4). See the Directory of published versions
Summary
| Defining URL: | http://fhir.naboto.com/ValueSet/naboto-appointment-status |
| Version: | 0.1.4 |
| Name: | NabotoAppointmentStatus |
| Status: | Active as of 2022-11-03 01:30:17+0000 |
| Definition: | The free/busy status of an appointment. |
| Publisher: | Naboto Software GmbH |
| Source Resource: | XML / JSON / Turtle |
References
http://hl7.org/fhir/appointmentstatus| Code | Display | Definition |
| booked | Booked | All participant(s) have been considered and the appointment is confirmed to go ahead at the date/times specified. |
| arrived | Arrived | The patient/patients has/have arrived and is/are waiting to be seen. |
| 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. |
| cancelled | Cancelled | The appointment has been cancelled. |
| noshow | No Show | Some or all of the participant(s) have not/did not appear for the appointment (usually the patient). |
| entered-in-error | Entered in error | This instance should not have been part of this patient's medical record. |
| 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). |
This value set contains 7 concepts
Expansion based on AppointmentStatus v4.0.1 (CodeSystem)
| Code | System | Display | Definition |
| booked | http://hl7.org/fhir/appointmentstatus | Booked | All participant(s) have been considered and the appointment is confirmed to go ahead at the date/times specified. |
| arrived | http://hl7.org/fhir/appointmentstatus | Arrived | The patient/patients has/have arrived and is/are waiting to be seen. |
| fulfilled | http://hl7.org/fhir/appointmentstatus | 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. |
| cancelled | http://hl7.org/fhir/appointmentstatus | Cancelled | The appointment has been cancelled. |
| noshow | http://hl7.org/fhir/appointmentstatus | No Show | Some or all of the participant(s) have not/did not appear for the appointment (usually the patient). |
| entered-in-error | http://hl7.org/fhir/appointmentstatus | Entered in error | This instance should not have been part of this patient's medical record. |
| checked-in | http://hl7.org/fhir/appointmentstatus | 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). |
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 |