pub struct AppointmentInner {Show 72 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub status: AppointmentStatus,
pub status_ext: Option<FieldExtension>,
pub cancellation_reason: Option<CodeableConcept>,
pub cancellation_reason_ext: Option<FieldExtension>,
pub class: Vec<Option<CodeableConcept>>,
pub class_ext: Vec<Option<FieldExtension>>,
pub service_category: Vec<Option<CodeableConcept>>,
pub service_category_ext: Vec<Option<FieldExtension>>,
pub service_type: Vec<Option<CodeableReference>>,
pub service_type_ext: Vec<Option<FieldExtension>>,
pub specialty: Vec<Option<CodeableConcept>>,
pub specialty_ext: Vec<Option<FieldExtension>>,
pub appointment_type: Option<CodeableConcept>,
pub appointment_type_ext: Option<FieldExtension>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub priority: Option<CodeableConcept>,
pub priority_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub replaces: Vec<Option<Reference>>,
pub replaces_ext: Vec<Option<FieldExtension>>,
pub virtual_service: Vec<Option<VirtualServiceDetail>>,
pub virtual_service_ext: Vec<Option<FieldExtension>>,
pub supporting_information: Vec<Option<Reference>>,
pub supporting_information_ext: Vec<Option<FieldExtension>>,
pub previous_appointment: Option<Reference>,
pub previous_appointment_ext: Option<FieldExtension>,
pub originating_appointment: Option<Reference>,
pub originating_appointment_ext: Option<FieldExtension>,
pub start: Option<Instant>,
pub start_ext: Option<FieldExtension>,
pub end: Option<Instant>,
pub end_ext: Option<FieldExtension>,
pub minutes_duration: Option<NonZero<u32>>,
pub minutes_duration_ext: Option<FieldExtension>,
pub requested_period: Vec<Option<Period>>,
pub requested_period_ext: Vec<Option<FieldExtension>>,
pub slot: Vec<Option<Reference>>,
pub slot_ext: Vec<Option<FieldExtension>>,
pub account: Vec<Option<Reference>>,
pub account_ext: Vec<Option<FieldExtension>>,
pub created: Option<DateTime>,
pub created_ext: Option<FieldExtension>,
pub cancellation_date: Option<DateTime>,
pub cancellation_date_ext: Option<FieldExtension>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub patient_instruction: Vec<Option<CodeableReference>>,
pub patient_instruction_ext: Vec<Option<FieldExtension>>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub subject: Option<Reference>,
pub subject_ext: Option<FieldExtension>,
pub participant: Vec<Option<AppointmentParticipant>>,
pub participant_ext: Vec<Option<FieldExtension>>,
pub recurrence_id: Option<NonZero<u32>>,
pub recurrence_id_ext: Option<FieldExtension>,
pub occurrence_changed: Option<bool>,
pub occurrence_changed_ext: Option<FieldExtension>,
pub recurrence_template: Vec<Option<AppointmentRecurrenceTemplate>>,
pub recurrence_template_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
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 v5.0.0
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).
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicit_rules: Option<String>A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
text: Option<Narrative>Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
identifier: Vec<Option<Identifier>>External Ids for this item
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).
identifier_ext: Vec<Option<FieldExtension>>Extension field.
status: AppointmentStatusAppointmentStatus; proposed | pending | booked | arrived | fulfilled | cancelled | noshow | entered-in-error | checked-in | waitlist
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.
If the Appointment’s status is “cancelled” then all participants are expected to have their calendars released for the appointment period, and as such any Slots that were marked as BUSY can be re-set to FREE.
This element is labeled as a modifier because the status contains the code entered-in-error that mark the Appointment as not currently valid.
status_ext: Option<FieldExtension>Extension field.
cancellation_reason: Option<CodeableConcept>cancellation-reason; The coded reason for the appointment being cancelled
The coded reason for the appointment being cancelled. This is often used in reporting/billing/futher processing to determine if further actions are required, or specific fees apply.
cancellation_reason_ext: Option<FieldExtension>Extension field.
class: Vec<Option<CodeableConcept>>EncounterClass; Classification when becoming an encounter
Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.
class_ext: Vec<Option<FieldExtension>>Extension field.
service_category: Vec<Option<CodeableConcept>>service-category; A broad categorization of the service that is to be performed during this appointment
A broad categorization of the service that is to be performed during this appointment.
service_category_ext: Vec<Option<FieldExtension>>Extension field.
service_type: Vec<Option<CodeableReference>>service-type; The specific service that is to be performed during this appointment
The specific service that is to be performed during this appointment.
For a provider to provider appointment the code “FOLLOWUP” may be appropriate, as this is expected to be discussing some patient that was seen in the past.
service_type_ext: Vec<Option<FieldExtension>>Extension field.
specialty: Vec<Option<CodeableConcept>>specialty; The specialty of a practitioner that would be required to perform the service requested in this appointment
The specialty of a practitioner that would be required to perform the service requested in this appointment.
specialty_ext: Vec<Option<FieldExtension>>Extension field.
appointment_type: Option<CodeableConcept>appointment-type; The style of appointment or patient that has been booked in the slot (not service type)
The style of appointment or patient that has been booked in the slot (not service type).
appointment_type_ext: Option<FieldExtension>Extension field.
reason: Vec<Option<CodeableReference>>ApptReason; Reason this appointment is scheduled
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.
reason_ext: Vec<Option<FieldExtension>>Extension field.
priority: Option<CodeableConcept>Priority; Used to make informed decisions if needing to re-prioritize
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).
Seeking implementer feedback on this property and how interoperable it is.
Using an extension to record a CodeableConcept for named values may be tested at a future connectathon.
priority_ext: Option<FieldExtension>Extension field.
description: Option<String>Shown on a subject line in a meeting request, or appointment list
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.
description_ext: Option<FieldExtension>Extension field.
replaces: Vec<Option<Reference>>Appointment replaced by this Appointment
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).
replaces_ext: Vec<Option<FieldExtension>>Extension field.
virtual_service: Vec<Option<VirtualServiceDetail>>Connection details of a virtual service (e.g. conference call)
Connection details of a virtual service (e.g. conference call).
There are two types of virtual meetings that often exist:
- a persistent, virtual meeting room that can only be used for a single purpose at a time,
- and a dynamic virtual meeting room that is generated on demand for a specific purpose.
Implementers may consider using Location.virtualService for persistent meeting rooms.
If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail can be applied to the Appointment.participant BackboneElement.
virtual_service_ext: Vec<Option<FieldExtension>>Extension field.
supporting_information: Vec<Option<Reference>>Additional information to support the appointment
Additional information to support the appointment provided when making the appointment.
supporting_information_ext: Vec<Option<FieldExtension>>Extension field.
previous_appointment: Option<Reference>The previous appointment in a series
The previous appointment in a series of related appointments.
This property is intended for use when representing a series of related appointments. For example, in a nuclear medicine procedure, where there is an appointment for the injection of the isotopes, and then a subsequent appointment for the scan, the scan appointment would refer to the injection appointment via Appointment.previousAppointment. For representing recurring appointments, see the guidance on recurring vs. series appointments.
previous_appointment_ext: Option<FieldExtension>Extension field.
originating_appointment: Option<Reference>The originating appointment in a recurring set of appointments
The originating appointment in a recurring set of related appointments.
This property is intended for use when representing a recurring set of related appointments.
For example, a patient undergoing physical therapy may have a recurring appointment every Tuesday and Thursday. Each occurrence of the set will refer to the originating appointment, which contains the recurring template information. For representing appointment series, see the guidance on recurring vs. series appointments.
originating_appointment_ext: Option<FieldExtension>Extension field.
start: Option<Instant>When appointment is to take place
Date/Time that the appointment is to take place.
If actual start/end times are not known then the requested period start/end can be used.
start_ext: Option<FieldExtension>Extension field.
end: Option<Instant>When appointment is to conclude
Date/Time that the appointment is to conclude.
If actual start/end times are not known then the requested period start/end can be used.
end_ext: Option<FieldExtension>Extension field.
minutes_duration: Option<NonZero<u32>>Can be less than start/end (e.g. estimate)
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.
minutes_duration_ext: Option<FieldExtension>Extension field.
requested_period: Vec<Option<Period>>Potential date/time interval(s) requested to allocate the appointment within
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.
This does not introduce a capacity for recurring appointments.
requested_period_ext: Vec<Option<FieldExtension>>Extension field.
slot: Vec<Option<Reference>>The slots that this appointment is filling
The slots from the participants’ schedules that will be filled by the appointment.
slot_ext: Vec<Option<FieldExtension>>Extension field.
account: Vec<Option<Reference>>The set of accounts that may be used for billing for this Appointment
The set of accounts that is expected to be used for billing the activities that result from this Appointment.
The specified account(s) could be those identified during pre-registration workflows in preparation for an upcoming Encounter.
account_ext: Vec<Option<FieldExtension>>Extension field.
created: Option<DateTime>The date that this appointment was initially created
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.
This property is required for many use cases where the age of an appointment is considered in processing workflows for scheduling and billing of appointments.
created_ext: Option<FieldExtension>Extension field.
cancellation_date: Option<DateTime>When the appointment was cancelled
The date/time describing when the appointment was cancelled.
If the appointment was cancelled multiple times, this would reflect the most recent cancellation.
cancellation_date_ext: Option<FieldExtension>Extension field.
note: Vec<Option<Annotation>>Additional comments
Additional notes/comments about the appointment.
Additional text to aid in facilitating the appointment. For instance, a note might be, “patient should proceed immediately to infusion room upon arrival”
Where this is a planned appointment and the start/end dates are not set then this field can be used to provide additional guidance on the details of the appointment request, including any restrictions on when to book it.
Typically only the concept.text will be used, however occasionally a reference to some generic documentation (or specific) and also supports coded instructions if/when they are required.
note_ext: Vec<Option<FieldExtension>>Extension field.
patient_instruction: Vec<Option<CodeableReference>>Detailed information and instructions for the patient
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).
patient_instruction_ext: Vec<Option<FieldExtension>>Extension field.
based_on: Vec<Option<Reference>>The request this appointment is allocated to assess
The request this appointment is allocated to assess (e.g. incoming referral or procedure request).
based_on_ext: Vec<Option<FieldExtension>>Extension field.
subject: Option<Reference>The patient or group associated with the appointment
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.
subject_ext: Option<FieldExtension>Extension field.
participant: Vec<Option<AppointmentParticipant>>Participants involved in appointment
List of participants involved in the appointment.
participant_ext: Vec<Option<FieldExtension>>Extension field.
recurrence_id: Option<NonZero<u32>>The sequence number in the recurrence
The sequence number that identifies a specific appointment in a recurring pattern.
recurrence_id_ext: Option<FieldExtension>Extension field.
occurrence_changed: Option<bool>Indicates that this appointment varies from a recurrence pattern
This appointment varies from the recurring pattern.
For example, if a patient has physical therapy appointments every Tuesday and Thursday, but due to a national holiday, a single occurrence was rescheduled to a different day, while the rest of the recurring series remained on Tuesday / Thursday.
occurrence_changed_ext: Option<FieldExtension>Extension field.
recurrence_template: Vec<Option<AppointmentRecurrenceTemplate>>Details of the recurrence pattern/template used to generate occurrences
The details of the recurrence pattern or template that is used to generate recurring appointments.
recurrence_template_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for AppointmentInner
impl Clone for AppointmentInner
Source§fn clone(&self) -> AppointmentInner
fn clone(&self) -> AppointmentInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more