Unfallereignis
Dieses Profil bildet ein Unfallereignis ab. Es wurde sich bewusst zur Verwendung der "AdversEvent"-Ressource entschieden, da der FHIR-Standard leider keine vollständig passende Basis-Ressource zur Umsetzung eines Unfalls bietet. Man hätte an dieser Stelle auch die Observation-Ressource verwenden können, welche aber auch nicht ideal dafür geeignet ist. Der Vorteil bei der Verwendung des "AdversEvent" ist, dass man eine Referenz auf den Unfallort (Location) und auf die verunfallte Person (Patient) abbilden kann.
Alle Extensions sind im Abschnitt Extensions für AdversEvent dokumentiert. {{pagelink:Home/Extensions/Extensions-für-AdverseEvent.page.md}
Name: Unfallereignis Simplifier Projekt Link
Canonical: https://fhir.dguv.de/Basis/AdverseEvent/DGUV-Basis-PR-Unfallereignis
AdverseEvent | I | AdverseEvent | Element IdAdverseEvent Dieses Profil bildet das Unfallereignis ab. Alternate namesAE DefinitionActual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death.
| |
meta | Σ | 1..1 | Meta | There are no (further) constraints on this element Element IdAdverseEvent.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element IdAdverseEvent.meta.versionId Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element IdAdverseEvent.meta.lastUpdated When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdAdverseEvent.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element IdAdverseEvent.meta.profile Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
https://fhir.dguv.de/Basis/AdverseEvent/DGUV-Basis-PR-Unfallereignis|1.0
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element IdAdverseEvent.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdAdverseEvent.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". CommonTags (example)Constraints
|
extension | I | 0..* | Extension | There are no (further) constraints on this element Element IdAdverseEvent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
BeginnDerArbeitszeit | I | 0..1 | Extension(dateTime) | Element IdAdverseEvent.extension:BeginnDerArbeitszeit Beginn der Arbeitszeit Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.dguv.de/Basis/Extension/DGUV_Basis_EX_BeginnDerArbeitszeit Constraints
|
EndeDerArbeitszeit | I | 0..1 | Extension(dateTime) | Element IdAdverseEvent.extension:EndeDerArbeitszeit Ende der Arbeitszeit Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.dguv.de/Basis/Extension/DGUV-Basis-EX-EndeDerArbeitszeit Constraints
|
Unfallhergang | I | 0..1 | Extension(string) | Element IdAdverseEvent.extension:Unfallhergang Unfallhergang Alternate namesextensions, user content DefinitionVon der versicherten Person und/oder Angehörigen vorgetragener Unfallhergang There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.dguv.de/Basis/Extension/DGUV-Basis-EX-Unfallhergang Constraints
|
url | 1..1 | System.StringFixed Value | There are no (further) constraints on this element Element IdAdverseEvent.extension:Unfallhergang.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. System.String Fixed Valuehttps://fhir.dguv.de/Basis/Extension/DGUV-Basis-EX-Unfallhergang
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdAdverseEvent.extension:Unfallhergang.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| ||
valueString | string | There are no (further) constraints on this element Data Type | ||
BeschwerdenKlagen | I | 0..1 | Extension(string) | Element IdAdverseEvent.extension:BeschwerdenKlagen Vorgetragenen subjektiven Beschwerden der versicherten Person und/oder Angehörigen Alternate namesextensions, user content DefinitionDiese Extension beschreibt die von der versicherten Person und/oder Angehörigen alle vorgetragenen subjektiven Beschwerden There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.dguv.de/Basis/Extension/DGUV-Basis-EX-BeschwerdenKlagen Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdAdverseEvent.identifier Business identifier for the event DefinitionBusiness identifiers assigned to this adverse event by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the adverse event as it is known by various participating systems and in a way that remains consistent across servers. 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.
|
actuality | Σ ?! | 1..1 | codeBindingFixed Value | Element IdAdverseEvent.actuality actual | potential DefinitionWhether the event actually happened, or just had the potential to. Note that this is independent of whether anyone was affected or harmed or how severely. Note that FHIR strings SHALL NOT exceed 1MB in size Overall nature of the adverse event, e.g. real or potential. AdverseEventActuality (required)Constraints
actual
|
category | Σ | 1..1 | CodeableConceptBinding | Element IdAdverseEvent.category Liegt eine Verletzung nach dem Verletzungsartenverzeichnis vor. Oder Handelt es sich hier um ein DAV DefinitionThe overall type of event, intended for search and filtering purposes. 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. Unordered, Open, by coding(Value) Binding Overall categorization of the event, e.g. product-related or situational. AdverseEventCategory (extensible)Constraints
|
SAV-VAV | Σ | 0..1 | CodeableConceptBinding | Element IdAdverseEvent.category:SAV-VAV Es Liegt eine Verletzung nach dem Verletzungsartenverzeichnis vor. DefinitionThe overall type of event, intended for search and filtering purposes. 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. Overall categorization of the event, e.g. product-related or situational. AdverseEventCategory (extensible)Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdAdverseEvent.category:SAV-VAV.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
system | Σ | 1..1 | uriBinding | Element IdAdverseEvent.category:SAV-VAV.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Verletzungsartenverzeichnis DGUV_Basis_CS_Verletzungsartenverzeichnis (required)Constraints
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.category:SAV-VAV.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | code | Element IdAdverseEvent.category:SAV-VAV.coding.code Code nach VAV oder SAV DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | Σ | 1..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.category:SAV-VAV.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdAdverseEvent.category:SAV-VAV.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.category:SAV-VAV.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
DAV | Σ | 0..1 | CodeableConceptBinding | Element IdAdverseEvent.category:DAV Es liegt keine Verletzung nach dem Verletzungsartenverfahren (VAV) vor / Stationäres Durchgangsarztverfahren (DAV) DefinitionThe overall type of event, intended for search and filtering purposes. 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. Overall categorization of the event, e.g. product-related or situational. AdverseEventCategory (extensible)Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdAdverseEvent.category:DAV.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdAdverseEvent.category:DAV.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.category:DAV.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element IdAdverseEvent.category:DAV.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
DAV
|
display | Σ | 1..1 | stringFixed Value | Element IdAdverseEvent.category:DAV.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
Durchgangarztverfahren
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdAdverseEvent.category:DAV.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.category:DAV.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
event | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdAdverseEvent.event Type of the event itself in relation to the subject DefinitionThis element defines the specific type of event that occurred or that was prevented from occurring. 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. Detailed type of event. SNOMEDCTClinicalFindings (example)Constraints
|
subject | Σ I | 1..1 | Reference(Versicherte Person) | Element IdAdverseEvent.subject Subject impacted by event Alternate namespatient DefinitionThis subject or group impacted by the event. Allows for exposure of biohazard (such as legionella) to a group of individuals in a hospital. If AdverseEvent.resultingCondition differs among members of the group, then use Patient as the subject.
|
reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.subject.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdAdverseEvent.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdAdverseEvent.subject.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdAdverseEvent.encounter Encounter created as part of DefinitionThe Encounter during which AdverseEvent was created or to which the creation of this record is tightly associated. 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. For example, if a medication administration was considered an adverse event because it resulted in a rash, then the encounter when the medication administration was given is the context. If the patient reports the AdverseEvent during a second encounter, that second encounter is not the context.
|
date | Σ | 1..1 | dateTime | Element IdAdverseEvent.date Unfallzeitpunkt DefinitionThe date (and perhaps time) when the adverse event occurred.
|
detected | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdAdverseEvent.detected When the event was detected DefinitionEstimated or actual date the AdverseEvent began, in the opinion of the reporter.
|
recordedDate | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdAdverseEvent.recordedDate When the event was recorded DefinitionThe date on which the existence of the AdverseEvent was first recorded. The recordedDate represents the date when this particular AdverseEvent record was created in the system, not the date of the most recent update. The date of the last record modification can be retrieved from the resource metadata.
|
resultingCondition | Σ I | 0..* | Reference(Condition) | There are no (further) constraints on this element Element IdAdverseEvent.resultingCondition Effect on the subject due to this event DefinitionIncludes information about the reaction that occurred as a result of exposure to a substance (for example, a drug or a chemical). 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.
|
location | Σ I | 0..1 | Reference(Unfallort) | Element IdAdverseEvent.location Location where adverse event occurred DefinitionThe information about where the adverse event occurred. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.location.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdAdverseEvent.location.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdAdverseEvent.location.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.location.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
|
seriousness | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdAdverseEvent.seriousness Seriousness of the event DefinitionAssessment whether this event was of real importance. 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. Overall seriousness of this event for the patient. AdverseEventSeriousness (example)Constraints
|
severity | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdAdverseEvent.severity mild | moderate | severe DefinitionDescribes the severity of the adverse event, in relation to the subject. Contrast to AdverseEvent.seriousness - a severe rash might not be serious, but a mild heart problem is. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The severity of the adverse event itself, in direct relation to the subject. AdverseEventSeverity (required)Constraints
|
outcome | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdAdverseEvent.outcome resolved | recovering | ongoing | resolvedWithSequelae | fatal | unknown DefinitionDescribes the type of outcome from the adverse event. 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. TODO (and should this be required?). AdverseEventOutcome (required)Constraints
|
recorder | Σ I | 0..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element IdAdverseEvent.recorder Who recorded the adverse event DefinitionInformation on who recorded the adverse event. May be the patient or a practitioner. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson) Constraints
|
contributor | Σ I | 0..* | Reference(Practitioner | PractitionerRole | Device) | There are no (further) constraints on this element Element IdAdverseEvent.contributor Who was involved in the adverse event or the potential adverse event DefinitionParties that may or should contribute or have contributed information to the adverse event, which can consist of one or more activities. Such information includes information leading to the decision to perform the activity and how to perform the activity (e.g. consultant), information that the activity itself seeks to reveal (e.g. informant of clinical history), or information about what activity was performed (e.g. informant witness). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Device) Constraints
|
suspectEntity | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity The suspected agent causing the adverse event DefinitionDescribes the entity that is suspected to have caused the adverse event.
|
instance | Σ I | 1..1 | Reference(Immunization | Procedure | Substance | Medication | MedicationAdministration | MedicationStatement | Device) | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.instance Refers to the specific entity that caused the adverse event Alternate namesSubstance or Medication or Device DefinitionIdentifies the actual instance of what caused the adverse event. May be a substance, medication, medication administration, medication statement or a device. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Immunization | Procedure | Substance | Medication | MedicationAdministration | MedicationStatement | Device) Constraints
|
causality | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.causality Information on the possible cause of the event DefinitionInformation on the possible cause of the event.
|
assessment | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.causality.assessment Assessment of if the entity caused the event DefinitionAssessment of if the entity caused the event. 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. Codes for the assessment of whether the entity caused the event. AdverseEventCausalityAssessment (example)Constraints
|
productRelatedness | Σ | 0..1 | string | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.causality.productRelatedness AdverseEvent.suspectEntity.causalityProductRelatedness DefinitionAdverseEvent.suspectEntity.causalityProductRelatedness. Note that FHIR strings SHALL NOT exceed 1MB in size
|
author | Σ I | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.causality.author AdverseEvent.suspectEntity.causalityAuthor DefinitionAdverseEvent.suspectEntity.causalityAuthor. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Constraints
|
method | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdAdverseEvent.suspectEntity.causality.method ProbabilityScale | Bayesian | Checklist DefinitionProbabilityScale | Bayesian | Checklist. 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. TODO. AdverseEventCausalityMethod (example)Constraints
|
subjectMedicalHistory | Σ I | 0..* | Reference(Condition | Observation | AllergyIntolerance | FamilyMemberHistory | Immunization | Procedure | Media | DocumentReference) | There are no (further) constraints on this element Element IdAdverseEvent.subjectMedicalHistory AdverseEvent.subjectMedicalHistory DefinitionAdverseEvent.subjectMedicalHistory. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Condition | Observation | AllergyIntolerance | FamilyMemberHistory | Immunization | Procedure | Media | DocumentReference) Constraints
|
referenceDocument | Σ I | 0..* | Reference(DocumentReference) | There are no (further) constraints on this element Element IdAdverseEvent.referenceDocument AdverseEvent.referenceDocument DefinitionAdverseEvent.referenceDocument. 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.
|
study | Σ I | 0..* | Reference(ResearchStudy) | There are no (further) constraints on this element Element IdAdverseEvent.study AdverseEvent.study DefinitionAdverseEvent.study. 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.
|
Besonderheiten
AdversEvent.category
An dieser Stelle wird ausgewählt, ob es sich bei dem Berufsunfall um das gewöhnliche "stationäre Durchgangarztverfahren" handelt (hier im Feld "DAV"), oder ein Code nach dem Verletzungsartenverfahren/Schwerstverletzungsartenverfahren (https://www.dguv.de/medien/landesverbaende/de/med_reha/documents/verletz3.pdf) der DGUV (category.SAV-VAV) gewählt werden muss. Für die Angabe des Verletzungs- bzw. Schwerstverletzungsartenverfahrens wurde ein Codesystem "Verletzungsartenverzeichnis" erstellt.
Siehe hierzu Verletzungsartenverzeichnis