Current Build

Переводит компания Health Samurai . Приглашаем поучаствовать в русификации стандарта FHIR: GitHub , Email.

12.12 Ресурс Schedule - Назначение

Patient Administration Work GroupMaturity Level: 3 Trial UseSecurity Category: Business Compartments: Device, Patient, Practitioner, RelatedPerson

Контейнер для слотов времени, которые могут быть доступными для бронирования.

Schedule resources provide a container for time-slots that can be booked using an appointment. It provides the window of time (period) that slots are defined for and what type of appointments can be booked.
The schedule does not provide any information about actual appointments. This separation greatly assists where access to the appointments would not be permitted for security or privacy reasons, while still being able to determine if an appointment might be available.

Note: A schedule is not used for the delivery of medication, the Timing data type should be used for that purpose.

A schedule controls the dates and times available for the performance of a service and/or the use of a resource. One schedule applies to one service or resource, since each service or resource can be reserved independently of the others.
If two or more services, people, locations, or things cannot be reserved independently of one another, they are considered to be one activity or resource.

A schedule consists of slots of time during which the controlled service or resource is potentially available for provision or use. Slots are categorized as open, booked, or blocked. An open slot on a schedule indicates that the service or resource is available for provision or use during that period of time. A booked slot indicates that the service or resource is not available during the time period, because an appointment has been scheduled. A blocked slot indicates that a service or resource is unavailable for reasons other than a scheduled appointment.

The real-world, non-automated analogue of the schedule described above is a standard appointment book. These books are generally organized with rows of time slots, during which a service or resource is available.

A slot is one unit on a schedule. A slot represents the smallest unit of time or quantity that a service or resource may be booked. Depending on the nature of the service or resource, there may be more than one defined slot at a given instant of time. For example, if a service is an open group therapy session with twelve available seats, then there are twelve slots for the given block of time.

The schedule belongs to a single instance of a service or resource. This is normally a HealthcareService, Practitioner, Location or Device. In the case where a single resource can provide different services, potentially at different location, then the schedulable resource is considered the composite of the actors.
For example, if a practitioner can provide services at multiple locations, they might have one schedule per location, where each schedule includes both the practitioner and location actors. When booking an appointment with multiple schedulable resources, multiple schedules may need to be checked depending on the configuration of the system.

If an appointment has two practitioners, a specific medical device and a room then there could be a schedule for each of these resources that may need to be consulted to ensure that no collisions occur.
If the schedule needed to be consulted, then there would be one created covering the planning horizon for the time of the appointment.

When checking availability for an appointment, the creator of the appointment should determine which schedules are applicable, then check for available slots within each schedule.

Determining which schedules should be consulted often will involve searching via the properties of the referenced actors, such as the ServiceCategory on the HealthcareService, or the Address on a Location.

The type parameter can be used to filter the type of services that can be booked within the associated slots.

If all slots are busy, the caller may attempt to book an appointment into an already-booked slot, but the server business rules will dictate whether overbooking is allowed, or whether the appointment may be given a higher precedence and allocated the overbooked slot.

На этот ресурс ссылаются TriggerDefinition и Slot

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. Schedule TUDomainResourceКонтейнер для слотов времени, которые могут быть доступными для бронирования
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierВнешние идентификаторы для этого объекта
... active ?!Σ0..1booleanWhether this schedule is in active use
... serviceCategory Σ0..*CodeableConceptHigh-level category
Service category (Example)
... serviceType Σ0..*CodeableConceptSpecific service
Service type (Example)
... specialty Σ0..*CodeableConceptType of specialty needed
Practice Setting Code Value Set (Preferred)
... actor Σ1..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)E.g. HealthCareService, Location, Practitioner, etc.
... planningHorizon Σ0..1PeriodPeriod of time covered by schedule
... comment 0..1stringComments on availability

doco Документация по этому формату

UML-диаграмма (Legend)

Schedule (DomainResource)Внешние идентификаторы для этого объектаidentifier : Identifier [0..*]Whether this schedule record is in active use or should not be used (such as was entered in error) (this element modifies the meaning of other elements)active : boolean [0..1]A broad categorization of the service that is to be performed during this appointmentserviceCategory : CodeableConcept [0..*] « (Strength=Example)ServiceCategory?? »The specific service that is to be performed during this appointmentserviceType : CodeableConcept [0..*] « (Strength=Example)ServiceType?? »The specialty of a practitioner that would be required to perform the service requested in this appointmentspecialty : CodeableConcept [0..*] « Дополнительные сведения о том, где было создано это содержимое (например клиническая специальность). (Strength=Preferred)PracticeSettingCodeValueSet? »Ресурс, информацию о доступности которого предоставляет данный ресурс Schedule. Ожидается, что это будет, как правило, один из ресурсов HealthcareService, Location, Practitioner, Device, Patient или RelatedPersonactor : Reference [1..*] « Patient|Practitioner|PractitionerRole| RelatedPerson|Device|HealthcareService|Location »Период времени, который охватывают слоты, приложенные к данному ресурсу Schedule (даже если нет ни одного). Он охватывает количество времени, являющееся горизонтом планирования организации; интервал, для которого они сейчас выполняют запись на прием. Это не задает шаблон планирования вне указанных здесь датplanningHorizon : Period [0..1]Примечания к доступности, содержащие любую расширенную информацию. Например пользовательские ограничения на слоты, которые могут быть привязаныcomment : string [0..1]

Turtle-шаблон

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Schedule;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Schedule.identifier [ Identifier ], ... ; # 0..* Внешние идентификаторы для этого объекта
  fhir:Schedule.active [ boolean ]; # 0..1 Whether this schedule is in active use
  fhir:Schedule.serviceCategory [ CodeableConcept ], ... ; # 0..* High-level category
  fhir:Schedule.serviceType [ CodeableConcept ], ... ; # 0..* Specific service
  fhir:Schedule.specialty [ CodeableConcept ], ... ; # 0..* Type of specialty needed
  fhir:Schedule.actor [ Reference(Patient|Practitioner|PractitionerRole|RelatedPerson|Device|HealthcareService|
  Location) ], ... ; # 1..* E.g. HealthCareService, Location, Practitioner, etc.
  fhir:Schedule.planningHorizon [ Period ]; # 0..1 Period of time covered by schedule
  fhir:Schedule.comment [ string ]; # 0..1 Comments on availability
]

Changes since R3

Schedule
Schedule.active
  • Default Value "true" removed
Schedule.serviceCategory
  • Max Cardinality changed from 1 to *

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 3 tests of which 3 fail to execute.)

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. Schedule TUDomainResourceКонтейнер для слотов времени, которые могут быть доступными для бронирования
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierВнешние идентификаторы для этого объекта
... active ?!Σ0..1booleanWhether this schedule is in active use
... serviceCategory Σ0..*CodeableConceptHigh-level category
Service category (Example)
... serviceType Σ0..*CodeableConceptSpecific service
Service type (Example)
... specialty Σ0..*CodeableConceptType of specialty needed
Practice Setting Code Value Set (Preferred)
... actor Σ1..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)E.g. HealthCareService, Location, Practitioner, etc.
... planningHorizon Σ0..1PeriodPeriod of time covered by schedule
... comment 0..1stringComments on availability

doco Документация по этому формату

UML-диаграмма (Legend)

Schedule (DomainResource)Внешние идентификаторы для этого объектаidentifier : Identifier [0..*]Whether this schedule record is in active use or should not be used (such as was entered in error) (this element modifies the meaning of other elements)active : boolean [0..1]A broad categorization of the service that is to be performed during this appointmentserviceCategory : CodeableConcept [0..*] « (Strength=Example)ServiceCategory?? »The specific service that is to be performed during this appointmentserviceType : CodeableConcept [0..*] « (Strength=Example)ServiceType?? »The specialty of a practitioner that would be required to perform the service requested in this appointmentspecialty : CodeableConcept [0..*] « Дополнительные сведения о том, где было создано это содержимое (например клиническая специальность). (Strength=Preferred)PracticeSettingCodeValueSet? »Ресурс, информацию о доступности которого предоставляет данный ресурс Schedule. Ожидается, что это будет, как правило, один из ресурсов HealthcareService, Location, Practitioner, Device, Patient или RelatedPersonactor : Reference [1..*] « Patient|Practitioner|PractitionerRole| RelatedPerson|Device|HealthcareService|Location »Период времени, который охватывают слоты, приложенные к данному ресурсу Schedule (даже если нет ни одного). Он охватывает количество времени, являющееся горизонтом планирования организации; интервал, для которого они сейчас выполняют запись на прием. Это не задает шаблон планирования вне указанных здесь датplanningHorizon : Period [0..1]Примечания к доступности, содержащие любую расширенную информацию. Например пользовательские ограничения на слоты, которые могут быть привязаныcomment : string [0..1]

Turtle-шаблон

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Schedule;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Schedule.identifier [ Identifier ], ... ; # 0..* Внешние идентификаторы для этого объекта
  fhir:Schedule.active [ boolean ]; # 0..1 Whether this schedule is in active use
  fhir:Schedule.serviceCategory [ CodeableConcept ], ... ; # 0..* High-level category
  fhir:Schedule.serviceType [ CodeableConcept ], ... ; # 0..* Specific service
  fhir:Schedule.specialty [ CodeableConcept ], ... ; # 0..* Type of specialty needed
  fhir:Schedule.actor [ Reference(Patient|Practitioner|PractitionerRole|RelatedPerson|Device|HealthcareService|
  Location) ], ... ; # 1..* E.g. HealthCareService, Location, Practitioner, etc.
  fhir:Schedule.planningHorizon [ Period ]; # 0..1 Period of time covered by schedule
  fhir:Schedule.comment [ string ]; # 0..1 Comments on availability
]

Changes since Release 3

Schedule
Schedule.active
  • Default Value "true" removed
Schedule.serviceCategory
  • Max Cardinality changed from 1 to *

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 3 tests of which 3 fail to execute.)

 

See the Profiles & Extensions and the Альтернативные определения: Основное определение XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the Анализ зависимостей

PathОписаниеТипСсылка
Schedule.serviceCategory ExampleServiceCategory
Schedule.serviceType ExampleServiceType
Schedule.specialty Дополнительные сведения о том, где было создано это содержимое (например клиническая специальность).PreferredPracticeSettingCodeValueSet

There is a strong desire that implementers of this resource should consider providing the resource in the iCalendar format as an alternative representation. Many 3rd party applications and component providers have parsers and user interface controls to display this information. This may lower the entry point to integrate outside the health-care specific applications, and into the consumer space. This would permit the easier creation of a mobile application that creates appointments in the devices native calendar.
The iCalendar specification can be found at http://www.ietf.org/rfc/rfc2445.txt .

Due to the dynamic nature of slots they are not included as a part of this resource.

It is anticipated that this resource is likely to be updated intermittently when the scope of slots is changed, i.e. to change the period of slots in the planning horizon. This could be performed each night to move the start and end date forward to keep the planning horizon as exactly 4 weeks.

The slot resource however is anticipated to be updated very regularly as the appointments that reference them are created/updated/cancelled.

Параметры поиска для этого ресурса. Также к нему применяются общие параметры. Более подробную информацию о поиске в REST, обмене сообщениями и сервисах см. в разделе Поиск.

ИмяТипОпределениеВыражениеIn Common
activetokenIs the schedule in active useSchedule.active
actorreferenceРесурс (HealthcareService, Practitioner, Location, ...), для которого необходимо найти расписаниеSchedule.actor
(Practitioner, Device, Patient, HealthcareService, PractitionerRole, RelatedPerson, Location)
datedateПоиск ресурсов Schedule, период которых содержит указанную датуSchedule.planningHorizon
identifiertokenИдентификатор расписанияSchedule.identifier
service-categorytokenHigh-level categorySchedule.serviceCategory
service-typetokenТип условленных встреч, которые можно зарезервировать в связанных слотахSchedule.serviceType
specialtytokenType of specialty neededSchedule.specialty