FHIR Release 3 (STU) CI-Build

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3 R2

6.3.10 Resource Provenance - Extensions & Profiles

Responsible Owner: Security icon Work Group Maturity Level Standards Status : N/A Informative Ballot Status Security Category : Informative Not Classified Compartments : Device , Group , Patient , Practitioner , RelatedPerson

This table lists profiles and extensions for the Provenance resource. For background information, see Profiling Resources and Extensibility . Additional profiles and resources extensions may be found in published Implementation Guides icon , or in the Conformance resource registry icon .

6.3.10.1 Profiles

Extensions that reference this resource: 6.3.10.3 Search Extensions
ehrsrle-provenance Profile Defines 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 for EHRS FM Record Lifecycle Event - Provenance 6.3.10.2 Extensions Description Context No Extensions defined for this resource
communicationrequest-relevantHistory ProvenanceRelevantHistory relevantHistory for CommunicationRequest HL7 Extensions

This profile is provided for guidance purposes only. There is no expectation that implementers must adhere to this profile. It is included in the specification to help implementers understand how they might use Provenance to satisfy the typical needs envisioned by the 'relevantHistory' elements found in various Event and Request resources.

This profile identifies the data elements most likely to be relevant to implementers who are using Provenance to convey the relevant history of a resource, as discussed in the request pattern . For the purposes of this profile, mustSupport should be interpreted as 'SHOULD be considered for population and SHOULD be understood by consumers.' Implementers are not obligated to handle all of these element and are not prohibited from also making use of additional data elements

Provenance Relevant History No Search Extensions defined for this resource