Release 4B R5 Final QA

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-draft-final: Final QA Preview for R5 - STU see ballot notes ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Consent-example-notThis.xml

Example Consent/consent-example-notThis (XML)

Community Based Collaborative Care Work Group Maturity Level : N/A Standards Status : Informative Compartments : Patient

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

Jump past Narrative

Withhold or withdraw consent for disclosure of records related to specific domain (e.g. DI, LAB, etc.) (id = "consent-example-notThis")

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

<Consent xmlns="http://hl7.org/fhir">
  <id value="consent-example-notThis"/> 
  <text> 
    <status value="generated"/> 
    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.
    
  specific to use-case 2. Withhold or withdraw consent for disclosure of a specific record
         (e.g. Lab Order/Result) 
  
    Patient &quot;P. van de Heuvel&quot; Primary Care Provider, Dr. Philip Primary, has
         ordered a set of lab test which Adam 
   wishes to keep as private as possible.  At the sample collection facility, he indicates
         that he would 
   like withhold consent to disclose the order and all results associated with that specific
         order from 

    <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.
         
         Withhold or withdraw consent for disclosure of a specific record (e.g.
         Lab Order/Result) 
      </p> 
      <p> 

    Patient &quot;Donal D DUCK&quot;'s Primary Care Provider, Dr. Philip Primary,
         has ordered a set of lab test which Adam 
   wishes to keep as private as possible.  At the sample collection facility, he
         indicates that he would 
   like withhold consent to disclose the order and all results associated with
         that specific order from 

   all other providers  
   
   

      </p> 
    </div> 
  </text> 
  <status value="active"/> 
  
    
      
      
    
  



  <category> 
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="59284-0"/> 
    </coding> 
  </category> 
  
    
    
  
  
  
  <!--   I assume the example given is Canada Infoway wide???  AND I assume it is desired to
   state that in the Consent.authority element   -->
  
    
  
  
  
    
    
  
  
  
    

  <subject> 
    <reference value="Patient/f001"/> 
    <display value="P. van de Heuvel"/> 
  </subject> 
  <date value="2018-12-28"/> 
  <controller> 
    <reference value="Organization/f001"/> 
  </controller> 
  <sourceAttachment> 
    <title value="The terms of the consent in lawyer speak."/> 
      <!--   likely use url pointer to common text   -->
  </sourceAttachment> 

  <regulatoryBasis> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> 
      
    
  

      <code value="INFA"/> 
    </coding> 
  </regulatoryBasis> 
  <decision value="permit"/> 
    <!--   this is opt-in - e.g. everything approved unless otherwise stated   -->


  <provision> 
    <data> 
      <meaning value="related"/> 
      <reference> 
        

        <reference value="MedicationRequest/medrx0305"/> 
      </reference> 
    </data> 
  </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.