Dieses Profil beschreibt einen Fall / Kontakt in der Medizininformatik-Initiative.
Differential
MII_PR_Fall_KontaktGesundheitseinrichtung (Encounter) | I | Encounter | Element idEncounter An interaction during which services are provided to the patient Alternate namesVisit DefinitionAn interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
| |
id | S Σ | 0..1 | string | Element idEncounter.id Logical id of this artifact DefinitionAngabe OPTIONAL, vom Server automatisch vergebene system-abhängige ID The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | S Σ | 0..1 | Meta | Element idEncounter.meta Metadata about the resource DefinitionAngabe OPTIONAL zur Provenance und zum Profil
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.meta.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.meta.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idEncounter.meta.versionId Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idEncounter.meta.lastUpdated When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | S Σ | 0..1 | uri | There are no (further) constraints on this element Element idEncounter.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | S Σ | 0..* | canonical(StructureDefinition) | There are no (further) constraints on this element Element idEncounter.meta.profile Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idEncounter.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System.
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idEncounter.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idEncounter.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idEncounter.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idEncounter.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
Aufnahmegrund | S I | 0..1 | Extension(Complex) | Element idEncounter.extension:Aufnahmegrund Aufnahmegrund Alternate namesextensions, user content DefinitionOPTIONAL, Aufnahmegrund entsprechend Schlüssel 1 der Anlage 2 der Datenübermittlung nach § 301 Abs. 3 SGB V 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. Extension(Complex) Extension URLhttp://fhir.de/StructureDefinition/Aufnahmegrund Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
ErsteUndZweiteStelle | S I | 0..1 | Extension | Element idEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle 1. und 2. Stelle Alternate namesextensions, user content DefinitionOPTIONAL, Aufnahmegrund (1. und 2. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. 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. ErsteUndZweiteStelle
| |
value[x] | 0..1 | Binding | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). AufnahmegrundErsteUndZweiteStelleVS (required) Constraints
| |
valueCoding | Coding | There are no (further) constraints on this element Data type | ||
DritteStelle | S I | 0..1 | Extension | Element idEncounter.extension:Aufnahmegrund.extension:DritteStelle 3. Stelle Alternate namesextensions, user content DefinitionOPTIONAL, Aufnahmegrund (3. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:DritteStelle.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:DritteStelle.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:DritteStelle.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. 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. DritteStelle
| |
value[x] | 0..1 | Binding | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:DritteStelle.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). AufnahmegrundDritteStelleVS (required) Constraints
| |
valueCoding | Coding | There are no (further) constraints on this element Data type | ||
VierteStelle | S I | 0..1 | Extension | Element idEncounter.extension:Aufnahmegrund.extension:VierteStelle 4. Stelle Alternate namesextensions, user content DefinitionOPTIONAL, Aufnahmegrund (4. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:VierteStelle.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:VierteStelle.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:VierteStelle.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. 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. VierteStelle
| |
value[x] | 0..1 | Binding | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.extension:VierteStelle.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). AufnahmegrundVierteStelleVS (required) Constraints
| |
valueCoding | Coding | There are no (further) constraints on this element Data type | ||
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. 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. http://fhir.de/StructureDefinition/Aufnahmegrund
| |
value[x] | 0..0 | There are no (further) constraints on this element Element idEncounter.extension:Aufnahmegrund.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| ||
plannedStartDate | I | 0..1 | Extension(dateTime) | Element idEncounter.extension:plannedStartDate Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate Constraints
|
plannedEndDate | I | 0..1 | Extension(dateTime) | Element idEncounter.extension:plannedEndDate Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedEndDate Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | S Σ | 0..* | Identifier | Element idEncounter.identifier Identifikator DefinitionKennung/en, unter der/denen dieser Kontakt bekannt ist. Unordered, Open, by $this(Pattern) Constraints
|
Aufnahmenummer | S Σ | 0..1 | IdentifierPattern | Element idEncounter.identifier:Aufnahmenummer Aufnahmenummer DefinitionOPTIONAL, Aufnahmenummer/Fallnummer, die Patient:innen bei der Planung einer Aufnahme oder bei der Aufnahme selbst bekommt. Generell SOLLTE die Aufnahmenummer in allen Encounter-Ressourcen unabhängig von der Kontaktebene und dem Kontakttyp angegeben werden. Als Gründe würden dagegen sprechen, wenn die Aufnahmenummer nur in einem Encounter der Encounter-Hierarchie angegeben werden kann. In diesem Fall SOLL auf die korrekte Encounter-Verlinkung über .partOf geachtet werden, sowie dass jeder Encounter einen eigenständigen Identifier mit unterschiedlichen Systemen enthält.
{ "type": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } ] } }
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
|
type | S Σ | 1..1 | CodeableConceptBindingPattern | Element idEncounter.identifier:Aufnahmenummer.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. 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. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" } ] }
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..* | CodingPattern | Element idEncounter.identifier:Aufnahmenummer.type.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Unordered, Open, by $this(Pattern) Constraints
{ "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" }
|
vn-type | S Σ | 1..1 | CodingPattern | Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
{ "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "VN" }
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | S Σ | 1..1 | uriPattern | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://terminology.hl7.org/CodeSystem/v2-0203
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.version Version of the system - if relevant DefinitionThe 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. 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.
|
code | S Σ | 1..1 | codePattern | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
VN
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.coding:vn-type.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). 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. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.type.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
|
system | S Σ | 1..1 | uri | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. 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. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
|
value | S Σ | 1..1 | string | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. 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.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idEncounter.identifier:Aufnahmenummer.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. 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.
|
status | S Σ ?! | 1..1 | codeBinding | Element idEncounter.status Status DefinitionVERPFLICHTEND, required Binding auf http://fhir.de/ValueSet/EncounterStatusDe Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes). Current state of the encounter.
|
statusHistory | 0..* | BackboneElement | There are no (further) constraints on this element Element idEncounter.statusHistory List of past encounter statuses DefinitionThe 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. The current status is always found in the current version of the resource, not the status history.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.statusHistory.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.statusHistory.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.statusHistory.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
status | 1..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.statusHistory.status planned | arrived | triaged | in-progress | onleave | finished | cancelled + Definitionplanned | arrived | triaged | in-progress | onleave | finished | cancelled +. Note that FHIR strings SHALL NOT exceed 1MB in size Current state of the encounter.
| |
period | I | 1..1 | Period | There are no (further) constraints on this element Element idEncounter.statusHistory.period The time that the episode was in the specified status DefinitionThe time that the episode was in the specified status. 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.
|
class | S Σ | 1..1 | CodingBinding | Element idEncounter.class Kontaktklasse DefinitionVERPFLICHTEND, Kontaktklasse. Required Binding auf http://fhir.de/ValueSet/EncounterClassDE. Klassifizierung des Kontaktes in stationär, ambulant, teilstationär oder andere. 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. Classification of the encounter.
|
classHistory | 0..* | BackboneElement | There are no (further) constraints on this element Element idEncounter.classHistory List of past encounter classes DefinitionThe 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.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.classHistory.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.classHistory.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.classHistory.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
class | 1..1 | CodingBinding | There are no (further) constraints on this element Element idEncounter.classHistory.class inpatient | outpatient | ambulatory | emergency + Definitioninpatient | outpatient | ambulatory | emergency +. 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. Classification of the encounter.
| |
period | I | 1..1 | Period | There are no (further) constraints on this element Element idEncounter.classHistory.period The time that the episode was in the specified class DefinitionThe time that the episode was in the specified class. 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.
|
type | S Σ | 0..* | CodeableConcept | Element idEncounter.type Kontakttyp DefinitionSpezifischer Typ des Kontaktes Since there are many ways to further classify encounters, this element is 0..*. Unordered, Open, by $this(Pattern) BindingThe type of encounter.
|
Kontaktebene | S Σ | 0..1 | CodeableConceptBindingPattern | Element idEncounter.type:Kontaktebene Kontaktebene DefinitionOPTIONAL, Unterscheidung der Kontakt-Hierarchieebenen Einrichtungskontakt, Abteilungskontakt, Versorgungsstellenkontakt. Die Gliederung gilt für stationäre Kontakte. Required Binding auf http://fhir.de/ValueSet/kontaktebene-de Since there are many ways to further classify encounters, this element is 0..*. Kontaktebene
{ "coding": [ { "system": "http://fhir.de/CodeSystem/Kontaktebene" } ] }
|
KontaktArt | S Σ | 0..1 | CodeableConceptBindingPattern | Element idEncounter.type:KontaktArt Kontaktart DefinitionOPTIONAL, Differenzierung zwischen verschiedenen Arten von Kontakten (z.B. vorstationär, nachstationär, intensivstationär). Required Binding auf http://fhir.de/ValueSet/kontaktart-de Since there are many ways to further classify encounters, this element is 0..*. The type of encounter.
{ "coding": [ { "system": "http://fhir.de/CodeSystem/kontaktart-de" } ] }
|
serviceType | S Σ | 0..1 | CodeableConcept | Element idEncounter.serviceType Fachabteilung DefinitionDie Fachdisziplin bzw. Fachabteilung wird durch einen vierstelligen Fachabteilungsschlüssel klassifiziert. 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. Broad categorization of the service that is to be provided.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.serviceType.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | S Σ | 0..* | Coding | Element idEncounter.serviceType.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Unordered, Open, by $this(Pattern) Constraints
|
Fachabteilungsschluessel | S Σ | 0..1 | CodingBindingPattern | Element idEncounter.serviceType.coding:Fachabteilungsschluessel Fachabteilungsschlüssel DefinitionOPTIONAL, required Binding auf http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel Fachabteilungen gemäß Anhang 1 der BPflV in der am 31.12.2003 geltenden Fassung Allows for alternative encodings within a code system, and translations to other code systems. 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. FachabteilungsschluesselVS (required) Constraints
{ "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel" }
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | S Σ | 1..1 | uriPattern | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.version Version of the system - if relevant DefinitionThe 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. 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.
|
code | S Σ | 1..1 | code | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idEncounter.serviceType.coding:Fachabteilungsschluessel.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). 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. 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.
|
ErweiterterFachabteilungsschluessel | S Σ | 0..1 | CodingBindingPattern | Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel Erweiterter Fachabteilungsschlüssel DefinitionOPTIONAL, required Binding auf http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel-erweitert Fachabteilungen gemäß Anhang 1 der BPflV in der am 31.12.2003 geltenden Fassung inkl. Spezialisierungen. Allows for alternative encodings within a code system, and translations to other code systems. 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. ValueSetFachabteilungsschluesselErweitert (required) Constraints
{ "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel-erweitert" }
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | S Σ | 1..1 | uriPattern | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel-erweitert
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.version Version of the system - if relevant DefinitionThe 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. 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.
|
code | S Σ | 1..1 | code | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idEncounter.serviceType.coding:ErweiterterFachabteilungsschluessel.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). 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. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.serviceType.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
|
priority | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idEncounter.priority Indicates the urgency of the encounter DefinitionIndicates the urgency of the encounter. 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. Indicates the urgency of the encounter.
| |
subject | S Σ I | 1..1 | Reference(Patient | Group) | Element idEncounter.subject Patientenidentifikator Alternate namespatient DefinitionVERPFLICHTEND, Referenz auf Patient:in. 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).
|
episodeOfCare | Σ I | 0..* | Reference(EpisodeOfCare) | There are no (further) constraints on this element Element idEncounter.episodeOfCare Episode(s) of care that this encounter should be recorded against DefinitionWhere 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). 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.
|
basedOn | I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element idEncounter.basedOn The ServiceRequest that initiated this encounter Alternate namesincomingReferral DefinitionThe request this encounter satisfies (e.g. incoming referral or procedure request). 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.
|
participant | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idEncounter.participant List of participants involved in the encounter DefinitionThe list of people responsible for providing the service.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.participant.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.participant.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.participant.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
type | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idEncounter.participant.type Role of participant in encounter DefinitionRole of participant in encounter. 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. Role of participant in encounter.
|
period | I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.participant.period Period of time during the encounter that the participant participated DefinitionThe period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. 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.
|
individual | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idEncounter.participant.individual Persons involved in the encounter other than the patient DefinitionPersons involved in the encounter other than the patient. 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. Reference(Practitioner | PractitionerRole | RelatedPerson) Constraints
|
appointment | Σ I | 0..* | Reference(Appointment) | There are no (further) constraints on this element Element idEncounter.appointment The appointment that scheduled this encounter DefinitionThe appointment that scheduled this encounter. 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.
|
period | S I | 0..1 | Period | Element idEncounter.period Zeitraum des Kontaktes DefinitionBeginn- und Endzeitpunkt des Kontaktes. DARF NICHT vorhanden sein, kann OPTIONAL oder VERPFLICHTEND sein, abhängig vom Status des Kontaktes - siehe Invarianten auf Ebene Encounter. If not (yet) known, the end of the Period may be omitted.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.period.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.period.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
start | S Σ I | 0..1 | dateTime | Element idEncounter.period.start Beginndatum DefinitionStart des Kontaktzeitraums. DARF NICHT vorhanden sein, kann OPTIONAL oder VERPFLICHTEND sein, abhängig vom Status des Kontaktes - siehe Invarianten auf Ebene Encounter. If the low element is missing, the meaning is that the low boundary is not known.
|
end | S Σ I | 0..1 | dateTime | Element idEncounter.period.end Enddatum DefinitionEnde des Kontaktzeitraums. DARF NICHT vorhanden sein, kann OPTIONAL oder VERPFLICHTEND sein, abhängig vom Status des Kontaktes - siehe Invarianten auf Ebene Encounter. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
length | I | 0..1 | Duration | There are no (further) constraints on this element Element idEncounter.length Quantity of time the encounter lasted (less time absent) DefinitionQuantity of time the encounter lasted. This excludes the time during leaves of absence. May differ from the time the Encounter.period lasted because of leave of absence.
|
reasonCode | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idEncounter.reasonCode Coded reason the encounter takes place Alternate namesIndication, Admission diagnosis DefinitionReason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. 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). Reason why the encounter takes place.
|
reasonReference | Σ I | 0..* | Reference(Condition | Procedure | Observation | ImmunizationRecommendation) | There are no (further) constraints on this element Element idEncounter.reasonReference Reason the encounter takes place (reference) Alternate namesIndication, Admission diagnosis DefinitionReason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. 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). Reference(Condition | Procedure | Observation | ImmunizationRecommendation) Constraints
|
diagnosis | S Σ | 0..* | BackboneElement | Element idEncounter.diagnosis Diagnosen DefinitionOPTIONAL, Angaben zu Diagnosen
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.diagnosis.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.diagnosis.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.diagnosis.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
condition | S Σ I | 1..1 | Reference(Condition | Procedure) | Element idEncounter.diagnosis.condition Referenz zu Diagnose-Ressource Alternate namesAdmission diagnosis, discharge diagnosis, indication DefinitionVERPFLICHTEND, wenn Diagnosedaten angegeben werden, dann MUSS diese referenziert werden. Es SOLLTE nur die Primärdiagnose referenziert werden. 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). Reference(Condition | Procedure) Constraints
|
use | S | 1..1 | CodeableConceptBinding | Element idEncounter.diagnosis.use Diagnosetyp DefinitionAttribute wie Aufnahme- oder Entlassdiagnose sind immer im Kontext eines stationären Aufenthaltes zu betrachten
und werden daher als Eigenschaft des Encounters modelliert.
VERPFLICHTEND mindestens die Angabe eines Codings. EMPFOHLEN ist die Angabe mittels Diagnosetyp- und DiagnosesubTyp-Coding.
Weitere Codings OPTIONAL. Extensible Binding auf Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type of diagnosis this condition represents.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.diagnosis.use.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.diagnosis.use.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | S Σ | 1..* | Coding | Element idEncounter.diagnosis.use.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Unordered, Open, by $this(Pattern) Constraints
|
Diagnosetyp | S Σ | 0..1 | CodingBinding | Element idEncounter.diagnosis.use.coding:Diagnosetyp Diagnosetyp DefinitionEinweisungs-/Überweisungsdiagnose | Behandlungsrelevante Diagnosen Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
DiagnosesubTyp | S Σ | 0..1 | CodingBinding | Element idEncounter.diagnosis.use.coding:DiagnosesubTyp Diagnosesubtyp DefinitionOperationsdiagnose | Abteilung Hauptdiagnose | Todesursache | Infektionsschutzdiagnose + Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.diagnosis.use.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
|
rank | S | 0..1 | positiveInt | Element idEncounter.diagnosis.rank Rangfolge DefinitionOPTIONAL, Rangfolge der Diagnose 32 bit number; for values larger than this, use decimal
|
account | I | 0..* | Reference(Account) | There are no (further) constraints on this element Element idEncounter.account The set of accounts that may be used for billing for this Encounter DefinitionThe set of accounts that may be used for billing for this Encounter. The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.
|
hospitalization | S | 0..1 | BackboneElement | Element idEncounter.hospitalization Klinikaufenthalt DefinitionOPTIONAL, Details zur Aufnahme und Entlassung An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.hospitalization.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.hospitalization.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.hospitalization.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
preAdmissionIdentifier | 0..1 | Identifier | There are no (further) constraints on this element Element idEncounter.hospitalization.preAdmissionIdentifier Pre-admission identifier DefinitionPre-admission identifier.
| |
origin | I | 0..1 | Reference(Location | Organization) | There are no (further) constraints on this element Element idEncounter.hospitalization.origin The location/organization from which the patient came before admission DefinitionThe location/organization from which the patient came before admission. 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. Reference(Location | Organization) Constraints
|
admitSource | S | 1..1 | CodeableConceptBinding | Element idEncounter.hospitalization.admitSource Aufnahmeanlass DefinitionVERPFLICHTEND, Aufnahmeanlass. Preferred Binding auf http://fhir.de/ValueSet/dgkev/Aufnahmeanlass 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. From where the patient was admitted.
|
reAdmission | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idEncounter.hospitalization.reAdmission The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission DefinitionWhether this hospitalization is a readmission and why if known. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The reason for re-admission of this hospitalization encounter.
| |
dietPreference | 0..* | CodeableConcept | There are no (further) constraints on this element Element idEncounter.hospitalization.dietPreference Diet preferences reported by the patient DefinitionDiet preferences reported by the patient. 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. For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). Medical, cultural or ethical food preferences to help with catering requirements.
| |
specialCourtesy | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idEncounter.hospitalization.specialCourtesy Special courtesies (VIP, board member) DefinitionSpecial courtesies (VIP, board member). 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. Special courtesies.
| |
specialArrangement | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idEncounter.hospitalization.specialArrangement Wheelchair, translator, stretcher, etc. DefinitionAny special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. 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. Special arrangements.
| |
destination | I | 0..1 | Reference(Location | Organization) | There are no (further) constraints on this element Element idEncounter.hospitalization.destination Location/organization to which the patient is discharged DefinitionLocation/organization to which the patient is discharged. 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. Reference(Location | Organization) Constraints
|
dischargeDisposition | S | 0..1 | CodeableConcept | Element idEncounter.hospitalization.dischargeDisposition Entlassung DefinitionOPTIONAL Daten zur Entlassung 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. Discharge Disposition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.hospitalization.dischargeDisposition.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.hospitalization.dischargeDisposition.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
Entlassungsgrund | S I | 0..1 | Extension(Complex) | Element idEncounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund Entlassungsgrund Alternate namesextensions, user content DefinitionOPTIONAL, Entlassungs-/Verlegungsgrund nach § 301 Abs. 3 SGB V 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. Extension(Complex) Extension URLhttp://fhir.de/StructureDefinition/Entlassungsgrund Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idEncounter.hospitalization.dischargeDisposition.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idEncounter.hospitalization.dischargeDisposition.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
|
location | 0..* | BackboneElement | Element idEncounter.location Kontaktort DefinitionOPTIONAL, Details zum Kontaktort wie Zimmer, Bett, Station 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". Unordered, Open, by physicalType(Pattern) Constraints
| |
(All Slices) | There are no (further) constraints on this element | |||
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.location.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
location | I | 1..1 | Reference(Location) | There are no (further) constraints on this element Element idEncounter.location.location Location the encounter takes place DefinitionThe location where the encounter takes place. 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.
|
status | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.location.status planned | active | reserved | completed DefinitionThe 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. 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. The status of the location.
| |
physicalType | 0..1 | CodeableConceptBinding | Element idEncounter.location.physicalType Kontaktorttyp DefinitionSOLL, extensible Binding auf https://www.medizininformatik-initiative.de/fhir/core/modul-fall/ValueSet/location-physical-type 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. Physical form of the location.
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.location.period Time period during which the patient was present at the location DefinitionTime period during which the patient was present at the location. 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.
|
Zimmer | 0..1 | BackboneElement | Element idEncounter.location:Zimmer Zimmer DefinitionVon Patient oder Patientin während des Kontaktes belegtes Zimmer auf einer Station. 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".
| |
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.location:Zimmer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Zimmer.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Zimmer.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
location | I | 1..1 | Reference(Location) | There are no (further) constraints on this element Element idEncounter.location:Zimmer.location Location the encounter takes place DefinitionThe location where the encounter takes place. 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.
|
status | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.location:Zimmer.status planned | active | reserved | completed DefinitionThe 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. 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. The status of the location.
| |
physicalType | 1..1 | CodeableConceptPattern | Element idEncounter.location:Zimmer.physicalType The physical type of the location (usually the level in the location hierachy - bed room ward etc.) DefinitionThis will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. 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. Physical form of the location.
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "ro" } ] }
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.location:Zimmer.period Time period during which the patient was present at the location DefinitionTime period during which the patient was present at the location. 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.
|
Bett | 0..1 | BackboneElement | Element idEncounter.location:Bett Bett DefinitionVon Patient oder Patientin während des Kontaktes belegter Bettenstellplatz. 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".
| |
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.location:Bett.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Bett.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Bett.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
location | I | 1..1 | Reference(Location) | There are no (further) constraints on this element Element idEncounter.location:Bett.location Location the encounter takes place DefinitionThe location where the encounter takes place. 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.
|
status | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.location:Bett.status planned | active | reserved | completed DefinitionThe 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. 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. The status of the location.
| |
physicalType | 1..1 | CodeableConceptPattern | Element idEncounter.location:Bett.physicalType The physical type of the location (usually the level in the location hierachy - bed room ward etc.) DefinitionThis will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. 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. Physical form of the location.
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "bd" } ] }
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.location:Bett.period Time period during which the patient was present at the location DefinitionTime period during which the patient was present at the location. 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.
|
Station | 0..1 | BackboneElement | Element idEncounter.location:Station Station DefinitionDie Station, auf welcher der Patient oder die Patientin während des Kontaktes behandelt wurde. 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".
| |
id | 0..1 | string | There are no (further) constraints on this element Element idEncounter.location:Station.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Station.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idEncounter.location:Station.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
location | I | 1..1 | Reference(Location) | There are no (further) constraints on this element Element idEncounter.location:Station.location Location the encounter takes place DefinitionThe location where the encounter takes place. 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.
|
status | 0..1 | codeBinding | There are no (further) constraints on this element Element idEncounter.location:Station.status planned | active | reserved | completed DefinitionThe 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. 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. The status of the location.
| |
physicalType | 1..1 | CodeableConceptPattern | Element idEncounter.location:Station.physicalType The physical type of the location (usually the level in the location hierachy - bed room ward etc.) DefinitionThis will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. 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. Physical form of the location.
{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/location-physical-type", "code": "wa" } ] }
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element idEncounter.location:Station.period Time period during which the patient was present at the location DefinitionTime period during which the patient was present at the location. 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.
|
serviceProvider | I | 0..1 | Reference(Organization) | Element idEncounter.serviceProvider Leistungserbringer DefinitionOPTIONAL. Leistungserbringer, der für den Kontakt verantwortlich ist. Referenz auf eine Organisation 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.
|
partOf | S I | 0..1 | Reference(Encounter) | Element idEncounter.partOf Teil von Kontakt DefinitionOPTIONAL. Abbildung der Hierarchie zwischen Kontaktebenen durch Referenz auf weitere Kontakte, wenn bspw. ein Versorgungsstellenkontakt Teil eines Abteilungskontaktes oder ein Abteilungskontakt Teil eines Einrichtungskontaktes ist. 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.
|
Zur Kodierung von Encounter.class wird auf das ValueSet ActEncounterCode verwiesen.
Fallart | Code in HL7 V2 | Repräsentation in FHIR |
---|---|---|
Ambulant | O | Encounter.class = AMB |
Ambulantes Operieren | O | Encounter.class = AMBEncounter.type = operation |
Stationär | I | Encounter.class = IMP |
Normalstationär | I | Encounter.class = IMPEncounter.type = normalstationaer |
Intensivstationär | I | Encounter.class = IMPEncounter.type = intensivstationaer |
Wiederaufnahme | R | Encounter.class = IMPEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle = 07 |
Voraufnahme | P | Encounter.class = PRENC |
Virtuell | - | Encounter.class = VR |
Vorstationär | V | Encounter.class = AMBEncounter.type = vorstationaer |
Nachstationär | NS | Encounter.class = AMBEncounter.type = nachstationaer |
Teilstationär | TS | Encounter.class = IMP oder SSEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle = 03Encounter.type = teilstationaer | tagesklinik | nachtklinik |
Begleitperson | H | Encounter.class = IMPEncounter.type = begleitperson |
Stationsäquivalent | - | Encounter.class = HHEncounter.type = stationsaequivalentEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle = 10 |
Entbindung | - | Encounter.class = IMPEncounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle = 05 |
Notfall | - | Encounter.class = AMB Encounter.extension:Aufnahmegrund.VierteStelle = 7 Falls eine anschließende stationäre Aufnahme erfolgt, kann Encounter.hospitalization.admitSource = "N" verwendet werden. Wenn der Aspekt der Dringlichkeit der Behandlung hervorgehoben werden soll, kann Encounter.priority = http://terminology.hl7.org/CodeSystem/v3-ActPriority|EM verwendet werden. |
Fallart | Code in HL7 V2 | Repräsentation in FHIR |
---|---|---|
Untersuchung und Behandlung | - | Encounter.class = IMPEncounter.type = ub |
Konsil | - | Encounter.class = IMPEncounter.type = konsil |
Operation | - | Encounter.class = IMPEncounter.type = operation |
FHIR-Element | Kurze Beschreibung |
---|---|
Encounter.id | optionale Angabe, vom Server automatisch vergebene system-abhängige ID |
Encounter.meta | optionale Angabe zur Provenance und zum Profil |
Encounter.extension:Aufnahmegrund | optional, Aufnahmegrund entsprechend Schlüssel 1 der Anlage 2 zur § 301-Vereinbarung |
Encounter.extension:Aufnahmegrund.extension:ErsteUndZweiteStelle | optional, Aufnahmegrund (1. und 2. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. Required Binding auf http://fhir.de/ValueSet/dkgev/AufnahmegrundErsteUndZweiteStelle |
Encounter.extension:Aufnahmegrund.extension:DritteStelle | optional, Aufnahmegrund (3. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. Required Binding auf http://fhir.de/ValueSet/dkgev/AufnahmegrundDritteStelle |
Encounter.extension:Aufnahmegrund.extension:VierteStelle | optional, Aufnahmegrund (4. Stelle), Datenübermittlung nach § 301 Abs. 3 SGB V. Required Binding auf http://fhir.de/ValueSet/dkgev/AufnahmegrundVierteStelle |
Encounter.identifier:Aufnahmenummer | optional, Aufnahmenummer/Fallnummer, die Patient:innen bei der Planung einer Aufnahme oder bei der Aufnahme selbst bekommt. Generell sollte die Aufnahmenummer in allen Encounter-Ressourcen unabhängig von der Kontaktebene und dem Kontakttyp angegeben werden. Als Gründe würden dagegen sprechen, wenn die Aufnahmenummer nur in einem Encounter der Encounter-Hierarchie angegeben werden kann. In diesem Fall ist auf die korrekte Encounter-Verlinkung über .partOf zu achten, sowie dass jeder Encounter einen eigenständigen Identifier mit unterschiedlichen Systemen enthält. |
Encounter.status | verpflichtend, required Binding auf https://www.medizininformatik-initiative.de/fhir/core/ValueSet/RestrictedEncounterStatus |
Encounter.class | verpflichtend, Kontaktklasse. Required Binding auf http://fhir.de/ValueSet/EncounterClassDE |
Encounter.type:Kontaktebene | optional, 3 Ebenen: Einrichtungskontakt, Abteilungskontakt, Versorgungsstellenkontakt. Required Binding auf http://fhir.de/ValueSet/kontaktebene-de |
Encounter.type:KontaktArt | Differenzierung zwischen verschiedenen Arten von Kontakten (z.B. vorstationär, nachstationär, intensivstationär). Required Binding auf http://fhir.de/ValueSet/kontaktart-de |
Encounter.serviceType.coding:Fachabteilungsschluessel | optional, extensible Binding auf http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel |
Encounter.subject | verpflichtende Referenz auf Patient:in |
Encounter.period | verpflichtend, Zeitraum des Kontaktes |
Encounter.period.start | verpflichtend, Start des Kontakt Zeitraums |
Encounter.period.end | optinal, Ende des Kontakt Zeitraums |
Encounter.diagnosis | optionale Angaben zu Diagnose(n) |
Encounter.diagnosis.condition | verplfichtend, wenn Diagnosedaten angegeben werden, dann muss diese referenziert werden. Es sollte nur die Primärdiagnose referenziert werden. |
Encounter.diagnosis.use | verpflichtend, preferred Binding auf http://hl7.org/fhir/ValueSet/diagnosis-role |
Encounter.diagnosis.rank | optional |
Encounter.hospitalization | verpflichtend, Daten zur Aufnahme und Entlassung |
Encounter.hospitalization.admitSource | verpflichtend, Aufnahmeanlass. Preferred Binding auf http://fhir.de/ValueSet/dgkev/Aufnahmeanlass |
Encounter.hospitalization.dischargeDisposition | optional, Entlassungsdaten |
Encounter.hospitalization.dischargeDisposition.extension:Entlassungsgrund | optional, Entlassungs-/Verlegungsgrund nach § 301 Abs. 3 SGB V. http://fhir.de/StructureDefinition/Entlassungsgrund |
Encounter.location | optional |
Encounter.serviceProvider | optionale Referenz auf eine Einrichtung |
Encounter.partOf | optionale Referenz auf andere Kontaktinstanzen |
FHIR Element | Logischer Datensatz |
---|---|
Encounter.type | Fall.Einrichtungskontakt.KontaktEbene |
Encounter.type | Fall.Einrichtungskontakt.KontaktArt |
Encounter.subject | Fall.Einrichtungskontakt.PatientenIdentifikator |
Encounter.identifier | Fall.Einrichtungskontakt.Aufnahmenummer |
Encounter.hospitalization.admitSource | Fall.Einrichtungskontakt.Aufnahmeanlass |
Encounter.reasonCode | Fall.Einrichtungskontakt.Aufnahmegrund |
Encounter.period.start | Fall.Einrichtungskontakt.Beginndatum |
Encounter.period.end | Fall.Einrichtungskontakt.Enddatum |
Encounter.hospitalization.dischargeDisposition | Fall.Einrichtungskontakt.Entlassungsgrund |
Encounter.type | Fall.Abteilungskontakt.KontaktEbene |
Encounter.type | Fall.Abteilungskontakt.KontaktArt |
Encounter.subject | Fall.Abteilungskontakt.PatientenIdentifikator |
Encounter.identifier | Fall.Abteilungskontakt.Aufnahmenummer |
Encounter.period.start | Fall.Abteilungskontakt.Beginndatum |
Encounter.period.end | Fall.Abteilungskontakt.Enddatum |
Encounter.type | Fall.Versorgungsstellenkontakt.KontaktEbene |
Encounter.type | Fall.Versorgungsstellenkontakt.KontaktArt |
Encounter.subject | Fall.Versorgungsstellenkontakt.PatientenIdentifikator |
Encounter.identifier | Fall.Versorgungsstellenkontakt.Aufnahmenummer |
Encounter.period.start | Fall.Versorgungsstellenkontakt.Beginndatum |
Encounter.period.end | Fall.Versorgungsstellenkontakt.Enddatum |
Invarianten | Beschreibung | Expression |
---|---|---|
Snapshot
Beispiele
Beispiel Einrichtungskontakt:
Beispiel Abteilungskontakt:
Powered by SIMPLIFIER.NET