HL7 Terminology
1.0.0 - Publication
HL7 Terminology
1.0.0 - Publication
This page is part of the HL7 Terminology (v1.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 
Summary
| Defining URL: | http://terminology.hl7.org/ValueSet/v3-ObligationPolicy |
| Version: | 2.0.0 |
| Name: | ObligationPolicy |
| Status: | Active |
| Title: | ObligationPolicy |
| Definition: | Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Examples:
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. |
| OID: | 2.16.840.1.113883.1.11.20445 (for OID based terminology systems) |
| Source Resource: | XML / JSON / Turtle |
References
http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a ObligationPolicy
This value set contains 29 concepts
Expansion based on ActCode v2.0.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ActCode
| Lvl | Code | Display | Definition |
| 0 | ObligationPolicy | obligation 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. |
| 1 | ANONY | anonymize | Custodian system must remove any information that could result in identifying the information subject. |
| 1 | AOD | accounting 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. |
| 1 | AUDIT | audit | Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. |
| 1 | AUDTR | audit trail | Custodian system must monitor and maintain retrievable log for each user and operation on information. |
| 1 | CPLYCC | comply 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. |
| 1 | CPLYCD | comply with consent directive | Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. |
| 1 | CPLYJPP | comply with jurisdictional privacy policy | Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. |
| 1 | CPLYOPP | comply with organizational privacy policy | Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. |
| 1 | CPLYOSP | comply with organizational security policy | Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. |
| 1 | CPLYPOL | comply with policy | Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. |
| 1 | DECLASSIFYLABEL | declassify 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. |
| 1 | DEID | deidentify | Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. |
| 1 | DELAU | delete after use | Custodian system must remove target information from access after use. |
| 1 | DOWNGRDLABEL | downgrade 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. |
| 1 | DRIVLABEL | derive 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. |
| 1 | ENCRYPT | encrypt | 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.) |
| 2 | ENCRYPTR | encrypt at rest | Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. |
| 2 | ENCRYPTT | encrypt 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. |
| 2 | ENCRYPTU | encrypt 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. |
| 1 | HUAPRV | human approval | Custodian system must require human review and approval for permission requested. |
| 1 | LABEL | assign 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. |
| 1 | MASK | mask | 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". |
| 1 | MINEC | minimum 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. |
| 1 | PERSISTLABEL | persist 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. |
| 1 | PRIVMARK | privacy 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." |
| 1 | PSEUD | pseudonymize | 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. |
| 1 | REDACT | redact | Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. |
| 1 | UPGRDLABEL | upgrade 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 |
| Source | 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
| Date | Action | Custodian | Author | Comment |
| 2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
| 2014-03-26 | revise | 2014T1_2014-03-26_001283 (RIM release ID) | Vocabulary (Woody Beeler) (no record of original request) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#1.0.0 based on FHIR 4.0.1. Generated 2020-05-09
Links: Table of Contents |
QA Report | Search
| Version History |
Propose a change