Bedeutung: DRG- und hiervon abweichende Krankenhausdiagnosen sollten im Account zusammenfassend und abschließend angegeben werden. Relevante Prozeduren können ebenfalls aufgelistet werden.
+
Account.identifier
+
Bedeutung: Der Account muss die Abrechnungsnummer des referenzierenden Kontaktes (Encounter) enthalten. Dies entspricht dem Wert des Elements Encounter.account.identifier.
+
Account.status
+
Bedeutung: Der Status MUSS insbesondere zur Differenzierung von abgeschlossenen und derzeitig noch aktiven Abrechnungsfällen angegeben werden. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "active", "inactive". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Bedeutung: Ein Patientenbezug des Falls MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Account.coverage
+
Bedeutung: Pro Abrechnungskontext (z.B. Selbstzahler, DRG, PEPP) sollte ein eigener Account angelegt werden. Für jeden Account sollte ersichtlich sein über welche Coverage der Account beglichen werden soll.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Beispiele.html
new file mode 100644
index 00000000..3be302ae
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Beispiele.html
@@ -0,0 +1,314 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Beispiele
+
Valides Minimalbeispiel für das Profil ISiKAbrechnungsfall:
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Kompatibilitaet.html
new file mode 100644
index 00000000..fffc3dbd
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Kompatibilitaet.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKAbrechnungsfall wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Motivation.html
new file mode 100644
index 00000000..3bab8786
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Motivation.html
@@ -0,0 +1,265 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Komplementär zum Datenobjekt "Kontakt - Encounter" können Fälle, im Sinne einer Gruppierung von medizinischen Leistungen, innerhalb eines gemeinsamen Kontextes, zu einem Abrechnungsfall zusammengefasst werden.
+Ein solcher Abrechnungsfall kann mehrere Kontakte umfassen (z.B. vorstationärer Besuch, stationärer Aufenthalt und nachstationärer Besuch).
+
Gemeinsam mit dem Einrichtungskontakt bildet der Abrechnungsfall einen wichtigen Einstiegspunkt in die Dokumentation der Behandlungsleistungen der Patienten.
+Als Bindeglied zwischen den Kontakten und dem Versicherungsverhältnis erfolgt eine feingranulare Auflistung, in welchen Zeiträumen ein Behandlungskontext zwischen einer Gesundheitseinrichtung und der Patienten bestand.
+Zudem werden Diagnosen abschließend / nachträglich dokumentiert, sodass eine Übersicht von relevanten (DRG)-Diagnosen ermöglicht wird, ohne die Gesamtheit aller Kontakte betrachten zu müssen.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Profil.html
new file mode 100644
index 00000000..df44fa5c
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Abrechnungsfall-Abrechnungsfall_Profil.html
@@ -0,0 +1,507 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
rim:Account
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Account.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Account.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Fallbezogene Abrechnungsrelevanz von Diagnosen und Prozeduren
Alternate names
extensions, user content
Definition
Optional Extension Element - found in all resources.
+
Comments
In dieser Extension SOLL das 'Use' Element nur einfach verwendet werden, um eine eindeutige Zuweisung (1 zu N) gegenüber dem Element 'Referenz' zu gewährleisten.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Account.status
Short description
active | inactive | entered-in-error | on-hold | unknown
Definition
Indicates whether the account is presently used/usable or not.
+
Comments
This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid.
Categorizes the account for reporting and searching purposes.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Identifies the entity which incurs the expenses. While the immediate recipients of services or goods might be entities related to the subject, the expenses were ultimately incurred by the subject of the Account.
+
Comments
Accounts can be applied to non-patients for tracking other non-patient related activities, such as group services (patients not tracked, and costs charged to another body), or might not be allocated.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.coverage
Short description
The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account
Definition
The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account.
+
Comments
Typically. this may be some form of insurance, internal charges, or self-pay.
+
Local or jurisdictional business rules may determine which coverage covers which types of billable items charged to the account, and in which order.
+Where the order is important, a local/jurisdictional extension may be defined to specify the order for the type of charge.
There are no (further) constraints on this element
Element Id
Account.coverage.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Account.coverage.coverage
Short description
The party(s), such as insurances, that may contribute to the payment of this account
Definition
The party(s) that contribute to payment (or part of) of the charges applied to this account (including self-pay).
+
A coverage may only be responsible for specific types of charges, and the sequence of the coverages in the account could be important when processing billing.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.coverage.priority
Short description
The priority of the coverage in the context of this account
Alternate names
coordination of benefit priority
Definition
The priority of the coverage in the context of this account.
+
Comments
It is common in some jurisdictions for there to be multiple coverages allocated to an account, and a sequence is required to order the settling of the account (often with insurance claiming).
There are no (further) constraints on this element
Element Id
Account.owner
Short description
Entity managing the Account
Definition
Indicates the service area, hospital, department, etc. with responsibility for managing the Account.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.guarantor.party
Short description
Responsible entity
Definition
The entity who is responsible.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.guarantor.period
Short description
Guarantee account during
Definition
The timeframe during which the guarantor accepts responsibility for the account.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Account.partOf
Short description
Reference to a parent Account
Definition
Reference to a parent Account.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Kompatibilitaet.html
new file mode 100644
index 00000000..e661b588
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Kompatibilitaet.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKAngehoeriger wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Motivation.html
new file mode 100644
index 00000000..cc61e61e
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Motivation.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Der Angehörige wird vor allem im Zusammenhang mit Anwendungsszenarien verwendet, in denen das Versicherungsverhältnis eine Rolle spielt. Hier können Angehörige, bspw. der hauptversicherte Elternteil eines minderjährigen Kindes, in der Familienversicherung sein. In Selbstzahler-Szenarien können Angehörige die Zahler für eine im Krankenhaus erbrachte Leistung sein.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Profil.html
new file mode 100644
index 00000000..2b984033
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Angehoeriger-Angehoeriger_Profil.html
@@ -0,0 +1,795 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A person that is related to a patient, but who is not a direct target of care
Definition
Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
relatedp-de-1:Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
There are no (further) constraints on this element
Element Id
RelatedPerson.identifier
Short description
A human identifier for this person
Definition
Identifier for a person within a particular scope.
+
Requirements
People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
RelatedPerson.patient
Short description
The patient this person is related to
Definition
The patient this person is related to.
+
Requirements
We need to know which patient this RelatedPerson is related to.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:PID-3
rim:scoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
RelatedPerson.relationship
Short description
The nature of the relationship
Definition
The nature of the relationship between a patient and the related person.
+
Requirements
We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
RelatedPerson.telecom
Short description
A contact detail for the person
Definition
A contact detail for the person, e.g. a telephone number or an email address.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.
There are no (further) constraints on this element
Element Id
RelatedPerson.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Address where the related person can be contacted or visited
Definition
Address where the related person can be contacted or visited.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
RelatedPerson.photo
Short description
Image of the person
Definition
Image of the person.
+
Requirements
Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.
+
Comments
When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
There are no (further) constraints on this element
Element Id
RelatedPerson.period
Short description
Period of time that this relationship is considered valid
Definition
The period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication
Short description
A language which may be used to communicate with about the patient's health
Definition
A language which may be used to communicate with about the patient's health.
+
Requirements
If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.
+
Comments
If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication.language
Short description
The language which can be used to communicate with the patient about his or her health
Definition
The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.
+
Requirements
Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication.preferred
Short description
Language preference indicator
Definition
Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).
+
Requirements
People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.
+
Comments
This language is specifically identified for communicating healthcare information.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
rim:preferenceInd
+
key
severity
human
expression
relatedp-de-1
error
Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden
gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..82ffb04c
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,337 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support-Feldern
+
Composition.id
+
Bedeutung: Subsystem-interne Datensatz-ID
+
Composition.profile
+
Bedeutung: Erklärung zur Konformität zum ISiK-Profil
+
Composition.text
+
Bedeutung: menschenlesbare Repräsentation des Dokumentenkopfes (Metadaten)
+
Hinweise: Die Mindestanforderungen an den Inhalt der menschenlesbaren Repräsentation umfasst folgende Informationen:
+
+
Composition.subject:Patient.name.family
+
Composition.subject:Patient.birthDate
+
Composition.subject:Patient.identifier:pid
+
Composition.status
+
Composition.type.text
+
Composition.date
+
Composition.title
+
Composition.author.display
+
+
Composition.identifier
+
Bedeutung: Subsystem-seitig zugewiesener Identifier des Berichtes mit Angabe der URL des vom Subsystem verwendeten Namensraumes
+
Hinweise: Werden eigene Identifier bzw. NamingSystems verwendet, so sei auf den Leitfaden der Basisprofile Deutschland (HL7 Deutschland) zu den Best-Practices bei Namensräumen verwiesen.
+
Dazu ein Beispiel für einen Identifier eines Sub-System-Berichts:
Hinweise: In der aktuellen Ausbaustufe von ISiK ist textuelle Repräsentation des Dokumenttyps (type.text) ausreichend. Die darüber hinausgehende Codierung des Dokumenttyps (z.B. mit LOINC, IHE-Typecodes oder KDL) in type.coding KANN implementiert werden
+
Composition.subject
+
Bedeutung: Patientenbezug des Dokumentes
+
Composition.encounter
+
Bedeutung: Fallbezug des Dokumentes
+
Composition.date
+
Bedeutung: Datum der letzten Änderung am Dokument
+
Composition.author.display
+
Bedeutung: Autor des Dokumentes (Person, Subsystem)
+
Hinweise: In der aktuellen Ausbaustufe von ISiK ist die Verwendung der textuellen Repräsentation (display) von Autor und Subsystem ausreichend. Die darüber hinaus gehende Verlinkung auf Practitioner bzw. Device-Ressourcen KANN implementiert werden.
+
Composition.title
+
Bedeutung: Dokumentenbezeichnung
+
Hinweise: Die Dokumentenbezeichnung dient der Darstellung des Dokumentes in einer Übersicht, z.B. in einer Patientenakte, und KANN der schnellen Auffindbarkeit eines gesuchten Dokumentes dienen. Geeignete Bezeichnungen sind zum Beispiel
+
+
"Kleines Blutbild vom 13.10.2020"
+
"Pathologiebefund (Abstrich) vom 13.10.2020"
+
"Blutgasmessung vom 13.10.2020 14:14h"
+
+
Composition.section.title
+
Bedeutung: Kapitelüberschrift
+
Composition.section.text
+
Bedeutung: menschenlesbare Repräsentation des Inhalts eines Kapitels
+
Hinweise: Für Aggregation einer vollständigen menschenlesbaren Repräsentation MÜSSEN die Repräsentationen der einzelnen Kapitel an die Repräsentation der Metadaten (Composition.text) angehängt werden. Für die Separierung KÖNNEN einfache <div>-Tags verwendet werden.
+Es ist zu beachten, dass Kapitel auch Unterkapitel enthalten KÖNNEN (Composition.section.section), die bei der Aggregation entsprechend berücksichtigt werden MÜSSEN.
+
Die Mindestanforderungen an den Inhalt der menschenlesbaren Repräsentation umfasst folgende Informationen:
+
+
section.title + Freitext oder
+
section.title + Resource.text der referenzierten Ressource oder
+
section.title + eine aggregierte Repräsentation von Resource.text wenn in einer Section mehrere Ressourcen referenziert werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Beispiele.html
new file mode 100644
index 00000000..38c19feb
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Beispiele.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Das Bundle dient der Aggregation aller Ressourcen, die Bestandteil des Dokumentes sind. Dabei ist die erste Ressource im Bundle (Bundle.entry.resource) stets eine Composition, alle weiteren Entries enthalten zusätzliche Ressourcen, auf die die Composition verweist.
+
Falls die im Dokumenten-Bundle enthaltene Patient-Ressource und/oder Encounter-Ressource nicht anhand der Business-Identifier oder anderer Matching-Kriterien im empfangenden System gefunden werden kann (d.h. der Patient oder der Encounter existiert im empfangenden System noch nicht), MUSS als Antwort der HTTP Status Code "422 - Unprocessable Entity" zurückgegeben werden. Im Body der Response ist eine OperationOutcome zurückzugeben, welche ein Issue mit dem Verweis auf die nicht auflösbare Referenz enthält. Zur Kodierung von OperationOutcome.issue.code MUSS als Code "processing" verwendet werden.
bdl-7:FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) (type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()
bdl-9:A document must have an identifier with a system and a value type = 'document' implies (identifier.system.exists() and identifier.value.exists())
bdl-3:entry.request mandatory for batch/transaction/history, otherwise prohibited entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))
bdl-4:entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))
bdl-12:A message must have a MessageHeader as the first resource type = 'message' implies entry.first().resource.is(MessageHeader)
bdl-1:total only when a search or history total.empty() or (type = 'searchset') or (type = 'history')
bdl-2:entry.search only when a search entry.search.empty() or (type = 'searchset')
bdl-11:A document must have a Composition as the first resource type = 'document' implies entry.first().resource.is(Composition)
bdl-10:A document must have a date type = 'document' implies (timestamp.hasValue())
ISiK-docBundle-1:All referenced Resources must be contained in the Bundle Bundle.entry.descendants().reference.distinct().subsetOf(%context.entry.fullUrl)
There are no (further) constraints on this element
Element Id
Bundle.identifier
Short description
Persistent identifier for the bundle
Definition
A persistent identifier for the bundle that won't change as a bundle is copied from server to server.
+
Comments
Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Indicates the purpose of this bundle - how it is intended to be used.
+
Comments
It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types.
There are no (further) constraints on this element
Element Id
Bundle.timestamp
Short description
When the bundle was assembled
Definition
The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.
+
Comments
For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
+
Usage:
+
+
document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
+
message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
+
history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
+
searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
+
transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
+
+
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.
There are no (further) constraints on this element
Element Id
Bundle.total
Short description
If search, the total number of matches
Definition
If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle.
+
Comments
Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.
There are no (further) constraints on this element
Element Id
Bundle.link
Short description
Links related to this Bundle
Definition
A series of links that provide context to this bundle.
+
Comments
Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS).
+
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly.
+
This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.
There are no (further) constraints on this element
Element Id
Bundle.entry.fullUrl
Short description
URI for resource (Absolute URL server address or URI for UUID/OID)
Definition
The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
+
+
fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
+
Results from operations might involve resources that are not identified.
+
+
Comments
fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id.
+
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).
There are no (further) constraints on this element
Element Id
Bundle.entry.request
Short description
Additional execution information (transaction/batch/history)
Definition
Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.
There are no (further) constraints on this element
Element Id
Bundle.entry.response
Short description
Results of execution (transaction/batch/history)
Definition
Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.fullUrl
Short description
URI for resource (Absolute URL server address or URI for UUID/OID)
Definition
The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
+
+
fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
+
Results from operations might involve resources that are not identified.
+
+
Comments
fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id.
+
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).
A set of resources composed into a single coherent clinical statement with clinical attestation
Definition
A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
+
Comments
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Document[classCode="DOC" and moodCode="EVN" and isNormalAct()]
cda:ClinicalDocument
fhirdocumentreference:when described by DocumentReference
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.search.mode
Short description
match | include | outcome - why this is in the result set
Definition
Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
+
Comments
There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.
Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.search.score
Short description
Search ranking (between 0 and 1)
Definition
When searching, the server's search ranking score for the entry.
+
Comments
Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
+
See Patient Match for the EMPI search which relates to this element.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request
Short description
Additional execution information (transaction/batch/history)
Definition
Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.url
Short description
URL for HTTP equivalent of this entry
Definition
The URL for this entry, relative to the root (the address to which the request is posted).
+
Comments
E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.ifModifiedSince
Short description
For managing cache currency
Definition
Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read".
+
Comments
Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.ifNoneExist
Short description
For conditional creates
Definition
Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?").
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response
Short description
Results of execution (transaction/batch/history)
Definition
Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response.status
Short description
Status response code (text optional)
Definition
The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response.outcome
Short description
OperationOutcome with hints and warnings (for batch/transaction)
Definition
An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.
+
Comments
For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
+
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.
There are no (further) constraints on this element
Element Id
Bundle.signature
Short description
Digital Signature
Definition
Digital Signature - base64 encoded. XML-DSig or a JWT.
+
Requirements
A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient.
+
Comments
The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.
Hinweis: Die nachfolgenden Regeln für die Verarbeitung eines Dokumentes gelten nur für Document-Bundles die an den oben genannten Endpunkt gesendet werden. Weitere ISiK-Module können Regeln für die Verarbeitung von anderen Bundle-Typen (z.B. 'transaction') aufstellen.
+
In der aktuellen Ausbaustufe von ISiK MUSS ein empfangenes Dokument in folgenden Schritten verarbeitet werden:
+
+
Extraktion der Patient-Ressource aus dem Bundle und Herstellung des Patientenbezuges anhand eines eindeutigen Identifiers ('Patient.identifier') oder ähnlich identifizieren Merkmalen
+
Extraktion der Encounter.Ressource aus dem Bundle und Herstellung des Fallbezuges anhand der Abrechnungsfallnummer ('Encounter.account.identifier') oder ähnlich identifizieren Merkmalen
+
Extraktion der Composition-Ressource aus dem Bundle und Auslesen der mit 'mustSupport' gekennzeichneten Meta-Daten, sowie der menschenlesbaren Repräsentation des Dokumentes ('Composition.text', 'Composition.section.text', 'Composition.section.section.text')
+
Hinzufügen des Dokumentes und seiner Metadaten zur Fallakte des Patienten.
+
Visualisierung des Dokumentes und seiner Metadaten in der Fallakte des Patienten
+
+
+
Die Grafik zeigt an einem vereinfachten Beispiel die Zuordnung des HTML-Dokumentes zu Patient und Kontakt in der aktuellen Ausbaustufe von ISiK (schwarze Pfeile). Die grauen Pfeile deuten die Übernahme strukturierter Daten, wie sie in weiteren Ausbaustufen erforderlich wird.
+
Hinweise zum Umgang mit der menschenlesbaren Repräsentation
+
Die menschenlesbare Repräsentation ("Narrative") eines Dokumentes setzt sich zusammen aus dem Inhalt von 'Composition.text', einer Repräsentation der Metadaten (z.B. Dokumenttyp, Patientenname, Patientennummer, Aufnahmenummer, Datum) sowie der Aggregation der Inhalte von 'Composition.section', wobei zu beachten ist, dass ein Dokument beliebig viele Sections haben kann.
+Die einzelnen Bestandteile des Narratives KÖNNEN mit <div>-Elementen zusammengefügt werden.
+
Extraktion der Patient-/ und Encounter-Ressource im Document-Bundle
+
Folgende Fälle sind zu beachten um eine Patient-/ und Encounter-Ressource aus dem Document-Bundle zu extrahieren:
+
+
Die aufzulösende Referenz ist eine URN (immer absolut, z. B. "urn:uuid:9d1714da-b7e6-455b-bfd2-69ce0ff5fb12"):
+
+
Suche nach einem Bundle-Entry mit einer fullUrl, die mit dem reference.value übereinstimmt
+
Wenn einer gefunden wird, ist die Auflösung erfolgreich (und endet hier)
+
Andernfalls schlägt die Auflösung fehl (und endet hier). Die Referenz hat in dieser Spezifikation keine definierte Bedeutung.
+
+
+
Wenn die Referenz eine absolute URL ist (z. B. "https://fhir.example.org/base/Patient/123", "https://fhir.example.org/base/Patient/123/_history/a"):
+
+
Suche nach einem Bundle-Entry mit einer fullUrl, die mit dem reference.value übereinstimmt
+
Wenn einer gefunden wird, ist die Auflösung hier erfolgreich (und endet)
+
Wird mehr als ein Eintrag gefunden, KANN der Server nach der neuesten Version suchen (basierend auf meta.lastUpdated). Wenn jener auf diese Weise genau eine aktuelle Version findet, ist die Auflösung erfolgreich (und endet hier)
+
+
+
Wenn die Referenz die Form "[Typ]/[id]" hat (z. B. "Patient/123")
+
+
Wenn der Bundle-Entry, der den Verweis enthält, eine FullUrl hat, die dem RESTful-URL-Regex entspricht (z. B. "https://fhir.example.org/Observation/456"):
+
+
Extrahiert wird die [root] aus der fullUrl des Bundle-Entries und mit der relative Referenz zusammenangefügt (z. B. "https://fhir.example.org/" + "Patient/123" --> "https://fhir.example.org/Patient/123")
+
Gefolgt wird den Schritten für die Auflösung absoluter Referenzen. Siehe oben.
+
+
+
+
+
+
Persistierung der menschenlesbaren Repräsentation
+
Das Narrative der Ressource KANN innerhalb einer DocumentReference-Ressource persistiert werden. Zum derzeitigen Zeitpunkt obliegt es der jeweiligen Implementierung wie diese DocumentReference Ressource ausgestaltet ist.
+Ein Mapping der Composition-Metadaten auf DocumentReference-Metadaten KANN der FHIR Kernspezifikation entnommen werden. Siehe Abschnitt "2.42.8.7 FHIR Composition".
+
Das Narrative MUSS als Binary-Ressource unter DocumentReference.content.attachment.url angegeben werden.
+
Hinweis: Es ist zu beachten, dass in einem Attachment-Datentyp im Element "url" eine absolute URL anzugeben ist. Somit muss zunächst das Binary auf dem externen System per POST angelegt werden. Der hieraus resultierende Link kann anschließend im Attachment verwendet werden.
+
Falls ein Bundle erneut mit dem gleichen Bundle.identifier übermittelt wird, MUSS eine neue DocumentReference erstellt werden, welche unter DocumentReference.relatesTo.target angegeben wird.
+
Hinweise zum Umgang mit strukturierten Daten
+
Auch wenn in der aktuellen Stufe nur die Übernahme der menschenlesbaren Repräsentation erforderlich ist, empfiehlt es sich dennoch, das vollständige Bundle samt der strukturierten Anteile zu einem Dokument zu persistieren, sodass zu einem späteren Zeitpunkt, wenn eine Übernahme einzelner Daten möglich ist, diese auch rückwirkend erfolgen kann.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Motivation.html
new file mode 100644
index 00000000..08be794b
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-BerichtSubsystem-BerichtSubsystem_Motivation.html
@@ -0,0 +1,273 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
In der heterogenen Systemlandschaft im Krankenhaus sind eine Vielzahl spezialisierter Subsysteme im Einsatz. Die Ergebnisse aus diesen Subsystemen sind aktuell jedoch häufig nicht in den Primärsystemen des Krankenhauses verfügbar, denn es bestehen folgende Herausforderungen:
+
+
Die Daten in Subsystemen sind sehr heterogen und können hochspezialisiert sein.
+
Bei der Nutzung dieser Subsysteme besteht häufig ein Interesse, auf die menschenlesbare Repräsentation der strukturierten Daten einwirken zu können.
+
Künftig ist mit Szenarien zu rechnen, bei denen Befunde aus Subsystemen in eine elektronische Patientenakte übertragen werden sollen.
+
Aktuell werden Befunde, obwohl diese in den Subsystemen in hochstrukturierter Form vorliegen, nur als PDF an das Primärsystem zurückübermittelt. Oft weil kein strukturiertes Format spezifiziert ist, das sowohl versendendes Subsystem als auch empfangendes Primärsystem implementiert haben.
+
Der Umfang, in dem eine Datenübernahme in ein Primärsystem möglich ist, variiert stark zwischen den Systemen oder Installationen, z.B. abhängig davon, ob ein Modul für Vitalparameter installiert ist.
+
+
Die ISiK-Spezifikation begegnet diesen Herausforderungen, indem sie die Rückübermittlung von Ergebnissen aus Subsystemen an die Primärsysteme in Form von strukturierten Dokumenten erfordert, die über eine menschenlesbare Repräsentation verfügen. Diese strukturierten Dokumente werden im ISiK-Kontext als Berichte bezeichnet. Dabei sind die strukturierten Inhalte der Berichte harmonisiert mit den verbreiteten Formaten für Primärsysteme.
+
In der aktuellen Ausbaustufe von ISiK ist lediglich die Übernahme und Anzeige der Dokument-Metadaten (z.B. Dokumenttyp, Dokumentdatum, Quelle) und der menschenlesbaren HTML-Repräsentation in die Primärsysteme erforderlich.
+
In weiteren Ausbaustufen von ISiK soll darüber hinaus eine Übernahme der strukturierten Anteile der Dokumente möglich sein, die den ISiK-Spezifikationen entsprechen, z.B. Diagnosen und Prozeduren.
+
Es obliegt dabei dem Ermessen des Herstellers, ob die Übernahme strukturierter Daten in das Primärsystem automatisch erfolgt, oder durch den Benutzer initiiert wird.
There are no (further) constraints on this element
Element Id
Composition
Short description
A set of resources composed into a single coherent clinical statement with clinical attestation
Definition
A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
+
Comments
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Document[classCode="DOC" and moodCode="EVN" and isNormalAct()]
cda:ClinicalDocument
fhirdocumentreference:when described by DocumentReference
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Composition.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Composition.text
Short description
Text summary of the resource, for human interpretation
Alternate names
narrative, html, xhtml, display
Definition
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
+
Comments
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
txt-1:The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes htmlChecks()
txt-2:The narrative SHALL have some non-whitespace content htmlChecks()
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.identifier.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Composition.identifier.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Composition.identifier.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.identifier.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Composition.identifier.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
+
Requirements
Need to be able to mark interim, amended, or withdrawn compositions or documents.
+
Comments
If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
+
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Fixed Value
+
final
Mappings
rim:n/a
workflow:Event.status
w5:FiveWs.status
rim:interim: .completionCode="IN" & ./statusCode[isNormalDatatype()]="active"; final: .completionCode="AU" && ./statusCode[isNormalDatatype()]="complete" and not(./inboundRelationship[typeCode="SUBJ" and isNormalActRelationship()]/source[subsumesCode("ActClass#CACT") and moodCode="EVN" and domainMember("ReviseComposition", code) and isNormalAct()]); amended: .completionCode="AU" && ./statusCode[isNormalDatatype()]="complete" and ./inboundRelationship[typeCode="SUBJ" and isNormalActRelationship()]/source[subsumesCode("ActClass#CACT") and moodCode="EVN" and domainMember("ReviseComposition", code) and isNormalAct() and statusCode="completed"]; withdrawn : .completionCode=NI && ./statusCode[isNormalDatatype()]="obsolete"
There are no (further) constraints on this element
Element Id
Composition.type
Short description
Kind of composition (LOINC if possible)
Definition
Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition.
+
Requirements
Key metadata element describing the composition, used in searching/filtering.
+
Comments
For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:KDL.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:KDL.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Composition.category
Short description
Categorization of Composition
Definition
A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.
+
Requirements
Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.category.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure).
+
Requirements
Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about.
+
Comments
For clinical documents, this is usually the patient.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Composition.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Composition.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Composition.encounter
Short description
Context of the Composition
Definition
Describes the clinical encounter or type of care this documentation is associated with.
+
Requirements
Provides context for the composition and supports searching.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.context
w5:FiveWs.context
rim:unique(highest(./outboundRelationship[typeCode="SUBJ" and isNormalActRelationship()], priorityNumber)/target[moodCode="EVN" and classCode=("ENC", "PCPR") and isNormalAct])
There are no (further) constraints on this element
Element Id
Composition.date
Short description
Composition editing time
Definition
The composition editing time, when the composition was last logically changed by the author.
+
Requirements
dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring. When packaged in a document, Bundle.timestamp is the date of packaging.
+
Comments
The Last Modified Date on the composition may be after the date of the document was attested without being changed.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
+
Requirements
Identifies who is responsible for the content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.author.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Composition.author.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Composition.author.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.author.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Composition.title
Short description
Human Readable name/title
Definition
Official human-readable label for the composition.
+
Comments
For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.
There are no (further) constraints on this element
Element Id
Composition.confidentiality
Short description
As defined by affinity domain
Definition
The code specifying the level of confidentiality of the Composition.
+
Comments
The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.
There are no (further) constraints on this element
Element Id
Composition.attester.party
Short description
Who attested the composition
Definition
Who attested the composition in the specified way.
+
Requirements
Identifies who has taken on the responsibility for accuracy of the composition content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.witness
rim:./role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()] or ./role[classCode="ASSIGNED" and isNormalRole and not(player)]/scoper[determinerCode="INST" and classCode="ORG" and isNormalEntity()]
There are no (further) constraints on this element
Element Id
Composition.custodian
Short description
Organization which maintains the composition
Definition
Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.
+
Requirements
Identifies where to go to find the current version, where to report issues, etc.
+
Comments
This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.participation[typeCode="RCV"].role[classCode="CUST"].scoper[classCode="ORG" and determinerCode="INST"]
There are no (further) constraints on this element
Element Id
Composition.event.code
Short description
Code(s) that apply to the event being documented
Definition
This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.
+
Comments
An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.
There are no (further) constraints on this element
Element Id
Composition.event.period
Short description
The period covered by the documentation
Definition
The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Composition.event.detail
Short description
The event(s) being documented
Definition
The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.section.title
Short description
Label for section (e.g. for ToC)
Alternate names
header, label, caption
Definition
The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents.
+
Requirements
Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
+
Comments
The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.
There are no (further) constraints on this element
Element Id
Composition.section.code
Short description
Classification of section (recommended)
Definition
A code identifying the kind of content contained within the section. This must be consistent with the section title.
+
Requirements
Provides computable standardized labels to topics within the document.
+
Comments
The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
+
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.
There are no (further) constraints on this element
Element Id
Composition.section.author
Short description
Who and/or what authored the section
Definition
Identifies who is responsible for the information in this section, not necessarily who typed it in.
+
Requirements
Identifies who is responsible for the content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.section.focus
Short description
Who/what the section is about, when it is not about the subject of composition
Definition
The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources).
+
Comments
Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
cda:.subject? (CDA did not differentiate between subject and focus)
There are no (further) constraints on this element
Element Id
Composition.section.text
Short description
Text summary of the section, for human interpretation
Definition
A human-readable narrative that contains the attested content of the section, 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.
+
Comments
Document profiles may define what content should be represented in the narrative to ensure clinical safety.
There are no (further) constraints on this element
Element Id
Composition.section.mode
Short description
working | snapshot | changes
Definition
How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.
+
Requirements
Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
+
Comments
This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
There are no (further) constraints on this element
Element Id
Composition.section.orderedBy
Short description
Order of section entries
Definition
Specifies the order applied to the items in the section entries.
+
Requirements
Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries.
+
Comments
Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.outboundRelationship[typeCode=COMP] or .participation[typeCode=SBJ]
There are no (further) constraints on this element
Element Id
Composition.section.emptyReason
Short description
Why the section is empty
Definition
If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
+
Requirements
Allows capturing things like "none exist" or "not asked" which can be important for most lists.
+
Comments
The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Interaktionen.html b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Interaktionen.html
new file mode 100644
index 00000000..2e18372e
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Interaktionen.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Interaktionen
+
Für die Ressource Binary MUSS die REST-Interaktion "READ" implementiert werden. Es MÜSSEN die Regeln aus der FHIR-Kernspezifikation zur Abfrage einer Binary Ressource beachtet werden. Siehe "Serving Binary Resources using the RESTful API".
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Motivation.html
new file mode 100644
index 00000000..b415ecdf
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Motivation.html
@@ -0,0 +1,267 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Die Binary-Ressource erlaubt den Umgang mit FHIR-fremden Formaten (z.B. PDFs, Bilder, CDA) innerhalb des FHIR-Frameworks.
+Dazu werden die Daten base64-codiert in der Binary-Ressource (in XML oder JSON) transportiert oder
+über die REST-API am Binary-Endpunkt in ihrem nativen Format bereitgestellt.
+Binary-Ressourcen werden von Attachment-Elementen verlinkt und damit in den Kontext anderer FHIR-Ressourcen
+(z.B. Patient und Encounter) gestellt.
+
Das ISIK-Binary-Profil ist nicht Bestandteil der Implementierung des ISIK Basismoduls.
+Das Profil ist Teil des ISIK Basismoduls, da es als übergreifend genutzte Ressource sowohl im Modul Terminplanung als auch im Modul Dokumentenaustausch implementiert werden muss.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Profil.html
new file mode 100644
index 00000000..ee4b4dbc
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Binary-Binary_Profil.html
@@ -0,0 +1,306 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
There are no (further) constraints on this element
Element Id
Binary
Short description
Pure binary content defined by a format other than FHIR
Definition
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.
+
Comments
Typically, Binary resources are used for handling content such as:
+
+
CDA Documents (i.e. with XDS)
+
PDF Documents
+
Images (the Media resource is preferred for handling images, but not possible when the content is already binary - e.g. XDS).
There are no (further) constraints on this element
Element Id
Binary.securityContext
Short description
Identifies another resource to use as proxy when enforcing access control
Definition
This element identifies another resource that can be used as a proxy of the security sensitivity to use when deciding and enforcing access control rules for the Binary resource. Given that the Binary resource contains very few elements that can be used to determine the sensitivity of the data and relationships to individuals, the referenced resource stands in as a proxy equivalent for this purpose. This referenced resource may be related to the Binary (e.g. Media, DocumentReference), or may be some non-related Resource purely as a security proxy. E.g. to identify that the binary resource relates to a patient, and access should only be granted to applications that have access to the patient.
+
Comments
Very often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type.
Das CapabilityStatement in dieser Spezifikation stellt die Anforderungen seitens der gematik dar (kind = "requirements"). Zur Unterscheidung von Anforderungen, die erfüllt werden MÜSSEN gegenüber jenen, die erfüllt werden KÖNNEN, wird die CapabilityStatement-Expectation-Extension mit den möglichen Werten "SHALL" (=MUSS) und "MAY" (=KANN) verwendet.
+
Eine Server-Instanz MUSS ihrerseits ein CapabilityStatement vom kind= "instance" liefern und im Element software den Namen und die Versionsnummer angeben.
+Darüber hinaus MUSS in CapabilityStatement.instantiates die Canonical URL des nachfolgenden CapabilityStatement in der jeweiligen CapabilityStatement Instanz angegeben werden.
+
Das CapabilityStatement der Instanz MUSS alle Funktionalitäten auflisten, die im folgenden CapabilityStatement mit "SHALL" gekennzeichnet sind. Das CapabilityStatement KANN darüber hinaus die mit "MAY" gekennzeichneten Funktionalitäten, sowie weitere Funktionalitäten auflisten, sofern diese in der Instanz implementiert wurden.
+
Die Verwendung der CapabilityStatement-Expectation-Extension ist im CapabilityStatement der Server-Instanz nicht erforderlich.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte.html b/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte.html
new file mode 100644
index 00000000..db33e0e5
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Datenobjekte
+
In den folgenden Unterkapiteln werden die ISiK-Datenobjekte, die in dem vereinfachten Informationsmodell dargestellt sind, und ihre FHIR-Spezifikation beschrieben.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte_Abrechnungsfall.html b/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte_Abrechnungsfall.html
new file mode 100644
index 00000000..b0e230b2
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Datenobjekte-Datenobjekte_Abrechnungsfall.html
@@ -0,0 +1,662 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Komplementär zum Datenobjekt "Kontakt - Encounter" können Fälle, im Sinne einer Gruppierung von medizinischen Leistungen, innerhalb eines gemeinsamen Kontextes, zu einem Abrechnungsfall zusammengefasst werden.
+Ein solcher Abrechnungsfall kann mehrere Kontakte umfassen (z.B. vorstationärer Besuch, stationärer Aufenthalt und nachstationärer Besuch).
+
Gemeinsam mit dem Einrichtungskontakt bildet der Abrechnungsfall einen wichtigen Einstiegspunkt in die Dokumentation der Behandlungsleistungen der Patienten.
+Als Bindeglied zwischen den Kontakten und dem Versicherungsverhältnis erfolgt eine feingranulare Auflistung, in welchen Zeiträumen ein Behandlungskontext zwischen einer Gesundheitseinrichtung und der Patienten bestand.
+Zudem werden Diagnosen abschließend / nachträglich dokumentiert, sodass eine Übersicht von relevanten (DRG)-Diagnosen ermöglicht wird, ohne die Gesamtheit aller Kontakte betrachten zu müssen.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKAbrechnungsfall wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
rim:Account
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Account.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Account.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Fallbezogene Abrechnungsrelevanz von Diagnosen und Prozeduren
Alternate names
extensions, user content
Definition
Optional Extension Element - found in all resources.
+
Comments
In dieser Extension SOLL das 'Use' Element nur einfach verwendet werden, um eine eindeutige Zuweisung (1 zu N) gegenüber dem Element 'Referenz' zu gewährleisten.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Account.identifier:Abrechnungsnummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Account.status
Short description
active | inactive | entered-in-error | on-hold | unknown
Definition
Indicates whether the account is presently used/usable or not.
+
Comments
This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid.
Categorizes the account for reporting and searching purposes.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Identifies the entity which incurs the expenses. While the immediate recipients of services or goods might be entities related to the subject, the expenses were ultimately incurred by the subject of the Account.
+
Comments
Accounts can be applied to non-patients for tracking other non-patient related activities, such as group services (patients not tracked, and costs charged to another body), or might not be allocated.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.coverage
Short description
The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account
Definition
The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account.
+
Comments
Typically. this may be some form of insurance, internal charges, or self-pay.
+
Local or jurisdictional business rules may determine which coverage covers which types of billable items charged to the account, and in which order.
+Where the order is important, a local/jurisdictional extension may be defined to specify the order for the type of charge.
There are no (further) constraints on this element
Element Id
Account.coverage.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Account.coverage.coverage
Short description
The party(s), such as insurances, that may contribute to the payment of this account
Definition
The party(s) that contribute to payment (or part of) of the charges applied to this account (including self-pay).
+
A coverage may only be responsible for specific types of charges, and the sequence of the coverages in the account could be important when processing billing.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.coverage.priority
Short description
The priority of the coverage in the context of this account
Alternate names
coordination of benefit priority
Definition
The priority of the coverage in the context of this account.
+
Comments
It is common in some jurisdictions for there to be multiple coverages allocated to an account, and a sequence is required to order the settling of the account (often with insurance claiming).
There are no (further) constraints on this element
Element Id
Account.owner
Short description
Entity managing the Account
Definition
Indicates the service area, hospital, department, etc. with responsibility for managing the Account.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.guarantor.party
Short description
Responsible entity
Definition
The entity who is responsible.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Account.guarantor.period
Short description
Guarantee account during
Definition
The timeframe during which the guarantor accepts responsibility for the account.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Account.partOf
Short description
Reference to a parent Account
Definition
Reference to a parent Account.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Bedeutung: DRG- und hiervon abweichende Krankenhausdiagnosen sollten im Account zusammenfassend und abschließend angegeben werden. Relevante Prozeduren können ebenfalls aufgelistet werden.
+
Account.identifier
+
Bedeutung: Der Account muss die Abrechnungsnummer des referenzierenden Kontaktes (Encounter) enthalten. Dies entspricht dem Wert des Elements Encounter.account.identifier.
+
Account.status
+
Bedeutung: Der Status MUSS insbesondere zur Differenzierung von abgeschlossenen und derzeitig noch aktiven Abrechnungsfällen angegeben werden. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "active", "inactive". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Bedeutung: Ein Patientenbezug des Falls MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Account.coverage
+
Bedeutung: Pro Abrechnungskontext (z.B. Selbstzahler, DRG, PEPP) sollte ein eigener Account angelegt werden. Für jeden Account sollte ersichtlich sein über welche Coverage der Account beglichen werden soll.
+
+
+
+
+
Interaktionen
+
Für die Ressource Account MUSS die REST-Interaktion "READ" implementiert werden.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
Der Angehörige wird vor allem im Zusammenhang mit Anwendungsszenarien verwendet, in denen das Versicherungsverhältnis eine Rolle spielt. Hier können Angehörige, bspw. der hauptversicherte Elternteil eines minderjährigen Kindes, in der Familienversicherung sein. In Selbstzahler-Szenarien können Angehörige die Zahler für eine im Krankenhaus erbrachte Leistung sein.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKAngehoeriger wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
A person that is related to a patient, but who is not a direct target of care
Definition
Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
relatedp-de-1:Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
There are no (further) constraints on this element
Element Id
RelatedPerson.identifier
Short description
A human identifier for this person
Definition
Identifier for a person within a particular scope.
+
Requirements
People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
RelatedPerson.patient
Short description
The patient this person is related to
Definition
The patient this person is related to.
+
Requirements
We need to know which patient this RelatedPerson is related to.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:PID-3
rim:scoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
RelatedPerson.patient.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
RelatedPerson.relationship
Short description
The nature of the relationship
Definition
The nature of the relationship between a patient and the related person.
+
Requirements
We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
RelatedPerson.telecom
Short description
A contact detail for the person
Definition
A contact detail for the person, e.g. a telephone number or an email address.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.
There are no (further) constraints on this element
Element Id
RelatedPerson.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Address where the related person can be contacted or visited
Definition
Address where the related person can be contacted or visited.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
Need to keep track where the related person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
RelatedPerson.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
RelatedPerson.photo
Short description
Image of the person
Definition
Image of the person.
+
Requirements
Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.
+
Comments
When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
There are no (further) constraints on this element
Element Id
RelatedPerson.period
Short description
Period of time that this relationship is considered valid
Definition
The period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication
Short description
A language which may be used to communicate with about the patient's health
Definition
A language which may be used to communicate with about the patient's health.
+
Requirements
If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.
+
Comments
If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication.language
Short description
The language which can be used to communicate with the patient about his or her health
Definition
The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.
+
Requirements
Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
There are no (further) constraints on this element
Element Id
RelatedPerson.communication.preferred
Short description
Language preference indicator
Definition
Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).
+
Requirements
People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.
+
Comments
This language is specifically identified for communicating healthcare information.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
rim:preferenceInd
+
key
severity
human
expression
relatedp-de-1
error
Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden
gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
Rückübermittlung Bericht aus Subsystemen (Composition)
+
+
+
+
+
Motivation
+
In der heterogenen Systemlandschaft im Krankenhaus sind eine Vielzahl spezialisierter Subsysteme im Einsatz. Die Ergebnisse aus diesen Subsystemen sind aktuell jedoch häufig nicht in den Primärsystemen des Krankenhauses verfügbar, denn es bestehen folgende Herausforderungen:
+
+
Die Daten in Subsystemen sind sehr heterogen und können hochspezialisiert sein.
+
Bei der Nutzung dieser Subsysteme besteht häufig ein Interesse, auf die menschenlesbare Repräsentation der strukturierten Daten einwirken zu können.
+
Künftig ist mit Szenarien zu rechnen, bei denen Befunde aus Subsystemen in eine elektronische Patientenakte übertragen werden sollen.
+
Aktuell werden Befunde, obwohl diese in den Subsystemen in hochstrukturierter Form vorliegen, nur als PDF an das Primärsystem zurückübermittelt. Oft weil kein strukturiertes Format spezifiziert ist, das sowohl versendendes Subsystem als auch empfangendes Primärsystem implementiert haben.
+
Der Umfang, in dem eine Datenübernahme in ein Primärsystem möglich ist, variiert stark zwischen den Systemen oder Installationen, z.B. abhängig davon, ob ein Modul für Vitalparameter installiert ist.
+
+
Die ISiK-Spezifikation begegnet diesen Herausforderungen, indem sie die Rückübermittlung von Ergebnissen aus Subsystemen an die Primärsysteme in Form von strukturierten Dokumenten erfordert, die über eine menschenlesbare Repräsentation verfügen. Diese strukturierten Dokumente werden im ISiK-Kontext als Berichte bezeichnet. Dabei sind die strukturierten Inhalte der Berichte harmonisiert mit den verbreiteten Formaten für Primärsysteme.
+
In der aktuellen Ausbaustufe von ISiK ist lediglich die Übernahme und Anzeige der Dokument-Metadaten (z.B. Dokumenttyp, Dokumentdatum, Quelle) und der menschenlesbaren HTML-Repräsentation in die Primärsysteme erforderlich.
+
In weiteren Ausbaustufen von ISiK soll darüber hinaus eine Übernahme der strukturierten Anteile der Dokumente möglich sein, die den ISiK-Spezifikationen entsprechen, z.B. Diagnosen und Prozeduren.
+
Es obliegt dabei dem Ermessen des Herstellers, ob die Übernahme strukturierter Daten in das Primärsystem automatisch erfolgt, oder durch den Benutzer initiiert wird.
Das Bundle dient der Aggregation aller Ressourcen, die Bestandteil des Dokumentes sind. Dabei ist die erste Ressource im Bundle (Bundle.entry.resource) stets eine Composition, alle weiteren Entries enthalten zusätzliche Ressourcen, auf die die Composition verweist.
+
Falls die im Dokumenten-Bundle enthaltene Patient-Ressource und/oder Encounter-Ressource nicht anhand der Business-Identifier oder anderer Matching-Kriterien im empfangenden System gefunden werden kann (d.h. der Patient oder der Encounter existiert im empfangenden System noch nicht), MUSS als Antwort der HTTP Status Code "422 - Unprocessable Entity" zurückgegeben werden. Im Body der Response ist eine OperationOutcome zurückzugeben, welche ein Issue mit dem Verweis auf die nicht auflösbare Referenz enthält. Zur Kodierung von OperationOutcome.issue.code MUSS als Code "processing" verwendet werden.
bdl-7:FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) (type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()
bdl-9:A document must have an identifier with a system and a value type = 'document' implies (identifier.system.exists() and identifier.value.exists())
bdl-3:entry.request mandatory for batch/transaction/history, otherwise prohibited entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))
bdl-4:entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))
bdl-12:A message must have a MessageHeader as the first resource type = 'message' implies entry.first().resource.is(MessageHeader)
bdl-1:total only when a search or history total.empty() or (type = 'searchset') or (type = 'history')
bdl-2:entry.search only when a search entry.search.empty() or (type = 'searchset')
bdl-11:A document must have a Composition as the first resource type = 'document' implies entry.first().resource.is(Composition)
bdl-10:A document must have a date type = 'document' implies (timestamp.hasValue())
ISiK-docBundle-1:All referenced Resources must be contained in the Bundle Bundle.entry.descendants().reference.distinct().subsetOf(%context.entry.fullUrl)
There are no (further) constraints on this element
Element Id
Bundle.identifier
Short description
Persistent identifier for the bundle
Definition
A persistent identifier for the bundle that won't change as a bundle is copied from server to server.
+
Comments
Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Indicates the purpose of this bundle - how it is intended to be used.
+
Comments
It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types.
There are no (further) constraints on this element
Element Id
Bundle.timestamp
Short description
When the bundle was assembled
Definition
The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.
+
Comments
For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
+
Usage:
+
+
document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
+
message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
+
history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
+
searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
+
transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
+
+
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.
There are no (further) constraints on this element
Element Id
Bundle.total
Short description
If search, the total number of matches
Definition
If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle.
+
Comments
Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.
There are no (further) constraints on this element
Element Id
Bundle.link
Short description
Links related to this Bundle
Definition
A series of links that provide context to this bundle.
+
Comments
Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS).
+
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly.
+
This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.
There are no (further) constraints on this element
Element Id
Bundle.entry.fullUrl
Short description
URI for resource (Absolute URL server address or URI for UUID/OID)
Definition
The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
+
+
fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
+
Results from operations might involve resources that are not identified.
+
+
Comments
fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id.
+
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).
There are no (further) constraints on this element
Element Id
Bundle.entry.request
Short description
Additional execution information (transaction/batch/history)
Definition
Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.
There are no (further) constraints on this element
Element Id
Bundle.entry.response
Short description
Results of execution (transaction/batch/history)
Definition
Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.fullUrl
Short description
URI for resource (Absolute URL server address or URI for UUID/OID)
Definition
The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that:
+
+
fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle)
+
Results from operations might involve resources that are not identified.
+
+
Comments
fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id.
+
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).
A set of resources composed into a single coherent clinical statement with clinical attestation
Definition
A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
+
Comments
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Document[classCode="DOC" and moodCode="EVN" and isNormalAct()]
cda:ClinicalDocument
fhirdocumentreference:when described by DocumentReference
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.search.mode
Short description
match | include | outcome - why this is in the result set
Definition
Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
+
Comments
There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.
Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.search.score
Short description
Search ranking (between 0 and 1)
Definition
When searching, the server's search ranking score for the entry.
+
Comments
Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
+
See Patient Match for the EMPI search which relates to this element.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request
Short description
Additional execution information (transaction/batch/history)
Definition
Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.url
Short description
URL for HTTP equivalent of this entry
Definition
The URL for this entry, relative to the root (the address to which the request is posted).
+
Comments
E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.ifModifiedSince
Short description
For managing cache currency
Definition
Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read".
+
Comments
Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.request.ifNoneExist
Short description
For conditional creates
Definition
Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?").
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response
Short description
Results of execution (transaction/batch/history)
Definition
Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response.status
Short description
Status response code (text optional)
Definition
The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Bundle.entry:Composition.response.outcome
Short description
OperationOutcome with hints and warnings (for batch/transaction)
Definition
An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.
+
Comments
For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
+
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.
There are no (further) constraints on this element
Element Id
Bundle.signature
Short description
Digital Signature
Definition
Digital Signature - base64 encoded. XML-DSig or a JWT.
+
Requirements
A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient.
+
Comments
The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.
Hinweis: Die nachfolgenden Regeln für die Verarbeitung eines Dokumentes gelten nur für Document-Bundles die an den oben genannten Endpunkt gesendet werden. Weitere ISiK-Module können Regeln für die Verarbeitung von anderen Bundle-Typen (z.B. 'transaction') aufstellen.
+
In der aktuellen Ausbaustufe von ISiK MUSS ein empfangenes Dokument in folgenden Schritten verarbeitet werden:
+
+
Extraktion der Patient-Ressource aus dem Bundle und Herstellung des Patientenbezuges anhand eines eindeutigen Identifiers ('Patient.identifier') oder ähnlich identifizieren Merkmalen
+
Extraktion der Encounter.Ressource aus dem Bundle und Herstellung des Fallbezuges anhand der Abrechnungsfallnummer ('Encounter.account.identifier') oder ähnlich identifizieren Merkmalen
+
Extraktion der Composition-Ressource aus dem Bundle und Auslesen der mit 'mustSupport' gekennzeichneten Meta-Daten, sowie der menschenlesbaren Repräsentation des Dokumentes ('Composition.text', 'Composition.section.text', 'Composition.section.section.text')
+
Hinzufügen des Dokumentes und seiner Metadaten zur Fallakte des Patienten.
+
Visualisierung des Dokumentes und seiner Metadaten in der Fallakte des Patienten
+
+
+
Die Grafik zeigt an einem vereinfachten Beispiel die Zuordnung des HTML-Dokumentes zu Patient und Kontakt in der aktuellen Ausbaustufe von ISiK (schwarze Pfeile). Die grauen Pfeile deuten die Übernahme strukturierter Daten, wie sie in weiteren Ausbaustufen erforderlich wird.
+
Hinweise zum Umgang mit der menschenlesbaren Repräsentation
+
Die menschenlesbare Repräsentation ("Narrative") eines Dokumentes setzt sich zusammen aus dem Inhalt von 'Composition.text', einer Repräsentation der Metadaten (z.B. Dokumenttyp, Patientenname, Patientennummer, Aufnahmenummer, Datum) sowie der Aggregation der Inhalte von 'Composition.section', wobei zu beachten ist, dass ein Dokument beliebig viele Sections haben kann.
+Die einzelnen Bestandteile des Narratives KÖNNEN mit <div>-Elementen zusammengefügt werden.
+
Extraktion der Patient-/ und Encounter-Ressource im Document-Bundle
+
Folgende Fälle sind zu beachten um eine Patient-/ und Encounter-Ressource aus dem Document-Bundle zu extrahieren:
+
+
Die aufzulösende Referenz ist eine URN (immer absolut, z. B. "urn:uuid:9d1714da-b7e6-455b-bfd2-69ce0ff5fb12"):
+
+
Suche nach einem Bundle-Entry mit einer fullUrl, die mit dem reference.value übereinstimmt
+
Wenn einer gefunden wird, ist die Auflösung erfolgreich (und endet hier)
+
Andernfalls schlägt die Auflösung fehl (und endet hier). Die Referenz hat in dieser Spezifikation keine definierte Bedeutung.
+
+
+
Wenn die Referenz eine absolute URL ist (z. B. "https://fhir.example.org/base/Patient/123", "https://fhir.example.org/base/Patient/123/_history/a"):
+
+
Suche nach einem Bundle-Entry mit einer fullUrl, die mit dem reference.value übereinstimmt
+
Wenn einer gefunden wird, ist die Auflösung hier erfolgreich (und endet)
+
Wird mehr als ein Eintrag gefunden, KANN der Server nach der neuesten Version suchen (basierend auf meta.lastUpdated). Wenn jener auf diese Weise genau eine aktuelle Version findet, ist die Auflösung erfolgreich (und endet hier)
+
+
+
Wenn die Referenz die Form "[Typ]/[id]" hat (z. B. "Patient/123")
+
+
Wenn der Bundle-Entry, der den Verweis enthält, eine FullUrl hat, die dem RESTful-URL-Regex entspricht (z. B. "https://fhir.example.org/Observation/456"):
+
+
Extrahiert wird die [root] aus der fullUrl des Bundle-Entries und mit der relative Referenz zusammenangefügt (z. B. "https://fhir.example.org/" + "Patient/123" --> "https://fhir.example.org/Patient/123")
+
Gefolgt wird den Schritten für die Auflösung absoluter Referenzen. Siehe oben.
+
+
+
+
+
+
Persistierung der menschenlesbaren Repräsentation
+
Das Narrative der Ressource KANN innerhalb einer DocumentReference-Ressource persistiert werden. Zum derzeitigen Zeitpunkt obliegt es der jeweiligen Implementierung wie diese DocumentReference Ressource ausgestaltet ist.
+Ein Mapping der Composition-Metadaten auf DocumentReference-Metadaten KANN der FHIR Kernspezifikation entnommen werden. Siehe Abschnitt "2.42.8.7 FHIR Composition".
+
Das Narrative MUSS als Binary-Ressource unter DocumentReference.content.attachment.url angegeben werden.
+
Hinweis: Es ist zu beachten, dass in einem Attachment-Datentyp im Element "url" eine absolute URL anzugeben ist. Somit muss zunächst das Binary auf dem externen System per POST angelegt werden. Der hieraus resultierende Link kann anschließend im Attachment verwendet werden.
+
Falls ein Bundle erneut mit dem gleichen Bundle.identifier übermittelt wird, MUSS eine neue DocumentReference erstellt werden, welche unter DocumentReference.relatesTo.target angegeben wird.
+
Hinweise zum Umgang mit strukturierten Daten
+
Auch wenn in der aktuellen Stufe nur die Übernahme der menschenlesbaren Repräsentation erforderlich ist, empfiehlt es sich dennoch, das vollständige Bundle samt der strukturierten Anteile zu einem Dokument zu persistieren, sodass zu einem späteren Zeitpunkt, wenn eine Übernahme einzelner Daten möglich ist, diese auch rückwirkend erfolgen kann.
There are no (further) constraints on this element
Element Id
Composition
Short description
A set of resources composed into a single coherent clinical statement with clinical attestation
Definition
A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
+
Comments
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Document[classCode="DOC" and moodCode="EVN" and isNormalAct()]
cda:ClinicalDocument
fhirdocumentreference:when described by DocumentReference
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Composition.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Composition.text
Short description
Text summary of the resource, for human interpretation
Alternate names
narrative, html, xhtml, display
Definition
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
+
Comments
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
txt-1:The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes htmlChecks()
txt-2:The narrative SHALL have some non-whitespace content htmlChecks()
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.identifier.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Composition.identifier.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Composition.identifier.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.identifier.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Composition.identifier.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
+
Requirements
Need to be able to mark interim, amended, or withdrawn compositions or documents.
+
Comments
If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
+
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Fixed Value
+
final
Mappings
rim:n/a
workflow:Event.status
w5:FiveWs.status
rim:interim: .completionCode="IN" & ./statusCode[isNormalDatatype()]="active"; final: .completionCode="AU" && ./statusCode[isNormalDatatype()]="complete" and not(./inboundRelationship[typeCode="SUBJ" and isNormalActRelationship()]/source[subsumesCode("ActClass#CACT") and moodCode="EVN" and domainMember("ReviseComposition", code) and isNormalAct()]); amended: .completionCode="AU" && ./statusCode[isNormalDatatype()]="complete" and ./inboundRelationship[typeCode="SUBJ" and isNormalActRelationship()]/source[subsumesCode("ActClass#CACT") and moodCode="EVN" and domainMember("ReviseComposition", code) and isNormalAct() and statusCode="completed"]; withdrawn : .completionCode=NI && ./statusCode[isNormalDatatype()]="obsolete"
There are no (further) constraints on this element
Element Id
Composition.type
Short description
Kind of composition (LOINC if possible)
Definition
Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition.
+
Requirements
Key metadata element describing the composition, used in searching/filtering.
+
Comments
For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:LOINC.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:KDL.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:KDL.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.type.coding:IHE.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Composition.category
Short description
Categorization of Composition
Definition
A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.
+
Requirements
Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.category.coding:LOINC.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Composition.category.coding:IHE.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Composition.category.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure).
+
Requirements
Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about.
+
Comments
For clinical documents, this is usually the patient.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Composition.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Composition.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Composition.encounter
Short description
Context of the Composition
Definition
Describes the clinical encounter or type of care this documentation is associated with.
+
Requirements
Provides context for the composition and supports searching.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.context
w5:FiveWs.context
rim:unique(highest(./outboundRelationship[typeCode="SUBJ" and isNormalActRelationship()], priorityNumber)/target[moodCode="EVN" and classCode=("ENC", "PCPR") and isNormalAct])
There are no (further) constraints on this element
Element Id
Composition.date
Short description
Composition editing time
Definition
The composition editing time, when the composition was last logically changed by the author.
+
Requirements
dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring. When packaged in a document, Bundle.timestamp is the date of packaging.
+
Comments
The Last Modified Date on the composition may be after the date of the document was attested without being changed.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
+
Requirements
Identifies who is responsible for the content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.author.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Composition.author.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Composition.author.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Composition.author.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Composition.title
Short description
Human Readable name/title
Definition
Official human-readable label for the composition.
+
Comments
For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.
There are no (further) constraints on this element
Element Id
Composition.confidentiality
Short description
As defined by affinity domain
Definition
The code specifying the level of confidentiality of the Composition.
+
Comments
The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.
There are no (further) constraints on this element
Element Id
Composition.attester.party
Short description
Who attested the composition
Definition
Who attested the composition in the specified way.
+
Requirements
Identifies who has taken on the responsibility for accuracy of the composition content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.witness
rim:./role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()] or ./role[classCode="ASSIGNED" and isNormalRole and not(player)]/scoper[determinerCode="INST" and classCode="ORG" and isNormalEntity()]
There are no (further) constraints on this element
Element Id
Composition.custodian
Short description
Organization which maintains the composition
Definition
Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.
+
Requirements
Identifies where to go to find the current version, where to report issues, etc.
+
Comments
This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.participation[typeCode="RCV"].role[classCode="CUST"].scoper[classCode="ORG" and determinerCode="INST"]
There are no (further) constraints on this element
Element Id
Composition.event.code
Short description
Code(s) that apply to the event being documented
Definition
This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.
+
Comments
An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries.
There are no (further) constraints on this element
Element Id
Composition.event.period
Short description
The period covered by the documentation
Definition
The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Composition.event.detail
Short description
The event(s) being documented
Definition
The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.section.title
Short description
Label for section (e.g. for ToC)
Alternate names
header, label, caption
Definition
The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents.
+
Requirements
Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized.
+
Comments
The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.
There are no (further) constraints on this element
Element Id
Composition.section.code
Short description
Classification of section (recommended)
Definition
A code identifying the kind of content contained within the section. This must be consistent with the section title.
+
Requirements
Provides computable standardized labels to topics within the document.
+
Comments
The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
+
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.
There are no (further) constraints on this element
Element Id
Composition.section.author
Short description
Who and/or what authored the section
Definition
Identifies who is responsible for the information in this section, not necessarily who typed it in.
+
Requirements
Identifies who is responsible for the content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Composition.section.focus
Short description
Who/what the section is about, when it is not about the subject of composition
Definition
The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources).
+
Comments
Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
cda:.subject? (CDA did not differentiate between subject and focus)
There are no (further) constraints on this element
Element Id
Composition.section.text
Short description
Text summary of the section, for human interpretation
Definition
A human-readable narrative that contains the attested content of the section, 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.
+
Comments
Document profiles may define what content should be represented in the narrative to ensure clinical safety.
There are no (further) constraints on this element
Element Id
Composition.section.mode
Short description
working | snapshot | changes
Definition
How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.
+
Requirements
Sections are used in various ways, and it must be known in what way it is safe to use the entries in them.
+
Comments
This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
There are no (further) constraints on this element
Element Id
Composition.section.orderedBy
Short description
Order of section entries
Definition
Specifies the order applied to the items in the section entries.
+
Requirements
Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries.
+
Comments
Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.outboundRelationship[typeCode=COMP] or .participation[typeCode=SBJ]
There are no (further) constraints on this element
Element Id
Composition.section.emptyReason
Short description
Why the section is empty
Definition
If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
+
Requirements
Allows capturing things like "none exist" or "not asked" which can be important for most lists.
+
Comments
The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.
There are no (further) constraints on this element
Element Id
Composition.section.section
Short description
Nested Section
Definition
A nested sub-section within this section.
+
Comments
Nested sections are primarily used to help human readers navigate to particular portions of the document.
+
Mappings
rim:./outboundRelationship[typeCode="COMP" and isNormalActRelationship()]/target[moodCode="EVN" and classCode="DOCSECT" and isNormalAct]
cda:.component.section
+
+
+
+
+
Anmerkungen zu den Must-Support-Feldern
+
Composition.id
+
Bedeutung: Subsystem-interne Datensatz-ID
+
Composition.profile
+
Bedeutung: Erklärung zur Konformität zum ISiK-Profil
+
Composition.text
+
Bedeutung: menschenlesbare Repräsentation des Dokumentenkopfes (Metadaten)
+
Hinweise: Die Mindestanforderungen an den Inhalt der menschenlesbaren Repräsentation umfasst folgende Informationen:
+
+
Composition.subject:Patient.name.family
+
Composition.subject:Patient.birthDate
+
Composition.subject:Patient.identifier:pid
+
Composition.status
+
Composition.type.text
+
Composition.date
+
Composition.title
+
Composition.author.display
+
+
Composition.identifier
+
Bedeutung: Subsystem-seitig zugewiesener Identifier des Berichtes mit Angabe der URL des vom Subsystem verwendeten Namensraumes
+
Hinweise: Werden eigene Identifier bzw. NamingSystems verwendet, so sei auf den Leitfaden der Basisprofile Deutschland (HL7 Deutschland) zu den Best-Practices bei Namensräumen verwiesen.
+
Dazu ein Beispiel für einen Identifier eines Sub-System-Berichts:
Hinweise: In der aktuellen Ausbaustufe von ISiK ist textuelle Repräsentation des Dokumenttyps (type.text) ausreichend. Die darüber hinausgehende Codierung des Dokumenttyps (z.B. mit LOINC, IHE-Typecodes oder KDL) in type.coding KANN implementiert werden
+
Composition.subject
+
Bedeutung: Patientenbezug des Dokumentes
+
Composition.encounter
+
Bedeutung: Fallbezug des Dokumentes
+
Composition.date
+
Bedeutung: Datum der letzten Änderung am Dokument
+
Composition.author.display
+
Bedeutung: Autor des Dokumentes (Person, Subsystem)
+
Hinweise: In der aktuellen Ausbaustufe von ISiK ist die Verwendung der textuellen Repräsentation (display) von Autor und Subsystem ausreichend. Die darüber hinaus gehende Verlinkung auf Practitioner bzw. Device-Ressourcen KANN implementiert werden.
+
Composition.title
+
Bedeutung: Dokumentenbezeichnung
+
Hinweise: Die Dokumentenbezeichnung dient der Darstellung des Dokumentes in einer Übersicht, z.B. in einer Patientenakte, und KANN der schnellen Auffindbarkeit eines gesuchten Dokumentes dienen. Geeignete Bezeichnungen sind zum Beispiel
+
+
"Kleines Blutbild vom 13.10.2020"
+
"Pathologiebefund (Abstrich) vom 13.10.2020"
+
"Blutgasmessung vom 13.10.2020 14:14h"
+
+
Composition.section.title
+
Bedeutung: Kapitelüberschrift
+
Composition.section.text
+
Bedeutung: menschenlesbare Repräsentation des Inhalts eines Kapitels
+
Hinweise: Für Aggregation einer vollständigen menschenlesbaren Repräsentation MÜSSEN die Repräsentationen der einzelnen Kapitel an die Repräsentation der Metadaten (Composition.text) angehängt werden. Für die Separierung KÖNNEN einfache <div>-Tags verwendet werden.
+Es ist zu beachten, dass Kapitel auch Unterkapitel enthalten KÖNNEN (Composition.section.section), die bei der Aggregation entsprechend berücksichtigt werden MÜSSEN.
+
Die Mindestanforderungen an den Inhalt der menschenlesbaren Repräsentation umfasst folgende Informationen:
+
+
section.title + Freitext oder
+
section.title + Resource.text der referenzierten Ressource oder
+
section.title + eine aggregierte Repräsentation von Resource.text wenn in einer Section mehrere Ressourcen referenziert werden.
Die Binary-Ressource erlaubt den Umgang mit FHIR-fremden Formaten (z.B. PDFs, Bilder, CDA) innerhalb des FHIR-Frameworks.
+Dazu werden die Daten base64-codiert in der Binary-Ressource (in XML oder JSON) transportiert oder
+über die REST-API am Binary-Endpunkt in ihrem nativen Format bereitgestellt.
+Binary-Ressourcen werden von Attachment-Elementen verlinkt und damit in den Kontext anderer FHIR-Ressourcen
+(z.B. Patient und Encounter) gestellt.
+
Das ISIK-Binary-Profil ist nicht Bestandteil der Implementierung des ISIK Basismoduls.
+Das Profil ist Teil des ISIK Basismoduls, da es als übergreifend genutzte Ressource sowohl im Modul Terminplanung als auch im Modul Dokumentenaustausch implementiert werden muss.
There are no (further) constraints on this element
Element Id
Binary
Short description
Pure binary content defined by a format other than FHIR
Definition
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.
+
Comments
Typically, Binary resources are used for handling content such as:
+
+
CDA Documents (i.e. with XDS)
+
PDF Documents
+
Images (the Media resource is preferred for handling images, but not possible when the content is already binary - e.g. XDS).
There are no (further) constraints on this element
Element Id
Binary.securityContext
Short description
Identifies another resource to use as proxy when enforcing access control
Definition
This element identifies another resource that can be used as a proxy of the security sensitivity to use when deciding and enforcing access control rules for the Binary resource. Given that the Binary resource contains very few elements that can be used to determine the sensitivity of the data and relationships to individuals, the referenced resource stands in as a proxy equivalent for this purpose. This referenced resource may be related to the Binary (e.g. Media, DocumentReference), or may be some non-related Resource purely as a security proxy. E.g. to identify that the binary resource relates to a patient, and access should only be granted to applications that have access to the patient.
+
Comments
Very often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
rim:ED.data
+
+
+
+
+
Anmerkungen zu den Must-Support Feldern
+
Binary.contentType
+
Bedeutung: MimeType der Binärdaten
+
Binary.data
+
Bedeutung: Base64-codierte Binärdaten
+
+
+
+
+
Interaktionen
+
Für die Ressource Binary MUSS die REST-Interaktion "READ" implementiert werden. Es MÜSSEN die Regeln aus der FHIR-Kernspezifikation zur Abfrage einer Binary Ressource beachtet werden. Siehe "Serving Binary Resources using the RESTful API".
ISiK erlaubt in diversen Kontexten die Erweiterung der Kodierung durch Krankenhaus-/Systeminterne Kodierungen. Das Profil ISiKKatalog (CodeSystem) als Profil erlaubt die Repräsentation der dazugehörigen Codes und Displaywerte.
+
Eine maschinenlesbare Repräsentation dieser Kodierungen erlaubt es Clients dazugehörige Anzeigetext und Definitionen zu verarbeiten.
+
Ein Codesystem eignet sich auch dazu, auf dessen Basis definierte ValueSets zu expandieren.
+Da ISiKValueSet expandierte Valuesets vorsieht, ist eine dynamische Expansion in der Regel nicht erforderlich.
+Darüber hinausgehend ist ein Use Case im Kontext der Katalogabfrage folgender: Ein Client möchte eine Expansion neu generieren (z.B. mit anderen Expansionen-Parametern), um das ValueSet beispielsweise in einer anderen Sprache auszugeben.
+
Normativer Status und Bestätigung
+
Dieses Profil MUSS im Rahmen der Bestätigung NICHT unterstützt werden. Falls das Profil unterstützt werden soll, MÜSSEN die hier definierten Festlegungen greifen (auch im Bestätigungsverfahren).
There are no (further) constraints on this element
Element Id
CodeSystem
Short description
Declares the existence of and describes a code system or code system supplement
Definition
The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
csd-1:Within a code system definition, all the codes SHALL be unique concept.code.combine($this.descendants().concept.code).isDistinct()
csd-0:Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
Mappings
rim:Entity. Role, or Act
rim:N/A
id
SΣ
1..1
System.String
There are no (further) constraints on this element
Element Id
CodeSystem.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
CodeSystem.url
Short description
Canonical identifier for this code system, represented as a URI (globally unique) (Coding.system)
Definition
An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this code system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the code system is stored on different servers. This is used in Coding.system.
+
Requirements
Allows the code system to be referenced by a single globally unique identifier.
+
Comments
Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
+
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.
+
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
There are no (further) constraints on this element
Element Id
CodeSystem.identifier
Short description
Additional identifier for the code system (business identifier)
Definition
A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance.
+
Requirements
Allows externally provided and/or usable business identifiers to be easily associated with the module.
+
Comments
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this code system outside of FHIR, where it is not possible to use the logical URI. Note that HL7 defines at least three identifiers for many of its code systems - the FHIR canonical URL, the OID and the V2 Table 0396 mnemonic code.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
CodeSystem.version
Short description
Business version of the code system (Coding.version)
Definition
The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. This is used in Coding.version.
+
Comments
There may be different code system instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the code system with the format [url]|[version].
There are no (further) constraints on this element
Element Id
CodeSystem.name
Short description
Name for this code system (computer friendly)
Definition
A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation.
+
Requirements
Support human navigation and code generation.
+
Comments
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
There are no (further) constraints on this element
Element Id
CodeSystem.experimental
Short description
For testing purposes, not real usage
Definition
A Boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
+
Requirements
Enables experimental content to be developed following the same lifecycle that would be used for a production-level code system.
+
Comments
Allows filtering of code systems that are appropriate for use versus not.
There are no (further) constraints on this element
Element Id
CodeSystem.date
Short description
Date last changed
Alternate names
Revision Date
Definition
The date (and optionally time) when the code system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the code system changes.
+
Comments
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the code system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
There are no (further) constraints on this element
Element Id
CodeSystem.publisher
Short description
Name of the publisher (organization or individual)
Definition
The name of the organization or individual that published the code system.
+
Requirements
Helps establish the "authority/credibility" of the code system. May also allow for contact.
+
Comments
Usually an organization but may be an individual. The publisher (or steward) of the code system is the organization or individual primarily responsible for the maintenance and upkeep of the code system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the code system. This item SHOULD be populated unless the information is available from context.
There are no (further) constraints on this element
Element Id
CodeSystem.description
Short description
Natural language description of the code system
Alternate names
Scope, Purpose
Definition
A free text natural language description of the code system from a consumer's perspective.
+
Comments
This description can be used to capture details such as why the code system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the code system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the code system is presumed to be the predominant language in the place the code system was created).
There are no (further) constraints on this element
Element Id
CodeSystem.useContext
Short description
The context that the content is intended to support
Definition
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate code system instances.
+
Requirements
Assist in searching for appropriate content.
+
Comments
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
There are no (further) constraints on this element
Element Id
CodeSystem.purpose
Short description
Why this code system is defined
Definition
Explanation of why this code system is needed and why it has been designed as it has.
+
Comments
This element does not describe the usage of the code system. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this code system.
There are no (further) constraints on this element
Element Id
CodeSystem.copyright
Short description
Use and/or publishing restrictions
Alternate names
License, Restrictions
Definition
A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system.
+
Requirements
Consumers must be able to determine any legal restrictions on the use of the code system and/or its content.
+
Comments
Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
+Sometimes, the copyright differs between the code system and the codes that are included. The copyright statement should clearly differentiate between these when required.
+Sometimes, the copyright differs between the code system and the codes that are included. The copyright statement should clearly differentiate between these when required.
There are no (further) constraints on this element
Element Id
CodeSystem.caseSensitive
Short description
If code comparison is case sensitive
Definition
If code comparison is case sensitive when codes within this system are compared to each other.
+
Comments
If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case. This element is primarily provided to support validation software.
There are no (further) constraints on this element
Element Id
CodeSystem.versionNeeded
Short description
If definitions are not stable
Definition
This flag is used to signify that the code system does not commit to concept permanence across versions. If true, a version must be specified when referencing this code system.
+
Comments
Best practice is that code systems do not redefine concepts, or that if concepts are redefined, a new code system definition is created. But this is not always possible, so some code systems may be defined as 'versionNeeded'.
+
Most code systems occasionally refine the displays defined for concepts between versions. Contexts in which the concept display values are validated may require that the version be specified for some code systems irrespective of the value of this property.
There are no (further) constraints on this element
Element Id
CodeSystem.count
Short description
Total concepts in the code system
Definition
The total number of concepts defined by the code system. Where the code system has a compositional grammar, the basis of this count is defined by the system steward.
+
Comments
The count of concepts defined in this resource cannot be more than this value but may be less for several reasons - see the content element.
There are no (further) constraints on this element
Element Id
CodeSystem.filter
Short description
Filter that can be used in a value set
Definition
A filter that can be used in a value set compose statement when selecting concepts using a filter.
+
Comments
Note that filters defined in code systems usually require custom code on the part of any terminology engine that will make them available for use in value set filters. For this reason, they are generally only seen in high value published terminologies.
There are no (further) constraints on this element
Element Id
CodeSystem.property.code
Short description
Identifies the property on the concepts, and when referred to in operations
Definition
A code that is used to identify the property. The code is used internally (in CodeSystem.concept.property.code) and also externally, such as in property filters.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
CodeSystem.concept
Short description
Concepts in the code system
Definition
Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are.
+
Comments
If this is empty, it means that the code system resource does not represent the content of the code system.
There are no (further) constraints on this element
Element Id
CodeSystem.concept.definition
Short description
Formal definition
Definition
The formal definition of the concept. The code system resource does not make formal definitions required, because of the prevalence of legacy systems. However, they are highly recommended, as without them there is no formal meaning associated with the concept.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
CodeSystem.concept.designation
Short description
Additional representations for the concept
Definition
Additional representations for the concept - other languages, aliases, specialized purposes, used for particular purposes, etc.
+
Requirements
Many concept definition systems support multiple representations, in multiple languages, and for multiple purposes.
+
Comments
Concepts have both a display and an array of designation. The display is equivalent to a special designation with an implied designation.use of "primary code" and a language equal to the Resource Language.
There are no (further) constraints on this element
Element Id
CodeSystem.concept.concept
Short description
Child Concepts (is-a/contains/categorizes)
Definition
Defines children of a concept to produce a hierarchy of concepts. The nature of the relationships is variable (is-a/contains/categorizes) - see hierarchyMeaning.
+
+
+
+
+
+
Interaktionen
+
Für die Ressource CodeSystem MUSS die REST-Interaktion "READ" implementiert werden, falls die Resource CodeSystem umgesetzt wird.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
+
+
Der Suchparameter "_id" MUSS unterstützt werden, falls die Resource CodeSystem umgesetzt wird:
Bedeutung: Eindeutige Url zur Identifizierung des CodeSystems. Absolute Url sind zu bevorzugen.
+
Hinweise: OIDs SOLLTEN als weitere Identifier des CodeSystems verwendet werden. In jedem Fall SOLLTE ein Canonical Url vergeben werden.
+
CodeSystem.version
+
Bedeutung: Version des CodeSystems
+
Hinweise: Jede Änderung des CodeSystems MUSS eine Änderung in der Version des CodeSystems und gebundenen ValueSets nach sich ziehen. Die Versionierung SOLLTE auf Basis von Semantic Versioning basieren.
+
CodeSystem.name
+
Bedeutung: Maschinenlesbarer Name des CodeSystems
+
Hinweise: Der Constraint cps-0 ist hierbei zu beachten.
+
CodeSystem.status
+
Bedeutung: Indikation, ob das CodeSystem in aktiver Verwendung ist.
+
Hinweise: Alle in einem System möglichen Status-Werte MÜSSEN über FHIR korrekt repräsentiert werden. KÖNNEN mindestens jedoch die Status-Werte "active" und "retired". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
CodeSystem.content
+
Bedeutung: Angabe, ob es sich um eine vollständige Repräsentation des CodeSystems oder nur um einen Auszug handelt.
+
Hinweise: Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "fragment" und "complete". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
CodeSystem.concept
+
Bedeutung: Angabe der Konzepte, aus denen sich das CodeSystem zusammensetzt.
+
Hinweise: Es MUSS mindestens ein Code und ein Anzeigetext spezifiziert werden.
Die Möglichkeit, auf eine Übersicht der Diagnosen eines Patienten zuzugreifen, Patienten anhand ihrer Diagnose zu suchen oder zu prüfen, ob eine konkrete Diagnose bei einem Patienten vorliegt, sind wichtige Funktionen im klinischen Behandlungsablauf.
+
In FHIR werden Diagnosen mit der Condition-Ressource repräsentiert.
+
Da die Diagnosen in klinischen Primärsystemen in der Regel in ICD-10-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches.
+Falls eine Diagnose zwar dokumentiert, aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Diagnose möglich.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKDiagnose wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKDiagnose valide sind, auch valide sind gegen:
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
con-5:Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
con-4:If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-3:Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
isik-con1:Falls eine kodierte Diagnose vorliegt muss angegeben werden durch welchen Kontakt diese Dokumentation erfolgte. code.coding.exists() implies encounter.exists()
Mappings
rim:Entity. Role, or Act
workflow:Event
sct-concept:< 243796009 |Situation with explicit context| : 246090004 |Associated finding| = ( ( < 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 272379006 |Event|)
There are no (further) constraints on this element
Element Id
Condition.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.identifier
Short description
External Ids for this condition
Definition
Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.
+
Requirements
Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.
+
Comments
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.
The verification status to support the clinical status of the condition.
+
Comments
verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.
+The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.
Identification of the condition, problem or diagnosis
Alternate names
type
Definition
Identification of the condition, problem or diagnosis.
+
Requirements
0..1 to account for primarily narrative only resources.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
icd-text-1:Entweder MUSS eine kodierte Diagnose vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt. coding.exists().not() implies text.exists()
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
workflow:Event.code
w5:FiveWs.what[x]
sct-concept:code 246090004 |Associated finding| (< 404684003 |Clinical finding| MINUS
+<< 420134006 |Propensity to adverse reactions| MINUS
+<< 473010000 |Hypersensitivity condition| MINUS
+<< 79899007 |Drug interaction| MINUS
+<< 69449002 |Drug action| MINUS
+<< 441742003 |Evaluation finding| MINUS
+<< 307824009 |Administrative status| MINUS
+<< 385356007 |Tumor stage finding|)
+OR < 413350009 |Finding with explicit context|
+OR < 272379006 |Event|
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.system
Short description
Canonische CodeSystem URL für ICD-10-GM
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.version
Short description
Die Jahresversion von ICD-10-GM. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von ICD-10-GM ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von ICD-10-GM ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.code
Short description
Der ICD-10-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.system
Short description
Canonische CodeSystem URL für Alpha-ID
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.version
Short description
Die Jahresversion von Alpha-ID. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von Alpha-ID ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von Alpha-ID ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.code
Short description
Der Alpha-ID-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.system
Short description
Identity of the terminology system
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.system
Short description
Identity of the terminology system
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Condition.code.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Condition.bodySite
Short description
Anatomical location, if relevant
Definition
The anatomical location where this condition manifests itself.
+
Comments
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both.
There are no (further) constraints on this element
Element Id
Condition.subject
Short description
Who has the condition?
Alternate names
patient
Definition
Indicates the patient or group who the condition record is associated with.
+
Requirements
Group is typically used for veterinary or public health use cases.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Condition.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Condition.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Condition.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Condition.encounter
Short description
Encounter created as part of
Definition
The Encounter during which this Condition was created or to which the creation of this record is tightly associated.
+
Comments
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.start.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.end.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
workflow:Event.occurrence[x]
w5:FiveWs.init
v2:PRB-16
rim:.effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value
abatement[x]
I
0..1
There are no (further) constraints on this element
Element Id
Condition.abatement[x]
Short description
When in resolution/remission
Definition
The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate.
+
Comments
There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
w5:FiveWs.done[x]
rim:.effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed
There are no (further) constraints on this element
Element Id
Condition.recorder
Short description
Who recorded the condition
Definition
Individual who recorded the record and takes responsibility for its content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.asserter
Short description
Person who asserts this condition
Definition
Individual who is making the condition statement.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.stage.summary
Short description
Simple summary (disease specific)
Definition
A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.stage.assessment
Short description
Formal record of assessment
Definition
Reference to a formal record of the evidence on which the staging assessment is based.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.stage.type
Short description
Kind of staging
Definition
The kind of staging, such as pathological or clinical staging.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.evidence
Short description
Supporting evidence
Definition
Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.
+
Comments
The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.
There are no (further) constraints on this element
Element Id
Condition.evidence.code
Short description
Manifestation/symptom
Definition
A manifestation or symptom that led to the recording of this condition.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.evidence.detail
Short description
Supporting information found elsewhere
Definition
Links to other relevant information, including pathology reports.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.note
Short description
Additional information about the Condition
Definition
Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.
+
Comments
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
isik-con1
error
Falls eine kodierte Diagnose vorliegt muss angegeben werden durch welchen Kontakt diese Dokumentation erfolgte.
code.coding.exists() implies encounter.exists()
+
icd-text-1
error
Entweder MUSS eine kodierte Diagnose vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.
Bedeutung: Kodierter klinischer Status der Diagnose. MUSS angegeben werden, da die Interpretation der Diagnose davon abhängt ob diese 'aktiv' ist oder einen anderen Status aufweist. Alle in einem System möglichen Clinical-Status-Werte müssen über FHIR korrekt repräsentiert werden, können mindestens jedoch die Status-Werte "active" und "inactive" unterstützen. Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Bedeutung: Kodierte Diagnose. Die Kodierung KANN nach den Vorgaben des BfArM per ICD-10GM kodiert werden. Weiterhin sind folgende Kodiersysteme u.a. auf Basis von Empfehlungen des BfArM zulässig:
Hinweise: Angaben zur ICD-Diagnosesicherheit ("A", "G", "V", "Z") müssen vom Code abgetrennt und in der Extension angegeben werden.
+
Condition.subject
+
Bedeutung: Ein Patientenbezug der Diagnose MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Condition.encounter
+
Bedeutung: Der Fallbezug einer Diagnose MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Hinweise:
+
Eine Verlinkung der Referenz auf den dazugehörigen Kontakt SOLL auf die Ebene des Abteilungskontaktes (entsprechend ISiKKontaktGesundheitseinrichtung) erfolgen.
+Bei der Auswahl des Kontaktes ist zu beachten, dass mehrere Encounter-Ressourcen mit identischen Aufnahmenummer-Identifiern existieren können (Abbildung Vor- und nachstationäre Kontakte).
+
Condition.recordedDate
+
Bedeutung: Das Dokumentationsdatum der Diagnose MUSS zu Qualitätssicherungszwecken angegeben werden. Dies ist das fachliche Dokumentationsdatum, nicht zu verwechseln mit der technischen Anlage des Datensatzes im Primärsystem. Diese beiden Daten können jedoch identisch sein.
+
Hinweise:
+
Das Recorded Date MUSS mindestens auf den Monat genau angegeben werden (vgl. FHIRPath Constraint rec-1)
+
Condition.note
+
Bedeutung: Weitere optionale Freitext-Notizen bezogen auf die Diagnose.
+
Condition.extension:ReferenzPrimaerdiagnose
+
Bedeutung: Bei mehrfachkodierten ICD-Diagnosen (z.B. Kreuz-Stern-Notation) muss die Sekundär- auf die Primärdiagnose verlinkt werden
+
+
+
+
+
Interaktionen
+
Für die Ressource Condition MUSS die REST-Interaktion "READ" implementiert werden.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
Informationen über die Besuche des Patienten entlang seines Behandlungspfades im Krankenhaus sind ein wichtiger Bestandteil des einrichtungsinternen Datenaustausches.
+Sie ermöglichen die Unterscheidung von stationären und ambulanten sowie aufgenommenen und entlassenen Patienten.
+Weiterhin ist aus den Besuchsinformationen der aktuelle Aufenthaltsort des Patienten (Fachabteilung, Station, Bettplatz) ermittelbar.
+Klinische Ressourcen werden in FHIR durch Verlinkung auf die Encounter-Ressource in einen Kontext zum Besuch gestellt. Dieser Kontext ist wichtig für die Steuerung von Zugriffsberechtigungen und Abrechnungsprozessen.
+
Zu Beginn der meisten klinischen Workflows steht die Auswahl des Besuchskontextes. Dies geschieht bspw. durch das Suchen der Encounter-Ressource anhand von Eigenschaften wie Aufnahmenummer, Fallart oder Aufnahmedatum. Daraufhin werden die zutreffenden Suchergebnisse angezeigt und der gewünschte Besuch ausgewählt.
+
+
Der Begriff "Fall" im Kontext von FHIR
+
Wichtig ist die Herausstellung, dass "Besuch" und "Fall" wechselseitig keine synonyme Begriffe sind.
+
Der Begriff "Fall" gruppiert im Sprachgebrauch verschiedene Konzepte, die in FHIR durch unterschiedliche Ressourcen repräsentiert werden:
+
+
Aufenthalt/Besuch/Kontakt (Encounter):
+Der stationäre Aufenthalt oder der ambulante Kontakt eines Patienten in einer Gesundheitseinrichtung wird in FHIR durch die Ressource Encounter abgebildet.
+
+
Abrechnungsfall (Account):
+Der Fall, im Sinne einer Gruppierung von medizinischen Leistungen, die in einem gemeinsamen Kontext abgerechnet werden, sind in FHIR durch die Ressource Account repräsentiert. Ein Abrechnungsfall kann mehrere Encounter umfassen (z.B. vorstationärer Besuch, stationärer Aufenthalt und nachstationäre Besuche)
+
+
+
+
+
+
Medizinischer Fall (EpisodeOfCare):
+Der medizinische Fall gruppiert Informationen, die im Kontext einer gemeinsamen (Dauer-)Diagnose stehen und wird in FHIR durch die EpisodeOfCare dargestellt.
+
+
+
+
+
+
+
+
Der Begriff "Fall" im Kontext der Medizininformatik-Initiative
Einrichtungskontakt:
+Als Kontakt eines Patienten mit einer Einrichtung (z.B: Klinik) gruppiert mehrere Besuche bei einer Einrichtung als gemeinsamen Behandlungskontext.
+
+
Abteilungskontakt:
+Als Kontakt des Patienten mit einer Fachabteilung eines Krankenhauses (z.B. einer Ambulanz oder einer stationären Fachabteilung).
+
+
Versorgungsstellenkontakt:
+Als Kontakt des Patienten mit konkreten Servicestellen, wie z.B. Radiologie oder Endoskopie
+
+
+
Zur Unterscheidung der verschiedenen Kontaktebenen wird in der MI-I eine Codierung in Encounter.type verwendet. Die Hierarchie der Encounter wird über die Encounter.partOf-Relation hergestellt. Ambulante Besuche werden in dem Modell derzeit noch nicht berücksichtigt.
+
+
+
+
+
+
Der Begriff "Fall" im Kontext der ISiK-Spezifikation
+
Für die Ausbaustufe 2 und 3 des ISiK Basismoduls werden alle zuvor genannten Sichtweise und Modelle berücksichtigt:
+
+
+
+
+
Verpflichtend umzusetzen ist für die bestätigungsrelevanten Systeme der Account, im Sinne der Gruppierung einzelner Besuche, zu einem gemeinsamen (Abrechnungs-)Fall sowie der Encounter der Ebene "Abteilungskontakt" im Sinne des Modells der Medizininformatikinitiative.
+
Herstellern steht es frei, weitere Ressourcen, wie zum Beispiel die EpisodeOfCare oder den Encounter, im Sinne des Einrichtungskontaktes bzw. des Versorgungststellenkontaktes, zu implementieren.
+
Wichtig sind dabei jedoch folgende Punkte zu beachten:
+
+
Encounter im ISiK-Kontext sind stets als "Abteilungskontakte, im Sinne der MI-I mit dem entsprechenden Encounter.type-Code, zu kennzeichnen.
+
jegliche im ISiK-Basis-Modul, als auch in anderen ISiK-Modulen definierte Ressourcen, die über einen Encounter-Kontext verfügen, müssen auf einen ISiK-Encounter (Abteilungskontakt) referenzieren.
+
+
+
+
+
+
+
Die Repräsentation der "Fall"-Nummer
+
Die "Fall"-Nummer ist ein im Kontext der stationären Versorgung häufig verwendetes Vehikel, um (insbesondere in der HL7-V2-Kommunikation) mit einfachen Mitteln den Fallkontext medizinischer Dokumentationen herzustellen.
+
In den meisten Fällen handelt es sich bei der "Fall"-Nummer um einen eindeutigen Identifier des Abrechnungsfalls.
+Im ISiK-Kontext ist die Fallnummer daher als Identifier des Accounts zu sehen und nicht geeignet, einen Encounter eindeutig zu identifizieren und damit den für FHIR-Ressourcen erforderlichen Encounter-Kontext zu etablieren.
+Es müssen zusätzliche Kriterien, wie z.B. Zeitraum(Encounter.period), Fallart (Encounter.class) oder Status (Encounter.status) berücksichtigt werden, um den korrekten Encounter zu finden.
+
ISiK berücksichtigt jedoch die gängige Praxis, dass die Fallnummer als primäres Suchkriterium verwendet wird; auch von Systemen, die rein der medizinischen Versorgung dienen und keine Abrechnungsfunktionen implementieren.
+Um insbesondere Subsysteme von der Pflicht zu entbinden, die Account-Ressource zu implementieren, nur um Zugriff zur Fallnummer zu bekommen, ist das Mitführen des Account-Identifiers als logische Referenz auf den Account im Encounter verpflichtend. Die Fallnummer eines Encounters kann daher auch ohne Kenntnis des Accounts ermittelt werden.
+
+
+
+
Hinweis
+
Änderung gegenüber ISiK-Basis-Modul Stufe 1!
+
+
+
+
+
Could not find subject. Project was not found for Material/Images/IG_Warning.
+
Die Abbildung der Fallnummer als Identifier des Accounts ist abweichend von der im Basismodul Stufe 1 festgelegten Abbildung der Fallnummer als Identifier des Encounters. Diese Änderung ist erforderlich, da die Fallnummer nicht geeignet ist, einen Encounter eindeutig zu identifizieren. Der Encounter kann weiterhin einen von der Abrechnungsfallnummer unabhänigen Identifier enthalten (z.B. "Aufnahmenummer", Bewegungsnummer). Dieser identifiziert eineindeutig den jeweiligen Kontakt.
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKKontaktGesundheitseinrichtung wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKKontaktGesundheitseinrichtung valide sind, auch valide sind gegen:
An interaction during which services are provided to the patient
Alternate names
Visit
Definition
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
ISiK-enc-1:Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben status = 'finished' and class = 'AMB' implies period.start.exists()
ISiK-enc-2:Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()
ISiK-enc-3:Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben status = 'planned' implies period.exists().not()
ISiK-enc-4:Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()
ISiK-enc-5:In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben status = 'in-progress' implies period.start.exists()
ISiK-enc-6:Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben status = 'onleave' implies period.start.exists()
ISiK-enc-7:Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben status = 'unknown' implies period.start.exists()
ISiK-enc-8:Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein diagnosis.use.all(coding.code != 'billing')
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Encounter[@moodCode='EVN']
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Encounter.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Encounter.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
ErsteUndZweiteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
DritteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
VierteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.url
Short description
identifies the meaning of the extension
Definition
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
http://fhir.de/StructureDefinition/Aufnahmegrund
Mappings
rim:N/A
value[x]
0..0
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.value[x]
Short description
Value of extension
Definition
Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Encounter.statusHistory
Short description
List of past encounter statuses
Definition
The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.
+
Comments
The current status is always found in the current version of the resource, not the status history.
There are no (further) constraints on this element
Element Id
Encounter.statusHistory.period
Short description
The time that the episode was in the specified status
Definition
The time that the episode was in the specified status.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Encounter.classHistory
Short description
List of past encounter classes
Definition
The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.
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.
There are no (further) constraints on this element
Element Id
Encounter.classHistory.period
Short description
The time that the episode was in the specified class
Definition
The time that the episode was in the specified class.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.serviceType
Short description
Specific type of service
Definition
Broad categorization of the service that is to be provided (e.g. cardiology).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Encounter.serviceType.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.priority
Short description
Indicates the urgency of the encounter
Definition
Indicates the urgency of the encounter.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.subject
Short description
The patient or group present at the encounter
Alternate names
patient
Definition
The patient or group present at the encounter.
+
Comments
While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.episodeOfCare
Short description
Episode(s) of care that this encounter should be recorded against
Definition
Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.basedOn
Short description
The ServiceRequest that initiated this encounter
Alternate names
incomingReferral
Definition
The request this encounter satisfies (e.g. incoming referral or procedure request).
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.participant.type
Short description
Role of participant in encounter
Definition
Role of participant in encounter.
+
Comments
The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.
There are no (further) constraints on this element
Element Id
Encounter.participant.period
Short description
Period of time during the encounter that the participant participated
Definition
The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.participant.individual
Short description
Persons involved in the encounter other than the patient
Definition
Persons involved in the encounter other than the patient.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.appointment
Short description
The appointment that scheduled this encounter
Definition
The appointment that scheduled this encounter.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
qty-3:If a code for the unit is present, the system SHALL also be present code.empty() or system.exists()
drt-1:There SHALL be a code if there is a value and it SHALL be an expression of time. If system is present, it SHALL be UCUM. code.exists() implies ((system = %ucum) and value.exists())
Mappings
rim:n/a
v2:SN (see also Range) or CQ
rim:PQ, IVL<PQ>, MO, CO, depending on the values
rim:PQ, IVL<PQ> depending on the values
workflow:Event.occurrence[x]
v2:(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes
There are no (further) constraints on this element
Element Id
Encounter.reasonCode
Short description
Coded reason the encounter takes place
Alternate names
Indication, Admission diagnosis
Definition
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
workflow:Event.reasonCode
w5:FiveWs.why[x]
v2:EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
There are no (further) constraints on this element
Element Id
Encounter.reasonReference
Short description
Reason the encounter takes place (reference)
Alternate names
Indication, Admission diagnosis
Definition
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.reasonCode
w5:FiveWs.why[x]
v2:EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.reasonReference
w5:FiveWs.why[x]
v2:Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.use
Short description
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Definition
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.use.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.account
Short description
The set of accounts that may be used for billing for this Encounter
Definition
The set of accounts that may be used for billing for this Encounter.
+
Comments
The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.account.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.account.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.account.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.account.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.origin
Short description
The location/organization from which the patient came before admission
Definition
The location/organization from which the patient came before admission.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
From where patient was admitted (physician referral, transfer)
Definition
From where patient was admitted (physician referral, transfer).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.reAdmission
Short description
The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Definition
Whether this hospitalization is a readmission and why if known.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.dietPreference
Short description
Diet preferences reported by the patient
Definition
Diet preferences reported by the patient.
+
Requirements
Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.
+
Comments
For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.specialCourtesy
Short description
Special courtesies (VIP, board member)
Definition
Special courtesies (VIP, board member).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.specialArrangement
Short description
Wheelchair, translator, stretcher, etc.
Definition
Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.destination
Short description
Location/organization to which the patient is discharged
Definition
Location/organization to which the patient is discharged.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.dischargeDisposition
Short description
Category or kind of location after discharge
Definition
Category or kind of location after discharge.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.
+
There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.
There are no (further) constraints on this element
Element Id
Encounter.location.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Station
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Station.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider
Short description
The organization (facility) responsible for this encounter
Definition
The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Es ist ein üblicher Fall, dass die Dauer eines Versorgungsstellenkontaktes die eines Abteilungskontaktes übersteigt. Ein Beispiel hierfür: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose über eine Fachabteilung (Onkologie) läuft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird.
+
Für einen solchen Fall gilt:
+
Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN nicht in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen.
+
Hinweis: Ein Versorgungsstellenkontakt endet zugleich nicht notwendigerweise mit einem Fachabteilungswechsel.
+
+
Constraints
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
ISiK-enc-1
error
Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben
status = 'finished' and class = 'AMB' implies period.start.exists()
+
ISiK-enc-2
error
Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben
status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()
+
ISiK-enc-3
error
Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben
status = 'planned' implies period.exists().not()
+
ISiK-enc-4
warning
Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden
status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()
+
ISiK-enc-5
error
In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben
status = 'in-progress' implies period.start.exists()
+
ISiK-enc-6
error
Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben
status = 'onleave' implies period.start.exists()
+
ISiK-enc-7
warning
Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben
status = 'unknown' implies period.start.exists()
+
ISiK-enc-8
error
Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein
Bedeutung: Der Status MUSS insbesondere zur Differenzierung von abgeschlossenen und derzeitig noch aktiven Kontakten angegeben werden. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden. Es KÖNNEN jedoch mindestens die Status-Werte "in-progress", "finished" und "cancelled" unterstützt werden. Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Anwendungshinweise: Weitere Informationen zur Suche nach "Encounter.period" finden sich in der FHIR-Basisspezifikation - Abschnitt "Date Search". Bei der Formulierung der Suche sollten die Vorgaben aus der Definition der Such-Prefixe - und hier insbesondere die Unterschiede zwischen "lt" und "eb" bzw. "gt" und "sa" - beachtet werden.
+
Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend.
+
+
Der Suchparameter "date-start" MUSS unterstützt werden:
Die nachfolgenden Festlegungen spezifizieren die Abbildung von Minimalanforderungen für die Bereitstellung von administrativen Patientendaten im Rahmen des Bestätigungsverfahrens der gematik.
+
+
+
+
+
Motivation
+
Der Austausch administrativer Patientendaten ist eine der grundlegenden Funktionalitäten beim Datenaustausch in der klinischen Versorgung.
+
In FHIR werden sämtliche klinischen Ressourcen durch Verlinkung auf die Ressource 'Patient' in einen Patientenkontext gestellt.
+
Die Herstellung des korrekten Patientenkontextes durch Suchen der Patientenressource anhand von Eigenschaften wie Aufnahmenummer, Name oder Geburtsdatum, die Anzeige der zutreffenden Suchergebnisse und der Auswahl bzw. Bestätigung des richtigen Datensatzes durch den Anwender steht am Beginn der meisten klinischen Workflows.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKPatient wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKPatient valide sind, auch valide sind gegen:
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
isik-pat-1:Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
Mappings
rim:Entity. Role, or Act
rim:Patient[classCode=PAT]
cda:ClinicalDocument.recordTarget.patientRole
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Patient.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Patient.active
Short description
Whether this patient's record is in active use
Definition
Whether this patient record is in active use.
+Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules.
+
It is often used to filter patient lists to exclude inactive patients
+
Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death.
+
Requirements
Need to be able to mark a patient record as not to be used because it was created in error.
+
Comments
If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.
+
Meaning When Missing
This resource is generally assumed to be active if no value is provided for the active element
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
In order to maintain the differntiations of name parts as given in the VSDM dataset or qualify prefixes as academic titles, vendors can opt to support the extensions specified in the German HumanName Base Profile https://simplifier.net/basisprofil-de-r4/humannamedebasis
+This is however not required within the scope of this specification.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Patient.name:Name.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension:nachname
Short description
Nachname ohne Vor- und Zusätze
Alternate names
extensions, user content
Definition
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension:vorsatzwort
Short description
Vorsatzwort
Alternate names
extensions, user content
Definition
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Patient.name:Name.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Patient.name:Name.prefix.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
There are no (further) constraints on this element
Element Id
Patient.name:Name.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.telecom
Short description
A contact detail for the individual
Definition
A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).
There are no (further) constraints on this element
Element Id
Patient.telecom.rank
Short description
Specify preferred order of use (1 = highest)
Definition
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
+
Comments
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
There are no (further) constraints on this element
Element Id
Patient.telecom.period
Short description
Time period when the contact point was/is in use
Definition
Time period when the contact point was/is in use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.gender
Short description
male | female | other | unknown
Definition
Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.
+
Requirements
Needed for identification of the individual, in combination with (at least) name and birth date.
+
Comments
The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.
There are no (further) constraints on this element
Element Id
Patient.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.birthDate
Short description
The date of birth for the individual
Definition
The date of birth for the individual.
+
Requirements
Age of the individual drives many clinical processes.
+
Comments
At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).
There are no (further) constraints on this element
Element Id
Patient.birthDate.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Provides a reason why the expected value or elements in the element that is extended are missing.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
There are no (further) constraints on this element
Element Id
Patient.deceased[x]
Short description
Indicates if the individual is deceased or not
Definition
Indicates if the individual is deceased or not.
+
Requirements
The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive.
+
Comments
If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:PID-30 (bool) and PID-29 (datetime)
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedTime
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.extension:Stadtteil
Short description
Stadt- oder Ortsteil
Alternate names
extensions, user content
Definition
A subsection of a municipality.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension:Strasse
Short description
Strassenname (ohne Hausnummer)
Alternate names
extensions, user content
Definition
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension:Postfach
Short description
Postfach
Alternate names
extensions, user content
Definition
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Patient.maritalStatus
Short description
Marital (civil) status of a patient
Definition
This field contains a patient's most recent marital (civil) status.
+
Requirements
Most, if not all systems capture it.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
v2:PID-16
rim:player[classCode=PSN]/maritalStatusCode
cda:.patient.maritalStatusCode
multipleBirth[x]
0..1
There are no (further) constraints on this element
Element Id
Patient.multipleBirth[x]
Short description
Whether patient is part of a multiple birth
Definition
Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).
+
Requirements
For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs.
+
Comments
Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:PID-24 (bool), PID-25 (integer)
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber
There are no (further) constraints on this element
Element Id
Patient.contact
Short description
A contact party (e.g. guardian, partner, friend) for the patient
Definition
A contact party (e.g. guardian, partner, friend) for the patient.
+
Requirements
Need to track people you can contact about the patient.
+
Comments
Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
pat-1:SHALL at least contain a contact's details or a reference to an organization name.exists() or telecom.exists() or address.exists() or organization.exists()
Mappings
rim:n/a
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
There are no (further) constraints on this element
Element Id
Patient.contact.relationship
Short description
The kind of relationship
Definition
The nature of the relationship between the patient and the contact person.
+
Requirements
Used to determine which contact person is the most relevant to approach, depending on circumstances.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Patient.contact.name
Short description
A name associated with the contact person
Definition
A name associated with the contact person.
+
Requirements
Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
There are no (further) constraints on this element
Element Id
Patient.contact.telecom
Short description
A contact detail for the person
Definition
A contact detail for the person, e.g. a telephone number or an email address.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.
There are no (further) constraints on this element
Element Id
Patient.contact.address
Short description
Address for the contact person
Definition
Address for the contact person.
+
Requirements
Need to keep track where the contact person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.contact.organization
Short description
Organization that is associated with the contact
Definition
Organization on behalf of which the contact is acting or for which the contact is working.
+
Requirements
For guardians or business related contacts, the organization is relevant.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Patient.contact.period
Short description
The period during which this contact person or organization is valid to be contacted relating to this patient
Definition
The period during which this contact person or organization is valid to be contacted relating to this patient.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.communication
Short description
A language which may be used to communicate with the patient about his or her health
Definition
A language which may be used to communicate with the patient about his or her health.
+
Requirements
If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.
+
Comments
If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
There are no (further) constraints on this element
Element Id
Patient.communication.language
Short description
The language which can be used to communicate with the patient about his or her health
Definition
The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.
+
Requirements
Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
There are no (further) constraints on this element
Element Id
Patient.communication.preferred
Short description
Language preference indicator
Definition
Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).
+
Requirements
People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.
+
Comments
This language is specifically identified for communicating healthcare information.
There are no (further) constraints on this element
Element Id
Patient.generalPractitioner
Short description
Patient's nominated primary care provider
Alternate names
careProvider
Definition
Patient's nominated care provider.
+
Comments
This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.
+Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.
+
Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Patient.managingOrganization
Short description
Organization that is the custodian of the patient record
Definition
Organization that is the custodian of the patient record.
+
Requirements
Need to know who recognizes this patient record, manages and updates it.
+
Comments
There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
rim:typeCode
cda:n/a
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
isik-pat-1
error
Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden
gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
+
+
+
+
+
Anmerkungen zu Must-Support-Feldern
+
Patient.active
+
Bedeutung: Indikator "Patientdatensatz ist in aktiver Benutzung"
Im Rahmen des ISiK Basismoduls SOLLTE die Stornierung eines Patienten entweder durch das Löschen der Patienten-Ressource oder der Verwendung des Feldes Patient.active abgebildet werden. Dies ist abhängig davon, wie die Stornierung im bestätigungsrelevanten System umgesetzt ist. Im letzteren Fall wird die Stornierung durch das Setzen von Patient.active auf false gekennzeichnet.
+
+
+
+
+
Interaktionen
+
Für die Ressource Patient MUSS die REST-Interaktion "READ" implementiert werden.
+
Für die Ressource Patient KANN die REST-Interaktion "POST" implementiert werden. Diese Interaktion dient für die Vorabübermittelung von (unverifizierten und/oder unvollständigen) Patientenstammdaten.
+
+
Das bestätigungsrelevante System SOLLTE die übermittelte Patient-Ressource löschen oder als inaktiv kennzeichnen, insoweit Geschäftsregeln oder andere Gründe dazu führen, dass die Patient-Ressource nicht permanent im System angelegt wird (z.B. keine Bestätigung durch die Anwender*in des Systems oder keine Aufnahme der Patient*in).
+
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
PersonImGesundheitsberuf können alle denkbaren medizinischen Fachexperten sein, ohne eine Rolle zu spielen. In den ISiK-FHIR-Profilen können PersonImGesundheitsberuf bspw. als Ausführende einer Prozedur auftreten, im Element performer der Procedure Ressource, oder als die Person, die eine Diagnose stellt, im Element asserter der Condition Ressource.
+
In FHIR werden PersonImGesundheitsberuf mit der Practitioner-Ressource repräsentiert.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKPersonImGesundheitsberuf wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKPatient valide sind, auch valide sind gegen:
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
prac-de-1:Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist gender='other' or gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').empty()
Mappings
rim:Entity. Role, or Act
v2:PRD (as one example)
rim:Role
servd:Provider
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Practitioner.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.assigner.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Requirements
Often, specific identities are assigned for the agent.
+
Comments
In bestimmten KIS wird keine EFN geführt, da diese aus Compliance-Gründen getrennt in HR-Systemen vorgehalten wird (Hinweis kam von Stakeholder), daher soll der entsprechende Test im Test-System mit "warningOnly" ausgegeben werden.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.active
Short description
Whether this practitioner's record is in active use
Definition
Whether this practitioner's record is in active use.
+
Requirements
Need to be able to mark a practitioner record as not to be used because it was created in error.
+
Comments
If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.
+
Meaning When Missing
This resource is generally assumed to be active if no value is provided for the active element
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate.
+
In general, select the value to be used in the ResourceReference.display based on this:
+
+
There is more than 1 name
+
Use = usual
+
Period is current to the date of the usage
+
Use = official
+
Other order as decided by internal business rules.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.family.extension:nachname
Short description
Nachname ohne Vor- und Zusätze
Alternate names
extensions, user content
Definition
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.prefix.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.telecom
Short description
A contact detail for the practitioner (that apply to all roles)
Definition
A contact detail for the practitioner, e.g. a telephone number or an email address.
+
Requirements
Need to know how to reach a practitioner independent to any roles the practitioner may have.
+
Comments
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.
There are no (further) constraints on this element
Element Id
Practitioner.telecom.rank
Short description
Specify preferred order of use (1 = highest)
Definition
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
+
Comments
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
There are no (further) constraints on this element
Element Id
Practitioner.telecom.period
Short description
Time period when the contact point was/is in use
Definition
Time period when the contact point was/is in use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Address(es) of the practitioner that are not role specific (typically home address)
Definition
Address(es) of the practitioner that are not role specific (typically home address).
+Work addresses are not typically entered in this property as they are usually role dependent.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.extension:Stadtteil
Short description
Stadt- oder Ortsteil
Alternate names
extensions, user content
Definition
A subsection of a municipality.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Practitioner.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
gender-amtlich-1:Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist %resource.where(gender='other').exists()
There are no (further) constraints on this element
Element Id
Practitioner.birthDate.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Provides a reason why the expected value or elements in the element that is extended are missing.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.photo
Short description
Image of the person
Definition
Image of the person.
+
Requirements
Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too.
+
Comments
When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
There are no (further) constraints on this element
Element Id
Practitioner.qualification
Short description
Certification, licenses, or training pertaining to the provision of care
Definition
The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.qualification.period
Short description
Period during which the qualification is valid
Definition
Period during which the qualification is valid.
+
Requirements
Qualifications are often for a limited period of time, and can be revoked.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.qualification.issuer
Short description
Organization that regulates and issues the qualification
Definition
Organization that regulates and issues the qualification.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Practitioner.communication
Short description
A language the practitioner can use in patient communication
Definition
A language the practitioner can use in patient communication.
+
Requirements
Knowing which language a practitioner speaks can help in facilitating communication with patients.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
v2:PID-15, NK1-20, LAN-2
rim:./languageCommunication
servd:./Languages.LanguageSpokenCode
+
+
Constraints
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
prac-de-1
error
Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist
gender='other' or gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').empty()
+
+
+
Terminology Bindings
+
+
+
+
+
Anmerkungen zu den Must-Support-Feldern
+
Practitioner.identifier:ANR
+
Bedeutung: Lebenslange Arztnummer. Im Krankenhaus ist die lebenslange Arztnummer der Ärzte bekannt und MUSS zur eindeutigen Identifikation eines Arztes bereitgestellt werden.
Während die Deutschen Basisprofile hier die Abkürzung LANR verwenden, ist im KBV-Kontext das Akronym ANR gebräuchlich. Die Bezeichnung des Slices hat jedoch keinerlei Auswirkungen auf die Kompatibilität.
+
Practitioner.name:name
+
Bedeutung: Vollständiger Name. Der Name des Arztes MUSS in konkreten Anwendungen angezeigt werden können. Es MUSS nach dem Namen des Arztes gesucht werden können.
+
Practitioner.address:Strassenanschrift
+
Bedeutung: Straßenanschrift. Ist die Adresse bekannt, unter der ein Arzt erreichbar ist, MUSS sie bereitgestellt werden.
+
Practitioner.address:Postfach
+
Bedeutung: Postfachanschrift. Ist die Postfachadresse bekannt, unter der ein Arzt erreichbar ist, MUSS sie bereitgestellt werden.
+
Practitioner.gender
+
Bedeutung: Administratives Geschlecht. Ist das Geschlecht des Arztes bekannt, MUSS es bereitgestellt werden.
+
Practitioner.birthDate
+
Bedeutung: Geburtsdatum. Ist das Geburtsdatum des Arztes bekannt, MUSS es bereitgestellt werden.
+
+
+
+
+
Interaktionen
+
Für die Ressource Practitioner MUSS die REST-Interaktion "READ" implementiert werden.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
Die Möglichkeit auf eine Übersicht der Prozeduren eines Patienten zuzugreifen, Patienten anhand durchgeführter oder geplanter Prozeduren zu suchen, oder zu prüfen, ob eine konkrete Prozedur bei einem Patienten durchgeführt wurde, sind wichtige Funktionen im klinischen Behandlungsablauf.
+
In FHIR werden Prozeduren mit der Procedure-Ressource repräsentiert.
+
Da die Prozeduren in klinischen Primärsystemen, in der Regel, in OPS-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches.
+Falls eine Prozedur zwar dokumentiert aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Prozedur möglich.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKProzedur wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKProzedur valide sind, auch valide sind gegen:
An action that is being or was performed on a patient
Definition
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
proc-ISiK-1:Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists() implies category.coding.where(system = 'http://snomed.info/sct').exists()
proc-ISiK-2:Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden code.coding.exists() implies category.coding.exists()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Procedure[moodCode=EVN]
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Procedure.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Procedure.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Dokumentationsdatum der Prozedur, falls abweichend vom Durchführungsdatum
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Procedure.identifier
Short description
External Identifiers for this procedure
Definition
Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
+
Requirements
Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers.
+
Comments
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Procedure.instantiatesUri
Short description
Instantiates external protocol or definition
Definition
The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
+
Comments
This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
There are no (further) constraints on this element
Element Id
Procedure.basedOn
Short description
A request for this procedure
Alternate names
fulfills
Definition
A reference to a resource that contains details of the request for this procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.basedOn
rim:.outboundRelationship[typeCode=FLFS].target[classCode=(various e.g. PROC, OBS, PCPR, ACT, moodCode=RQO].code
There are no (further) constraints on this element
Element Id
Procedure.partOf
Short description
Part of referenced event
Alternate names
container
Definition
A larger event of which this particular procedure is a component or step.
+
Comments
The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.partOf
rim:.inboundRelationship[typeCode=COMP].source[classCode=SBADM or PROC or OBS, moodCode=EVN]
A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
+
Comments
The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.
+
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
There are no (further) constraints on this element
Element Id
Procedure.statusReason
Short description
Reason for current status
Alternate names
Suspended Reason, Cancelled Reason
Definition
Captures the reason for the current state of the procedure.
+
Comments
This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here.
There are no (further) constraints on this element
Element Id
Procedure.category
Short description
Classification of the procedure
Definition
A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Procedure.category.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
+
Requirements
0..1 to account for primarily narrative only resources.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
sct-ops-1:Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden. Liegt die Prozedur nicht kodiert vor SOLL Freitext angegeben werden. coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()
proc-ISiK-3:Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt. coding.exists().not() implies text.exists()
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.system
Short description
Canonische CodeSystem URL für OPS
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.version
Short description
Die Jahresversion des OPS Kataloges. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von OPS ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.code
Short description
Der OPS-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Procedure.code.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Procedure.subject
Short description
Who the procedure was performed on
Alternate names
patient
Definition
The person, animal or group on which the procedure was performed.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Procedure.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Procedure.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Procedure.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Procedure.encounter
Short description
Encounter created as part of
Definition
The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
+
Comments
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performed[x]
Short description
When the procedure was performed
Definition
Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
+
Comments
Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
There are no (further) constraints on this element
Element Id
Procedure.recorder
Short description
Who recorded the procedure
Definition
Individual who recorded the record and takes responsibility for its content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.asserter
Short description
Person who asserts this procedure
Definition
Individual who is making the procedure statement.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performer.function
Short description
Type of performance
Definition
Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist.
+
Requirements
Allows disambiguation of the types of involvement of different performers.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.performer.actor
Short description
The reference to the practitioner
Definition
The practitioner who was involved in the procedure.
+
Requirements
A reference to Device supports use cases, such as pacemakers.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performer.onBehalfOf
Short description
Organization the device or practitioner was acting for
Definition
The organization the device or practitioner was acting on behalf of.
+
Requirements
Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.location
Short description
Where the procedure happened
Definition
The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
+
Requirements
Ties a procedure to where the records are likely kept.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.reasonCode
Short description
Coded reason procedure performed
Definition
The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
+
Comments
Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.
There are no (further) constraints on this element
Element Id
Procedure.reasonReference
Short description
The justification that the procedure was performed
Definition
The justification of why the procedure was performed.
+
Comments
It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use).
+Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.bodySite
Short description
Target body sites
Definition
Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
+
Comments
If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension procedure-targetbodystructure.
There are no (further) constraints on this element
Element Id
Procedure.report
Short description
Any report resulting from the procedure
Definition
This could be a histology result, pathology report, surgical report, etc.
+
Comments
There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.complication
Short description
Complication following the procedure
Definition
Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
+
Comments
If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text.
There are no (further) constraints on this element
Element Id
Procedure.complicationDetail
Short description
A condition that is a result of the procedure
Definition
Any complications that occurred during the procedure, or in the immediate post-performance period.
+
Requirements
This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.followUp
Short description
Instructions for follow up
Definition
If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.note
Short description
Additional information about the procedure
Definition
Any other notes and comments about the procedure.
+
Comments
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
There are no (further) constraints on this element
Element Id
Procedure.focalDevice
Short description
Manipulated, implanted, or removed device
Definition
A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
There are no (further) constraints on this element
Element Id
Procedure.focalDevice.action
Short description
Kind of change to device
Definition
The kind of change that happened to the device during the procedure.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.focalDevice.manipulated
Short description
Device that was changed
Definition
The device that was manipulated (changed) during the procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.participation[typeCode=DEV].role[classCode=MANU] or
+.participation[typeCode=CSM].role[classCode=ADMM] (for Medication or Substance)
Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden. Liegt die Prozedur nicht kodiert vor SOLL Freitext angegeben werden.
coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()
+
proc-ISiK-3
error
Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.
Bedeutung:
+Das Dokumentationsdatum der Prozedur MUSS zu Qualitätssicherungszwecken angegeben werden. Dies ist das fachliche Dokumentationsdatum, nicht zu verwechseln mit der technischen Anlage des Datensatzes im Primärsystem. Diese beiden Daten können jedoch identisch sein.
+
Procedure.status
+
Bedeutung:
+Kodierter klinischer Status der Prozedur. MUSS angegeben werden, da die Interpretation der Prozedur davon abhängt, ob diese 'completed' ist oder einen anderen Status aufweist. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "completed" und "unknown". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
Procedure.category
+
Bedeutung:
+Zur groben Kategorisierung MUSS eine Kodierung auf Basis der OPS-Klassencodes erfolgen. Eine ConceptMap für das Mapping von OPS-Kodes -> Kategorie findet sich in den Deutschen Basisprofilen - Implementierungsleitfaden Abschnitt Terminologien. Die Angabe der Kategeorie MUSS nur für OPS-kodierte Prozeduren erfolgen.
+
Procedure.code.coding
+
Bedeutung: Codierte Prozedur. Entweder kodiert per OPS oder SNOMED CT. Bei der Kodierung per SNOMED CT ist das ValueSet ProzedurenCodesSCT zu beachten.
+
Procedure.code.text
+
Bedeutung: Freitext-Beschreibung der Prozedur
+
Procedure.performed
+
Bedeutung: Zur zeitlichen Einordnung der Prozedur KANN das Durchführungsdatum der Prozedur dokumentiert werden. Mindestens MUSS der Beginn der Prozedur dokumentiert werden, das Ende KANN implementiert werden.
+
Procedure.subject
+
Bedeutung: Ein Patientenbezug der Prozedur MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Procedure.note
+
Bedeutung: Weitere optionale Freitext-Notizen bezogen auf die durchgeführte Prozedur.
+
+
+
+
+
Interaktionen
+
Für die Ressource Procedure MUSS die REST-Interaktion "READ" implementiert werden.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
ISiK erlaubt in diversen Kontexten die Erweiterung der Kodierung durch Krankenhaus- / Systeminterne Kodierungen.
+Mittels der Publizierung von ValueSets können Auswahllisten für externe Clients bereitgestellt werden, sodass diese Kodierungen ebenfalls anbieten können.
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKValueSet wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
There are no (further) constraints on this element
Element Id
ValueSet
Short description
A set of codes drawn from one or more code systems
Definition
A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
vsd-0:Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
Mappings
rim:Entity. Role, or Act
rim:N/A
id
SΣ
1..1
System.String
There are no (further) constraints on this element
Element Id
ValueSet.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
ValueSet.url
Short description
Canonical identifier for this value set, represented as a URI (globally unique)
Definition
An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this value set is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the value set is stored on different servers.
+
Requirements
Allows the value set to be referenced by a single globally unique identifier.
+
Comments
Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
+
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.
+
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
There are no (further) constraints on this element
Element Id
ValueSet.identifier
Short description
Additional identifier for the value set (business identifier)
Definition
A formal identifier that is used to identify this value set when it is represented in other formats, or referenced in a specification, model, design or an instance.
+
Requirements
Allows externally provided and/or usable business identifiers to be easily associated with the module.
+
Comments
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this value set outside of FHIR, where it is not possible to use the logical URI.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
ValueSet.version
Short description
Business version of the value set
Definition
The identifier that is used to identify this version of the value set when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.
+
Comments
There may be different value set instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the value set with the format [url]|[version].
There are no (further) constraints on this element
Element Id
ValueSet.name
Short description
Name for this value set (computer friendly)
Definition
A natural language name identifying the value set. This name should be usable as an identifier for the module by machine processing applications such as code generation.
+
Requirements
Support human navigation and code generation.
+
Comments
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.
There are no (further) constraints on this element
Element Id
ValueSet.status
Short description
draft | active | retired | unknown
Definition
The status of this value set. Enables tracking the life-cycle of the content. The status of the value set applies to the value set definition (ValueSet.compose) and the associated ValueSet metadata. Expansions do not have a state.
+
Comments
Allows filtering of value sets that are appropriate for use versus not.See also the valueset-workflowStatus extension for additional status information related to the editorial process.
There are no (further) constraints on this element
Element Id
ValueSet.experimental
Short description
For testing purposes, not real usage
Definition
A Boolean value to indicate that this value set is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
+
Requirements
Enables experimental content to be developed following the same lifecycle that would be used for a production-level value set.
+
Comments
Allows filtering of value sets that are appropriate for use versus not.
There are no (further) constraints on this element
Element Id
ValueSet.date
Short description
Date last changed
Alternate names
Revision Date
Definition
The date (and optionally time) when the value set was created or revised (e.g. the 'content logical definition').
+
Comments
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
There are no (further) constraints on this element
Element Id
ValueSet.publisher
Short description
Name of the publisher (organization or individual)
Definition
The name of the organization or individual that published the value set.
+
Requirements
Helps establish the "authority/credibility" of the value set. May also allow for contact.
+
Comments
Usually an organization but may be an individual. The publisher (or steward) of the value set is the organization or individual primarily responsible for the maintenance and upkeep of the value set. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the value set. This item SHOULD be populated unless the information is available from context.
There are no (further) constraints on this element
Element Id
ValueSet.description
Short description
Natural language description of the value set
Alternate names
Scope, Purpose
Definition
A free text natural language description of the value set from a consumer's perspective. The textual description specifies the span of meanings for concepts to be included within the Value Set Expansion, and also may specify the intended use and limitations of the Value Set.
+
Comments
This description can be used to capture details such as why the value set was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the value set as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the value set is presumed to be the predominant language in the place the value set was created).The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description.
There are no (further) constraints on this element
Element Id
ValueSet.useContext
Short description
The context that the content is intended to support
Definition
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate value set instances.
+
Requirements
Assist in searching for appropriate content.
+
Comments
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
A code that identifies the type of context being specified by this usage context.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
ValueSet.immutable
Short description
Indicates whether or not any change to the content logical definition may occur
Definition
If this is set to 'true', then no new versions of the content logical definition can be created. Note: Other metadata might still change.
+
Comments
Normally immutability is set to 'false', which is the default assumption if it is not populated. Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change. For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition.
There are no (further) constraints on this element
Element Id
ValueSet.purpose
Short description
Why this value set is defined
Definition
Explanation of why this value set is needed and why it has been designed as it has.
+
Comments
This element does not describe the usage of the value set. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this value set.
There are no (further) constraints on this element
Element Id
ValueSet.copyright
Short description
Use and/or publishing restrictions
Alternate names
License, Restrictions
Definition
A copyright statement relating to the value set and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the value set.
+
Requirements
Consumers must be able to determine any legal restrictions on the use of the value set and/or its content.
+
Comments
nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.
There are no (further) constraints on this element
Element Id
ValueSet.compose
Short description
Content logical definition of the value set (CLD)
Alternate names
Content Logical Definition, CLD
Definition
A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD).
There are no (further) constraints on this element
Element Id
ValueSet.compose.lockedDate
Short description
Fixed date for references with no specified version (transitive)
Definition
The Locked Date is the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version.
+
Comments
With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.
There are no (further) constraints on this element
Element Id
ValueSet.compose.inactive
Short description
Whether inactive codes are in the value set
Definition
Whether inactive codes - codes that are not approved for current use - are in the value set. If inactive = true, inactive codes are to be included in the expansion, if inactive = false, the inactive codes will not be included in the expansion. If absent, the behavior is determined by the implementation, or by the applicable $expand parameters (but generally, inactive codes would be expected to be included).
+
Comments
Note that in the FHIR terminology framework, "deprecated" does not mean inactive, but in some code systems, e.g. LOINC, "deprecated" does mean inactive. Code systems should define what codes are considered to be inactive. If this is not clearly defined (including in the FHIR code system resource), then all codes are assumed to be active.
+
The Value Set Definition specification defines an ActiveOnly element, which is the reverse of this element e.g. (ValueSet.compose.inactive=FALSE) is the same as (VSD.ActiveOnly=TRUE).
There are no (further) constraints on this element
Element Id
ValueSet.compose.include
Short description
Include one or more codes from a code system or other value set(s)
Definition
Include one or more codes from a code system or other value set(s).
+
Comments
All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is 'include all the codes that meet all these conditions'.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.system
Short description
The system the codes come from
Definition
An absolute URI which is the code system from which the selected codes come from.
+
Comments
If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes. See ''Coding.system'' for further documentation about the correct value for the system element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.version
Short description
Specific version of the code system referred to
Definition
The version of the code system that the codes are selected from, or the special version '*' for all versions.
+
Comments
This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set might not be known until a context of use binds it to a particular version. The special value '*' means all versions; It is at server discretion regarding expansions and which versions must be supported.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept
Short description
A concept defined in the system
Definition
Specifies a concept to be included or excluded.
+
Comments
The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept.display
Short description
Text to display for this code for this value set in this valueset
Definition
The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system.
+
Comments
The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept.designation
Short description
Additional representations for this concept
Definition
Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc.
+
Comments
Concepts have both a display and an array of designation. The display is equivalent to a special designation with an implied designation.use of "primary code" and a language equal to the Resource Language.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.filter
Short description
Select codes/concepts by their properties (including relationships)
Definition
Select concepts by specify a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified, they SHALL all be true.
+
Comments
Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.
The kind of operation to perform as a part of the filter criteria.
+
Comments
In case filter.property represents a property of the system, the operation applies to the selected property. In case filter.property represents a filter of the system, the operation SHALL match one of the CodeSystem.filter.operator values.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.filter.value
Short description
Code from the system, or regex criteria, or boolean value for exists
Definition
The match value may be either a code defined by the system, or a string value, which is a regex match on the literal string of the property value (if the filter represents a property defined in CodeSystem) or of the system filter value (if the filter represents a filter defined in CodeSystem) when the operation is 'regex', or one of the values (true and false), when the operation is 'exists'.
+
Comments
Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.valueSet
Short description
Select the contents included in this value set
Definition
Selects the concepts found in this value set (based on its value set definition). This is an absolute URI that is a reference to ValueSet.url. If multiple value sets are specified this includes the union of the contents of all of the referenced value sets.
+
Comments
The value set URI is either a logical reference to a defined value set such as a SNOMED CT reference set, or a direct reference to a value set definition using ValueSet.url. The reference might not refer to an actual FHIR ValueSet resource; in this case, whatever is referred to is an implicit definition of a value set that needs to be clear about how versions are resolved.
There are no (further) constraints on this element
Element Id
ValueSet.compose.exclude
Short description
Explicitly exclude codes from a code system or other value sets
Definition
Exclude one or more codes from the value set based on code system filters and/or other value sets.
+
Comments
Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.
There are no (further) constraints on this element
Element Id
ValueSet.expansion
Short description
Used when the value set is "expanded"
Definition
A value set can also be "expanded", where the value set is turned into a simple collection of enumerated codes. This element holds the expansion, if it has been performed.
+
Comments
Expansion is performed to produce a collection of codes that are ready to use for data entry or validation. Value set expansions are always considered to be stateless - they are a record of the set of codes in the value set at a point in time under a given set of conditions, and are not subject to ongoing maintenance.
+
Expansion.parameter is a simplified list of parameters - a subset of the features of the Parameters resource.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.identifier
Short description
Identifies the value set expansion (business identifier)
Definition
An identifier that uniquely identifies this expansion of the valueset, based on a unique combination of the provided parameters, the system default parameters, and the underlying system code system versions etc. Systems may re-use the same identifier as long as those factors remain the same, and the expansion is the same, but are not required to do so. This is a business identifier.
+
Comments
Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).
There are no (further) constraints on this element
Element Id
ValueSet.expansion.timestamp
Short description
Time ValueSet expansion happened
Definition
The time at which the expansion was produced by the expanding system.
+
Comments
This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.total
Short description
Total number of codes in the expansion
Definition
The total number of concepts in the expansion. If the number of concept nodes in this resource is less than the stated number, then the server can return more using the offset parameter.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.offset
Short description
Offset at which this resource starts
Definition
If paging is being used, the offset at which this resource starts. I.e. this resource is a partial view into the expansion. If paging is not being used, this element SHALL NOT be present.
+
Comments
Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.parameter
Short description
Parameter that controlled the expansion process
Definition
A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion.
+
Comments
The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).
There are no (further) constraints on this element
Element Id
ValueSet.expansion.parameter.name
Short description
Name as assigned by the client or server
Definition
Name of the input parameter to the $expand operation; may be a server-assigned name for additional default or other server-supplied parameters used to control the expansion process.
+
Comments
The names are assigned at the discretion of the server.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.abstract
Short description
If user cannot select this entry
Definition
If true, this entry is included in the expansion for navigational purposes, and the user cannot select the code directly as a proper value.
+
Comments
This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.
+
Meaning When Missing
If this is not populated, systems can assume that the concept it not abstract. This SHALL always be populated for abstract concepts
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.inactive
Short description
If concept is inactive in the code system
Definition
If the concept is inactive in the code system that defines it. Inactive codes are those that are no longer to be used, but are maintained by the code system for understanding legacy data. It might not be known or specified whether an concept is inactive (and it may depend on the context of use).
+
Comments
This should only have a value if the concept is inactive.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.version
Short description
Version in which this code/display is defined
Definition
The version of the code system from this code was taken. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
The exact value of the version string is specified by the system from which the code is derived.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.code
Short description
Code - if blank, this is not a selectable code
Definition
The code for this item in the expansion hierarchy. If this code is missing the entry in the hierarchy is a place holder (abstract) and does not represent a valid code in the value set.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.designation
Short description
Additional representations for this item
Definition
Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation.
+
Comments
The designations provided must be based on the value set and code system definitions.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.contains
Short description
Codes contained under this entry
Definition
Other codes and entries contained under this entry in the hierarchy.
+
Comments
If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion.
+
+
+
+
+
+
Anmerkungen zu Must-Support-Feldern
+
ValueSet.url
+
Bedeutung: Eindeutige Url zur Identifizierung des ValueSets. Absolute Urls sind zu bevorzugen.
+
Hinweise: OIDs SOLLTEN als weitere Identifier des CodeSystems verwendet werden. In jedem Fall SOLLTE eine Canonical Url vergeben werden.
+
ValueSet.version
+
Bedeutung: Version des ValueSets
+
Hinweise: Jede Änderung des dazugehörigen CodeSystems MUSS eine Änderung in der Version des CodeSystems und ValueSets nach sich ziehen.
+
ValueSet.name
+
Bedeutung: Maschinenlesbarer Name des ValueSets
+
Hinweise: Der Constraint vsd-0 ist hierbei zu beachten.
+
ValueSet.status
+
Bedeutung: Indikation, ob das ValueSet in aktiver Verwendung ist.
+
Hinweise: Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "active" und "retired". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
ValueSet.useContext
+
Bedeutung: Angabe für welches Datenelement das ValueSet relevant ist
+
Hinweise: Es muss mindestens ein useContext angegeben werden, in dem der Ressourcen-Typ kodiert wird, in dem das ValueSet in einem Element zur Verwendung kommt.
+
ValueSet.expansion
+
Bedeutung: Angabe der Konzepte aus denen sich das ValueSet zusammensetzt.
+
Hinweise: Mindestens MUSS ein Code und ein Anzeigetext spezifiziert werden.
+
+
+
+
+
Interaktionen
+
Für die Ressource ValueSet MUSS die REST-Interaktion "READ" implementiert werden.
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
Der Suchparameter "context-type-value" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/ValueSet?context-type-value=http://terminology.hl7.org/CodeSystem/usage-context-type|focus$http://hl7.org/fhir/resource-types|Encounter
+
Mit dieser Abfrage können hausinterne Kataloge anhand des Ressource-Typs ermittelt werden. Diese Informationen sind u.a. relevant im Kontext von:
+
+
Hausinternen Prozeduren/Diagnosen-Codes
+
Kodierung von Encounter-Informationen (z.B. Wahlleistungen, Orttypen)
+
+
Use Cases im Zusammenhang:
+
(A) Zur Konfigurationszeit können passende ValueSets von einem Server spezifisch für einen Ressourcentyp abgerufen und vorbereitend auf eine Systemintegration begutachtet bzw. in Client-Systeme eingebunden werden. In diesem Sinne wird die Abfrage im Kontext der Terminvereinbarung durch einen Termin-Requestor genutzt.
+
(B) Zur Laufzeit können spezifische ValueSets synchronisiert bzw. direkt in die Eingabemasken von Clients eingebunden werden.
ISiK unterstützt Anwendungsszenarien, in denen durch das Krankenhaus erbrachte Leistungen erfasst oder gegenüber Kostenträgern abgerechnet werden. In diesen Anwendungsszenarien wird das Versicherungsverhältnis verwendet, um bspw. den Versicherungsstatus oder die Rechnungsanschrift der Versicherung zu ermitteln.
+
In FHIR werden Versicherungsverhältnisse mit der Coverage-Ressource repräsentiert.
+
+
+
+
+
Kompatibilität
+
Profil ISiKVersicherungsverhaeltnisGesetzlich
+
Das Profil ISiKVersicherungsverhaeltnisGesetzlich basiert auf dem Profil Coverage der deutschen Basisprofile.
+Instanzen, die gegen ISiKVersicherungsverhaeltnisGesetzlich valide sind, sind auch valide gegen
Kostenübernahme im Rahmen eines gesetzlichen Versicherungsverhältnisses in Deutschland.
+
Comments
The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
There are no (further) constraints on this element
Element Id
Coverage.identifier
Short description
Business Identifier for the coverage
Definition
A unique identifier assigned to this coverage.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.status
Short description
active | cancelled | draft | entered-in-error
Definition
The status of the resource instance.
+
Requirements
Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.
+
Comments
This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.
Art der Versicherung: Selbstzahler, gesetzliche/private Versicherung, Berufsgenossenschaft oder Sozialamt
+
Requirements
The order of application of coverages is dependent on the types of coverage.
+
Comments
28.07.2017 (zulip): TC Konsens bzgl. Verwendung eines eigenen ValueSets anstelle des im Standrad definierten preferred bindings, da die dortigen Codes nicht passen.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Coverage.policyHolder
Short description
Owner of the policy
Definition
The party who 'owns' the insurance policy.
+
Requirements
This provides employer information in the case of Worker's Compensation and other policies.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.subscriber.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Pattern
+
{
+ "system": "http://fhir.de/sid/gkv/kvid-10"
+}
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.subject
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Pattern
+
{
+ "system": "http://fhir.de/sid/gkv/kvid-10"
+}
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Die Angabe des Namens des Versicherten dient der geeigneten Darstellung für den Benutzer und hat keine technische Bedeutung.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.period
Short description
Coverage start and end dates
Definition
Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.
+
Requirements
Some insurers require the submission of the coverage term.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Gibt den Kostenträger des Versicherten an. Die Angabe der IK-Nummer als logische Referenz sowie des Namens als Display ist zwingend erforderlich.
+Die Referenz auf eine Resource vom Typ Organization, die weitere Details zur Versicherung enthalten kann (z.B. Adresse, Kontaktdaten) ist optional.
+Sofern eine zweite Referenz auf einen Kostenträger existiert, so handelt es sich hierbei um den abrechnenden Kostenträger
+
Requirements
Need to identify the issuer to target for claim processing and for coordination of benefit processing.
+
Comments
Die Angabe der IK-Nummer des Versicherers in payor.identifier ist verpflichtend. Weitere Angaben zum Versicherer (Name, Adresse) können in einer Organization-Resource hinterlegt werden, auf die hier referenziert wird.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage.payor.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.payor.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Coverage.payor.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.class.type
Short description
Type of class such as 'group' or 'plan'
Definition
The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.
+
Requirements
The insurer issued label for a specific health card value.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.order
Short description
Relative order of the coverage
Definition
The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.
+
Requirements
Used in managing the coordination of benefits.
+
Comments
Es git derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Für die Priorisierung der Versicherungsverhältnisse sollte statt dessen Account.coverage.priority verwendet werden, da die Priorisierung abhängig von Fall- und Abrechnungsart unterschiedlich sein kann.
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.network
Short description
Insurer network
Definition
Die Versicherungsleistungen sind an ein bestimmtes Netzwerk von Gesundheitsdienstleistern gebunden
+
Requirements
Used in referral for treatment and in claims processing.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary
Short description
Patient payments for services/products
Alternate names
CoPay, Deductible, Exceptions
Definition
A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.
+
Requirements
Required by providers to manage financial transaction with the patient.
+
Comments
For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.type
Short description
Exception category
Definition
The code for the specific exception.
+
Requirements
Needed to identify the exception associated with the amount for the patient.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.period
Short description
The effective period of the exception
Definition
The timeframe during when the exception is in force.
+
Requirements
Needed to identify the applicable timeframe for the exception for the correct calculation of patient costs.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.subrogation
Short description
Reimbursement to insurer
Definition
When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.
+
Requirements
See definition for when to be used.
+
Comments
Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.
There are no (further) constraints on this element
Element Id
Coverage.contract
Short description
Contract details
Definition
The policy(s) which constitute this insurance coverage.
+
Requirements
To reference the legally binding contract between the policy holder and the insurer.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage
Short description
Versicherungsdaten
Definition
Angaben zur Versicherung oder zur Kostenübernahme durch den Patienten selbst oder durch Dritte.
+
Comments
The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
There are no (further) constraints on this element
Element Id
Coverage.identifier
Short description
Business Identifier for the coverage
Definition
A unique identifier assigned to this coverage.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.identifier:pkv
Short description
An identifier intended for computation
Definition
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.status
Short description
active | cancelled | draft | entered-in-error
Definition
The status of the resource instance.
+
Requirements
Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.
+
Comments
This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.
There are no (further) constraints on this element
Element Id
Coverage.type
Short description
Versicherungsart
Definition
Art der Versicherung: Selbstzahler, gesetzliche/private Versicherung, Berufsgenossenschaft oder Sozialamt
+
Requirements
The order of application of coverages is dependent on the types of coverage.
+
Comments
28.07.2017 (zulip): TC Konsens bzgl. Verwendung eines eigenen ValueSets anstelle des im Standrad definierten preferred bindings, da die dort igen Codes nicht passen.
There are no (further) constraints on this element
Element Id
Coverage.type.coding
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.coding:VersicherungsArtDeBasis
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Coverage.policyHolder
Short description
Owner of the policy
Definition
The party who 'owns' the insurance policy.
+
Requirements
This provides employer information in the case of Worker's Compensation and other policies.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.subscriber.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.subscriber.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary
Short description
Begünstigte Person
Definition
Person, auf die sich die Kostenübernahme bezieht (der Patient)
+
Requirements
This is the party who receives treatment for which the costs are reimbursed under the coverage.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.subject
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.period
Short description
Coverage start and end dates
Definition
Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.
+
Requirements
Some insurers require the submission of the coverage term.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Person, die die Kosten übernimmt (beim Selbstzahlerverhältnis i.d.R. identisch mit subscriber)
+Sonderfall: Die Kostenübernahme wird von einer Person (subscriber) erklärt, die Übernahme erfolgt jedoch durch eine Organisation
+
Requirements
Need to identify the issuer to target for claim processing and for coordination of benefit processing.
+
Comments
May provide multiple identifiers such as insurance company identifier or business identifier (BIN number).
+For selfpay it may provide multiple paying persons and/or organizations.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage.class.type
Short description
Type of class such as 'group' or 'plan'
Definition
The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.
+
Requirements
The insurer issued label for a specific health card value.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.order
Short description
Relative order of the coverage
Definition
The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.
+
Requirements
Used in managing the coordination of benefits.
+
Comments
Es git derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Für die Priorisierung der Versicherungsverhältnisse sollte statt dessen Account.coverage.priority verwendet werden, da die Priorisierung abhängig von Fall- und Abrechnungsart unterschiedlich sein kann.
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.network
Short description
Insurer network
Definition
Die Versicherungsleistungen sind an ein bestimmtes Netzwerk von Gesundheitsdienstleistern gebunden
+
Requirements
Used in referral for treatment and in claims processing.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary
Short description
Patient payments for services/products
Alternate names
CoPay, Deductible, Exceptions
Definition
A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.
+
Requirements
Required by providers to manage financial transaction with the patient.
+
Comments
For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.type
Short description
Exception category
Definition
The code for the specific exception.
+
Requirements
Needed to identify the exception associated with the amount for the patient.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.period
Short description
The effective period of the exception
Definition
The timeframe during when the exception is in force.
+
Requirements
Needed to identify the applicable timeframe for the exception for the correct calculation of patient costs.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.subrogation
Short description
Reimbursement to insurer
Definition
When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.
+
Requirements
See definition for when to be used.
+
Comments
Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.
There are no (further) constraints on this element
Element Id
Coverage.contract
Short description
Contract details
Definition
The policy(s) which constitute this insurance coverage.
+
Requirements
To reference the legally binding contract between the policy holder and the insurer.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
cdanetv4:D01 through D09
v2:IN1-16, 18, 19
cpha3pharm:C.35
+
+
+
+
+
Anmerkungen zu den Must-Support Feldern
+
Das Profil ISiKVersicherungsverhaeltnisGesetzlich
+
Coverage.identifier
+
Hinweise: Grundsätzlich ist zu beachten, dass das Versicherungsverhältnis für die gesetzliche Versicherung durch die 30-stellige KVNR identifiziert wird. Die 10-stellige KVNR ist hingegen ein Identifier für das Datenobjekt Patient. Siehe
Command 'pagelink' could not render: Page not found.
. Es wird in ISiK davon ausgegangen, dass die 30-stellige KVNR nicht in bestätigungrelevanten Systemen geführt wird, sodass diese nicht als zuverlässiger Identifier für das Versicherungsverhältnis verwendbar ist. Bei einer Suche nach einem Versicherungsverhältnis SOLLTE dieses per Chaining auf das Datenobjekt Patient ermittelt werden.
+
Coverage.status
+
Bedeutung: Der Status einer Instanz des Profils ISiKVersicherungsverhaeltnisGesetzlich.
+
Hinweise: Das Element status macht deutlich, ob diese Instanz genutzt werden kann oder ob sie bspw. als ungültig oder falsch gekennzeichnet ist, siehe FHIR Kernspezifikaton.
+
Coverage.type
+
Bedeutung: Das Element type kennzeichnet die Art der Versicherung.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..f4234203
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,296 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support-Feldern
+
Condition.clinicalStatus
+
Bedeutung: Kodierter klinischer Status der Diagnose. MUSS angegeben werden, da die Interpretation der Diagnose davon abhängt ob diese 'aktiv' ist oder einen anderen Status aufweist. Alle in einem System möglichen Clinical-Status-Werte müssen über FHIR korrekt repräsentiert werden, können mindestens jedoch die Status-Werte "active" und "inactive" unterstützen. Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Bedeutung: Kodierte Diagnose. Die Kodierung KANN nach den Vorgaben des BfArM per ICD-10GM kodiert werden. Weiterhin sind folgende Kodiersysteme u.a. auf Basis von Empfehlungen des BfArM zulässig:
Hinweise: Angaben zur ICD-Diagnosesicherheit ("A", "G", "V", "Z") müssen vom Code abgetrennt und in der Extension angegeben werden.
+
Condition.subject
+
Bedeutung: Ein Patientenbezug der Diagnose MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Condition.encounter
+
Bedeutung: Der Fallbezug einer Diagnose MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Hinweise:
+
Eine Verlinkung der Referenz auf den dazugehörigen Kontakt SOLL auf die Ebene des Abteilungskontaktes (entsprechend ISiKKontaktGesundheitseinrichtung) erfolgen.
+Bei der Auswahl des Kontaktes ist zu beachten, dass mehrere Encounter-Ressourcen mit identischen Aufnahmenummer-Identifiern existieren können (Abbildung Vor- und nachstationäre Kontakte).
+
Condition.recordedDate
+
Bedeutung: Das Dokumentationsdatum der Diagnose MUSS zu Qualitätssicherungszwecken angegeben werden. Dies ist das fachliche Dokumentationsdatum, nicht zu verwechseln mit der technischen Anlage des Datensatzes im Primärsystem. Diese beiden Daten können jedoch identisch sein.
+
Hinweise:
+
Das Recorded Date MUSS mindestens auf den Monat genau angegeben werden (vgl. FHIRPath Constraint rec-1)
+
Condition.note
+
Bedeutung: Weitere optionale Freitext-Notizen bezogen auf die Diagnose.
+
Condition.extension:ReferenzPrimaerdiagnose
+
Bedeutung: Bei mehrfachkodierten ICD-Diagnosen (z.B. Kreuz-Stern-Notation) muss die Sekundär- auf die Primärdiagnose verlinkt werden
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Beispiele.html
new file mode 100644
index 00000000..917e5a1e
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Beispiele.html
@@ -0,0 +1,309 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Kompatibilitaet.html
new file mode 100644
index 00000000..91227644
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Kompatibilitaet.html
@@ -0,0 +1,265 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKDiagnose wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKDiagnose valide sind, auch valide sind gegen:
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Motivation.html
new file mode 100644
index 00000000..61f7c438
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Motivation.html
@@ -0,0 +1,264 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Die Möglichkeit, auf eine Übersicht der Diagnosen eines Patienten zuzugreifen, Patienten anhand ihrer Diagnose zu suchen oder zu prüfen, ob eine konkrete Diagnose bei einem Patienten vorliegt, sind wichtige Funktionen im klinischen Behandlungsablauf.
+
In FHIR werden Diagnosen mit der Condition-Ressource repräsentiert.
+
Da die Diagnosen in klinischen Primärsystemen in der Regel in ICD-10-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches.
+Falls eine Diagnose zwar dokumentiert, aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Diagnose möglich.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Profil.html
new file mode 100644
index 00000000..a6e9cddb
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Diagnose-Diagnose_Profil.html
@@ -0,0 +1,874 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
con-5:Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
con-4:If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-3:Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
isik-con1:Falls eine kodierte Diagnose vorliegt muss angegeben werden durch welchen Kontakt diese Dokumentation erfolgte. code.coding.exists() implies encounter.exists()
Mappings
rim:Entity. Role, or Act
workflow:Event
sct-concept:< 243796009 |Situation with explicit context| : 246090004 |Associated finding| = ( ( < 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 272379006 |Event|)
There are no (further) constraints on this element
Element Id
Condition.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.identifier
Short description
External Ids for this condition
Definition
Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.
+
Requirements
Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.
+
Comments
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.
The verification status to support the clinical status of the condition.
+
Comments
verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.
+The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.
Identification of the condition, problem or diagnosis
Alternate names
type
Definition
Identification of the condition, problem or diagnosis.
+
Requirements
0..1 to account for primarily narrative only resources.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
icd-text-1:Entweder MUSS eine kodierte Diagnose vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt. coding.exists().not() implies text.exists()
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
workflow:Event.code
w5:FiveWs.what[x]
sct-concept:code 246090004 |Associated finding| (< 404684003 |Clinical finding| MINUS
+<< 420134006 |Propensity to adverse reactions| MINUS
+<< 473010000 |Hypersensitivity condition| MINUS
+<< 79899007 |Drug interaction| MINUS
+<< 69449002 |Drug action| MINUS
+<< 441742003 |Evaluation finding| MINUS
+<< 307824009 |Administrative status| MINUS
+<< 385356007 |Tumor stage finding|)
+OR < 413350009 |Finding with explicit context|
+OR < 272379006 |Event|
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.system
Short description
Canonische CodeSystem URL für ICD-10-GM
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.version
Short description
Die Jahresversion von ICD-10-GM. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von ICD-10-GM ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von ICD-10-GM ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.code
Short description
Der ICD-10-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:ICD-10-GM.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.system
Short description
Canonische CodeSystem URL für Alpha-ID
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.version
Short description
Die Jahresversion von Alpha-ID. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von Alpha-ID ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von Alpha-ID ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.code
Short description
Der Alpha-ID-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:Alpha-ID.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.system
Short description
Identity of the terminology system
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.system
Short description
Identity of the terminology system
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Condition.code.coding:Orphanet.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Condition.code.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Condition.bodySite
Short description
Anatomical location, if relevant
Definition
The anatomical location where this condition manifests itself.
+
Comments
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both.
There are no (further) constraints on this element
Element Id
Condition.subject
Short description
Who has the condition?
Alternate names
patient
Definition
Indicates the patient or group who the condition record is associated with.
+
Requirements
Group is typically used for veterinary or public health use cases.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Condition.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Condition.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Condition.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Condition.encounter
Short description
Encounter created as part of
Definition
The Encounter during which this Condition was created or to which the creation of this record is tightly associated.
+
Comments
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.start.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Condition.onset[x]:onsetPeriod.end.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
workflow:Event.occurrence[x]
w5:FiveWs.init
v2:PRB-16
rim:.effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value
abatement[x]
I
0..1
There are no (further) constraints on this element
Element Id
Condition.abatement[x]
Short description
When in resolution/remission
Definition
The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate.
+
Comments
There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
w5:FiveWs.done[x]
rim:.effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed
There are no (further) constraints on this element
Element Id
Condition.recorder
Short description
Who recorded the condition
Definition
Individual who recorded the record and takes responsibility for its content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.asserter
Short description
Person who asserts this condition
Definition
Individual who is making the condition statement.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.stage.summary
Short description
Simple summary (disease specific)
Definition
A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.stage.assessment
Short description
Formal record of assessment
Definition
Reference to a formal record of the evidence on which the staging assessment is based.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.stage.type
Short description
Kind of staging
Definition
The kind of staging, such as pathological or clinical staging.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.evidence
Short description
Supporting evidence
Definition
Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.
+
Comments
The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.
There are no (further) constraints on this element
Element Id
Condition.evidence.code
Short description
Manifestation/symptom
Definition
A manifestation or symptom that led to the recording of this condition.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Condition.evidence.detail
Short description
Supporting information found elsewhere
Definition
Links to other relevant information, including pathology reports.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Condition.note
Short description
Additional information about the Condition
Definition
Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.
+
Comments
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
isik-con1
error
Falls eine kodierte Diagnose vorliegt muss angegeben werden durch welchen Kontakt diese Dokumentation erfolgte.
code.coding.exists() implies encounter.exists()
+
icd-text-1
error
Entweder MUSS eine kodierte Diagnose vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.
Interoperabler Datenaustausch durch Informationssysteme im Krankenhaus (ISiK)
+
Die gematik wurde vom Gesetzgeber beauftragt, im Benehmen mit der Deutschen Krankenhausgesellschaft (DKG) und den maßgeblichen Bundesverbänden der Industrie im Gesundheitswesen, verbindliche Standards für den Austausch von Gesundheitsdaten mit Informationssystemen im Krankenhaus zu erarbeiten. Dieser FHIR ImplementationGuide (IG) beschreibt die für diesen Zweck entwickelten FHIR Profile und das REST-basierte Application Programming Interface (API). Die REST-API wird im Wesentlichen vom FHIR Standard vorgegeben. Dieser Leitfaden konkretisiert die ISiK-relevanten Funktionen der Standard-REST-API und trifft inhaltliche Festlegungen zu den ISiK-relevanten Ressourcen in Form von Ressourcen-Profilen.
+
Hersteller bestätigungsrelevanter Systeme sollen durch diesen IG in die Lage versetzt werden, eine konforme Implementierung zu erstellen und das Bestätigungsverfahren der gematik erfolgreich zu absolvieren.
Hinweis: Sowohl für die Implementierung der ISiK-Spezifikation als auch für den Betrieb eines Produktes, das die ISiK-Spezifikation implementiert, ist eine SNOMED-CT-Lizenz notwendig. Diese kann beim National Release Center für SNOMED CT in Deutschland beantragt werden.
+
Kontakt
+
Bringen Sie Allgemeine Fragen und Anmerkungen gerne über unser Anfrageportal ein: Anfragen ISiK + ISiP
+
Falls Sie keinen Zugang zum Anfrageportal haben und dieses nutzen wollen, senden Sie uns bitte eine Nachricht an die Adresse isik [ at ] gematik.de mit dem Betreff "Portalzugang".
Zugunsten des Leseflusses wird in dieser Publikation meist die
+männliche Form verwendet. Wir bitten, dies nicht als Zeichen einer
+geschlechtsspezifischen Wertung zu deuten. Diese Variante deckt auch alle
+weiteren Geschlechter, neben männlich und weiblich, ab.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..f72ab459
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,278 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu Must-Support-Feldern
+
CodeSystem.url
+
Bedeutung: Eindeutige Url zur Identifizierung des CodeSystems. Absolute Url sind zu bevorzugen.
+
Hinweise: OIDs SOLLTEN als weitere Identifier des CodeSystems verwendet werden. In jedem Fall SOLLTE ein Canonical Url vergeben werden.
+
CodeSystem.version
+
Bedeutung: Version des CodeSystems
+
Hinweise: Jede Änderung des CodeSystems MUSS eine Änderung in der Version des CodeSystems und gebundenen ValueSets nach sich ziehen. Die Versionierung SOLLTE auf Basis von Semantic Versioning basieren.
+
CodeSystem.name
+
Bedeutung: Maschinenlesbarer Name des CodeSystems
+
Hinweise: Der Constraint cps-0 ist hierbei zu beachten.
+
CodeSystem.status
+
Bedeutung: Indikation, ob das CodeSystem in aktiver Verwendung ist.
+
Hinweise: Alle in einem System möglichen Status-Werte MÜSSEN über FHIR korrekt repräsentiert werden. KÖNNEN mindestens jedoch die Status-Werte "active" und "retired". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
CodeSystem.content
+
Bedeutung: Angabe, ob es sich um eine vollständige Repräsentation des CodeSystems oder nur um einen Auszug handelt.
+
Hinweise: Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "fragment" und "complete". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
CodeSystem.concept
+
Bedeutung: Angabe der Konzepte, aus denen sich das CodeSystem zusammensetzt.
+
Hinweise: Es MUSS mindestens ein Code und ein Anzeigetext spezifiziert werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Beispiele.html
new file mode 100644
index 00000000..b7ad71a8
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Beispiele.html
@@ -0,0 +1,284 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Motivation.html
new file mode 100644
index 00000000..6b5a6df2
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Motivation.html
@@ -0,0 +1,268 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Katalog
+
ISiK erlaubt in diversen Kontexten die Erweiterung der Kodierung durch Krankenhaus-/Systeminterne Kodierungen. Das Profil ISiKKatalog (CodeSystem) als Profil erlaubt die Repräsentation der dazugehörigen Codes und Displaywerte.
+
Eine maschinenlesbare Repräsentation dieser Kodierungen erlaubt es Clients dazugehörige Anzeigetext und Definitionen zu verarbeiten.
+
Ein Codesystem eignet sich auch dazu, auf dessen Basis definierte ValueSets zu expandieren.
+Da ISiKValueSet expandierte Valuesets vorsieht, ist eine dynamische Expansion in der Regel nicht erforderlich.
+Darüber hinausgehend ist ein Use Case im Kontext der Katalogabfrage folgender: Ein Client möchte eine Expansion neu generieren (z.B. mit anderen Expansionen-Parametern), um das ValueSet beispielsweise in einer anderen Sprache auszugeben.
+
Normativer Status und Bestätigung
+
Dieses Profil MUSS im Rahmen der Bestätigung NICHT unterstützt werden. Falls das Profil unterstützt werden soll, MÜSSEN die hier definierten Festlegungen greifen (auch im Bestätigungsverfahren).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Profil.html
new file mode 100644
index 00000000..638a13c4
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Katalog-CodeSystem_Profil.html
@@ -0,0 +1,601 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
There are no (further) constraints on this element
Element Id
CodeSystem
Short description
Declares the existence of and describes a code system or code system supplement
Definition
The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
csd-1:Within a code system definition, all the codes SHALL be unique concept.code.combine($this.descendants().concept.code).isDistinct()
csd-0:Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
Mappings
rim:Entity. Role, or Act
rim:N/A
id
SΣ
1..1
System.String
There are no (further) constraints on this element
Element Id
CodeSystem.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
CodeSystem.url
Short description
Canonical identifier for this code system, represented as a URI (globally unique) (Coding.system)
Definition
An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this code system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the code system is stored on different servers. This is used in Coding.system.
+
Requirements
Allows the code system to be referenced by a single globally unique identifier.
+
Comments
Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
+
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.
+
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
There are no (further) constraints on this element
Element Id
CodeSystem.identifier
Short description
Additional identifier for the code system (business identifier)
Definition
A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance.
+
Requirements
Allows externally provided and/or usable business identifiers to be easily associated with the module.
+
Comments
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this code system outside of FHIR, where it is not possible to use the logical URI. Note that HL7 defines at least three identifiers for many of its code systems - the FHIR canonical URL, the OID and the V2 Table 0396 mnemonic code.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
CodeSystem.version
Short description
Business version of the code system (Coding.version)
Definition
The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. This is used in Coding.version.
+
Comments
There may be different code system instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the code system with the format [url]|[version].
There are no (further) constraints on this element
Element Id
CodeSystem.name
Short description
Name for this code system (computer friendly)
Definition
A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation.
+
Requirements
Support human navigation and code generation.
+
Comments
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
There are no (further) constraints on this element
Element Id
CodeSystem.experimental
Short description
For testing purposes, not real usage
Definition
A Boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
+
Requirements
Enables experimental content to be developed following the same lifecycle that would be used for a production-level code system.
+
Comments
Allows filtering of code systems that are appropriate for use versus not.
There are no (further) constraints on this element
Element Id
CodeSystem.date
Short description
Date last changed
Alternate names
Revision Date
Definition
The date (and optionally time) when the code system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the code system changes.
+
Comments
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the code system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
There are no (further) constraints on this element
Element Id
CodeSystem.publisher
Short description
Name of the publisher (organization or individual)
Definition
The name of the organization or individual that published the code system.
+
Requirements
Helps establish the "authority/credibility" of the code system. May also allow for contact.
+
Comments
Usually an organization but may be an individual. The publisher (or steward) of the code system is the organization or individual primarily responsible for the maintenance and upkeep of the code system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the code system. This item SHOULD be populated unless the information is available from context.
There are no (further) constraints on this element
Element Id
CodeSystem.description
Short description
Natural language description of the code system
Alternate names
Scope, Purpose
Definition
A free text natural language description of the code system from a consumer's perspective.
+
Comments
This description can be used to capture details such as why the code system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the code system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the code system is presumed to be the predominant language in the place the code system was created).
There are no (further) constraints on this element
Element Id
CodeSystem.useContext
Short description
The context that the content is intended to support
Definition
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate code system instances.
+
Requirements
Assist in searching for appropriate content.
+
Comments
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
There are no (further) constraints on this element
Element Id
CodeSystem.purpose
Short description
Why this code system is defined
Definition
Explanation of why this code system is needed and why it has been designed as it has.
+
Comments
This element does not describe the usage of the code system. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this code system.
There are no (further) constraints on this element
Element Id
CodeSystem.copyright
Short description
Use and/or publishing restrictions
Alternate names
License, Restrictions
Definition
A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system.
+
Requirements
Consumers must be able to determine any legal restrictions on the use of the code system and/or its content.
+
Comments
Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
+Sometimes, the copyright differs between the code system and the codes that are included. The copyright statement should clearly differentiate between these when required.
+Sometimes, the copyright differs between the code system and the codes that are included. The copyright statement should clearly differentiate between these when required.
There are no (further) constraints on this element
Element Id
CodeSystem.caseSensitive
Short description
If code comparison is case sensitive
Definition
If code comparison is case sensitive when codes within this system are compared to each other.
+
Comments
If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case. This element is primarily provided to support validation software.
There are no (further) constraints on this element
Element Id
CodeSystem.versionNeeded
Short description
If definitions are not stable
Definition
This flag is used to signify that the code system does not commit to concept permanence across versions. If true, a version must be specified when referencing this code system.
+
Comments
Best practice is that code systems do not redefine concepts, or that if concepts are redefined, a new code system definition is created. But this is not always possible, so some code systems may be defined as 'versionNeeded'.
+
Most code systems occasionally refine the displays defined for concepts between versions. Contexts in which the concept display values are validated may require that the version be specified for some code systems irrespective of the value of this property.
There are no (further) constraints on this element
Element Id
CodeSystem.count
Short description
Total concepts in the code system
Definition
The total number of concepts defined by the code system. Where the code system has a compositional grammar, the basis of this count is defined by the system steward.
+
Comments
The count of concepts defined in this resource cannot be more than this value but may be less for several reasons - see the content element.
There are no (further) constraints on this element
Element Id
CodeSystem.filter
Short description
Filter that can be used in a value set
Definition
A filter that can be used in a value set compose statement when selecting concepts using a filter.
+
Comments
Note that filters defined in code systems usually require custom code on the part of any terminology engine that will make them available for use in value set filters. For this reason, they are generally only seen in high value published terminologies.
There are no (further) constraints on this element
Element Id
CodeSystem.property.code
Short description
Identifies the property on the concepts, and when referred to in operations
Definition
A code that is used to identify the property. The code is used internally (in CodeSystem.concept.property.code) and also externally, such as in property filters.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
CodeSystem.concept
Short description
Concepts in the code system
Definition
Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are.
+
Comments
If this is empty, it means that the code system resource does not represent the content of the code system.
There are no (further) constraints on this element
Element Id
CodeSystem.concept.definition
Short description
Formal definition
Definition
The formal definition of the concept. The code system resource does not make formal definitions required, because of the prevalence of legacy systems. However, they are highly recommended, as without them there is no formal meaning associated with the concept.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
CodeSystem.concept.designation
Short description
Additional representations for the concept
Definition
Additional representations for the concept - other languages, aliases, specialized purposes, used for particular purposes, etc.
+
Requirements
Many concept definition systems support multiple representations, in multiple languages, and for multiple purposes.
+
Comments
Concepts have both a display and an array of designation. The display is equivalent to a special designation with an implied designation.use of "primary code" and a language equal to the Resource Language.
There are no (further) constraints on this element
Element Id
CodeSystem.concept.concept
Short description
Child Concepts (is-a/contains/categorizes)
Definition
Defines children of a concept to produce a hierarchy of concepts. The nature of the relationships is variable (is-a/contains/categorizes) - see hierarchyMeaning.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..0d58b26b
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,277 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support Feldern
+
Encounter.status
+
Bedeutung: Der Status MUSS insbesondere zur Differenzierung von abgeschlossenen und derzeitig noch aktiven Kontakten angegeben werden. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden. Es KÖNNEN jedoch mindestens die Status-Werte "in-progress", "finished" und "cancelled" unterstützt werden. Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
Anwendungshinweise: Weitere Informationen zur Suche nach "Encounter.period" finden sich in der FHIR-Basisspezifikation - Abschnitt "Date Search". Bei der Formulierung der Suche sollten die Vorgaben aus der Definition der Such-Prefixe - und hier insbesondere die Unterschiede zwischen "lt" und "eb" bzw. "gt" und "sa" - beachtet werden.
+
Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend.
+
+
Der Suchparameter "date-start" MUSS unterstützt werden:
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Kompatibilitaet.html
new file mode 100644
index 00000000..b3e367d5
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Kompatibilitaet.html
@@ -0,0 +1,265 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKKontaktGesundheitseinrichtung wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKKontaktGesundheitseinrichtung valide sind, auch valide sind gegen:
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden..
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Motivation.html
new file mode 100644
index 00000000..06d2b4c5
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Motivation.html
@@ -0,0 +1,351 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Informationen über die Besuche des Patienten entlang seines Behandlungspfades im Krankenhaus sind ein wichtiger Bestandteil des einrichtungsinternen Datenaustausches.
+Sie ermöglichen die Unterscheidung von stationären und ambulanten sowie aufgenommenen und entlassenen Patienten.
+Weiterhin ist aus den Besuchsinformationen der aktuelle Aufenthaltsort des Patienten (Fachabteilung, Station, Bettplatz) ermittelbar.
+Klinische Ressourcen werden in FHIR durch Verlinkung auf die Encounter-Ressource in einen Kontext zum Besuch gestellt. Dieser Kontext ist wichtig für die Steuerung von Zugriffsberechtigungen und Abrechnungsprozessen.
+
Zu Beginn der meisten klinischen Workflows steht die Auswahl des Besuchskontextes. Dies geschieht bspw. durch das Suchen der Encounter-Ressource anhand von Eigenschaften wie Aufnahmenummer, Fallart oder Aufnahmedatum. Daraufhin werden die zutreffenden Suchergebnisse angezeigt und der gewünschte Besuch ausgewählt.
+
+
Der Begriff "Fall" im Kontext von FHIR
+
Wichtig ist die Herausstellung, dass "Besuch" und "Fall" wechselseitig keine synonyme Begriffe sind.
+
Der Begriff "Fall" gruppiert im Sprachgebrauch verschiedene Konzepte, die in FHIR durch unterschiedliche Ressourcen repräsentiert werden:
+
+
Aufenthalt/Besuch/Kontakt (Encounter):
+Der stationäre Aufenthalt oder der ambulante Kontakt eines Patienten in einer Gesundheitseinrichtung wird in FHIR durch die Ressource Encounter abgebildet.
+
+
Abrechnungsfall (Account):
+Der Fall, im Sinne einer Gruppierung von medizinischen Leistungen, die in einem gemeinsamen Kontext abgerechnet werden, sind in FHIR durch die Ressource Account repräsentiert. Ein Abrechnungsfall kann mehrere Encounter umfassen (z.B. vorstationärer Besuch, stationärer Aufenthalt und nachstationäre Besuche)
+
+
+
+
+
+
Medizinischer Fall (EpisodeOfCare):
+Der medizinische Fall gruppiert Informationen, die im Kontext einer gemeinsamen (Dauer-)Diagnose stehen und wird in FHIR durch die EpisodeOfCare dargestellt.
+
+
+
+
+
+
+
+
Der Begriff "Fall" im Kontext der Medizininformatik-Initiative
Einrichtungskontakt:
+Als Kontakt eines Patienten mit einer Einrichtung (z.B: Klinik) gruppiert mehrere Besuche bei einer Einrichtung als gemeinsamen Behandlungskontext.
+
+
Abteilungskontakt:
+Als Kontakt des Patienten mit einer Fachabteilung eines Krankenhauses (z.B. einer Ambulanz oder einer stationären Fachabteilung).
+
+
Versorgungsstellenkontakt:
+Als Kontakt des Patienten mit konkreten Servicestellen, wie z.B. Radiologie oder Endoskopie
+
+
+
Zur Unterscheidung der verschiedenen Kontaktebenen wird in der MI-I eine Codierung in Encounter.type verwendet. Die Hierarchie der Encounter wird über die Encounter.partOf-Relation hergestellt. Ambulante Besuche werden in dem Modell derzeit noch nicht berücksichtigt.
+
+
+
+
+
+
Der Begriff "Fall" im Kontext der ISiK-Spezifikation
+
Für die Ausbaustufe 2 und 3 des ISiK Basismoduls werden alle zuvor genannten Sichtweise und Modelle berücksichtigt:
+
+
+
+
+
Verpflichtend umzusetzen ist für die bestätigungsrelevanten Systeme der Account, im Sinne der Gruppierung einzelner Besuche, zu einem gemeinsamen (Abrechnungs-)Fall sowie der Encounter der Ebene "Abteilungskontakt" im Sinne des Modells der Medizininformatikinitiative.
+
Herstellern steht es frei, weitere Ressourcen, wie zum Beispiel die EpisodeOfCare oder den Encounter, im Sinne des Einrichtungskontaktes bzw. des Versorgungststellenkontaktes, zu implementieren.
+
Wichtig sind dabei jedoch folgende Punkte zu beachten:
+
+
Encounter im ISiK-Kontext sind stets als "Abteilungskontakte, im Sinne der MI-I mit dem entsprechenden Encounter.type-Code, zu kennzeichnen.
+
jegliche im ISiK-Basis-Modul, als auch in anderen ISiK-Modulen definierte Ressourcen, die über einen Encounter-Kontext verfügen, müssen auf einen ISiK-Encounter (Abteilungskontakt) referenzieren.
+
+
+
+
+
+
+
Die Repräsentation der "Fall"-Nummer
+
Die "Fall"-Nummer ist ein im Kontext der stationären Versorgung häufig verwendetes Vehikel, um (insbesondere in der HL7-V2-Kommunikation) mit einfachen Mitteln den Fallkontext medizinischer Dokumentationen herzustellen.
+
In den meisten Fällen handelt es sich bei der "Fall"-Nummer um einen eindeutigen Identifier des Abrechnungsfalls.
+Im ISiK-Kontext ist die Fallnummer daher als Identifier des Accounts zu sehen und nicht geeignet, einen Encounter eindeutig zu identifizieren und damit den für FHIR-Ressourcen erforderlichen Encounter-Kontext zu etablieren.
+Es müssen zusätzliche Kriterien, wie z.B. Zeitraum(Encounter.period), Fallart (Encounter.class) oder Status (Encounter.status) berücksichtigt werden, um den korrekten Encounter zu finden.
+
ISiK berücksichtigt jedoch die gängige Praxis, dass die Fallnummer als primäres Suchkriterium verwendet wird; auch von Systemen, die rein der medizinischen Versorgung dienen und keine Abrechnungsfunktionen implementieren.
+Um insbesondere Subsysteme von der Pflicht zu entbinden, die Account-Ressource zu implementieren, nur um Zugriff zur Fallnummer zu bekommen, ist das Mitführen des Account-Identifiers als logische Referenz auf den Account im Encounter verpflichtend. Die Fallnummer eines Encounters kann daher auch ohne Kenntnis des Accounts ermittelt werden.
+
+
+
+
Hinweis
+
Änderung gegenüber ISiK-Basis-Modul Stufe 1!
+
+
+
+
+
Could not find subject. Project was not found for Material/Images/IG_Warning.
+
Die Abbildung der Fallnummer als Identifier des Accounts ist abweichend von der im Basismodul Stufe 1 festgelegten Abbildung der Fallnummer als Identifier des Encounters. Diese Änderung ist erforderlich, da die Fallnummer nicht geeignet ist, einen Encounter eindeutig zu identifizieren. Der Encounter kann weiterhin einen von der Abrechnungsfallnummer unabhänigen Identifier enthalten (z.B. "Aufnahmenummer", Bewegungsnummer). Dieser identifiziert eineindeutig den jeweiligen Kontakt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Profil.html
new file mode 100644
index 00000000..e40bdf16
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-KontaktGesundheitseinrichtung-Kontakt_Profil.html
@@ -0,0 +1,1449 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
An interaction during which services are provided to the patient
Alternate names
Visit
Definition
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
ISiK-enc-1:Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben status = 'finished' and class = 'AMB' implies period.start.exists()
ISiK-enc-2:Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()
ISiK-enc-3:Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben status = 'planned' implies period.exists().not()
ISiK-enc-4:Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()
ISiK-enc-5:In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben status = 'in-progress' implies period.start.exists()
ISiK-enc-6:Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben status = 'onleave' implies period.start.exists()
ISiK-enc-7:Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben status = 'unknown' implies period.start.exists()
ISiK-enc-8:Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein diagnosis.use.all(coding.code != 'billing')
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Encounter[@moodCode='EVN']
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Encounter.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Encounter.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
ErsteUndZweiteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
DritteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
VierteStelle
Mappings
rim:N/A
value[x]
0..1
Binding
There are no (further) constraints on this element
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.url
Short description
identifies the meaning of the extension
Definition
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
+
Data Type
System.String
Fixed Value
+
http://fhir.de/StructureDefinition/Aufnahmegrund
Mappings
rim:N/A
value[x]
0..0
There are no (further) constraints on this element
Element Id
Encounter.extension:Aufnahmegrund.value[x]
Short description
Value of extension
Definition
Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.identifier:Aufnahmenummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Encounter.statusHistory
Short description
List of past encounter statuses
Definition
The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.
+
Comments
The current status is always found in the current version of the resource, not the status history.
There are no (further) constraints on this element
Element Id
Encounter.statusHistory.period
Short description
The time that the episode was in the specified status
Definition
The time that the episode was in the specified status.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Encounter.classHistory
Short description
List of past encounter classes
Definition
The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.
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.
There are no (further) constraints on this element
Element Id
Encounter.classHistory.period
Short description
The time that the episode was in the specified class
Definition
The time that the episode was in the specified class.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.serviceType
Short description
Specific type of service
Definition
Broad categorization of the service that is to be provided (e.g. cardiology).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Encounter.serviceType.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.priority
Short description
Indicates the urgency of the encounter
Definition
Indicates the urgency of the encounter.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.subject
Short description
The patient or group present at the encounter
Alternate names
patient
Definition
The patient or group present at the encounter.
+
Comments
While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.episodeOfCare
Short description
Episode(s) of care that this encounter should be recorded against
Definition
Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.basedOn
Short description
The ServiceRequest that initiated this encounter
Alternate names
incomingReferral
Definition
The request this encounter satisfies (e.g. incoming referral or procedure request).
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.participant.type
Short description
Role of participant in encounter
Definition
Role of participant in encounter.
+
Comments
The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.
There are no (further) constraints on this element
Element Id
Encounter.participant.period
Short description
Period of time during the encounter that the participant participated
Definition
The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.participant.individual
Short description
Persons involved in the encounter other than the patient
Definition
Persons involved in the encounter other than the patient.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.appointment
Short description
The appointment that scheduled this encounter
Definition
The appointment that scheduled this encounter.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
qty-3:If a code for the unit is present, the system SHALL also be present code.empty() or system.exists()
drt-1:There SHALL be a code if there is a value and it SHALL be an expression of time. If system is present, it SHALL be UCUM. code.exists() implies ((system = %ucum) and value.exists())
Mappings
rim:n/a
v2:SN (see also Range) or CQ
rim:PQ, IVL<PQ>, MO, CO, depending on the values
rim:PQ, IVL<PQ> depending on the values
workflow:Event.occurrence[x]
v2:(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes
There are no (further) constraints on this element
Element Id
Encounter.reasonCode
Short description
Coded reason the encounter takes place
Alternate names
Indication, Admission diagnosis
Definition
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
workflow:Event.reasonCode
w5:FiveWs.why[x]
v2:EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
There are no (further) constraints on this element
Element Id
Encounter.reasonReference
Short description
Reason the encounter takes place (reference)
Alternate names
Indication, Admission diagnosis
Definition
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.reasonCode
w5:FiveWs.why[x]
v2:EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.
+
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.reasonReference
w5:FiveWs.why[x]
v2:Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.condition.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.use
Short description
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Definition
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Encounter.diagnosis.use.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Encounter.account
Short description
The set of accounts that may be used for billing for this Encounter
Definition
The set of accounts that may be used for billing for this Encounter.
+
Comments
The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.account.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.account.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.account.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.account.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.origin
Short description
The location/organization from which the patient came before admission
Definition
The location/organization from which the patient came before admission.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
From where patient was admitted (physician referral, transfer)
Definition
From where patient was admitted (physician referral, transfer).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.reAdmission
Short description
The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Definition
Whether this hospitalization is a readmission and why if known.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.dietPreference
Short description
Diet preferences reported by the patient
Definition
Diet preferences reported by the patient.
+
Requirements
Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.
+
Comments
For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.specialCourtesy
Short description
Special courtesies (VIP, board member)
Definition
Special courtesies (VIP, board member).
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.specialArrangement
Short description
Wheelchair, translator, stretcher, etc.
Definition
Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.destination
Short description
Location/organization to which the patient is discharged
Definition
Location/organization to which the patient is discharged.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.hospitalization.dischargeDisposition
Short description
Category or kind of location after discharge
Definition
Category or kind of location after discharge.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.
+
There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.
There are no (further) constraints on this element
Element Id
Encounter.location.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Zimmer.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Bett.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.location:Station
Short description
List of locations where the patient has been
Definition
List of locations where the patient has been during this encounter.
+
Comments
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location
Short description
Location the encounter takes place
Definition
The location where the encounter takes place.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.location:Station.location.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Encounter.location:Station.status
Short description
planned | active | reserved | completed
Definition
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.
+
Comments
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.
The physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Definition
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.
+
Comments
Die Kodierung in diesem Slice entstammt folgendem Valueset - gelistet unter .location.(All slices.)physicalType: https://gematik.de/fhir/isik/v3/Basismodul/ValueSet/ISiKLocationPhysicalType
There are no (further) constraints on this element
Element Id
Encounter.location:Station.period
Short description
Time period during which the patient was present at the location
Definition
Time period during which the patient was present at the location.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider
Short description
The organization (facility) responsible for this encounter
Definition
The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Encounter.serviceProvider.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Es ist ein üblicher Fall, dass die Dauer eines Versorgungsstellenkontaktes die eines Abteilungskontaktes übersteigt. Ein Beispiel hierfür: Ein Patient bleibt im Bett (Versorgungsstellenkontakt), aber ein Fachabteilungswechsel geschieht, da die Diagnose über eine Fachabteilung (Onkologie) läuft, dann aber der Wechsel zur Fachabteilung Chirurgie (neuer Abteilungskontakt) notwendig wird.
+
Für einen solchen Fall gilt:
+
Im Falle eines Fachabteilungswechsels legt ein System einen neuen Abteilungskontakt an. Bestehende Versorgungsstellenkontakt SOLLEN nicht in ihrer Relation (.partOf) zum Abteilungskontakt modifiziert werden. Hingegen SOLL das System einen oder mehrere Versorgungsstellenkontakte erzeugen und mit dem neu angelegten Abteilungskontakt in Verbindung setzen.
+
Hinweis: Ein Versorgungsstellenkontakt endet zugleich nicht notwendigerweise mit einem Fachabteilungswechsel.
+
+
Constraints
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
ISiK-enc-1
error
Abgeschlossene, ambulante Kontakte sollten einen Start-Zeitpunkt angeben
status = 'finished' and class = 'AMB' implies period.start.exists()
+
ISiK-enc-2
error
Abgeschlossene, stationäre Kontakte sollten einen Start- und End-Zeitpunkt angeben
status = 'finished' and class = 'IMP' implies period.start.exists() and period.end.exists()
+
ISiK-enc-3
error
Geplante Kontakte sollten keinen Start- oder End-Zeitpunkt angeben
status = 'planned' implies period.exists().not()
+
ISiK-enc-4
warning
Geplante Kontakte sollten die Extensions für den geplanten Start- oder End-Zeitpunkt verwenden
status = 'planned' implies extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate').exists()
+
ISiK-enc-5
error
In-Durchführung befindliche Kontakte sollten einen Start-Zeitpunkt angeben
status = 'in-progress' implies period.start.exists()
+
ISiK-enc-6
error
Kontakte mit Abwesenheitsstatus sollten einen Start-Zeitpunkt angeben
status = 'onleave' implies period.start.exists()
+
ISiK-enc-7
warning
Kontakte mit unbekannten Status sollten einen Start-Zeitpunkt angeben
status = 'unknown' implies period.start.exists()
+
ISiK-enc-8
error
Die Rolle der assoziierten Diagnose(n) darf nicht 'Billing' sein
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Motivation.html
new file mode 100644
index 00000000..2ac3fd4a
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Motivation.html
@@ -0,0 +1,276 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Die Landschaft informationstechnischer Systeme in Krankenhäusern ist enorm heterogen. Für die Patientenverwaltung und -abrechnung, die medizinische Dokumentation, die Laborverwaltung, die Blutbank bis hin zum Dokumentenarchiv werden verschiedene, auf das jeweilige Fachgebiet spezialisierte Systeme verwendet. Es besteht daher der Bedarf, diese Systeme über ihren Primärzweck hinaus sinnvoll zu integrieren. Ein Szenario ist beispielsweise die Abrechnung der im Krankenhaus erbrachten Leistungen. Aus den ursprünglich in verschiedenen Spezialsystemen erfassten Informationen werden die für die Abrechnung relevanten Informationen an ein Abrechnungssystem gesendet und dort zur Rechnungslegung weiterverarbeitet.
+
Herausforderungen stellen dabei die Vielzahl der Schnittstellen von informationstechnischen Systemen im Krankenhaus sowie zusätzliche Anforderungen für die Nutzung in mobilen Anwendungen dar. Durch die Festlegung und Verwendung von offenen und standardisierten Schnittstellen können diese Herausforderungen effizienter angenommen werden.
+
Im Folgenden leiten wir - die gematik GmbH - her, warum die bestehenden Integrationsansätze im Krankenhaus noch unzureichend sind und durch die im Bestätigungsverfahren „Interoperabler Datenaustausch durch Informationssysteme im Krankenhaus“ (ISiK) spezifizierten Ansätze ergänzt werden, um die Vielzahl sinnvoller Integrationsszenarien effizient abzudecken.
+
Reaktiver Datenaustausch im Krankenhaus
+
Der aktuell in Krankenhäusern vorherrschende Integrationsansatz nach dem Standard HL7 Version 2 (HL7v2) sieht vor, dass fachdomänenspezifische Systeme Nachrichten versenden, sobald für andere Systeme interessante Ereignisse eintreten. Bei Anlegen einer Diagnose in einem System für medizinische Dokumentation wird beispielsweise eine entsprechende Nachricht versendet, die vom Abrechnungssystem konsumiert und in der Rechnungslegung berücksichtigt wird. Für diesen Ansatz ist es nötig, dass die konsumierenden Systeme direkt auf die für sie passenden Nachrichten reagieren können. Leider werden dieselben Inhalte in verschiedenen Krankenhäusern oft unterschiedlich in HL7v2-Nachrichten kodiert. Darum wird häufig ein Kommunikationsserver verwendet, der die krankenhausspezifischen Nachrichten in ein Format übersetzt, dass die konsumierenden Systeme verarbeiten können. Erst wenn diese Übersetzung der HL7v2 Nachrichten eingerichtet ist, können Daten zwischen den Systemen ausgetauscht werden.
+
Daraus ergeben sich einige relevante Nachteile:
+
+
Es ist nur eine im Voraus definierte Datenverarbeitung möglich. Es müssen Verarbeitungsregeln im Kommunikationsserver festgelegt werden, die empfangene HL7v2-Nachrichten zur Weiterverarbeitung in ein geeignetes Format überführen.
+
Es können keine HL7v2-Nachrichten genutzt werden, die vor Aktivierung der Verarbeitungsregeln im Krankenhaus versandt wurden. Damit bleibt ein großer Teil der verfügbaren Daten des Krankenhauses ungenutzt.
+
Gerade große Krankenhäuser müssen tausende dieser Verarbeitungsregeln verwalten. Dies erschwert den Überblick und nicht mehr benötigte Regeln belasten den Kommunikationsserver.
+
+
Daher hat der Gesetzgeber im Patientendaten-Schutzgesetz (PDSG) der gematik den Auftrag erteilt, offene und standardisierte Schnittstellen zu spezifizieren, die über den reaktiven Datenaustausch hinaus einen bedarfsgerechten Datenaustausch ermöglichen. Die Einhaltung dieser Spezifikation wird in dem ISiK Bestätigungsverfahren geprüft. Die Beschreibung des Bestätigungsverfahrens ist nicht Inhalt dieses Implementierungsleitfadens und wird im Fachportal der gematik erfolgen (https://fachportal.gematik.de/).
+
Bedarfsgerechter Datenaustausch im Krankenhaus
+
Um die oben skizzierten Nachteile zu vermeiden, wird in diesem Leitfaden ein bedarfsgerechter Datenaustausch im Krankenhaus spezifiziert. Benötigte Daten werden zum gewünschten Zeitpunkt im nötigen Umfang angefragt und zur Verfügung gestellt. So sind prinzipiell alle Daten eines Krankenhauses nutzbar, auch wenn sie lange vor dem Bedarf zur Nachnutzung erhoben wurden. Es müssen keine statischen Verarbeitungsregeln in einer Drittsoftware - dem Kommunikationsserver - verwaltet werden. Diese Art des bedarfsgerechten Datenaustausches wird in ISiK durch den internationalen HL7-Standard FHIR in seiner aktuellen Version R4 realisiert. Dabei folgt die Kommunikation dem Architekturstil Representational State Transfer - REST - auf dem auch wesentliche Teile der Kommunikation im Internet und mit mobilen Geräten im Besonderen basieren.
+
Anwendungsfälle und Interaktionen
+
Mit ISiK sollen eine Vielzahl digital unterstützter Anwendungsfälle im Krankenhaus realisiert werden. Dabei soll nicht die Vielfalt an möglichen Anwendungsfällen im Voraus komplett spezifiziert werden. Damit würde die Implementierung von ISiK durch zu enge und komplexe Vorgaben eher verhindert werden, gerade mit Blick auf zu erwartende zukünftige Anwendungsfälle.
+Das Ziel von ISiK ist es, digitale Interaktionen in den Anwendungsfällen zu identifizieren, für die eine Standardisierung besonders wertstiftend ist. Wertstiftend sind Interaktionen, die bspw. viele Anwendungsfälle unterstützen oder in einem Anwendungsfall einen besonders aufwändigen manuellen Schritt automatisieren.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..29e63cab
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,292 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu Must-Support-Feldern
+
Patient.active
+
Bedeutung: Indikator "Patientdatensatz ist in aktiver Benutzung"
Im Rahmen des ISiK Basismoduls SOLLTE die Stornierung eines Patienten entweder durch das Löschen der Patienten-Ressource oder der Verwendung des Feldes Patient.active abgebildet werden. Dies ist abhängig davon, wie die Stornierung im bestätigungsrelevanten System umgesetzt ist. Im letzteren Fall wird die Stornierung durch das Setzen von Patient.active auf false gekennzeichnet.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Beispiele.html
new file mode 100644
index 00000000..5ef0df72
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Beispiele.html
@@ -0,0 +1,416 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Interaktionen.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Interaktionen.html
new file mode 100644
index 00000000..bcdf3a5f
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Interaktionen.html
@@ -0,0 +1,346 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Interaktionen
+
Für die Ressource Patient MUSS die REST-Interaktion "READ" implementiert werden.
+
Für die Ressource Patient KANN die REST-Interaktion "POST" implementiert werden. Diese Interaktion dient für die Vorabübermittelung von (unverifizierten und/oder unvollständigen) Patientenstammdaten.
+
+
Das bestätigungsrelevante System SOLLTE die übermittelte Patient-Ressource löschen oder als inaktiv kennzeichnen, insoweit Geschäftsregeln oder andere Gründe dazu führen, dass die Patient-Ressource nicht permanent im System angelegt wird (z.B. keine Bestätigung durch die Anwender*in des Systems oder keine Aufnahme der Patient*in).
+
+
Folgende Suchparameter sind für das Bestätigungsverfahren relevant, auch in Kombination:
Dieser Suchparameter ist für die Umsetzung des IHE PDQm Profils verpflichtend.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Kompatibilitaet.html
new file mode 100644
index 00000000..25d2d057
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Kompatibilitaet.html
@@ -0,0 +1,267 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKPatient wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKPatient valide sind, auch valide sind gegen:
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden..
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Motivation.html
new file mode 100644
index 00000000..460d24d3
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Motivation.html
@@ -0,0 +1,263 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Der Austausch administrativer Patientendaten ist eine der grundlegenden Funktionalitäten beim Datenaustausch in der klinischen Versorgung.
+
In FHIR werden sämtliche klinischen Ressourcen durch Verlinkung auf die Ressource 'Patient' in einen Patientenkontext gestellt.
+
Die Herstellung des korrekten Patientenkontextes durch Suchen der Patientenressource anhand von Eigenschaften wie Aufnahmenummer, Name oder Geburtsdatum, die Anzeige der zutreffenden Suchergebnisse und der Auswahl bzw. Bestätigung des richtigen Datensatzes durch den Anwender steht am Beginn der meisten klinischen Workflows.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Profil.html
new file mode 100644
index 00000000..5eb82000
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Patient-Patient_Profil.html
@@ -0,0 +1,1521 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
isik-pat-1:Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
Mappings
rim:Entity. Role, or Act
rim:Patient[classCode=PAT]
cda:ClinicalDocument.recordTarget.patientRole
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Patient.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.identifier:VersichertenId-GKV.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.identifier:Patientennummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Patient.identifier:Versichertennummer_PKV.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Patient.active
Short description
Whether this patient's record is in active use
Definition
Whether this patient record is in active use.
+Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules.
+
It is often used to filter patient lists to exclude inactive patients
+
Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death.
+
Requirements
Need to be able to mark a patient record as not to be used because it was created in error.
+
Comments
If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.
+
Meaning When Missing
This resource is generally assumed to be active if no value is provided for the active element
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
In order to maintain the differntiations of name parts as given in the VSDM dataset or qualify prefixes as academic titles, vendors can opt to support the extensions specified in the German HumanName Base Profile https://simplifier.net/basisprofil-de-r4/humannamedebasis
+This is however not required within the scope of this specification.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Patient.name:Name.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension:nachname
Short description
Nachname ohne Vor- und Zusätze
Alternate names
extensions, user content
Definition
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
There are no (further) constraints on this element
Element Id
Patient.name:Name.family.extension:vorsatzwort
Short description
Vorsatzwort
Alternate names
extensions, user content
Definition
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Patient.name:Name.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Patient.name:Name.prefix.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
There are no (further) constraints on this element
Element Id
Patient.name:Name.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Patient.name:Geburtsname.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.telecom
Short description
A contact detail for the individual
Definition
A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).
There are no (further) constraints on this element
Element Id
Patient.telecom.rank
Short description
Specify preferred order of use (1 = highest)
Definition
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
+
Comments
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
There are no (further) constraints on this element
Element Id
Patient.telecom.period
Short description
Time period when the contact point was/is in use
Definition
Time period when the contact point was/is in use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.gender
Short description
male | female | other | unknown
Definition
Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.
+
Requirements
Needed for identification of the individual, in combination with (at least) name and birth date.
+
Comments
The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.
There are no (further) constraints on this element
Element Id
Patient.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.birthDate
Short description
The date of birth for the individual
Definition
The date of birth for the individual.
+
Requirements
Age of the individual drives many clinical processes.
+
Comments
At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).
There are no (further) constraints on this element
Element Id
Patient.birthDate.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Provides a reason why the expected value or elements in the element that is extended are missing.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
There are no (further) constraints on this element
Element Id
Patient.deceased[x]
Short description
Indicates if the individual is deceased or not
Definition
Indicates if the individual is deceased or not.
+
Requirements
The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive.
+
Comments
If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:PID-30 (bool) and PID-29 (datetime)
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedTime
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.address:Strassenanschrift.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
address-cnt-2or3-char:The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2. country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.extension:Stadtteil
Short description
Stadt- oder Ortsteil
Alternate names
extensions, user content
Definition
A subsection of a municipality.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension:Strasse
Short description
Strassenname (ohne Hausnummer)
Alternate names
extensions, user content
Definition
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.line.extension:Postfach
Short description
Postfach
Alternate names
extensions, user content
Definition
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Patient.maritalStatus
Short description
Marital (civil) status of a patient
Definition
This field contains a patient's most recent marital (civil) status.
+
Requirements
Most, if not all systems capture it.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
v2:PID-16
rim:player[classCode=PSN]/maritalStatusCode
cda:.patient.maritalStatusCode
multipleBirth[x]
0..1
There are no (further) constraints on this element
Element Id
Patient.multipleBirth[x]
Short description
Whether patient is part of a multiple birth
Definition
Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).
+
Requirements
For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs.
+
Comments
Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:PID-24 (bool), PID-25 (integer)
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber
There are no (further) constraints on this element
Element Id
Patient.contact
Short description
A contact party (e.g. guardian, partner, friend) for the patient
Definition
A contact party (e.g. guardian, partner, friend) for the patient.
+
Requirements
Need to track people you can contact about the patient.
+
Comments
Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
pat-1:SHALL at least contain a contact's details or a reference to an organization name.exists() or telecom.exists() or address.exists() or organization.exists()
Mappings
rim:n/a
rim:player[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
There are no (further) constraints on this element
Element Id
Patient.contact.relationship
Short description
The kind of relationship
Definition
The nature of the relationship between the patient and the contact person.
+
Requirements
Used to determine which contact person is the most relevant to approach, depending on circumstances.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Patient.contact.name
Short description
A name associated with the contact person
Definition
A name associated with the contact person.
+
Requirements
Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
There are no (further) constraints on this element
Element Id
Patient.contact.telecom
Short description
A contact detail for the person
Definition
A contact detail for the person, e.g. a telephone number or an email address.
+
Requirements
People have (primary) ways to contact them in some way such as phone, email.
+
Comments
Contact may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.
There are no (further) constraints on this element
Element Id
Patient.contact.address
Short description
Address for the contact person
Definition
Address for the contact person.
+
Requirements
Need to keep track where the contact person can be contacted per postal mail or visited.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Patient.contact.organization
Short description
Organization that is associated with the contact
Definition
Organization on behalf of which the contact is acting or for which the contact is working.
+
Requirements
For guardians or business related contacts, the organization is relevant.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Patient.contact.period
Short description
The period during which this contact person or organization is valid to be contacted relating to this patient
Definition
The period during which this contact person or organization is valid to be contacted relating to this patient.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Patient.communication
Short description
A language which may be used to communicate with the patient about his or her health
Definition
A language which may be used to communicate with the patient about his or her health.
+
Requirements
If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.
+
Comments
If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
There are no (further) constraints on this element
Element Id
Patient.communication.language
Short description
The language which can be used to communicate with the patient about his or her health
Definition
The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.
+
Requirements
Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
There are no (further) constraints on this element
Element Id
Patient.communication.preferred
Short description
Language preference indicator
Definition
Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).
+
Requirements
People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.
+
Comments
This language is specifically identified for communicating healthcare information.
There are no (further) constraints on this element
Element Id
Patient.generalPractitioner
Short description
Patient's nominated primary care provider
Alternate names
careProvider
Definition
Patient's nominated care provider.
+
Comments
This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.
+Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues.
+
Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Patient.managingOrganization
Short description
Organization that is the custodian of the patient record
Definition
Organization that is the custodian of the patient record.
+
Requirements
Need to know who recognizes this patient record, manages and updates it.
+
Comments
There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
rim:typeCode
cda:n/a
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
isik-pat-1
error
Falls die Geschlechtsangabe 'other' gewählt wird, muss die amtliche Differenzierung per Extension angegeben werden
gender.exists() and gender='other' implies gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').exists()
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
address-cnt-2or3-char
warning
The content of the country element (if present) SHALL be selected EITHER from ValueSet ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2 OR MAY be selected from ISO Country Alpha-3 Value Set http://hl7.org/fhir/ValueSet/iso3166-1-3, IF the country is not specified in value Set ISO Country Alpha-2 http://hl7.org/fhir/ValueSet/iso3166-1-2.
country.empty() or (country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-2') or country.memberOf('http://hl7.org/fhir/ValueSet/iso3166-1-3'))
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..164b60d6
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,274 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support-Feldern
+
Practitioner.identifier:ANR
+
Bedeutung: Lebenslange Arztnummer. Im Krankenhaus ist die lebenslange Arztnummer der Ärzte bekannt und MUSS zur eindeutigen Identifikation eines Arztes bereitgestellt werden.
Während die Deutschen Basisprofile hier die Abkürzung LANR verwenden, ist im KBV-Kontext das Akronym ANR gebräuchlich. Die Bezeichnung des Slices hat jedoch keinerlei Auswirkungen auf die Kompatibilität.
+
Practitioner.name:name
+
Bedeutung: Vollständiger Name. Der Name des Arztes MUSS in konkreten Anwendungen angezeigt werden können. Es MUSS nach dem Namen des Arztes gesucht werden können.
+
Practitioner.address:Strassenanschrift
+
Bedeutung: Straßenanschrift. Ist die Adresse bekannt, unter der ein Arzt erreichbar ist, MUSS sie bereitgestellt werden.
+
Practitioner.address:Postfach
+
Bedeutung: Postfachanschrift. Ist die Postfachadresse bekannt, unter der ein Arzt erreichbar ist, MUSS sie bereitgestellt werden.
+
Practitioner.gender
+
Bedeutung: Administratives Geschlecht. Ist das Geschlecht des Arztes bekannt, MUSS es bereitgestellt werden.
+
Practitioner.birthDate
+
Bedeutung: Geburtsdatum. Ist das Geburtsdatum des Arztes bekannt, MUSS es bereitgestellt werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Beispiele.html
new file mode 100644
index 00000000..601e614e
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Beispiele.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Kompatibilitaet.html
new file mode 100644
index 00000000..d7601624
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Kompatibilitaet.html
@@ -0,0 +1,266 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKPersonImGesundheitsberuf wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKPatient valide sind, auch valide sind gegen:
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden..
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Motivation.html
new file mode 100644
index 00000000..00cc7390
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Motivation.html
@@ -0,0 +1,262 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
PersonImGesundheitsberuf können alle denkbaren medizinischen Fachexperten sein, ohne eine Rolle zu spielen. In den ISiK-FHIR-Profilen können PersonImGesundheitsberuf bspw. als Ausführende einer Prozedur auftreten, im Element performer der Procedure Ressource, oder als die Person, die eine Diagnose stellt, im Element asserter der Condition Ressource.
+
In FHIR werden PersonImGesundheitsberuf mit der Practitioner-Ressource repräsentiert.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Profil.html
new file mode 100644
index 00000000..d58c136b
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-PersonImGesundheitsberuf-PersonImGesundheitsberuf_Profil.html
@@ -0,0 +1,1453 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
prac-de-1:Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist gender='other' or gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').empty()
Mappings
rim:Entity. Role, or Act
v2:PRD (as one example)
rim:Role
servd:Provider
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Practitioner.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:Arztnummer.assigner.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Requirements
Often, specific identities are assigned for the agent.
+
Comments
In bestimmten KIS wird keine EFN geführt, da diese aus Compliance-Gründen getrennt in HR-Systemen vorgehalten wird (Hinweis kam von Stakeholder), daher soll der entsprechende Test im Test-System mit "warningOnly" ausgegeben werden.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
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.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.identifier:EFN.assigner.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.identifier:TelematikId.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Practitioner.active
Short description
Whether this practitioner's record is in active use
Definition
Whether this practitioner's record is in active use.
+
Requirements
Need to be able to mark a practitioner record as not to be used because it was created in error.
+
Comments
If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.
+
Meaning When Missing
This resource is generally assumed to be active if no value is provided for the active element
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate.
+
In general, select the value to be used in the ResourceReference.display based on this:
+
+
There is more than 1 name
+
Use = usual
+
Period is current to the date of the usage
+
Use = official
+
Other order as decided by internal business rules.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.family.extension:nachname
Short description
Nachname ohne Vor- und Zusätze
Alternate names
extensions, user content
Definition
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.prefix.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.name:Name.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Personenname mit in Deutschland üblichen Erweiterungen
+
Requirements
The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.
+
Comments
Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
hum-1:Wenn die Extension 'namenszusatz' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://fhir.de/StructureDefinition/humanname-namenszusatz').empty() or family.hasValue()
hum-2:Wenn die Extension 'nachname' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty() or family.hasValue()
hum-3:Wenn die Extension 'vorsatzwort' verwendet wird, dann muss der vollständige Name im Attribut 'family' angegeben werden family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty() or family.hasValue()
hum-4:Wenn die Extension 'prefix-qualifier' verwendet wird, dann muss ein Namenspräfix im Attribut 'prefix' angegeben werden prefix.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier').empty() or $this.hasValue())
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.text
Short description
Text representation of the full name
Definition
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.family.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert.
+Beispiele: Gräfin, Prinz oder Fürst
+
Comments
Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt.
+Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden.
Nachname ohne Vor- und Zusätze.
+Dient z.B. der alphabetischen Einordnung des Namens.
+
Comments
If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name".
Vorsatzwort wie z.B.: von, van, zu
+Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK")
+
Comments
An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.given
Short description
Vorname
Alternate names
first name, middle name
Definition
Vorname der Person
+
Comments
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
There are no (further) constraints on this element
Element Id
Practitioner.name:Geburtsname.period
Short description
Time period when name was/is in use
Definition
Indicates the period of time when this name was valid for the named person.
+
Requirements
Allows names to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.telecom
Short description
A contact detail for the practitioner (that apply to all roles)
Definition
A contact detail for the practitioner, e.g. a telephone number or an email address.
+
Requirements
Need to know how to reach a practitioner independent to any roles the practitioner may have.
+
Comments
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.
There are no (further) constraints on this element
Element Id
Practitioner.telecom.rank
Short description
Specify preferred order of use (1 = highest)
Definition
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
+
Comments
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
There are no (further) constraints on this element
Element Id
Practitioner.telecom.period
Short description
Time period when the contact point was/is in use
Definition
Time period when the contact point was/is in use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Address(es) of the practitioner that are not role specific (typically home address)
Definition
Address(es) of the practitioner that are not role specific (typically home address).
+Work addresses are not typically entered in this property as they are usually role dependent.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
In order to differentiate between post box addresses and physical addresses, street names and house numbers, and to add city district names, vendors can opt to support the extensions as suggested in the German Address Base Profile http://fhir.de/StructureDefinition/address-de-basis.
+Such differentiations are however not required within the scope of this specification.
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.address:Strassenanschrift.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden.
+
Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird.
+
Insbesondere bei ausländischen Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend.
+
Requirements
The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.
+
Comments
Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
add-1:Wenn die Extension 'Hausnummer' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty() or $this.hasValue())
add-2:Wenn die Extension 'Strasse' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() or $this.hasValue())
add-3:Wenn die Extension 'Postfach' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue())
add-4:Eine Postfach-Adresse darf nicht vom Type "physical" oder "both" sein. line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or $this.hasValue()) or type='postal' or type.empty()
add-5:Wenn die Extension 'Adresszusatz' verwendet wird, muss auch Address.line gefüllt werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty() or $this.hasValue())
add-6:Wenn die Extension 'Postfach' verwendet wird, dürfen die Extensions 'Strasse' und 'Hausnummer' nicht verwendet werden line.all($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-postBox').empty() or ($this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty() and $this.extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty()))
add-7:Wenn die Extension 'Precinct' (Stadtteil) verwendet wird, dann muss diese Information auch als separates line-item abgebildet sein. extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').empty() or all(line contains extension('http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-precinct').value.ofType(string))
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.extension:Stadtteil
Short description
Stadt- oder Ortsteil
Alternate names
extensions, user content
Definition
A subsection of a municipality.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.type
Short description
postal | physical | both
Definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
+
Comments
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.text
Short description
Text representation of the address
Definition
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
+
Requirements
A renderable, unencoded form.
+
Comments
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.line
Short description
Straßenname mit Hausnummer oder Postfach sowie weitere Angaben zur Zustellung
Definition
Diese Komponente kann Straßennamen, Hausnummer, Appartmentnummer, Postfach, c/o sowie weitere Zustellungshinweise enthalten. Die Informationen können in mehrere line-Komponenten aufgeteilt werden.
+Bei Verwendung der Extensions, um Straße, Hausnnummer und Postleitzahl strukturiert zu übermitteln, müssen diese Informationen stets vollständig auch in der line-Komponente, die sie erweitern, enthalten sein, um es Systemen, die diese Extensions nicht verwenden zu ermöglichen, auf diese Informationen zugreifen zu können.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.line.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Strassenname (ohne Hausnummer)
+Bei Angabe einer Strasse in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Hausnummer, sowie Zusätze (Appartmentnummer, Etage...)
+Bei Angabe einer Hausnummer in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Zusätzliche Informationen, wie z.B. "3. Etage", "Appartment C"
+Bei Angabe einer Zusatzinformation in dieser Extension muss diese auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Postfach-Adresse.
+Bei Angabe eines Postfaches in dieser Extension muss das Postfach auch in Address.line angegeben werden um die Interoperabilität mit Systemen zu gewährleisten, die diese Extension nicht verwenden.
+Eine Postfach-Adresse darf nicht in Verbindung mit Address.type "physical" oder "both" verwendet werden.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.district
Short description
District name (aka county)
Alternate names
County
Definition
The name of the administrative area (county).
+
Comments
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.country
Short description
Staat
Definition
Staat (vorzugsweise als 2-Stelliger ISO-Ländercode).
+Es obliegt abgeleiteten Profilen, hier die Verwendung der ISO-Ländercodes verbindlich vorzuschreiben
+
Comments
ISO 3166 3 letter codes can be used in place of a human readable country name.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.period
Short description
Time period when address was/is in use
Definition
Time period when address was/is in use.
+
Requirements
Allows addresses to be placed in historical context.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.address:Postfach.period.end
Short description
End time with inclusive boundary, if not ongoing
Definition
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
+
Comments
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.
+
Meaning When Missing
If the end of the period is missing, it means that the period is ongoing
There are no (further) constraints on this element
Element Id
Practitioner.gender.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
+
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
gender-amtlich-1:Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist %resource.where(gender='other').exists()
There are no (further) constraints on this element
Element Id
Practitioner.birthDate.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Provides a reason why the expected value or elements in the element that is extended are missing.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Practitioner.photo
Short description
Image of the person
Definition
Image of the person.
+
Requirements
Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too.
+
Comments
When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
There are no (further) constraints on this element
Element Id
Practitioner.qualification
Short description
Certification, licenses, or training pertaining to the provision of care
Definition
The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Practitioner.qualification.period
Short description
Period during which the qualification is valid
Definition
Period during which the qualification is valid.
+
Requirements
Qualifications are often for a limited period of time, and can be revoked.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Practitioner.qualification.issuer
Short description
Organization that regulates and issues the qualification
Definition
Organization that regulates and issues the qualification.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Practitioner.communication
Short description
A language the practitioner can use in patient communication
Definition
A language the practitioner can use in patient communication.
+
Requirements
Knowing which language a practitioner speaks can help in facilitating communication with patients.
+
Comments
The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CE/CNE/CWE
rim:CD
orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
v2:PID-15, NK1-20, LAN-2
rim:./languageCommunication
servd:./Languages.LanguageSpokenCode
+
+
Constraints
+
Folgende FHIRPath-Constraints sind im Profil zu beachten:
+
key
severity
human
expression
prac-de-1
error
Die amtliche Differenzierung der Geschlechtsangabe 'other' darf nur gefüllt sein, wenn das Geschlecht 'other' angegeben ist
gender='other' or gender.extension('http://fhir.de/StructureDefinition/gender-amtlich-de').empty()
+
+
+
Terminology Bindings
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..5940ec3c
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,279 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support Feldern
+
Procedure.extension:recordedDate
+
Bedeutung:
+Das Dokumentationsdatum der Prozedur MUSS zu Qualitätssicherungszwecken angegeben werden. Dies ist das fachliche Dokumentationsdatum, nicht zu verwechseln mit der technischen Anlage des Datensatzes im Primärsystem. Diese beiden Daten können jedoch identisch sein.
+
Procedure.status
+
Bedeutung:
+Kodierter klinischer Status der Prozedur. MUSS angegeben werden, da die Interpretation der Prozedur davon abhängt, ob diese 'completed' ist oder einen anderen Status aufweist. Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "completed" und "unknown". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
Procedure.category
+
Bedeutung:
+Zur groben Kategorisierung MUSS eine Kodierung auf Basis der OPS-Klassencodes erfolgen. Eine ConceptMap für das Mapping von OPS-Kodes -> Kategorie findet sich in den Deutschen Basisprofilen - Implementierungsleitfaden Abschnitt Terminologien. Die Angabe der Kategeorie MUSS nur für OPS-kodierte Prozeduren erfolgen.
+
Procedure.code.coding
+
Bedeutung: Codierte Prozedur. Entweder kodiert per OPS oder SNOMED CT. Bei der Kodierung per SNOMED CT ist das ValueSet ProzedurenCodesSCT zu beachten.
+
Procedure.code.text
+
Bedeutung: Freitext-Beschreibung der Prozedur
+
Procedure.performed
+
Bedeutung: Zur zeitlichen Einordnung der Prozedur KANN das Durchführungsdatum der Prozedur dokumentiert werden. Mindestens MUSS der Beginn der Prozedur dokumentiert werden, das Ende KANN implementiert werden.
+
Procedure.subject
+
Bedeutung: Ein Patientenbezug der Prozedur MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.
+
Procedure.note
+
Bedeutung: Weitere optionale Freitext-Notizen bezogen auf die durchgeführte Prozedur.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Beispiele.html
new file mode 100644
index 00000000..eea209f4
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Beispiele.html
@@ -0,0 +1,310 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Dieser Suchparameter ist für die Umsetzung des IHE QEDm Profils verpflichtend.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Kompatibilitaet.html
new file mode 100644
index 00000000..6b4a3165
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Kompatibilitaet.html
@@ -0,0 +1,265 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISIKProzedur wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISIKProzedur valide sind, auch valide sind gegen:
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden..
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Motivation.html
new file mode 100644
index 00000000..1840d45a
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Motivation.html
@@ -0,0 +1,264 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
Die Möglichkeit auf eine Übersicht der Prozeduren eines Patienten zuzugreifen, Patienten anhand durchgeführter oder geplanter Prozeduren zu suchen, oder zu prüfen, ob eine konkrete Prozedur bei einem Patienten durchgeführt wurde, sind wichtige Funktionen im klinischen Behandlungsablauf.
+
In FHIR werden Prozeduren mit der Procedure-Ressource repräsentiert.
+
Da die Prozeduren in klinischen Primärsystemen, in der Regel, in OPS-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches.
+Falls eine Prozedur zwar dokumentiert aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Prozedur möglich.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Profil.html
new file mode 100644
index 00000000..ad7e28f2
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Prozedur-Prozedur_Profil.html
@@ -0,0 +1,918 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
An action that is being or was performed on a patient
Definition
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
proc-ISiK-1:Falls die Prozedur per OPS kodiert wird, MUSS eine SNOMED-CT kodierte Category abgebildet werden code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists() implies category.coding.where(system = 'http://snomed.info/sct').exists()
proc-ISiK-2:Falls eine codierte Prozedur vorliegt MUSS eine kodierte Category abgebildet werden code.coding.exists() implies category.coding.exists()
Mappings
rim:Entity. Role, or Act
workflow:Event
rim:Procedure[moodCode=EVN]
id
SΣ
0..1
System.String
There are no (further) constraints on this element
Element Id
Procedure.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
Procedure.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Dokumentationsdatum der Prozedur, falls abweichend vom Durchführungsdatum
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Procedure.identifier
Short description
External Identifiers for this procedure
Definition
Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
+
Requirements
Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers.
+
Comments
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Procedure.instantiatesUri
Short description
Instantiates external protocol or definition
Definition
The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
+
Comments
This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
There are no (further) constraints on this element
Element Id
Procedure.basedOn
Short description
A request for this procedure
Alternate names
fulfills
Definition
A reference to a resource that contains details of the request for this procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.basedOn
rim:.outboundRelationship[typeCode=FLFS].target[classCode=(various e.g. PROC, OBS, PCPR, ACT, moodCode=RQO].code
There are no (further) constraints on this element
Element Id
Procedure.partOf
Short description
Part of referenced event
Alternate names
container
Definition
A larger event of which this particular procedure is a component or step.
+
Comments
The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.partOf
rim:.inboundRelationship[typeCode=COMP].source[classCode=SBADM or PROC or OBS, moodCode=EVN]
A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
+
Comments
The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.
+
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
There are no (further) constraints on this element
Element Id
Procedure.statusReason
Short description
Reason for current status
Alternate names
Suspended Reason, Cancelled Reason
Definition
Captures the reason for the current state of the procedure.
+
Comments
This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here.
There are no (further) constraints on this element
Element Id
Procedure.category
Short description
Classification of the procedure
Definition
A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.category.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Procedure.category.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
+
Requirements
0..1 to account for primarily narrative only resources.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
sct-ops-1:Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden. Liegt die Prozedur nicht kodiert vor SOLL Freitext angegeben werden. coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()
proc-ISiK-3:Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt. coding.exists().not() implies text.exists()
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.extension
Short description
Additional content defined by implementations
Alternate names
extensions, user content
Definition
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Optional Extension Element - found in all resources.
+
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.system
Short description
Canonische CodeSystem URL für OPS
Definition
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.version
Short description
Die Jahresversion des OPS Kataloges. Angegeben wird immer die vierstellige Jahreszahl (z.B. "2017")
Definition
Bie Verwendung von OPS ist die Angabe der Version zwingend erforderlich.
+Hierdurch wird der Tatsache Rechnung getragen, dass jede der jährlich neu erscheinenden Fassung von OPS ein neues Codesystem darstellt.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.code
Short description
Der OPS-Code
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.code.coding:OPS.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
The identification of the code system that defines the meaning of the symbol in the code.
+
Requirements
Need to be unambiguous about the source of the definition of the symbol.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.version
Short description
Version of the system - if relevant
Definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.code
Short description
Symbol in syntax defined by the system
Definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
+
Requirements
Need to refer to a particular code in the system.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
Procedure.code.coding:SNOMED-CT.userSelected
Short description
If this coding was chosen directly by the user
Definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
+
Requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
+
Comments
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
There are no (further) constraints on this element
Element Id
Procedure.code.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Procedure.subject
Short description
Who the procedure was performed on
Alternate names
patient
Definition
The person, animal or group on which the procedure was performed.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.subject.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Procedure.subject.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Procedure.subject.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Procedure.subject.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Procedure.encounter
Short description
Encounter created as part of
Definition
The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
+
Comments
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performed[x]
Short description
When the procedure was performed
Definition
Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured.
+
Comments
Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone.
+
Constraints
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
There are no (further) constraints on this element
Element Id
Procedure.recorder
Short description
Who recorded the procedure
Definition
Individual who recorded the record and takes responsibility for its content.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.asserter
Short description
Person who asserts this procedure
Definition
Individual who is making the procedure statement.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performer.function
Short description
Type of performance
Definition
Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist.
+
Requirements
Allows disambiguation of the types of involvement of different performers.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.performer.actor
Short description
The reference to the practitioner
Definition
The practitioner who was involved in the procedure.
+
Requirements
A reference to Device supports use cases, such as pacemakers.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.performer.onBehalfOf
Short description
Organization the device or practitioner was acting for
Definition
The organization the device or practitioner was acting on behalf of.
+
Requirements
Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.location
Short description
Where the procedure happened
Definition
The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
+
Requirements
Ties a procedure to where the records are likely kept.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.reasonCode
Short description
Coded reason procedure performed
Definition
The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
+
Comments
Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.
There are no (further) constraints on this element
Element Id
Procedure.reasonReference
Short description
The justification that the procedure was performed
Definition
The justification of why the procedure was performed.
+
Comments
It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use).
+Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.bodySite
Short description
Target body sites
Definition
Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
+
Comments
If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension procedure-targetbodystructure.
There are no (further) constraints on this element
Element Id
Procedure.report
Short description
Any report resulting from the procedure
Definition
This could be a histology result, pathology report, surgical report, etc.
+
Comments
There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.complication
Short description
Complication following the procedure
Definition
Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.
+
Comments
If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text.
There are no (further) constraints on this element
Element Id
Procedure.complicationDetail
Short description
A condition that is a result of the procedure
Definition
Any complications that occurred during the procedure, or in the immediate post-performance period.
+
Requirements
This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Procedure.followUp
Short description
Instructions for follow up
Definition
If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.note
Short description
Additional information about the procedure
Definition
Any other notes and comments about the procedure.
+
Comments
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
There are no (further) constraints on this element
Element Id
Procedure.focalDevice
Short description
Manipulated, implanted, or removed device
Definition
A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
There are no (further) constraints on this element
Element Id
Procedure.focalDevice.action
Short description
Kind of change to device
Definition
The kind of change that happened to the device during the procedure.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Procedure.focalDevice.manipulated
Short description
Device that was changed
Definition
The device that was manipulated (changed) during the procedure.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
rim:.participation[typeCode=DEV].role[classCode=MANU] or
+.participation[typeCode=CSM].role[classCode=ADMM] (for Medication or Substance)
Falls die Prozedur kodiert vorliegt, SOLL mindestens ein OPS oder SNOMED-CT Code angegeben werden. Liegt die Prozedur nicht kodiert vor SOLL Freitext angegeben werden.
coding.exists() implies coding.where(system = 'http://snomed.info/sct').exists() or coding.where(system = 'http://fhir.de/CodeSystem/bfarm/ops').exists()
+
proc-ISiK-3
error
Entweder MUSS eine kodierte Prozedur vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ReleaseNotes.html b/IG/3.0.4/ImplementationGuide-markdown-ReleaseNotes.html
new file mode 100644
index 00000000..b1a06dfc
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ReleaseNotes.html
@@ -0,0 +1,599 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Release Notes
+
Im Rahmen der ISiK-Veröffentlichungen wird das Semantic Versioning verwendet.
+
Die erste Ziffer X bezeichnet ein Major-Release und regelt die Gültigkeit von Releases. Die dritte Ziffer Y (Release x.0.y) bezeichnet eine technische Korrektur und versioniert kleinere Änderungen (Packages) während eines Jahres, z. B. 1.0.1.
Hinzufügen optionaler Suchparameter für RelatedPerson: Add new optional SearchParameter for RelatedPerson.address - Feature/anfisk 146 search related person by @f-peverali in https://github.com/gematik/spec-ISiK-Basismodul/pull/346
KontaktGesundheitseinrichtung: SearchParameter aus FHIR-R5 für Encounter.period als Custom SearchParameter eingeführt, um die effektive Suche auf Encounter ohne abgeschlossene "period" zu ermöglichen
+
ISiKVersicherungsverhaeltnisSelbstzahler: Organisation als möglicher 'payor' hinzugefügt (es gibt auch Konstellationen, in denen die Zahlung direkt über die PKV erfolgt)
+
Hierbei ist anzumerken, dass der Zusatz "for mobile" seitens IHE irreführend sein kann.
+Konkret fasst IHE unter diesem Begriff nicht nur Systeme zusammen, die "Plattform- und Ressourcenbeschränkt sind, wie z.B. Tablets, Smartphones und Embedded Devices, sondern auch größere Systeme in Umgebungen, in denen die Interoperabilitätsanforderungen einfach sind (z.B. Anzeige der aktuellen Übersicht eines Patienten)" (Quelle: IHE QEDm - Introduction)
+
Die im Folgenden genannten IHE-Spezifikationen beschreiben lediglich Interaktionen zwischen den Systemen und machen verbindliche Vorgaben zum Ablauf, Format und zu den unterstützten Such-Parametern, jedoch keine inhaltlichen Vorgaben. So beschreibt PDQm beispielsweise den Ablauf einer Suche nach Patientendaten, enthält aber keine Vereinbarungen, wie die zurückgelieferte Patientenressource konkret auszusehen hat (Pflichtfelder, Terminologien, Constraints).
+
Der Mehrwert der ISiK-Spezifikation besteht darin, dass die genannten IHE-Interaktionen um Festlegungen zu den auszutauschenden Inhalten ergänzt werden, die zugeschnitten sind auf die Anforderungen des Datenaustausches zwischen Systemen innerhalb einer Einrichtung, basierend auf den Deutschen Basisprofilen von HL7 Deutschland e.V. und abgeglichen mit den Festlegungen der KBV zu den Inhalten der elektronischen Patientenakte (MIOs) sowie den Spezifikationen der Medizininformatik-Initiative.
+
Die Darstellungen der in diesen IHE-Profilen festgelegten Interaktionen und UseCases sind den oben verlinkten Dokumenten zu entnehmen.
+
IHE PDQm
+
Umfang
+
PDQm unterstützt das Abfragen von demografischen Patientendaten.
+Damit fällt dieser Anwendungsfall vollständig in den Umfang der Festlegungen von ISiK.
+
Akteure
+
PDQm definiert die Kommunikation zwischen zwei Akteuren:
+
+
dem Patient Demographics Consumer und
+
dem Patient Demographics Supplier
+
+
Im ISiK Kontext nehmen die bestätigungsrelevanten Systeme die Rolle des Patient Demographics Supplier ein.
+Die Pediatric Demographics Option liegt außerhalb des Abdeckungsbereiches von ISiK.
+
Transaktionen
+
PDQm definiert die Transaktion ITI-78 (Mobile Patient Demographics Query), deren Grundlagen identisch sind mit den in ISiK definierten Interaktionen auf dem Datenobjekt "Patient".
+Der Unterschied zwischen PDQm und ISiK besteht lediglich darin, dass ISiK nicht alle in PDQm spezifizierten Suchparameter zwingend erfordert.
+Suchparameter, die in PDQm obligatorisch sind, in ISiK jedoch optional, sind in diesem Leitfaden mit einem entsprechenden Hinweis versehen.
+
IHE QEDm
+
Umfang
+
QEDm unterstützt das Abfragen klinischer Informationen wie zum Beispiel Diagnosen, Beobachtungen (u.a. Vitalparameter), Messdaten und Allergien unter Verwendung des FHIR-Standards.
+Damit überlappt der Anwendungsfall von QEDm in großen Teilen mit den Festlegungen von ISiK.
+
Akteure
+
QEDm definiert die Kommunikation zwischen zwei Akteuren:
+
+
dem Clinical Data Consumer und
+
der Clinical Data Source
+
+
Im ISiK Kontext nehmen die bestätigungsrelevanten Systeme die Rolle der Clinical Data Source mit folgenden Optionen ein:
+
+
Conditions Option
+
Procedures Option
+
Encounters Option
+
+
Alle weiteren Optionen liegen außerhalb des Abdeckungsbereiches von ISiK in Hinblick auf den Scope der aktuellen Veröffentlichung.
+
Die Aufgabe der Clinical Data Source liegt in der Beantwortung der Anfragen nach Informationen durch die Rückgabe von FHIR-Ressourcen, die den gegebenen Suchparametern entsprechen.
+
Transaktionen
+
QEDm definiert die Transaktion PCC-44 (Mobile Query for Existing Data), deren Grundlagen identisch sind mit den in ISiK definierten Interaktionen auf den Datenobjekten "Diagnose" "Prozedur" und "Kontakt/Fall".
+Der Unterschied zwischen QEDm und ISiK besteht lediglich darin, dass ISiK über die Vorgaben von PDQm hinaus die Implementierung weiterer Suchparameter fordert.
+
So beschränkt sich QEDm zum Beispiel auf die Encounter-Suchparameter patient und date, während ISiK auch die Suche nach der Fallnummer (identifier) und weiteren, für die einrichtungsinterne Kommunikation relevanten Kriterien unterstützt.
+
Abweichungen
+
Hersteller, die die ISiK-Vorgaben implementiert haben, können erwarten, dass ihre Systeme damit die Anforderungen von QEDm im Rahmen der oben genannten Optionen sowie PDQm vollständig erfüllen.
+
Sollten sich Abweichungen ergeben in dem Sinne, dass Hersteller, die ISiK implementiert und erfolgreich bestätigt haben zusätzliche Funktionen implementieren müssen, um QEDm- bzw. PDQm-konform zu sein, so werden diese hier aufgelistet:
+
+
PDQm fordert die Implementierung des Suchparameters address-state. Dieser ist nicht Bestandteil der ISiK-Spezifikation
+
IHE fordert von Clinical Data Source- sowie Patient Demographic Supplier-Akteuren die Implementierung der Spezifikationen ATNA Secure Node oder ATNA Secure Application. Diese sind nicht Bestandteil des ISiK-Bestätigungsverfahrens.
+
+
+
+
+
Kompatibilität zu anderen nationalen FHIR-basierten Spezifikationen
+
Grundlage des ISiK-Leitfadens sind in Deutschland bereits abgestimmte und erprobte Profile, unter anderem:
Dennoch erstellt die gematik für die Durchführung des Verfahrens eigene, technisch unabhängige Profile. Dabei wird jedoch stets sichergestellt, dass Instanzen, die gegen gematik-Profile valide sind, ebenfalls gegen die zugrunde gelegten Profile valide sind. Ist dies ausnahmsweise nicht der Fall, dann enthalten die Profile der gematik einen entsprechenden Hinweis mit einer Begründung, warum von dem Profil abgewichen wurde bzw. eine Information darüber, welche Schritte notwendig sind, um die Kompatibilität herzustellen. Dies kann beispielsweise die zusätzliche Implementierung weiterer Elemente sein, die nicht Bestandteil des ISiK-Bestätigungsverfahrens sind, für die Erfüllung des zugrundeliegenden Profils jedoch notwendig sind. Bei der Betrachtung der Kompatibilität wird stets von Implementierungen ausgegangen, die exakt die Minimalanforderungen (Pflichtfelder, Must-Support-Felder) der gematik-Spezifikation umsetzen. Weiterhin ist die Betrachtung auf harte Inkompatibilitäten begrenzt, d.h. widersprüchliche Kardinalitäten oder abweichende Kodierungen. Auf ggf. abweichende Must-Support-Felder mit optionaler Kardinalität, die zu keiner technischen Inkompatibilität führen, wird nicht explizit hingewiesen.
+
Die Hinweise zur Kompatibilität sind jeweils im Unterkapitel "Kompatibilität" der einzelnen Datenobjekte zu finden.
+
Wichtig: Inkompatibilitäten, die sich dadurch ergeben, dass die KBV-Basisprofile und die Formularübergreifenden Vorgaben für Digitale Muster noch eine ältere Fassung der Deutschen Basisprofile (<1.0) verwenden, werden bei der Betrachtung der Kompatibilitäten nicht gesondert aufgeführt. Hierzu verweisen wir auf die Releasenotes der Deutschen Basisprofile. Ein Update dieser Profile auf die Version 1.0 ist seitens der KBV avisiert, zum Zeitpunkt der Veröffentlichung konnte jedoch noch kein konkreter Termin genannt werden.
+
Das Erfordernis der Erstellung eigener, unabhängiger Profile für ISiK ergibt sich aus folgenden Gründen:
+
+
Technische Gründe: Im Rahmen von Connectathons können kurzfristige Bugfixes erforderlich werden, die von der gematik umsetzbar sein müssen, ohne auf einen Beschluss/ein Update seitens der MI-Initiative oder der KBV warten zu müssen.
+
Tooling: Das von der gematik verwendete Tooling für die Bestätigung kann es erforderlich machen, dass Profile mit zusätzlichen Attributen/Extensions versehen werden müssen, die seitens anderer Organisationen nicht benötigt werden.
+
Darstellung: Für die Teilnehmer am Bestätigungsverfahren soll auf einen Blick erkennbar sein, welche Elemente der Profile für die Bestätigung relevant sind. Um dies zu vereinfachen, setzt die gematik sog. "Must-Support"-Flags ein, um die relevanten Merkmale hervorzuheben. Die Bedeutung des Must-Support-Flags und der Umfang der entsprechend markierten Elemente kann in anderen Szenarien abweichen. Da es sich beim Must-Support-Flags jedoch um rein informative Attribute handelt, deren Einhaltung im Rahmen der Validierung nicht maschinell überprüft werden kann, hat dies keinen Einfluss auf die Kompatibilität. Slices und Extensions, die in den zugrundeliegenden Profilen optional und nicht Bestandteil des Bestätigungsverfahrens sind, können in den gematik-Profilen weggelassen werden, um die Lesbarkeit zu verbessern. Auch diese haben keine Auswirkungen auf die Kompatibilität.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_Andere.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_Andere.html
new file mode 100644
index 00000000..dd51f158
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_Andere.html
@@ -0,0 +1,286 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität zu anderen nationalen FHIR-basierten Spezifikationen
+
Grundlage des ISiK-Leitfadens sind in Deutschland bereits abgestimmte und erprobte Profile, unter anderem:
Dennoch erstellt die gematik für die Durchführung des Verfahrens eigene, technisch unabhängige Profile. Dabei wird jedoch stets sichergestellt, dass Instanzen, die gegen gematik-Profile valide sind, ebenfalls gegen die zugrunde gelegten Profile valide sind. Ist dies ausnahmsweise nicht der Fall, dann enthalten die Profile der gematik einen entsprechenden Hinweis mit einer Begründung, warum von dem Profil abgewichen wurde bzw. eine Information darüber, welche Schritte notwendig sind, um die Kompatibilität herzustellen. Dies kann beispielsweise die zusätzliche Implementierung weiterer Elemente sein, die nicht Bestandteil des ISiK-Bestätigungsverfahrens sind, für die Erfüllung des zugrundeliegenden Profils jedoch notwendig sind. Bei der Betrachtung der Kompatibilität wird stets von Implementierungen ausgegangen, die exakt die Minimalanforderungen (Pflichtfelder, Must-Support-Felder) der gematik-Spezifikation umsetzen. Weiterhin ist die Betrachtung auf harte Inkompatibilitäten begrenzt, d.h. widersprüchliche Kardinalitäten oder abweichende Kodierungen. Auf ggf. abweichende Must-Support-Felder mit optionaler Kardinalität, die zu keiner technischen Inkompatibilität führen, wird nicht explizit hingewiesen.
+
Die Hinweise zur Kompatibilität sind jeweils im Unterkapitel "Kompatibilität" der einzelnen Datenobjekte zu finden.
+
Wichtig: Inkompatibilitäten, die sich dadurch ergeben, dass die KBV-Basisprofile und die Formularübergreifenden Vorgaben für Digitale Muster noch eine ältere Fassung der Deutschen Basisprofile (<1.0) verwenden, werden bei der Betrachtung der Kompatibilitäten nicht gesondert aufgeführt. Hierzu verweisen wir auf die Releasenotes der Deutschen Basisprofile. Ein Update dieser Profile auf die Version 1.0 ist seitens der KBV avisiert, zum Zeitpunkt der Veröffentlichung konnte jedoch noch kein konkreter Termin genannt werden.
+
Das Erfordernis der Erstellung eigener, unabhängiger Profile für ISiK ergibt sich aus folgenden Gründen:
+
+
Technische Gründe: Im Rahmen von Connectathons können kurzfristige Bugfixes erforderlich werden, die von der gematik umsetzbar sein müssen, ohne auf einen Beschluss/ein Update seitens der MI-Initiative oder der KBV warten zu müssen.
+
Tooling: Das von der gematik verwendete Tooling für die Bestätigung kann es erforderlich machen, dass Profile mit zusätzlichen Attributen/Extensions versehen werden müssen, die seitens anderer Organisationen nicht benötigt werden.
+
Darstellung: Für die Teilnehmer am Bestätigungsverfahren soll auf einen Blick erkennbar sein, welche Elemente der Profile für die Bestätigung relevant sind. Um dies zu vereinfachen, setzt die gematik sog. "Must-Support"-Flags ein, um die relevanten Merkmale hervorzuheben. Die Bedeutung des Must-Support-Flags und der Umfang der entsprechend markierten Elemente kann in anderen Szenarien abweichen. Da es sich beim Must-Support-Flags jedoch um rein informative Attribute handelt, deren Einhaltung im Rahmen der Validierung nicht maschinell überprüft werden kann, hat dies keinen Einfluss auf die Kompatibilität. Slices und Extensions, die in den zugrundeliegenden Profilen optional und nicht Bestandteil des Bestätigungsverfahrens sind, können in den gematik-Profilen weggelassen werden, um die Lesbarkeit zu verbessern. Auch diese haben keine Auswirkungen auf die Kompatibilität.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_IHE.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_IHE.html
new file mode 100644
index 00000000..d7b92c1c
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-KompatibilitaetDerGematikSpezifikation_IHE.html
@@ -0,0 +1,320 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität zu IHE-Profilen
+
Die ISiK-Spezifikationen werden basierend auf folgenden IHE-Profilen entwickelt:
Hierbei ist anzumerken, dass der Zusatz "for mobile" seitens IHE irreführend sein kann.
+Konkret fasst IHE unter diesem Begriff nicht nur Systeme zusammen, die "Plattform- und Ressourcenbeschränkt sind, wie z.B. Tablets, Smartphones und Embedded Devices, sondern auch größere Systeme in Umgebungen, in denen die Interoperabilitätsanforderungen einfach sind (z.B. Anzeige der aktuellen Übersicht eines Patienten)" (Quelle: IHE QEDm - Introduction)
+
Die im Folgenden genannten IHE-Spezifikationen beschreiben lediglich Interaktionen zwischen den Systemen und machen verbindliche Vorgaben zum Ablauf, Format und zu den unterstützten Such-Parametern, jedoch keine inhaltlichen Vorgaben. So beschreibt PDQm beispielsweise den Ablauf einer Suche nach Patientendaten, enthält aber keine Vereinbarungen, wie die zurückgelieferte Patientenressource konkret auszusehen hat (Pflichtfelder, Terminologien, Constraints).
+
Der Mehrwert der ISiK-Spezifikation besteht darin, dass die genannten IHE-Interaktionen um Festlegungen zu den auszutauschenden Inhalten ergänzt werden, die zugeschnitten sind auf die Anforderungen des Datenaustausches zwischen Systemen innerhalb einer Einrichtung, basierend auf den Deutschen Basisprofilen von HL7 Deutschland e.V. und abgeglichen mit den Festlegungen der KBV zu den Inhalten der elektronischen Patientenakte (MIOs) sowie den Spezifikationen der Medizininformatik-Initiative.
+
Die Darstellungen der in diesen IHE-Profilen festgelegten Interaktionen und UseCases sind den oben verlinkten Dokumenten zu entnehmen.
+
IHE PDQm
+
Umfang
+
PDQm unterstützt das Abfragen von demografischen Patientendaten.
+Damit fällt dieser Anwendungsfall vollständig in den Umfang der Festlegungen von ISiK.
+
Akteure
+
PDQm definiert die Kommunikation zwischen zwei Akteuren:
+
+
dem Patient Demographics Consumer und
+
dem Patient Demographics Supplier
+
+
Im ISiK Kontext nehmen die bestätigungsrelevanten Systeme die Rolle des Patient Demographics Supplier ein.
+Die Pediatric Demographics Option liegt außerhalb des Abdeckungsbereiches von ISiK.
+
Transaktionen
+
PDQm definiert die Transaktion ITI-78 (Mobile Patient Demographics Query), deren Grundlagen identisch sind mit den in ISiK definierten Interaktionen auf dem Datenobjekt "Patient".
+Der Unterschied zwischen PDQm und ISiK besteht lediglich darin, dass ISiK nicht alle in PDQm spezifizierten Suchparameter zwingend erfordert.
+Suchparameter, die in PDQm obligatorisch sind, in ISiK jedoch optional, sind in diesem Leitfaden mit einem entsprechenden Hinweis versehen.
+
IHE QEDm
+
Umfang
+
QEDm unterstützt das Abfragen klinischer Informationen wie zum Beispiel Diagnosen, Beobachtungen (u.a. Vitalparameter), Messdaten und Allergien unter Verwendung des FHIR-Standards.
+Damit überlappt der Anwendungsfall von QEDm in großen Teilen mit den Festlegungen von ISiK.
+
Akteure
+
QEDm definiert die Kommunikation zwischen zwei Akteuren:
+
+
dem Clinical Data Consumer und
+
der Clinical Data Source
+
+
Im ISiK Kontext nehmen die bestätigungsrelevanten Systeme die Rolle der Clinical Data Source mit folgenden Optionen ein:
+
+
Conditions Option
+
Procedures Option
+
Encounters Option
+
+
Alle weiteren Optionen liegen außerhalb des Abdeckungsbereiches von ISiK in Hinblick auf den Scope der aktuellen Veröffentlichung.
+
Die Aufgabe der Clinical Data Source liegt in der Beantwortung der Anfragen nach Informationen durch die Rückgabe von FHIR-Ressourcen, die den gegebenen Suchparametern entsprechen.
+
Transaktionen
+
QEDm definiert die Transaktion PCC-44 (Mobile Query for Existing Data), deren Grundlagen identisch sind mit den in ISiK definierten Interaktionen auf den Datenobjekten "Diagnose" "Prozedur" und "Kontakt/Fall".
+Der Unterschied zwischen QEDm und ISiK besteht lediglich darin, dass ISiK über die Vorgaben von PDQm hinaus die Implementierung weiterer Suchparameter fordert.
+
So beschränkt sich QEDm zum Beispiel auf die Encounter-Suchparameter patient und date, während ISiK auch die Suche nach der Fallnummer (identifier) und weiteren, für die einrichtungsinterne Kommunikation relevanten Kriterien unterstützt.
+
Abweichungen
+
Hersteller, die die ISiK-Vorgaben implementiert haben, können erwarten, dass ihre Systeme damit die Anforderungen von QEDm im Rahmen der oben genannten Optionen sowie PDQm vollständig erfüllen.
+
Sollten sich Abweichungen ergeben in dem Sinne, dass Hersteller, die ISiK implementiert und erfolgreich bestätigt haben zusätzliche Funktionen implementieren müssen, um QEDm- bzw. PDQm-konform zu sein, so werden diese hier aufgelistet:
+
+
PDQm fordert die Implementierung des Suchparameters address-state. Dieser ist nicht Bestandteil der ISiK-Spezifikation
+
IHE fordert von Clinical Data Source- sowie Patient Demographic Supplier-Akteuren die Implementierung der Spezifikationen ATNA Secure Node oder ATNA Secure Application. Diese sind nicht Bestandteil des ISiK-Bestätigungsverfahrens.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html
new file mode 100644
index 00000000..3ce6dcf6
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Übergreifende Festlegungen
+
In diesem Kapitel werden die folgenden übergreifenden Festlegungen definiert, die generell für die weitere Spezifikation gelten:
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_BestaetigungsrelevanteSysteme.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_BestaetigungsrelevanteSysteme.html
new file mode 100644
index 00000000..956a806a
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_BestaetigungsrelevanteSysteme.html
@@ -0,0 +1,310 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Bestätigungsrelevante Systeme
+
Hier folgt die Festlegung der Deutschen Krankenhausgesellschaft e. V. wie hier aufgeführt
+
Festlegung der Deutschen Krankenhausgesellschaft e. V. aus dem Jahr 2022
+
Die im Folgenden definierten Subsysteme müssen gemäß § 373 Abs. 2 SGB V nach
+zweijähriger Übergangsfrist im Krankenhaus um die Schnittstelle erweitert sein, die
+das ISIK-Modul bzw. die Datenobjekte der gematik jeweils beschreiben. Die Festlegung der Systeme zu den einzelnen ISiK-Modulen ist um Erläuterungen in eckigen
+Klammern ergänzt.
+
ISiK-Basismodul (Stufe 1 und Stufe 2)
+
+
Krankenhaus-Informationssystem (KIS)
+
+
ISiK-Modul Vitalwerte und Körpermaße
+
+
KIS mit Funktion elektronische Kurve bzw. entsprechendes KIS-Modul
+
Patientendaten-Managementsystem (PDMS) [z.B. für Intensivbereiche]
+
Elektronische Kurve [z.B. für die Verwendung auf Normal-Stationen]
+
+
ISiK-Modul Dokumentenaustausch
+
+
KIS
+
Dokumentenmanagementsystem (DMS)
+
Archivsystem
+
Telekonsil-Modul gemäß § 31a BMV-Ä [Ziel ist die clientseitige Implementierung für die Suche nach Dokumenten anhand von Metadaten,
+Verarbeitung von Suchergebnissen und Dokumentenzugriff zur Verwendung in Telekonsilien], hierbei keine Umsetzung einer Funktion zum Abruf von Dokumenten aus dem Telekonsil-Modul
+
KIM-Client-Anwendungssoftware [die Anwendungsintegration, nicht der
+KIM-Client, Implementierung für die Ablage von Dokumenten aus KIM-Nachrichten und den Versand von Dokumenten mit KIM-Nachrichten],
+hierbei keine Umsetzung einer Funktion zum Abruf von Dokumenten aus
+der KIM-Client-Anwendungssoftware
+
+
ISiK-Modul Medication
+
+
KIS
+
PDMS [Anwendungsfallbeispiel: Medikationsdaten in das KIS übertragen bei Verlegung vom Intensivbereich auf Normal-Station]
+
Software für digitales Medikationsmanagement [z.B. für die Umsetzung
+von KHZG Fördertatbestand 5]
+
E-Therapieplan-System für Zytostatika-Behandlung mit Verarbeitung
+von Verordnungs- und Medikationsinformationen [teilweise Grundlage
+für onkologische Verordnungsdaten], gemäß diesen Festlegungen keine
+Umsetzung des ISIK-Datenobjekts MedikationsVerabreichung notwendig
+
Herstellungssystem mit Verarbeitung von Verordnungs- und Medikationsinformationen [in KH-Apotheke, z.B. für Zytostatika], gemäß diesen
+Festlegungen keine Umsetzung des ISIK-Datenobjekts MedikationsVerabreichung notwendig
+
E-Rezept-Modul für Herstellungen [eRezept an Fachdienst in TI übertragen]
+
Taxierungssoftware [in KH-Apotheke]
+
+
ISiK-Modul Terminplanung [z.B. für die Umsetzung von KHZG Fördertatbestand 2]
+
+
KIS
+
Patientenportal-Terminmodul
+
+
Hinweise und Rückfragen zu den bestätigungsrelevante Systemen können an die DKG-Geschäftsstelle gerichtet werden.
+
Festlegungen auf Profilebene im CapabilityStatement
+
Festlegungen zu Anforderungen auf Profilebene werden unter CapabilityStatement geführt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Methodik.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Methodik.html
new file mode 100644
index 00000000..6c81434b
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Methodik.html
@@ -0,0 +1,260 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Methodik
+
Anforderungen als Ausdruck normativer Festlegungen werden durch die dem RFC2119 entsprechenden, in Großbuchstaben geschriebenen deutschen Schlüsselworte MUSS, DARF NICHT, SOLL, SOLL NICHT, KANN sowie ihrer Pluralformen gekennzeichnet.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Must-Support-Flags.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Must-Support-Flags.html
new file mode 100644
index 00000000..f1aaaab2
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Must-Support-Flags.html
@@ -0,0 +1,269 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Must-Support-Flags
+
Die Verwendung des Must-Support-Flags an Profil-Elementen hat im Kontext dieses Leitfadens folgende Bedeutung:
+
+
Im Kontext der Erstellung von FHIR-Ressourcen:
+
Wenn die entsprechende Information in einem der Testszenarien bekannt ist, dann MUSS das Feld in der erstellten Ressource gefüllt sein. Ist die Information nicht bekannt, KANN es leer bleiben.
+
+
Im Kontext der Verarbeitung von FHIR-Ressourcen:
+
Wenn die entsprechende Information in einer Ressource vorhanden ist, so MUSS diese vom verarbeitenden System ausgewertet, persistiert und dem Anwender dargestellt werden können.
+
Sollte ein Hersteller den Bedarf an einer Änderung der Must-Support Vorgaben der ISiK Profile haben, MUSS er von den Profilen ableiten, auf denen die ISiK Profile basieren. Angaben dazu finden sich für jedes Datenobjekt im Kapitel Kompatibilität. In diesem Fall MUSS der Hersteller auch dafür sorgen, dass seine abgeleiteten Profile weiterhin kompatibel mit den ISiK Profilen bleiben.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Repraesentationsformate.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Repraesentationsformate.html
new file mode 100644
index 00000000..b0008c8d
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Repraesentationsformate.html
@@ -0,0 +1,266 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Repräsentationsformate
+
Der FHIR-Standard beschreibt drei verschiedene Repräsentationsformate: XML, JSON und RDF (Turtle).
+Im Rahmen der ISiK-Spezifikation MÜSSEN bestätigungsrelevante Systeme (Server) die Formate XML und JSON unterstützen.
+
Client-seitige Implementierungen haben die Wahl zwischen XML- und JSON-Repräsentation, müssen jedoch in den HTTP Accept- und Content-Type-Headern entsprechend ausweisen, welche Repräsentation gewählt wurde.
+
Wenn ein Client im Accept-Header ein vom Server nicht unterstütztes Format anfordert, so MUSS der Server mit dem Fehlercode 406 not acceptable antworten.
+Wenn ein Client im Content-Type-Header ein vom Server nicht unterstütztes Format sendet, so MUSS der Server mit dem Fehlercode 415 unsupported media type antworten.
+
Es ist zu beachten, dass die Header Content-Type und Accept noch weitere FHIR-spezifische und allgemeine Parameter enthalten können. Siehe beispielsweise https://www.hl7.org/fhir/R4/http.html#version-parameter. Das Vorhandensein dieser Parameter darf nicht zu einem Fehler führen.
+
Anfragen, in denen eine andere FHIR-Version als die hier vereinbarte Version 4.0 angefordert wird, müssen mit Fehlercode 406 - not acceptable beantwortet werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Rest.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Rest.html
new file mode 100644
index 00000000..6baca1ae
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Rest.html
@@ -0,0 +1,293 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
REST-API
+
Read-Interaktionen
+
Instanzen von Datenobjekten, die die REST-Interaktion "READ" fordern MÜSSEN per HTTP GET auf [BASE_URL]/[resourceType]/[ID] abgerufen werden können.
+Siehe: https://www.hl7.org/fhir/R4/http.html#read
+
Search-Interaktionen
+
Die Suche MUSS sowohl mittels HTTP GET als auch HTTP POST (vgl. FHIR RESTful Search - Introduction) unterstützt werden. Die URL-Parameter komplexer Suchanfragen können personenbezogene Merkmale enthalten, daher ist im Echtbetrieb die Suche mittels HTTP POST in Verbindung mit TLS-Verschlüsselung vorzuziehen.
+
Create-Interaktionen
+
Das Erstellen einer Ressource kann per HTTP POST (vgl. FHIR RESTful API - create) unterstützt werden. Einzelne Datenobjekte (spezifiziert im vorliegenden Basismodul oder in einem ISiK Erweiterungsmodul) können diese Interaktion als verpflichtend kennzeichnen.
+
Es liegt im Ermessen des bestätigungsrelevanten Systems, ob eine externe Ressource durch das System direkt übernommen wird. Auch wie die Herkunft der übernommenen Ressource gekennzeichnet wird, liegt im Ermessen des bestätigungsrelevanten Systems.
+
Eine Ressource welche nicht durch das bestätigungsrelevante System angelegt wird, KANN in Resource.meta.tag eine Angabe enthalten, welche indiziert, dass diese Ressource durch ein Fremdsystem erzeugt wurde. Dieser Tag KANN durch den Server hinzugefügt werden, sollte der Client diese Angabe nicht mit übermitteln. Eine von einem System vorgenommene Auszeichnung von Fremdübernahmen SOLL über den Code external aus dem Kodiersystem https://fhir.de/CodeSystem/common-meta-tag-de erfolgen. Weitere Kodierungen KÖNNEN hinzugefügt werden.
Eine weitere Differenzierung der Herkunft kann mittels Resource.meta.security kodiert werden. Hierzu KÖNNEN Codes aus dem ValueSet SecurityIntegrityObservationValue verwendet werden.
+
Sollte die erzeugte Ressource dauerhaft in das bestätigungsrelevante System übernommen werden, KANN der entsprechende Tag in Patient.meta.tag entfernt werden. In diesem Falle MUSS die id der Ressource stabil bleiben und darf nicht verändert werden.
+
Per Create-Interaktion erzeugte Ressourcen MÜSSEN im Falle einer erfolgreichen Übermittlung direkt über die READ- und SEARCH-Interaktionen zur Verfügung gestellt werden.
+
Ressourcen, die zu einem entsprechenden ISiK-Profil nicht konform sind, MÜSSEN durch das bestätigungsrelevante System abgelehnt werden. Als Antwort MUSS ein HTTP Status-Code 400 - Bad Request mit einer OperationOutcome-Ressource zurückgegeben werden, falls es sich um einen syntaktischen Fehler in der Repräsentation der Ressource handelt. Die OperationOutcome MUSS eine Auflistung aller Fehler in der übermittelten Ressource in kodierter Form vorweisen. Anderweitig (semantisch) invalide Ressourcen MÜSSEN ebenfalls mit einer entsprechenden OperationOutcome-Ressource abgewiesen werden. In diesem Fall SOLLTE der HTTP Status-Code HTTP 422 - Unprocessable Entity verwendet werden.
+
Update-Interaktionen
+
Das Update einer Ressource KANN per HTTP PUT (vgl. FHIR RESTful API - update) unterstützt werden. Es ist zu beachten, dass beim Update einer Ressource bestimmte dazugehörige Metadaten beibehalten werden SOLLTEN. Die gleichen Vorgaben für die Handhabung von invaliden Ressourcen wie beschrieben im Abschnitt "Create-Interaktionen", gelten auch für Update-Interaktionen.
+
Sicherheitsaspekte
+
Alle REST-Interaktionen müssen sowohl mittels HTTP als auch HTTPS (TLS-Verschlüsselung) unterstützt werden. Vorgaben zur TLS-Verschlüsselung sind dem nachfolgenden Link für die FHIR Security Check List zu entnehmen.
+Im Echtbetrieb MUSS die Kommunikation ausschließlich per HTTPS erfolgen.
+Weiterhin sind geeignete Maßnahmen zur Risiko-Minimierung (z.B. Benutzerautorisierung / -authentifikation) zu treffen, siehe http://build.fhir.org/security.html#6.1.0.
+Diese sind in Stufe 1 des ISiK Basismoduls jedoch nicht bestätigungsrelevant.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Suchparameter.html b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Suchparameter.html
new file mode 100644
index 00000000..aec6f3aa
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-UebergreifendeFestlegungen-UebergreifendeFestlegungen_Suchparameter.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Allgemeine Hinweise zu Suchparametern
+
Innerhalb der jeweiligen Abschnitte 'Interaktionen' (Siehe Datenobjekte) werden für alle innerhalb dieses Implementierungsleitfadens spezifizierten FHIR-Ressourcen Suchparameter bestimmt, welche im Rahmen des Bestätigungsverfahrens von ISiK unterstützt werden MÜSSEN.
+
Es MUSS sichergestellt werden, dass nicht unterstützte oder leere Suchparameter nicht zu einem Fehler führen. Siehe FHIR RESTful Search - Handling Errors. Alle unterstützten und verwendeten Suchparameter sind im Self-Link des Suchbundles korrekt anzugeben.
+
Alle Suchparameter in FHIR entsprechen einem von neun definierten Such-Parameter-Typen:
+
+
Number
+
Date/DateTime
+
String
+
Token
+
Reference
+
Composite
+
Quantity
+
URI
+
Special
+
+
Des Weiteren werden zusätzlich sogenannte 'Modifier' pro Suchparameter-Typ definiert. Eine Übersicht findet sich unter "Search Modifiers".
+
Für die im Rahmen dieses Leitfadens relevanten Typen gelten folgende allgemeinen Festlegungen:
+
Date/DateTime
+
Die Präfixe lt,le,gt,ge,eq MÜSSEN für jeden Suchparameter vom Typ 'date/dateTime' unterstützt werden.
+
Beispiele:
+
[base]/Patient?birthDate=ge2000-01-01
+Suche nach allen Patienten mit einem Geburtsdatum 2000-01-01T00:00 oder später.
+
[base]/Patient?birthDate=eq2000-01-01
+Suche nach allen Patienten mit einem Geburtsdatum von 2000-01-01T00:00 bis (aber nicht einschließlich) 2000-02-01T00:00
Der Modifier :contains MUSS für alle spezifizierten Suchparameter vom Typ 'String' unterstützt werden.
+
Beispiele:
+
[base]/Patient?address:contains=Berlin
+Diese Suchanfrage gibt alle Patienten zurück zum Client, welche in einem Adress-Bestandteil den String 'Berlin' enthält (z.B. alle Berliner Adressen unabhängig von konkreten Bezirken).
+
Token
+
Der Modifier :not MUSS für alle spezifizierten Suchparameter vom Typ 'Token' unterstützt werden, sofern diese auf die Datentypen "code", "Coding" oder "CodeableConcept" verwendet werden.
+
Der Modifier :text MUSS für alle spezifizierten Suchparameter vom Typ 'Token' unterstützt werden, sofern diese auf die Datentypen "Coding" oder "CodeableConcept" verwendet werden.
+
Beispiele:
+
[base]/Condition?code:text=Freitext
+Diese Suche gibt alle Condition-Ressourcen zurück zum Client, welche innerhalb Condition.code.text das Wort "Freitext" enthält. Es ist zu beachten, dass hier ein partielles Matching erfolgen MUSS (es ist implizit der Modifier :contains anzunehmen).
+
[base]/Condition?code:not=Test
+Diese Suche gibt alle Condition-Ressourcen zurück zum Client, welche innerhalb Condition.code.coding NICHT den Code 'Test' enthält. Es ist zu beachten, dass dies auch alle Ressourcen beinhaltet, die keinen kodierten Wert für Condition.code enthalten.
+
Reference
+
Der Modifier :identifier MUSS für alle spezifizierten Suchparameter vom Typ 'Reference' unterstützt werden.
+
Der [type] Modifier MUSS für alle spezifizierten Suchparameter vom Typ 'Reference' unterstützt werden.
+
Beispiele:
+
[base]/Procedure?subject:Patient=Test
+Diese Suche gibt alle Prozeduren zurück zum Client, welche innerhalb Procedure.subject auf einen Patienten verweist mit dem der ID "Test". Hierdurch werden Referenzen auf den Ressourcentyp "Group" in der Suche ausgeschlossen.
+
Beispiele:
+
[base]/Coverage?Payor:identifier=http://fhir.de/sid/arge-ik/iknr|123456
+Diese Suche gibt alle Coverage-Ressourcen zurück zum Client, welche innerhalb Coverage.payor eine logische Referenz auf den Versicherer mit der IK-Nummer "123456" enthält.
+
Für Suchparameter vom Typ 'Reference' MÜSSEN die Festlegungen für Chaining und Reverse Chaining verpflichtend implementiert werden. Chaining und Reverse Chaining MUSS für alle Suchparameter über alle Ebenen und Datenobjekte hinweg (potentiell in Kombination) unterstützt werden.
+
Beispiele:
+
[base]/Procedure?subject.name=Test
+Diese Suche gibt alle Prozeduren zurück zum Client, welche innerhalb Procedure.subject auf einen Patienten verweist mit dem Namen "Test".
+
[base]/Condition?encounter.subject.name=Test
+Diese Suche gibt alle Diagnosen zurück zum Client, welche eine Encounter Reference besitzen und innerhalb Encounter.subject auf einen Patienten verweist mit dem Namen "Test".
+
[base]/Patient?_has:Procedure:patient:code=1234-5
+Diese Suche gibt alle Patienten zurück zum Client, welche innerhalb Procedure.subject auf einen Patienten verweisen und einen Code mit dem Wert '1234-5' in Procedure.code enthalten.
+
[base]/Patient?_has:Procedure:patient:encounter.identifier=12345
+Diese Suche gibt alle Patienten zurück zum Client, welche innerhalb Procedure.subject auf einen Patienten verweisen und einen deren Procedure auf einen Encounter verweist z.B. mit der Aufnahmenummer '1234-5'.
+
[base]/Procedure?_has:Encounter:diagnosis:diagnosis:Condition.code=http://fhir.de/CodeSystem/bfarm/icd-10-gm|F16.1
+Diese Suche gibt alle Prozeduren zurück zum Client, welche innerhalb Encounter.diagnosis.condition auf einen Encounter verweisen, der wiederrum mit einer Condition verlinkt ist mit dem ICD-10-GM Code 'F16.1'.
+
Verpflichtende Suchparameter (Alle Datenobjekte)
+
Folgende Suchparameter MÜSSEN für alle bestätigungsrelevante Datenojekte implementiert werden:
Hierraus ergibt sich, dass durch ein Paging ensprechende der FHIR-Kernspezifikation unterstützt werden MUSS.
+Für die URIs in den Link-Relationen "first", "last", "next", sowie "prev" MUSS sichergestellt werden, dass NICHT die ursprünglich verwendeten Suchparameter, sowie anderweitig sensitive Informationen enthalten, welche in der Suchanfrage an das bestätigungsrelevante System versendet wurden.
+Der "self"-Link innerhalb des Such-Bundles MUSS entsprechend der Vorgaben aus FHIR Kernspezifikation - 3.1.1.6 - Server Conformance strukturiert sein.
+
+
_include
+
+
Beispiele: GET [base]/Encounter?_include=Patient:subject
Alle Referenzen für die ein Chaining unterstützt wird MUSS auch der _include-Parameter implementiert werden. Alle unterstützten Include-Referenzen MÜSSEN im CapabilityStatement unter CapabilityStatement.rest.resource.searchInclude angegeben werden. Siehe CapabilityStatement.
+
+
Der :iterate Modifier KANN unterstützt werden.
+
+
_revinclude
+
+
Beispiele: GET [base]/Patient?_revinclude=Encounter:subject
Alle Referenzen für die ein Chaining unterstützt wird MUSS auch der _include-Parameter implementiert werden. Alle unterstützten Include-Referenzen MÜSSEN im CapabilityStatement unter CapabilityStatement.rest.resource.searchRevInclude angegeben werden. Siehe CapabilityStatement.
+
+
Der :iterate Modifier KANN unterstützt werden.
+
+
+
Die aufgelisteten Suchparameter MÜSSEN entsprechend der Vorgaben für das CapabilityStatement pro Ressource aufgelistet werden.
+
Best Practice Empfehlungen für Standard-Suchfilter
+
Diese grundlegenden Best Practice Empfehlungen beziehen sich auf die korrekte Verwaltung des Suchprozesses seitens des Servers, mit Bezug auf Sicherheit im klinischen Umfeld. Unstimmigkeiten in den Erwartungen zwischen Client und Server können dazu führen, dass mehr Ressourcen als erwartet oder angemessen gefunden werden, oder, dass Ressourcen in den Suchergebnissen fehlen, die eigentlich vorhanden sein sollten. Im Folgenden werden daher Empfehlungen für Standard-Suchfilter genannt, die ein Grundmaß an Sicherheit im klinischen Umfeld bereitstellen sollen.
+
+
Der Server SOLLTE dafür sorgen, dass Clients die benötigten Informationen finden können, auch bei Inhalten, die sich über mehrere FHIR-Ressourcen hinweg strecken.
+
+
Wenn der Inhalt eines Suchparameters leer ist, SOLLTE der Server diesen ignorieren.
+
+
Wenn der Inhalt eines Suchparameters syntaktisch falsch ist, SOLLTE der Server einen Fehler zurückgeben. Handelt es sich jedoch um eine logische Bedingung (z. B. einen Code), SOLLTE der Server die Suche verarbeiten, einschließlich des Parameters. Als Ergebnis wird in diesem Fall eine leere Suchmenge zurückgegeben, da der Parameter nicht erfüllt werden kann. In solchen Fällen kann zusätzlich ein OperationOutcome mit Hinweisen und Warnungen über den Suchprozess in das Ergebnis aufgenommen werden. Dieses wird in die Suchergebnisse als Eintrag mit search mode = outcome aufgenommen. Clients können diese Informationen nutzen, um zukünftige Suchen zu verbessern.
+
+
Wenn der Server geeignete Standardfilter bei der Suche auf der Grundlage des Patientenkontextes (z. B. das Herausfiltern von fehlerhaften Datensätzen oder inaktiven und verstorbenen Patienten) enthält, SOLLTEN diese angemessen und eindeutig dokumentiert sein (vorzugsweise durch Aufnahme in den 'self link' für eine Suche).
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..a402b1b8
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,278 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu Must-Support-Feldern
+
ValueSet.url
+
Bedeutung: Eindeutige Url zur Identifizierung des ValueSets. Absolute Urls sind zu bevorzugen.
+
Hinweise: OIDs SOLLTEN als weitere Identifier des CodeSystems verwendet werden. In jedem Fall SOLLTE eine Canonical Url vergeben werden.
+
ValueSet.version
+
Bedeutung: Version des ValueSets
+
Hinweise: Jede Änderung des dazugehörigen CodeSystems MUSS eine Änderung in der Version des CodeSystems und ValueSets nach sich ziehen.
+
ValueSet.name
+
Bedeutung: Maschinenlesbarer Name des ValueSets
+
Hinweise: Der Constraint vsd-0 ist hierbei zu beachten.
+
ValueSet.status
+
Bedeutung: Indikation, ob das ValueSet in aktiver Verwendung ist.
+
Hinweise: Alle in einem System möglichen Status-Werte müssen über FHIR korrekt repräsentiert werden können, mindestens jedoch die Status-Werte "active" und "retired". Deren korrekte Abbildung wird im Rahmen des Bestätigungsverfahrens überprüft.
+
ValueSet.useContext
+
Bedeutung: Angabe für welches Datenelement das ValueSet relevant ist
+
Hinweise: Es muss mindestens ein useContext angegeben werden, in dem der Ressourcen-Typ kodiert wird, in dem das ValueSet in einem Element zur Verwendung kommt.
+
ValueSet.expansion
+
Bedeutung: Angabe der Konzepte aus denen sich das ValueSet zusammensetzt.
+
Hinweise: Mindestens MUSS ein Code und ein Anzeigetext spezifiziert werden.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Beispiele.html b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Beispiele.html
new file mode 100644
index 00000000..fe970bde
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Beispiele.html
@@ -0,0 +1,300 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Der Suchparameter "context-type-value" MUSS unterstützt werden:
+
Beispiele:
+
GET [base]/ValueSet?context-type-value=http://terminology.hl7.org/CodeSystem/usage-context-type|focus$http://hl7.org/fhir/resource-types|Encounter
+
Mit dieser Abfrage können hausinterne Kataloge anhand des Ressource-Typs ermittelt werden. Diese Informationen sind u.a. relevant im Kontext von:
+
+
Hausinternen Prozeduren/Diagnosen-Codes
+
Kodierung von Encounter-Informationen (z.B. Wahlleistungen, Orttypen)
+
+
Use Cases im Zusammenhang:
+
(A) Zur Konfigurationszeit können passende ValueSets von einem Server spezifisch für einen Ressourcentyp abgerufen und vorbereitend auf eine Systemintegration begutachtet bzw. in Client-Systeme eingebunden werden. In diesem Sinne wird die Abfrage im Kontext der Terminvereinbarung durch einen Termin-Requestor genutzt.
+
(B) Zur Laufzeit können spezifische ValueSets synchronisiert bzw. direkt in die Eingabemasken von Clients eingebunden werden.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Kompatibilitaet.html
new file mode 100644
index 00000000..95d430ac
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Kompatibilitaet.html
@@ -0,0 +1,260 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Für das Profil ISiKValueSet wurde bis zum Zeitpunkt der Veröffentlichung kein Abgleich der Kompatibilität zu anderen Profilen (der KBV und der Medizininformatik-Initiative) durchgeführt.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Motivation.html
new file mode 100644
index 00000000..438fdcb1
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Motivation.html
@@ -0,0 +1,262 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
ISiK erlaubt in diversen Kontexten die Erweiterung der Kodierung durch Krankenhaus- / Systeminterne Kodierungen.
+Mittels der Publizierung von ValueSets können Auswahllisten für externe Clients bereitgestellt werden, sodass diese Kodierungen ebenfalls anbieten können.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Profil.html
new file mode 100644
index 00000000..0a638f41
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-ValueSet-ValueSet_Profil.html
@@ -0,0 +1,645 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
There are no (further) constraints on this element
Element Id
ValueSet
Short description
A set of codes drawn from one or more code systems
Definition
A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
vsd-0:Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
Mappings
rim:Entity. Role, or Act
rim:N/A
id
SΣ
1..1
System.String
There are no (further) constraints on this element
Element Id
ValueSet.id
Short description
Logical id of this artifact
Definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
+
Comments
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
There are no (further) constraints on this element
Element Id
ValueSet.url
Short description
Canonical identifier for this value set, represented as a URI (globally unique)
Definition
An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this value set is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the value set is stored on different servers.
+
Requirements
Allows the value set to be referenced by a single globally unique identifier.
+
Comments
Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
+
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.
+
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
There are no (further) constraints on this element
Element Id
ValueSet.identifier
Short description
Additional identifier for the value set (business identifier)
Definition
A formal identifier that is used to identify this value set when it is represented in other formats, or referenced in a specification, model, design or an instance.
+
Requirements
Allows externally provided and/or usable business identifiers to be easily associated with the module.
+
Comments
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this value set outside of FHIR, where it is not possible to use the logical URI.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
ValueSet.version
Short description
Business version of the value set
Definition
The identifier that is used to identify this version of the value set when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.
+
Comments
There may be different value set instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the value set with the format [url]|[version].
There are no (further) constraints on this element
Element Id
ValueSet.name
Short description
Name for this value set (computer friendly)
Definition
A natural language name identifying the value set. This name should be usable as an identifier for the module by machine processing applications such as code generation.
+
Requirements
Support human navigation and code generation.
+
Comments
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.
There are no (further) constraints on this element
Element Id
ValueSet.status
Short description
draft | active | retired | unknown
Definition
The status of this value set. Enables tracking the life-cycle of the content. The status of the value set applies to the value set definition (ValueSet.compose) and the associated ValueSet metadata. Expansions do not have a state.
+
Comments
Allows filtering of value sets that are appropriate for use versus not.See also the valueset-workflowStatus extension for additional status information related to the editorial process.
There are no (further) constraints on this element
Element Id
ValueSet.experimental
Short description
For testing purposes, not real usage
Definition
A Boolean value to indicate that this value set is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
+
Requirements
Enables experimental content to be developed following the same lifecycle that would be used for a production-level value set.
+
Comments
Allows filtering of value sets that are appropriate for use versus not.
There are no (further) constraints on this element
Element Id
ValueSet.date
Short description
Date last changed
Alternate names
Revision Date
Definition
The date (and optionally time) when the value set was created or revised (e.g. the 'content logical definition').
+
Comments
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
There are no (further) constraints on this element
Element Id
ValueSet.publisher
Short description
Name of the publisher (organization or individual)
Definition
The name of the organization or individual that published the value set.
+
Requirements
Helps establish the "authority/credibility" of the value set. May also allow for contact.
+
Comments
Usually an organization but may be an individual. The publisher (or steward) of the value set is the organization or individual primarily responsible for the maintenance and upkeep of the value set. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the value set. This item SHOULD be populated unless the information is available from context.
There are no (further) constraints on this element
Element Id
ValueSet.description
Short description
Natural language description of the value set
Alternate names
Scope, Purpose
Definition
A free text natural language description of the value set from a consumer's perspective. The textual description specifies the span of meanings for concepts to be included within the Value Set Expansion, and also may specify the intended use and limitations of the Value Set.
+
Comments
This description can be used to capture details such as why the value set was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the value set as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the value set is presumed to be the predominant language in the place the value set was created).The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description.
There are no (further) constraints on this element
Element Id
ValueSet.useContext
Short description
The context that the content is intended to support
Definition
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate value set instances.
+
Requirements
Assist in searching for appropriate content.
+
Comments
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
A code that identifies the type of context being specified by this usage context.
+
Comments
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
There are no (further) constraints on this element
Element Id
ValueSet.immutable
Short description
Indicates whether or not any change to the content logical definition may occur
Definition
If this is set to 'true', then no new versions of the content logical definition can be created. Note: Other metadata might still change.
+
Comments
Normally immutability is set to 'false', which is the default assumption if it is not populated. Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change. For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition.
There are no (further) constraints on this element
Element Id
ValueSet.purpose
Short description
Why this value set is defined
Definition
Explanation of why this value set is needed and why it has been designed as it has.
+
Comments
This element does not describe the usage of the value set. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this value set.
There are no (further) constraints on this element
Element Id
ValueSet.copyright
Short description
Use and/or publishing restrictions
Alternate names
License, Restrictions
Definition
A copyright statement relating to the value set and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the value set.
+
Requirements
Consumers must be able to determine any legal restrictions on the use of the value set and/or its content.
+
Comments
nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.
There are no (further) constraints on this element
Element Id
ValueSet.compose
Short description
Content logical definition of the value set (CLD)
Alternate names
Content Logical Definition, CLD
Definition
A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD).
There are no (further) constraints on this element
Element Id
ValueSet.compose.lockedDate
Short description
Fixed date for references with no specified version (transitive)
Definition
The Locked Date is the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version.
+
Comments
With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.
There are no (further) constraints on this element
Element Id
ValueSet.compose.inactive
Short description
Whether inactive codes are in the value set
Definition
Whether inactive codes - codes that are not approved for current use - are in the value set. If inactive = true, inactive codes are to be included in the expansion, if inactive = false, the inactive codes will not be included in the expansion. If absent, the behavior is determined by the implementation, or by the applicable $expand parameters (but generally, inactive codes would be expected to be included).
+
Comments
Note that in the FHIR terminology framework, "deprecated" does not mean inactive, but in some code systems, e.g. LOINC, "deprecated" does mean inactive. Code systems should define what codes are considered to be inactive. If this is not clearly defined (including in the FHIR code system resource), then all codes are assumed to be active.
+
The Value Set Definition specification defines an ActiveOnly element, which is the reverse of this element e.g. (ValueSet.compose.inactive=FALSE) is the same as (VSD.ActiveOnly=TRUE).
There are no (further) constraints on this element
Element Id
ValueSet.compose.include
Short description
Include one or more codes from a code system or other value set(s)
Definition
Include one or more codes from a code system or other value set(s).
+
Comments
All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is 'include all the codes that meet all these conditions'.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.system
Short description
The system the codes come from
Definition
An absolute URI which is the code system from which the selected codes come from.
+
Comments
If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes. See ''Coding.system'' for further documentation about the correct value for the system element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.version
Short description
Specific version of the code system referred to
Definition
The version of the code system that the codes are selected from, or the special version '*' for all versions.
+
Comments
This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set might not be known until a context of use binds it to a particular version. The special value '*' means all versions; It is at server discretion regarding expansions and which versions must be supported.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept
Short description
A concept defined in the system
Definition
Specifies a concept to be included or excluded.
+
Comments
The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept.display
Short description
Text to display for this code for this value set in this valueset
Definition
The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system.
+
Comments
The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.concept.designation
Short description
Additional representations for this concept
Definition
Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc.
+
Comments
Concepts have both a display and an array of designation. The display is equivalent to a special designation with an implied designation.use of "primary code" and a language equal to the Resource Language.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.filter
Short description
Select codes/concepts by their properties (including relationships)
Definition
Select concepts by specify a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified, they SHALL all be true.
+
Comments
Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.
The kind of operation to perform as a part of the filter criteria.
+
Comments
In case filter.property represents a property of the system, the operation applies to the selected property. In case filter.property represents a filter of the system, the operation SHALL match one of the CodeSystem.filter.operator values.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.filter.value
Short description
Code from the system, or regex criteria, or boolean value for exists
Definition
The match value may be either a code defined by the system, or a string value, which is a regex match on the literal string of the property value (if the filter represents a property defined in CodeSystem) or of the system filter value (if the filter represents a filter defined in CodeSystem) when the operation is 'regex', or one of the values (true and false), when the operation is 'exists'.
+
Comments
Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example.
There are no (further) constraints on this element
Element Id
ValueSet.compose.include.valueSet
Short description
Select the contents included in this value set
Definition
Selects the concepts found in this value set (based on its value set definition). This is an absolute URI that is a reference to ValueSet.url. If multiple value sets are specified this includes the union of the contents of all of the referenced value sets.
+
Comments
The value set URI is either a logical reference to a defined value set such as a SNOMED CT reference set, or a direct reference to a value set definition using ValueSet.url. The reference might not refer to an actual FHIR ValueSet resource; in this case, whatever is referred to is an implicit definition of a value set that needs to be clear about how versions are resolved.
There are no (further) constraints on this element
Element Id
ValueSet.compose.exclude
Short description
Explicitly exclude codes from a code system or other value sets
Definition
Exclude one or more codes from the value set based on code system filters and/or other value sets.
+
Comments
Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.
There are no (further) constraints on this element
Element Id
ValueSet.expansion
Short description
Used when the value set is "expanded"
Definition
A value set can also be "expanded", where the value set is turned into a simple collection of enumerated codes. This element holds the expansion, if it has been performed.
+
Comments
Expansion is performed to produce a collection of codes that are ready to use for data entry or validation. Value set expansions are always considered to be stateless - they are a record of the set of codes in the value set at a point in time under a given set of conditions, and are not subject to ongoing maintenance.
+
Expansion.parameter is a simplified list of parameters - a subset of the features of the Parameters resource.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.identifier
Short description
Identifies the value set expansion (business identifier)
Definition
An identifier that uniquely identifies this expansion of the valueset, based on a unique combination of the provided parameters, the system default parameters, and the underlying system code system versions etc. Systems may re-use the same identifier as long as those factors remain the same, and the expansion is the same, but are not required to do so. This is a business identifier.
+
Comments
Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).
There are no (further) constraints on this element
Element Id
ValueSet.expansion.timestamp
Short description
Time ValueSet expansion happened
Definition
The time at which the expansion was produced by the expanding system.
+
Comments
This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.total
Short description
Total number of codes in the expansion
Definition
The total number of concepts in the expansion. If the number of concept nodes in this resource is less than the stated number, then the server can return more using the offset parameter.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.offset
Short description
Offset at which this resource starts
Definition
If paging is being used, the offset at which this resource starts. I.e. this resource is a partial view into the expansion. If paging is not being used, this element SHALL NOT be present.
+
Comments
Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.parameter
Short description
Parameter that controlled the expansion process
Definition
A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion.
+
Comments
The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).
There are no (further) constraints on this element
Element Id
ValueSet.expansion.parameter.name
Short description
Name as assigned by the client or server
Definition
Name of the input parameter to the $expand operation; may be a server-assigned name for additional default or other server-supplied parameters used to control the expansion process.
+
Comments
The names are assigned at the discretion of the server.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.abstract
Short description
If user cannot select this entry
Definition
If true, this entry is included in the expansion for navigational purposes, and the user cannot select the code directly as a proper value.
+
Comments
This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.
+
Meaning When Missing
If this is not populated, systems can assume that the concept it not abstract. This SHALL always be populated for abstract concepts
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.inactive
Short description
If concept is inactive in the code system
Definition
If the concept is inactive in the code system that defines it. Inactive codes are those that are no longer to be used, but are maintained by the code system for understanding legacy data. It might not be known or specified whether an concept is inactive (and it may depend on the context of use).
+
Comments
This should only have a value if the concept is inactive.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.version
Short description
Version in which this code/display is defined
Definition
The version of the code system from this code was taken. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
+
Comments
The exact value of the version string is specified by the system from which the code is derived.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.code
Short description
Code - if blank, this is not a selectable code
Definition
The code for this item in the expansion hierarchy. If this code is missing the entry in the hierarchy is a place holder (abstract) and does not represent a valid code in the value set.
+
Comments
Note that FHIR strings SHALL NOT exceed 1MB in size
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.designation
Short description
Additional representations for this item
Definition
Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation.
+
Comments
The designations provided must be based on the value set and code system definitions.
There are no (further) constraints on this element
Element Id
ValueSet.expansion.contains.contains
Short description
Codes contained under this entry
Definition
Other codes and entries contained under this entry in the hierarchy.
+
Comments
If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_AnmerkungenZuDenMustSupportFeldern.html b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_AnmerkungenZuDenMustSupportFeldern.html
new file mode 100644
index 00000000..f586973c
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_AnmerkungenZuDenMustSupportFeldern.html
@@ -0,0 +1,284 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Anmerkungen zu den Must-Support Feldern
+
Das Profil ISiKVersicherungsverhaeltnisGesetzlich
+
Coverage.identifier
+
Hinweise: Grundsätzlich ist zu beachten, dass das Versicherungsverhältnis für die gesetzliche Versicherung durch die 30-stellige KVNR identifiziert wird. Die 10-stellige KVNR ist hingegen ein Identifier für das Datenobjekt Patient. Siehe
Command 'pagelink' could not render: Page not found.
. Es wird in ISiK davon ausgegangen, dass die 30-stellige KVNR nicht in bestätigungrelevanten Systemen geführt wird, sodass diese nicht als zuverlässiger Identifier für das Versicherungsverhältnis verwendbar ist. Bei einer Suche nach einem Versicherungsverhältnis SOLLTE dieses per Chaining auf das Datenobjekt Patient ermittelt werden.
+
Coverage.status
+
Bedeutung: Der Status einer Instanz des Profils ISiKVersicherungsverhaeltnisGesetzlich.
+
Hinweise: Das Element status macht deutlich, ob diese Instanz genutzt werden kann oder ob sie bspw. als ungültig oder falsch gekennzeichnet ist, siehe FHIR Kernspezifikaton.
+
Coverage.type
+
Bedeutung: Das Element type kennzeichnet die Art der Versicherung.
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Kompatibilitaet.html b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Kompatibilitaet.html
new file mode 100644
index 00000000..3bfb16f9
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Kompatibilitaet.html
@@ -0,0 +1,274 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kompatibilität
+
Profil ISiKVersicherungsverhaeltnisGesetzlich
+
Das Profil ISiKVersicherungsverhaeltnisGesetzlich basiert auf dem Profil Coverage der deutschen Basisprofile.
+Instanzen, die gegen ISiKVersicherungsverhaeltnisGesetzlich valide sind, sind auch valide gegen
Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden..
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Motivation.html b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Motivation.html
new file mode 100644
index 00000000..26732bba
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Motivation.html
@@ -0,0 +1,262 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Motivation
+
ISiK unterstützt Anwendungsszenarien, in denen durch das Krankenhaus erbrachte Leistungen erfasst oder gegenüber Kostenträgern abgerechnet werden. In diesen Anwendungsszenarien wird das Versicherungsverhältnis verwendet, um bspw. den Versicherungsstatus oder die Rechnungsanschrift der Versicherung zu ermitteln.
+
In FHIR werden Versicherungsverhältnisse mit der Coverage-Ressource repräsentiert.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Profil.html b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Profil.html
new file mode 100644
index 00000000..acb50a21
--- /dev/null
+++ b/IG/3.0.4/ImplementationGuide-markdown-Versicherungsverhaeltnis-Versicherungsverhaeltnis_Profil.html
@@ -0,0 +1,1046 @@
+
+
+
+
+
+
+
+ Implementierungsleitfaden ISiK-Basismodul
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Kostenübernahme im Rahmen eines gesetzlichen Versicherungsverhältnisses in Deutschland.
+
Comments
The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
There are no (further) constraints on this element
Element Id
Coverage.identifier
Short description
Business Identifier for the coverage
Definition
A unique identifier assigned to this coverage.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.status
Short description
active | cancelled | draft | entered-in-error
Definition
The status of the resource instance.
+
Requirements
Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.
+
Comments
This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.
Art der Versicherung: Selbstzahler, gesetzliche/private Versicherung, Berufsgenossenschaft oder Sozialamt
+
Requirements
The order of application of coverages is dependent on the types of coverage.
+
Comments
28.07.2017 (zulip): TC Konsens bzgl. Verwendung eines eigenen ValueSets anstelle des im Standrad definierten preferred bindings, da die dortigen Codes nicht passen.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Coverage.policyHolder
Short description
Owner of the policy
Definition
The party who 'owns' the insurance policy.
+
Requirements
This provides employer information in the case of Worker's Compensation and other policies.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.subscriber.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Pattern
+
{
+ "system": "http://fhir.de/sid/gkv/kvid-10"
+}
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.subject
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Pattern
+
{
+ "system": "http://fhir.de/sid/gkv/kvid-10"
+}
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Die Angabe des Namens des Versicherten dient der geeigneten Darstellung für den Benutzer und hat keine technische Bedeutung.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.period
Short description
Coverage start and end dates
Definition
Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.
+
Requirements
Some insurers require the submission of the coverage term.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Gibt den Kostenträger des Versicherten an. Die Angabe der IK-Nummer als logische Referenz sowie des Namens als Display ist zwingend erforderlich.
+Die Referenz auf eine Resource vom Typ Organization, die weitere Details zur Versicherung enthalten kann (z.B. Adresse, Kontaktdaten) ist optional.
+Sofern eine zweite Referenz auf einen Kostenträger existiert, so handelt es sich hierbei um den abrechnenden Kostenträger
+
Requirements
Need to identify the issuer to target for claim processing and for coordination of benefit processing.
+
Comments
Die Angabe der IK-Nummer des Versicherers in payor.identifier ist verpflichtend. Weitere Angaben zum Versicherer (Name, Adresse) können in einer Organization-Resource hinterlegt werden, auf die hier referenziert wird.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage.payor.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.payor.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.type
Short description
Description of identifier
Definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
+
Requirements
Allows users to make use of identifiers when the identifier system is not known.
+
Comments
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.system
Short description
The namespace for the identifier value
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
+
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.value
Short description
The value that is unique
Definition
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
+
Comments
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.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.period
Short description
Time period when id is/was valid for use
Definition
Time period during which identifier is/was valid for use.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.payor.identifier.assigner
Short description
Organization that issued id (may be just text)
Definition
Organization that issued/manages the identifier.
+
Comments
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
v2:CX.4 / (CX.4,CX.9,CX.10)
rim:II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
There are no (further) constraints on this element
Element Id
Coverage.payor.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.class.type
Short description
Type of class such as 'group' or 'plan'
Definition
The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.
+
Requirements
The insurer issued label for a specific health card value.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.order
Short description
Relative order of the coverage
Definition
The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.
+
Requirements
Used in managing the coordination of benefits.
+
Comments
Es git derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Für die Priorisierung der Versicherungsverhältnisse sollte statt dessen Account.coverage.priority verwendet werden, da die Priorisierung abhängig von Fall- und Abrechnungsart unterschiedlich sein kann.
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.network
Short description
Insurer network
Definition
Die Versicherungsleistungen sind an ein bestimmtes Netzwerk von Gesundheitsdienstleistern gebunden
+
Requirements
Used in referral for treatment and in claims processing.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary
Short description
Patient payments for services/products
Alternate names
CoPay, Deductible, Exceptions
Definition
A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.
+
Requirements
Required by providers to manage financial transaction with the patient.
+
Comments
For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.type
Short description
Exception category
Definition
The code for the specific exception.
+
Requirements
Needed to identify the exception associated with the amount for the patient.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.period
Short description
The effective period of the exception
Definition
The timeframe during when the exception is in force.
+
Requirements
Needed to identify the applicable timeframe for the exception for the correct calculation of patient costs.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.subrogation
Short description
Reimbursement to insurer
Definition
When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.
+
Requirements
See definition for when to be used.
+
Comments
Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.
There are no (further) constraints on this element
Element Id
Coverage.contract
Short description
Contract details
Definition
The policy(s) which constitute this insurance coverage.
+
Requirements
To reference the legally binding contract between the policy holder and the insurer.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage
Short description
Versicherungsdaten
Definition
Angaben zur Versicherung oder zur Kostenübernahme durch den Patienten selbst oder durch Dritte.
+
Comments
The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.
dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-6:A resource should have narrative for robust management text.`div`.exists()
dom-5:If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
There are no (further) constraints on this element
Element Id
Coverage.identifier
Short description
Business Identifier for the coverage
Definition
A unique identifier assigned to this coverage.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.identifier:pkv
Short description
An identifier intended for computation
Definition
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
+
Requirements
Allows coverages to be distinguished and referenced.
+
Comments
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.status
Short description
active | cancelled | draft | entered-in-error
Definition
The status of the resource instance.
+
Requirements
Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.
+
Comments
This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.
There are no (further) constraints on this element
Element Id
Coverage.type
Short description
Versicherungsart
Definition
Art der Versicherung: Selbstzahler, gesetzliche/private Versicherung, Berufsgenossenschaft oder Sozialamt
+
Requirements
The order of application of coverages is dependent on the types of coverage.
+
Comments
28.07.2017 (zulip): TC Konsens bzgl. Verwendung eines eigenen ValueSets anstelle des im Standrad definierten preferred bindings, da die dort igen Codes nicht passen.
There are no (further) constraints on this element
Element Id
Coverage.type.coding
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.coding:VersicherungsArtDeBasis
Short description
Code defined by a terminology system
Definition
A reference to a code defined by a terminology system.
+
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
+
Comments
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
There are no (further) constraints on this element
Element Id
Coverage.type.text
Short description
Plain text representation of the concept
Definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
+
Requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
+
Comments
Very often the text is the same as a displayName of one of the codings.
There are no (further) constraints on this element
Element Id
Coverage.policyHolder
Short description
Owner of the policy
Definition
The party who 'owns' the insurance policy.
+
Requirements
This provides employer information in the case of Worker's Compensation and other policies.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.subscriber.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Coverage.subscriber.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.subscriber.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary
Short description
Begünstigte Person
Definition
Person, auf die sich die Kostenübernahme bezieht (der Patient)
+
Requirements
This is the party who receives treatment for which the costs are reimbursed under the coverage.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
workflow:Event.subject
w5:FiveWs.subject[x]
cdanetv4:D01 through D09
v2:IN1-16, 18, 19-name of insured, address, date of birth
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.reference
Short description
Literal reference, Relative, internal or absolute URL
Definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
+
Comments
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.type
Short description
Type the reference refers to (e.g. "Patient")
Definition
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.
+
The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
+
Comments
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.identifier
Short description
Logical reference, when literal reference is not known
Definition
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
+
Comments
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.
+
When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference
+
Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
+
Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
Mappings
rim:n/a
v2:CX / EI (occasionally, more often EI maps to a resource id or a URL)
rim:II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
There are no (further) constraints on this element
Element Id
Coverage.beneficiary.display
Short description
Text alternative for the resource
Definition
Plain text narrative that identifies the resource in addition to the resource reference.
+
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
There are no (further) constraints on this element
Element Id
Coverage.period
Short description
Coverage start and end dates
Definition
Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.
+
Requirements
Some insurers require the submission of the coverage term.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
Person, die die Kosten übernimmt (beim Selbstzahlerverhältnis i.d.R. identisch mit subscriber)
+Sonderfall: Die Kostenübernahme wird von einer Person (subscriber) erklärt, die Übernahme erfolgt jedoch durch eine Organisation
+
Requirements
Need to identify the issuer to target for claim processing and for coordination of benefit processing.
+
Comments
May provide multiple identifiers such as insurance company identifier or business identifier (BIN number).
+For selfpay it may provide multiple paying persons and/or organizations.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
There are no (further) constraints on this element
Element Id
Coverage.class.type
Short description
Type of class such as 'group' or 'plan'
Definition
The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.
+
Requirements
The insurer issued label for a specific health card value.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.order
Short description
Relative order of the coverage
Definition
The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.
+
Requirements
Used in managing the coordination of benefits.
+
Comments
Es git derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Für die Priorisierung der Versicherungsverhältnisse sollte statt dessen Account.coverage.priority verwendet werden, da die Priorisierung abhängig von Fall- und Abrechnungsart unterschiedlich sein kann.
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.network
Short description
Insurer network
Definition
Die Versicherungsleistungen sind an ein bestimmtes Netzwerk von Gesundheitsdienstleistern gebunden
+
Requirements
Used in referral for treatment and in claims processing.
+
Comments
Es gibt derzeit in DE keine Verwendung für dieses Attribut
+(Konsens Interop-Forum 12.6.2017)
+Falls es UseCases gibt, die dieses Attribut benötigen, bitte Info auf chat.fhir.org
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary
Short description
Patient payments for services/products
Alternate names
CoPay, Deductible, Exceptions
Definition
A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.
+
Requirements
Required by providers to manage financial transaction with the patient.
+
Comments
For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.type
Short description
Exception category
Definition
The code for the specific exception.
+
Requirements
Needed to identify the exception associated with the amount for the patient.
+
Comments
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
There are no (further) constraints on this element
Element Id
Coverage.costToBeneficiary.exception.period
Short description
The effective period of the exception
Definition
The timeframe during when the exception is in force.
+
Requirements
Needed to identify the applicable timeframe for the exception for the correct calculation of patient costs.
+
Comments
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").
+
Period is not used for a duration (a measure of elapsed time). See Duration.
There are no (further) constraints on this element
Element Id
Coverage.subrogation
Short description
Reimbursement to insurer
Definition
When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.
+
Requirements
See definition for when to be used.
+
Comments
Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.
There are no (further) constraints on this element
Element Id
Coverage.contract
Short description
Contract details
Definition
The policy(s) which constitute this insurance coverage.
+
Requirements
To reference the legally binding contract between the policy holder and the insurer.
+
Comments
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
ele-1:All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ref-1:SHALL have a contained resource if a local reference is provided reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
rim:n/a
rim:The target of a resource reference is a RIM entry point (Act, Role, or Entity)
+
+
+
+
+ 
+