This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

Security icon Work GroupMaturity Level: N/AStandards Status: InformativeSecurity Category: Not Classified Compartments: Device, Patient, Practitioner, RelatedPerson

Example NameidFormat
General Provenance Example - data extracted from CDA document from XDSexampleXMLJSONTurtle
Targeted Provenance Example - got the patients name from the patient directlyexample1XMLJSONTurtle
Targeted Provenance Example - got the patient nickname from his partnerexample2XMLJSONTurtle
Targeted Provenance Example - followUp note came from specified practitionerexample3XMLJSONTurtle
Provenance holding a signaturesignatureXMLJSONTurtle
Provenance with signature for a Consentconsent-signatureXMLJSONTurtle
MolecularSequence recorded by a Biocompute objectsexample-biocompute-objectXMLJSONTurtle
MolecularSequence for CWL workflow projectexample-cwlXMLJSONTurtle
Creation of a Consent from a Questionnaireexample-create-consentXMLJSONTurtle
Advanced Provenance of a create with all elements filled including patient, encounter, authorization, baseOn, and jpeg signatureexample-advancedXMLJSONTurtle
Provenance of a signature activity against a DiagnosticReport using an electronic signature (no evidence of signature, neither image or digital-signature)example-diagnosticreport-sigXMLJSONTurtle
Provenance of import of resources from a document (DocumentReference) to show provenance from resources back to the source document.example-importXMLJSONTurtle
Provenance of a delete of a codeSystem.example-deleteXMLJSONTurtle
Example of using Provenance as De-Identifiation linkage with security tag protection, enabling Re-Identification with authorization.example-anon0XMLJSONTurtle

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.