Provenance (10)

#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.
2ConsentApproval-IEHRfhir.uv.crossborderdataexchange#currentR4
3DualSubmissionProvenancehl7.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
4HRex 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
5PACIO 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.
6PAO Provenancehl7.fhir.us.dme-orders#currentR4PAO Provenance Profile based on US Core
7PDex 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.
8Provenance-IEHRfhir.uv.crossborderdataexchange#currentR4
9U.S. Data Access Framework (DAF) Provenancehl7.fhir.us.daf#2.0.0R3
10US 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
Provenance I I S D
Provenance.meta
Provenance.implicitRules
Provenance.language
Provenance.text
Provenance.contained
Provenance.extension
Provenance.modifierExtension
Provenance.target C C C
Provenance.target.reference C
Provenance.occurred[x] C
Provenance.recorded C
Provenance.policy
Provenance.location
Provenance.authorization
Provenance.activity C
Provenance.basedOn
Provenance.patient
Provenance.encounter
Provenance.agent S C C C 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 C F D C F C F B M (2) F D (2) C F B M (3)
Provenance.agent.role C
Provenance.agent.who (3) C (2)
Provenance.agent.onBehalfOf
Provenance.entity C
Provenance.entity.extension S C (2)
Provenance.entity.extension.value[x] B M
Provenance.entity.modifierExtension
Provenance.entity.role F
Provenance.entity.what
Provenance.entity.agent
Provenance.signature C C
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