EMA Scheduling Implementation Guide
0.1.0 - ci-build
EMA Scheduling Implementation Guide
0.1.0 - ci-build
EMA Scheduling Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://emahealth.io/fhir/scheduling/ValueSet/ema-appointment-status | Version: 0.1.0 | |||
| Draft as of 2026-03-09 | Computable Name: EmaAppointmentStatus | |||
Estados permitidos para una cita en EMA Clinic.
References
http://hl7.org/fhir/appointmentstatus version 📦4.0.1| Code | Display | Definition |
| 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. |
| pending | Pending | Some or all of the participant(s) have not finalized their acceptance of the appointment request. |
| 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). |
Expansion performed internally based on codesystem AppointmentStatus v4.0.1 (CodeSystem)
This value set contains 7 concepts
| System | Code | Display (es) | Definition | JSON | XML |
http://hl7.org/fhir/appointmentstatus | proposed | None of the participant(s) have finalized their acceptance of the appointment request, and the start/end time might not be set yet. | |||
http://hl7.org/fhir/appointmentstatus | pending | Some or all of the participant(s) have not finalized their acceptance of the appointment request. | |||
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. | |||
http://hl7.org/fhir/appointmentstatus | arrived | The patient/patients has/have arrived and is/are waiting to be seen. | |||
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. | |||
http://hl7.org/fhir/appointmentstatus | cancelled | The appointment has been cancelled. | |||
http://hl7.org/fhir/appointmentstatus | noshow | Some or all of the participant(s) have not/did not appear for the appointment (usually the patient). |
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 |
| System | 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 |