This page is part of the FHIR Specification (v4.1.0: Release 4B Ballot #1). 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
Community Based Collaborative Care Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Patient |
Raw XML (canonical form + also see XML Format Specification)
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">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 "consent to" rather than "withhold" or "withdraw" 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 "P. van de Heuvel" wishes to have all of the PHI collected at the Good Health Psychiatric Hospital restricted from disclosure to every provider. </p> </div> </text> <status value="active"/> <scope> <coding> <system value="http://terminology.hl7.org/CodeSystem/consentscope"/> <code value="patient-privacy"/> </coding> </scope> <category> <coding> <system value="http://loinc.org"/> <code value="59284-0"/> </coding> </category> <patient> <reference value="Patient/f001"/> <display value="P. van de Heuvel"/> </patient> <dateTime value="2015-11-18"/> <!-- not bound by a timeframe - Consent.period --> <organization> <reference value="Organization/f001"/> </organization> <!-- 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 --> <policyRule> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> <code value="OPTIN"/> </coding> </policyRule> <provision> <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> </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.