FHIR Data Segmentation for Privacy
1.0.0 - trial-use International flag

This page is part of the FHIR Data Segmentation for Privacy (v1.0.0: STU 1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: Security Authorization Policy ValueSet - XML Representation

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download



<ValueSet xmlns="http://hl7.org/fhir">
  <id value="valueset-security-authorization"/>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><ul><li>Include these codes as defined in <a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActCode</code></a><table class="none"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-AUTHPOL">AUTHPOL</a></td><td>authorization policy</td><td>Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system.<br/><br/>A positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions. (Based on PONDERS)</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-ACCESSCONSCHEME">ACCESSCONSCHEME</a></td><td>access control scheme</td><td>An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies.<br/><br/>*Usage Note:* Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service.<br/><br/>There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also.<br/><br/>An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these. An access control scheme is a component of an access control mechanism or &quot;service&quot;) along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a PDP). (Based on ISO/IEC 10181-3:1996)<br/><br/>**Examples:** <br/><br/> *  Attribute Based Access Control (ABAC)<br/> *  Discretionary Access Control (DAC)<br/> *  History Based Access Control (HBAC)<br/> *  Identity Based Access Control (IBAC)<br/> *  Mandatory Access Control (MAC)<br/> *  Organization Based Access Control (OrBAC)<br/> *  Relationship Based Access Control (RelBac)<br/> *  Responsibility Based Access Control (RespBAC)<br/> *  Risk Adaptable Access Control (RAdAC)<br/><br/>&gt;</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-DELEPOL">DELEPOL</a></td><td>delegation policy</td><td>Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated.<br/><br/>Delegation policies are aimed at subjects delegating rights to servers or third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden.<br/><br/>A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of delegation policy, positive and negative. (Based on PONDERS)</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOACCESS">INFOACCESS</a></td><td>access information</td><td>Authorization to obtain information with no further permission to collect and store it.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOCOLLECT">INFOCOLLECT</a></td><td>collect information</td><td>Authorization to gather and store information.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFODEIDENTIFIY">INFODEIDENTIFIY</a></td><td>deidentify information</td><td>Authorization to alter or remove identifying characteristics of an entity or individual that is a subject of the information.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFODISCLOSE">INFODISCLOSE</a></td><td>disclose information</td><td>Authorization to make information known to another party.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOMASK">INFOMASK</a></td><td>mask information</td><td>Authorization to alter information in order to conceal it from unauthorized recipients.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOREADONLY">INFOREADONLY</a></td><td>read only information</td><td>Authorization to access information within a specific context for communication purposes only. Storing, manipulating, and further disclosure are prohibited and may be technically disabled.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOREDACT">INFOREDACT</a></td><td>redact information</td><td>Authorization to remove information that a recipient is not authorized to access.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOREDISCLOSE">INFOREDISCLOSE</a></td><td>redisclose information</td><td>Authorization to make disclosed information known to another party.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOREIDENTIFY">INFOREIDENTIFY</a></td><td>reidentify information</td><td>Authorization to alter or relink deidentified information so that an entity or individual that is the subject of that information identifiable.</td></tr><tr><td><a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-ActCode.html#v3-ActCode-INFOUSE">INFOUSE</a></td><td>use information</td><td>Authorization to employ or alter information.</td></tr></table></li></ul></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="sec"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/security-label-ds4p/ValueSet/valueset-security-authorization"/>
  <version value="1.0.0"/>
  <name value="ValueSetSecurityAuthorizationPolicy"/>
  <title value="Security Authorization Policy ValueSet"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2020-03-30"/>
  <publisher value="HL7 Security Working Group"/>
  <contact>
    <name value="HL7 Security Working Group"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/secure/index.cfm"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="security-cc@lists.hl7.org"/>
    </telecom>
  </contact>
  <description
               value="Security label metadata that may be used to 'segment' an IT resource by conveying a displayed mark, required to be rendered to indicate that the electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <compose>
    <include>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/>
      <concept>
        <code value="AUTHPOL"/>
        <display value="authorization policy"/>
      </concept>
      <concept>
        <code value="ACCESSCONSCHEME"/>
        <display value="access control scheme"/>
      </concept>
      <concept>
        <code value="DELEPOL"/>
        <display value="delegation policy"/>
      </concept>
      <concept>
        <code value="INFOACCESS"/>
        <display value="access information"/>
      </concept>
      <concept>
        <code value="INFOCOLLECT"/>
        <display value="collect information"/>
      </concept>
      <concept>
        <code value="INFODEIDENTIFIY"/>
        <display value="deidentify information"/>
      </concept>
      <concept>
        <code value="INFODISCLOSE"/>
        <display value="disclose information"/>
      </concept>
      <concept>
        <code value="INFOMASK"/>
        <display value="mask information"/>
      </concept>
      <concept>
        <code value="INFOREADONLY"/>
        <display value="read only information"/>
      </concept>
      <concept>
        <code value="INFOREDACT"/>
        <display value="redact information"/>
      </concept>
      <concept>
        <code value="INFOREDISCLOSE"/>
        <display value="redisclose information"/>
      </concept>
      <concept>
        <code value="INFOREIDENTIFY"/>
        <display value="reidentify information"/>
      </concept>
      <concept>
        <code value="INFOUSE"/>
        <display value="use information"/>
      </concept>
    </include>
  </compose>
</ValueSet>