Provenance - FHIR v5.0.0

Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

6.3.7 Resource Provenance - Examples

Security

Work Group

Maturity Level: N/A

Standards Status: Informative

Security Category: Not Classified

Compartments: Device, Patient, Practitioner, RelatedPerson

Example Name	id	Format
General Provenance Example - data extracted from CDA document from XDS	example	XML	JSON	Turtle
Targeted Provenance Example - got the patients name from the patient directly	example1	XML	JSON	Turtle
Targeted Provenance Example - got the patient nickname from his partner	example2	XML	JSON	Turtle
Targeted Provenance Example - followUp note came from specified practitioner	example3	XML	JSON	Turtle
Provenance holding a signature	signature	XML	JSON	Turtle
Provenance with signature for a Consent	consent-signature	XML	JSON	Turtle
MolecularSequence recorded by a Biocompute objects	example-biocompute-object	XML	JSON	Turtle
MolecularSequence for CWL workflow project	example-cwl	XML	JSON	Turtle
Creation of a Consent from a Questionnaire	example-create-consent	XML	JSON	Turtle
Advanced Provenance of a create with all elements filled including patient, encounter, authorization, baseOn, and jpeg signature	example-advanced	XML	JSON	Turtle
Provenance of a signature activity against a DiagnosticReport using an electronic signature (no evidence of signature, neither image or digital-signature)	example-diagnosticreport-sig	XML	JSON	Turtle
Provenance of import of resources from a document (DocumentReference) to show provenance from resources back to the source document.	example-import	XML	JSON	Turtle
Provenance of a delete of a codeSystem.	example-delete	XML	JSON	Turtle
Example of using Provenance as De-Identifiation linkage with security tag protection, enabling Re-Identification with authorization.	example-anon0	XML	JSON	Turtle

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.