HL7 Terminology (THO)
4.0.0 - Publication International flag

This page is part of the HL7 Terminology (v4.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: Confidentiality

Official URL: http://terminology.hl7.org/ValueSet/v2-0952 Version: 2.0.0
Active as of 2019-12-01 Responsible: HL7, Inc Computable Name: Confidentiality
Other Identifiers: : urn:oid:2.16.840.1.113883.1.11.10228

Copyright/Legal: Copyright HL7. Licensed under creative commons public domain

Concepts drawn from the HL7 V3 Confidentiality code system . Used in Version 2 messaging in the Security Classification elements in the Message Header segment (MSH) and the Access Restrictions segment (ARV).

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 17 concepts

Expansion based on Confidentiality v2.2.0 (CodeSystem)

LevelCodeSystemDisplayDefinition
1  _Confidentialityhttp://terminology.hl7.org/CodeSystem/v3-ConfidentialityConfidentiality

A specializable code and its leaf codes used in Confidentiality value sets to value the Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".

2    Lhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitylow

Privacy metadata indicating that a low level of protection is required to safeguard personal and healthcare information, which has been altered in such a way as to minimize the need for confidentiality protections with some residual risks associated with re-linking. The risk of harm to an individual's reputation and sense of privacy if disclosed without authorization is considered negligible, and mitigations are in place to address reidentification risk.

Usage Note:

The level of protection afforded anonymized and pseudonymized, and non-personally identifiable information (e.g., a limited data set) is dictated by privacy policies and data use agreements intended to engender trust that health information can be used and disclosed with little or no risk of re-identification.

Example: Personal and healthcare information, which excludes 16 designated categories of direct identifiers in a HIPAA Limited Data Set. This information may be disclosed by HIPAA Covered Entities without patient authorization for a research, public health, and operations purposes if conditions are met, which includes obtaining a signed data use agreement from the recipient. See 45 CFR Section 164.514.

This metadata indicates that the receiver may have an obligation to comply with a data use agreement with the discloser. The discloser may have obligations to comply with policies dictating the methods for de-identification.

Confidentiality code total order hierarchy: Low (L) is less protective than V, R, N, and M, and subsumes U.

2    Mhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitymoderate

Privacy metadata indicating the level of protection required to safeguard personal and healthcare information, which if disclosed without authorization, would present a moderate risk of harm to an individual's reputation and sense of privacy.

Usage Note: The level of protection afforded moderately confidential information is dictated by privacy policies intended to engender trust in a service provider. May include publicly available information in jurisdictions that restrict uses of that information without the consent of the data subject.

Privacy policies mandating moderate levels of protection, which preempt less protective privacy policies. "Moderate" confidentiality policies differ from and would be preempted by the prevailing privacy policies mandating the normative level of protection for information used in the delivery and management of healthcare.

Confidentiality code total order hierarchy: Moderate (M) is less protective than V, R, and N, and subsumes all other protection levels (i.e., L and U).

Examples: Includes personal and health information that an individual authorizes to be collected, accessed, used or disclosed to a bank for a health credit card or savings account; to health oversight authorities; to a hospital patient directory; to worker compensation, disability, property and casualty or life insurers; and to personal health record systems, consumer-controlled devices, social media accounts and online Apps; or for marketing purposes

2    Nhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitynormal

Privacy metadata indicating the level of protection required to safeguard personal and healthcare information, which if disclosed without authorization, would present a considerable risk of harm to an individual's reputation and sense of privacy.

Usage Note: The level of protection afforded normatively confidential information is dictated by the prevailing normative privacy policies, which are intended to engender patient trust in their healthcare providers.

Privacy policies mandating normative levels of protection, which preempt less protective privacy policies when the information is used in the delivery and management of healthcare. May be pre-empted by jurisdictional law (e.g., for public health reporting or emergency treatment).

Confidentiality code total order hierarchy: Normal (N) is less protective than V and R, and subsumes all other protection levels (i.e., M, L, and U).

**Map:**Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care when purpose of use is treatment: Default for normal clinical care access (i.e., most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.

Examples:

n the US, this includes what HIPAA identifies as protected health information (PHI) under 45 CFR Section 160.103.

2    Rhttp://terminology.hl7.org/CodeSystem/v3-Confidentialityrestricted

Privacy metadata indicating the level of protection required to safeguard potentially stigmatizing information, which if disclosed without authorization, would present a high risk of harm to an individual's reputation and sense of privacy.

Usage Note: The level of protection afforded restricted confidential information is dictated by specially protective organizational or jurisdictional privacy policies, including at an authorized individual’s request, intended to engender patient trust in providers of sensitive services.

Privacy policies mandating additional levels of protection by restricting information access preempt less protective privacy policies when the information is used in the delivery and management of healthcare. May be pre-empted by jurisdictional law (e.g., for public health reporting or emergency treatment).

Confidentiality code total order hierarchy: Restricted (R) is less protective than V, and subsumes all other protection levels (i.e., N, M, L, and U).

Examples:

Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient’s standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual (e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer).

2    Uhttp://terminology.hl7.org/CodeSystem/v3-Confidentialityunrestricted

Privacy metadata indicating that no level of protection is required to safeguard personal and healthcare information that has been disclosed by an authorized individual without restrictions on its use.

Examples: Includes publicly available information e.g., business name, phone, email and physical address.

Usage Note: The authorization to collect, access, use, and disclose this information may be stipulated in a contract of adhesion by a data user (e.g., via terms of service or data user privacy policies) in exchange for the data subject's use of a service.

This metadata indicates that the receiver has no obligation to consider privacy policies other than its own when making access control decisions.

This metadata indicates that the receiver has no obligation to consider privacy policies other than its own when making access control decisions.

Confidentiality code total order hierarchy: Unrestricted (U) is less protective than V, R, N, M, and L, and is the lowest protection levels.

2    Vhttp://terminology.hl7.org/CodeSystem/v3-Confidentialityvery restricted

Privacy metadata indicating the level of protection required under atypical cicumstances to safeguard potentially damaging or harmful information, which if disclosed without authorization, would (1) present an extremely high risk of harm to an individual's reputation, sense of privacy, and possibly safety; or (2) impact an individual's or organization's legal matters.

Usage Note: The level of protection afforded very restricted confidential information is dictated by specially protective privacy or legal policies intended to ensure that under atypical circumstances additional protections limit access to only those with a high 'need to know' and the information is kept in highest confidence..

Privacy and legal policies mandating the highest level of protection by stringently restricting information access, preempt less protective privacy policies when the information is used in the delivery and management of healthcare including legal proceedings related to healthcare. May be pre-empted by jurisdictional law (e.g., for public health reporting or emergency treatment but only under limited circumstances).

Confidentiality code total order hierarchy: Very Restricted (V) is the highest protection level and subsumes all other protection levels s (i.e., R, N, M, L, and UI).

Examples:

Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient. May also include information held under a legal hold or attorney-client privilege.

1  _ConfidentialityByAccessKindhttp://terminology.hl7.org/CodeSystem/v3-ConfidentialityConfidentialityByAccessKind

Description: By accessing subject / role and relationship based rights (These concepts are mutually exclusive, one and only one is required for a valid confidentiality coding.)

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

2    Bhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitybusiness

Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. However, no patient related information may ever be of this confidentiality level.

Deprecation Comment: Replced by ActCode.B

2    Dhttp://terminology.hl7.org/CodeSystem/v3-Confidentialityclinician

Description: Only clinicians may see this item, billing and administration persons can not access this item without special permission.

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

2    Ihttp://terminology.hl7.org/CodeSystem/v3-Confidentialityindividual

Description: Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor type code).

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

1  _ConfidentialityByInfoTypehttp://terminology.hl7.org/CodeSystem/v3-ConfidentialityConfidentialityByInfoType

Description: By information type, only for service catalog entries (multiples allowed). Not to be used with actual patient data!

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

2    ETHhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitysubstance abuse related

Description: Alcohol/drug-abuse related item

*Deprecation Comment:*Replced by ActCode.ETH

2    HIVhttp://terminology.hl7.org/CodeSystem/v3-ConfidentialityHIV related

Description: HIV and AIDS related item

*Deprecation Comment:*Replced by ActCode.HIV

2    PSYhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitypsychiatry relate

Description: Psychiatry related item

*Deprecation Comment:*Replced by ActCode.PSY

2    SDVhttp://terminology.hl7.org/CodeSystem/v3-Confidentialitysexual and domestic violence related

Description: Sexual assault / domestic violence related item

*Deprecation Comment:*Replced by ActCode.SDV

1  _ConfidentialityModifiershttp://terminology.hl7.org/CodeSystem/v3-ConfidentialityConfidentialityModifiers

Description: Modifiers of role based access rights (multiple allowed)

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

2    Chttp://terminology.hl7.org/CodeSystem/v3-Confidentialitycelebrity

Description: Celebrities are people of public interest (VIP) including employees, whose information require special protection.

*Deprecation Comment:*Replced by ActCode.CEL

2    Shttp://terminology.hl7.org/CodeSystem/v3-Confidentialitysensitive

Description:

Information for which the patient seeks heightened confidentiality. Sensitive information is not to be shared with family members. Information reported by the patient about family members is sensitive by default. Flag can be set or cleared on patient's request.

*Deprecation Comment:*Deprecated due to updated confidentiality codes under ActCode

2    Thttp://terminology.hl7.org/CodeSystem/v3-Confidentialitytaboo

Description: Information not to be disclosed or discussed with patient except through physician assigned to patient in this case. This is usually a temporary constraint only, example use is a new fatal diagnosis or finding, such as malignancy or HIV.

*Deprecation Note:*Replced by ActCode.TBOO


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

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.