- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
StructureDefinition UKCore-Slot
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-Slot | active | 1.3.0 | 2023-12-12 | This profile defines the UK constraints and extensions on the International FHIR resource Slot. |
Profile_Purpose |
---|
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. Slots can also be marked as busy without having appointments associated. |
Detailed Descriptions
Slot | |
Definition | A slot of time on a schedule that may be available for booking appointments. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Slot.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Slot.meta | |
Definition | 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Slot.implicitRules | |
Definition | 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
Slot.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Mappings |
|
Slot.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have 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. |
Invariants |
|
Mappings |
|
Slot.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Slot.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Slot.extension:deliveryChannel | |
Definition | An extension to record the delivery channel of a scheduled Appointment. |
Cardinality | 0...1 |
Type | Extension(CodeableConcept) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
Slot.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Slot.identifier | |
Definition | External Ids for this item. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Slot.serviceCategory | |
Definition | A broad categorization of the service that is to be performed during this appointment. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | ServiceCategory (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Slot.serviceType | |
Definition | The type of appointments that can be booked into this slot (ideally this would be an identifiable service - which is at a location, rather than the location itself). If provided then this overrides the value provided on the availability resource. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | ServiceType (example) |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Slot.specialty | |
Definition | The specialty of a practitioner that would be required to perform the service requested in this appointment. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Additional details about where the content was created (e.g. clinical specialty). |
Must Support | True |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Slot.appointmentType | |
Definition | The style of appointment or patient that may be booked in the slot (not service type). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | v2.0276 (preferred) |
Must Support | True |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
Slot.schedule | |
Definition | The schedule resource that this slot defines an interval of status information. |
Cardinality | 1...1 |
Type | Reference(Schedule) |
Must Support | True |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Slot.status | |
Definition | busy | free | busy-unavailable | busy-tentative | entered-in-error. |
Cardinality | 1...1 |
Type | code |
Binding | The free/busy status of the slot. |
Must Support | True |
Summary | True |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Slot.start | |
Definition | Date/Time that the slot is to begin. |
Cardinality | 1...1 |
Type | instant |
Must Support | True |
Summary | True |
Comments | Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required |
Invariants |
|
Mappings |
|
Slot.end | |
Definition | Date/Time that the slot is to conclude. |
Cardinality | 1...1 |
Type | instant |
Must Support | True |
Summary | True |
Comments | Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required |
Invariants |
|
Mappings |
|
Slot.overbooked | |
Definition | This slot has already been overbooked, appointments are unlikely to be accepted for this time. |
Cardinality | 0...1 |
Type | boolean |
Invariants |
|
Mappings |
|
Slot.comment | |
Definition | Comments on the slot to describe any extended information. Such as custom constraints on the slot. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Table View
Slot | .. | |
Slot.extension | Extension | ..1 |
Slot.specialty | .. | |
Slot.appointmentType | .. | |
Slot.schedule | .. | |
Slot.status | .. | |
Slot.start | .. | |
Slot.end | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-Slot" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-Slot" /> <version value="1.3.0" /> <name value="UKCoreSlot" /> <title value="UK Core Slot" /> <status value="active" /> <date value="2023-12-12" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [Slot](https://hl7.org/fhir/R4/Slot.html)." /> <purpose value="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.\nSlots can also be marked as busy without having appointments associated." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Slot" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Slot" /> <derivation value="constraint" /> <differential> <element id="Slot.extension:deliveryChannel"> <path value="Slot.extension" /> <sliceName value="deliveryChannel" /> <short value="This describes the delivery channel of a scheduled appointment." /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-DeliveryChannel" /> </type> <isModifier value="false" /> </element> <element id="Slot.specialty"> <path value="Slot.specialty" /> <short value="The specialty of a practitioner that would be required to perform the service requested in this appointment." /> <mustSupport value="true" /> <binding> <strength value="extensible" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-PracticeSettingCode" /> </binding> </element> <element id="Slot.appointmentType"> <path value="Slot.appointmentType" /> <short value="The style of appointment or patient that may be booked in the slot." /> <mustSupport value="true" /> </element> <element id="Slot.schedule"> <path value="Slot.schedule" /> <short value="A reference to the Schedule that this Slot is an interval of." /> <mustSupport value="true" /> </element> <element id="Slot.status"> <path value="Slot.status" /> <short value="The status of the slot, e.g free, busy, etc." /> <mustSupport value="true" /> </element> <element id="Slot.start"> <path value="Slot.start" /> <short value="Date/Time that the slot is to begin." /> <mustSupport value="true" /> </element> <element id="Slot.end"> <path value="Slot.end" /> <short value="Date/Time that the slot is to conclude." /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-Slot", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-Slot", "version": "1.3.0", "name": "UKCoreSlot", "title": "UK Core Slot", "status": "active", "date": "2023-12-12", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [Slot](https://hl7.org/fhir/R4/Slot.html).", "purpose": "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.\nSlots can also be marked as busy without having appointments associated.", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Slot", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Slot", "derivation": "constraint", "differential": { "element": [ { "id": "Slot.extension:deliveryChannel", "path": "Slot.extension", "sliceName": "deliveryChannel", "short": "This describes the delivery channel of a scheduled appointment.", "max": "1", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-DeliveryChannel" ] } ], "isModifier": false }, { "id": "Slot.specialty", "path": "Slot.specialty", "short": "The specialty of a practitioner that would be required to perform the service requested in this appointment.", "mustSupport": true, "binding": { "strength": "extensible", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-PracticeSettingCode" } }, { "id": "Slot.appointmentType", "path": "Slot.appointmentType", "short": "The style of appointment or patient that may be booked in the slot.", "mustSupport": true }, { "id": "Slot.schedule", "path": "Slot.schedule", "short": "A reference to the Schedule that this Slot is an interval of.", "mustSupport": true }, { "id": "Slot.status", "path": "Slot.status", "short": "The status of the slot, e.g free, busy, etc.", "mustSupport": true }, { "id": "Slot.start", "path": "Slot.start", "short": "Date/Time that the slot is to begin.", "mustSupport": true }, { "id": "Slot.end", "path": "Slot.end", "short": "Date/Time that the slot is to conclude.", "mustSupport": true } ] } }
Feedback
Click here to:Report issue for UKCore-Slot, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Available Walk In Visit - An example to illustrate a slot regarding a walk in visit.Example UKCore-Slot-AvailableWalkInVisit
Example Usage Scenarios
The following are example usage scenarios for the UK Core Slot profile:
- Query for slot information from a given schedule
- Exchange slot information within a FHIR document or message.
Profile Specific Implementation Guidance:
Mandatory and Must Support Data Elements
The following elements are identified as MustSupport, and it is expected that consumers and suppliers SHALL support these as per the MustSupport Guidance.
Element | Reason |
---|---|
Slot.specialty | The specialty of a practitioner that would be required to perform the service requested in this appointment. |
Slot.appointmentType | The style of appointment or patient that may be booked in the slot. |
Slot.schedule | A reference to the Schedule that this Slot is an interval of. |
Slot.status | The status of the slot, e.g free, busy, etc. |
Slot.start | Date/Time that the slot is to begin. |
Slot.end | Date/Time that the slot is to conclude. |
Extensions
More information about the extensions on the UKCore-Slot
profile can be found using the links below.
Extension | Context | Link | Comment |
---|---|---|---|
deliveryChannel | Slot.extension | https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-DeliveryChannel | This describes the delivery channel of a scheduled appointment. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
Slot.specialty | extensible | https://fhir.hl7.org.uk/ValueSet/UKCore-PracticeSettingCode |
Slot.extension:deliveryChannel | extensible | ValueSet UKCore-DeliveryChannel |
schedule
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Schedule.