Name Flags Card. Type Description & Constraints Appointment 0..* Appointment 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) status 1..1 code proposed | pending | booked | arrived | fulfilled | cancelled | noshow | entered-in-error | checked-in | waitlist cancellationReason 0..1 CodeableConcept 取消预约原因 serviceCategory 0..* CodeableConcept 号源分类 appointmentType 0..1 CodeableConcept 预约患者类型 start 0..1 instant 预约开始时间 end 0..1 instant 预约结束时间 slot 0..* Reference(日程计划可预约时间段本地化定义) The slots that this appointment is filling created 0..1 dateTime 预约申请创建时间 cancellationDate 0..1 dateTime 取消预约申请时间 participant 1..* BackboneElement 预约的参与者 required 0..1 boolean 标识该参与者是否必须参加 Documentation for this format
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)
Either start and end are specified, or neither
Only proposed or cancelled appointments can be missing start/end dates
(start.exists() and end.exists()) or (status in ('proposed' | 'cancelled' | 'waitlist'))
Cancellation reason is only used for appointments that have been cancelled, or noshow
cancellationReason.exists() implies (status='noshow' or status='cancelled')
The start must be less than or equal to the end
For a recurring series of appointments, the originating appointment should have the recurrenceTemplate defining the details of the overall recurrence. Each occurence should refer back to the originatingAppointment as the single source of truth for the details of the recurrence.
An appointment may have an originatingAppointment or recurrenceTemplate, but not both
originatingAppointment.exists().not() or recurrenceTemplate.exists().not()
Cancellation date is only used for appointments that have been cancelled, or noshow
cancellationDate.exists() implies (status='noshow' or status='cancelled')
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Entity, Role, or Act,Act[@moodCode <= 'INT']
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.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
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 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.
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.
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.
Must have either extensions or value[x], not both
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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
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).
proposed | pending | booked | arrived | fulfilled | cancelled | noshow | entered-in-error | checked-in | waitlist
预约登记状态，包括：建议 |待定 |已预订 |到达 |履行 |已取消 |爽约 |输入错误 |已报到 |进入候补名单
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.
This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
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.
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.
A broad categorization of the service that is to be performed during this appointment.
n/a, might be inferred from the ServiceDeliveryLocation
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.
The specialty of a practitioner that would be required to perform the service requested in this appointment
描述提供预约的方式，如：定期|步入|常规体检|复诊|急诊
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 Reason for the appointment to take place.
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.
Indicates the urgency of the appointment.
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.
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).
.inboundRelationship[@typeCode = 'SPRT'].observation
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.
Additional information to support the appointment
Additional information to support the appointment provided when making the appointment.
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.
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.
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.
Date/Time that the appointment is to conclude.
SCH-11.5 / TQ1-8/ calculated based on the start and the duration which is in ARQ-9
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.
.activityTime[@xsi:type = ('SXPR_TS', 'PIVL_TS')].width
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.
.activityTime[@xsi:type = ('SXPR_TS', 'PIVL_TS')]
The slots that this appointment is filling
The slots from the participants' schedules that will be filled by the appointment.
.outboundRelationship[@typeCode = 'REFR'].act[@classCode = 'ACT'][@moodCode = 'SLOT']
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.
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.
The date/time describing when the appointment was cancelled.
If the appointment was cancelled multiple times, this would reflect the most recent cancellation.
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.
.subjectOf.observation[@moodCode = 'EVN'][code = 'annotation'].value
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).
The request this appointment is allocated to assess
The request this appointment is allocated to assess (e.g. incoming referral or procedure request).
.outboundRelationship[@typeCode = 'FLFS'].act[@classCode < 'ActCareProvisionRequestType'][@moodCode = 'RQO']
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.
预约的参与者可以包括患者、医生、位置、科室、设备等
Either the type or actor on the participant SHALL be specified
performer | reusableDevice | subject | location
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
May be used to represent additional information that is not part of the basic definition of the element. 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.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The role of the participant can be used to declare what the actor will be doing in the scope of this appointment. If the actor is not specified, then it is expected that the actor will be filled in at a later stage of planning. This value SHALL be the same when creating an AppointmentResponse so that they can be matched, and subsequently update the Appointment.
(performer | reusableDevice | subject | location).@typeCode
The individual, device, location, or service participating in the appointment
Where a CareTeam is provided, this does not imply that the entire team is included, just a single member from the group with the appropriate role. Where multiple members are required, please include the CareTeam the required number of times.
PID-3-Patient ID List | AIL-3 | AIG-3 | AIP-3
performer.person | reusableDevice.manufacturedDevice | subject.patient | location.serviceDeliveryLocation
ATTENDEE: (Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
Whether this participant is required to be present at the meeting. If false, the participant is optional.
For the use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present include the patient in the subject field, but do not include them as a participant - this was formerly done prior to R5 with required='information-only'.
(performer | reusableDevice | subject | location).@performInd
accepted | declined | tentative | needs-action
The Participation status of an appointment.
(performer | reusableDevice | subject | location).statusCode
ATTENDEE;CN="John Doe";RSVP=TRUE:mailto:john@doe.com (rsvpparam | partstatparam)
The sequence number that identifies a specific appointment in a recurring pattern.
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.
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.
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.
Specific dates for a recurring set of appointments (no template)
The list of specific dates that will have appointments generated.
Information about weekly recurring appointments
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.
Information about monthly recurring appointments
Indicates that appointments in the series of recurring appointments should occur on a specific day of the month.
Indicates which week of the month the appointment should occur
Indicates which week within a month the appointments in the series of recurring appointments should occur on.
Indicates which day of the week the appointment should occur
Indicates which day of the week the recurring appointments should occur each nth week.
This property is intended to be used with Appointment.recurrenceTemplate.monthly.nthWeek.
Indicates that recurring appointments should occur every nth month.
Information about yearly recurring appointments
Any dates that should be excluded from the series
Any dates, such as holidays, that should be excluded from the recurrence.
excludingDate is an alternative to excludingRecurrenceId. You may say either that 12/25/XXXX should be excluded using excludingDate, or you may indicate the recurrenceId of the appointment that would fall on the excluded date in the excludingRecurrenceId property.
Any recurrence IDs that should be excluded from the recurrence
excludingRecurrenceId is an alternative to excludingDate. You may say either that 12/25/XXXX should be excluded using excludingDate, or you may indicate the recurrenceId of the appointment that would fall on the excluded date in the excludingRecurrenceId property.