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

FHIR Data Segmentation for Privacy, published by HL7 Security Working Group. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-security-label-ds4p/ and changes regularly. See the Directory of published versions

ValueSet: Security Authorization Policy ValueSet

Official URL: http://hl7.org/fhir/uv/security-label-ds4p/ValueSet/valueset-security-authorization Version: 1.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: ValueSetSecurityAuthorizationPolicy

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.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActCode
    CodeDisplayDefinition
    AUTHPOLauthorization policyAuthorisation 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.

    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)
    ACCESSCONSCHEMEaccess control schemeAn access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies.

    *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.

    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.

    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 "service") 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)

    **Examples:**

    * Attribute Based Access Control (ABAC)
    * Discretionary Access Control (DAC)
    * History Based Access Control (HBAC)
    * Identity Based Access Control (IBAC)
    * Mandatory Access Control (MAC)
    * Organization Based Access Control (OrBAC)
    * Relationship Based Access Control (RelBac)
    * Responsibility Based Access Control (RespBAC)
    * Risk Adaptable Access Control (RAdAC)

    >
    DELEPOLdelegation policyDelegation 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.

    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.

    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)
    INFOACCESSaccess informationAuthorization to obtain information with no further permission to collect and store it.
    INFOCOLLECTcollect informationAuthorization to gather and store information.
    INFODEIDENTIFIYdeidentify informationAuthorization to alter or remove identifying characteristics of an entity or individual that is a subject of the information.
    INFODISCLOSEdisclose informationAuthorization to make information known to another party.
    INFOMASKmask informationAuthorization to alter information in order to conceal it from unauthorized recipients.
    INFOREADONLYread only informationAuthorization to access information within a specific context for communication purposes only. Storing, manipulating, and further disclosure are prohibited and may be technically disabled.
    INFOREDACTredact informationAuthorization to remove information that a recipient is not authorized to access.
    INFOREDISCLOSEredisclose informationAuthorization to make disclosed information known to another party.
    INFOREIDENTIFYreidentify informationAuthorization to alter or relink deidentified information so that an entity or individual that is the subject of that information identifiable.
    INFOUSEuse informationAuthorization to employ or alter information.

 

Expansion

This value set contains 13 concepts

Expansion based on ActCode v8.0.0 (CodeSystem)

CodeSystemDisplayDefinition
  AUTHPOLhttp://terminology.hl7.org/CodeSystem/v3-ActCodeauthorization policy

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.

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)

  ACCESSCONSCHEMEhttp://terminology.hl7.org/CodeSystem/v3-ActCodeaccess control scheme

An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies.

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.

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.

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 "service") 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)

Examples:

  • Attribute Based Access Control (ABAC)
  • Discretionary Access Control (DAC)
  • History Based Access Control (HBAC)
  • Identity Based Access Control (IBAC)
  • Mandatory Access Control (MAC)
  • Organization Based Access Control (OrBAC)
  • Relationship Based Access Control (RelBac)
  • Responsibility Based Access Control (RespBAC)
  • Risk Adaptable Access Control (RAdAC)
  DELEPOLhttp://terminology.hl7.org/CodeSystem/v3-ActCodedelegation policy

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.

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.

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)

  INFOACCESShttp://terminology.hl7.org/CodeSystem/v3-ActCodeaccess information

Authorization to obtain information with no further permission to collect and store it.

  INFOCOLLECThttp://terminology.hl7.org/CodeSystem/v3-ActCodecollect information

Authorization to gather and store information.

  INFODEIDENTIFIYhttp://terminology.hl7.org/CodeSystem/v3-ActCodedeidentify information

Authorization to alter or remove identifying characteristics of an entity or individual that is a subject of the information.

  INFODISCLOSEhttp://terminology.hl7.org/CodeSystem/v3-ActCodedisclose information

Authorization to make information known to another party.

  INFOMASKhttp://terminology.hl7.org/CodeSystem/v3-ActCodemask information

Authorization to alter information in order to conceal it from unauthorized recipients.

  INFOREADONLYhttp://terminology.hl7.org/CodeSystem/v3-ActCoderead only information

Authorization to access information within a specific context for communication purposes only. Storing, manipulating, and further disclosure are prohibited and may be technically disabled.

  INFOREDACThttp://terminology.hl7.org/CodeSystem/v3-ActCoderedact information

Authorization to remove information that a recipient is not authorized to access.

  INFOREDISCLOSEhttp://terminology.hl7.org/CodeSystem/v3-ActCoderedisclose information

Authorization to make disclosed information known to another party.

  INFOREIDENTIFYhttp://terminology.hl7.org/CodeSystem/v3-ActCodereidentify information

Authorization to alter or relink deidentified information so that an entity or individual that is the subject of that information identifiable.

  INFOUSEhttp://terminology.hl7.org/CodeSystem/v3-ActCodeuse information

Authorization to employ or alter information.


Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code