STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). 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

1.30.2.2.20445 HL7 v3 Value Set ObligationPolicy

This value set (http://hl7.org/fhir/ValueSet/v3-ObligationPolicy) is defined as part of HL7 v3. Related FHIR content: ObligationPolicy.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-ObligationPolicy
Name:ObligationPolicy
Definition: 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.
OID:2.16.840.1.113883.1.11.20445 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is not currently used

1.30.2.2.20445.1 Content Logical Definition

This value set includes codes from the following code systems:

 

1.30.2.2.20445.2 Expansion

This expansion generated 31 Mar 2016

This value set contains 23 concepts

All codes from system http://hl7.org/fhir/v3/ActCode

CodeDisplayDefinition
ObligationPolicyobligation policyConveys 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.
ANONYanonymizeCustodian system must remove any information that could result in identifying the information subject.
AODaccounting of disclosureCustodian 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.
AUDITauditCustodian system must monitor systems to ensure that all users are authorized to operate on information objects.
AUDTRaudit trailCustodian system must monitor and maintain retrievable log for each user and operation on information.
CPLYCCcomply with confidentiality codeCustodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.
CPLYCDcomply with consent directiveCustodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
CPLYJPPcomply with jurisdictional privacy policyCustodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
CPLYOPPcomply with organizational privacy policyCustodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
CPLYOSPcomply with organizational security policyCustodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
CPLYPOLcomply with policyCustodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
DEIDdeidentifyCustodian system must strip information of data that would allow the identification of the source of the information or the information subject.
DELAUdelete after useCustodian system must remove target information from access after use.
ENCRYPTencryptCustodian 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.)
ENCRYPTRencrypt at restCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
ENCRYPTTencrypt in transitCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.
ENCRYPTUencrypt in useCustodian 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.
HUAPRVhuman approvalCustodian system must require human review and approval for permission requested.
MASKmaskCustodian 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".
MINECminimum necessaryCustodian 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.
PRIVMARKprivacy markCustodian 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."
PSEUDpseudonymizeCustodian 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.
REDACTredactCustodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.

This value set includes codes from the following code systems: