- A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s) Base StructureDefinition for Appointment Resource
-
-
Key: = Must support, = QICore-defined extension, = Is-Modifier
Field Card. Type and Description 
appointmentType 0..1ConceptThe style of appointment or patient that has been booked in the slot (not service type).Binding: value set (Preferred)
comment 0..1StringAdditional comments about the appointment.created 0..1DateTimeThe date that this appointment was initially created. This could be different to the meta.lastModified value on the initial entry, as this could have been before the resource was created on the FHIR server, and should remain unchanged over the lifespan of the appointment.description 0..1StringThe brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list. Detailed or expanded information should be put in the comment field.end 0..1DateTimeDate/Time that the appointment is to conclude.identifier 0..*List<Identifier>This records identifiers associated with this appointment concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).minutesDuration 0..1positiveIntNumber of minutes that the appointment is to take. This can be less than the duration between the start and end times (where actual time of appointment is only an estimate or is a planned appointment request).participant 1..*List<Participant>List of participants involved in the appointment.priority 0..1unsignedIntThe priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments. (The iCal Standard specifies 0 as undefined, 1 as highest, 9 as lowest priority).reason 0..1ConceptThe reason that this appointment is being scheduled. This is more clinical than administrative.Binding: Encounter Reason Codes (Preferred)
serviceCategory 0..1ConceptA broad categorisation of the service that is to be performed during this appointment.Binding: ServiceCategory (Example)
serviceType 0..*List<Concept>The specific service that is to be performed during this appointment.Binding: ServiceType (Example)
slot 0..*List<Slot>The slot that this appointment is filling. If provided then the schedule will not be provided as slots are not recursive, and the start/end values MUST be the same as from the slot.specialty 0..*List<Concept>The specialty of a practitioner that would be required to perform the service requested in this appointment.Binding: Practice Setting Code Value Set (Preferred)
start 0..1DateTimeDate/Time that the appointment is to take place.status 1..1codeThe overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.Binding: AppointmentStatus (Required)
Key: = Must support, = QICore-defined extension, = Is-Modifier
-