STU3 Candidate

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

4.3.2.20444 HL7 v3 Value Set SecurityPolicy

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

Summary

Defining URL: http://hl7.org/fhir/ValueSet/v3-SecurityPolicy
Name: SecurityPolicy
Definition: Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive
OID: 2.16.840.1.113883.1.11.20444 (for OID based terminology systems)
Source Resource XML / JSON

This value set is not currently used

4.3.2.20444.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.2.20444.2 Expansion

This expansion generated 06 Dec 2016

This value set contains 48 concepts

Expansion based on http://hl7.org/fhir/v3/ActCode version 2016-11-11

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

Code Display Definition
SecurityPolicy security policy Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
   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.
     ANONY anonymize Custodian system must remove any information that could result in identifying the information subject.
     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.
     AUDIT audit Custodian system must monitor systems to ensure that all users are authorized to operate on information objects.
     AUDTR audit trail Custodian system must monitor and maintain retrievable log for each user and operation on information.
     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.
     CPLYCD comply with consent directive Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
     CPLYJPP comply with jurisdictional privacy policy Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
     CPLYOPP comply with organizational privacy policy Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
     CPLYOSP comply with organizational security policy Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
     CPLYPOL comply with policy Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
     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.
     DEID deidentify Custodian system must strip information of data that would allow the identification of the source of the information or the information subject.
     DELAU delete after use Custodian system must remove target information from access after use.
     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.
     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.
     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.)
       ENCRYPTR encrypt at rest Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
       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.
       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.
     HUAPRV human approval Custodian system must require human review and approval for permission requested.
     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.
     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".
     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.
     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.
     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."
     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.
     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.
     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.
   RefrainPolicy refrain policy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc.
     NOAUTH no disclosure without subject authorization Prohibition on disclosure without information subject's authorization.
     NOCOLLECT no collection Prohibition on collection or storage of the information.
     NODSCLCD no disclosure without consent directive Prohibition on disclosure without organizational approved patient restriction.
     NODSCLCDS no disclosure without information subject's consent directive Prohibition on disclosure without a consent directive from the information subject.
     NOINTEGRATE no integration Prohibition on Integration into other records.
     NOLIST no unlisted entity disclosure Prohibition on disclosure except to entities on specific access list.
     NOMOU no disclosure without MOU Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
     NOORGPOL no disclosure without organizational authorization Prohibition on disclosure without organizational authorization.
     NOPAT no disclosure to patient, family or caregivers without attending provider's authorization Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone).
     NOPERSISTP no collection beyond purpose of use Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
     NORDSCLCD no redisclosure without consent directive Prohibition on redisclosure without patient consent directive.
     NORDSCLCDS no redisclosure without information subject's consent directive Prohibition on redisclosure without a consent directive from the information subject.
     NORDSCLW no disclosure without jurisdictional authorization Prohibition on disclosure without authorization under jurisdictional law.
     NORELINK no relinking Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked.
     NOREUSE no reuse beyond purpose of use Prohibition on use of the information beyond the purpose of use initially authorized.
     NOVIP no unauthorized VIP disclosure Prohibition on disclosure except to principals with access permission to specific VIP information.
     ORCON no disclosure without originator authorization Prohibition on disclosure except as permitted by the information originator.