DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). 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: R4 R3 R2

V3-Compartment.xml

Raw XML (canonical form)

A named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note: This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk."

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-Compartment"/>
  <meta>
    <lastUpdated value="2015-10-24T07:41:03.495+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>Compartment</h2>
      <p> A named tag set for metadata used to populate a security category label field that &quot;segments&q
          uot; an IT resource per policy by indicating that access and use is restricted to members
           of a defined community or project. (HL7 Healthcare Privacy and Security Classification
           System)  Usage Note:
        <br/>This is the healthcare analog to the US Intelligence Community's concept of a Special
           Access Program.  Compartment codes may be used in as a field value in an initiator's clearance
           to indicate permission to access and use an IT Resource with a security label having the
           same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition
           of Compartment -  &quot;A division of data into isolated blocks with separate security
           controls for the purpose of reducing risk.&quot;
      </p>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include codes from 
          <a href="../../v3/ActCode/index.html">http://hl7.org/fhir/v3/ActCode</a> where concept  is-a  
          <a href="../../v3/ActCode/index.html#COMPT">COMPT</a>
        </li>
      </ul>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.1.11.20478"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/v3-Compartment"/>
  <version value="2014-03-26"/>
  <name value="Compartment"/>
  <status value="active"/>
  <experimental value="false"/>
  <publisher value="HL7 v3"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://www.hl7.org"/>
    </telecom>
  </contact>
  <description value=" A named tag set for metadata used to populate a security category label field that &quot;segments&q
    uot; an IT resource per policy by indicating that access and use is restricted to members
     of a defined community or project. (HL7 Healthcare Privacy and Security Classification
     System)  Usage Note: This is the healthcare analog to the US Intelligence Community's
     concept of a Special Access Program.  Compartment codes may be used in as a field value
     in an initiator's clearance to indicate permission to access and use an IT Resource with
     a security label having the same compartment value in security category label field. Map:
     Aligns with ISO 2382-8 definition of Compartment -  &quot;A division of data into isolated
     blocks with separate security controls for the purpose of reducing risk.&quot;"/>
  <compose>
    <include>
      <system value="http://hl7.org/fhir/v3/ActCode"/>
      <filter>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="COMPT"/>
      </filter>
    </include>
  </compose>
</ValueSet>

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.