FHIR CI-Build

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

Example Contract/pcd-example-notAuthor (XML)

Financial Management Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Patient

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

Jump past Narrative

ConsentDirective Example (id = "pcd-example-notAuthor")

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

<Contract xmlns="http://hl7.org/fhir">
  <id value="pcd-example-notAuthor"/> 

  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">The following scenario is based on existing
      jurisdictional policy and are realized in existing systems in Canada. The
       default policy is
      one of implied consent for the provision of care, so these scenarios all
       deal with withdrawal
      or withholding consent for that purpose. In other jurisdictions, where an
       express consent
      model is used (Opt-In), these would examples would contain the phrase &quot;consent
       to&quot; rather than
      &quot;withhold&quot; or &quot;withdraw&quot; consent for. <p>  specific to use-case 5) Withhold or withdraw consent
        for disclosure of records that were authored by a specific organization
         (or service delivery
        location). </p> <p>  Patient &quot;P. van de Heuvel&quot; wishes to have all of the PHI collected at
         the
        Good Health Psychiatric Hospital restricted from disclosure to every provider.
         </p> 
    </div> 
  </text> 

  <issued value="2015-11-18"/> 
    <!--   not bound by a timeframe - Contract.applies   -->

  <subject> 
    <reference value="Patient/f001"/> 
    <display value="P. van de Heuvel"/> 
  </subject> 

  <authority> 
    <reference value="Organization/3"/> 
    <display value="Michigan Health"/> 
  </authority> 

    <!--   and/or would this [also] go into Contract.domain as a Jurisdiction?? (see the
   example on UK Pharamacy Juristiction)   -->
  <domain> 
    <reference value="Location/ukp"/> 
    <display value="UK Pharmacies"/> 
  </domain> 

  <type> 
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="57016-8"/> 
    </coding> 
  </type> 

    <!--   made up code-system to represent the set of privacy consent sub-types known and
   published by Canada Infoway   -->
  <subType> 
    <coding> 
      <system value="http://www.infoway-inforoute.ca.org/Consent-subtype-codes"/> 
      <code value="Opt-In"/> 
      <display value="Default Authorization with exceptions."/> 
    </coding> 
  </subType> 

  <term> 
    <type> 
      <coding> 
          <!--   made up code system   -->
        <system value="http://example.org/fhir/consent-term-type-codes"/> 
        <code value="withhold-authored-by"/> 
        <display value="Withhold all data authored by specified actor entity."/> 
      </coding> 
    </type> 
    <offer> 
      <topic> 
        <reference value="Organization/2.16.840.1.113883.19.5"/> 
        <display value="Good Health Clinic"/> 
      </topic> 

      <text value="Withhold all data authored by Good Health provider."/> 
    </offer> 
  </term> 

    <!--   the terms of the consent in friendly consumer speak   -->
  <friendly> 
    <contentAttachment> 
      <title value="The terms of the consent in friendly consumer speak."/> 
        <!--   likely use url pointer to common text   -->
    </contentAttachment> 
  </friendly> 

    <!--   the legal terms of the consent in lawyer speak   -->
  <legal> 
    <contentAttachment> 
      <title value="The terms of the consent in lawyer speak."/> 
        <!--   likely use url pointer to common text   -->
        <!--   I think some think that this should be the pointer to the law by which this consent
       is derived under. Such as http://lois-laws.justice.gc.ca/eng/acts/P-21/index.html
         -->
    </contentAttachment> 
  </legal> 
</Contract> 

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.