Implementierungsleitfaden ISiK-Basismodul (4.0.1)

Kontakt/Fall (Encounter)

ISiKKontaktGesundheitseinrichtung

Dieses Profil ermöglicht die Abbildung von Besuchen/Aufenthalten eines Patienten in einer Gesundheitseinrichtung.

Motivation

Informationen über die Besuche des Patienten entlang seines Behandlungspfades im Krankenhaus sind ein wichtiger Bestandteil des einrichtungsinternen Datenaustausches. Sie ermöglichen die Unterscheidung von stationären und ambulanten sowie aufgenommenen und entlassenen Patienten. Weiterhin ist aus den Besuchsinformationen der aktuelle Aufenthaltsort des Patienten (Fachabteilung, Station, Bettplatz) ermittelbar. Klinische Ressourcen werden in FHIR durch Verlinkung auf die Encounter-Ressource in einen Kontext zum Besuch gestellt. Dieser Kontext ist wichtig für die Steuerung von Zugriffsberechtigungen und Abrechnungsprozessen.

Zu Beginn der meisten klinischen Workflows steht die Auswahl des Besuchskontextes. Dies geschieht bspw. durch das Suchen der Encounter-Ressource anhand von Eigenschaften wie Aufnahmenummer, Fallart oder Aufnahmedatum. Daraufhin werden die zutreffenden Suchergebnisse angezeigt und der gewünschte Besuch ausgewählt.

In FHIR werden Besuche, Aufenthalte, aber auch virtuelle Kontakte mit der Encounter-Ressource repräsentiert.

Weitere Hinweise zu den Abgrenzungen der Begrifflichkeiten Fall und Kontakt finden sie unter Fall-Begriff in ISiK

Kompatibilität

Für das Profil ISiKKontaktGesundheitseinrichtung wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKKontaktGesundheitseinrichtung valide sind, auch valide sind gegen:

Profil Kontakt mit einer Gesundheitseinrichtung der Medizininformatik-Initiative

Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden.

Bestätigungsrelevanz

Verbindlichkeit	SHALL

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung
Status	active
Version	4.0.1
Basis	http://hl7.org/fhir/StructureDefinition/Encounter

Inhalt

ISiKKontaktGesundheitseinrichtung (Encounter)	I		Encounter	Element id Encounter Short description An interaction during which services are provided to the patient Alternate names Visit Definition An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. Data type Encounter Constraints 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-enc-1: Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben `status = 'finished' and class = 'AMB' implies period.start.exists()` ISiK-enc-2: Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben `status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()` ISiK-enc-3: Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben `status = 'planned' implies period.exists().not()` ISiK-enc-4: Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden `status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()` ISiK-enc-5: In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben `status = 'in-progress' implies period.start.exists()` ISiK-enc-6: Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben `status = 'onleave' implies period.start.exists()` ISiK-enc-7: Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben `status = 'unknown' implies period.start.exists()` ISiK-enc-8: Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein `diagnosis.use.all(coding.code != 'billing')` Mappings rim: Entity. Role, or Act workflow: Event rim: Encounter[@moodCode='EVN']
id	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Encounter.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. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Encounter.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id Encounter.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Encounter.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	S I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
Aufnahmegrund	S I	0..1	Extension(Complex)	Element id Encounter.extension:Aufnahmegrund Short description Aufnahmegrund Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments Aufnahmegrund nach § 301 Abs. 3 SGB V. Data type Extension(Complex) Extension URL http://fhir.de/StructureDefinition/Aufnahmegrund Constraints 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
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
ErsteUndZweiteStelle	S I	0..1	Extension	Element id Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle Short description Aufnahmegrund: 1. & 2. Stelle 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 und 2. Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V. Data type Extension Constraints 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
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..0	Extension	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.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 uri Fixed value ErsteUndZweiteStelle Mappings rim: N/A
value[x]		0..1	Binding	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.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). Binding AufnahmegrundErsteUndZweiteStelleVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
valueCoding			Coding	There are no (further) constraints on this element Data type Coding
DritteStelle	S I	0..1	Extension	Element id Encounter.extension:Aufnahmegrund.extension:DritteStelle Short description Aufnahmegrund: 3. Stelle 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 Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V. Data type Extension Constraints 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
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:DritteStelle.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..0	Extension	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:DritteStelle.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:DritteStelle.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 uri Fixed value DritteStelle Mappings rim: N/A
value[x]		0..1	Binding	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:DritteStelle.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). Binding AufnahmegrundDritteStelleVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
valueCoding			Coding	There are no (further) constraints on this element Data type Coding
VierteStelle	S I	0..1	Extension	Element id Encounter.extension:Aufnahmegrund.extension:VierteStelle Short description Aufnahmegrund: 4. Stelle 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 Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V. Data type Extension Constraints 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
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:VierteStelle.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..0	Extension	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:VierteStelle.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:VierteStelle.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 uri Fixed value VierteStelle Mappings rim: N/A
value[x]		0..1	Binding	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.extension:VierteStelle.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). Binding AufnahmegrundVierteStelleVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
valueCoding			Coding	There are no (further) constraints on this element Data type Coding
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.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 uri Fixed value http://fhir.de/StructureDefinition/Aufnahmegrund Mappings rim: N/A
value[x]		0..0		There are no (further) constraints on this element Element id Encounter.extension:Aufnahmegrund.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). Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
plannedStartDate	S I	0..1	Extension(dateTime)	Element id Encounter.extension:plannedStartDate Short description geplantes Aufnahmedatum Alternate names extensions, user content Definition 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. Data type Extension(dateTime) Extension URL http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate Constraints 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
plannedEndDate	S I	0..1	Extension(dateTime)	Element id Encounter.extension:plannedEndDate Short description geplantes Entlassdatum Alternate names extensions, user content Definition 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. Data type Extension(dateTime) Extension URL http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedEndDate Constraints 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
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
identifier	S Σ	1..*	Identifier	Element id Encounter.identifier Short description Identifier(s) by which this encounter is known Definition Identifier(s) by which this encounter is known. Data type Identifier Sliced: Unordered, Open, by $this(Pattern) Constraints 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] servd: Identifier workflow: Event.identifier w5: FiveWs.identifier v2: PV1-19 rim: .id
Aufnahmenummer	S Σ	0..1	IdentifierPattern	Element id Encounter.identifier:Aufnahmenummer Short description Identifier(s) by which this encounter is known Definition Identifier(s) by which this encounter is known. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "type": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } ] } } 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] servd: Identifier workflow: Event.identifier w5: FiveWs.identifier v2: PV1-19 rim: .id
id		0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.use Short description usual \| official \| temp \| secondary \| old (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Constraints 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: Role.code or implied by context
type	S Σ	1..1	CodeableConceptBindingPattern	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
id		0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	S Σ	1..*	CodingPattern	Element id Encounter.identifier:Aufnahmenummer.type.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Sliced: Unordered, Open, by $this(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
vn-type	S Σ	1..1	CodingPattern	Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type Short description Codierte Darstellung des Identifier-Typs Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/v2-0203` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://terminology.hl7.org/CodeSystem/v2-0203 Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	codePattern	Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Hier ist stets der Wert `VN` anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern VN Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.coding:vn-type.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.type.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
system	S Σ	0..1	uri	Element id Encounter.identifier:Aufnahmenummer.system Short description Namensraum des Identifiers Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	Element id Encounter.identifier:Aufnahmenummer.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.identifier:Aufnahmenummer.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(Organization) Constraints 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) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
status	S Σ ?!	1..1	codeBinding	Element id Encounter.status Short description Status Definition planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled +. Comments Zeigt den aktuellen Status der Ressource an. WICHTIGER Hinweis für Implementierer: Alle server-seitigen Implementierungen MÜSSEN in der Lage sein, die systemintern möglichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `in-progress`, `finished` und `cancelled`. Alle client-seitigen Implementierungen MÜSSEN in der Lage sein, sämtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu können, beispielsweise durch Ausblenden/Durchstreichen von Ressourcen mit dem status `entered-in-error` und Ausgrauen von Ressourcen, die einen Plan- oder Entwurfs-Status haben. Historie: Die Reduktion der zulässigen Status-Werte im Vergleich zur FHIR-Kernspezifikation erfolgt im Vorgriff auf eine entsprechende Anpassung in FHIR R5. Data type code Binding Eingeschränkter Status vgl. FHIR R5 EncounterStatusDe (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.status w5: FiveWs.status v2: No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16 rim: .statusCode
statusHistory		0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.statusHistory Short description List of past encounter statuses Definition The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. Comments The current status is always found in the current version of the resource, not the status history. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.statusHistory.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.statusHistory.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.statusHistory.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
status		1..1	codeBinding	There are no (further) constraints on this element Element id Encounter.statusHistory.status Short description planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled + Definition planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled +. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type code Binding Current state of the encounter. EncounterStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
period	I	1..1	Period	There are no (further) constraints on this element Element id Encounter.statusHistory.period Short description The time that the episode was in the specified status Definition The time that the episode was in the specified status. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"]
class	S Σ	1..1	CodingBinding	Element id Encounter.class Short description Fallart Definition Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. Comments Die Klassifikation von Encountern nach Fallarten folgt den internationalen Vorgaben und dient der groben Unterscheidung von Besuchen mit und ohne Bettendisposition (ambulant/stationär). Die in Deutschland übliche Fallklassifikation anhand von unterschiedlichen regulatorischen und abrechnungrelevanten Rahmenbedingungen, erfolgt in `type`. Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `class` siehe Deutsche Basisprofile Data type Coding Binding Classification of the encounter. EncounterClassDE (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding w5: FiveWs.class v2: PV1-2 rim: .inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
classHistory		0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.classHistory Short description List of past encounter classes Definition The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
class		1..1	CodingBinding	There are no (further) constraints on this element Element id Encounter.classHistory.class Short description inpatient \| outpatient \| ambulatory \| emergency + Definition inpatient \| outpatient \| ambulatory \| emergency +. Comments Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Data type Coding Binding Classification of the encounter. v3.ActEncounterCode (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding
period	I	1..1	Period	There are no (further) constraints on this element Element id Encounter.classHistory.period Short description The time that the episode was in the specified class Definition The time that the episode was in the specified class. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"]
type	S Σ	1..*	CodeableConcept	Element id Encounter.type Short description Specific type of encounter Definition Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Comments Since there are many ways to further classify encounters, this element is 0... Data type* CodeableConcept Sliced: Unordered, Open, by $this(Pattern) Binding The type of encounter. EncounterType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code w5: FiveWs.class v2: PV1-4 / PV1-18 rim: .code
Kontaktebene	S Σ	1..1	CodeableConceptBindingPattern	Element id Encounter.type:Kontaktebene Short description Kontaktebene Definition Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Comments Begründung Pflichtfeld: Die Abteilungsebene muss aus Kompatibilitätsgründen angegeben werden. `Hinweis bei Abbildung von Versorgungsstellenkontakten:` Es ist ein üblicher Fall, dass die Dauer eines Versorgungsstellenkontaktes in der Versorgung die eines Abteilungskontaktes übersteigt. Ein Beispiel hierfür: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose über eine Fachabteilung (Onkologie) läuft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird. Für einen solchen Fall gilt auf Ebene der FHIR-Instanzen (z.B. entgegen des tatsächliche Aufenthaltes im gleichen Bett): Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN NICHT in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen. Hintergrund: Das Konzept der 'Kontaktebene' stammt aus dem Fallmodell der Medizininformatik-Initiative, das bei Encountern zwischen 'Einrichtungskontakten', 'Fachabteilungskontakten' und 'Versorgungsstellenkontakten' unterscheidet. Im Kontext dieses Moduls werden lediglich Encounter der Ebene 'Fachabteilungskontakt' abgebildet. Data type CodeableConcept Binding Kontaktebene KontaktebeneDe (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://fhir.de/CodeSystem/Kontaktebene", "code": "abteilungskontakt" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code w5: FiveWs.class v2: PV1-4 / PV1-18 rim: .code
id		0..1	string	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	Σ	0..*	CodingPattern	Element id Encounter.type:Kontaktebene.coding Short description Codierte Darstellung der Kontaktebene Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://fhir.de/CodeSystem/Kontaktebene", "code": "abteilungskontakt" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.coding.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.type:Kontaktebene.coding.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://fhir.de/CodeSystem/Kontaktebene` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://fhir.de/CodeSystem/Kontaktebene Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	codePattern	Element id Encounter.type:Kontaktebene.coding.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Hier ist stets der Wert `abteilungskontakt` anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern abteilungskontakt Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:Kontaktebene.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
KontaktArt	S Σ	0..1	CodeableConceptBindingPattern	Element id Encounter.type:KontaktArt Short description Kontaktart Definition Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Comments Die Kontaktart dient der feingranularen Differenzierung unterschiedlicher stationärer und ambulanter Fallarten gemäß der in Deutschland üblichen regulatorischen und abrechnungsrelevanten Rahmenbedingungen. Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `type` siehe Deutsche Basisprofile Data type CodeableConcept Binding The type of encounter. KontaktartDe (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://fhir.de/CodeSystem/kontaktart-de" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code w5: FiveWs.class v2: PV1-4 / PV1-18 rim: .code
id		0..1	string	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	Σ	0..*	CodingPattern	Element id Encounter.type:KontaktArt.coding Short description Codierte Darstellung der Kontaktart Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://fhir.de/CodeSystem/kontaktart-de" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.coding.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.type:KontaktArt.coding.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://fhir.de/CodeSystem/kontaktart-de` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://fhir.de/CodeSystem/kontaktart-de Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	code	Element id Encounter.type:KontaktArt.coding.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments vorstationaer \| nachstationaer \| begleitperson \| tagesklinik \| + Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.type:KontaktArt.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
serviceType	S Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.serviceType Short description Specific type of service Definition Broad categorization of the service that is to be provided (e.g. cardiology). 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. Data type CodeableConcept Binding Broad categorization of the service that is to be provided. ServiceType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.code v2: PV1-10
id		0..1	string	There are no (further) constraints on this element Element id Encounter.serviceType.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.serviceType.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	S Σ	1..*	Coding	Element id Encounter.serviceType.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Sliced: Unordered, Open, by $this(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Fachabteilungsschluessel	S Σ	0..1	CodingBindingPattern	Element id Encounter.serviceType.coding:Fachabteilungsschluessel Short description Fachabteilungsschlüssel Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Fachabteilungen gemäß Anhang 1 der BPflV Data type Coding Binding FachabteilungsschluesselVS (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
ErweiterterFachabteilungsschluessel	S Σ	0..1	CodingBindingPattern	Element id Encounter.serviceType.coding:ErweiterterFachabteilungsschluessel Short description Fachabteilungsschlüssel Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Fachabteilungen gemäß Anhang 1 der BPflV inkl. Spezialisierungen Data type Coding Binding ValueSetFachabteilungsschluesselErweitert (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel-erweitert" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.serviceType.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
priority		0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.priority Short description Indicates the urgency of the encounter Definition Indicates the urgency of the encounter. 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. Data type CodeableConcept Binding Indicates the urgency of the encounter. v3.ActPriority (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.grade v2: PV2-25 rim: .priorityCode
subject	S Σ I	1..1	Reference(Patient \| Group)	Element id Encounter.subject Short description Patientenbezug Alternate names patient Definition The patient or group present at the encounter. Comments While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked). Data type Reference(Patient \| Group) Constraints 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) workflow: Event.subject w5: FiveWs.subject[x] v2: PID-3 rim: .participation[typeCode=SBJ]/role[classCode=PAT] w5: FiveWs.subject
id		0..1	string	There are no (further) constraints on this element Element id Encounter.subject.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.subject.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	1..1	string	Element id Encounter.subject.reference Short description Patienten-Link 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 Begründung Pflichtfeld: Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.subject.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Encounter.subject.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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.subject.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
episodeOfCare	Σ I	0..*	Reference(EpisodeOfCare)	There are no (further) constraints on this element Element id Encounter.episodeOfCare Short description Episode(s) of care that this encounter should be recorded against Definition Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). 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. Data type Reference(EpisodeOfCare) Constraints 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) workflow: Event.context w5: FiveWs.context v2: PV1-54, PV1-53
basedOn	I	0..*	Reference(ServiceRequest)	There are no (further) constraints on this element Element id Encounter.basedOn Short description The ServiceRequest that initiated this encounter Alternate names incomingReferral Definition The request this encounter satisfies (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. Data type Reference(ServiceRequest) Constraints 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) workflow: Event.basedOn rim: .reason.ClinicalDocument
participant	Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.participant Short description List of participants involved in the encounter Definition The list of people responsible for providing the service. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Event.performer v2: ROL rim: .participation[typeCode=PFM]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.participant.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
type	Σ	0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.participant.type Short description Role of participant in encounter Definition Role of participant in encounter. Comments The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc. Data type CodeableConcept Binding Role of participant in encounter. ParticipantType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.performer.function v2: ROL-3 (or maybe PRT-4) rim: .functionCode
period	I	0..1	Period	There are no (further) constraints on this element Element id Encounter.participant.period Short description Period of time during the encounter that the participant participated Definition The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: ROL-5, ROL-6 (or maybe PRT-5) rim: .time
individual	Σ I	0..1	Reference(Practitioner \| PractitionerRole \| RelatedPerson)	There are no (further) constraints on this element Element id Encounter.participant.individual Short description Persons involved in the encounter other than the patient Definition Persons involved in the encounter other than the patient. 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. Data type Reference(Practitioner \| PractitionerRole \| RelatedPerson) Constraints 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) workflow: Event.performer.actor w5: FiveWs.who v2: ROL-4 rim: .role
appointment	Σ I	0..*	Reference(Appointment)	There are no (further) constraints on this element Element id Encounter.appointment Short description The appointment that scheduled this encounter Definition The appointment that scheduled this encounter. 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. Data type Reference(Appointment) Constraints 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) workflow: Event.basedOn v2: SCH-1 / SCH-2 rim: .outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
period	S I	0..1	Period	Element id Encounter.period Short description Aufenthaltszeitraum Definition The start and end time of the encounter. Comments WICHTIGER Hinweis für Implementierer: Das Aufnahmedatum MUSS angegeben werden, wenn der `status` des Encounters impliziert, dass dieser bereits begonnen hat. Das Entlassdatum MUSS angegeben werden, wenn der `status` des Encounters impliziert, dass dieser beendet ist. Siehe hierzu die Übersicht der Invarianten in diesem Profil. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] workflow: Event.occurrence[x] w5: FiveWs.done[x] v2: PV1-44, PV1-45 rim: .effectiveTime (low & high)
id		0..1	string	There are no (further) constraints on this element Element id Encounter.period.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.period.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
start	S Σ I	0..1	dateTime	Element id Encounter.period.start Short description Aufnahmedatum Definition The start of the period. The boundary is inclusive. Comments Hier ist stets das tatsächliche Aufnahmedatum anzugeben. Geplante Aufnahmedaten müssen über die Extension `plannedStartDate` erfasst werden. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: DR.1 rim: ./low
end	S Σ I	0..1	dateTime	Element id Encounter.period.end Short description Entlassdatum Definition The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. Comments Hier ist stets das tatsächliche Entlassdatum anzugeben. Geplante Entlassdaten müssen über die Extension `plannedEndDate` erfasst werden. Meaning when missing If the end of the period is missing, it means that the period is ongoing Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: DR.2 rim: ./high
length	I	0..1	Duration	There are no (further) constraints on this element Element id Encounter.length Short description Quantity of time the encounter lasted (less time absent) Definition Quantity of time the encounter lasted. This excludes the time during leaves of absence. Comments May differ from the time the Encounter.period lasted because of leave of absence. Data type Duration Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` qty-3: If a code for the unit is present, the system SHALL also be present `code.empty() or system.exists()` drt-1: There SHALL be a code if there is a value and it SHALL be an expression of time. If system is present, it SHALL be UCUM. `code.exists() implies ((system = %ucum) and value.exists())` Mappings rim: n/a v2: SN (see also Range) or CQ rim: PQ, IVL<PQ>, MO, CO, depending on the values rim: PQ, IVL<PQ> depending on the values workflow: Event.occurrence[x] v2: (PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes rim: .lengthOfStayQuantity
reasonCode	Σ	0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.reasonCode Short description Coded reason the encounter takes place Alternate names Indication, Admission diagnosis Definition Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. Comments For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). Data type CodeableConcept Binding Reason why the encounter takes place. EncounterReasonCodes (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Event.reasonCode w5: FiveWs.why[x] v2: EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations ) rim: .reasonCode
reasonReference	Σ I	0..*	Reference(Condition \| Procedure \| Observation \| ImmunizationRecommendation)	There are no (further) constraints on this element Element id Encounter.reasonReference Short description Reason the encounter takes place (reference) Alternate names Indication, Admission diagnosis Definition Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. Comments For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). Data type Reference(Condition \| Procedure \| Observation \| ImmunizationRecommendation) Constraints 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) workflow: Event.reasonCode w5: FiveWs.why[x] v2: EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations ) rim: .reasonCode
diagnosis	Σ	0..*	BackboneElement	Element id Encounter.diagnosis Short description Falldiagnosen/-prozeduren Definition The list of diagnosis relevant to this encounter. Comments Verweis auf Diagnosen/Prozeduren, die eine besondere Rolle im Kontext eines Encounters einnehmen, z.B. "Aufnahmediagnose" WICHTIGER Hinweis für Implementierer: Der Fallbezug von Diagnosen und Prozeduren wird über das jeweilige `encounter`-Element der Condition bzw. Procedure-Ressource hinreichend etabliert. Die zusätzliche Rückverlinkung von `Encounter.diagnosis` auf Condition/Procedure wird nur dann verwendet, wenn einer Diagnose bzw. Prozedur im Kontext eines Aufenthaltes eine besondere Rolle zugewiesen werden soll, z.B. Haupt-/Neben-/Aufnahme- oder Überweisungsdiagnose). Hier werden Diagnosen und Prozeduren nur nach ihrer medizinschen Relevanz bezüglich eines Aufenthaltes qualifiziert. Die Qualifikation von Diagnosen und Prozeduren im Kontext der Abrechnung erfolgt in der `Account`-Ressource! Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .outboundRelationship[typeCode=RSON]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
condition	S Σ I	1..1	Reference(Condition \| Procedure)	Element id Encounter.diagnosis.condition Short description Verweis auf Diagnose/Prozedur Alternate names Admission diagnosis, discharge diagnosis, indication Definition Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. Comments For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). Data type Reference(Condition \| Procedure) Constraints 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) workflow: Event.reasonReference w5: FiveWs.why[x] v2: Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively. rim: .outboundRelationship[typeCode=RSON].target
id		0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.condition.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.condition.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	1..1	string	Element id Encounter.diagnosis.condition.reference Short description Condition/Procedure-Link 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 Begründung Pflichtfeld: Die Verlinkung auf die Condition/Procedure-Ressource dient der technischen Zuordnung des Encounters zur Condition/Precedure und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.diagnosis.condition.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Encounter.diagnosis.condition.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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.condition.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
use	S	1..1	CodeableConceptBinding	Element id Encounter.diagnosis.use Short description Bedeutung der Diagnose/Prozedur Definition Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). Comments Bedeutung der Diagnose/Prozedur im Encounter-Kontext Data type CodeableConcept Binding The type of diagnosis this condition represents. DiagnosisRole (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
id		0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.use.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.use.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	S Σ	1..*	Coding	Element id Encounter.diagnosis.use.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Sliced: Unordered, Open, by $this(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Diagnosetyp	S Σ	1..1	CodingBinding	Element id Encounter.diagnosis.use.coding:Diagnosetyp Short description Diagnosetyp Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments International standardisierte, grobgranulare Unterscheidung zwischen extern gestellten Diagnosen (`referral-diagnosis`) und intern gestellten Diagnosen (`treatment-diagnosis`) Data type Coding Binding DiagnoseTyp (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
DiagnosesubTyp	S Σ	0..*	CodingBinding	Element id Encounter.diagnosis.use.coding:DiagnosesubTyp Short description Diagnosesubtyp Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments An deutschen Kodierrichtlinien orientierte, feingranulare Unterscheidung von Diagnose-Rollen, z.B. "Fachabteilungshauptdiagnose", "Todesursache" etc. Data type Coding Binding Diagnosesubtyp (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.use.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
rank	S	0..1	positiveInt	There are no (further) constraints on this element Element id Encounter.diagnosis.rank Short description Ranking of the diagnosis (for each role type) Definition Ranking of the diagnosis (for each role type). Comments 32 bit number; for values larger than this, use decimal Data type positiveInt Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .outboundRelationship[typeCode=RSON].priority
account	S I	0..*	Reference(Account)	Element id Encounter.account Short description Abrechnungskontext Definition The set of accounts that may be used for billing for this Encounter. Comments Der Bezug zu einem Account stellt den Abrechnungskontext für einen oder mehrere Encounter her. Mittels der Account-Referenz können zum Beispiel ein vorstationärer, ein stationärer und ein nachstationärer Besuch zu einem 'DRG-Fall' zusammengefasst werden. WICHTIGER Hinweis für Implementierer: Im Deutschen Sprachgebrauch ist unter dem Begriff 'Fall' meist der Abrechnungskontext gemeint, nicht der einzelne Besuch. Die 'Fallnummer' ist daher nicht der Identifier des Encounters, sondern der des Accounts auf den der Encounter referenziert. Auf diesem Wege können mehrere Besuche einer Fallnummer zugeordnet werden. Da die Fallnummer ein häufig verwendetes Suchkriterium darstellt, ist diese hier als logische Referenz (`account.identifier`) zu hinterlegen. Damit wird sichergestellt, dass diese als Suchparameter für die Suche nach Encountern zur Verfügung steht, auch wenn einzelne Systeme kein Chaining unterstützen oder einzelne Benutzer keine Sichtberechtigung auf Abrechnungsdaten haben, im Versorgunskontext aber dennoch Encounter anhand der assoziierten Fallnummer suchen möchten. Data type Reference(Account) Constraints 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) rim: .pertains.A_Account
id		0..1	string	There are no (further) constraints on this element Element id Encounter.account.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.account.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	0..1	string	Element id Encounter.account.reference Short description Account-Link 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 Begründung MS: Die Verlinkung auf eine Account-Ressource dient der technischen Zuordnung des Besuchs zu einem Abrechnungskontext und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.account.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	S Σ	1..1	Identifier	Element id Encounter.account.identifier Short description (Abrechnungs-)Fallnummer 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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.account.identifier.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.account.identifier.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.account.identifier.use Short description usual \| official \| temp \| secondary \| old (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Constraints 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: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.account.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	S Σ	1..1	uri	Element id Encounter.account.identifier.system Short description Namensraum des Identifiers Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	1..1	string	Element id Encounter.account.identifier.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id Encounter.account.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.account.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(Organization) Constraints 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) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.account.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
hospitalization	S	0..1	BackboneElement	Element id Encounter.hospitalization Short description Details zum Aufenthalt Definition Details about the admission to a healthcare service. Comments Details zu einem stationären Aufenthalt Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .outboundRelationship[typeCode=COMP].target[classCode=ENC, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.hospitalization.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.hospitalization.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
Wahlleistung	S I	0..*	Extension(Coding)	Element id Encounter.hospitalization.extension:Wahlleistung Short description Wahlleistung Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments Begründung MS: Vom Patienten gebuchte Wahlleistungen (z.B. Chefarztbehandlung, Einzelzimmer) sind häufig system- und abteilungsübergreifend zu beachten und sollten daher über die Schnittstelle kommuniziert werden können. Data type Extension(Coding) Extension URL http://fhir.de/StructureDefinition/Wahlleistung Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.hospitalization.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
preAdmissionIdentifier		0..1	Identifier	There are no (further) constraints on this element Element id Encounter.hospitalization.preAdmissionIdentifier Short description Pre-admission identifier Definition Pre-admission identifier. Data type Identifier Constraints 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] servd: Identifier v2: PV1-5 rim: .id
origin	I	0..1	Reference(Location \| Organization)	There are no (further) constraints on this element Element id Encounter.hospitalization.origin Short description The location/organization from which the patient came before admission Definition The location/organization from which the patient came before admission. 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. Data type Reference(Location \| Organization) Constraints 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) rim: .participation[typeCode=ORG].role
admitSource	S	0..1	CodeableConceptBinding	Element id Encounter.hospitalization.admitSource Short description Aufnahmeanlass Definition From where patient was admitted (physician referral, transfer). Comments Anlass der stationären Aufnahme, z.B. "Einweisung", "Notfall" etc. Begründung MS: Zur Harmonisierung den Festlegungen der Medizininformatik-Initiative Data type CodeableConcept Binding From where the patient was admitted. AufnahmeanlassVS (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-14 rim: .admissionReferralSourceCode
reAdmission		0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.hospitalization.reAdmission Short description The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission Definition Whether this hospitalization is a readmission and why if known. 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. Data type CodeableConcept Binding The reason for re-admission of this hospitalization encounter. v2.0092 (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-13
dietPreference		0..*	CodeableConcept	There are no (further) constraints on this element Element id Encounter.hospitalization.dietPreference Short description Diet preferences reported by the patient Definition Diet preferences reported by the patient. Requirements Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter. Comments For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). Data type CodeableConcept Binding Medical, cultural or ethical food preferences to help with catering requirements. Diet (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-38 rim: .outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
specialCourtesy		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.hospitalization.specialCourtesy Short description Special courtesies (VIP, board member) Definition Special courtesies (VIP, board member). 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. Data type CodeableConcept Binding Special courtesies. SpecialCourtesy (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-16 rim: .specialCourtesiesCode
specialArrangement		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.hospitalization.specialArrangement Short description Wheelchair, translator, stretcher, etc. Definition Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. 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. Data type CodeableConcept Binding Special arrangements. SpecialArrangements (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-15 / OBR-30 / OBR-43 rim: .specialArrangementCode
destination	I	0..1	Reference(Location \| Organization)	There are no (further) constraints on this element Element id Encounter.hospitalization.destination Short description Location/organization to which the patient is discharged Definition Location/organization to which the patient is discharged. 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. Data type Reference(Location \| Organization) Constraints 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) v2: PV1-37 rim: .participation[typeCode=DST]
dischargeDisposition	S	0..1	CodeableConcept	Element id Encounter.hospitalization.dischargeDisposition Short description Entlassungsart bzw. -grund Definition Category or kind of location after discharge. 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. Data type CodeableConcept Binding Discharge Disposition. DischargeDisposition (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: PV1-36 rim: .dischargeDispositionCode
id		0..1	string	There are no (further) constraints on this element Element id Encounter.hospitalization.dischargeDisposition.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.hospitalization.dischargeDisposition.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
Entlassungsgrund	S I	0..1	Extension(Complex)	Element id Encounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund Short description Entlassungsgrund Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments Entlassungsgrund nach § 301 Abs. 3 SGB V Einschränkung MS: Der Entlassungsgrund muss nur implementiert werden, wenn das bestätigungsrelevante System in der Akutversorgung eingesetzt wird. Data type Extension(Complex) Extension URL http://fhir.de/StructureDefinition/Entlassungsgrund Constraints 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
RehaEntlassung	S I	0..1	Extension(Complex)	Element id Encounter.hospitalization.dischargeDisposition.extension:RehaEntlassung Short description Entlassungsgrund Reha Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments Entlassungsgrund nach §301 (Abs. 4 und 4a) SGB V Einschränkung MS: Der Entlassungsgrund Reha muss nur implementiert werden, wenn das bestätigungsrelevante System in der Reha-Versorgung eingesetzt wird Data type Extension(Complex) Extension URL https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKRehaEntlassung Constraints 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
coding	Σ	0..*	Coding	There are no (further) constraints on this element Element id Encounter.hospitalization.dischargeDisposition.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.hospitalization.dischargeDisposition.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
location	S	0..*	BackboneElement	Element id Encounter.location Short description Aufenthaltsorte des Patienten Definition List of locations where the patient has been during this encounter. Comments Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". Data type BackboneElement Sliced: Unordered, Open, by physicalType(Pattern), status(Pattern) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .participation[typeCode=LOC]
(All Slices)				There are no (further) constraints on this element
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
location	I	1..1	Reference(Location)	There are no (further) constraints on this element Element id Encounter.location.location Short description Location the encounter takes place Definition The location where the encounter takes place. 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. Data type Reference(Location) Constraints 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) workflow: Event.location w5: FiveWs.where[x] v2: PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43 rim: .role
status		0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.location.status Short description planned \| active \| reserved \| completed Definition The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. Comments When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. Data type code Binding The status of the location. EncounterLocationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .role.statusCode
physicalType		0..1	CodeableConceptBinding	Element id Encounter.location.physicalType Short description The physical type of the location (usually the level in the location hierachy - bed room ward etc.) Definition This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. Comments This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario. Data type CodeableConcept Binding Physical form of the location. ISiKLocationPhysicalType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
period	I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location.period Short description Time period during which the patient was present at the location Definition Time period during which the patient was present at the location. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] rim: .time
Zimmer	S	0..1	BackboneElement	There are no (further) constraints on this element Element id Encounter.location:Zimmer Short description List of locations where the patient has been Definition List of locations where the patient has been during this encounter. Comments Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .participation[typeCode=LOC]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
location	S I	1..1	Reference(Location)	Element id Encounter.location:Zimmer.location Short description Aufenthaltsort Definition The location where the encounter takes place. 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. Data type Reference(Location) Constraints 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) workflow: Event.location w5: FiveWs.where[x] v2: PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43 rim: .role
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	0..1	string	Element id Encounter.location:Zimmer.location.reference Short description Location-Link 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 Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	S Σ	1..1	Identifier	Element id Encounter.location:Zimmer.location.identifier Short description Identifier des Aufenthaltsortes 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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.use Short description usual \| official \| temp \| secondary \| old (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Constraints 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: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	S Σ	0..1	uri	Element id Encounter.location:Zimmer.location.identifier.system Short description Namensraum des Identifiers Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	Element id Encounter.location:Zimmer.location.identifier.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.location:Zimmer.location.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(Organization) Constraints 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) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	S Σ	1..1	string	Element id Encounter.location:Zimmer.location.display Short description (Menschenlesbarer) Name des Aufenthaltsortes 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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
status	S	1..1	codeBindingPattern	Element id Encounter.location:Zimmer.status Short description planned \| active \| reserved \| completed Definition The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. Comments When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. Data type code Binding The status of the location. EncounterLocationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern active Mappings rim: n/a rim: .role.statusCode
physicalType	S	1..1	CodeableConceptPattern	Element id Encounter.location:Zimmer.physicalType Short description Art des Aufenthaltsortes (hier: Zimmer) Definition This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. Comments This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario. Data type CodeableConcept Binding Physical form of the location. LocationType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "ro" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	Σ	0..*	CodingPattern	Element id Encounter.location:Zimmer.physicalType.coding Short description Codierte Darstellung der Art des Aufenthaltortes Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "ro" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.coding.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.location:Zimmer.physicalType.coding.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://terminology.hl7.org/CodeSystem/location-physical-type Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	codePattern	Element id Encounter.location:Zimmer.physicalType.coding.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Hier ist stets der Wert `ro` anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern ro Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Zimmer.physicalType.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
period	I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Zimmer.period Short description Time period during which the patient was present at the location Definition Time period during which the patient was present at the location. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] rim: .time
Bettenstellplatz	S	0..1	BackboneElement	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz Short description List of locations where the patient has been Definition List of locations where the patient has been during this encounter. Comments Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .participation[typeCode=LOC]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
location	S I	1..1	Reference(Location)	Element id Encounter.location:Bettenstellplatz.location Short description Aufenthaltsort Definition The location where the encounter takes place. 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. Data type Reference(Location) Constraints 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) workflow: Event.location w5: FiveWs.where[x] v2: PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43 rim: .role
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	0..1	string	Element id Encounter.location:Bettenstellplatz.location.reference Short description Location-Link 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 Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	S Σ	1..1	Identifier	Element id Encounter.location:Bettenstellplatz.location.identifier Short description Identifier des Aufenthaltsortes 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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.use Short description usual \| official \| temp \| secondary \| old (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Constraints 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: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	S Σ	0..1	uri	Element id Encounter.location:Bettenstellplatz.location.identifier.system Short description Namensraum des Identifiers Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	Element id Encounter.location:Bettenstellplatz.location.identifier.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.location.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(Organization) Constraints 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) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	S Σ	1..1	string	Element id Encounter.location:Bettenstellplatz.location.display Short description (Menschenlesbarer) Name des Aufenthaltsortes 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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
status	S	1..1	codeBindingPattern	Element id Encounter.location:Bettenstellplatz.status Short description planned \| active \| reserved \| completed Definition The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. Comments When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. Data type code Binding The status of the location. EncounterLocationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern active Mappings rim: n/a rim: .role.statusCode
physicalType	S	1..1	CodeableConceptPattern	Element id Encounter.location:Bettenstellplatz.physicalType Short description Art des Aufenthaltsortes (hier: Bettenstellplatz) Definition This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. Comments Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType Data type CodeableConcept Binding Physical form of the location. LocationType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "bd" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	Σ	0..*	CodingPattern	Element id Encounter.location:Bettenstellplatz.physicalType.coding Short description Codierte Darstellung der Art des Aufenthaltortes Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "bd" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.coding.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.location:Bettenstellplatz.physicalType.coding.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://terminology.hl7.org/CodeSystem/location-physical-type Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	codePattern	Element id Encounter.location:Bettenstellplatz.physicalType.coding.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Hier ist stets der Wert `bd` anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern bd Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.physicalType.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
period	I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Bettenstellplatz.period Short description Time period during which the patient was present at the location Definition Time period during which the patient was present at the location. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] rim: .time
Station	S	0..1	BackboneElement	There are no (further) constraints on this element Element id Encounter.location:Station Short description List of locations where the patient has been Definition List of locations where the patient has been during this encounter. Comments Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: .participation[typeCode=LOC]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints 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
location	S I	1..1	Reference(Location)	Element id Encounter.location:Station.location Short description Aufenthaltsort Definition The location where the encounter takes place. Comments Begründung MS: die Kenntnis des aktuellen Aufenthaltsortes ist häufig systemübergreifend relevant (z.B. für Küchen- und Logistiksysteme) und sollte daher über die Schnittstelle kommuniziert werden können. Data type Reference(Location) Constraints 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) workflow: Event.location w5: FiveWs.where[x] v2: PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43 rim: .role
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.location.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.location.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	S Σ I	0..1	string	Element id Encounter.location:Station.location.reference Short description Location-Link 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 Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.location:Station.location.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	S Σ	1..1	Identifier	Element id Encounter.location:Station.location.identifier Short description Identifier des Aufenthaltsortes 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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.use Short description usual \| official \| temp \| secondary \| old (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Constraints 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: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	S Σ	0..1	uri	Element id Encounter.location:Station.location.identifier.system Short description Namensraum des Identifiers Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	Element id Encounter.location:Station.location.identifier.value Short description The value that is unique Definition The portion of the identifier typically relevant to the user and which is unique within the context of the system. Comments Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.location:Station.location.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(Organization) Constraints 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) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	S Σ	1..1	string	Element id Encounter.location:Station.location.display Short description (Menschenlesbarer) Name des Aufenthaltsortes 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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
status	S	1..1	codeBindingPattern	Element id Encounter.location:Station.status Short description planned \| active \| reserved \| completed Definition The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. Comments When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. Data type code Binding The status of the location. EncounterLocationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern active Mappings rim: n/a rim: .role.statusCode
physicalType	S	1..1	CodeableConceptPattern	Element id Encounter.location:Station.physicalType Short description Art des Aufenthaltsortes (hier: Station) Definition This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. Comments This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario. Data type CodeableConcept Binding Physical form of the location. LocationType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "wa" } ] } Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
coding	Σ	0..*	CodingPattern	Element id Encounter.location:Station.physicalType.coding Short description Codierte Darstellung der Art des Aufenthaltortes Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "wa" } Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.coding.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
system	S Σ	1..1	uriPattern	Element id Encounter.location:Station.physicalType.coding.system Short description Codier-Schema Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern http://terminology.hl7.org/CodeSystem/location-physical-type Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	1..1	codePattern	Element id Encounter.location:Station.physicalType.coding.code Short description Code Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Hier ist stets der Wert `wa` anzugeben. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Pattern wa Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.location:Station.physicalType.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
period	I	0..1	Period	There are no (further) constraints on this element Element id Encounter.location:Station.period Short description Time period during which the patient was present at the location Definition Time period during which the patient was present at the location. 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. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] rim: .time
serviceProvider	S I	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.serviceProvider Short description The organization (facility) responsible for this encounter Definition The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy. 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. Data type Reference(Organization) Constraints 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) workflow: Event.performer.actor v2: PL.6 & PL.1 rim: .particiaption[typeCode=PFM].role
id		0..1	string	There are no (further) constraints on this element Element id Encounter.serviceProvider.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Encounter.serviceProvider.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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
reference	Σ I	0..1	string	There are no (further) constraints on this element Element id Encounter.serviceProvider.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
type	Σ	0..1	uriBinding	There are no (further) constraints on this element Element id Encounter.serviceProvider.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. Data type uri Binding Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	S Σ	1..1	Identifier	There are no (further) constraints on this element Element id Encounter.serviceProvider.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). Data type Identifier Constraints 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] servd: Identifier rim: .identifier
display	S Σ	1..1	string	There are no (further) constraints on this element Element id Encounter.serviceProvider.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. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
partOf	I	0..1	Reference(Encounter)	There are no (further) constraints on this element Element id Encounter.partOf Short description Another Encounter this encounter is part of Definition Another Encounter of which this encounter is a part of (administratively or in time). Comments This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details. Data type Reference(Encounter) Constraints 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) workflow: Event.partOf rim: .inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="ISiKKontaktGesundheitseinrichtung" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
    <version value="4.0.1" />
    <name value="ISiKKontaktGesundheitseinrichtung" />
    <status value="active" />
    <experimental value="false" />
    <date value="2024-11-25" />
    <publisher value="gematik GmbH" />
    <description value="Dieses Profil erm&#246;glicht die Abbildung von Besuchen/Aufenthalten eines Patienten in einer Gesundheitseinrichtung.\n### Motivation\nInformationen &#252;ber die Besuche des Patienten entlang seines \nBehandlungspfades im Krankenhaus sind ein wichtiger Bestandteil \ndes einrichtungsinternen Datenaustausches. \nSie erm&#246;glichen die Unterscheidung von station&#228;ren und ambulanten \nsowie aufgenommenen und entlassenen Patienten. \nWeiterhin ist aus den Besuchsinformationen der aktuelle Aufenthaltsort \ndes Patienten (Fachabteilung, Station, Bettplatz) ermittelbar. \nKlinische Ressourcen werden in FHIR durch Verlinkung auf die \nEncounter-Ressource in einen Kontext zum Besuch gestellt. \nDieser Kontext ist wichtig f&#252;r die Steuerung von Zugriffsberechtigungen \nund Abrechnungsprozessen.  \n\nZu Beginn der meisten klinischen Workflows steht die Auswahl \ndes Besuchskontextes. \nDies geschieht bspw. durch das Suchen der Encounter-Ressource \nanhand von Eigenschaften wie Aufnahmenummer, Fallart oder Aufnahmedatum. \nDaraufhin werden die zutreffenden Suchergebnisse angezeigt \nund der gew&#252;nschte Besuch ausgew&#228;hlt.\n\nIn FHIR werden Besuche, Aufenthalte, aber auch virtuelle Kontakte mit der `Encounter`-Ressource repr&#228;sentiert.\n\nWeitere Hinweise zu den Abgrenzungen der Begrifflichkeiten Fall und Kontakt finden sie unter {{pagelink: Fall, text: Fall-Begriff in ISiK}}\n\n### Kompatibilit&#228;t\nF&#252;r das Profil ISiKKontaktGesundheitseinrichtung wird eine Kompatibilit&#228;t \nmit folgenden Profilen angestrebt; \nallerdings kann nicht sichergestellt werden, dass Instanzen, \ndie gegen ISiKKontaktGesundheitseinrichtung valide sind, \nauch valide sind gegen:\n\n* Profil [Kontakt mit einer Gesundheitseinrichtung \nder Medizininformatik-Initiative](https://www.medizininformatik-initiative.de/fhir/core/modul-fall/StructureDefinition/KontaktGesundheitseinrichtung)\n\nHinweise zu Inkompatibilit&#228;ten k&#246;nnen &#252;ber die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Encounter" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Encounter" />
    <derivation value="constraint" />
    <differential>
        <element id="Encounter">
            <path value="Encounter" />
            <constraint>
                <key value="ISiK-enc-1" />
                <severity value="error" />
                <human value="Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben" />
                <expression value="status = &#39;finished&#39; and class = &#39;AMB&#39; implies period.start.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-2" />
                <severity value="error" />
                <human value="Abgeschlossene, station&#228;re Kontakte sollten einen Start- und End-Zeitpunkt angeben" />
                <expression value="status = &#39;finished&#39; and class = &#39;IMP&#39; implies period.start.exists() and period.end.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-3" />
                <severity value="error" />
                <human value="Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben" />
                <expression value="status = &#39;planned&#39; implies period.exists().not()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-4" />
                <severity value="warning" />
                <human value="Geplante Kontakte sollten die Extensions f&#252;r den geplanten Start- oder End-Zeitpunkt verwenden" />
                <expression value="status = &#39;planned&#39; implies extension.where(url = &#39;http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate&#39;).exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-5" />
                <severity value="error" />
                <human value="In-Durchf&#252;hrung befindliche Kontakte sollten einen Start-Zeitpunkt angeben" />
                <expression value="status = &#39;in-progress&#39; implies period.start.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-6" />
                <severity value="error" />
                <human value="Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben" />
                <expression value="status = &#39;onleave&#39; implies period.start.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-7" />
                <severity value="warning" />
                <human value="Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben" />
                <expression value="status = &#39;unknown&#39; implies period.start.exists()" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
            <constraint>
                <key value="ISiK-enc-8" />
                <severity value="error" />
                <human value="Die Rolle der assoziierten Diagnose(n) darf nicht &#39;Billing&#39; sein" />
                <expression value="diagnosis.use.all(coding.code != &#39;billing&#39;)" />
                <source value="https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung" />
            </constraint>
        </element>
        <element id="Encounter.extension">
            <path value="Encounter.extension" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:Aufnahmegrund">
            <path value="Encounter.extension" />
            <sliceName value="Aufnahmegrund" />
            <short value="Aufnahmegrund" />
            <comment value="Aufnahmegrund nach &#167; 301 Abs. 3 SGB V." />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="http://fhir.de/StructureDefinition/Aufnahmegrund" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle">
            <path value="Encounter.extension.extension" />
            <sliceName value="ErsteUndZweiteStelle" />
            <short value="Aufnahmegrund: 1. &amp; 2. Stelle" />
            <comment value="1. und 2. Stelle des Aufnahmegrunds nach &#167; 301 Abs. 3 SGB V." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:Aufnahmegrund.extension:DritteStelle">
            <path value="Encounter.extension.extension" />
            <sliceName value="DritteStelle" />
            <short value="Aufnahmegrund: 3. Stelle" />
            <comment value="3. Stelle des Aufnahmegrunds nach &#167; 301 Abs. 3 SGB V." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:Aufnahmegrund.extension:VierteStelle">
            <path value="Encounter.extension.extension" />
            <sliceName value="VierteStelle" />
            <short value="Aufnahmegrund: 4. Stelle" />
            <comment value="4. Stelle des Aufnahmegrunds nach &#167; 301 Abs. 3 SGB V." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:plannedStartDate">
            <path value="Encounter.extension" />
            <sliceName value="plannedStartDate" />
            <short value="geplantes Aufnahmedatum" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.extension:plannedEndDate">
            <path value="Encounter.extension" />
            <sliceName value="plannedEndDate" />
            <short value="geplantes Entlassdatum" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedEndDate" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier">
            <path value="Encounter.identifier" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="$this" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer">
            <path value="Encounter.identifier" />
            <sliceName value="Aufnahmenummer" />
            <min value="0" />
            <max value="1" />
            <patternIdentifier>
                <type>
                    <coding>
                        <system value="http://terminology.hl7.org/CodeSystem/v2-0203" />
                        <code value="VN" />
                    </coding>
                </type>
            </patternIdentifier>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.type">
            <path value="Encounter.identifier.type" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.type.coding">
            <path value="Encounter.identifier.type.coding" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="$this" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.type.coding:vn-type">
            <path value="Encounter.identifier.type.coding" />
            <sliceName value="vn-type" />
            <short value="Codierte Darstellung des Identifier-Typs" />
            <min value="1" />
            <max value="1" />
            <patternCoding>
                <system value="http://terminology.hl7.org/CodeSystem/v2-0203" />
                <code value="VN" />
            </patternCoding>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.type.coding:vn-type.system">
            <path value="Encounter.identifier.type.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/v2-0203` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.type.coding:vn-type.code">
            <path value="Encounter.identifier.type.coding.code" />
            <short value="Code" />
            <comment value="Hier ist stets der Wert `VN` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.system">
            <path value="Encounter.identifier.system" />
            <short value="Namensraum des Identifiers" />
            <comment value="Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n    aus dem der Identifier stammt. \n    Hinweise zur Festlegung der URLs f&#252;r lokale Namensr&#228;ume sind in den \n    [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n    **Begr&#252;ndung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.identifier:Aufnahmenummer.value">
            <path value="Encounter.identifier.value" />
            <comment value="Enth&#228;lt den eigentlichen Wert des Identifiers.  \n    **Begr&#252;ndung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.status">
            <path value="Encounter.status" />
            <short value="Status" />
            <comment value="Zeigt den aktuellen Status der Ressource an.     \n  **WICHTIGER Hinweis f&#252;r Implementierer:**    \n  * Alle server-seitigen Implementierungen M&#220;SSEN in der Lage sein, \n  die systemintern m&#246;glichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `in-progress`, `finished` und `cancelled`.\n  * Alle client-seitigen Implementierungen M&#220;SSEN in der Lage sein, s&#228;mtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu k&#246;nnen, \n  beispielsweise durch Ausblenden/Durchstreichen von Ressourcen mit dem status `entered-in-error` und Ausgrauen von Ressourcen, die einen Plan- oder Entwurfs-Status haben.  \n  **Historie:** Die Reduktion der zul&#228;ssigen Status-Werte im Vergleich zur FHIR-Kernspezifikation \n  erfolgt im Vorgriff auf eine entsprechende Anpassung in FHIR R5." />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <description value="Eingeschr&#228;nkter Status vgl. FHIR R5" />
                <valueSet value="http://fhir.de/ValueSet/EncounterStatusDe" />
            </binding>
        </element>
        <element id="Encounter.class">
            <path value="Encounter.class" />
            <short value="Fallart" />
            <comment value="Die Klassifikation von Encountern nach Fallarten folgt den internationalen Vorgaben und \n  dient der groben Unterscheidung von Besuchen mit und ohne Bettendisposition (ambulant/station&#228;r). \n  Die in Deutschland &#252;bliche Fallklassifikation anhand von unterschiedlichen \n  regulatorischen und abrechnungrelevanten Rahmenbedingungen, erfolgt in `type`.  \n  F&#252;r ein korrektes Mapping der in Deutschland gebr&#228;uchlichen Fallarten auf `class` siehe [Deutsche Basisprofile](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Ressourcen-AmbulanterStationaererFall?version=current)" />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/EncounterClassDE" />
            </binding>
        </element>
        <element id="Encounter.type">
            <path value="Encounter.type" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="$this" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.type:Kontaktebene">
            <path value="Encounter.type" />
            <sliceName value="Kontaktebene" />
            <short value="Kontaktebene" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Die Abteilungsebene muss aus Kompatibilit&#228;tsgr&#252;nden angegeben werden.\n  \n    **Hinweis bei Abbildung von Versorgungsstellenkontakten:**\n  Es ist ein &#252;blicher Fall, dass die Dauer eines Versorgungsstellenkontaktes in der Versorgung die eines Abteilungskontaktes &#252;bersteigt. Ein Beispiel hierf&#252;r: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose &#252;ber eine Fachabteilung (Onkologie) l&#228;uft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird.\n  F&#252;r einen solchen Fall gilt auf Ebene der FHIR-Instanzen (z.B. entgegen des tats&#228;chliche Aufenthaltes im gleichen Bett): Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN NICHT in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen.\n\n  Hintergrund: Das Konzept der &#39;Kontaktebene&#39; stammt aus dem Fallmodell der Medizininformatik-Initiative, \n    das bei Encountern zwischen &#39;Einrichtungskontakten&#39;, &#39;Fachabteilungskontakten&#39; und &#39;Versorgungsstellenkontakten&#39; unterscheidet.\n    Im Kontext dieses Moduls werden lediglich Encounter der Ebene &#39;Fachabteilungskontakt&#39; abgebildet." />
            <min value="1" />
            <max value="1" />
            <patternCodeableConcept>
                <coding>
                    <system value="http://fhir.de/CodeSystem/Kontaktebene" />
                    <code value="abteilungskontakt" />
                </coding>
            </patternCodeableConcept>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <description value="Kontaktebene" />
                <valueSet value="http://fhir.de/ValueSet/kontaktebene-de" />
            </binding>
        </element>
        <element id="Encounter.type:Kontaktebene.coding">
            <path value="Encounter.type.coding" />
            <short value="Codierte Darstellung der Kontaktebene" />
        </element>
        <element id="Encounter.type:Kontaktebene.coding.system">
            <path value="Encounter.type.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://fhir.de/CodeSystem/Kontaktebene` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.type:Kontaktebene.coding.code">
            <path value="Encounter.type.coding.code" />
            <short value="Code" />
            <comment value="Hier ist stets der Wert `abteilungskontakt` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.type:KontaktArt">
            <path value="Encounter.type" />
            <sliceName value="KontaktArt" />
            <short value="Kontaktart" />
            <comment value="Die Kontaktart dient der feingranularen Differenzierung unterschiedlicher station&#228;rer \n  und ambulanter Fallarten gem&#228;&#223; der in Deutschland &#252;blichen regulatorischen \n  und abrechnungsrelevanten Rahmenbedingungen.  \n  F&#252;r ein korrektes Mapping der in Deutschland gebr&#228;uchlichen Fallarten auf `type` siehe [Deutsche Basisprofile](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Ressourcen-AmbulanterStationaererFall?version=current)" />
            <min value="0" />
            <max value="1" />
            <patternCodeableConcept>
                <coding>
                    <system value="http://fhir.de/CodeSystem/kontaktart-de" />
                </coding>
            </patternCodeableConcept>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/kontaktart-de" />
            </binding>
        </element>
        <element id="Encounter.type:KontaktArt.coding">
            <path value="Encounter.type.coding" />
            <short value="Codierte Darstellung der Kontaktart" />
        </element>
        <element id="Encounter.type:KontaktArt.coding.system">
            <path value="Encounter.type.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://fhir.de/CodeSystem/kontaktart-de` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.type:KontaktArt.coding.code">
            <path value="Encounter.type.coding.code" />
            <short value="Code" />
            <comment value="vorstationaer | nachstationaer | begleitperson | tagesklinik | +" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceType">
            <path value="Encounter.serviceType" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceType.coding">
            <path value="Encounter.serviceType.coding" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="$this" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceType.coding:Fachabteilungsschluessel">
            <path value="Encounter.serviceType.coding" />
            <sliceName value="Fachabteilungsschluessel" />
            <short value="Fachabteilungsschl&#252;ssel" />
            <comment value="Fachabteilungen gem&#228;&#223; Anhang 1 der BPflV" />
            <min value="0" />
            <max value="1" />
            <patternCoding>
                <system value="http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel" />
            </patternCoding>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel" />
            </binding>
        </element>
        <element id="Encounter.serviceType.coding:ErweiterterFachabteilungsschluessel">
            <path value="Encounter.serviceType.coding" />
            <sliceName value="ErweiterterFachabteilungsschluessel" />
            <short value="Fachabteilungsschl&#252;ssel" />
            <comment value="Fachabteilungen gem&#228;&#223; Anhang 1 der BPflV inkl. Spezialisierungen" />
            <min value="0" />
            <max value="1" />
            <patternCoding>
                <system value="http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel-erweitert" />
            </patternCoding>
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel-erweitert" />
            </binding>
        </element>
        <element id="Encounter.subject">
            <path value="Encounter.subject" />
            <short value="Patientenbezug" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.subject.reference">
            <path value="Encounter.subject.reference" />
            <short value="Patienten-Link" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten \n      und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.period">
            <path value="Encounter.period" />
            <short value="Aufenthaltszeitraum" />
            <comment value="**WICHTIGER Hinweis f&#252;r Implementierer:** \n  * Das Aufnahmedatum  MUSS angegeben werden, \n  wenn der `status` des Encounters impliziert, dass dieser bereits begonnen hat.\n  * Das Entlassdatum MUSS angegeben werden, \n  wenn der `status` des Encounters impliziert, dass dieser beendet ist.  \n  Siehe hierzu die &#220;bersicht der Invarianten in diesem Profil." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.period.start">
            <path value="Encounter.period.start" />
            <short value="Aufnahmedatum" />
            <comment value="Hier ist stets das *tats&#228;chliche* Aufnahmedatum anzugeben.\n    *Geplante* Aufnahmedaten m&#252;ssen &#252;ber die Extension `plannedStartDate` erfasst werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.period.end">
            <path value="Encounter.period.end" />
            <short value="Entlassdatum" />
            <comment value="Hier ist stets das *tats&#228;chliche* Entlassdatum anzugeben.\n    *Geplante* Entlassdaten m&#252;ssen &#252;ber die Extension `plannedEndDate` erfasst werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.diagnosis">
            <path value="Encounter.diagnosis" />
            <short value="Falldiagnosen/-prozeduren" />
            <comment value="Verweis auf Diagnosen/Prozeduren, die eine besondere Rolle im Kontext eines Encounters einnehmen, z.B. &amp;quot;Aufnahmediagnose&amp;quot;   \n  **WICHTIGER Hinweis f&#252;r Implementierer:**   Der Fallbezug von Diagnosen und Prozeduren wird &#252;ber das jeweilige `encounter`-Element \n  der Condition bzw. Procedure-Ressource hinreichend etabliert.  Die *zus&#228;tzliche* R&#252;ckverlinkung von `Encounter.diagnosis` auf Condition/Procedure wird *nur dann* verwendet, \n  wenn einer Diagnose bzw. Prozedur *im Kontext eines Aufenthaltes* eine besondere Rolle zugewiesen werden soll, z.B. Haupt-/Neben-/Aufnahme- oder &#220;berweisungsdiagnose).  \n  Hier werden Diagnosen und Prozeduren nur nach ihrer *medizinschen* Relevanz bez&#252;glich eines Aufenthaltes qualifiziert. \n  Die Qualifikation von Diagnosen und Prozeduren im Kontext der *Abrechnung* erfolgt in der `Account`-Ressource!" />
        </element>
        <element id="Encounter.diagnosis.condition">
            <path value="Encounter.diagnosis.condition" />
            <short value="Verweis auf Diagnose/Prozedur" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.diagnosis.condition.reference">
            <path value="Encounter.diagnosis.condition.reference" />
            <short value="Condition/Procedure-Link" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Die Verlinkung auf die Condition/Procedure-Ressource dient der technischen Zuordnung des Encounters zur Condition/Precedure \n  und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.diagnosis.use">
            <path value="Encounter.diagnosis.use" />
            <short value="Bedeutung der Diagnose/Prozedur" />
            <comment value="Bedeutung der Diagnose/Prozedur im Encounter-Kontext" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.diagnosis.use.coding">
            <path value="Encounter.diagnosis.use.coding" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="$this" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.diagnosis.use.coding:Diagnosetyp">
            <path value="Encounter.diagnosis.use.coding" />
            <sliceName value="Diagnosetyp" />
            <short value="Diagnosetyp" />
            <comment value="International standardisierte, grobgranulare Unterscheidung zwischen extern gestellten Diagnosen (`referral-diagnosis`) und intern gestellten Diagnosen (`treatment-diagnosis`)" />
            <min value="1" />
            <max value="1" />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/DiagnoseTyp" />
            </binding>
        </element>
        <element id="Encounter.diagnosis.use.coding:DiagnosesubTyp">
            <path value="Encounter.diagnosis.use.coding" />
            <sliceName value="DiagnosesubTyp" />
            <short value="Diagnosesubtyp" />
            <comment value="An deutschen Kodierrichtlinien orientierte, feingranulare Unterscheidung von Diagnose-Rollen, \n      z.B. &amp;quot;Fachabteilungshauptdiagnose&amp;quot;, &amp;quot;Todesursache&amp;quot; etc." />
            <min value="0" />
            <max value="*" />
            <mustSupport value="true" />
            <binding>
                <strength value="required" />
                <valueSet value="http://fhir.de/ValueSet/Diagnosesubtyp" />
            </binding>
        </element>
        <element id="Encounter.diagnosis.rank">
            <path value="Encounter.diagnosis.rank" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.account">
            <path value="Encounter.account" />
            <short value="Abrechnungskontext" />
            <comment value="Der Bezug zu einem Account stellt den Abrechnungskontext f&#252;r einen oder mehrere Encounter her.\n  Mittels der Account-Referenz k&#246;nnen zum Beispiel ein vorstation&#228;rer, ein station&#228;rer \n  und ein nachstation&#228;rer Besuch zu einem &#39;DRG-Fall&#39; zusammengefasst werden.  \n  **WICHTIGER Hinweis f&#252;r Implementierer:** Im Deutschen Sprachgebrauch ist unter dem Begriff &#39;Fall&#39; \n  meist der Abrechnungskontext gemeint, nicht der einzelne Besuch. Die &#39;Fallnummer&#39; ist daher nicht der Identifier des Encounters, \n  sondern der des Accounts auf den der Encounter referenziert. \n  Auf diesem Wege k&#246;nnen mehrere Besuche einer Fallnummer zugeordnet werden.  \n  Da die Fallnummer ein h&#228;ufig verwendetes Suchkriterium darstellt, \n  ist diese hier als logische Referenz (`account.identifier`) zu hinterlegen.\n  Damit wird sichergestellt, dass diese als Suchparameter f&#252;r die Suche nach Encountern zur Verf&#252;gung steht, \n  auch wenn einzelne Systeme kein Chaining unterst&#252;tzen oder einzelne Benutzer keine Sichtberechtigung auf Abrechnungsdaten haben,\n  im Versorgunskontext aber dennoch Encounter anhand der assoziierten Fallnummer suchen m&#246;chten." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.account.reference">
            <path value="Encounter.account.reference" />
            <short value="Account-Link" />
            <comment value="**Begr&#252;ndung MS:** Die Verlinkung auf eine Account-Ressource dient der technischen Zuordnung des Besuchs zu einem Abrechnungskontext \n  und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.account.identifier">
            <path value="Encounter.account.identifier" />
            <short value="(Abrechnungs-)Fallnummer" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.account.identifier.system">
            <path value="Encounter.account.identifier.system" />
            <short value="Namensraum des Identifiers" />
            <comment value="Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n      aus dem der Identifier stammt. \n      Hinweise zur Festlegung der URLs f&#252;r lokale Namensr&#228;ume sind in den \n      [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n      **Begr&#252;ndung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.account.identifier.value">
            <path value="Encounter.account.identifier.value" />
            <comment value="Enth&#228;lt den eigentlichen Wert des Identifiers.  \n        **Begr&#252;ndung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.hospitalization">
            <path value="Encounter.hospitalization" />
            <short value="Details zum Aufenthalt" />
            <comment value="Details zu einem station&#228;ren Aufenthalt" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.hospitalization.extension:Wahlleistung">
            <path value="Encounter.hospitalization.extension" />
            <sliceName value="Wahlleistung" />
            <short value="Wahlleistung" />
            <comment value="**Begr&#252;ndung MS:**  Vom Patienten gebuchte Wahlleistungen (z.B. Chefarztbehandlung, Einzelzimmer) \n    sind h&#228;ufig system- und abteilungs&#252;bergreifend zu beachten und sollten daher &#252;ber die Schnittstelle kommuniziert werden k&#246;nnen." />
            <min value="0" />
            <max value="*" />
            <type>
                <code value="Extension" />
                <profile value="http://fhir.de/StructureDefinition/Wahlleistung" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.hospitalization.admitSource">
            <path value="Encounter.hospitalization.admitSource" />
            <short value="Aufnahmeanlass" />
            <comment value="Anlass der station&#228;ren Aufnahme, z.B. &amp;quot;Einweisung&amp;quot;, &amp;quot;Notfall&amp;quot; etc.  \n      Begr&#252;ndung MS: Zur Harmonisierung den Festlegungen der Medizininformatik-Initiative" />
            <mustSupport value="true" />
            <binding>
                <strength value="extensible" />
                <valueSet value="http://fhir.de/ValueSet/dgkev/Aufnahmeanlass" />
            </binding>
        </element>
        <element id="Encounter.hospitalization.dischargeDisposition">
            <path value="Encounter.hospitalization.dischargeDisposition" />
            <short value="Entlassungsart bzw. -grund" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund">
            <path value="Encounter.hospitalization.dischargeDisposition.extension" />
            <sliceName value="Entlassungsgrund" />
            <short value="Entlassungsgrund" />
            <comment value="Entlassungsgrund nach &#167; 301 Abs. 3 SGB V  \n        **Einschr&#228;nkung MS:** Der Entlassungsgrund muss nur implementiert werden,\n         wenn das best&#228;tigungsrelevante System in der Akutversorgung eingesetzt wird." />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="http://fhir.de/StructureDefinition/Entlassungsgrund" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.hospitalization.dischargeDisposition.extension:RehaEntlassung">
            <path value="Encounter.hospitalization.dischargeDisposition.extension" />
            <sliceName value="RehaEntlassung" />
            <short value="Entlassungsgrund Reha" />
            <comment value="Entlassungsgrund nach &#167;301 (Abs. 4 und 4a) SGB V  \n      **Einschr&#228;nkung MS:** Der Entlassungsgrund Reha muss nur implementiert werden,\n        wenn das best&#228;tigungsrelevante System in der Reha-Versorgung eingesetzt wird" />
            <min value="0" />
            <max value="1" />
            <type>
                <code value="Extension" />
                <profile value="https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKRehaEntlassung" />
            </type>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location">
            <path value="Encounter.location" />
            <slicing>
                <discriminator>
                    <type value="pattern" />
                    <path value="physicalType" />
                </discriminator>
                <discriminator>
                    <type value="pattern" />
                    <path value="status" />
                </discriminator>
                <rules value="open" />
            </slicing>
            <short value="Aufenthaltsorte des Patienten" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location.physicalType">
            <path value="Encounter.location.physicalType" />
            <binding>
                <strength value="extensible" />
                <valueSet value="https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType" />
            </binding>
        </element>
        <element id="Encounter.location:Zimmer">
            <path value="Encounter.location" />
            <sliceName value="Zimmer" />
            <min value="0" />
            <max value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location">
            <path value="Encounter.location.location" />
            <short value="Aufenthaltsort" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location.reference">
            <path value="Encounter.location.location.reference" />
            <short value="Location-Link" />
            <comment value="**Begr&#252;ndung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location.identifier">
            <path value="Encounter.location.location.identifier" />
            <short value="Identifier des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location.identifier.system">
            <path value="Encounter.location.location.identifier.system" />
            <short value="Namensraum des Identifiers" />
            <comment value="Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs f&#252;r lokale Namensr&#228;ume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begr&#252;ndung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location.identifier.value">
            <path value="Encounter.location.location.identifier.value" />
            <comment value="Enth&#228;lt den eigentlichen Wert des Identifiers.  \n          **Begr&#252;ndung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.location.display">
            <path value="Encounter.location.location.display" />
            <short value="(Menschenlesbarer) Name des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.status">
            <path value="Encounter.location.status" />
            <min value="1" />
            <patternCode value="active" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.physicalType">
            <path value="Encounter.location.physicalType" />
            <short value="Art des Aufenthaltsortes (hier: Zimmer)" />
            <min value="1" />
            <patternCodeableConcept>
                <coding>
                    <system value="http://terminology.hl7.org/CodeSystem/location-physical-type" />
                    <code value="ro" />
                </coding>
            </patternCodeableConcept>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.physicalType.coding">
            <path value="Encounter.location.physicalType.coding" />
            <short value="Codierte Darstellung der Art des Aufenthaltortes" />
        </element>
        <element id="Encounter.location:Zimmer.physicalType.coding.system">
            <path value="Encounter.location.physicalType.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Zimmer.physicalType.coding.code">
            <path value="Encounter.location.physicalType.coding.code" />
            <short value="Code" />
            <comment value="Hier ist stets der Wert `ro` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz">
            <path value="Encounter.location" />
            <sliceName value="Bettenstellplatz" />
            <min value="0" />
            <max value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location">
            <path value="Encounter.location.location" />
            <short value="Aufenthaltsort" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location.reference">
            <path value="Encounter.location.location.reference" />
            <short value="Location-Link" />
            <comment value="**Begr&#252;ndung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location.identifier">
            <path value="Encounter.location.location.identifier" />
            <short value="Identifier des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location.identifier.system">
            <path value="Encounter.location.location.identifier.system" />
            <short value="Namensraum des Identifiers" />
            <comment value="Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs f&#252;r lokale Namensr&#228;ume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begr&#252;ndung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location.identifier.value">
            <path value="Encounter.location.location.identifier.value" />
            <comment value="Enth&#228;lt den eigentlichen Wert des Identifiers.  \n          **Begr&#252;ndung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.location.display">
            <path value="Encounter.location.location.display" />
            <short value="(Menschenlesbarer) Name des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.status">
            <path value="Encounter.location.status" />
            <min value="1" />
            <patternCode value="active" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.physicalType">
            <path value="Encounter.location.physicalType" />
            <short value="Art des Aufenthaltsortes (hier: Bettenstellplatz)" />
            <comment value="Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType" />
            <min value="1" />
            <patternCodeableConcept>
                <coding>
                    <system value="http://terminology.hl7.org/CodeSystem/location-physical-type" />
                    <code value="bd" />
                </coding>
            </patternCodeableConcept>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.physicalType.coding">
            <path value="Encounter.location.physicalType.coding" />
            <short value="Codierte Darstellung der Art des Aufenthaltortes" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.physicalType.coding.system">
            <path value="Encounter.location.physicalType.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Bettenstellplatz.physicalType.coding.code">
            <path value="Encounter.location.physicalType.coding.code" />
            <short value="Code" />
            <comment value="Hier ist stets der Wert `bd` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station">
            <path value="Encounter.location" />
            <sliceName value="Station" />
            <min value="0" />
            <max value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location">
            <path value="Encounter.location.location" />
            <short value="Aufenthaltsort" />
            <comment value="**Begr&#252;ndung MS:** die Kenntnis des aktuellen Aufenthaltsortes ist h&#228;ufig system&#252;bergreifend relevant (z.B. f&#252;r K&#252;chen- und Logistiksysteme) und sollte daher &#252;ber die Schnittstelle kommuniziert werden k&#246;nnen." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location.reference">
            <path value="Encounter.location.location.reference" />
            <short value="Location-Link" />
            <comment value="**Begr&#252;ndung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und erm&#246;glicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location.identifier">
            <path value="Encounter.location.location.identifier" />
            <short value="Identifier des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location.identifier.system">
            <path value="Encounter.location.location.identifier.system" />
            <short value="Namensraum des Identifiers" />
            <comment value="Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs f&#252;r lokale Namensr&#228;ume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begr&#252;ndung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location.identifier.value">
            <path value="Encounter.location.location.identifier.value" />
            <comment value="Enth&#228;lt den eigentlichen Wert des Identifiers.  \n          **Begr&#252;ndung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden." />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.location.display">
            <path value="Encounter.location.location.display" />
            <short value="(Menschenlesbarer) Name des Aufenthaltsortes" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.status">
            <path value="Encounter.location.status" />
            <min value="1" />
            <patternCode value="active" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.physicalType">
            <path value="Encounter.location.physicalType" />
            <short value="Art des Aufenthaltsortes (hier: Station)" />
            <min value="1" />
            <patternCodeableConcept>
                <coding>
                    <system value="http://terminology.hl7.org/CodeSystem/location-physical-type" />
                    <code value="wa" />
                </coding>
            </patternCodeableConcept>
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.physicalType.coding">
            <path value="Encounter.location.physicalType.coding" />
            <short value="Codierte Darstellung der Art des Aufenthaltortes" />
        </element>
        <element id="Encounter.location:Station.physicalType.coding.system">
            <path value="Encounter.location.physicalType.coding.system" />
            <short value="Codier-Schema" />
            <comment value="Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.location:Station.physicalType.coding.code">
            <path value="Encounter.location.physicalType.coding.code" />
            <short value="Code" />
            <comment value="Hier ist stets der Wert `wa` anzugeben." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceProvider">
            <path value="Encounter.serviceProvider" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceProvider.identifier">
            <path value="Encounter.serviceProvider.identifier" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
        <element id="Encounter.serviceProvider.display">
            <path value="Encounter.serviceProvider.display" />
            <min value="1" />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "ISiKKontaktGesundheitseinrichtung",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung",
    "version": "4.0.1",
    "name": "ISiKKontaktGesundheitseinrichtung",
    "status": "active",
    "experimental": false,
    "date": "2024-11-25",
    "publisher": "gematik GmbH",
    "description": "\nDieses Profil ermöglicht die Abbildung von Besuchen/Aufenthalten eines Patienten in einer Gesundheitseinrichtung.\n### Motivation\nInformationen über die Besuche des Patienten entlang seines \nBehandlungspfades im Krankenhaus sind ein wichtiger Bestandteil \ndes einrichtungsinternen Datenaustausches. \nSie ermöglichen die Unterscheidung von stationären und ambulanten \nsowie aufgenommenen und entlassenen Patienten. \nWeiterhin ist aus den Besuchsinformationen der aktuelle Aufenthaltsort \ndes Patienten (Fachabteilung, Station, Bettplatz) ermittelbar. \nKlinische Ressourcen werden in FHIR durch Verlinkung auf die \nEncounter-Ressource in einen Kontext zum Besuch gestellt. \nDieser Kontext ist wichtig für die Steuerung von Zugriffsberechtigungen \nund Abrechnungsprozessen.  \n\nZu Beginn der meisten klinischen Workflows steht die Auswahl \ndes Besuchskontextes. \nDies geschieht bspw. durch das Suchen der Encounter-Ressource \nanhand von Eigenschaften wie Aufnahmenummer, Fallart oder Aufnahmedatum. \nDaraufhin werden die zutreffenden Suchergebnisse angezeigt \nund der gewünschte Besuch ausgewählt.\n\nIn FHIR werden Besuche, Aufenthalte, aber auch virtuelle Kontakte mit der `Encounter`-Ressource repräsentiert.\n\nWeitere Hinweise zu den Abgrenzungen der Begrifflichkeiten Fall und Kontakt finden sie unter {{pagelink: Fall, text: Fall-Begriff in ISiK}}\n\n### Kompatibilität\nFür das Profil ISiKKontaktGesundheitseinrichtung wird eine Kompatibilität \nmit folgenden Profilen angestrebt; \nallerdings kann nicht sichergestellt werden, dass Instanzen, \ndie gegen ISiKKontaktGesundheitseinrichtung valide sind, \nauch valide sind gegen:\n\n* Profil [Kontakt mit einer Gesundheitseinrichtung \nder Medizininformatik-Initiative](https://www.medizininformatik-initiative.de/fhir/core/modul-fall/StructureDefinition/KontaktGesundheitseinrichtung)\n\nHinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Encounter",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Encounter",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Encounter",
                "path": "Encounter",
                "constraint":  [
                    {
                        "key": "ISiK-enc-1",
                        "severity": "error",
                        "human": "Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben",
                        "expression": "status = 'finished' and class = 'AMB' implies period.start.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-2",
                        "severity": "error",
                        "human": "Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben",
                        "expression": "status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-3",
                        "severity": "error",
                        "human": "Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben",
                        "expression": "status = 'planned' implies period.exists().not()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-4",
                        "severity": "warning",
                        "human": "Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden",
                        "expression": "status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-5",
                        "severity": "error",
                        "human": "In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben",
                        "expression": "status = 'in-progress' implies period.start.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-6",
                        "severity": "error",
                        "human": "Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben",
                        "expression": "status = 'onleave' implies period.start.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-7",
                        "severity": "warning",
                        "human": "Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben",
                        "expression": "status = 'unknown' implies period.start.exists()",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    },
                    {
                        "key": "ISiK-enc-8",
                        "severity": "error",
                        "human": "Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein",
                        "expression": "diagnosis.use.all(coding.code != 'billing')",
                        "source": "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
                    }
                ]
            },
            {
                "id": "Encounter.extension",
                "path": "Encounter.extension",
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:Aufnahmegrund",
                "path": "Encounter.extension",
                "sliceName": "Aufnahmegrund",
                "short": "Aufnahmegrund",
                "comment": "Aufnahmegrund nach § 301 Abs. 3 SGB V.",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://fhir.de/StructureDefinition/Aufnahmegrund"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle",
                "path": "Encounter.extension.extension",
                "sliceName": "ErsteUndZweiteStelle",
                "short": "Aufnahmegrund: 1. & 2. Stelle",
                "comment": "1. und 2. Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.",
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:Aufnahmegrund.extension:DritteStelle",
                "path": "Encounter.extension.extension",
                "sliceName": "DritteStelle",
                "short": "Aufnahmegrund: 3. Stelle",
                "comment": "3. Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.",
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:Aufnahmegrund.extension:VierteStelle",
                "path": "Encounter.extension.extension",
                "sliceName": "VierteStelle",
                "short": "Aufnahmegrund: 4. Stelle",
                "comment": "4. Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.",
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:plannedStartDate",
                "path": "Encounter.extension",
                "sliceName": "plannedStartDate",
                "short": "geplantes Aufnahmedatum",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.extension:plannedEndDate",
                "path": "Encounter.extension",
                "sliceName": "plannedEndDate",
                "short": "geplantes Entlassdatum",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedEndDate"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier",
                "path": "Encounter.identifier",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "$this"
                        }
                    ],
                    "rules": "open"
                },
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer",
                "path": "Encounter.identifier",
                "sliceName": "Aufnahmenummer",
                "min": 0,
                "max": "1",
                "patternIdentifier": {
                    "type": {
                        "coding":  [
                            {
                                "code": "VN",
                                "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
                            }
                        ]
                    }
                },
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.type",
                "path": "Encounter.identifier.type",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.type.coding",
                "path": "Encounter.identifier.type.coding",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "$this"
                        }
                    ],
                    "rules": "open"
                },
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.type.coding:vn-type",
                "path": "Encounter.identifier.type.coding",
                "sliceName": "vn-type",
                "short": "Codierte Darstellung des Identifier-Typs",
                "min": 1,
                "max": "1",
                "patternCoding": {
                    "code": "VN",
                    "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
                },
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.type.coding:vn-type.system",
                "path": "Encounter.identifier.type.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/v2-0203` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.type.coding:vn-type.code",
                "path": "Encounter.identifier.type.coding.code",
                "short": "Code",
                "comment": "Hier ist stets der Wert `VN` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.system",
                "path": "Encounter.identifier.system",
                "short": "Namensraum des Identifiers",
                "comment": "Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n    aus dem der Identifier stammt. \n    Hinweise zur Festlegung der URLs für lokale Namensräume sind in den \n    [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n    **Begründung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.",
                "mustSupport": true
            },
            {
                "id": "Encounter.identifier:Aufnahmenummer.value",
                "path": "Encounter.identifier.value",
                "comment": "Enthält den eigentlichen Wert des Identifiers.  \n    **Begründung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.status",
                "path": "Encounter.status",
                "short": "Status",
                "comment": "Zeigt den aktuellen Status der Ressource an.     \n  **WICHTIGER Hinweis für Implementierer:**    \n  * Alle server-seitigen Implementierungen MÜSSEN in der Lage sein, \n  die systemintern möglichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `in-progress`, `finished` und `cancelled`.\n  * Alle client-seitigen Implementierungen MÜSSEN in der Lage sein, sämtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu können, \n  beispielsweise durch Ausblenden/Durchstreichen von Ressourcen mit dem status `entered-in-error` und Ausgrauen von Ressourcen, die einen Plan- oder Entwurfs-Status haben.  \n  **Historie:** Die Reduktion der zulässigen Status-Werte im Vergleich zur FHIR-Kernspezifikation \n  erfolgt im Vorgriff auf eine entsprechende Anpassung in FHIR R5.",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/EncounterStatusDe",
                    "description": "Eingeschränkter Status vgl. FHIR R5"
                }
            },
            {
                "id": "Encounter.class",
                "path": "Encounter.class",
                "short": "Fallart",
                "comment": "Die Klassifikation von Encountern nach Fallarten folgt den internationalen Vorgaben und \n  dient der groben Unterscheidung von Besuchen mit und ohne Bettendisposition (ambulant/stationär). \n  Die in Deutschland übliche Fallklassifikation anhand von unterschiedlichen \n  regulatorischen und abrechnungrelevanten Rahmenbedingungen, erfolgt in `type`.  \n  Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `class` siehe [Deutsche Basisprofile](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Ressourcen-AmbulanterStationaererFall?version=current)",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/EncounterClassDE"
                }
            },
            {
                "id": "Encounter.type",
                "path": "Encounter.type",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "$this"
                        }
                    ],
                    "rules": "open"
                },
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.type:Kontaktebene",
                "path": "Encounter.type",
                "sliceName": "Kontaktebene",
                "short": "Kontaktebene",
                "comment": "  **Begründung Pflichtfeld:** Die Abteilungsebene muss aus Kompatibilitätsgründen angegeben werden.\n  \n    **Hinweis bei Abbildung von Versorgungsstellenkontakten:**\n  Es ist ein üblicher Fall, dass die Dauer eines Versorgungsstellenkontaktes in der Versorgung die eines Abteilungskontaktes übersteigt. Ein Beispiel hierfür: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose über eine Fachabteilung (Onkologie) läuft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird.\n  Für einen solchen Fall gilt auf Ebene der FHIR-Instanzen (z.B. entgegen des tatsächliche Aufenthaltes im gleichen Bett): Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN NICHT in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen.\n\n  Hintergrund: Das Konzept der 'Kontaktebene' stammt aus dem Fallmodell der Medizininformatik-Initiative, \n    das bei Encountern zwischen 'Einrichtungskontakten', 'Fachabteilungskontakten' und 'Versorgungsstellenkontakten' unterscheidet.\n    Im Kontext dieses Moduls werden lediglich Encounter der Ebene 'Fachabteilungskontakt' abgebildet.\n  \n  ",
                "min": 1,
                "max": "1",
                "patternCodeableConcept": {
                    "coding":  [
                        {
                            "code": "abteilungskontakt",
                            "system": "http://fhir.de/CodeSystem/Kontaktebene"
                        }
                    ]
                },
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/kontaktebene-de",
                    "description": "Kontaktebene"
                }
            },
            {
                "id": "Encounter.type:Kontaktebene.coding",
                "path": "Encounter.type.coding",
                "short": "Codierte Darstellung der Kontaktebene"
            },
            {
                "id": "Encounter.type:Kontaktebene.coding.system",
                "path": "Encounter.type.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://fhir.de/CodeSystem/Kontaktebene` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.type:Kontaktebene.coding.code",
                "path": "Encounter.type.coding.code",
                "short": "Code",
                "comment": "Hier ist stets der Wert `abteilungskontakt` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.type:KontaktArt",
                "path": "Encounter.type",
                "sliceName": "KontaktArt",
                "short": "Kontaktart",
                "comment": "Die Kontaktart dient der feingranularen Differenzierung unterschiedlicher stationärer \n  und ambulanter Fallarten gemäß der in Deutschland üblichen regulatorischen \n  und abrechnungsrelevanten Rahmenbedingungen.  \n  Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `type` siehe [Deutsche Basisprofile](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Ressourcen-AmbulanterStationaererFall?version=current)",
                "min": 0,
                "max": "1",
                "patternCodeableConcept": {
                    "coding":  [
                        {
                            "system": "http://fhir.de/CodeSystem/kontaktart-de"
                        }
                    ]
                },
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/kontaktart-de"
                }
            },
            {
                "id": "Encounter.type:KontaktArt.coding",
                "path": "Encounter.type.coding",
                "short": "Codierte Darstellung der Kontaktart"
            },
            {
                "id": "Encounter.type:KontaktArt.coding.system",
                "path": "Encounter.type.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://fhir.de/CodeSystem/kontaktart-de` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.type:KontaktArt.coding.code",
                "path": "Encounter.type.coding.code",
                "short": "Code",
                "comment": "vorstationaer | nachstationaer | begleitperson | tagesklinik | +",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceType",
                "path": "Encounter.serviceType",
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceType.coding",
                "path": "Encounter.serviceType.coding",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "$this"
                        }
                    ],
                    "rules": "open"
                },
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceType.coding:Fachabteilungsschluessel",
                "path": "Encounter.serviceType.coding",
                "sliceName": "Fachabteilungsschluessel",
                "short": "Fachabteilungsschlüssel",
                "comment": "Fachabteilungen gemäß Anhang 1 der BPflV",
                "min": 0,
                "max": "1",
                "patternCoding": {
                    "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel"
                },
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel"
                }
            },
            {
                "id": "Encounter.serviceType.coding:ErweiterterFachabteilungsschluessel",
                "path": "Encounter.serviceType.coding",
                "sliceName": "ErweiterterFachabteilungsschluessel",
                "short": "Fachabteilungsschlüssel",
                "comment": "Fachabteilungen gemäß Anhang 1 der BPflV inkl. Spezialisierungen",
                "min": 0,
                "max": "1",
                "patternCoding": {
                    "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel-erweitert"
                },
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel-erweitert"
                }
            },
            {
                "id": "Encounter.subject",
                "path": "Encounter.subject",
                "short": "Patientenbezug",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.subject.reference",
                "path": "Encounter.subject.reference",
                "short": "Patienten-Link",
                "comment": "**Begründung Pflichtfeld:** Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten \n      und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.period",
                "path": "Encounter.period",
                "short": "Aufenthaltszeitraum",
                "comment": "**WICHTIGER Hinweis für Implementierer:** \n  * Das Aufnahmedatum  MUSS angegeben werden, \n  wenn der `status` des Encounters impliziert, dass dieser bereits begonnen hat.\n  * Das Entlassdatum MUSS angegeben werden, \n  wenn der `status` des Encounters impliziert, dass dieser beendet ist.  \n  Siehe hierzu die Übersicht der Invarianten in diesem Profil. ",
                "mustSupport": true
            },
            {
                "id": "Encounter.period.start",
                "path": "Encounter.period.start",
                "short": "Aufnahmedatum",
                "comment": "Hier ist stets das *tatsächliche* Aufnahmedatum anzugeben.\n    *Geplante* Aufnahmedaten müssen über die Extension `plannedStartDate` erfasst werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.period.end",
                "path": "Encounter.period.end",
                "short": "Entlassdatum",
                "comment": "Hier ist stets das *tatsächliche* Entlassdatum anzugeben.\n    *Geplante* Entlassdaten müssen über die Extension `plannedEndDate` erfasst werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.diagnosis",
                "path": "Encounter.diagnosis",
                "short": "Falldiagnosen/-prozeduren",
                "comment": "Verweis auf Diagnosen/Prozeduren, die eine besondere Rolle im Kontext eines Encounters einnehmen, z.B. &quot;Aufnahmediagnose&quot;   \n  **WICHTIGER Hinweis für Implementierer:**   Der Fallbezug von Diagnosen und Prozeduren wird über das jeweilige `encounter`-Element \n  der Condition bzw. Procedure-Ressource hinreichend etabliert.  Die *zusätzliche* Rückverlinkung von `Encounter.diagnosis` auf Condition/Procedure wird *nur dann* verwendet, \n  wenn einer Diagnose bzw. Prozedur *im Kontext eines Aufenthaltes* eine besondere Rolle zugewiesen werden soll, z.B. Haupt-/Neben-/Aufnahme- oder Überweisungsdiagnose).  \n  Hier werden Diagnosen und Prozeduren nur nach ihrer *medizinschen* Relevanz bezüglich eines Aufenthaltes qualifiziert. \n  Die Qualifikation von Diagnosen und Prozeduren im Kontext der *Abrechnung* erfolgt in der `Account`-Ressource!"
            },
            {
                "id": "Encounter.diagnosis.condition",
                "path": "Encounter.diagnosis.condition",
                "short": "Verweis auf Diagnose/Prozedur",
                "mustSupport": true
            },
            {
                "id": "Encounter.diagnosis.condition.reference",
                "path": "Encounter.diagnosis.condition.reference",
                "short": "Condition/Procedure-Link",
                "comment": "**Begründung Pflichtfeld:** Die Verlinkung auf die Condition/Procedure-Ressource dient der technischen Zuordnung des Encounters zur Condition/Precedure \n  und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.diagnosis.use",
                "path": "Encounter.diagnosis.use",
                "short": "Bedeutung der Diagnose/Prozedur",
                "comment": "Bedeutung der Diagnose/Prozedur im Encounter-Kontext",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.diagnosis.use.coding",
                "path": "Encounter.diagnosis.use.coding",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "$this"
                        }
                    ],
                    "rules": "open"
                },
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.diagnosis.use.coding:Diagnosetyp",
                "path": "Encounter.diagnosis.use.coding",
                "sliceName": "Diagnosetyp",
                "short": "Diagnosetyp",
                "comment": "International standardisierte, grobgranulare Unterscheidung zwischen extern gestellten Diagnosen (`referral-diagnosis`) und intern gestellten Diagnosen (`treatment-diagnosis`)",
                "min": 1,
                "max": "1",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/DiagnoseTyp"
                }
            },
            {
                "id": "Encounter.diagnosis.use.coding:DiagnosesubTyp",
                "path": "Encounter.diagnosis.use.coding",
                "sliceName": "DiagnosesubTyp",
                "short": "Diagnosesubtyp",
                "comment": "An deutschen Kodierrichtlinien orientierte, feingranulare Unterscheidung von Diagnose-Rollen, \n      z.B. &quot;Fachabteilungshauptdiagnose&quot;, &quot;Todesursache&quot; etc.",
                "min": 0,
                "max": "*",
                "mustSupport": true,
                "binding": {
                    "strength": "required",
                    "valueSet": "http://fhir.de/ValueSet/Diagnosesubtyp"
                }
            },
            {
                "id": "Encounter.diagnosis.rank",
                "path": "Encounter.diagnosis.rank",
                "mustSupport": true
            },
            {
                "id": "Encounter.account",
                "path": "Encounter.account",
                "short": "Abrechnungskontext",
                "comment": "Der Bezug zu einem Account stellt den Abrechnungskontext für einen oder mehrere Encounter her.\n  Mittels der Account-Referenz können zum Beispiel ein vorstationärer, ein stationärer \n  und ein nachstationärer Besuch zu einem 'DRG-Fall' zusammengefasst werden.  \n  **WICHTIGER Hinweis für Implementierer:** Im Deutschen Sprachgebrauch ist unter dem Begriff 'Fall' \n  meist der Abrechnungskontext gemeint, nicht der einzelne Besuch. Die 'Fallnummer' ist daher nicht der Identifier des Encounters, \n  sondern der des Accounts auf den der Encounter referenziert. \n  Auf diesem Wege können mehrere Besuche einer Fallnummer zugeordnet werden.  \n  Da die Fallnummer ein häufig verwendetes Suchkriterium darstellt, \n  ist diese hier als logische Referenz (`account.identifier`) zu hinterlegen.\n  Damit wird sichergestellt, dass diese als Suchparameter für die Suche nach Encountern zur Verfügung steht, \n  auch wenn einzelne Systeme kein Chaining unterstützen oder einzelne Benutzer keine Sichtberechtigung auf Abrechnungsdaten haben,\n  im Versorgunskontext aber dennoch Encounter anhand der assoziierten Fallnummer suchen möchten.",
                "mustSupport": true
            },
            {
                "id": "Encounter.account.reference",
                "path": "Encounter.account.reference",
                "short": "Account-Link",
                "comment": "**Begründung MS:** Die Verlinkung auf eine Account-Ressource dient der technischen Zuordnung des Besuchs zu einem Abrechnungskontext \n  und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "mustSupport": true
            },
            {
                "id": "Encounter.account.identifier",
                "path": "Encounter.account.identifier",
                "short": "(Abrechnungs-)Fallnummer",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.account.identifier.system",
                "path": "Encounter.account.identifier.system",
                "short": "Namensraum des Identifiers",
                "comment": "Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n      aus dem der Identifier stammt. \n      Hinweise zur Festlegung der URLs für lokale Namensräume sind in den \n      [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n      **Begründung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.account.identifier.value",
                "path": "Encounter.account.identifier.value",
                "comment": "Enthält den eigentlichen Wert des Identifiers.  \n        **Begründung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.hospitalization",
                "path": "Encounter.hospitalization",
                "short": "Details zum Aufenthalt",
                "comment": "Details zu einem stationären Aufenthalt",
                "mustSupport": true
            },
            {
                "id": "Encounter.hospitalization.extension:Wahlleistung",
                "path": "Encounter.hospitalization.extension",
                "sliceName": "Wahlleistung",
                "short": "Wahlleistung",
                "comment": "**Begründung MS:**  Vom Patienten gebuchte Wahlleistungen (z.B. Chefarztbehandlung, Einzelzimmer) \n    sind häufig system- und abteilungsübergreifend zu beachten und sollten daher über die Schnittstelle kommuniziert werden können.",
                "min": 0,
                "max": "*",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://fhir.de/StructureDefinition/Wahlleistung"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.hospitalization.admitSource",
                "path": "Encounter.hospitalization.admitSource",
                "short": "Aufnahmeanlass",
                "comment": "Anlass der stationären Aufnahme, z.B. &quot;Einweisung&quot;, &quot;Notfall&quot; etc.  \n      Begründung MS: Zur Harmonisierung den Festlegungen der Medizininformatik-Initiative",
                "mustSupport": true,
                "binding": {
                    "strength": "extensible",
                    "valueSet": "http://fhir.de/ValueSet/dgkev/Aufnahmeanlass"
                }
            },
            {
                "id": "Encounter.hospitalization.dischargeDisposition",
                "path": "Encounter.hospitalization.dischargeDisposition",
                "short": "Entlassungsart bzw. -grund",
                "mustSupport": true
            },
            {
                "id": "Encounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund",
                "path": "Encounter.hospitalization.dischargeDisposition.extension",
                "sliceName": "Entlassungsgrund",
                "short": "Entlassungsgrund",
                "comment": "Entlassungsgrund nach § 301 Abs. 3 SGB V  \n        **Einschränkung MS:** Der Entlassungsgrund muss nur implementiert werden,\n         wenn das bestätigungsrelevante System in der Akutversorgung eingesetzt wird.",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "http://fhir.de/StructureDefinition/Entlassungsgrund"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.hospitalization.dischargeDisposition.extension:RehaEntlassung",
                "path": "Encounter.hospitalization.dischargeDisposition.extension",
                "sliceName": "RehaEntlassung",
                "short": "Entlassungsgrund Reha",
                "comment": "Entlassungsgrund nach §301 (Abs. 4 und 4a) SGB V  \n      **Einschränkung MS:** Der Entlassungsgrund Reha muss nur implementiert werden,\n        wenn das bestätigungsrelevante System in der Reha-Versorgung eingesetzt wird",
                "min": 0,
                "max": "1",
                "type":  [
                    {
                        "code": "Extension",
                        "profile":  [
                            "https://gematik.de/fhir/isik/StructureDefinition/ExtensionISiKRehaEntlassung"
                        ]
                    }
                ],
                "mustSupport": true
            },
            {
                "id": "Encounter.location",
                "path": "Encounter.location",
                "slicing": {
                    "discriminator":  [
                        {
                            "type": "pattern",
                            "path": "physicalType"
                        },
                        {
                            "type": "pattern",
                            "path": "status"
                        }
                    ],
                    "rules": "open"
                },
                "short": "Aufenthaltsorte des Patienten",
                "mustSupport": true
            },
            {
                "id": "Encounter.location.physicalType",
                "path": "Encounter.location.physicalType",
                "binding": {
                    "strength": "extensible",
                    "valueSet": "https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType"
                }
            },
            {
                "id": "Encounter.location:Zimmer",
                "path": "Encounter.location",
                "sliceName": "Zimmer",
                "min": 0,
                "max": "1",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location",
                "path": "Encounter.location.location",
                "short": "Aufenthaltsort",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location.reference",
                "path": "Encounter.location.location.reference",
                "short": "Location-Link",
                "comment": "**Begründung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location.identifier",
                "path": "Encounter.location.location.identifier",
                "short": "Identifier des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location.identifier.system",
                "path": "Encounter.location.location.identifier.system",
                "short": "Namensraum des Identifiers",
                "comment": "Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs für lokale Namensräume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begründung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location.identifier.value",
                "path": "Encounter.location.location.identifier.value",
                "comment": "Enthält den eigentlichen Wert des Identifiers.  \n          **Begründung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.location.display",
                "path": "Encounter.location.location.display",
                "short": "(Menschenlesbarer) Name des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.status",
                "path": "Encounter.location.status",
                "min": 1,
                "patternCode": "active",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.physicalType",
                "path": "Encounter.location.physicalType",
                "short": "Art des Aufenthaltsortes (hier: Zimmer)",
                "min": 1,
                "patternCodeableConcept": {
                    "coding":  [
                        {
                            "code": "ro",
                            "system": "http://terminology.hl7.org/CodeSystem/location-physical-type"
                        }
                    ]
                },
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.physicalType.coding",
                "path": "Encounter.location.physicalType.coding",
                "short": "Codierte Darstellung der Art des Aufenthaltortes"
            },
            {
                "id": "Encounter.location:Zimmer.physicalType.coding.system",
                "path": "Encounter.location.physicalType.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Zimmer.physicalType.coding.code",
                "path": "Encounter.location.physicalType.coding.code",
                "short": "Code",
                "comment": "Hier ist stets der Wert `ro` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz",
                "path": "Encounter.location",
                "sliceName": "Bettenstellplatz",
                "min": 0,
                "max": "1",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location",
                "path": "Encounter.location.location",
                "short": "Aufenthaltsort",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location.reference",
                "path": "Encounter.location.location.reference",
                "short": "Location-Link",
                "comment": "**Begründung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location.identifier",
                "path": "Encounter.location.location.identifier",
                "short": "Identifier des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location.identifier.system",
                "path": "Encounter.location.location.identifier.system",
                "short": "Namensraum des Identifiers",
                "comment": "Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs für lokale Namensräume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begründung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location.identifier.value",
                "path": "Encounter.location.location.identifier.value",
                "comment": "Enthält den eigentlichen Wert des Identifiers.  \n          **Begründung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.location.display",
                "path": "Encounter.location.location.display",
                "short": "(Menschenlesbarer) Name des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.status",
                "path": "Encounter.location.status",
                "min": 1,
                "patternCode": "active",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.physicalType",
                "path": "Encounter.location.physicalType",
                "short": "Art des Aufenthaltsortes (hier: Bettenstellplatz)",
                "comment": "Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType",
                "min": 1,
                "patternCodeableConcept": {
                    "coding":  [
                        {
                            "code": "bd",
                            "system": "http://terminology.hl7.org/CodeSystem/location-physical-type"
                        }
                    ]
                },
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.physicalType.coding",
                "path": "Encounter.location.physicalType.coding",
                "short": "Codierte Darstellung der Art des Aufenthaltortes"
            },
            {
                "id": "Encounter.location:Bettenstellplatz.physicalType.coding.system",
                "path": "Encounter.location.physicalType.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Bettenstellplatz.physicalType.coding.code",
                "path": "Encounter.location.physicalType.coding.code",
                "short": "Code",
                "comment": "Hier ist stets der Wert `bd` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station",
                "path": "Encounter.location",
                "sliceName": "Station",
                "min": 0,
                "max": "1",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location",
                "path": "Encounter.location.location",
                "short": "Aufenthaltsort",
                "comment": "**Begründung MS:** die Kenntnis des aktuellen Aufenthaltsortes ist häufig systemübergreifend relevant (z.B. für Küchen- und Logistiksysteme) und sollte daher über die Schnittstelle kommuniziert werden können.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location.reference",
                "path": "Encounter.location.location.reference",
                "short": "Location-Link",
                "comment": "**Begründung MS:** Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort \n  und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location.identifier",
                "path": "Encounter.location.location.identifier",
                "short": "Identifier des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location.identifier.system",
                "path": "Encounter.location.location.identifier.system",
                "short": "Namensraum des Identifiers",
                "comment": "Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, \n        aus dem der Identifier stammt. \n        Hinweise zur Festlegung der URLs für lokale Namensräume sind in den \n        [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Terminologie-Namensraeume?version=current) beschrieben.  \n        **Begründung Pflichtfeld:** `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location.identifier.value",
                "path": "Encounter.location.location.identifier.value",
                "comment": "Enthält den eigentlichen Wert des Identifiers.  \n          **Begründung Pflichtfeld:** Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.location.display",
                "path": "Encounter.location.location.display",
                "short": "(Menschenlesbarer) Name des Aufenthaltsortes",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.status",
                "path": "Encounter.location.status",
                "min": 1,
                "patternCode": "active",
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.physicalType",
                "path": "Encounter.location.physicalType",
                "short": "Art des Aufenthaltsortes (hier: Station)",
                "min": 1,
                "patternCodeableConcept": {
                    "coding":  [
                        {
                            "code": "wa",
                            "system": "http://terminology.hl7.org/CodeSystem/location-physical-type"
                        }
                    ]
                },
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.physicalType.coding",
                "path": "Encounter.location.physicalType.coding",
                "short": "Codierte Darstellung der Art des Aufenthaltortes"
            },
            {
                "id": "Encounter.location:Station.physicalType.coding.system",
                "path": "Encounter.location.physicalType.coding.system",
                "short": "Codier-Schema",
                "comment": "Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.location:Station.physicalType.coding.code",
                "path": "Encounter.location.physicalType.coding.code",
                "short": "Code",
                "comment": "Hier ist stets der Wert `wa` anzugeben.",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceProvider",
                "path": "Encounter.serviceProvider",
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceProvider.identifier",
                "path": "Encounter.serviceProvider.identifier",
                "min": 1,
                "mustSupport": true
            },
            {
                "id": "Encounter.serviceProvider.display",
                "path": "Encounter.serviceProvider.display",
                "min": 1,
                "mustSupport": true
            }
        ]
    }
}

ISiKKontaktGesundheitseinrichtung

Constraints/Invarianten

Name	Schweregrad	Beschreibung	Ausdruck
ISiK-enc-1	error	Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben	status = 'finished' and class = 'AMB' implies period.start.exists()
ISiK-enc-2	error	Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben	status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()
ISiK-enc-3	error	Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben	status = 'planned' implies period.exists().not()
ISiK-enc-4	warning	Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden	status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()
ISiK-enc-5	error	In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben	status = 'in-progress' implies period.start.exists()
ISiK-enc-6	error	Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben	status = 'onleave' implies period.start.exists()
ISiK-enc-7	warning	Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben	status = 'unknown' implies period.start.exists()
ISiK-enc-8	error	Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein	diagnosis.use.all(coding.code != 'billing')

Terminology-Bindings

Element	Staerke	ValueSet
Encounter.status	required	http://fhir.de/ValueSet/EncounterStatusDe
Encounter.class	required	http://fhir.de/ValueSet/EncounterClassDE
Encounter.type:Kontaktebene	required	http://fhir.de/ValueSet/kontaktebene-de
Encounter.type:KontaktArt	required	http://fhir.de/ValueSet/kontaktart-de
Encounter.serviceType.coding:Fachabteilungsschluessel	required	http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel
Encounter.serviceType.coding:ErweiterterFachabteilungsschluessel	required	http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel-erweitert
Encounter.diagnosis.use.coding:Diagnosetyp	required	http://fhir.de/ValueSet/DiagnoseTyp
Encounter.diagnosis.use.coding:DiagnosesubTyp	required	http://fhir.de/ValueSet/Diagnosesubtyp
Encounter.hospitalization.admitSource	extensible	http://fhir.de/ValueSet/dgkev/Aufnahmeanlass
Encounter.location.physicalType	extensible	https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType

Anmerkungen zu Must-Support-Feldern

Feldname	Kurzbeschreibung	Hinweise
Encounter.extension
Encounter.extension:Aufnahmegrund	Aufnahmegrund	Aufnahmegrund nach § 301 Abs. 3 SGB V.
Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle	Aufnahmegrund: 1. & 2. Stelle	und 2. Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.
Encounter.extension:Aufnahmegrund.extension:DritteStelle	Aufnahmegrund: 3. Stelle	Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.
Encounter.extension:Aufnahmegrund.extension:VierteStelle	Aufnahmegrund: 4. Stelle	Stelle des Aufnahmegrunds nach § 301 Abs. 3 SGB V.
Encounter.extension:plannedStartDate	geplantes Aufnahmedatum
Encounter.extension:plannedEndDate	geplantes Entlassdatum
Encounter.identifier
Encounter.identifier:Aufnahmenummer
Encounter.identifier:Aufnahmenummer.type
Encounter.identifier:Aufnahmenummer.type.coding
Encounter.identifier:Aufnahmenummer.type.coding:vn-type	Codierte Darstellung des Identifier-Typs
Encounter.identifier:Aufnahmenummer.type.coding:vn-type.system	Codier-Schema	Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/v2-0203` anzugeben.
Encounter.identifier:Aufnahmenummer.type.coding:vn-type.code	Code	Hier ist stets der Wert `VN` anzugeben.
Encounter.identifier:Aufnahmenummer.system	Namensraum des Identifiers	Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.
Encounter.identifier:Aufnahmenummer.value		Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.
Encounter.status	Status	Zeigt den aktuellen Status der Ressource an. WICHTIGER Hinweis für Implementierer: Alle server-seitigen Implementierungen MÜSSEN in der Lage sein, die systemintern möglichen Statuswerte korrekt in FHIR abzubilden, mindestens jedoch die Werte `in-progress`, `finished` und `cancelled`. Alle client-seitigen Implementierungen MÜSSEN in der Lage sein, sämtliche Status-Codes zu interpretieren und dem Anwender in angemessener Form darstellen zu können, beispielsweise durch Ausblenden/Durchstreichen von Ressourcen mit dem status `entered-in-error` und Ausgrauen von Ressourcen, die einen Plan- oder Entwurfs-Status haben. Historie: Die Reduktion der zulässigen Status-Werte im Vergleich zur FHIR-Kernspezifikation erfolgt im Vorgriff auf eine entsprechende Anpassung in FHIR R5.
Encounter.class	Fallart	Die Klassifikation von Encountern nach Fallarten folgt den internationalen Vorgaben und dient der groben Unterscheidung von Besuchen mit und ohne Bettendisposition (ambulant/stationär). Die in Deutschland übliche Fallklassifikation anhand von unterschiedlichen regulatorischen und abrechnungrelevanten Rahmenbedingungen, erfolgt in `type`. Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `class` siehe Deutsche Basisprofile
Encounter.type
Encounter.type:Kontaktebene	Kontaktebene	Begründung Pflichtfeld: Die Abteilungsebene muss aus Kompatibilitätsgründen angegeben werden. `Hinweis bei Abbildung von Versorgungsstellenkontakten:` Es ist ein üblicher Fall, dass die Dauer eines Versorgungsstellenkontaktes in der Versorgung die eines Abteilungskontaktes übersteigt. Ein Beispiel hierfür: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose über eine Fachabteilung (Onkologie) läuft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird. Für einen solchen Fall gilt auf Ebene der FHIR-Instanzen (z.B. entgegen des tatsächliche Aufenthaltes im gleichen Bett): Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN NICHT in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen. Hintergrund: Das Konzept der 'Kontaktebene' stammt aus dem Fallmodell der Medizininformatik-Initiative, das bei Encountern zwischen 'Einrichtungskontakten', 'Fachabteilungskontakten' und 'Versorgungsstellenkontakten' unterscheidet. Im Kontext dieses Moduls werden lediglich Encounter der Ebene 'Fachabteilungskontakt' abgebildet.
Encounter.type:Kontaktebene.coding.system	Codier-Schema	Hier ist stets der Wert `http://fhir.de/CodeSystem/Kontaktebene` anzugeben.
Encounter.type:Kontaktebene.coding.code	Code	Hier ist stets der Wert `abteilungskontakt` anzugeben.
Encounter.type:KontaktArt	Kontaktart	Die Kontaktart dient der feingranularen Differenzierung unterschiedlicher stationärer und ambulanter Fallarten gemäß der in Deutschland üblichen regulatorischen und abrechnungsrelevanten Rahmenbedingungen. Für ein korrektes Mapping der in Deutschland gebräuchlichen Fallarten auf `type` siehe Deutsche Basisprofile
Encounter.type:KontaktArt.coding.system	Codier-Schema	Hier ist stets der Wert `http://fhir.de/CodeSystem/kontaktart-de` anzugeben.
Encounter.type:KontaktArt.coding.code	Code	vorstationaer \| nachstationaer \| begleitperson \| tagesklinik \| +
Encounter.serviceType
Encounter.serviceType.coding
Encounter.serviceType.coding:Fachabteilungsschluessel	Fachabteilungsschlüssel	Fachabteilungen gemäß Anhang 1 der BPflV
Encounter.serviceType.coding:ErweiterterFachabteilungsschluessel	Fachabteilungsschlüssel	Fachabteilungen gemäß Anhang 1 der BPflV inkl. Spezialisierungen
Encounter.subject	Patientenbezug
Encounter.subject.reference	Patienten-Link	Begründung Pflichtfeld: Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.period	Aufenthaltszeitraum	WICHTIGER Hinweis für Implementierer: Das Aufnahmedatum MUSS angegeben werden, wenn der `status` des Encounters impliziert, dass dieser bereits begonnen hat. Das Entlassdatum MUSS angegeben werden, wenn der `status` des Encounters impliziert, dass dieser beendet ist. Siehe hierzu die Übersicht der Invarianten in diesem Profil.
Encounter.period.start	Aufnahmedatum	Hier ist stets das tatsächliche Aufnahmedatum anzugeben. Geplante Aufnahmedaten müssen über die Extension `plannedStartDate` erfasst werden.
Encounter.period.end	Entlassdatum	Hier ist stets das tatsächliche Entlassdatum anzugeben. Geplante Entlassdaten müssen über die Extension `plannedEndDate` erfasst werden.
Encounter.diagnosis.condition	Verweis auf Diagnose/Prozedur
Encounter.diagnosis.condition.reference	Condition/Procedure-Link	Begründung Pflichtfeld: Die Verlinkung auf die Condition/Procedure-Ressource dient der technischen Zuordnung des Encounters zur Condition/Precedure und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.diagnosis.use	Bedeutung der Diagnose/Prozedur	Bedeutung der Diagnose/Prozedur im Encounter-Kontext
Encounter.diagnosis.use.coding
Encounter.diagnosis.use.coding:Diagnosetyp	Diagnosetyp	International standardisierte, grobgranulare Unterscheidung zwischen extern gestellten Diagnosen (`referral-diagnosis`) und intern gestellten Diagnosen (`treatment-diagnosis`)
Encounter.diagnosis.use.coding:DiagnosesubTyp	Diagnosesubtyp	An deutschen Kodierrichtlinien orientierte, feingranulare Unterscheidung von Diagnose-Rollen, z.B. "Fachabteilungshauptdiagnose", "Todesursache" etc.
Encounter.diagnosis.rank
Encounter.account	Abrechnungskontext	Der Bezug zu einem Account stellt den Abrechnungskontext für einen oder mehrere Encounter her. Mittels der Account-Referenz können zum Beispiel ein vorstationärer, ein stationärer und ein nachstationärer Besuch zu einem 'DRG-Fall' zusammengefasst werden. WICHTIGER Hinweis für Implementierer: Im Deutschen Sprachgebrauch ist unter dem Begriff 'Fall' meist der Abrechnungskontext gemeint, nicht der einzelne Besuch. Die 'Fallnummer' ist daher nicht der Identifier des Encounters, sondern der des Accounts auf den der Encounter referenziert. Auf diesem Wege können mehrere Besuche einer Fallnummer zugeordnet werden. Da die Fallnummer ein häufig verwendetes Suchkriterium darstellt, ist diese hier als logische Referenz (`account.identifier`) zu hinterlegen. Damit wird sichergestellt, dass diese als Suchparameter für die Suche nach Encountern zur Verfügung steht, auch wenn einzelne Systeme kein Chaining unterstützen oder einzelne Benutzer keine Sichtberechtigung auf Abrechnungsdaten haben, im Versorgunskontext aber dennoch Encounter anhand der assoziierten Fallnummer suchen möchten.
Encounter.account.reference	Account-Link	Begründung MS: Die Verlinkung auf eine Account-Ressource dient der technischen Zuordnung des Besuchs zu einem Abrechnungskontext und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.account.identifier	(Abrechnungs-)Fallnummer
Encounter.account.identifier.system	Namensraum des Identifiers	Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.
Encounter.account.identifier.value		Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.
Encounter.hospitalization	Details zum Aufenthalt	Details zu einem stationären Aufenthalt
Encounter.hospitalization.extension:Wahlleistung	Wahlleistung	Begründung MS: Vom Patienten gebuchte Wahlleistungen (z.B. Chefarztbehandlung, Einzelzimmer) sind häufig system- und abteilungsübergreifend zu beachten und sollten daher über die Schnittstelle kommuniziert werden können.
Encounter.hospitalization.admitSource	Aufnahmeanlass	Anlass der stationären Aufnahme, z.B. "Einweisung", "Notfall" etc. Begründung MS: Zur Harmonisierung den Festlegungen der Medizininformatik-Initiative
Encounter.hospitalization.dischargeDisposition	Entlassungsart bzw. -grund
Encounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund	Entlassungsgrund	Entlassungsgrund nach § 301 Abs. 3 SGB V Einschränkung MS: Der Entlassungsgrund muss nur implementiert werden, wenn das bestätigungsrelevante System in der Akutversorgung eingesetzt wird.
Encounter.hospitalization.dischargeDisposition.extension:RehaEntlassung	Entlassungsgrund Reha	Entlassungsgrund nach §301 (Abs. 4 und 4a) SGB V Einschränkung MS: Der Entlassungsgrund Reha muss nur implementiert werden, wenn das bestätigungsrelevante System in der Reha-Versorgung eingesetzt wird
Encounter.location	Aufenthaltsorte des Patienten
Encounter.location:Zimmer
Encounter.location:Zimmer.location	Aufenthaltsort
Encounter.location:Zimmer.location.reference	Location-Link	Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.location:Zimmer.location.identifier	Identifier des Aufenthaltsortes
Encounter.location:Zimmer.location.identifier.system	Namensraum des Identifiers	Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.
Encounter.location:Zimmer.location.identifier.value		Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.
Encounter.location:Zimmer.location.display	(Menschenlesbarer) Name des Aufenthaltsortes
Encounter.location:Zimmer.status
Encounter.location:Zimmer.physicalType	Art des Aufenthaltsortes (hier: Zimmer)
Encounter.location:Zimmer.physicalType.coding.system	Codier-Schema	Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.
Encounter.location:Zimmer.physicalType.coding.code	Code	Hier ist stets der Wert `ro` anzugeben.
Encounter.location:Bettenstellplatz
Encounter.location:Bettenstellplatz.location	Aufenthaltsort
Encounter.location:Bettenstellplatz.location.reference	Location-Link	Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.location:Bettenstellplatz.location.identifier	Identifier des Aufenthaltsortes
Encounter.location:Bettenstellplatz.location.identifier.system	Namensraum des Identifiers	Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.
Encounter.location:Bettenstellplatz.location.identifier.value		Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.
Encounter.location:Bettenstellplatz.location.display	(Menschenlesbarer) Name des Aufenthaltsortes
Encounter.location:Bettenstellplatz.status
Encounter.location:Bettenstellplatz.physicalType	Art des Aufenthaltsortes (hier: Bettenstellplatz)	Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/ValueSet/ISiKLocationPhysicalType
Encounter.location:Bettenstellplatz.physicalType.coding.system	Codier-Schema	Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.
Encounter.location:Bettenstellplatz.physicalType.coding.code	Code	Hier ist stets der Wert `bd` anzugeben.
Encounter.location:Station
Encounter.location:Station.location	Aufenthaltsort	Begründung MS: die Kenntnis des aktuellen Aufenthaltsortes ist häufig systemübergreifend relevant (z.B. für Küchen- und Logistiksysteme) und sollte daher über die Schnittstelle kommuniziert werden können.
Encounter.location:Station.location.reference	Location-Link	Begründung MS: Die Verlinkung auf eine Location-Ressource dient der technischen Zuordnung des Besuchs zu einem Aufenthaltsort und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.
Encounter.location:Station.location.identifier	Identifier des Aufenthaltsortes
Encounter.location:Station.location.identifier.system	Namensraum des Identifiers	Hier ist stets der eindeutige Name (URL) des Namensraums anzugeben, aus dem der Identifier stammt. Hinweise zur Festlegung der URLs für lokale Namensräume sind in den Deutschen Basisprofilen beschrieben. Begründung Pflichtfeld: `system` stellt in Kombination mit `value` die Eindeutigkeit eines Identifiers sicher.
Encounter.location:Station.location.identifier.value		Enthält den eigentlichen Wert des Identifiers. Begründung Pflichtfeld: Ist der Wert nicht bekannt, sollte der gesamte Slice weggelassen werden.
Encounter.location:Station.location.display	(Menschenlesbarer) Name des Aufenthaltsortes
Encounter.location:Station.status
Encounter.location:Station.physicalType	Art des Aufenthaltsortes (hier: Station)
Encounter.location:Station.physicalType.coding.system	Codier-Schema	Hier ist stets der Wert `http://terminology.hl7.org/CodeSystem/location-physical-type` anzugeben.
Encounter.location:Station.physicalType.coding.code	Code	Hier ist stets der Wert `wa` anzugeben.
Encounter.serviceProvider
Encounter.serviceProvider.identifier
Encounter.serviceProvider.display

Interaktionen

Interaktion	Verbindlichkeit
read	SHALL
search-type	SHALL

Parameter	Typ	Verbindlichkeit	Hinweise
_id	token	SHALL	Beispiel: `GET [base]/[Resourcetype]?_id=103270` Anwendungshinweis: Der Parameter `_id` wird selten alleinstehend verwendet, da sich zum Abruf einer Ressource anhand der `id` die `READ`-Interaktion besser anbietet. Der Parameter kann jedoch verwendet werden, um den Abruf einer Ressource bspw. mit einem `_include` weiterer Ressourcen zu verbinden, z.B. zum Abruf eines Encounters in Verbindung mit dem zugehörigen Patienten: `GET [base]/Encounter?_id=103270&_include=Encounter:patient` Weitere Details siehe FHIR-Kernspezifikation, Abschnitt Parameters for all resources. Dieser Suchparameter ist für die Umsetzung des IHE PDQm Profils verpflichtend.
_tag	token	SHALL	Beispiel: `GET [base]/[Resourcetype]?_tag=https://example.org/codes\|needs-review` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation, Abschnitt Parameters for all resources sowie Abschnitt Tags.
_count	number	SHALL	Beispiel: `GET [base]/[Resourcetype]?_count=100` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation, Abschnitt Page Count.
_has	string	MAY	Beispiel: Suche nach allen Patienten, die eine Observation mit dem Code '1234-5' haben `GET [base]/Patient?_has:Observation:patient:code=1234-5` Beispiel: Suche nach allen Encountern, bei denen die Diagnose 'A12.3' gestellt wurde `GET [base]/Encounter?_has:Condition:encounter:code=A12.3` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation, Abschnitt Reverse Chaining.
identifier	token	SHALL	Beispiel: `GET [base]/Encounter?identifier=http://test.krankenhaus.de/fhir/sid/fallnr\|123456` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
status	token	SHALL	Beispiel: `GET [base]/Encounter?status=finished` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
class	token	SHALL	Beispiel: `GET [base]/Encounter?class=IMP` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
type	token	SHALL	Beispiel: `GET [base]/Encounter?type=http://fhir.de/CodeSystem/kontaktart-de\|stationaer` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
patient	reference	SHALL	Beispiel: `GET [base]/Encounter?patient=Patient/123` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation. Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend.
subject	reference	SHALL	Beispiel: `GET [base]/Encounter?subject=Patient/123` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
account	reference	SHALL	Beispiel: `GET [base]/Encounter?account=Account/123` `GET [base]/Encounter?account:identifier=123456` `GET [base]/Encounter?account:identifier=https://example.org/fhir/sid/abrechnungsfallnr\|123456` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
date	date	SHALL	Beispiel: `GET [base]/Encounter?date=lt2020-26-10` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation. Bei der Formulierung der Suche sollten die Vorgaben aus der Definition der Such-Prefixe - und hier insbesondere die Unterschiede zwischen `lt` und `eb` bzw. `gt` und `sa` - beachtet werden.
date-start	date	SHALL	Beispiel: `GET [base]/Encounter?end-date=lt2020-26-10` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation. Bei diesem Suchparameter handelt es sich um eine Präadoption eines Suchparameters, der in FHIR R5 hinzugefügt wurde.
end-date	date	SHALL	Beispiel: `GET [base]/Encounter?end-date=lt2020-26-10` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation. Bei diesem Suchparameter handelt es sich um eine Präadoption eines Suchparameters, der in FHIR R5 hinzugefügt wurde.
location	reference	MAY	Beispiel: `GET [base]/Encounter?location=Location/test` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.
service-provider	reference	MAY	Beispiel: `GET [base]/Encounter?service-provider=Organization/test` Anwendungshinweis: Weitere Details siehe FHIR-Kernspezifikation.

(Reverse-)Include

Include	ReverseInclude
Encounter:patient; Encounter:subject; Encounter:part-of; Encounter:diagnosis; Encounter:account	Encounter:part-of; Condition:encounter; Composition:encounter; Procedure:encounter

CapabilityStatement

Beispiele

Ein Beispiel für das Profil ISiKKontaktGesundheitseinrichtung:

{
    "resourceType": "Encounter",
    "id": "Fachabteilungskontakt",
    "meta": {
        "profile":  [
            "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"
        ]
    },
    "type":  [
        {
            "coding":  [
                {
                    "code": "abteilungskontakt",
                    "system": "http://fhir.de/CodeSystem/Kontaktebene"
                }
            ]
        },
        {
            "coding":  [
                {
                    "system": "http://fhir.de/CodeSystem/kontaktart-de",
                    "code": "operation"
                }
            ]
        }
    ],
    "extension":  [
        {
            "url": "http://fhir.de/StructureDefinition/Aufnahmegrund",
            "extension":  [
                {
                    "url": "ErsteUndZweiteStelle",
                    "valueCoding": {
                        "code": "01",
                        "system": "http://fhir.de/CodeSystem/dkgev/AufnahmegrundErsteUndZweiteStelle",
                        "display": "Krankenhausbehandlung, vollstationär"
                    }
                },
                {
                    "url": "DritteStelle",
                    "valueCoding": {
                        "code": "0",
                        "system": "http://fhir.de/CodeSystem/dkgev/AufnahmegrundDritteStelle",
                        "display": "Anderes"
                    }
                },
                {
                    "url": "VierteStelle",
                    "valueCoding": {
                        "code": "1",
                        "system": "http://fhir.de/CodeSystem/dkgev/AufnahmegrundVierteStelle",
                        "display": "Normalfall"
                    }
                }
            ]
        }
    ],
    "identifier":  [
        {
            "type": {
                "coding":  [
                    {
                        "code": "VN",
                        "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
                    }
                ]
            },
            "system": "https://test.krankenhaus.de/fhir/sid/besuchsnummer",
            "value": "0123456789"
        }
    ],
    "status": "finished",
    "class": {
        "code": "IMP",
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode"
    },
    "serviceType": {
        "coding":  [
            {
                "code": "0100",
                "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel"
            }
        ]
    },
    "subject": {
        "reference": "Patient/PatientinMusterfrau"
    },
    "period": {
        "start": "2021-02-12",
        "end": "2021-02-13"
    },
    "diagnosis":  [
        {
            "condition": {
                "reference": "Condition/BehandlungsDiagnoseFreitext"
            },
            "use": {
                "coding":  [
                    {
                        "code": "treatment-diagnosis",
                        "system": "http://fhir.de/CodeSystem/KontaktDiagnoseProzedur"
                    }
                ]
            }
        }
    ],
    "account":  [
        {
            "reference": "Account/AbrechnungsfallDRG",
            "identifier": {
                "value": "XZY",
                "system": "https://test.krankenhaus.de/fhir/sid/fallnummer"
            }
        }
    ],
    "hospitalization": {
        "admitSource": {
            "coding":  [
                {
                    "code": "E",
                    "system": "http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass"
                }
            ]
        },
        "dischargeDisposition": {
            "extension":  [
                {
                    "url": "http://fhir.de/StructureDefinition/Entlassungsgrund",
                    "extension":  [
                        {
                            "url": "ErsteUndZweiteStelle",
                            "valueCoding": {
                                "code": "01",
                                "system": "http://fhir.de/CodeSystem/dkgev/EntlassungsgrundErsteUndZweiteStelle",
                                "display": "Behandlung regulär beendet"
                            }
                        },
                        {
                            "url": "DritteStelle",
                            "valueCoding": {
                                "code": "1",
                                "system": "http://fhir.de/CodeSystem/dkgev/EntlassungsgrundDritteStelle",
                                "display": "arbeitsfähig entlassen"
                            }
                        }
                    ]
                }
            ]
        }
    },
    "location":  [
        {
            "physicalType": {
                "coding":  [
                    {
                        "code": "bd",
                        "system": "http://terminology.hl7.org/CodeSystem/location-physical-type",
                        "display": "Bed"
                    }
                ]
            },
            "status": "active",
            "location": {
                "identifier": {
                    "system": "https://test.krankenhaus.de/fhir/sid/locationid",
                    "value": "123"
                },
                "display": "Bettenstellplatz 123"
            }
        }
    ],
    "serviceProvider": {
        "identifier": {
            "system": "https://test.krankenhaus.de/fhir/sid/fachabteilungsid",
            "value": "XYZ"
        },
        "display": "Fachabteilung XYZ"
    }
}