SlotLiteSe
Introduction
SlotLiteSe is a profile based on the FHIR resource Slot.
Intended Use
SlotLiteSe may be used for getting slots that can be used for booking an appointment.
Specific Rules and Limitations
Type | Description |
---|---|
Rule | The patient header 'Patient' must be included. |
Rule | The start and end date range should never exceed one full day |
Profile Overview
SlotLiteSe (Slot) | I | SlotCoreSe | There are no (further) constraints on this element Element idSlot A slot of time on a schedule that may be available for booking appointments DefinitionA slot of time on a schedule that may be available for booking appointments.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSlot.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSlot.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSlot.implicitRules A set of rules under which this content was created DefinitionA 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 it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSlot.language Language of the resource content DefinitionThe 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSlot.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 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 | 0..* | Resource | There are no (further) constraints on this element Element idSlot.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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 | I | 0..* | Extension | There are no (further) constraints on this element Element idSlot.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
permittedPatientActions | I | 0..* | Extension(Coding) | There are no (further) constraints on this element Element idSlot.extension:permittedPatientActions Use to describe what a patient is permitted to do Alternate namesextensions, user content DefinitionUse to describe what a patient is permitted to do in the area of booking, rebooking and cancellations. 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. http://cambio.se/fhir/StructureDefinition/common-permittedPatientActions/v1 Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSlot.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idSlot.identifier External Ids for this item DefinitionExternal Ids for this item.
|
serviceCategory | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idSlot.serviceCategory A broad categorization of the service that is to be performed during this appointment DefinitionA broad categorization of the service that is to be performed during this appointment. 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.
|
serviceType | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idSlot.serviceType 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 DefinitionThe 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. 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.
|
specialty | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idSlot.specialty The specialty of a practitioner that would be required to perform the service requested in this appointment DefinitionThe specialty of a practitioner that would be required to perform the service requested in this appointment. 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. Additional details about where the content was created (e.g. clinical specialty).
|
appointmentType | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idSlot.appointmentType The style of appointment or patient that may be booked in the slot (not service type) DefinitionThe style of appointment or patient that may be booked in the slot (not service type). 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.
|
schedule | Σ I | 1..1 | Reference(Schedule) | Element idSlot.schedule The schedule resource that this slot defines an interval of status information DefinitionThe schedule resource that this slot defines an interval of status information. 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. Allowed aggregation: contained Constraints
|
status | Σ | 1..1 | codeBindingFixed Value | Element idSlot.status busy | free | busy-unavailable | busy-tentative | entered-in-error Definitionbusy | free | busy-unavailable | busy-tentative | entered-in-error. Note that FHIR strings SHALL NOT exceed 1MB in size The free/busy status of the slot.
free
|
start | Σ | 1..1 | instant | There are no (further) constraints on this element Element idSlot.start Date/Time that the slot is to begin DefinitionDate/Time that the slot is to begin. 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
|
end | Σ | 1..1 | instant | There are no (further) constraints on this element Element idSlot.end Date/Time that the slot is to conclude DefinitionDate/Time that the slot is to conclude. 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
|
overbooked | 0..0 | boolean | There are no (further) constraints on this element Element idSlot.overbooked This slot has already been overbooked, appointments are unlikely to be accepted for this time DefinitionThis slot has already been overbooked, appointments are unlikely to be accepted for this time. If overbooked is missing, systems may assume that there are still appointments available
| |
comment | 0..0 | string | There are no (further) constraints on this element Element idSlot.comment Comments on the slot to describe any extended information. Such as custom constraints on the slot DefinitionComments on the slot to describe any extended information. Such as custom constraints on the slot. Note that FHIR strings SHALL NOT exceed 1MB in size
|
Versions
COS version | Profile version | Required COSMIC version | Date | Description |
---|---|---|---|---|
3.0.0 | 1.0.0 | R8.3.05 | May 2022 | Initial version, support for search. |
Extensions
Extension | Data type | Description |
---|---|---|
PermittedPatientActions | Coding | Describes what actions the patient have permission for. Never mapped on HealthcareServiceLiteSe. Only available on Appointment. |
Supported Operations
HTTP Methods
Method | Description |
---|---|
GET | Used to search for slots based on a search parameter. |
Query Operations
Search Parameters
Parameter | Format | Mandatory | Comment |
---|---|---|---|
start | date | Yes | Is used to define start and end of the date range to be searched for. Can be passed multiple times, use operators gt(greater than) and lt(less than) to define the range. Both gt and lt operators must be used, see query example. |
healthcareFacility | HSA ID | Yes | |
healthcareService | Internal Id | Yes | |
_profile | URL | No | |
appointmentId | Internal Id | No |
HealthcareFacility, HealthcareService and AppointmentID cannot be found in profile.
Supported Queries
GET [baseURL]/Slot/_search?start=gt<start date>&start=lt<end date>&healthcareFacility=<healthcare unit Id>&healthcareService=<Healthcare Service Id>&appointmentId=<appointment Id>
Supported SearchInclude Operations
IncludeParam = "Slot:schedule", Slot:schedule.practitioner”
Supported RevInclude Operations
N/A
Error Codes
No specific error codes for Slot. For common codes, refer to Error handling section.