FHIR CI-Build

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

Example Permission/example-saner (XML)

Security Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

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

Jump past Narrative

Example of permission for SANER (id = "example-saner")

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

<!--  
        <p>
      Given the importance of current public health information, only the latest
 version of the report is
  authorized for access.
      </p>

  <rule>
    <type value="deny" />
    <data>
      <expression>
        <language value="text/fhirpath" />
        <expression value="meta.versionId.exists() and meta.versionId != 'latest'"
 />
      </expression>
    </data>
  </rule>
    --><Permission xmlns="http://hl7.org/fhir">
  <id value="example-saner"/> 
  <text> 
    <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">
      <p> 
        Read-Only access to a given SANER report is authorized for PurposeOfUse
         of Public-Health
        compliance, from the given Organization.
        Access requests authorized shall be recorded.
      </p> 
      <p> 
        Read-Only access to a given SANER report is authorized for PurposeOfUse
         of Public-Health
        compliance, from the given Group.
        Access requests authorized shall be recorded.
      </p> 
    </div> 
  </text> 
  <identifier> 
    <system value="http://example.org/identifiers"/> 
    <value value="saner-report"/> 
  </identifier> 
  <status value="active"/> 
  <asserter> 
    <reference value="Organization/f203"/> 
  </asserter> 
  <date value="2018-12-24"/> 
  <combining value="deny-overrides"/> 
  <rule> 
    <type value="permit"/> 
    <data> 
      <resource> 
        <meaning value="instance"/> 
        <reference> 
          <reference value="http://hl7.org/fhir/uv/saner/Measure/CDCHealthcareSupplyPathway"/> 
        </reference> 
      </resource> 
    </data> 
    <activity> 
      <actor> 
        <reference> 
          <reference value="Organization/f203"/> 
        </reference> 
      </actor> 
      <action> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/consentaction"/> 
          <code value="access"/> 
        </coding> 
      </action> 
      <purpose> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/v3-ActReason"/> 
          <code value="HCOMPL"/> 
        </coding> 
      </purpose> 
    </activity> 
    <limit> 
      <control> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> 
          <code value="AUDIT"/> 
        </coding> 
      </control> 
    </limit> 
  </rule> 
  <rule> 
    <type value="permit"/> 
    <data> 
      <resource> 
        <meaning value="instance"/> 
        <reference> 
          <reference value="http://hl7.org/fhir/uv/saner/Measure/CDCHealthcareSupplyPathway"/> 
        </reference> 
      </resource> 
    </data> 
    <activity> 
      <actor> 
        <reference> 
          <reference value="Group/102"/> 
        </reference> 
      </actor> 
      <action> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/consentaction"/> 
          <code value="access"/> 
        </coding> 
      </action> 
      <purpose> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/v3-ActReason"/> 
          <code value="HCOMPL"/> 
        </coding> 
      </purpose> 
    </activity> 
    <limit> 
      <control> 
        <coding> 
          <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> 
          <code value="AUDIT"/> 
        </coding> 
      </control> 
    </limit> 
  </rule> 
</Permission> 

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.