Sha256: d478899e6323bd720db5cb50076cb3146f947c69d06dac5859af929dc00fcc64
Contents?: true
Size: 1.8 KB
Versions: 4
Compression:
Stored size: 1.8 KB
Contents
<?xml version="1.0" encoding="UTF-8"?><Provenance xmlns="http://hl7.org/fhir">
<id value="signature"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">procedure record authored on 27-June 2015 by Harold Hippocrates, MD Content extracted from Referral received 26-June</div>
</text>
<!--
where possible, provenance targets should be version specific,
so that there is no ambiguity about which version of the
record this relates to
-->
<target>
<reference value="DocumentReference/example"/>
</target>
<recorded value="2015-08-27T08:39:24+10:00"/>
<reason>
<system value="http://hl7.org/fhir/v3/ActReason"/>
<code value="TREAT"/>
<display value="treatment"/>
</reason>
<activity>
<system value="http://hl7.org/fhir/v3/DocumentCompletion"/>
<code value="AU"/>
<display value="authenticated"/>
</activity>
<!-- signer = Harold Hippocrates -->
<agent>
<role>
<system value="http://hl7.org/fhir/provenance-participant-role"/>
<code value="verifier"/>
</role>
<!-- very often, the user won't have a known system - these aren't available
for security system log ons. But where you can define it, you should.
Most of the time the userId is fully qualfied such as an email address -->
<whoUri value="mailto://hhd@ssa.gov"/>
</agent>
<signature>
<!-- verification signature -->
<type>
<system value="http://hl7.org/fhir/valueset-signature-type"/>
<code value="1.2.840.10065.1.12.1.5"/>
<display value="Verification Signature"/>
</type>
<when value="2015-08-27T08:39:24+10:00"/>
<whoReference>
<reference value="Practitioner/xcda-author"/>
</whoReference>
<contentType value="application/signature+xml"/>
<blob value="Li4u"/>
</signature>
</Provenance>
Version data entries
4 entries across 4 versions & 1 rubygems