Interweave Implementation Guide
0.1.0 - ci-build
Interweave Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the R4 profiles here.
Draft as of 2018-09-27 |
Definitions for the CareConnect-Slot-1 resource profile.
Guidance on how to interpret the contents of this table can be found here.
1. Slot | |
2. Slot.extension | |
Slicing | This element introduces a set of slices on Slot.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
3. Slot.extension:deliveryChannel | |
SliceName | deliveryChannel |
Definition | An extension to record the delivery channel of a scheduled Appointment. |
Control | 0..1 |
Type | Extension(Extension-CareConnect-DeliveryChannel-1) (Extension Type: code) |
4. Slot.identifier | |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 10..1* |
Guidance on how to interpret the contents of this table can be found here.
1. Slot | |
Definition | A slot of time on a schedule that may be available for booking appointments. |
Control | 0..* |
Invariants | Defined on this element dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty()) dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty()) dom-4: 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()) |
2. 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. |
Control | 0..1 |
Type | uri |
Is 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
3. Slot.extension | |
Definition | An Extension May be used to represent additional information that is not part of the basic definition of the resource. In order 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. |
Control | 0..* |
Type | Extension |
Alternate Names | 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 | This element introduces a set of slices on Slot.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
4. Slot.extension:deliveryChannel | |
SliceName | deliveryChannel |
Definition | An extension to record the delivery channel of a scheduled Appointment. |
Control | 0..1 This element is affected by the following invariants: ele-1 |
Type | Extension(Extension-CareConnect-DeliveryChannel-1) (Extension Type: code) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
5. 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. Usually modifier elements provide negation or qualification. In order 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | 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. |
6. Slot.identifier | |
Definition | External Ids for this item. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 10..1* |
Type | Identifier |
Summary | true |
7. Slot.schedule | |
Definition | The schedule resource that this slot defines an interval of status information. |
Control | 1..1 |
Type | Reference(Schedule) |
Summary | true |
8. Slot.status | |
Definition | busy | free | busy-unavailable | busy-tentative | entered-in-error. |
Control | 1..1 |
Binding | The codes SHALL be taken from SlotStatus The free/busy status of the slot. |
Type | code |
Summary | true |
9. Slot.start | |
Definition | Date/Time that the slot is to begin. |
Control | 1..1 |
Type | instant |
Summary | true |
10. Slot.end | |
Definition | Date/Time that the slot is to conclude. |
Control | 1..1 |
Type | instant |
Summary | true |
Guidance on how to interpret the contents of this table can be found here.
1. Slot | |||||
Definition | A slot of time on a schedule that may be available for booking appointments. | ||||
Control | 0..* | ||||
2. Slot.id | |||||
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||||
Control | 0..1 | ||||
Type | id | ||||
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. | ||||
3. Slot.meta | |||||
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. | ||||
Control | 0..1 | ||||
Type | Meta | ||||
Summary | true | ||||
4. 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. | ||||
Control | 0..1 | ||||
Type | uri | ||||
Is 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. | ||||
5. Slot.language | |||||
Definition | The base language in which the resource is written. | ||||
Control | 0..1 | ||||
Binding | The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
A human language
| ||||
Type | code | ||||
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). | ||||
6. Slot.text | |||||
Definition | A human-readable narrative that contains a summary of the resource, and may 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. | ||||
Control | 0..1 This element is affected by the following invariants: dom-1 | ||||
Type | Narrative | ||||
Alternate Names | 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 in formation is added later. | ||||
7. 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. | ||||
Control | 0..* | ||||
Type | Resource | ||||
Alternate Names | 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. | ||||
8. Slot.extension | |||||
Definition | An Extension | ||||
Control | 0..* | ||||
Type | Extension | ||||
Slicing | This element introduces a set of slices on Slot.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
| ||||
9. Slot.extension:deliveryChannel | |||||
SliceName | deliveryChannel | ||||
Definition | An extension to record the delivery channel of a scheduled Appointment. | ||||
Control | 0..1 This element is affected by the following invariants: ele-1 | ||||
Type | Extension(Extension-CareConnect-DeliveryChannel-1) (Extension Type: code) | ||||
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) | ||||
10. 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. Usually modifier elements provide negation or qualification. In order 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. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true | ||||
Alternate Names | 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. | ||||
11. Slot.identifier | |||||
Definition | External Ids for this item. | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 1..1 | ||||
Type | Identifier | ||||
Summary | true | ||||
12. Slot.serviceCategory | |||||
Definition | A broad categorisation of the service that is to be performed during this appointment. | ||||
Control | 0..1 | ||||
Binding | For example codes, see ServiceCategory | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
13. 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. | ||||
Control | 0..* | ||||
Binding | For example codes, see ServiceType | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
14. Slot.specialty | |||||
Definition | The specialty of a practitioner that would be required to perform the service requested in this appointment. | ||||
Control | 0..* | ||||
Binding | The codes SHOULD be taken from Practice Setting Code Value Set Additional details about where the content was created (e.g. clinical specialty) | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
15. Slot.appointmentType | |||||
Definition | The style of appointment or patient that may be booked in the slot (not service type). | ||||
Control | 0..1 | ||||
Binding | The codes SHOULD be taken from v2 Appointment reason codes | ||||
Type | CodeableConcept | ||||
Summary | true | ||||
16. Slot.schedule | |||||
Definition | The schedule resource that this slot defines an interval of status information. | ||||
Control | 1..1 | ||||
Type | Reference(Schedule) | ||||
Summary | true | ||||
17. Slot.status | |||||
Definition | busy | free | busy-unavailable | busy-tentative | entered-in-error. | ||||
Control | 1..1 | ||||
Binding | The codes SHALL be taken from SlotStatus The free/busy status of the slot | ||||
Type | code | ||||
Summary | true | ||||
18. Slot.start | |||||
Definition | Date/Time that the slot is to begin. | ||||
Control | 1..1 | ||||
Type | instant | ||||
Summary | true | ||||
19. Slot.end | |||||
Definition | Date/Time that the slot is to conclude. | ||||
Control | 1..1 | ||||
Type | instant | ||||
Summary | true | ||||
20. Slot.overbooked | |||||
Definition | This slot has already been overbooked, appointments are unlikely to be accepted for this time. | ||||
Control | 0..1 | ||||
Type | boolean | ||||
Meaning if Missing | If overbooked is missing, systems may assume that there are still appointments available | ||||
21. Slot.comment | |||||
Definition | Comments on the slot to describe any extended information. Such as custom constraints on the slot. | ||||
Control | 0..1 | ||||
Type | string |