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). 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). If the element is present, it must have either a @value, an @id, or extensions 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). The 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. The coded reason for the appointment being cancelled. This is often used in reporting/billing/further processing to determine if further actions are required, or specific fees apply. Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. A broad categorization of the service that is to be performed during this appointment. The specific service that is to be performed during this appointment. The specialty of a practitioner that would be required to perform the service requested in this appointment. The style of appointment or patient that has been booked in the slot (not service type). The reason that this appointment is being scheduled. This is more clinical than administrative. This can be coded, or as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. The 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). The 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 note field. Appointment replaced by this Appointment in cases where there is a cancellation, the details of the cancellation can be found in the cancellationReason property (on the referenced resource). Connection details of a virtual service (e.g. conference call). Additional information to support the appointment provided when making the appointment. The previous appointment in a series of related appointments. The originating appointment in a recurring set of related appointments. Date/Time that the appointment is to take place. Date/Time that the appointment is to conclude. Number of minutes that the appointment is to take. This can be less than the duration between the start and end times. For example, where the actual time of appointment is only an estimate or if a 30 minute appointment is being requested, but any time would work. Also, if there is, for example, a planned 15 minute break in the middle of a long appointment, the duration may be 15 minutes less than the difference between the start and end. A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within. The duration (usually in minutes) could also be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. However, in other situations the duration may be calculated by the scheduling system. The slots from the participants' schedules that will be filled by the appointment. The set of accounts that is expected to be used for billing the activities that result from this Appointment. The 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. The date/time describing when the appointment was cancelled. Additional notes/comments about the appointment. While Appointment.note contains information for internal use, Appointment.patientInstructions is used to capture patient facing information about the Appointment (e.g. please bring your referral or fast from 8pm night before). The request this appointment is allocated to assess (e.g. incoming referral or procedure request). The patient or group associated with the appointment, if they are to be present (usually) then they should also be included in the participant backbone element. List of participants involved in the appointment. The sequence number that identifies a specific appointment in a recurring pattern. This appointment varies from the recurring pattern. The details of the recurrence pattern or template that is used to generate recurring appointments. 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). Role of participant in the appointment. Participation period of the actor. The individual, device, location, or service participating in the appointment. Whether this participant is required to be present at the meeting. If false, the participant is optional. Participation status of the actor. 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). The timezone of the recurring appointment occurrences. How often the appointment series should recur. Recurring appointments will not occur after this date. How many appointments are planned in the recurrence. The list of specific dates that will have appointments generated. Information about weekly recurring appointments. Information about monthly recurring appointments. Information about yearly recurring appointments. Any dates, such as holidays, that should be excluded from the recurrence. Any dates, such as holidays, that should be excluded from the recurrence. 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). Indicates that recurring appointments should occur on Mondays. Indicates that recurring appointments should occur on Tuesdays. Indicates that recurring appointments should occur on Wednesdays. Indicates that recurring appointments should occur on Thursdays. Indicates that recurring appointments should occur on Fridays. Indicates that recurring appointments should occur on Saturdays. Indicates that recurring appointments should occur on Sundays. The interval defines if the recurrence is every nth week. The default is every week, so it is expected that this value will be 2 or more. e.g. For recurring every second week this interval would be 2, or every third week the interval would be 3. 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). Indicates that appointments in the series of recurring appointments should occur on a specific day of the month. Indicates which week within a month the appointments in the series of recurring appointments should occur on. Indicates which day of the week the recurring appointments should occur each nth week. Indicates that recurring appointments should occur every nth month. 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). Appointment recurs every nth year. Proposed Pending Booked Arrived Fulfilled Cancelled No Show Entered in error Checked In Waitlisted If the element is present, it must have either a @value, an @id, or extensions Accepted Declined Tentative Needs Action If the element is present, it must have either a @value, an @id, or extensions