HL7 Terminology (THO)
5.0.0 - Publication International flag

This page is part of the HL7 Terminology (v5.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: ObligationPolicy

Official URL: http://terminology.hl7.org/ValueSet/v3-ObligationPolicy Version: 2.0.0
Active as of 2014-03-26 Computable Name: ObligationPolicy
Other Identifiers: : urn:oid:2.16.840.1.113883.1.11.20445

Conveys the mandated workflow action that an information custodian, receiver, or user must perform.

Examples:

  • encrypt

Usage Note: Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.

References

Logical Definition (CLD)

 

Expansion

This value set contains 32 concepts

Expansion based on ActCode v7.0.0 (CodeSystem)

LevelCodeSystemDisplayDefinition
1  ObligationPolicyhttp://terminology.hl7.org/CodeSystem/v3-ActCodeobligation policy

Conveys the mandated workflow action that an information custodian, receiver, or user must perform.

Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.

2    ANONYhttp://terminology.hl7.org/CodeSystem/v3-ActCodeanonymize

Custodian system must remove any information that could result in identifying the information subject.

2    AODhttp://terminology.hl7.org/CodeSystem/v3-ActCodeaccounting of disclosure

Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested.

2    AUDIThttp://terminology.hl7.org/CodeSystem/v3-ActCodeaudit

Custodian system must monitor systems to ensure that all users are authorized to operate on information objects.

2    AUDTRhttp://terminology.hl7.org/CodeSystem/v3-ActCodeaudit trail

Custodian system must monitor and maintain retrievable log for each user and operation on information.

2    CPLYPOLhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with policy

Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.

Usage Note: CPLYPOL may be used as a security label code to inform senders and receivers of the tagged information to comply with applicable policy without specifying the specific policy type(s).

3      CPLYCChttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with confidentiality code

Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.

Usage Note: CPLYCC may be used as a security label code to inform senders and receivers of information tagged with a Confidentiality Code to comply with applicable level of protection required by the assigned confidentiality code.

3      CPLYCDhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with consent directive

Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.

Usage Note: CPLYCD may be used as a security label code to inform senders and receivers of information tagged with an ActCode_ActPolicyType_ActConsent code or an ActCode_ActPolicyType_ActPrivacyPolicy_ActConsentDirective code to comply with applicable consent directives.

3      CPLYCUIhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with controlled unclassified information policy

Custodian security system must retrieve, evaluate, and comply with applicable Controlled Unclassified Information (CUI) policies associated with the target information.

Usage Note: In the US, CPLYCUI may be used as a security label code to inform recipients of information designated by a US Federal Agency as Controlled Unclassified Information (CUI) to comply with the applicable laws, regulations, executive orders, and other guidances, such as included in DURSAs, to persist, mark, and enforce required CUI controls

Background:

In accordance with US 32 CFR Part 2002 and US Executive Order 13556 Controlled Unclassified Information, US Federal Agencies and their contractors are charged with classifying and marking certain information they create as Controlled Unclassified Information (CUI).

The following definitions, which are provided for context, are based on terms defined by the CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html

  • CUI is defined as "information in any form that the Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls."
  • Designating CUI occurs when an authorized holder, consistent with 32 CFR Part 2002 and the CUI Registry, determines that a specific item of information falls into a CUI category or subcategory.
  • The designating agency is the executive branch agency that designates or approves the designation of a specific item of information as CUI.
  • The authorized holder who designates the CUI must make recipients aware of the information's CUI status when disseminating that information.
  • • Disseminating occurs when authorized holders provide access, transmit, or transfer CUI to other authorized holders through any means, whether internal or external to the agency.

Once designated as CUI, US Federal Agencies and their contractors must assign CUI marks as prescribed by the National Archives and Records Administration (NARA) CUI Registry, and display marks as prescribed by the CUI Marking Handbook.

CUI markings must be displayed on hard copy, on containers, electronic media, and to end users for IT systems.

When HL7 content is designated as CUI, these computable markings can be interoperably conveyed using HL7 security label CUI tags, and may be included in HL7 text and narrative elements as human readable markings.

Impact of CUI markings:

CUI Custodians must enforce CUI security controls per applicable CUI policies. Federal agencies and their contractors must adhere to FISMA and NIST SP 800-53 security controls. Custodians, who are not Federal agencies or agency contractors, and are receivers of CUI, must adhere to NIST SP 800-171 security controls and those dictated by the Authorities indicated by the assigned CUI markings.

For most participants in US healthcare information exchange, including Federal Agencies and their contractors, additional controls are required by HIPAA Security standards for health information US 42 USC 1320d-2(d)(2) https://www.govinfo.gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf

Federal Agencies and their contractors may be the CUI classifier of original CUI content; or a CUI derivative classifier, which reclassifies CUI content that has been aggregated with other CUI or Unclassified Uncontrolled Information (U) or dissembled from a larger CUI content; or declassifiers, depending on the designating agency's policies.

Applicable CUI policies include the following and any future applicable updates to policies or laws related to CUI:

  • Executive Order 13556 https://www.federalregister.gov/articles/2010/11/09/2010-28360/controlled-unclassified-information
  • US 32 CFR Part 2002 https://www.govinfo.gov/content/pkg/CFR-2017-title32-vol6/pdf/CFR-2017-title32-vol6-part2002.pdf
  • NIST SP 800-171 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171r1.pdf
  • NIST SP 800-171A https://doi.org/10.6028/NIST.SP.800-171A
  • CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf
  • CUI Registry - Health Information Category https://www.archives.gov/cui/registry/category-detail/health-info
  • CUI Registry: Limited Dissemination Controls https://www.archives.gov/cui/registry/limited-dissemination
  • CUI Policy and Guidance https://www.archives.gov/cui/registry/policy-guidance
3      CPLYJPPhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with jurisdictional privacy policy

Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.

Usage Note: CPLYJPP may be used as a security label code to inform senders and receivers of information tagged with an ActCode_ActPolicyType_ActPrivacyPolicy_ActPrivacyLaw code or an ActCode_ActPolicyType_ActInformationPolicy.JurisIP code to comply with applicable jurisdictional privacy policy.

3      CPLYJSPhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with jurisdictional security policy

Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional security policies associated with the target information.

Usage Note: CPLYJSP may be used as a security label code to inform senders and receivers of information tagged with an ActCode_ActPolicyType.SecurityPolicy code to comply with applicable jurisdictional security policy.

3      CPLYOPPhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with organizational privacy policy

Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.

Usage Note: CPLYOPP may be used as a security label code to inform senders and receivers of information tagged with an ActCode_ActPolicyType_ActInformationPolicy.OrgIP code to comply with applicable organizational privacy policy.

3      CPLYOSPhttp://terminology.hl7.org/CodeSystem/v3-ActCodecomply with organizational security policy

Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.

Usage Note: CPLYOSP may be used as a security label code to inform senders and receivers of information tagged with an ActCode_ActPolicyType.SecurityPolicy code to comply with applicable organizational security policy.

2    DECLASSIFYLABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodedeclassify security label

Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.

2    DEIDhttp://terminology.hl7.org/CodeSystem/v3-ActCodedeidentify

Custodian system must strip information of data that would allow the identification of the source of the information or the information subject.

2    DELAUhttp://terminology.hl7.org/CodeSystem/v3-ActCodedelete after use

Custodian system must remove target information from access after use.

2    DOWNGRDLABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodedowngrade security label

Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.

2    DRIVLABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodederive security label

Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.

2    ENCRYPThttp://terminology.hl7.org/CodeSystem/v3-ActCodeencrypt

Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext.

Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.)

3      ENCRYPTRhttp://terminology.hl7.org/CodeSystem/v3-ActCodeencrypt at rest

Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.

3      ENCRYPTThttp://terminology.hl7.org/CodeSystem/v3-ActCodeencrypt in transit

Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.

3      ENCRYPTUhttp://terminology.hl7.org/CodeSystem/v3-ActCodeencrypt in use

Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user.

2    HUAPRVhttp://terminology.hl7.org/CodeSystem/v3-ActCodehuman approval

Custodian system must require human review and approval for permission requested.

2    LABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodeassign security label

Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.

Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes.

2    MASKhttp://terminology.hl7.org/CodeSystem/v3-ActCodemask

Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret".

2    MINEChttp://terminology.hl7.org/CodeSystem/v3-ActCodeminimum necessary

Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use.

Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use.

2    PERSISTLABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodepersist security label

Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.

2    PRIVMARKhttp://terminology.hl7.org/CodeSystem/v3-ActCodeprivacy mark

Custodian must create and/or maintain human readable security label tags as required by policy.

Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label."

3      CUIMarkhttp://terminology.hl7.org/CodeSystem/v3-ActCodeCUI Mark

An originator must mark, persist, display, and convey computable and renderable Controlled Unclassified Information (CUI) marks as required by policy. A recipient must consume, persist, display, and reconvey CUI marks on information received based on agreements with the originator..

Examples:

  • As CUI custodians, Federal Agencies and their contractors must mark, persist, display, and convey these marks.
  • All CUI receivers must consume, persist, display, and reconvey CUI markings on information further disclosed

Usage Note:

In accordance with US 32 CFR Part 2002 and US Executive Order 13556 Controlled Unclassified Information, US Federal Agencies and their contractors are charged with classifying and marking certain information they create as Controlled Unclassified Information (CUI).

The following definitions, which are provided for context, are based on terms defined by the CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html

  • CUI is defined as "information in any form that the Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls"
  • Designating CUI occurs when an authorized holder, consistent with US 32 CFR Part 2002 and the CUI Registry, determines that a specific item of information falls into a CUI category or subcategory.
  • The designating agency is the executive branch agency that designates or approves the designation of a specific item of information as CUI.
  • The authorized holder who designates the CUI must make recipients aware of the information’s CUI status when disseminating that information.
  • Disseminating occurs when authorized holders provide access, transmit, or transfer CUI to other authorized holders through any means, whether internal or external to the agency.

Once designated as CUI, US Federal Agencies and their contractors must assign CUI marks as prescribed by the National Archives and Records Administration (NARA) CUI Registry, and display marks as prescribed by the CUI Marking Handbook.

CUI markings must be displayed on hard copy, on containers, electronic media, and to end users for IT systems.

When HL7 content is designated as CUI, these computable markings can be interoperably conveyed using HL7 security label CUI tags, and may be included in HL7 text and narrative elements as human readable markings.

Impact of CUI markings:

CUI Custodians must enforce CUI security controls per applicable CUI policies. Federal agencies and their contractors must adhere to FISMA and NIST SP 800-53 security controls. Custodians, who are not Federal agencies or agency contractors, and are receivers of CUI, must adhere to NIST SP 800-171 security controls and those dictated by the Authorities indicated by the assigned CUI markings.

For most participants in US healthcare information exchange, including Federal Agencies and their contractors, additional controls are required by HIPAA Security standards for health information US 42 USC 1320d-2(d)(2) https://www.govinfo.gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf

Federal Agencies and their contractors may be the CUI classifier of original CUI content; or a CUI derivative classifier, which reclassifies CUI content that has been aggregated with other CUI or Unclassified Uncontrolled Information (U) or dissembled from a larger CUI content; or declassifiers, depending on the designating agency's policies.

Applicable CUI policies include the following and any future applicable updates to policies or laws related to CUI:

  • Executive Order 13556 https://www.federalregister.gov/articles/2010/11/09/2010-28360/controlled-unclassified-information
  • US 32 CFR Part 2002 https://www.govinfo.gov/content/pkg/CFR-2017-title32-vol6/pdf/CFR-2017-title32-vol6-part2002.pdf
  • NIST SP 800-171 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171r1.pdf
  • NIST SP 800-171A https://doi.org/10.6028/NIST.SP.800-171A
  • CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf
  • CUI Registry - Health Information Category https://www.archives.gov/cui/registry/category-detail/health-info
  • CUI Registry: Limited Dissemination Controls https://www.archives.gov/cui/registry/limited-dissemination
  • CUI Policy and Guidance https://www.archives.gov/cui/registry/policy-guidance
2    PSEUDhttp://terminology.hl7.org/CodeSystem/v3-ActCodepseudonymize

Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject.

2    REDACThttp://terminology.hl7.org/CodeSystem/v3-ActCoderedact

Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.

2    UPGRDLABELhttp://terminology.hl7.org/CodeSystem/v3-ActCodeupgrade security label

Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.


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

History

DateActionAuthorCustodianComment
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26