This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). 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.4.2.20444 HL7 v3 Value Set SecurityPolicy

Vocabulary

Work Group

Maturity Level: N/A

External

Use Context: Any

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

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-SecurityPolicy

Version:

2014-03-26

Name:

v3.SecurityPolicy

Title:

V3 Value SetSecurityPolicy

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.4.2.20444.1 Content Logical Definition

This value set includes codes from the following code systems:

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a SecurityPolicy

4.4.2.20444.2 Expansion

This expansion generated 19 Aug 2018

This value set contains 51 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-ActCode version 2018-08-12

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActCode

Lvl	Code	Display	Definition
0	SecurityPolicy	security policy	Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
1	AUTHPOL	authorization 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)
2	ACCESSCONSCHEME	access 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) >
1	DELEPOL	delegation 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)
1	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.
2	ANONY	anonymize	Custodian system must remove any information that could result in identifying the information subject.
2	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.
2	AUDIT	audit	Custodian system must monitor systems to ensure that all users are authorized to operate on information objects.
2	AUDTR	audit trail	Custodian system must monitor and maintain retrievable log for each user and operation on information.
2	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.
2	CPLYCD	comply with consent directive	Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
2	CPLYJPP	comply with jurisdictional privacy policy	Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
2	CPLYOPP	comply with organizational privacy policy	Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
2	CPLYOSP	comply with organizational security policy	Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
2	CPLYPOL	comply with policy	Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
2	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.
2	DEID	deidentify	Custodian system must strip information of data that would allow the identification of the source of the information or the information subject.
2	DELAU	delete after use	Custodian system must remove target information from access after use.
2	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.
2	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.
2	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.)
3	ENCRYPTR	encrypt at rest	Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
3	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.
3	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.
2	HUAPRV	human approval	Custodian system must require human review and approval for permission requested.
2	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.
2	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".
2	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.
2	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.
2	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."
2	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.
2	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.
2	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.
1	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.
2	NOAUTH	no disclosure without subject authorization	Prohibition on disclosure without information subject's authorization.
2	NOCOLLECT	no collection	Prohibition on collection or storage of the information.
2	NODSCLCD	no disclosure without consent directive	Prohibition on disclosure without organizational approved patient restriction.
2	NODSCLCDS	no disclosure without information subject's consent directive	Prohibition on disclosure without a consent directive from the information subject.
2	NOINTEGRATE	no integration	Prohibition on Integration into other records.
2	NOLIST	no unlisted entity disclosure	Prohibition on disclosure except to entities on specific access list.
2	NOMOU	no disclosure without MOU	Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
2	NOORGPOL	no disclosure without organizational authorization	Prohibition on disclosure without organizational authorization.
2	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).
2	NOPERSISTP	no collection beyond purpose of use	Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
2	NORDSCLCD	no redisclosure without consent directive	Prohibition on redisclosure without patient consent directive.
2	NORDSCLCDS	no redisclosure without information subject's consent directive	Prohibition on redisclosure without a consent directive from the information subject.
2	NORDSCLW	no disclosure without jurisdictional authorization	Prohibition on disclosure without authorization under jurisdictional law.
2	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.
2	NOREUSE	no reuse beyond purpose of use	Prohibition on use of the information beyond the purpose of use initially authorized.
2	NOVIP	no unauthorized VIP disclosure	Prohibition on disclosure except to principals with access permission to specific VIP information.
2	ORCON	no disclosure without originator authorization	Prohibition on disclosure except as permitted by the information originator.