This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

• Content
• Examples Detailed Descriptions
• Detailed Descriptions Search Params
• Mappings
• Examples
• Operations
• Profiles & Extensions
• R3 Conversions Extensions

6.3 Resource Provenance - Content

Responsible Owner: Security Work Group

Maturity Level : 3   Trial Use Normative

Security Category : Not Classified

Compartments : Device , Group , Patient , Practitioner , RelatedPerson

Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may MAY impact security, privacy, and trust policies.

This resource is referenced by

6.3.4 References to this Resource

• Implements: Event
• Resource References: Contract , DeviceRequest , MedicationAdministration , MedicationDispense , MedicationRequest , ... Show 2 more , ServiceRequest and Task
• Extension References: Event history and Relevant history

6.3.4 6.3.5 Resource Content

 

See the Profiles & Extensions and the alternate Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis

6.3.4.1 6.3.5.1 Terminology Bindings

Provenance.reason Provenance.agent.role

Path	Definition ValueSet	Type	Reference Documentation
Provenance.authorization	The reason the activity took place. PurposeOfUse	Extensible Example	v3.PurposeOfUse Supports communication of purpose of use at a general level.
Provenance.activity	The activity that took place. ProvenanceActivityType	Extensible Example	ProvenanceActivityType code systems are: v3-DocumentCompletion Provenance.agent.type The type of participation that a provenance agent played with respect to the activity. v3-DataOperation v3-ActCode Extensible ISO Lifecycle FHIR RESTful interactions W3C PROV Activity Types ProvenanceParticipantType
Provenance.agent.type	ParticipationRoleType	Example	The This FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role that a provenance elements. The codes are intended to express how the agent played with respect participated in some activity. Sometimes refered to the agent functional-role relative to the activity.
Provenance.agent.role	SecurityRoleTypeExamples (a valid code from Example Codes for Security Structural Role )	Example	SecurityRoleType This value set contains example structural roles. In general, two types of roles can be distinguished: structural roles and functional roles. Structural Roles reflect human or organizational categories (hierarchies), and describe prerequisites, feasibilities, or competences for actions. Functional roles are bound to the realization or performance of actions.
Provenance.entity.role	ProvenanceEntityRole	Required	How an entity was used in an activity.

6.3.5.2 Constraints

6.3.4.2 6.3.5.3 Using the Provenance Resource

The Provenance resource identifies information about another resource (the reference target element). The Provenance resource may MAY be used in several different ways:

• As part of a document bundle Bundle where it identifies the provenance of part or all of the document resources in the Bundle (e.g. Documents )
• On a RESTful system where it keeps track of provenance information relating to resources

When used The resources found in a document bundle, the references Bundle are often not explicitly versioned, but they always implicitly pertain to the latest version of and don't have a version identified , yet Provenance resources in the Bundle MAY have references (e.g. .target) to version specific resources. When de-referencing resource references that MAY have a version identified one SHOULD look for the non-version resource found in the document. Bundle.

On a RESTful system, the target resource reference should SHOULD be version specific, but this requires special care: For new resources that need to have a corresponding Provenance resource, the version-specific reference is often not knowable until after the target resource has been updated. This can create an integrity problem for the system - what if the Provenance resource cannot be created after the target resource has been updated? To avoid any such integrity problems, the target resource and the Provenance resources should SHOULD be submitted as a pair using a transaction (see the Transaction Example ). Alternatively, the Provenance http header MAY be used if supported.

6.3.5.3.1 Element Level Provenance

The Provenance.target MAY point at a specific element within the targeted resource using the target element extension or target path extension . For example when updating a Patient resource with a new official name, such as shown in example 1 , where the Provenance is indicating that the official name was provided by the Patient themselves.

6.3.4.2.1 6.3.5.3.2 HTTP Header

The custom header X-Provenance to provide a provenance resource when performing PUT or POST operations using the RESTful interface :

POST [base]/Observation
Content-Type: application/fhir+?
X-Provenance: { "resourceType": "Provenance", "location": { "reference": "Location/1" }," agent" ... }

[body]

The intent is that the server picks up the provenance, fills out the target , and then stores the provenance information as it normally would. Notes:

• Irrespective of the Content-Type or Accept headers, the Provenance resource is in the JSON format
• The provenance SHALL not NOT have a specified Provenance.target . The server will fill the target in as it processes the contents of the POST/PUT and determines the ids of the resource(s) to which the interaction applies
• Servers MAY ignore the header, but SHOULD process it if they support provenance
• Some server frameworks impose a length limit on individual HTTP headers, or on the the headers as a whole. Servers MAY reject a request if the X-Provenance header is too long
• The use of the header is not documented for other HTTP methods (GET etc) etc.)
• When recording an AuditEvent, one AuditEvent MAY be used to record the create of the resource and provenance

6.3.4.3 6.3.5.4 Signatures

The Provenance resource includes a signature element (digital signature) which can be used for standards based integrity verification and non-repudiation purposes. The Signature datatype provides details on use of the signature element. The Signature.type coded value of "Source" should SHOULD be used when the signature is for simply proving that the resource content is the same as it was when the resource was updated or created.

6.3.4.4 6.3.5.5 Provenance of Removal

A Provenance record can be recorded to indicate who deleted a Resource. If versioning is supported, the version that was deleted is referenced in Provenance.target; if versioning is not supported then Provenance.target contains the non-version reference. Provenance.entity is not used unless there is a business requirement to do so.

6.3.4.5

6.3.5.6 Use of Provenance to record Import and Transform

Provenance can be used to record activities of an automaton that transforms input. Such as middleware that extracts information from a HL7 v2 V2 message and creates FHIR resources, or middleware that extracts information from an HL7 CDA document and creates FHIR resources, etc. The Provenance in these cases is recording the activity of the middleware.

The middleware in this case would, in addition to creating the target resources, create a Provenance resource that indicates all the target resources (using Provenance.target). Provenance.target ). The middleware is identified as one of the Provenance.agent elements, with the Provenance.agent.role Provenance.agent.type of assembler. assembler .

The middleware may MAY record the source as another Provenance.agent element.

The original content is optionally saved. This might be as a DocumentReference, or Binary. The Provenance.entity would then point at this original content.

The original source might include some form of 'provenance' to cover the history of the original content prior to the import transformation. This original source 'provenance' should SHOULD be converted into FHIR Provenance records as appropriate.

Examples of this activity with Provenance profile can be found in the IHE Implementation Guides for

• Query for Existing Data for Mobile - QEDm
• Reconciliation of Clinical Content and Care Providers - RECON

6.3.5.7 Multiple Patients Affected

Where a provenance activity impacts more than one Patient/Subject; multiple Provenance resources SHOULD be recorded, one for each Patient/Subject. This best enables segmentation of the Provenance details so as to limit the Privacy impact. The use of multiple Provenance is a best-practice and SHOULD be driven by a Policy. There will be cases where the use of multiple Provenance resources is not necessary, such as public health reporting.

6.3.5.8 Relevant History Provenance

Some Event pattern or Request pattern resources will have a relevantHistory element. These elements would point to a subset of all Provenance about that resource that are considered relevant. For further guidance on relevantHistory see Event history pattern or Request history pattern.

6.3.5 6.3.6 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name	Type	Description	Expression	In Common
activity	token	Activity that occurred	Provenance.activity
agent	reference	Who participated	Provenance.agent.who ( Practitioner , Group , Organization , CareTeam , Device , Patient , HealthcareService , PractitionerRole , RelatedPerson )
agent-role	token	What the agents role was	Provenance.agent.role
agent-type	token	How the agent participated	Provenance.agent.type
based-on	reference	Reference to the service request.	Provenance.basedOn (Any)
encounter	reference	Encounter related to the Provenance	Provenance.encounter ( Encounter )	27 Resources
entity	reference	Identity of entity	Provenance.entity.what (Any)
location	reference	Where the activity occurred, if relevant	Provenance.location ( Location )
patient	reference	Target Reference(s) (usually version specific) Where the activity involved patient data	Provenance.target.where(resolve() is Patient) Provenance.patient ( Patient )	61 Resources
recorded	date	When the activity was recorded / updated	Provenance.recorded
signature-type	token	Indication of the reason the entity signed the object(s)	Provenance.signature.type
target	reference	Target Reference(s) (usually version specific)	Provenance.target (Any)
when	date	When the activity occurred	(Provenance.occurred as dateTime) (Provenance.occurred.ofType(dateTime))