EPAProvenance
Das EPAProvenance
-Profil wird im Medication Service sowohl für den Herkunftsnachweis als auch im Kontext des elektronischen Medikationsplans als Verifizierungsnachweis verwendet. Diese Ressource dokumentiert die Ursprünge, die Historie und die Verantwortlichkeiten der im Medikationsplan enthaltenen Informationen.
Das EPAProvenance
-Profil enthält wichtige Metadaten, die den Ursprung der Daten belegen. Dazu gehören Angaben darüber, wer die Daten erstellt oder verändert hat und wann diese Aktionen durchgeführt wurden. Diese Nachverfolgbarkeit ist entscheidend, um die Verlässlichkeit der Medikationsinformationen sicherzustellen.
Ein zentrales Merkmal der EPAProvenance
-Ressource ist die versionierte Referenzierung der Daten. Jede Änderung an den Medikationsinformationen wird versioniert dokumentiert, sodass jederzeit die genaue Historie der Daten nachvollzogen werden kann. Dies ermöglicht es dem Medication Service, die Herkunft und die Validität der Informationen kontinuierlich zu überprüfen und sicherzustellen, dass immer die aktuellsten und verifizierten Daten verwendet werden.
Profil für gemeinsame Datengrundlage im ePA Medication Service
EPAProvenance (Provenance) | I | Provenance | |
id | Σ | 0..1 | string |
meta | S Σ | 0..1 | Meta |
id | 0..1 | string | |
extension | I | 0..* | Extension |
versionId | S Σ | 0..1 | id |
lastUpdated | S Σ | 0..1 | instant |
source | Σ | 0..1 | uri |
profile | Σ | 0..* | canonical(StructureDefinition) |
security | Σ | 0..* | CodingBinding |
tag | Σ | 0..* | Coding |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
status | 1..1 | codeBindingFixed Value | |
div | I | 1..1 | xhtml |
contained | 0..* | Resource | |
extension | I | 0..* | Extension |
modifierExtension | ?! I | 0..* | Extension |
target | S Σ I | 1..* | Reference(Resource) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | S Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | S Σ | 0..1 | IdentifierKvid10, IdentifierTelematikId |
display | S Σ | 0..1 | string |
occurred[x] | S | 0..1 | |
occurredDateTime | S | 0..1 | dateTime |
recorded | S Σ | 1..1 | instant |
policy | 0..* | uri | |
location | I | 0..1 | Reference(Location) |
reason | 0..* | CodeableConceptBinding | |
activity | S | 1..1 | CodeableConceptBinding |
agent | S | 1..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
type | S Σ | 1..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | S Σ | 1..1 | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | S Σ | 1..1 | uri |
version | S Σ | 1..1 | string |
code | S Σ | 1..1 | code |
display | S Σ | 1..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
role | 0..* | CodeableConcept | |
who | S Σ I | 1..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | S Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | S Σ | 0..1 | IdentifierKvid10, IdentifierTelematikId |
display | Σ | 0..1 | string |
onBehalfOf | I | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
entity | S | 0..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
role | S Σ | 1..1 | codeBindingPattern |
what | S Σ I | 1..1 | Reference(Resource) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | Σ | 0..1 | Identifier |
display | S Σ | 1..1 | string |
agent | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
type | Σ | 0..1 | CodeableConceptBinding |
role | 0..* | CodeableConcept | |
who | Σ I | 1..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
onBehalfOf | I | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
signature | 0..* | Signature |
Provenance | |
Definition | Dieses Profil bildet die Herkunftsdaten ab. |
Cardinality | 0...* |
Alias | History, Event, Activity |
Comments | Some parties may be duplicated between the target resource and its provenance. For instance, the prescriber is usually (but not always) the author of the prescription resource. This resource is defined with close consideration for W3C Provenance. |
Invariants |
|
Mappings |
|
Provenance.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Provenance.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Must Support | True |
Summary | True |
Invariants |
|
Mappings |
|
Provenance.meta.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.meta.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.meta.versionId | |
Definition | The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. |
Cardinality | 0...1 |
Type | id |
Must Support | True |
Summary | True |
Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. |
Invariants |
|
Mappings |
|
Provenance.meta.lastUpdated | |
Definition | When the resource last changed - e.g. when the version changed. |
Cardinality | 0...1 |
Type | instant |
Must Support | True |
Summary | True |
Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction. |
Invariants |
|
Mappings |
|
Provenance.meta.source | |
Definition | A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](provenance.html#) 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. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Comments | In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL. |
Invariants |
|
Mappings |
|
Provenance.meta.profile | |
Definition | A list of profiles (references to [StructureDefinition](structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](structuredefinition-definitions.html#StructureDefinition.url). |
Cardinality | 0...* |
Type | canonical(StructureDefinition) |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
Provenance.meta.security | |
Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. |
Cardinality | 0...* |
Type | Coding |
Binding | Security Labels from the Healthcare Privacy and Security Classification System. |
Summary | True |
Comments | The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Mappings |
|
Provenance.meta.tag | |
Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. |
Cardinality | 0...* |
Type | Coding |
Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". |
Summary | True |
Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Mappings |
|
Provenance.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
Provenance.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Invariants |
|
Mappings |
|
Provenance.text | |
Definition | In diesem Element können die, in der Instanz, enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
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. |
Invariants |
|
Mappings |
|
Provenance.text.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.text.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.text.status | |
Definition | 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. |
Cardinality | 1...1 |
Type | code |
Binding | The status of a resource narrative. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Fixed Value | extensions |
Mappings |
|
Provenance.text.div | |
Definition | The actual narrative content, a stripped down version of XHTML. |
Cardinality | 1...1 |
Type | xhtml |
Comments | The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Invariants |
|
Mappings |
|
Provenance.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
Mappings |
|
Provenance.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.target | |
Definition | Hier wird die Information bzw. Informationsgruppe als Ziel referenziert, auf die sich die Herkunftsinformation bezieht. |
Cardinality | 1...* |
Type | Reference(Resource) |
Must Support | True |
Summary | True |
Comments | Target references are usually version specific, but might not be, if a version has not been assigned or if the provenance information is part of the set of resources being maintained (i.e. a document). When using the RESTful API, the identity of the resource might not be known (especially not the version specific one); the client may either submit the resource first, and then the provenance, or it may submit both using a single transaction. See the notes on transaction for further discussion. |
Invariants |
|
Mappings |
|
Provenance.target.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.target.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.target.reference | |
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. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.target.type | |
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). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.target.identifier | |
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. |
Cardinality | 0...1 |
Type | IdentifierKvid10, IdentifierTelematikId |
Must Support | True |
Summary | True |
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). |
Invariants |
|
Mappings |
|
Provenance.target.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.occurred[x] | |
Definition | Hier wird der Zeitpunkt angegeben, an dem die jeweilige Aktivität durchgeführt wurde. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Comments | The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time. |
Slicing | Unordered, Open, by $this(Type) |
Invariants |
|
Mappings |
|
Provenance.occurred[x]:occurredDateTime | |
Definition | The period during which the activity occurred. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Comments | The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time. |
Invariants |
|
Mappings |
|
Provenance.recorded | |
Definition | The instant of time at which the activity was recorded. |
Cardinality | 1...1 |
Type | instant |
Must Support | True |
Summary | True |
Comments | This can be a little different from the time stamp on the resource if there is a delay between recording the event and updating the provenance and target resource. |
Invariants |
|
Mappings |
|
Provenance.policy | |
Definition | Policy or plan the activity was defined by. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc. |
Cardinality | 0...* |
Type | uri |
Comments | For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element. |
Invariants |
|
Mappings |
|
Provenance.location | |
Definition | Where the activity occurred, if relevant. |
Cardinality | 0...1 |
Type | Reference(Location) |
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. |
Invariants |
|
Mappings |
|
Provenance.reason | |
Definition | The reason that the activity was taking place. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The reason the activity took place. |
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. |
Invariants |
|
Mappings |
|
Provenance.activity | |
Definition | Hier kann die Art der durchgeführten Aktivität in codierter Form angegeben werden. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | The activity that took place. |
Must Support | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent | |
Definition | Hier wird eine Person/Entität , die an der Integration der Dokumentation in das Zielsystem beteiligt ist, in Kombination mit einer bestimmten Rolle angegeben. **Beispiele:** * Verfassende Entität (z.B. eine \"Behandelnde Person\" wie eine ÄrztIn oder eine ApothekerIn/Apotheken-Fachangestellte setzt eine neue Medikation an und verfasst dazu einen Eintrag \"Medikation-Information\", wo die Informationen zu dieser Medikation abgebildet werden). * Eintragende Entität (z.B. die behandelnde HausärztIn als \"Behandelnde Person\" übernimmt eine neu angesetzte Medikation aus dem \"Dokumentenverweis\" Krankenhaus-Entlassbrief) |
Cardinality | 1...* |
Type | BackboneElement |
Must Support | True |
Requirements | An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility. |
Comments | Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. |
Invariants |
|
Mappings |
|
Provenance.agent.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.agent.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.agent.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Provenance.agent.type | |
Definition | Hier ist die Rolle/Funktion der Person/Entität anzugeben. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | The type of participation that a provenance agent played with respect to the activity. |
Must Support | True |
Summary | True |
Comments | For example: author, performer, enterer, attester, etc. |
Invariants |
|
Mappings |
|
Provenance.agent.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.agent.type.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.agent.type.coding.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.version | |
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. |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.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). |
Cardinality | 1...1 |
Type | code |
Must Support | True |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Provenance.agent.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.type.text | |
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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.role | |
Definition | Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The role that a provenance agent played with respect to the activity. |
Comments | For example: doctor, nurse, clerk, etc. |
Invariants |
|
Mappings |
|
Provenance.agent.who | |
Definition | Hier wird die Person/Entität referenziert, die die Integration der Dokumentation in das Zielsystem durchführt. |
Cardinality | 1...1 |
Type | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) |
Must Support | True |
Summary | True |
Comments | whoIdentity should be used when the agent is not a Resource type. |
Invariants |
|
Mappings |
|
Provenance.agent.who.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.agent.who.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.agent.who.reference | |
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. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.who.type | |
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). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.who.identifier | |
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. |
Cardinality | 0...1 |
Type | IdentifierKvid10, IdentifierTelematikId |
Must Support | True |
Summary | True |
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). |
Invariants |
|
Mappings |
|
Provenance.agent.who.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.agent.onBehalfOf | |
Definition | The individual, device, or organization for whom the change was made. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
Comments | onBehalfOfIdentity should be used when the agent is not a Resource type. |
Invariants |
|
Mappings |
|
Provenance.entity | |
Definition | Hier kann ein Dokument als Informationsquelle für die Information angegeben werden, die als Ziel der Herkunfts-Information referenziert ist. |
Cardinality | 0...* |
Type | BackboneElement |
Must Support | True |
Invariants |
|
Mappings |
|
Provenance.entity.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.entity.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.entity.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Provenance.entity.role | |
Definition | Dieses Element beschreibt, wie die Information genutzt wird. |
Cardinality | 1...1 |
Type | code |
Binding | How an entity was used in an activity. |
Must Support | True |
Summary | True |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Pattern | source |
Mappings |
|
Provenance.entity.what | |
Definition | Hier wird das Element referenziert, das als Quell-Element für die Information gedient hat. |
Cardinality | 1...1 |
Type | Reference(Resource) |
Must Support | True |
Summary | True |
Comments | whatIdentity should be used for entities that are not a Resource type. |
Invariants |
|
Mappings |
|
Provenance.entity.what.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.entity.what.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.entity.what.reference | |
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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.entity.what.type | |
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). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.entity.what.identifier | |
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. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
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). |
Invariants |
|
Mappings |
|
Provenance.entity.what.display | |
Definition | Freitext der die Ursprungs-Information identifiziert. Beispielsweise "Krankenhaus-Entlassbrief vom 25.01.24". |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Provenance.entity.agent | |
Definition | Hier wird eine Person/Entität angegeben, die an der Dokumentation beteiligt ist. |
Cardinality | 0...* |
Type | BackboneElement |
Comments | A usecase where one Provenance.entity.agent is used where the Entity that was used in the creation/updating of the Target, is not in the context of the same custodianship as the Target, and thus the meaning of Provenance.entity.agent is to say that the entity referenced is managed elsewhere and that this Agent provided access to it. This would be similar to where the Entity being referenced is managed outside FHIR, such as through HL7 v2, v3, or XDS. This might be where the Entity being referenced is managed in another FHIR resource server. Thus it explains the Provenance of that Entity's use in the context of this Provenance activity. |
Mappings |
|
Provenance.entity.agent.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Provenance.entity.agent.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Provenance.entity.agent.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Provenance.entity.agent.type | |
Definition | Hier ist die Rolle/Funktion der Person/Entität anzugeben. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The type of participation that a provenance agent played with respect to the activity. |
Summary | True |
Comments | For example: author, performer, enterer, attester, etc. |
Invariants |
|
Mappings |
|
Provenance.entity.agent.role | |
Definition | Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | The role that a provenance agent played with respect to the activity. |
Comments | For example: doctor, nurse, clerk, etc. |
Invariants |
|
Mappings |
|
Provenance.entity.agent.who | |
Definition | Hier wird die datenintegrierende Person referenziert. |
Cardinality | 1...1 |
Type | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
Summary | True |
Comments | whoIdentity should be used when the agent is not a Resource type. |
Invariants |
|
Mappings |
|
Provenance.entity.agent.onBehalfOf | |
Definition | The individual, device, or organization for whom the change was made. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) |
Comments | onBehalfOfIdentity should be used when the agent is not a Resource type. |
Invariants |
|
Mappings |
|
Provenance.signature | |
Definition | A digital signature on the target Reference(s). The signer should match a Provenance.agent. The purpose of the signature is indicated. |
Cardinality | 0...* |
Type | Signature |
Comments | The elements of the Signature Resource are for ease of access of these elements. For digital signatures (Xml DigSig, JWS), the non-repudiation proof comes from the Signature validation, which includes validation of the referenced objects (e.g. Resources) (a.k.a., Content) in the XML-Signature Detached form. |
Invariants |
|
Mappings |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="epa-provenance" /> <url value="https://gematik.de/fhir/epa/StructureDefinition/epa-provenance" /> <version value="1.1.0" /> <name value="EPAProvenance" /> <title value="EPA Provenance" /> <status value="active" /> <experimental value="false" /> <date value="2024-08-14" /> <publisher value="mio42 GmbH" /> <description value="Dieses Profil bildet die Herkunftsdaten ab." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Provenance" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Provenance" /> <derivation value="constraint" /> <differential> <element id="Provenance"> <path value="Provenance" /> <definition value="Dieses Profil bildet die Herkunftsdaten ab." /> </element> <element id="Provenance.meta"> <path value="Provenance.meta" /> <mustSupport value="true" /> </element> <element id="Provenance.meta.versionId"> <path value="Provenance.meta.versionId" /> <mustSupport value="true" /> </element> <element id="Provenance.meta.lastUpdated"> <path value="Provenance.meta.lastUpdated" /> <mustSupport value="true" /> </element> <element id="Provenance.text"> <path value="Provenance.text" /> <definition value="In diesem Element können die, in der Instanz, enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind." /> </element> <element id="Provenance.text.status"> <path value="Provenance.text.status" /> <fixedCode value="extensions" /> </element> <element id="Provenance.target"> <path value="Provenance.target" /> <definition value="Hier wird die Information bzw. Informationsgruppe als Ziel referenziert, auf die sich die Herkunftsinformation bezieht." /> <mustSupport value="true" /> </element> <element id="Provenance.target.reference"> <path value="Provenance.target.reference" /> <mustSupport value="true" /> </element> <element id="Provenance.target.identifier"> <path value="Provenance.target.identifier" /> <type> <code value="Identifier" /> <profile value="http://fhir.de/StructureDefinition/identifier-kvid-10" /> <profile value="http://fhir.de/StructureDefinition/identifier-telematik-id" /> </type> <mustSupport value="true" /> </element> <element id="Provenance.target.display"> <path value="Provenance.target.display" /> <mustSupport value="true" /> </element> <element id="Provenance.occurred[x]"> <path value="Provenance.occurred[x]" /> <slicing> <discriminator> <type value="type" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <definition value="Hier wird der Zeitpunkt angegeben, an dem die jeweilige Aktivität durchgeführt wurde." /> <type> <code value="dateTime" /> </type> <mustSupport value="true" /> </element> <element id="Provenance.occurred[x]:occurredDateTime"> <path value="Provenance.occurred[x]" /> <sliceName value="occurredDateTime" /> <min value="0" /> <max value="1" /> <type> <code value="dateTime" /> </type> <mustSupport value="true" /> </element> <element id="Provenance.recorded"> <path value="Provenance.recorded" /> <mustSupport value="true" /> </element> <element id="Provenance.activity"> <path value="Provenance.activity" /> <definition value="Hier kann die Art der durchgeführten Aktivität in codierter Form angegeben werden." /> <min value="1" /> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/terminology/ValueSet/epa-provenance-activity-type-vs" /> </binding> </element> <element id="Provenance.agent"> <path value="Provenance.agent" /> <definition value="Hier wird eine Person/Entität , die an der Integration der Dokumentation in das Zielsystem beteiligt ist, in Kombination mit einer bestimmten Rolle angegeben.\n\n**Beispiele:**\n* Verfassende Entität (z.B. eine \"Behandelnde Person\" wie eine ÄrztIn oder eine ApothekerIn/Apotheken-Fachangestellte setzt eine neue Medikation an und verfasst dazu einen Eintrag \"Medikation-Information\", wo die Informationen zu dieser Medikation abgebildet werden).\n* Eintragende Entität (z.B. die behandelnde HausärztIn als \"Behandelnde Person\" übernimmt eine neu angesetzte Medikation aus dem \"Dokumentenverweis\" Krankenhaus-Entlassbrief)" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.type"> <path value="Provenance.agent.type" /> <definition value="Hier ist die Rolle/Funktion der Person/Entität anzugeben." /> <min value="1" /> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/terminology/ValueSet/epa-provenance-participant-type-vs" /> </binding> </element> <element id="Provenance.agent.type.coding"> <path value="Provenance.agent.type.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.type.coding.system"> <path value="Provenance.agent.type.coding.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.type.coding.version"> <path value="Provenance.agent.type.coding.version" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.type.coding.code"> <path value="Provenance.agent.type.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.type.coding.display"> <path value="Provenance.agent.type.coding.display" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.role"> <path value="Provenance.agent.role" /> <definition value="Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist." /> </element> <element id="Provenance.agent.who"> <path value="Provenance.agent.who" /> <definition value="Hier wird die Person/Entität referenziert, die die Integration der Dokumentation in das Zielsystem durchführt." /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/PractitionerRole" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/RelatedPerson" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> </type> <mustSupport value="true" /> </element> <element id="Provenance.agent.who.reference"> <path value="Provenance.agent.who.reference" /> <mustSupport value="true" /> </element> <element id="Provenance.agent.who.identifier"> <path value="Provenance.agent.who.identifier" /> <type> <code value="Identifier" /> <profile value="http://fhir.de/StructureDefinition/identifier-kvid-10" /> <profile value="http://fhir.de/StructureDefinition/identifier-telematik-id" /> </type> <mustSupport value="true" /> </element> <element id="Provenance.entity"> <path value="Provenance.entity" /> <definition value="Hier kann ein Dokument als Informationsquelle für die Information angegeben werden, die als Ziel der Herkunfts-Information referenziert ist." /> <mustSupport value="true" /> </element> <element id="Provenance.entity.role"> <path value="Provenance.entity.role" /> <definition value="Dieses Element beschreibt, wie die Information genutzt wird." /> <patternCode value="source" /> <mustSupport value="true" /> </element> <element id="Provenance.entity.what"> <path value="Provenance.entity.what" /> <definition value="Hier wird das Element referenziert, das als Quell-Element für die Information gedient hat." /> <mustSupport value="true" /> </element> <element id="Provenance.entity.what.display"> <path value="Provenance.entity.what.display" /> <definition value="Freitext der die Ursprungs-Information identifiziert. Beispielsweise "Krankenhaus-Entlassbrief vom 25.01.24"." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Provenance.entity.agent"> <path value="Provenance.entity.agent" /> <definition value="Hier wird eine Person/Entität angegeben, die an der Dokumentation beteiligt ist." /> <type> <code value="BackboneElement" /> </type> </element> <element id="Provenance.entity.agent.type"> <path value="Provenance.entity.agent.type" /> <definition value="Hier ist die Rolle/Funktion der Person/Entität anzugeben." /> </element> <element id="Provenance.entity.agent.role"> <path value="Provenance.entity.agent.role" /> <definition value="Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist." /> </element> <element id="Provenance.entity.agent.who"> <path value="Provenance.entity.agent.who" /> <definition value="Hier wird die datenintegrierende Person referenziert." /> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "epa-provenance", "url": "https://gematik.de/fhir/epa/StructureDefinition/epa-provenance", "version": "1.1.0", "name": "EPAProvenance", "title": "EPA Provenance", "status": "active", "experimental": false, "date": "2024-08-14", "publisher": "mio42 GmbH", "description": "Dieses Profil bildet die Herkunftsdaten ab.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Provenance", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Provenance", "derivation": "constraint", "differential": { "element": [ { "id": "Provenance", "path": "Provenance", "definition": "Dieses Profil bildet die Herkunftsdaten ab." }, { "id": "Provenance.meta", "path": "Provenance.meta", "mustSupport": true }, { "id": "Provenance.meta.versionId", "path": "Provenance.meta.versionId", "mustSupport": true }, { "id": "Provenance.meta.lastUpdated", "path": "Provenance.meta.lastUpdated", "mustSupport": true }, { "id": "Provenance.text", "path": "Provenance.text", "definition": "In diesem Element können die, in der Instanz, enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind." }, { "id": "Provenance.text.status", "path": "Provenance.text.status", "fixedCode": "extensions" }, { "id": "Provenance.target", "path": "Provenance.target", "definition": "Hier wird die Information bzw. Informationsgruppe als Ziel referenziert, auf die sich die Herkunftsinformation bezieht.", "mustSupport": true }, { "id": "Provenance.target.reference", "path": "Provenance.target.reference", "mustSupport": true }, { "id": "Provenance.target.identifier", "path": "Provenance.target.identifier", "type": [ { "code": "Identifier", "profile": [ "http://fhir.de/StructureDefinition/identifier-kvid-10", "http://fhir.de/StructureDefinition/identifier-telematik-id" ] } ], "mustSupport": true }, { "id": "Provenance.target.display", "path": "Provenance.target.display", "mustSupport": true }, { "id": "Provenance.occurred[x]", "path": "Provenance.occurred[x]", "slicing": { "discriminator": [ { "type": "type", "path": "$this" } ], "rules": "open" }, "definition": "Hier wird der Zeitpunkt angegeben, an dem die jeweilige Aktivität durchgeführt wurde.", "type": [ { "code": "dateTime" } ], "mustSupport": true }, { "id": "Provenance.occurred[x]:occurredDateTime", "path": "Provenance.occurred[x]", "sliceName": "occurredDateTime", "min": 0, "max": "1", "type": [ { "code": "dateTime" } ], "mustSupport": true }, { "id": "Provenance.recorded", "path": "Provenance.recorded", "mustSupport": true }, { "id": "Provenance.activity", "path": "Provenance.activity", "definition": "Hier kann die Art der durchgeführten Aktivität in codierter Form angegeben werden.", "min": 1, "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/terminology/ValueSet/epa-provenance-activity-type-vs" } }, { "id": "Provenance.agent", "path": "Provenance.agent", "definition": "Hier wird eine Person/Entität , die an der Integration der Dokumentation in das Zielsystem beteiligt ist, in Kombination mit einer bestimmten Rolle angegeben.\n\n**Beispiele:**\n* Verfassende Entität (z.B. eine \\\"Behandelnde Person\\\" wie eine ÄrztIn oder eine ApothekerIn/Apotheken-Fachangestellte setzt eine neue Medikation an und verfasst dazu einen Eintrag \\\"Medikation-Information\\\", wo die Informationen zu dieser Medikation abgebildet werden).\n* Eintragende Entität (z.B. die behandelnde HausärztIn als \\\"Behandelnde Person\\\" übernimmt eine neu angesetzte Medikation aus dem \\\"Dokumentenverweis\\\" Krankenhaus-Entlassbrief)", "mustSupport": true }, { "id": "Provenance.agent.type", "path": "Provenance.agent.type", "definition": "Hier ist die Rolle/Funktion der Person/Entität anzugeben.", "min": 1, "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/terminology/ValueSet/epa-provenance-participant-type-vs" } }, { "id": "Provenance.agent.type.coding", "path": "Provenance.agent.type.coding", "min": 1, "max": "1", "mustSupport": true }, { "id": "Provenance.agent.type.coding.system", "path": "Provenance.agent.type.coding.system", "min": 1, "mustSupport": true }, { "id": "Provenance.agent.type.coding.version", "path": "Provenance.agent.type.coding.version", "min": 1, "mustSupport": true }, { "id": "Provenance.agent.type.coding.code", "path": "Provenance.agent.type.coding.code", "min": 1, "mustSupport": true }, { "id": "Provenance.agent.type.coding.display", "path": "Provenance.agent.type.coding.display", "min": 1, "mustSupport": true }, { "id": "Provenance.agent.role", "path": "Provenance.agent.role", "definition": "Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist." }, { "id": "Provenance.agent.who", "path": "Provenance.agent.who", "definition": "Hier wird die Person/Entität referenziert, die die Integration der Dokumentation in das Zielsystem durchführt.", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient", "http://hl7.org/fhir/StructureDefinition/Practitioner", "http://hl7.org/fhir/StructureDefinition/PractitionerRole", "http://hl7.org/fhir/StructureDefinition/RelatedPerson", "http://hl7.org/fhir/StructureDefinition/Organization" ] } ], "mustSupport": true }, { "id": "Provenance.agent.who.reference", "path": "Provenance.agent.who.reference", "mustSupport": true }, { "id": "Provenance.agent.who.identifier", "path": "Provenance.agent.who.identifier", "type": [ { "code": "Identifier", "profile": [ "http://fhir.de/StructureDefinition/identifier-kvid-10", "http://fhir.de/StructureDefinition/identifier-telematik-id" ] } ], "mustSupport": true }, { "id": "Provenance.entity", "path": "Provenance.entity", "definition": "Hier kann ein Dokument als Informationsquelle für die Information angegeben werden, die als Ziel der Herkunfts-Information referenziert ist.", "mustSupport": true }, { "id": "Provenance.entity.role", "path": "Provenance.entity.role", "definition": "Dieses Element beschreibt, wie die Information genutzt wird.", "patternCode": "source", "mustSupport": true }, { "id": "Provenance.entity.what", "path": "Provenance.entity.what", "definition": "Hier wird das Element referenziert, das als Quell-Element für die Information gedient hat.", "mustSupport": true }, { "id": "Provenance.entity.what.display", "path": "Provenance.entity.what.display", "definition": "Freitext der die Ursprungs-Information identifiziert. Beispielsweise \"Krankenhaus-Entlassbrief vom 25.01.24\".", "min": 1, "mustSupport": true }, { "id": "Provenance.entity.agent", "path": "Provenance.entity.agent", "definition": "Hier wird eine Person/Entität angegeben, die an der Dokumentation beteiligt ist.", "type": [ { "code": "BackboneElement" } ] }, { "id": "Provenance.entity.agent.type", "path": "Provenance.entity.agent.type", "definition": "Hier ist die Rolle/Funktion der Person/Entität anzugeben." }, { "id": "Provenance.entity.agent.role", "path": "Provenance.entity.agent.role", "definition": "Hier wird angegeben, in welcher Rolle die Person/Entität an der Integration der Dokumentation in das Zielsystem beteiligt ist." }, { "id": "Provenance.entity.agent.who", "path": "Provenance.entity.agent.who", "definition": "Hier wird die datenintegrierende Person referenziert." } ] } }
Informationsmodell als LogicalModel
Das Profil basiert auf folgendem Informationsmodell:
Herkunftsinformation (herkunftsinformation) | http://hl7.org/fhir/StructureDefinition/Base | ||
artDerAktivitaet | 1..1 | CodingBinding | |
zielReferenz | 1..* | BackboneElement | |
mioMedikationsplan | 0..1 | Reference() | |
arzneimittel | 0..1 | Reference() | |
allergieUnvertraeglichkeit | 0..1 | Reference() | |
allergienUnvertraeglichkeitenListe | 0..1 | Reference() | |
beobachtungenMessungenListe | 0..1 | Reference() | |
geschaetzterEntbindungstermin | 0..1 | Reference() | |
glomerulaereFiltrationsrateGfr | 0..1 | Reference() | |
koerpergewicht | 0..1 | Reference() | |
koerperlaengeKoerpergroesse | 0..1 | Reference() | |
medikationsInformation | 0..1 | Reference() | |
medikationsInformationenListe | 0..1 | Reference() | |
schwangerschaftsstatus | 0..1 | Reference() | |
kreatinin | 0..1 | Reference() | |
stillzeitstatus | 0..1 | Reference() | |
ursprungsInformation | 0..* | BackboneElement | |
artDerNutzung | 1..1 | CodingFixed Value | |
freitext | 1..1 | string | |
beteiligtePersonEntitaet | 1..* | BackboneElement | |
personEntitaetReferenz | 1..1 | BackboneElement | |
behandelndePersonVzdFhirDirectory | 0..1 | Reference() | |
behandelndePersonEinrichtung | 0..1 | Reference() | |
einrichtungVzdFhirDirectory | 0..1 | Reference() | |
patientInEpa | 0..1 | Reference() | |
kontaktperson | 0..1 | Reference() | |
artDerBeteiligung | 1..1 | CodingBinding | |
zeitpunktDerDurchgefuehrtenAktivitaet | 0..1 | dateTime |
Beispiele
{ "resourceType": "Provenance", "id": "8d34cc94-5d23-4ed0-b6a7-e1131f58804c", "meta": { "versionId": "1", "lastUpdated": "2024-01-01T00:00:00Z", "profile": [ "https://gematik.de/fhir/epa/StructureDefinition/epa-provenance" ] }, "recorded": "2024-01-01T00:00:00Z", "activity": { "coding": [ { "code": "CREATE", "system": "http://terminology.hl7.org/CodeSystem/v3-DataOperation" } ] }, "target": [ { "reference": "Observation/32668ee0-bf06-42ca-9577-c4abac3ede49" } ], "agent": [ { "type": { "coding": [ { "code": "enterer", "system": "http://terminology.hl7.org/CodeSystem/provenance-participant-type", "version": "4.0.1", "display": "Enterer" } ] }, "who": { "reference": "Practitioner/498c345f-31f5-4da6-9f04-00fa2bc8af7c" } }, { "type": { "coding": [ { "code": "performer", "system": "http://terminology.hl7.org/CodeSystem/provenance-participant-type", "version": "4.0.1", "display": "Performer" } ] }, "who": { "reference": "Organization/ad7dc0e7-cb44-4740-ba67-cb573e29d596" } } ] }
<Provenance xmlns="http://hl7.org/fhir"> <id value="8d34cc94-5d23-4ed0-b6a7-e1131f58804c" /> <meta> <versionId value="1" /> <lastUpdated value="2024-01-01T00:00:00Z" /> <profile value="https://gematik.de/fhir/epa/StructureDefinition/epa-provenance" /> </meta> <target> <reference value="Observation/32668ee0-bf06-42ca-9577-c4abac3ede49" /> </target> <recorded value="2024-01-01T00:00:00Z" /> <activity> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-DataOperation" /> <code value="CREATE" /> </coding> </activity> <agent> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/provenance-participant-type" /> <version value="4.0.1" /> <code value="enterer" /> <display value="Enterer" /> </coding> </type> <who> <reference value="Practitioner/498c345f-31f5-4da6-9f04-00fa2bc8af7c" /> </who> </agent> <agent> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/provenance-participant-type" /> <version value="4.0.1" /> <code value="performer" /> <display value="Performer" /> </coding> </type> <who> <reference value="Organization/ad7dc0e7-cb44-4740-ba67-cb573e29d596" /> </who> </agent> </Provenance>