- FHIR Slot Resource
- Electronic Health Records Exchange Through FHIR
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
A slot of time on a schedule that may be available for booking appointments. Slot resources are used to provide time-slots that can be booked using an appointment. They do not provide any information about appointments that are available, just the time, and optionally what the time can be used for. These are effectively spaces of free/busy time.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
Slots can also be marked as busy without having appointments associated. A slot can have more than one appointment allocated to it. A scheduling system may permit multiple allocations up to a specific number of places. An example of this type of usage could be where the slot is being used for a group service that permits 5 participants at the same time.
A slot can be marked as over-booked indicating that there are too many appointments allocated to it. In some situations a service may have a specific set of slots reserved for specific uses, such as “walk-ins” or a specific organization has a “standing booking” for Thursday mornings. These should be represented using the appointment type field with a specified and agreed value.
Security Permissions or specific business rules on the system could enforce that only eligible appointments are allocated to them.
If a service had a weekly schedule created that permitted eight 1 hour appointments each day of a working week (Monday – Friday), this would be constructed by a single Schedule resource with the dates for the start and end of the week set, and then 40 (5×8) Slot resources associated with it. As appointments fill up the schedule, these slots would individually be marked as busy as the appointments are filled into the slots. The slots in a schedule do not need to be the same size, and can be different for different days of the week.
Slot instances do not have any recurrence information included. If recurring information is desired, this will be managed outside these resources, or included as extensions.
Note that booking an appointment does not necessarily require that slot resources be identified. When attempting to book an appointment, if the requestor knows ahead of time which schedulable resources are required, then identifying individual slots from the resources’ schedules prior to creating the appointment is appropriate. However, in some medical scheduling scenarios, determining which resources are required for an appointment is very complex, and options other than using schedule+slot may be a better solution.
About this Dataset
John Snow Labs; Health Level Seven International;
|Source License URL|
|Source License Requirements||
FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR
FHIR Slot Resource, Electronic Health Records Exchange Through FHIR
|Concept_Name||Name of the concept in the FHIR structure||string||required : 1|
|Computer_Ready_Name||A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.||string||-|
|Type||The type the structure describes.||string||-|
|Dollar_Ref||The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.||string||-|
|Description||A free text natural language description of the structure and its use||string||-|
|Items||The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.||string||-|
|Enum||The value of the keyword should be an array of unique strings. The data object tobe valid should contain all properties with names equal to the elements in the keyword value.||string||-|
|Required||The value of the keyword should be an array of unique strings. The data object tobe valid should contain all properties with names equal to the elements in the keyword value.||string||-|
|Const||The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.||string||-|
|Concept Name||Computer Ready Name||Type||Dollar Ref||Description||Items||Enum||Required||Const|
|Slot||resourceType||This is a Slot resource||Slot|
|Slot||id||#/definitions/id||The logical id of the resource|
|Slot||meta||#/definitions/Meta||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.|
|Slot||implicitRules||#/definitions/uri||A reference to a set of rules that were followed when the resource was constructed|
|Slot||_implicitRules||#/definitions/Element||Extensions for implicitRules|
|Slot||language||#/definitions/code||The base language in which the resource is written.|
|Slot||_language||#/definitions/Element||Extensions for language|
|Slot||text||#/definitions/Narrative||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|
|Slot||contained||array||These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently|
|Slot||extension||array||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|