Release 4


Security Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Device, Patient, Practitioner, RelatedPerson

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

Provenance holding a signature (id = "signature")

<?xml version="1.0" encoding="UTF-8"?>

<Provenance xmlns="">
  <id value="signature"/> 
    <status value="generated"/> 
    <div xmlns="">procedure record authored on 27-June 2015 by Harold Hippocrates, MD Content extracted
       from Referral received 26-June</div> 
    where possible, provenance targets should be version specific,
    so that there is no ambiguity about which version of the 
    record this relates to
    <reference value="DocumentReference/example"/>     
  <recorded value="2015-08-27T08:39:24+10:00"/> 
      <system value=""/> 
      <code value="TREAT"/> 
      <display value="treatment"/> 
      <system value=""/> 
      <code value="AU"/> 
      <display value="authenticated"/> 

  <!--   signer = Harold Hippocrates   -->
        <system value=""/> 
        <code value="VERF"/> 

    <!--   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      -->
        <system value="urn:ietf:rfc:3986"/> 
        <value value="mailto://"/> 
    <!--   verification signature   -->
      <system value="urn:iso-astm:E1762-95:2013"/> 
      <code value="1.2.840.10065."/> 
      <display value="Verification Signature"/> 
    <when value="2015-08-27T08:39:24+10:00"/> 
      <reference value="Practitioner/xcda-author"/> 
    <targetFormat value="application/fhir+xml"/> 
    <sigFormat value="application/signature+xml"/> 
    <data value="Li4u"/> 

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.