Jede Instanz eines bestätigungsrelevanten Systems MUSS an ihrem Endpunkt eine [CapabilityStatement]https://hl7.org/fhir/R4/capabilitystatement.html)-Ressource bereitstellen.
+
Hierzu MUSS die [capabilities-Interaktion gemäß FHIR-Spezifikation]https://hl7.org/fhir/R4/http.html#capabilities) unterstützt werden.
+Der "MODE"-Parameter kann ignoriert werden.
+
Das CapabilityStatement in dieser Spezifikation stellt die Anforderungen seitens der gematik dar (kind = "requirements"). Zur Unterscheidung von Anforderungen, die erfüllt werden MÜSSEN, gegenüber jenen, die erfüllt werden KÖNNEN, wird die CapabilityStatement-Expectation-Extension mit den möglichen Werten "SHALL" (=MUSS) und "MAY" (=KANN) verwendet.
+
Eine Server-Instanz MUSS ihrerseits ein CapabilityStatement vom kind= "instance" liefern und im Element software den Namen und die Versionsnummer angeben.
+
Das CapabilityStatement der Instanz MUSS alle Funktionalitäten auflisten, die im folgenden CapabilityStatement mit "SHALL" gekennzeichnet sind. Das CapabilityStatement KANN darüber hinaus die mit "MAY" gekennzeichneten Funktionalitäten, sowie weitere Funktionalitäten auflisten, sofern diese in der Instanz implementiert wurden.
+
Die Verwendung der CapabilityStatement-Expectation-Extension ist im CapabilityStatement der Server-Instanz nicht erforderlich.
Die Bereitstellung des CapabilityStatements für das Modul "Terminplanung" erfolgt zusammen mit der Festlegung der bestätigungsrelevanten Systeme in Stufe 2
+
Für Systeme, die das Modul "Terminplanung" implementieren, ist außerdem die Erfüllung der Mindestanforderungen des Moduls "Basis" erfoderlich:
ISiKBinary dient im Kontext der Terminplanung dazu Zusatzinformationen an das Termin-Repository bzw. den Termin-Requestor zu übermitteln (vgl. 'ISiKCommunication.payload.contentAttachment').
+
+
FHIR-Profil
+
Es gelten bis auf weiteres die Vorgaben des ISiK Basismoduls für das Profil 'ISiKBinary'.
+Ein Termin Repository MUSS die Anlage (Create-Interaktion) einer Binary-Ressource entsprechend der Vorgaben des ISiK-Basismoduls unterstützen.
+Die Binary-Ressource MUSS in ihrem originalen Repräsentationsformat, sowie als FHIR-Ressource abgerufen werden können (vgl. Serving Binary Resources using the RESTful API).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-ISiKKalenderSchedule.html b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-ISiKKalenderSchedule.html
new file mode 100644
index 00000000..62441203
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-ISiKKalenderSchedule.html
@@ -0,0 +1,724 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Das Datenobjekt ISiKKalender bietet die Möglichkeit Kalender für verschiedene Akteure (Practitioner, Device, HealthcareService) zu exponieren, sodass für die Ressourcen Termine gebucht werden können.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.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()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
rim:n/a
ical:BEGIN:VFREEBUSY ??? END:VFREEBUSY (If your fhir server provides this information via calDAV, then you may want to include addressing information in a URL section, and with the search, a DTSTART and DTEND component can be included to indicate the range of time that has been covered in the collection of slots, where these overlap the resources period values. For all slots that reference this resource, include a FREEBUSY row for each slot)
There are no (further) constraints on this element
Element Id
Schedule.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
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.
+
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.
There are no (further) constraints on this element
Element Id
Schedule.extension.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. 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.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1:Must have either extensions or value[x], not both extension.exists() != value.exists()
Mappings
rim:n/a
rim:N/A
url
1..1
System.String
There are no (further) constraints on this element
Element Id
Schedule.extension.url
Short description
identifies the meaning of the extension
Definition
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Mappings
rim:N/A
value[x]
1..1
Element Id
Schedule.extension.value[x]
Short description
Value of extension
Definition
Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
+
Sliced:
Unordered, Open, by $this(Type)
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Optional Extension Element - found in all resources.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Schedule.serviceCategory
Short description
High-level category
Definition
A broad categorization of the service that is to be performed during this appointment.
+
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.
There are no (further) constraints on this element
Element Id
Schedule.serviceType
Short description
Specific service
Definition
The specific service that is to be performed during this appointment.
+
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.
The specialty of a practitioner that would be required to perform the service requested in this appointment.
+
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.
The specialty of a practitioner that would be required to perform the service requested in this appointment.
+
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.
Resource(s) that availability information is being provided for
Definition
Slots that reference this schedule resource provide the availability details to these referenced resource(s).
+
Comments
The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
ical:ATTENDEE:MAILTO:john_public@host2.com This can be populated with a value from the referenced resource
There are no (further) constraints on this element
Element Id
Schedule.actor.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Schedule.actor.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Schedule.actor.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Schedule.actor.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Resource(s) that availability information is being provided for
Definition
Slots that reference this schedule resource provide the availability details to these referenced resource(s).
+
Comments
The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
ical:ATTENDEE:MAILTO:john_public@host2.com This can be populated with a value from the referenced resource
There are no (further) constraints on this element
Element Id
Schedule.actor:Akteur.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Schedule.actor:Akteur.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Schedule.actor:Akteur.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Schedule.actor:Akteur.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Schedule.planningHorizon
Short description
Period of time covered by schedule
Definition
The period of time that the slots that reference this Schedule resource cover (even if none exist). These cover the amount of time that an organization's planning horizon; the interval for which they are currently accepting appointments. This does not define a "template" for planning outside these dates.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Hinweis: Im alltäglichen Kontext besitzen Kalender neben der Zugehörigkeit zu einer Ressource teilweise einen Namen. Dieser muss nicht zwingend ein eineindeutiger Identifier sein. Aufgrund dessen kann dieser Name zusätzlich abgebildet werden. Falls kein Name angegeben wird, kann ein Termin-Consumer einen Namen z.B. aus den Elementen "serviceType" oder "specialty" für Anzeigezwecke ableiten.
+
Schedule.active
+
Bedeutung: Ist der Kalender in aktiver Verwendung?
+
Hinweis: Historische Kalender können ebenfalls über die ISiK-Schnittstelle ausgetauscht werden. Für diese dürfen jedoch keine Termine vereinbart werden. Das terminführende System MUSS dies bei der Buchung überprüfen.
+
Schedule.serviceType
+
Bedeutung: Welche Besuchsgründe / Behandlungsleistungen werden durch diesen Kalender erfasst?
+
Hinweis: Die Besuchsgründe / Behandlungsleistungen SOLLEN im Schedule angegeben werden, falls unter Schedule.actor nur Referenzen mit Referenz.display angegeben werden oder direkt auf einen Practitioner referenziert wird. Im Falle, dass ein HealthcareService referenziert wird, SOLLEN die gleichen Informationen wie in HealthcareService.type angegeben werden. Seitens der aktuellen Spezifikation werden keine Vorgaben bezüglich der zu verwendenden Terminologie gemacht. Entsprechend verwendete Kataloge müssen als CodeSystem-Ressource exponiert werden.
+
Schedule.specialty
+
Bedeutung: Welche Fachrichtung(en) führen die Behandlungsleistungen, die durch diesen Kalender erfasst werden, aus?
+
Hinweis: Die Fachrichtung(en) SOLL(EN) im Schedule angegeben werden, falls unter Schedule.actor nur Referenzen mit Referenz.display angegeben werden oder direkt auf einen Practitioner referenziert wird. Im Falle, dass ein HealthcareService referenziert wird, SOLLEN die gleichen Informationen wie in HealthcareService.specialty angegeben werden.
+
Schedule.actor
+
Bedeutung: Für welche Akteure wird der Kalender geführt?
+
Hinweis: Nicht alle Target-Ressourcen dieser Referenz existieren als Profil innerhalb des ISiK-Basismoduls oder ISiK-Terminplanung. Für alle Target-Ressourcen SOLL ein Displaywert für die Referenz angegeben werden. Nur für HealthcareService und Practitioner MUSS Reference.reference angegeben werden.
+
+
Interaktionen
+
Für die Ressource Schedule MUSS die REST-Interaktion "READ" implementiert werden.
+
+
Der Suchparameter "_id" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Schedule?_id=103270
+
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"]https://hl7.org/fhir/R4/search.html#all).
+
+
Der Suchparameter "active" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Schedule?active=true
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Schedule.active" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "service-type" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Schedule?service-type=http://example.org/fhir/CodeSystem/ScheduleServiceType|CT
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Schedule.serviceType" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "specialty" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Schedule?specialty=urn:oid:1.2.276.0.76.5.114|535
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Schedule.specialty" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "actor" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Schedule?actor=Practitioner/ISiKPractitionerExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Schedule.actor" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference).
Unter einer medizinischen Behandlungseinheit wird innerhalb dieser Spezifikation ein (virtueller) Zusammenschluss von Fachabteilungen, darin agierenden Personen im Gesundheitswesen und zur Verfügung stehenden Ressourcen (z.B. Räume / Geräte), zum Zweck der Ausübung einer Behandlungsleistung, verstanden. Hierfür können von der Fachabteilung (Organization) unabhängige Kalender gepflegt werden.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.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()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
HealthcareService.active
Short description
Whether this HealthcareService record is in active use
Definition
This flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this.
+
Comments
This element is labeled as a modifier because it may be used to mark that the resource was created in error.
+
Meaning When Missing
This resource is generally assumed to be active if no value is provided for the active element
There are no (further) constraints on this element
Element Id
HealthcareService.providedBy
Short description
Organization that provides this service
Definition
The organization that provides this healthcare service.
+
Comments
This property is recommended to be the same as the Location's managingOrganization, and if not provided should be interpreted as such. If the Location does not have a managing Organization, then this property should be populated.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
HealthcareService.type
Short description
Type of service that may be delivered or performed
Alternate names
service type
Definition
The specific type of service that may be delivered or performed.
+
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.
Collection of specialties handled by the service site. This is more of a medical term.
+
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.
Collection of specialties handled by the service site. This is more of a medical term.
+
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.
There are no (further) constraints on this element
Element Id
HealthcareService.location
Short description
Location(s) where service may be provided
Definition
The location(s) where this healthcare service may be provided.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
HealthcareService.comment
Short description
Additional description and/or any specific issues not covered elsewhere
Definition
Any additional description of the service and/or any specific issues not covered by the other attributes, which can be displayed as further detail under the serviceName.
+
Comments
Would expect that a user would not see this information on a search results, and it would only be available when viewing the complete details of the service.
There are no (further) constraints on this element
Element Id
HealthcareService.extraDetails
Short description
Extra details about the service that can't be placed in the other fields
Definition
Extra details about the service that can't be placed in the other fields.
+
Comments
Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
There are no (further) constraints on this element
Element Id
HealthcareService.photo
Short description
Facilitates quick identification of the service
Definition
If there is a photo/symbol associated with this HealthcareService, it may be included here to facilitate quick identification of the service in a list.
+
Comments
When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
There are no (further) constraints on this element
Element Id
HealthcareService.coverageArea
Short description
Location(s) service is intended for/available to
Definition
The location(s) that this service is available to (not where the service is provided).
+
Comments
The locations referenced by the coverage area can include both specific locations, including areas, and also conceptual domains too (mode = kind), such as a physical area (tri-state area) and some other attribute (covered by Example Care Organization). These types of Locations are often not managed by any specific organization. This could also include generic locations such as "in-home".
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
HealthcareService.serviceProvisionCode
Short description
Conditions under which service is available/offered
Definition
The code(s) that detail the conditions under which the healthcare service is available/offered.
+
Comments
The provision means being commissioned by, contractually obliged or financially sourced. Types of costings that may apply to this healthcare service, such if the service may be available for free, some discounts available, or fees apply.
There are no (further) constraints on this element
Element Id
HealthcareService.eligibility.code
Short description
Coded value for the eligibility
Definition
Coded value for the eligibility.
+
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.
There are no (further) constraints on this element
Element Id
HealthcareService.eligibility.comment
Short description
Describes the eligibility conditions for the service
Definition
Describes the eligibility conditions for the service.
+
Comments
The description of service eligibility should, in general, not exceed one or two paragraphs. It should be sufficient for a prospective consumer to determine if they are likely to be eligible or not. Where eligibility requirements and conditions are complex, it may simply be noted that an eligibility assessment is required. Where eligibility is determined by an outside source, such as an Act of Parliament, this should be noted, preferably with a reference to a commonly available copy of the source document such as a web page.
There are no (further) constraints on this element
Element Id
HealthcareService.communication
Short description
The language that this service is offered in
Definition
Some services are specifically made available in multiple languages, this property permits a directory to declare the languages this is offered in. Typically this is only provided where a service operates in communities with mixed languages used.
+
Comments
When using this property it indicates that the service is available with this language, it is not derived from the practitioners, and not all are required to use this language, just that this language is available while scheduling.
There are no (further) constraints on this element
Element Id
HealthcareService.referralMethod
Short description
Ways that the service accepts referrals
Definition
Ways that the service accepts referrals, if this is not provided then it is implied that no referral is required.
+
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.
There are no (further) constraints on this element
Element Id
HealthcareService.appointmentRequired
Short description
If an appointment is required for access to this service
Definition
Indicates whether or not a prospective consumer will require an appointment for a particular service at a site to be provided by the Organization. Indicates if an appointment is required for access to this service.
There are no (further) constraints on this element
Element Id
HealthcareService.notAvailable.during
Short description
Service not available from this date
Definition
Service is not available (seasonally or for a public holiday) from this date.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
HealthcareService.availabilityExceptions
Short description
Description of availability exceptions
Definition
A description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
HealthcareService.endpoint
Short description
Technical endpoints providing access to electronic services operated for the healthcare service
Definition
Technical endpoints providing access to services operated for the specific healthcare services defined at this resource.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
Bedeutung: Ist der HealthcareService in aktiver Verwendung.
+
Hinweis: Historische HealthcareServices können ebenfalls über die ISiK-Schnittstelle ausgetauscht werden. Für diese dürfen jedoch keine Termine vereinbart werden. Das terminführende System MUSS dies bei der Buchung überprüfen.
+
HealthcareService.type
+
Bedeutung: Klassifikation der Behandlungsleistung welche durch den HealthcareService erbracht wird
+
Hinweis: Diese Klassifikation SOLL stets auch in Appointment.serviceType und Schedule.serviceType angegeben werden. Seitens der aktuellen Spezifikation werden keine Vorgaben bezüglich der zu verwendenden Terminologie gemacht. Entsprechend verwendete Kataloge müssen als CodeSystem- und ValueSet-Ressourcen exponiert werden. Siehe Suchparameter "context-type-value" in ISiK Basis - Datenobjekt ValueSet.
+
HealthcareService.specialty
+
Bedeutung: Fachrichtung der Behandlungsleistung welche durch den HealthcareService erbracht wird
+
Hinweis: Diese Fachrichtung SOLL stets auch in Appointment.specialty und Schedule.specialty angegeben werden.
+
HealthcareService.name
+
Bedeutung: Informeller Name der Behandlungseinheit
+
Hinweis: Es wird im Rahmen dieser Spezifikation davon ausgegangen, dass für einen HealthcareService keine natürlichen Identifier vorliegen, die in einem realen Kontext vergeben werden. Somit kann durch den Namen ein informeller, jedoch identifizierender Bezeichner vergeben werden.
+
+
Interaktionen
+
Für die Ressource HealthcareService MUSS die REST-Interaktion "READ" implementiert werden.
+
+
Der Suchparameter "_id" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/HealthcareService?_id=103270
+
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"]https://hl7.org/fhir/R4/search.html#all).
+
+
Der Suchparameter "active" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/HealthcareService?active=true
+
Anwendungshinweise: Weitere Informationen zur Suche nach "HealthcareService.active" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "service-type" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/HealthcareService?service-type=http://example.org/fhir/CodeSystem/ScheduleServiceType|CT
+
Anwendungshinweise: Weitere Informationen zur Suche nach "HealthcareService.type" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "specialty" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/HealthcareService?specialty=urn:oid:1.2.276.0.76.5.114|535
+
Anwendungshinweise: Weitere Informationen zur Suche nach "HealthcareService.specialty" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "name" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/HealthcareService?name=Medizinische Behandlungseinheit Des Fachbereichs 0100
Die Communication-Ressource dient als Datenobjekt für den Austausch von Nachrichten zwischen einem Leistungserbringer und einem Patienten. Es können sowohl Textnachrichten als auch Binärdateien ausgetauscht werden.
There are no (further) constraints on this element
Element Id
Communication
Short description
A record of information transmitted from a sender to a receiver
Definition
An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.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()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
There are no (further) constraints on this element
Element Id
Communication.identifier
Short description
Unique identifier
Definition
Business identifiers assigned to this communication by the performer or other systems which remain constant as the resource is updated and propagates from server to server.
+
Requirements
Allows identification of the communication as it is known by various participating systems and in a way that remains consistent across servers.
+
Comments
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Communication.instantiatesUri
Short description
Instantiates external protocol or definition
Definition
The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.
+
Comments
This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.partOf
Short description
Part of this action
Alternate names
container
Definition
Part of this action.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.inResponseTo
Short description
Reply to
Definition
Prior communication that this communication is in response to.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.
There are no (further) constraints on this element
Element Id
Communication.statusReason
Short description
Reason for current status
Alternate names
Suspended Reason, Cancelled Reason
Definition
Captures the reason for the current state of the Communication.
+
Comments
This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here.
There are no (further) constraints on this element
Element Id
Communication.medium
Short description
A channel of communication
Definition
A channel that was used for this communication (e.g. email, fax).
+
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.
The patient or group that was the focus of this communication.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.encounter
Short description
Encounter created as part of
Definition
The Encounter during which this Communication was created or to which the creation of this record is tightly associated.
+
Comments
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time).
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.recipient.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Communication.recipient.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Communication.recipient.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Communication.recipient.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time).
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.recipient:ISiKRecipient.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Communication.recipient:ISiKRecipient.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Communication.recipient:ISiKRecipient.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Communication.recipient:ISiKRecipient.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Communication.sender
Short description
Message sender
Definition
The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Communication.sender.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Communication.sender.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Communication.sender.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Communication.sender.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Communication.reasonReference
Short description
Why was communication done?
Definition
Indicates another resource whose existence justifies this communication.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.
+
Requirements
Processors of the data need to be able to know how to interpret the data.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
The calculated hash of the data using SHA-1. Represented using base64.
+
Requirements
Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version).
+
Comments
The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
There are no (further) constraints on this element
Element Id
Communication.note
Short description
Comments made about the communication
Definition
Additional notes or commentary about the communication by the sender, receiver or other interested parties.
+
Comments
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:N/A
rim:Act
workflow:Event.note
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
+
Anmerkungen zu Must-Support-Feldern
+
Communication.inResponseTo
+
Bedeutung: Falls die Communication-Ressource in einen zeitlichen Zusammenhang mit weiteren Nachrichten gebracht werden muss, KÖNNEN die Nachrichten miteinander verknüpft werden. Neue Nachrichten MÜSSEN auf die bereits zuvor existierenden Nachrichten zeigen.
+
Communication.subject
+
Bedeutung: Patient-Referenz als Aussage für welche Patienten die Communication verfasst wird
+
Hinweis: Ein Patientenbezug muss stets gegeben sein, soweit möglich.
+
Communication.recipient
+
Bedeutung: Empfänger der Communication
+
Hinweis: Für Practitioner und HealthcareService muss Reference.reference angegeben werden. Für weitere Ressourcen MUSS ein Reference.display angegeben werden.
+
Communication.sender
+
Hinweis: Für Patient, Practitioner und HealthcareService muss Reference.reference angegeben werden. Für weitere Ressourcen MUSS ein Reference.display angegeben werden.
+
Communication.payload
+
Bedeutung: Inhalt der Communication
+
Hinweis: Es MÜSSEN sowohl Freitext, als auch base64-kodierte Inhalte unterstützt werden. Falls strukturierte Metadaten über das zu übermittelnde Dokument verfügbar sind, KANN es als DocumentReference-Ressource abgelegt werden. Für die Anlage einer solchen Ressource wird auf das ISiK Dokumentenaustausch verwiesen. Die erzeugte Ressource ist anschließend unter dem contentReference-Element als Referenz anzugeben. Jegliche Funktionalität bezogen auf das Modul Dokumentenaustausch ist nicht bestätigungsrelevant. Dokumente welche als Attachment angegeben werden, MÜSSEN in ihrer URL auf eine Binary Ressource verweisen. Diese Binary-Ressource sollte per CREATE-Interaktion angelegt werden im empfangenden System.
+
+
Interaktionen
+
Für die Ressource Communication MÜSSEN die REST-Interaktionen "READ", "CREATE", "UPDATE" implementiert werden.
+
+
Der Suchparameter "_id" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Communication?_id=103270
+
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"]https://hl7.org/fhir/R4/search.html#all).
+
+
Der Suchparameter "subject" MUSS unterstützt werden:
+
Beispiele
+
GET [base]/Communication?subject=Patient/ISiKPatientExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Communication.subject" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference)
+
+
Der Suchparameter "recipient" MUSS unterstützt werden:
+
Beispiele
+
GET [base]/Communication?recipient=Practitioner/ISiKPractitionerExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Communication.subject" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference)
+
+
Der Suchparameter "sender" MUSS unterstützt werden:
+
Beispiele
+
GET [base]/Communication?sender=Practitioner/ISiKPractitionerExample
A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s)
Definition
A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.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()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
app-4:Cancelation reason is only used for appointments that have been cancelled, or no-show Appointment.cancelationReason.exists() implies (Appointment.status='no-show' or Appointment.status='cancelled')
app-3:Only proposed or cancelled appointments can be missing start/end dates (start.exists() and end.exists()) or (status in ('proposed' | 'cancelled' | 'waitlist'))
app-2:Either start and end are specified, or neither start.exists() = end.exists()
ISiK-app-1:Der Endzeitpunkt eines Termins MUSS nach dem Startzeitpunkt liegen start <= end
There are no (further) constraints on this element
Element Id
Appointment.meta
Short description
Metadata about the resource
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.
There are no (further) constraints on this element
Element Id
Appointment.meta.versionId
Short description
Version specific identifier
Definition
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
+
Comments
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
There are no (further) constraints on this element
Element Id
Appointment.meta.lastUpdated
Short description
When the resource version last changed
Definition
When the resource last changed - e.g. when the version changed.
+
Comments
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
There are no (further) constraints on this element
Element Id
Appointment.meta.source
Short description
Identifies where the resource comes from
Definition
A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
+
Comments
In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.
+
This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
There are no (further) constraints on this element
Element Id
Appointment.meta.security
Short description
Security Labels applied to this resource
Definition
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
+
Comments
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
+
Comments
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
+
Comments
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
There are no (further) constraints on this element
Element Id
Appointment.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
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.
+
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.
Optional Extension Element - found in all resources.
+
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.
Optional Extension Element - found in all resources.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.identifier
Short description
External Ids for this item
Definition
This records identifiers associated with this appointment concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.
+
Comments
If the Appointment's status is "cancelled" then all participants are expected to have their calendars released for the appointment period, and as such any Slots that were marked as BUSY can be re-set to FREE.
+
This element is labeled as a modifier because the status contains the code entered-in-error that mark the Appointment as not currently valid.
The coded reason for the appointment being cancelled
Definition
The coded reason for the appointment being cancelled. This is often used in reporting/billing/futher processing to determine if further actions are required, or specific fees apply.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.serviceCategory
Short description
A broad categorization of the service that is to be performed during this appointment
Definition
A broad categorization of the service that is to be performed during this appointment.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.serviceType
Short description
The specific service that is to be performed during this appointment
Definition
The specific service that is to be performed during this appointment.
+
Comments
For a provider to provider appointment the code "FOLLOWUP" may be appropriate, as this is expected to be discussing some patient that was seen in the past.
The specialty of a practitioner that would be required to perform the service requested in this appointment
Definition
The specialty of a practitioner that would be required to perform the service requested in this appointment.
+
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.
The specialty of a practitioner that would be required to perform the service requested in this appointment
Definition
The specialty of a practitioner that would be required to perform the service requested in this appointment.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.appointmentType
Short description
The style of appointment or patient that has been booked in the slot (not service type)
Definition
The style of appointment or patient that has been booked in the slot (not service type).
+
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.
There are no (further) constraints on this element
Element Id
Appointment.reasonCode
Short description
Coded reason this appointment is scheduled
Definition
The coded reason that this appointment is being scheduled. This is more clinical than administrative.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.reasonReference
Short description
Reason the appointment is to take place (resource)
Definition
Reason the appointment has been scheduled to take place, as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Appointment.priority
Short description
Used to make informed decisions if needing to re-prioritize
Definition
The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments. (The iCal Standard specifies 0 as undefined, 1 as highest, 9 as lowest priority).
+
Comments
Seeking implementer feedback on this property and how interoperable it is.
+
Using an extension to record a CodeableConcept for named values may be tested at a future connectathon.
There are no (further) constraints on this element
Element Id
Appointment.priority.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. 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.
+
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.
Optional Extension Element - found in all resources.
+
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.
There are no (further) constraints on this element
Element Id
Appointment.description
Short description
Shown on a subject line in a meeting request, or appointment list
Definition
The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list. Detailed or expanded information should be put in the comment field.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Appointment.supportingInformation
Short description
Additional information to support the appointment
Definition
Additional information to support the appointment provided when making the appointment.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Appointment.start
Short description
When appointment is to take place
Definition
Date/Time that the appointment is to take place.
+
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
There are no (further) constraints on this element
Element Id
Appointment.end
Short description
When appointment is to conclude
Definition
Date/Time that the appointment is to conclude.
+
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
There are no (further) constraints on this element
Element Id
Appointment.minutesDuration
Short description
Can be less than start/end (e.g. estimate)
Definition
Number of minutes that the appointment is to take. This can be less than the duration between the start and end times. For example, where the actual time of appointment is only an estimate or if a 30 minute appointment is being requested, but any time would work. Also, if there is, for example, a planned 15 minute break in the middle of a long appointment, the duration may be 15 minutes less than the difference between the start and end.
+
Comments
32 bit number; for values larger than this, use decimal
The slots from the participants' schedules that will be filled by the appointment.
+
Comments
Zur Referenzierung auf eine Slot-Ressource MUSS eine Reference.reference mit einer URL verwendet werden. Das Termin-Repository muss so gestaltet sein, dass es aus Perspektive des Clients nur eine Service-BaseUrl gibt.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Appointment.slot.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Appointment.slot.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Appointment.slot.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Appointment.slot.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Appointment.created
Short description
The date that this appointment was initially created
Definition
The date that this appointment was initially created. This could be different to the meta.lastModified value on the initial entry, as this could have been before the resource was created on the FHIR server, and should remain unchanged over the lifespan of the appointment.
+
Comments
This property is required for many use cases where the age of an appointment is considered in processing workflows for scheduling and billing of appointments.
There are no (further) constraints on this element
Element Id
Appointment.comment
Short description
Additional comments
Definition
Additional comments about the appointment.
+
Comments
Additional text to aid in facilitating the appointment. For instance, a comment might be, "patient should proceed immediately to infusion room upon arrival"
+
Where this is a planned appointment and the start/end dates are not set then this field can be used to provide additional guidance on the details of the appointment request, including any restrictions on when to book it.
There are no (further) constraints on this element
Element Id
Appointment.patientInstruction
Short description
Detailed information and instructions for the patient
Definition
While Appointment.comment contains information for internal use, Appointment.patientInstructions is used to capture patient facing information about the Appointment (e.g. please bring your referral or fast from 8pm night before).
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Appointment.basedOn
Short description
The service request this appointment is allocated to assess
Alternate names
incomingReferral
Definition
The service request this appointment is allocated to assess (e.g. incoming referral or procedure request).
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Appointment.participant.actor
Short description
Person, Location/HealthcareService or Device
Definition
A Person, Location/HealthcareService or Device that is participating in the appointment.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ical:ATTENDEE: (Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
There are no (further) constraints on this element
Element Id
Appointment.participant.actor.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Appointment.participant.actor.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Appointment.participant.actor.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Appointment.participant.actor.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Appointment.participant.required
Short description
required | optional | information-only
Definition
Whether this participant is required to be present at the meeting. This covers a use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Appointment.participant.period
Short description
Participation period of the actor
Definition
Participation period of the actor.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
A Person, Location/HealthcareService or Device that is participating in the appointment.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ical:ATTENDEE: (Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Appointment.participant:AkteurPatient.actor.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Appointment.participant:AkteurPatient.required
Short description
required | optional | information-only
Definition
Whether this participant is required to be present at the meeting. This covers a use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Appointment.participant:AkteurPatient.period
Short description
Participation period of the actor
Definition
Participation period of the actor.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
A Person, Location/HealthcareService or Device that is participating in the appointment.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ical:ATTENDEE: (Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Whether this participant is required to be present at the meeting. This covers a use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
A Person, Location/HealthcareService or Device that is participating in the appointment.
+
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ical:ATTENDEE: (Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Whether this participant is required to be present at the meeting. This covers a use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Appointment.requestedPeriod
Short description
Potential date/time interval(s) requested to allocate the appointment within
Definition
A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within.
+
The duration (usually in minutes) could also be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. However, in other situations the duration may be calculated by the scheduling system.
+
Comments
This does not introduce a capacity for recurring appointments.
Hinweis: Angabe, ob der Termin durch einen externen Termin Requestor eingestellt wurde. Falls das Datenobjekt dauerhaft in das Termin Repository gespeichert wird, KANN der Tag entfernt werden. Für die weitere Prozesssteuerung kann eine Unterscheidung, ob es sich um einen intern oder extern erstellten Termin handelt, notwendig sein, sodass aus Gründen der Nachvollziehbarkeit der Tag bestehen bleiben sollte. Des Weiteren gelten die Vorgaben des ISiK Basismoduls zur CREATE-Interaktion.
+
Appointment.extension:Nachricht
+
Bedeutung: Kommunikation mit dem Patienten
+
Hinweis: Für die Kommunikation mit dem Patienten sind Communication-Ressourcen zu verwenden. Für den Termin relevante Kommentare oder Anhänge MÜSSEN angegeben werden. Zudem kann die Communication-Ressource auch für die Kommunikation zwischen Leistungserbringer verwendet werden. Es ist zu beachten, dass in diesem Fall Kommentare vor der Herausgabe an die Patient:in gefiltert werden sollten.
+
Appointment.extension:replaces
+
Bedeutung: Angabe eines abgesagten / verschobenen Termins
+
Hinweis: Im Falle, dass per $book-Operation ein verschobener / abgesagter Termin angegeben wird, MUSS dieser für die Rückverfolgbarkeit referenziert werden.
+
Appointment.status
+
Bedeutung: Differenzierung zwischen Terminwunsch und gebuchten Termin
+
Hinweis: Ein Termin Requestor kann im Status entsprechend wählen, sodass der Termin als Terminwunsch zu interpretieren ist. Nachdem der Termin bestätigt wurde, ist der Terminstatus durch das Termin-Repository anzupassen.
+
Alle Statuswerte MÜSSEN durch ein bestätigungsrelevantes System unterstützt werden, insbesondere der Status "proposed" und "booked".
+
Appointment.cancelationReason
+
Bedeutung: Grund für die Absage eines Termins
+
Hinweis: Eine minimale Kodierung MUSS mittels des vorgeschlagenen Bindings vorliegen. Differenzierungen mit feinerer Granularität können durch weitere Codings erfolgen.
+
Appointment.serviceType
+
Bedeutung: Kodierung der Behandlungsleistung des Termins
+
Hinweis: Dies SOLLTE der Kodierung des serviceType eines Schedules entsprechen, der innerhalb des Termins gebucht wird.
+
Appointment.specialty
+
Bedeutung: Kodierung der Fachrichtung des Termins
+
Hinweis: Dies SOLLTE der Kodierung des specialty des Schedules entsprechend, der innerhalb des Termins gebucht wird.
+
Appointment.priority.extension:Priority
+
Bedeutung: Kodierte Angabe der Priorität des Termins
+
Hinweis: Anstelle der numerischen Priorität MUSS in ISiK eine kodierte Priorität angegeben werden.
+
Appointment.start
+
Bedeutung: Startzeitpunkt des Termins
+
Hinweis: Dies MUSS dem Startzeitpunkt des ersten Slots eines Termins entsprechen
+
Appointment.end
+
Bedeutung: Endzeitpunkt des Termins
+
Hinweis: Dies MUSS dem Endzeitpunkt des letzten Slots eines Termins entsprechen
+
Appointment.slot
+
Bedeutung: Referenzierung der Slots für die Verknüpfung des Termins mit einem Schedule
+
Hinweis: Die Referenzierung des Schedules kann durch einen oder mehrere Slots erfolgen. Falls mehrere Slots referenziert werden, MÜSSEN diese den gleichen Schedule referenzieren. Es kann keine Reihenfolge durch die Angabe der Slots abgeleitet werden.
+
Hinweis: In der Vergangenheit liegende Slots, welche nicht verknüpft wurden, dürfen nicht mehr abrufbar sein. Jegliche andere Slots müssen auch per id, herausgegeben werden. Sobald die id einmalig per Search herausgeben wurde, müssen diese gleichbleibend abrufbar sein.
+
Appointment.patientInstruction
+
Bedeutung: Handlungsanweisungen für die Patienten in Vorbereitung auf den Termin
+
Appointment.participant
+
Bedeutung: TeilnehmerInnen des Termins
+
Hinweis: Mindestens eine Patient-Referenz MUSS angegeben werden. Dies MUSS durch das Termin-Repository während der Buchung des Termins geprüft werden. Weitere Leistungserbringer KÖNNEN angegeben werden.
+
+
Interaktionen
+
Für die Ressource Appointment MÜSSEN die REST-Interaktionen "READ" und "PATCH" implementiert werden.
+
+
Der Suchparameter "_id" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?_id=103270
+
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"]https://hl7.org/fhir/R4/search.html#all).
+
+
Der Suchparameter "status" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?status=booked
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Appointment.status" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "service-type" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?service-type=http://example.org/fhir/CodeSystem/ScheduleServiceType|CT
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Schedule.serviceType" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "specialty" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?specialty=urn:oid:1.2.276.0.76.5.114|535
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Appointment.specialty" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "date" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?date=2022-12-10T09:00:00Z
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Appointment.start" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Date Search"]https://hl7.org/fhir/R4/search.html#date).
+
+
Der Suchparameter "slot" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?slot=Slot/ISiKSlotExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Appointment.slot" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference).
+
+
Der Suchparameter "actor" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Appointment?actor=Patient/ISiKPatientExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Appointment.participant.actor" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference).
Die Slot-Ressource repräsentiert die Verbindung eines Termins (Appointment) und den dazugehörigen Ressourcen (z.B. HealthcareService, Device, Practitioner). Für diese Ressourcen können separate Kalender (Schedules) verwaltet werden. Der Slot agiert als Verbindungsstück zwischen diesen Ressourcen.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.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()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
ISiK-slot-1:Der Endzeitpunkt eines Terminsblocks MUSS nach dem Startzeitpunkt liegen start <= end
Mappings
rim:Entity. Role, or Act
rim:n/a
ical:(refer to the Availability resource for the header mapping details)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Slot.serviceCategory
Short description
A broad categorization of the service that is to be performed during this appointment
Definition
A broad categorization of the service that is to be performed during this appointment.
+
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.
There are no (further) constraints on this element
Element Id
Slot.serviceType
Short description
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
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.
+
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.
There are no (further) constraints on this element
Element Id
Slot.specialty
Short description
The specialty of a practitioner that would be required to perform the service requested in this appointment
Definition
The specialty of a practitioner that would be required to perform the service requested in this appointment.
+
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.
There are no (further) constraints on this element
Element Id
Slot.appointmentType
Short description
The style of appointment or patient that may be booked in the slot (not service type)
Definition
The style of appointment or patient that may be booked in the slot (not service type).
+
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.
The schedule resource that this slot defines an interval of status information
Definition
The schedule resource that this slot defines an interval of status information.
+
Comments
Zur Referenzierung auf eine Schedule-Ressource MUSS eine Reference.reference mit einer URL verwendet werden. Das Termin-Repository muss so gestaltet sein, dass es aus Perspektive des Clients nur eine Service-BaseUrl gibt.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Slot.schedule.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Slot.schedule.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Slot.schedule.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Slot.schedule.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Slot.start
Short description
Date/Time that the slot is to begin
Definition
Date/Time that the slot is to begin.
+
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
There are no (further) constraints on this element
Element Id
Slot.end
Short description
Date/Time that the slot is to conclude
Definition
Date/Time that the slot is to conclude.
+
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
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
ISiK-slot-1
error
Der Endzeitpunkt eines Terminsblocks MUSS nach dem Startzeitpunkt liegen
start <= end
+
+
+
Anmerkungen zu Must-Support-Feldern
+
Slot.schedule
+
Bedeutung: Verknüpfung einer Termins / Terminblocks und den dazugehörigen Terminlisten bzw. deren Ressourcen.
+
Hinweise: Die Referenz auf Schedule bietet die Möglichkeit der Abfrage eines Appointments / Slots auf Basis einer Verknüpfung mit einem Schedule bzw. eines Schedules für eine bestimmte Ressource (Schedule.actor).
+
Slot.status
+
Bedeutung: Indikator ob ein Slot verwendbar ist für die Buchung eines Appointments.
+
Hinweise: Inbesondere eine Differenzierung des Status "busy" ermöglicht es einem Termin Requestor passende Termine einer BenutzerIn zur Verfügung zu stellen. Durch entsprechende Kombinationen können somit Termine in einer passenden Länge gebucht werden.
+
Slot.start
+
Bedeutung: Startdatum des Slots (sekundengenau).
+
Hinweise: Falls sich ein Appoinment über mehrere Slots erstreckt, kann mit Hilfe des Startdatums der Beginn eines zu vereinbarenden Termins gefunden werden.
+
Slot.end
+
Bedeutung: Enddatum des Slots (sekundengenau).
+
Hinweise: Falls sich ein Appoinment über mehrere Slots erstreckt, kann mit Hilfe des Enddatums der Slot gefunden werden, welcher als nächste innerhalb einer Reihe gebucht werden muss, sodass das Appointment eine gewünschte Länge erreicht.
+
+
Interaktionen
+
Für die Ressource Slot MUSS die REST-Interaktion "READ" implementiert werden.
+
+
Der Suchparameter "_id" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Slot?_id=103270
+
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Parameters for all resources"]https://hl7.org/fhir/R4/search.html#all).
+
+
Der Suchparameter "schedule" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Slot?schedule=Schedule/ISiKKalenderExample
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Slot.schedule" finden sich in der [FHIR-Basisspezifikation - Abschnitt "reference"]https://hl7.org/fhir/R4/search.html#reference).
+
+
Der Suchparameter "status" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Slot?status=busy
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Slot.status" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Token Search"]https://hl7.org/fhir/R4/search.html#token).
+
+
Der Suchparameter "start" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/Slot?start=2022-12-10T09:00:00Z
+
Anwendungshinweise: Weitere Informationen zur Suche nach "Slot.start" finden sich in der [FHIR-Basisspezifikation - Abschnitt "Date Search"]https://hl7.org/fhir/R4/search.html#date).
+
+
Abfrage aller verfügbaren Slots für einen Kalender:
+
GET https://example.org/fhir/Slot?schedule=<Scheudule/ISiKKalenderExampple>
+
Anwendungshinweise: In diesem Fall ist auch ein Chaining auf weitere verknüpfte Akteure möglich: GET https://example.org/fhir/Slot?schedule.actor:HealthcareService.type=https://example.org/fhir/CodeSystem/Behandlungsleistung|CT
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-Operations.html b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-Operations.html
new file mode 100644
index 00000000..837fa854
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte-Operations.html
@@ -0,0 +1,402 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Operations
+
Es gelten die allgemeinen Vorgaben der FHIR-Kernspezifikation für die Ausführung von Custom Operations.
+
+
Buchung eines Termins
+
Invocations
URL: [base]/Appointment/$book
+
This operation changes content
Parameters (In)
Name
Cardinality
Type
Documentation
appt-resource
1..1
Appointment
Eine Appointment-Ressource entsprechend dem dazugehörigen ISiK-Profil MUSS übergeben werden. Falls das Parameter-Element 'Appointment' als einziges Parameter-Element verwendet wird, SOLL die Appointment-Ressource direkt im HTTP Body übergeben werden, alternativ zu einer Parameter-Ressource inklusive dem eingebetteten Appointment-Element. Invalide Ressourcen MÜSSEN abgelehnt werden durch das Termin Repository (zur Form der Ablehnung s.u.). Das Appointment MUSS den Status 'proposed' enthalten.
cancelled-appt-id
0..1
uri
Für die vorliegende Spezifikation ist die Verschiebung eines Termin eins zwei-stufiger Prozess, bei dem ein Termin storniert und ein neuer Termin neu gebucht wird. Dieser Parameter repräsentiert die Ressourcen-Id des stornierten Appointments. Der uri-Parameter kann eine absoulte URL enthalten, Server SOLLEN jedoch nur Termine für ihre eigene Domäne verwalten. Im neu-angelegten Appointment MUSS eine Reference auf den abgesagten Termin hinterlegt werden (vgl. Appointment.extension:replaces). Der Status der abgesagten Ressource MUSS durch den Server angepasst werden.
Im Falle dass ein Appointment keine Referenz auf ein oder mehrere Slots enthält, MUSS der Server die benötigten Slots auf Basis der Referenz auf Schedule, sowie dem Start- und Endzeitpunkt im Appointment ermitteln.
Return Values (Out)
Name
Cardinality
Type
Documentation
return
0..1
Bundle
Als Return-Parameter MUSS ein Bundle vom Typ 'searchset' zurückgegeben werden, welches eine aktualisierte Appointment- oder eine OperationOutcome-Ressource enthält. Falls die Terminbuchung akzeptiert wird, MUSS das Appointment persistiert werden. Das id-Element der Ressource MUSS korrekt gefüllt werden. Der Status der Appointment-Ressource MUSS auf 'booked' geändert werden. Der Server MUSS die verwendeten Slot-Ressourcen als Referenz im Appointment angeben.
+
Übersicht Interaktion Termin Requestor mit Termin Repository
+
Folgende Schritte KÖNNEN notwendig sein, sodass ein Termin durch einen Termin Requestor innerhalb eines Termin Repository eingestellt wird. Es ist zu beachten, dass für spezielle Implementierungen nicht alle Schritte hiervon relevant sind und übersprungen werden können.
+
Generell wird darauf hingewiesen, dass abhängig davon, welcher Client oder Benutzer eine Interaktion ausführt, unterschiedliche Ergebnisse zurückgeliefert werden können. Die vorliegende Spezifikation macht keine Vorgaben, wie eine Authentifizierung zu implementieren ist. Es wird als Best-Practice auf das ISiK-Modul 'Sicherheit' verwiesen.
+
+
Abfrage aller Kodierungen der Behandlungsleistungen durch den Termin-Requestor: GET https://example.org/fhir/CodeSystem?context-type-value=https://gematik.de/fhir/isik/v2/Terminplanung/CodeSystem/ContextType|ResourceUsage$http://hl7.org/fhir/resource-types|HealthcareService
+
+
Das Termin-Repository MUSS alle CodeSysteme exponieren, welche für die Kodierung eines HealthcareService relevant sind. Die Anfrage ist nicht auf HealthcareService beschränkt, weitere Ressourcen-Kontexte können abgefragt werden. Alle verwendeten CodeSysteme MÜSSEN exponiert werden, insoweit diese sich als CodeSystem-Ressourcen ausdrücken lassen.
+
Hinweis: Diese Abfrage ist für eine Initialisierung des Termin-Requestors gedacht. Es ist davon auszugehen, dass diese Auswahlliste nicht dynamisch angepasst wird durch das Termin-Repository und nicht bei jeder Terminbuchung erneut abgefragt werden muss.
+
+
Abfrage aller verfügbaren Kalender: GET https://example.org/fhir/Schedule
+
+
Der Termin-Requestor KANN durch die Abfrage aller verfügbaren Kalender alle Ressourcen abfragen, für die eine Termin-Buchung zur Verfügung steht.
+
+
Abfrage aller verfügbaren Slots für einen Kalender durch den Termin-Requestor: GET https://example.org/fhir/Slot?schedule=<Schedule/ISiKKalenderExample>&status=free
+
+
In diesem Fall ist auch ein Chaining auf weitere verknüpfte Akteure möglich: GET https://example.org/fhir/Slot?schedule.actor:HealthcareService.type=http://dicom.nema.org/resources/ontology/DCM|CT
+
+
Anlage einer Patient-Ressource: POST https://example.org/fhir/Patient
Es ist zu beachten, dass es aus Effizienzgründen für bestimmte Implementierungen sinnvoll sein kann, dass Updates einer Appointment-Ressource ausgelöst durch das Termin-Repository mittels eines Push-Mechanismus an Termin-Consumer / Termin-Requestor übermittelt werden. Im Standard-Fall müssen diese Akteure die Ressourcen mittels des entsprechenden Endpunktes eigenständig abfragen und auf Updates überprüfen. Für einen Push-Mechanismus wird auf FHIR Subscriptions verwiesen. Die vorliegende Spezifikation macht jedoch KEINE Vorgaben für die Verwendung einer solchen Methodik.
+
Eine Aktualisierung der Ressource erfolgt mittels einer HTTP PATCH-Interaktion. Updates einer Appointment-Ressource MUSS das Termin Repository unterstützen. Es MUSS mindestens die PATCH-Interaktion auf Basis einer FHIRPath-Patch-Parameter Ressource unterstüzt werden.
+
Folgende Elemente DÜRFEN NICHT durch ein Update der Ressourcen verändert werden:
+
+
Appointment.slot
+
Appointment.start
+
Appointment.end
+
Appointment.participant.actor.where(resolve() is Patient)
+
+
Hinweis: Hinweis: Ein Termin Repository MUSS einen Termin ablehnen, falls der Termin auf einen nicht vorhandenen (gelöscht oder inkativ) Patienten referenziert. Dies gilt insbesondere auch nachträglich für vorläufig angelegte Patienten-Ressourcen.
+
Sollte die PATCH-Parameter-Ressource eins dieser Elemente verändern, MUSS die Operation mit einem Status Code "HTTP 400 - Bad Request" zurückgewiesen werden. Eine OperationOutcome Ressource MUSS zurückgegeben werden, die in kodierter Form den entsprechenden Fehler beschreibt.
Ein Termin Repository MUSS die Anlage (Create-Interaktion) einer Patient-Ressource entsprechend der Vorgaben des ISiK-Basismoduls unterstützen.
+
+
Asynchrone Ausführung $book
+
Die Operation zur Buchung eines Termin MUSS ebenfalls asynchron ausgeführt werden können, für den Fall, dass ein Termin-Repository keine Terminbestätigung als direkte Antwort versenden kann. Beispielsweise kann dies der Fall sein, falls ein Termin zunächst manuell im Termin-Repository bestätigt werden muss. Es gelten die Regeln der FHIR Kernspezifikation - Abschnitt 3.2.0.7 Executing an Operation Asynchronously:
+
+
Der Aufruf der $book-Operation erfolgte auch im asynchronen Fall durch einen POST-Request
+
Ein HTTP-Header mit dem Namen "Prefer" und dem Inhalt "respond-async" MUSS im Aufruf der Operation enthalten sein
+
Als HTTP-Status-Code MUSS das Termin-Repository 202 - Accepted zurückgeben
+
Im Fehlerfall MUSS ein 4XX- oder 5XX-HTTP-Status-Code zurückgeben werden
+
Zudem MUSS das Termin-Repository einen "Content-Location"-Header zurückliefern indem eine valide absolute URL enthalten ist unter welcher das oben beschriebene Suchbundle inkl. Appointment-Ressource als Antwort auf die Buchung des Termins abgerufen werden kann
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte.html b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte.html
new file mode 100644
index 00000000..c4eedff2
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-Datenobjekte.html
@@ -0,0 +1,227 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Datenobjekte
+
Folgende Datenobjekte und Interaktionen aus dem Modul ISiK Basis Stufe 2 sind in diesem Modul bestätigungsrelevant:
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-Einfuehrung.html b/IG/2.0.4/ImplementationGuide-markdown-Einfuehrung.html
new file mode 100644
index 00000000..c739c470
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-Einfuehrung.html
@@ -0,0 +1,241 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Version: 2.0.4
+
Datum: 29.11.2023
+
Status: Aktiv
+
Realm: Deutschland
+
+
Interoperabler Datenaustausch durch Informationssysteme im Krankenhaus (ISiK)
+
Die gematik wurde vom Gesetzgeber beauftragt, im Benehmen mit der Deutschen Krankenhausgesellschaft (DKG) und den maßgeblichen Bundesverbänden der Industrie im Gesundheitswesen, verbindliche Standards für den Austausch von Gesundheitsdaten mit Informationssystemen im Krankenhaus zu erarbeiten. Dieser FHIR ImplementationGuide (IG) beschreibt die für diesen Zweck entwickelten FHIR Profile und das REST-basierte Application Programming Interface (API). Die REST-API wird im Wesentlichen vom FHIR Standard vorgegeben. Dieser Leitfaden konkretisiert die ISiK-relevanten Funktionen der Standard-REST-API und trifft inhaltliche Festlegungen zu den ISiK-relevanten Ressourcen in Form von Ressourcen-Profilen.
+
Hersteller bestätigungsrelevanter Systeme sollen durch diesen IG in die Lage versetzt werden, eine konforme Implementierung zu erstellen und das Bestätigungsverfahren der gematik erfolgreich zu absolvieren.
Hinweis: Sowohl für die Implementierung der ISiK-Spezifikation als auch für den Betrieb eines Produktes, das die ISiK-Spezifikation implementiert, ist eine SNOMED-CT-Lizenz notwendig. Diese kann beim National Release Center für SNOMED CT in Deutschland beantragt werden.
+
Kontakt
+
Bringen Sie allgemeine Fragen und Anmerkungen gerne über unser Anfrageportal ein: Anfragen ISiK + ISiP
+
Falls Sie keinen Zugang zum Anfrageportal haben und dieses nutzen wollen, senden Sie uns bitte eine Nachricht an die Adresse isik [ at ] gematik.de mit dem Betreff "Portalzugang".
Zugunsten des Leseflusses wird in dieser Publikation meist die
+männliche Form verwendet. Wir bitten, dies nicht als Zeichen einer
+geschlechtsspezifischen Wertung zu deuten. Diese Variante deckt auch alle
+weiteren Geschlechter, neben männlich und weiblich, ab.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-Motivation.html b/IG/2.0.4/ImplementationGuide-markdown-Motivation.html
new file mode 100644
index 00000000..ad6f8966
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-Motivation.html
@@ -0,0 +1,230 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Die Vereinbarung von Terminen für Behandlungsleistungen repräsentiert oftmals für Patienten oder für sie zuständige Leistungserbringer den Einstieg in den Versorgungsablauf im Krankenhaus. Die Terminplanung agiert somit als kritische Schnittstelle zwischen diversen Akteuren im Gesundheitswesen, inklusive der zu behandelnden Personen. Informationen zu notwendigen und/oder gewünschten Behandlungen, Verfügbarkeiten der involvierten Personen und abrechnungsrelevante Details zur Krankenversicherung müssen potenziell ausgetauscht werden um einen optimierten Ablauf des Aufenthaltes im Krankenhaus zu ermöglichen.
+
Das Krankenhauszukunftsgesetz (KHZG) hebt die zentrale Rolle der Terminvereinbarung hervor in dem in den dazugehörigen Fördertatbeständen Vorgaben für die Terminplanung im digitalen Aufnahmemanagement bzw. für die Terminplanung mittels Patientenportalen gemacht werden (vgl. §19 Abs. 1 Satz 1 Nr. 2 KHSFV bzw. §21 Abs. 2 KHSFV).
+
Angelehnt an diese Vorgaben soll mittels ISiK die Grundlage geschaffen werden, um die beschriebenen oder ähnliche Use Cases durchzuführen und die fachlich-inhaltlichen Informationen in einer interoperablen Art und Weise auszutauschen. ISiK versteht sich somit als Schnittstellenbeschreibung, um eine einheitliche API zu dokumentieren, durch die ein Termin vereinbart und verwaltet werden kann. Das vorliegende ISiK-Modul bietet somit explizit KEIN umfassendes Datenmodell für die krankenhausinterne Ressourcenplanung. Hingegen werden durch ISiK Minimalvorgaben für bestätigungsrelevante Systeme spezifiziert, auf die komplexere Workflows ausgestaltet werden können.
+
Durch ISiK Terminplanung sollen folgende Möglichkeiten eröffnet werden:
+
+
Abruf von Abbildungen von verfügbaren teil- und voll- stationären Behandlungsleistungen durch ein Krankenhaus
+
Abfrage von Terminen und Verfügbarkeiten
+
Buchungsmanagement von verfügbaren Terminen
+
Benachrichtigungen bei Terminänderungen
+
Anlage eines neuen Patienten im terminführenden System (Übermittlung Patient/Versicherungsinformationen)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-ReleaseNotes.html b/IG/2.0.4/ImplementationGuide-markdown-ReleaseNotes.html
new file mode 100644
index 00000000..88f92718
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-ReleaseNotes.html
@@ -0,0 +1,284 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Release Notes
+
Im Rahmen der ISiK-Veröffentlichungen wird das Semantic Versioning verwendet.
+
Die erste Ziffer X bezeichnet ein Major-Release und regelt die Gültigkeit von Releases. Die dritte Ziffer Y (Release x.0.y) bezeichnet eine technische Korrektur und versioniert kleinere Änderungen (Packages) während eines Jahres, z. B. 1.0.1.
Reference(Schedule) statt Reference(ISiKKalender). Reference-Element erweitert auf die Kernspezifikation (entspricht allgemeinem Design-Prinzip), damit die Profile auch außerhalb des ISiK-Kontextes nutzbar sind.
+
+
+
Update Basismodul Dependency -> 2.0.4
+
weitere Änderungen an IG (informativ)
+
+
+
Version: 2.0.2
+
Datum: 31.01.2023
+
+
ISiKTerminblock
+
+
Reference(Schedule) statt Reference(ISiKKalender). Reference-Element erweitert auf die Kernspezifikation (entspricht allgemeinem Design-Prinzip), damit die Profile auch außerhalb des ISiK-Kontextes nutzbar sind.
+
+
+
Update Basismodul Dependency -> 2.0.4
+
weitere Änderungen an IG (informativ)
+
+
+
Version: 2.0.1
+
Datum: 31.10.2022
+
+
Update Basismodul Dependency -> 2.0.2
+
+
+
Version: 2.0.0
+
Datum: 30.06.2022
+
+
Initialer Release
+
+
+
Version: 2.0.0 (Ballotierung)
+
Datum: 31.03.2022
+
+
Initiale Ballotierungsversion für ISiK Stufe 2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Akteure.html b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Akteure.html
new file mode 100644
index 00000000..662b61e7
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Akteure.html
@@ -0,0 +1,262 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Akteure
+
Innerhalb des ISiK Moduls Terminplanung kann ein beteiligtes System verschiedene Rollen einnehmen und somit unterschiedliche Aufgaben innerhalb der im Abschnitt Interaktionen definierten Arbeitsabläufe übernehmen. Im Weiteren werden diese Rollen mithilfe der Definition von Akteuren formalisiert, sodass eine Zuordnung von relevanten Interaktionen zum jeweiligen Akteur erfolgen kann.
+
Grundsätzlich wird als Terminblock eine für einen Termin buchbare Zeiteinheit verstanden, in der bestimmte Ressourcen (z.B. Fachabteilungen, Personen im Gesundheitswesen, Geräten, Räumen) zur Verfügung stehen. Übergreifend über ein oder mehrere Terminblöcke hinweg kann für diese Ressourcen anschließend ein Termin vereinbart werden.
+
Termin Repository
+
Definition:
+
Als Termin Repository werden alle Systeme definiert, die Informationen zu verfügbaren Termineinheiten von Ressourcen (vgl. zuvor genannte Definition) vorhalten und die dafür vereinbarten Termine als führendes System verwalten.
+
Das Termin Repository kann intern in ein Repository für die Termine und ein separates Repository für die buchbaren Terminblöcke (Terminblock Repository) geteilt werden.
+
Beispielsysteme:
+
+
Patientenportal im Falle, dass das System selbst terminführend ist
+
KIS / KAS inkl. Terminverwaltung
+
+
Termin Requestor / Termin Source
+
Definition:
+
Als Termin Requestor (in Anlehnung an die IHE Terminologie auch als Termin Source zu bezeichnen) werden alle Systeme definiert, die zur Erhebung, Erfassung, Anpassung oder Veränderung von Termininformationen dienen. Ein Termin Requestor verfügt über keine permanente Persistierung der verarbeiteten Informationen. Der Termin Requestor übernimmt die Koordination der Schnittstellenaufrufe, um einen Termin zu buchen.
+
Beispielsysteme:
+
+
Patientenportal im Falle, dass ein externes System das terminführende System ist
+
+
Termin Consumer
+
Definition:
+
Als Termin Consumer werden alle System definiert, die Termininformationen abfragen, um diese einer BenutzerIn zu präsentieren. Ein Termin Consumer verfügt über keine permanente Persistierung der abgefragten Informationen. Durch den Termin Consumer erfolgt explizit nur die Aufbereitung und Präsentation der Termininformationen. Eine anderweitige Verarbeitung der Termininformationen fällt in die Kategorie der anderen Akteure.
+
Beispielsysteme:
+
+
Apps zum Anzeigen eines Kalenders
+
Backendsysteme zum Versenden von Benachrichtigungen im Kontext eines Termins
+
Ressourcenmanagementsoftware
+
+
Übersicht der Akteure
+
Es sei zu beachten, dass in vielen Fällen ein Terminmangementsystem aus unterschiedlichen Modulen besteht, die mehreren oder allen der genannten Akteure entsprechen:
+
+
Ein Termin Repository, da das System das terminführende System ist
+
Ein Termin Requestor, um intern im System einen Termin zu vereinbaren
+
Ein Termin Consumer um eine Übersicht der vereinbarten Termine anzuzeigen
+
+
+
+
+
+
Darüber hinaus kann auch der Fall eintreten, dass ein Termin Repository als Termin Requestor interagiert. In diesem Fall ist das Termin Repository (z.B. ein Patientenportal) das terminführende System und übermittelt die vereinbarten Termine einem weiteren (internen) Termin Repository zur Synchronisation.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-BestaetigungsrelevanteSysteme.html b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-BestaetigungsrelevanteSysteme.html
new file mode 100644
index 00000000..ff1a2934
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-BestaetigungsrelevanteSysteme.html
@@ -0,0 +1,268 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Bestätigungsrelevante Systeme
+
Hier folgt die Festlegung der Deutschen Krankenhausgesellschaft e. V. wie hier aufgeführt
+
Festlegung der Deutschen Krankenhausgesellschaft e. V. aus dem Jahr 2022
+
Die im Folgenden definierten Subsysteme müssen gemäß § 373 Abs. 2 SGB V nach
+zweijähriger Übergangsfrist im Krankenhaus um die Schnittstelle erweitert sein, die
+das ISIK-Modul bzw. die Datenobjekte der gematik jeweils beschreiben. Die Festlegung der Systeme zu den einzelnen ISiK-Modulen ist um Erläuterungen in eckigen
+Klammern ergänzt.
+
ISiK-Basismodul (Stufe 1 und Stufe 2)
+
+
Krankenhaus-Informationssystem (KIS)
+
+
ISiK-Modul Vitalwerte und Körpermaße
+
+
KIS mit Funktion elektronische Kurve bzw. entsprechendes KIS-Modul
+
Patientendaten-Managementsystem (PDMS) [z.B. für Intensivbereiche]
+
Elektronische Kurve [z.B. für die Verwendung auf Normal-Stationen]
+
+
ISiK-Modul Dokumentenaustausch
+
+
KIS
+
Dokumentenmanagementsystem (DMS)
+
Archivsystem
+
Telekonsil-Modul gemäß § 31a BMV-Ä [Ziel ist die clientseitige Implementierung für die Suche nach Dokumenten anhand von Metadaten,
+Verarbeitung von Suchergebnissen und Dokumentenzugriff zur Verwendung in Telekonsilien], hierbei keine Umsetzung einer Funktion zum Abruf von Dokumenten aus dem Telekonsil-Modul
+
KIM-Client-Anwendungssoftware [die Anwendungsintegration, nicht der
+KIM-Client, Implementierung für die Ablage von Dokumenten aus KIM-Nachrichten und den Versand von Dokumenten mit KIM-Nachrichten],
+hierbei keine Umsetzung einer Funktion zum Abruf von Dokumenten aus
+der KIM-Client-Anwendungssoftware
+
+
ISiK-Modul Medication
+
+
KIS
+
PDMS [Anwendungsfallbeispiel: Medikationsdaten in das KIS übertragen bei Verlegung vom Intensivbereich auf Normal-Station]
+
Software für digitales Medikationsmanagement [z.B. für die Umsetzung
+von KHZG Fördertatbestand 5]
+
E-Therapieplan-System für Zytostatika-Behandlung mit Verarbeitung
+von Verordnungs- und Medikationsinformationen [teilweise Grundlage
+für onkologische Verordnungsdaten], gemäß diesen Festlegungen keine
+Umsetzung des ISIK-Datenobjekts MedikationsVerabreichung notwendig
+
Herstellungssystem mit Verarbeitung von Verordnungs- und Medikationsinformationen [in KH-Apotheke, z.B. für Zytostatika], gemäß diesen
+Festlegungen keine Umsetzung des ISIK-Datenobjekts MedikationsVerabreichung notwendig
+
E-Rezept-Modul für Herstellungen [eRezept an Fachdienst in TI übertragen]
+
Taxierungssoftware [in KH-Apotheke]
+
+
ISiK-Modul Terminplanung [z.B. für die Umsetzung von KHZG Fördertatbestand 2]
+
+
KIS
+
Patientenportal-Terminmodul
+
+
Hinweise und Rückfragen zu den bestätigungsrelevante Systemen können an die DKG-Geschäftsstelle gerichtet werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Interaktionen.html b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Interaktionen.html
new file mode 100644
index 00000000..0184a028
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Interaktionen.html
@@ -0,0 +1,299 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Interaktionen
+
Für folgende Interaktionen werden im vorliegenden Implementierungsleitfaden Vorgaben für die Umsetzung innerhalb der ISiK-Schnittstelle definiert:
+
+
+
+
+
+
Für die Auswahl eines verfügbaren Terminblocks kann es notwendig sein, dass das Termin Repository vorab durch den Termin Requestor Vorabinformationen (z.B. für die Krankenversicherung) erhält. Diese können über eine schreibende Schnittstelle an das Terminrepository übermittelt werden. Es ist zu beachten, dass das Termin Repository gegebenenfalls diese Informationen separat von eigens erstellten Datenobjekten vorhält und/oder die Information dauerhaft erst nach einer manuellen Überprüfung durch eine BenutzerIn freigibt.
+
Gleichermaßen können Informationen zum Patienten vorab übermittelt werden, sodass gewisse Basisangaben bereits im Terminrepository vorliegen.
Als Einstiegspunkt in die Terminvereinbarung können durch den Termin Requester alle verfügbaren Behandlungsleistungen (HealthcareServices) abgerufen werden, für die das Termin Repository Informationen zu notwendigen Ressourcen (Räume, Personen, Geräte, etc.) bereitstellt.
Der Termin Requestor kann nach der Auswahl einer Behandlungsleistung verfügbare Terminlisten (Schedules) für diese im Termin Repository abrufen. Die Terminlisten repräsentieren somit den "Kalender" in dem Termine gebucht werden können.
Für einen jeweiligen Kalender kann der Termin Requestor die darin definierten Terminblöcke abfragen. Diese können entsprechend eines Zeitraums und/oder Status (verfügbar, belegt) gefiltert werden.
Für einen durch die BenutzerIn ausgewählten Terminblock bzw. mehreren aufeinander folgenden Terminblöcken kann durch den Termin Requestor ein Termin angefragt werden. Dieser kann direkt oder erst nach manueller Bestätigung durch das Termin Repository freigegeben werden.
+
Es ist zu beachten, dass innerhalb dieser Aktion ein terminführendes Termin Repository die Rolle des Termin Requestors übernehmen kann und den neu-angelegten Termin in ein weiteres Terminrepository spiegelt.
+
In diesem Kontext kann das Termin-Repsoitory zudem Zusatzinformationen (z.B. Lagepläne) an den Termin-Requestor übermitteln.
Termine können sowohl durch den Termin Requestor als Client oder durch das Termin Repository als terminführendes System verschoben werden. Im Falle, dass das Termin Repository den Termin verschiebt ist der Termin Consumer darüber zu benachrichtigen.
Termine können sowohl durch den Termin Requestor als Client oder durch das Termin Repository als terminführendes System durch Zusatzinformationen (z.B. welche Teilnehmer oder Ressourcen sind Teil des Termins) erweitert werden.
+
In diesem Kontext kann der Termin-Requestor zudem Zusatzinformationen (z.B. Einwilligungen) an das Termin-Repository übermitteln.
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Kompatibilitaet.html b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Kompatibilitaet.html
new file mode 100644
index 00000000..c782c88b
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-Kompatibilitaet.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität zu anderen nationalen FHIR-basierten Spezifikationen
+
Die vorliegende Spezifikation orientiert sich teilweise an bereits vorhandenen (internationalen) FHIR-Projekten zum Thema Terminvergabe. Hier sei vorallem das [Argonaut Scheduling Project]https://fhir.org/guides/argonaut/scheduling/) hervorgehoben.
+
Kompatibilität zum KBV eTerminService
+
Bei folgenden FHIR-Ressourcen existiert zum Zeitpunkt der Veröffentlichung eine inhatliche Überschneidung mit dem eTerminService der KBV:
+
+
Patient - Jede ISiK "Patient"-Instanz ist auch valide gegen das entsprechende KBV ETS Profil falls:
+
+
Elemente, die auf eine Kardinalität von 0..0 beschränkt sind, entfernt werden
+
+
+
Appointment - Jede ISiK "Appointment"-Instanz ist auch valide gegen das entsprechende KBV ETS Profil falls:
+
+
Elemente, die auf eine Kardinalität von 0..0 beschränkt sind, entfernt werden
+
Eine PractitionerRole Referenz als Akteur angegeben wird
+
+
+
+
Aufgrund von fachlichen Unterschieden in den zu unterstützenden Arbeitsabläufen sind die OperationDefinitions für die Buchung eines Termins nicht vergleichbar.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html
new file mode 100644
index 00000000..5fac253d
--- /dev/null
+++ b/IG/2.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html
@@ -0,0 +1,229 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Modul Terminplanung
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Übergreifende Festlegungen
+
Folgende Festlegungen aus dem Modul ISiK Basis Stufe 2 haben in diesem Modul Gültigkeit:
+