Snapshot 3: Connectathon 32 Base

This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.

Example Consent/consent-example-notAuthor (XML)

Community Based Collaborative Care Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Patient

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

Jump past Narrative

Withhold or withdraw consent for disclosure of records that were authored by a specific organization (or service delivery location). (id = "consent-example-notAuthor")

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

<Consent xmlns="http://hl7.org/fhir">
  <id value="consent-example-notAuthor"/> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> 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.
         
      This example is to 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 Burgers University Medical Center restricted from disclosure to every provider.</p> 
    </div> 
  </text> 
  <status value="active"/> 

  <category> 
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="59284-0"/> 
    </coding> 
  </category> 
  <subject> 
    <reference value="Patient/f001"/> 
    <display value="P. van de Heuvel"/> 
  </subject> 
  <date value="2015-11-18"/> 
  <controller> 
    <reference value="Organization/f001"/> 
  </controller> 
    <!--   the text terms of the consent in lawyer speak   -->
  <sourceAttachment> 
    <title value="The terms of the consent in lawyer speak."/> 
      <!--   likely use url pointer to common text   -->
  </sourceAttachment> 
    <!--   this is opt-in - e.g. everything approved unless otherwise stated   -->
  <regulatoryBasis> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> 
      <code value="INFA"/> 
    </coding> 
  </regulatoryBasis> 
  <provision> 
    <type value="permit"/> 
    <provision> 
      <type value="deny"/> 
      <actor> 
        <role> 
          <coding> 
            <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> 
            <code value="CST"/> 
          </coding> 
        </role> 
        <reference> 
          <reference value="Organization/f001"/> 
        </reference> 
      </actor> 
    </provision> 
  </provision> 
</Consent> 

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.