Provenance (24)

#NameSourceVerDescription
1ADI Provenancehl7.fhir.us.pacio-adi#currentR4Advance Directive Interoperability Provenance based on US Core to capture, search and fetch provenance information associated with advance directive interoperability data.
2AU Core Provenancehl7.fhir.au.core#currentR4This profile sets minimum expectations for an Provenance resource to record, search, and fetch basic encounter information for a patient. It is based on the core FHIR [Provenance](http://hl7.org/fhir/R4/provenance.html) resource and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the Provenance when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
3BeProvenancehl7.fhir.be.core#currentR4Belgian federal profile for a provenance. Note this profile does not introduce any changes from the base profile but has been created to mark its importance, specifically when FHIR is used in a non-document approach. General use case remarks: 'Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource.' (cfr. the HL7 base specifications) According to the FHIR specifications, the provenance resource SHALL only be provided when no other resource already plays this role: for a Patient it SHOULD be its managing organization, provenance of an Observation SHOULD be its performer, provenance of an AllergyIntolerance SHOULD be its recorder. 'Many other FHIR resources contain some elements that represent information about how the resource was obtained, and therefore they overlap with the functionality of the Provenance.' Special remarks for KMEHR users: The FHIR Provenance resource in general refers to an entity that had something to do with the creation or updating of something else. In a KMEHR context, this is somewhat different – as it is ‘XML document’ based, each KMEHR message has an 'author' element that is responsible.
4CL Provenancehl7.fhir.cl.corecl#currentR4Este Perfil describe la forma de validación respecto a la procedencia de un recurso genrado durante un acto clínico.
5CL Provenancehl7.fhir.cl.clcore#1.8.4R4Este Perfil describe la forma de validación respecto a la procedencia de un recurso genrado durante un acto clínico.
6ConsentApproval-IEHRfhir.uv.crossborderdataexchange#currentR4
7DualSubmissionProvenancehl7.fhir.us.spl#currentR4BA profile that links changes made to a FHIR system either via a converted SPL document or that are sent to a SPL system
8EHRS Functional Model - Record Lifecycle Events - Provenancehl7.fhir.uv.ehrs-rle#currentR5Defines the elements to be supported within the Provenance resource in order to conform with the Electronic Health Record System Functional Model Record Lifecycle Event standard
9FI Base Information Custodian (Individual Provider)hl7.fhir.fi.base#currentR4This is the Finnish base profile for the Provenance resource, used to communicate an individual practitioner as the custodian of information (*rekisterinpitäjä*).
10FI Base Information Custodian (Private Organization)hl7.fhir.fi.base#currentR4This is the Finnish base profile for the Provenance resource, used to communicate a private organization as the custodian of information (*rekisterinpitäjä*).
11FI Base Information Custodian (Public Organization)hl7.fhir.fi.base#currentR4This is the Finnish base profile for the Provenance resource, used to communicate a public organization as the custodian of information (*rekisterinpitäjä*).
12FI Base InformationCustodianhl7.fhir.fi.base#currentR4This is a Finnish abstract base profile for the Provenance resource, used to communicate the custodian of information (*rekisterinpitäjä*).
13FI Base Provenancehl7.fhir.fi.base#currentR4This is the Finnish base profile for the Provenance resource.
14HRex Provenance Profilehl7.fhir.us.davinci-hrex#currentR4Additional constraints on US Core Provenance to ensure it meets payer needs, including indicating when the event occurred and retaining signatures if present
15MedComMessagingProvenancemedcom.fhir.dk.messaging#currentR4Provenance information about the messages preceeding the current message
16mXDE Provenanceihe.iti.mxde#currentR4Provenance profile for use in mXDE when the data-elements (Resources pointed to by target) come from an XDS or MHD document. There will be one Provenance record for each document that has been decomposed by mXDE. - policy will be `urn:ihe:iti:mxde:2023:document-provenance-policy` to indicate mXDE produced provenance - target will point at ALL of the data found within the document - some target resources will be only found in the document - some target resources may have been found in other documents - activity will be `Derivation` to indicate the target resources were derived from documents - recorded will indicate when the document was decomposed into these target resources - agent will identify the software/service that implements the decomposition of the documents - this agent would be type `assembler` as it has assembled the FHIR Resources - this agent should describe the version of the software so as to understand data translation rules used - this agent may be a Resource or may be Contained depending on environment policy - other agent elements may be included - entity will point at the DocumentReference for the document from which the target data came
17PACIO ADI Provenancehl7.fhir.us.pacio-adi#currentR4Advance Directive Interoperability Provenance based on US Core to capture, search and fetch provenance information associated with advance directive interoperability data.
18PAO Provenancehl7.fhir.us.dme-orders#currentR4PAO Provenance Profile based on US Core
19PDex Provenancehl7.fhir.us.davinci-pdex#currentR4Provenance is provided by the payer to identify the source of the information, whether the data came via a clinical record or a claim record and whether the data was subject to manual transcription or other interpretive transformation. This profile adds PayerSourceFormat as an extension on the entity base element.
20Provenance - Dossier Farmaceuticohl7.fhir.it.dossierpharma#currentR4Profilo Provenance per Dossier Farmaceutico
21Provenance core BE profileehealthplatform.be.r4.federalprofiles#1.3.3-betaR4Belgian federal profile for a provenance. Note this profile does not introduce any changes from the base profile but has been created to mark its importance, specifically when FHIR is used in a non-document approach. General use case remarks: 'Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource.' (cfr. the HL7 base specifications) According to the FHIR specifications, the provenance resource SHALL only be provided when no other resource already plays this role: for a Patient it SHOULD be its managing organization, provenance of an Observation SHOULD be its performer, provenance of an AllergyIntolerance SHOULD be its recorder. 'Many other FHIR resources contain some elements that represent information about how the resource was obtained, and therefore they overlap with the functionality of the Provenance.' Special remarks for KMEHR users: The FHIR Provenance resource in general refers to an entity that had something to do with the creation or updating of something else. In a KMEHR context, this is somewhat different – as it is ‘XML document’ based, each KMEHR message has an 'author' element that is responsible.
22Provenance-IEHRfhir.uv.crossborderdataexchange#currentR4
23U.S. Data Access Framework (DAF) Provenancehl7.fhir.us.daf#2.0.0R3
24US Core Provenance Profilehl7.fhir.us.core#currentR4This profile sets minimum expectations for the Provenance resource to record, search, and fetch Provenance information associated with a record to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. This FHIR Provenance profile here covers the minimal (basic) information to support lineage of information. It provides the floor for standards development for specific use cases. Prior to reviewing this profile, implementers are encouraged to read the Basic Provenance guidance page which documents several key use cases, specifically, what organization was responsible for the most recent action on the resource.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Provenance I I S D
Provenance.meta
Provenance.implicitRules
Provenance.language
Provenance.text
Provenance.contained
Provenance.extension
Provenance.modifierExtension C
Provenance.target D D C C C C
Provenance.target.reference C D C D C
Provenance.occurred[x] C S C (2)
Provenance.recorded D D C
Provenance.policy C F
Provenance.location D D
Provenance.authorization
Provenance.activity D D C C D B M C F
Provenance.activity.coding C
Provenance.activity.coding.code B M B M C D
Provenance.basedOn
Provenance.patient
Provenance.encounter
Provenance.agent S C D D C C S C D (2) S C (2) S C S (3) S C D (3) C S C I D (3)
Provenance.agent.who[x] C
Provenance.agent.extension
Provenance.agent.modifierExtension
Provenance.agent.type C F D D C F D C F C F C F C F B M (2) F D (2) C F B M (3)
Provenance.agent.type.coding
Provenance.agent.type.coding.system B M B M
Provenance.agent.role C D C D C
Provenance.agent.role.coding
Provenance.agent.role.coding.code F F F
Provenance.agent.role.coding.system B M B M F D
Provenance.agent.who D D D (3) C (2)
Provenance.agent.who.identifier C
Provenance.agent.who.reference D D
Provenance.agent.onBehalfOf
Provenance.agent.onBehalfOf.identifier C
Provenance.agent.onBehalfOf.identifier.value C
Provenance.agent.onBehalfOf.identifier.system C F
Provenance.entity C S C D (5) D C C
Provenance.entity.extension S C (2)
Provenance.entity.extension.value[x] B M
Provenance.entity.modifierExtension
Provenance.entity.role F F (4) F F
Provenance.entity.what
Provenance.entity.what.reference D
Provenance.entity.what.identifier D
Provenance.entity.what.identifier.value C D
Provenance.entity.what.identifier.type F (2)
Provenance.entity.what.identifier.system C F D (4) C D
Provenance.entity.agent C
Provenance.signature C D C D C C
Provenance.signature.data C D C D
Provenance.signature.sigFormat D D
Provenance.signature.who D D
Provenance.signature.who.reference D D
Provenance.signature.when D D
Provenance.signature.type D B M D B M
Provenance.agent.who.identifier.type F F F
Provenance.agent.who.identifier.system F D F D F D
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023