Generated Narrative: ValueSet R5-v3-SecurityCategoryObservationValue-for-R4B This value set expansion contains 300 concepts. Code System Display Definition ICOL http://terminology.hl7.org/CodeSystem/v3-ActCode information collection Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated. IDSCL http://terminology.hl7.org/CodeSystem/v3-ActCode information disclosure Definition: Consent to have collected healthcare information disclosed. INFA http://terminology.hl7.org/CodeSystem/v3-ActCode information access Definition: Consent to access healthcare information. INFAO http://terminology.hl7.org/CodeSystem/v3-ActCode access only Definition: Consent to access or "read" only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way. This level ensures that data which is masked or to which access is restricted will not be. Example: Opened and then emailed or screen printed for use outside of the consent directive purpose. INFASO http://terminology.hl7.org/CodeSystem/v3-ActCode access and save only Definition: Consent to access and save only, which entails that access to the saved copy will remain locked. IRDSCL http://terminology.hl7.org/CodeSystem/v3-ActCode information redisclosure Definition: Information re-disclosed without the patient's consent. RESEARCH http://terminology.hl7.org/CodeSystem/v3-ActCode research information access Definition: Consent to have healthcare information in an electronic health record accessed for research purposes. RSDID http://terminology.hl7.org/CodeSystem/v3-ActCode de-identified information access Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. RSREID http://terminology.hl7.org/CodeSystem/v3-ActCode re-identifiable information access Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. Example:: Where there is a need to inform the subject of potential health issues. EMRGONLY http://terminology.hl7.org/CodeSystem/v3-ActCode emergency only Privacy consent directive restricting or prohibiting access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for all purposes except for emergency treatment generally, which may include treatment during a disaster, a threat, in an emergency department and for break the glass purposes of use as specified by applicable domain policy. Usage Note: To specify the scope of an "EMRGONLY" consent directive within a policy domain, use one or more of the following Purpose of Use codes in the ActReason code system OID: 2.16.840.1.113883.5.8. ETREAT (Emergency Treatment): To perform one or more operations on information for provision of immediately needed health care for an emergent condition. BTG (break the glass): To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access. ERTREAT (emergency room treatment): To perform one or more operations on information for provision of immediately needed health care for an emergent condition in an emergency room or similar emergent care context by end users provisioned for this purpose, which does not constitute as policy override such as in a "Break the Glass" purpose of use. THREAT (threat): To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. DISASTER (disaster): To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone. Map: An "emergency only" consent directive maps to ISO/TS 17975:2015(E) 5.13 Exceptional access GRANTORCHOICE http://terminology.hl7.org/CodeSystem/v3-ActCode grantor choice A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions. Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms. Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered "basic consent". If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered "granular consent". Examples: Healthcare: A PHR account holder [grantor] may require any PHR user [grantee] to accept the terms of agreement in full, or may permit a PHR user to extend or restrict terms selected by the account holder or requested by the PHR user. Non-healthcare: The owner of a resource server [grantor] may require any authorization server [grantee] to meet authorization requirements stipulated in the grantor's terms of agreement. IMPLIED http://terminology.hl7.org/CodeSystem/v3-ActCode implied consent A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee. Comment: Implied or "implicit" consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms. Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered "basic consent". Examples: Healthcare: A patient schedules an appointment with a provider, and either does not take the opportunity to expressly assent or dissent to the provider's consent directive, does not have an opportunity to do so, as in the case where emergency care is required, or simply behaves as though the patient [grantor] agrees to the rights granted to the provider [grantee] in an implicit consent directive. An injured and unconscious patient is deemed to have assented to emergency treatment by those permitted to do so under jurisdictional laws, e.g., Good Samaritan laws. Non-healthcare: Upon receiving a driver's license, the driver is deemed to have assented without explicitly consenting to undergoing field sobriety tests. A corporation that does business in a foreign nation is deemed to have deemed to have assented without explicitly consenting to abide by that nation's laws. IMPLIEDD http://terminology.hl7.org/CodeSystem/v3-ActCode implied consent with opportunity to dissent A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent. Usage Note: Implied or "implicit" consent with an "opportunity to dissent" occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered "granular consent". Examples: Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of health information to family members and friends, but offers an opportunity or permits the patient to dissent to such disclosures. A health information exchanges deems a patient to have assented to disclosure of health information for treatment purposes, but offers the patient an opportunity to dissents to disclosure to particular provider organizations. Non-healthcare Examples: A bank deems a banking customer's assent to specified collection, access, use, or disclosure of financial information as a requirement of holding a bank account, but provides the user an opportunity to limit third-party collection, access, use or disclosure of that information for marketing purposes. NOCONSENT http://terminology.hl7.org/CodeSystem/v3-ActCode no consent No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement. Comment: A "No Consent" policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures. Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge. Examples: Healthcare: Without notification or an opportunity to assent or dissent, a patient's health information is automatically included in and available (often according to certain rules) through a health information exchange. Note that this differs from implied consent, where the patient is assumed to have consented. Without notification or an opportunity to assent or dissent, a patient's health information is collected, accessed, used, or disclosed for research, public health, security, fraud prevention, court order, or law enforcement. Non-healthcare: Without notification or an opportunity to assent or dissent, a consumer's healthcare or non-healthcare internet searches are aggregated for secondary uses such as behavioral tracking and profiling. Without notification or an opportunity to assent or dissent, a consumer's location and activities in a shopping mall are tracked by RFID tags on purchased items. NOPP http://terminology.hl7.org/CodeSystem/v3-ActCode notice of privacy practices An implied privacy consent directive or notification, which the data subject may or may not acknowledge. The notification specifies permitted actions, which may include access, use, or disclosure of any and all personal information. The notification specifies the scope of personal information, which may include de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, that may be used to identify an individual in a registry or repository. The notification specifies the purposes for which personal information may be used such as treatment, payment, operations, research, information exchange, public health, disaster, quality and safety reporting; as required by law including court order, law enforcement, national security, military authorities; and for data analytics, marketing, and profiling. Usage Notes: Map: An "implied" consent directive maps to ISO/TS 17975:2015(E) definition forImplied: Consent to Collect, Use and Disclose personal health information is implied by the actions or inactions of the individual and the circumstances under which it was implied". OPTIN http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". Examples: Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies. Non-healthcare: An employee [grantor] signs an employer's [grantee's] non-disclosure and non-compete agreement. OPTINR http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in with restrictions A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms. Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent. Usage Note: Opt-in with restrictions is considered "granular consent" because the grantor has an opportunity to narrow the permissions sought by the grantee. Examples: Healthcare: A patient assent to grantee's consent directive terms for collection, access, use, or disclosure of health information, and dissents to disclosure to certain recipients as allowed by the provider's pre-approved restriction list. Non-Healthcare: A cell phone user assents to the cell phone's privacy practices and terms of use, but dissents from location tracking by turning off the cell phone's tracking capability. OPTOUT http://terminology.hl7.org/CodeSystem/v3-ActCode op-out A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms. Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered "basic consent". Examples: Healthcare: A patient [grantor] declines to sign a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, revocation policies, and consequences of not assenting. Non-healthcare: An employee [grantor] refuses to sign an employer's [grantee's] agreement not to join unions or participate in a strike where state law protects employee's collective bargaining rights. A citizen [grantor] refuses to enroll in mandatory government [grantee] health insurance based on religious beliefs, which is an exemption. OPTOUTE http://terminology.hl7.org/CodeSystem/v3-ActCode opt-out with exceptions A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms. Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms. Usage Note: Opt-out with exceptions is considered a "granular consent" because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms. Examples: Healthcare: A patient [grantor] dissents to a health information exchange consent directive with the exception of disclosure based on a limited "time to live" shared secret [e.g., a token or password], which the patient can give to a provider when seeking care. Non-healthcare: A social media user [grantor] dissents from public access to their account, but assents to access to a circle of friends. GDPRCONSENT http://terminology.hl7.org/CodeSystem/v3-ActCode GDPR Consent Processing of personal data, inclusive of the special categories of data, is lawful only if the data subject has given explicit consent to the processing of his or her personal data, inclusive of the special categories of data, for one or more specific purposes, except where Union or Member State law provide that the prohibition to use the data may not be lifted by the data subject; and for personal data which are manifestly made public by the data subject. Usage Note: The description is based on the following GDPR provisions: Article 6.1.a https://gdpr-info.eu/art-6-gdpr/ 1Processing shall be lawful only if and to the extent that at least one of the following applies: (a) the data subject has given consent to the processing of his or her personal data for one or more specific purposes. Article 9.1, 9.2a., 9.2.e https://gdpr-info.eu/art-9-gdpr/ 1. Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation shall be prohibited. 2. Paragraph 1 shall not apply if one of the following applies: (a) the data subject has given explicit consent to the processing of those personal data for one or more specified purposes, except where Union or Member State law provide that the prohibition referred to in paragraph 1 may not be lifted by the data subject; and (e) processing relates to personal data which are manifestly made public by the data subject. _ActUSPrivacyLaw http://terminology.hl7.org/CodeSystem/v3-ActCode _ActUSPrivacyLaw Definition: A jurisdictional mandate in the U.S. relating to privacy. Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1. 42CFRPart2 http://terminology.hl7.org/CodeSystem/v3-ActCode 42 CFR Part2 A code representing 42 CFR Part 2 Confidentiality of Substance Use Disorder Patient Records. 42 CFR Part 2 stipulates the privacy rights of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program, which includes non-disclosure of health information relating to health care paid for by a federally assisted substance use disorder program without patient consent. https://www.gpo.gov/fdsys/pkg/CFR-2010-title42-vol1/pdf/CFR-2010-title42-vol1-part2.pdf Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, the collection, access, use, and disclosure of healthcare information is governed by 42 CFR Part 2 Confidentiality of Substance Use Disorder Patient Records https://www.gpo.gov/fdsys/pkg/CFR-2010-title42-vol1/pdf/CFR-2010-title42-vol1-part2.pdf use "42CFRPart2" as the security label policy code. Since information governed by a 42 CFR Part 2 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf assign the HL7 Confidentiality code "R" (restricted). CommonRule http://terminology.hl7.org/CodeSystem/v3-ActCode Common Rule A code representing U.S. Federal laws governing research-related privacy policies known as the "Common Rule". The Common Rule is the U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46), which has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements. Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information or biospecimen is governed by the Common Rule use "COMMONRULE" as the security label policy code. Information or biospecimen disclosed under the Common Rule are not protected by the HIPAA Privacy Rule. If protected under other laws such as confidentiality provisions under the Common Rule, assign the HL7 Confidentiality code "M" (moderate). HIPAAAuth http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Authorization for Disclosure A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508) Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which stipulates the process by which a covered entity seeks agreement from an individual to use or disclose protected health information for other purposes, or to authorize another covered entity to disclose protected health information to the requesting covered entity, are termed "authorizations". An "authorization" is required by the Privacy Rule for uses and disclosures of protected health information not otherwise allowed by the Rule. Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization. An authorization is a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual. An authorization must specify a number of elements, including a description of the protected health information to be used and disclosed, the person authorized to make the use or disclosure, the person to whom the covered entity may make the disclosure, an expiration date, and, in some cases, the purpose for which the information may be used or disclosed. With limited exceptions, covered entities may not condition treatment or coverage on the individual providing an authorization. https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, where use or disclosure of healthcare information is governed by a covered entity's HIPAA Authorization for Disclosure, use "HIPAAAuth" as the security label policy code. Information disclosed under a HIPAA Authorization for Disclosure no longer has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is considered the "norm", assign the HL7 Confidentiality code "M" (moderate), which may be protected under other laws such as the Federal Trade Commission privacy and security regulations. HIPAAConsent http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Consent A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.522), which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent". The Privacy Rule permits, but does not require, a covered entity to voluntarily obtain patient consent for uses and disclosures of protected health information for treatment, payment, and health care operations. Covered entities that do so have complete discretion to design a process that best suits their needs. From https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html. The provisions relating to consent are largely contained in Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf. Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by 45 CFR Section 164.522 use 'HIPAAConsent' as the security label policy code. Since information governed by a 45 CFR Section 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code 'R' (restricted). HIPAANOPP http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA notice of privacy practices A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.520), which stipulates an individual's right to adequate notice of the uses and disclosures of protected health information that may be made by the covered entity, and of the individual's rights and the covered entity's legal duties with respect to protected health information. Relevant HIPAA Privacy Rule provisions are at Section 164.520 (a) Standard: Notice of privacy practices. https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-520.pdf Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, if collection, access, use, or disclosure of healthcare information is governed by a covered entity's HIPAA Notice of Privacy Practices, use "HIPAANOPP" as the security label policy code. Information governed under a HIPAA Notice of Privacy Practices has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf , which is considered the "norm", assign the HL7 Confidentiality code "N" (normal). HIPAAPsyNotes http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA psychotherapy notes A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508), which stipulates the privacy rights of an individual who is the subject of psychotherapy notes, and requires authorization for certain uses and disclosure of that information. Definition of Psychotherapy notes 45 CFR Section 164.501 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-501.pdf: Psychotherapy notes means notes recorded (in any medium) by a health care provider who is a mental health professional documenting or analyzing the contents of conversation during a private counseling session or a group, joint, or family counseling session and that are separated from the rest of the individual's medical record. Psychotherapy notes excludes medication prescription and monitoring, counseling session start and stop times, the modalities and frequencies of treatment furnished, results of clinical tests, and any summary of the following items: Diagnosis, functional status, the treatment plan, symptoms, prognosis, and progress to date. See Section 164.508 Uses and disclosures for which an authorization is required. (2)Authorization required: Psychotherapy notes https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf: Notwithstanding any provision of this subpart, other than the transition provisions in Section 164.532, a covered entity must obtain an authorization for any use or disclosure of psychotherapy notes, except: (i) To carry out the following treatment, payment, or health care operations: (A) Use by the originator of the psychotherapy notes for treatment; (B) Use or disclosure by the covered entity for its own training programs in which students, trainees, or practitioners in mental health learn under supervision to practice or improve their skills in group, joint, family, or individual counseling; or (C) Use or disclosure by the covered entity to defend itself in a legal action or other proceeding brought by the individual; and (ii) A use or disclosure that is required by Section 164.502(a)(2)(ii) or permitted by Section 164.512(a); Section 164.512(d) with respect to the oversight of the originator of the psychotherapy notes; Section 164.512(g)(1); Section 164.512(j)(1)(i). Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, the collection, access, use, or disclosure of healthcare information is governed by HIPAA 45 CFR 164.508 (2) Authorization required: Psychotherapy notes https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf , use "HIPAAPsyNotes" as the security label policy code. Since information governed by a HIPAA 45 CFR 164.508 (2) has a level of confidentiality protection that is more stringent than the normal level of protection under 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted). HIPAAROA http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Right of Access A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.524 Access of individuals to protected health information https://www.govinfo.gov/app/details/CFR-2017-title45-vol1/CFR-2017-title45-vol1-sec164-524, which stipulates that an individual has a right of access to inspect and obtain a copy of protected health information about the individual in a designated record set, for as long as the protected health information is maintained in the designated record set with exceptions stipulated in HIPAA Privacy Rule Section 164.524. Exceptions include psychotherapy notes and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding. If an individual's request for access directs the covered entity to transmit the copy of protected health information directly to another person designated by the individual, the covered entity must provide the copy to the person designated by the individual. The individual's request must be in writing, signed by the individual, and clearly identify the designated person and where to send the copy of protected health information. For discussion on extent of right, grounds for denial, and documentation requirements see: HHS Individuals' Right under HIPAA to Access their Health Information 45 CFR Section 164.524 https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html and HHS FAQ on Right of Access vs. HIPAA Authorization https://www.hhs.gov/hipaa/for-professionals/faq/2041/why-depend-on-the-individuals-right/index.html Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed under 45 CFR Section 164.5224 use "HIPAAROA" as the security label policy code. Information disclosed under a HIPAA 42 CFR Section 164.524 no longer has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is considered the "norm", assign the HL7 Confidentiality code "M" (moderate), which may be protected under other laws such as the Federal Trade Commission privacy and security regulations. HIPAASelfPay http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA self-pay A code representing 45 CFR 164.522 Rights to request privacy protection for protected health information, which is a US Federal law stipulating the privacy rights of an individual to restrict disclosure of information related to health care items or services for which the individual pays out of pocket in full to a health plan or payer. See 45 CFR 164.522 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf. (vi) A covered entity must agree to the request of an individual to restrict disclosure of protected health information about the individual to a health plan if: (A) The disclosure is for the purpose of carrying out payment or health care operations and is not otherwise required by law; and (B) The protected health information pertains solely to a health care item or service for which the individual, or person other than the health plan on behalf of the individual, has paid the covered entity in full. Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, the collection, access, use, or disclosure of healthcare information is governed by HIPAA 45 CFR 164.522 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf use "HIPAASelfPay" as the security label policy code. Since information governed by a HIPAA 45 CFR 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted). Title38Section7332 http://terminology.hl7.org/CodeSystem/v3-ActCode Title 38 Section 7332 A code representing Title 38 Section 7332, which is a US Federal law stipulating the privacy rights of veterans diagnosed and treated for substance use disorders, infection with the human immunodeficiency virus, or sickle cell anemia. https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-partV-chap73-subchapIII-sec7332/content-detail.html . (1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b). (2) Paragraph (1) prohibits the disclosure to any person or entity other than the patient or subject concerned of the fact that a special written consent is required in order for such records to be disclosed. (b) (1) The content of any record referred to in subsection (a) may be disclosed by the Secretary in accordance with the prior written consent of the patient or subject with respect to whom such record is maintained, but only to such extent, under such circumstances, and for such purposes as may be allowed in regulations prescribed by the Secretary. (2) Whether or not any patient or subject, with respect to whom any given record referred to in subsection (a) is maintained, gives written consent, the content of such record may be disclosed by the Secretary as follows: (A) To medical personnel to the extent necessary to meet a bona fide medical emergency. (B) To qualified personnel for the purpose of conducting scientific research, management audits, financial audits, or program evaluation, but such personnel may not identify, directly or indirectly, any individual patient or subject in any report of such research, audit, or evaluation, or otherwise disclose patient or subject identities in any manner. (C) (i) In the case of any record which is maintained in connection with the performance of any program or activity relating to infection with the human immunodeficiency virus, to a Federal, State, or local public-health authority charged under Federal or State law with the protection of the public health, and to which Federal or State law requires disclosure of such record, if a qualified representative of such authority has made a written request that such record be provided as required pursuant to such law for a purpose authorized by such law. (ii) A person to whom a record is disclosed under this paragraph may not redisclose or use such record for a purpose other than that for which the disclosure was made. (D) If authorized by an appropriate order of a court of competent jurisdiction granted after application showing good cause therefor. In assessing good cause the court shall weigh the public interest and the need for disclosure against the injury to the patient or subject, to the physician-patient relationship, and to the treatment services. Upon the granting of such order, the court, in determining the extent to which any disclosure of all or any part of any record is necessary, shall impose appropriate safeguards against unauthorized disclosure. (E) To an entity described in paragraph (1)(B) of section 5701(k) of this title, but only to the extent authorized by such section. (F) (i) To a representative of a patient who lacks decision-making capacity, when a practitioner deems the content of the given record necessary for that representative to make an informed decision regarding the patient's treatment. (ii) In this subparagraph, the term "representative" means an individual, organization, or other body authorized under section 7331 of this title and its implementing regulations to give informed consent on behalf of a patient who lacks decision-making capacity. (G) To a State controlled substance monitoring program, including a program approved by the Secretary of Health and Human Services under section 399O of the Public Health Service Act (42 U.S.C. 280g-3), to the extent necessary to prevent misuse and diversion of prescription medicines. (H) (i) To a non-Department entity (including private entities and other Federal agencies) for purposes of providing health care, including hospital care, medical services, and extended care services, to Veterans or performing other health care-related activities or functions. (ii) An entity to which a record is disclosed under this subparagraph may not disclose or use such record for a purpose other than that for which the disclosure was made or as permitted by law. (I) To a third party in order to recover or collect reasonable charges for care furnished to, or paid on behalf of, a Veteran in connection with a non-service connected disability as permitted by section 1729 of this title or for a condition for which recovery is authorized or with respect to which the United States is deemed to be a third party beneficiary under the Act entitled 'An Act to provide for the recovery from tortiously liable third persons of the cost of hospital and medical care and treatment furnished by the United States' (Public Law 87-693; 42 U.S.C. 2651 et seq.; commonly known as the 'Federal Medical Care Recovery Act'). Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by 38 U.S. Code Section 7332 - Confidentiality of certain medical records https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-partV-chap73-subchapIII-sec7332/content-detail.html use "Title38Section7332" as the security label policy code. Since information governed by a Title 38 Section 7332 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted). a) HIPAAConsent http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Consent Code retired in December 2019 and replaced by code HIPAAConsent. Originally entered with copy/paste error in code value. A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.522), which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent." The Privacy Rule permits, but does not require, a covered entity to voluntarily obtain patient consent for uses and disclosures of protected health information for treatment, payment, and health care operations. Covered entities that do so have complete discretion to design a process that best suits their needs. From https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html. The provisions relating to consent are largely contained in Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf. Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by 45 CFR Section 164.522 use "HIPAAConsent" as the security label policy code. Since information governed by a 45 CFR Section 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted). ETH http://terminology.hl7.org/CodeSystem/v3-ActCode substance abuse information sensitivity Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. GDIS http://terminology.hl7.org/CodeSystem/v3-ActCode genetic disease information sensitivity Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. HIV http://terminology.hl7.org/CodeSystem/v3-ActCode HIV/AIDS information sensitivity Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. MST http://terminology.hl7.org/CodeSystem/v3-ActCode military sexual trauma information sensitivity Policy for handling information related to sexual assault or repeated, threatening sexual harassment that occurred while the patient was in the military, which is afforded heightened confidentiality. Access control concerns for military sexual trauma is based on the patient being subject to control by a higher ranking military perpetrator and/or censure by others within the military unit. Due to the relatively unfettered access to healthcare information by higher ranking military personnel and those who have command over the patient, there is a need to sequester this information outside of the typical controls on access to military health records. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. PREGNANT http://terminology.hl7.org/CodeSystem/v3-ActCode pregnancy information sensitivity Policy for handling information about an individual's current or past pregnancy status, deemed sensitive by the individual or by policy, which may be afforded heightened confidentiality. Usage Note: Information about a patient's current or past pregnancy status may be considered sensitive in circumstances in which that status could result in discrimination or stigmatization. SCA http://terminology.hl7.org/CodeSystem/v3-ActCode sickle cell anemia information sensitivity Policy for handling sickle cell disease information, which is afforded heightened confidentiality. Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then the Act valued with this ActCode should be associated with an Act valued with any applicable laws from the ActPrivacyLaw code system. SDV http://terminology.hl7.org/CodeSystem/v3-ActCode sexual assault, abuse, or domestic violence information sensitivity Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive. SDV code covers violence perpetrated by related and non-related persons. This code should be specific to physical and mental trauma caused by a related person only. The access control concerns are keeping the patient safe from the perpetrator who may have an abusive psychological control over the patient, may be stalking the patient, or may try to manipulate care givers into allowing the perpetrator to make contact with the patient. The definition needs to be clarified. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. SEX http://terminology.hl7.org/CodeSystem/v3-ActCode sexuality and reproductive health information sensitivity Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. SPI http://terminology.hl7.org/CodeSystem/v3-ActCode specially protected information sensitivity Policy for handling information deemed specially protected by law or policy including substance abuse, substance use, psychiatric, mental health, behavioral health, and cognitive disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. BH http://terminology.hl7.org/CodeSystem/v3-ActCode behavioral health information sensitivity Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. COGN http://terminology.hl7.org/CodeSystem/v3-ActCode cognitive disability information sensitivity Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. Examples may include dementia, traumatic brain injury, attention deficit, hearing and visual disability such as dyslexia and other disorders and related conditions which impair learning and self-sufficiency. However, the cognitive disabilities to which this term may apply versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. DVD http://terminology.hl7.org/CodeSystem/v3-ActCode developmental disability information sensitivity Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. A diverse group of chronic conditions that are due to mental or physical impairments impacting activities of daily living, self-care, language acuity, learning, mobility, independent living and economic self-sufficiency. Examples may include Down syndrome and Autism spectrum. However, the developmental disabilities to which this term applies versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. EMOTDIS http://terminology.hl7.org/CodeSystem/v3-ActCode emotional disturbance information sensitivity Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. Typical used to characterize behavioral and mental health issues of adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term. MH http://terminology.hl7.org/CodeSystem/v3-ActCode mental health information sensitivity Policy for handling information related to psychological disorders, which is afforded heightened confidentiality. Mental health information may be deemed specifically sensitive and distinct from physical health, substance use disorders, and behavioral disabilities and disorders in some jurisdictions. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. PSY http://terminology.hl7.org/CodeSystem/v3-ActCode psychiatry disorder information sensitivity Policy for handling psychiatry psychiatric disorder information, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. PSYTHPN http://terminology.hl7.org/CodeSystem/v3-ActCode psychotherapy note information sensitivity Policy for handling psychotherapy note information, which is afforded heightened confidentiality. Usage Note: In some jurisdiction, disclosure of psychotherapy notes requires patient consent. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. SUD http://terminology.hl7.org/CodeSystem/v3-ActCode substance use disorder information sensitivity Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. ETHUD http://terminology.hl7.org/CodeSystem/v3-ActCode alcohol use disorder information sensitivity Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. OPIOIDUD http://terminology.hl7.org/CodeSystem/v3-ActCode opioid use disorder information sensitivity Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. STD http://terminology.hl7.org/CodeSystem/v3-ActCode sexually transmitted disease information sensitivity Policy for handling sexually transmitted disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. TBOO http://terminology.hl7.org/CodeSystem/v3-ActCode taboo Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. Open Issue: This definition conflates a rule and a characteristic, and there may be a similar issue with ts sibling codes. VIO http://terminology.hl7.org/CodeSystem/v3-ActCode violence information sensitivity Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person. Access control concerns for information about mental or physical harm resulting from violence caused by an unrelated person may include manipulation of care givers or access to records that enable the perpetrator contact or locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. IDS http://terminology.hl7.org/CodeSystem/v3-ActCode Identifier Sensitivity Policy for handling information related to an identifier of an information subject, which will be afforded heightened confidentiality. Usage Note: Such policies may govern the sensitivity of information related to an identifier of an act, such as the identifier of a contract; a role, such as a citizen, a patient, a practitioner, or an organization; or an entity such as a medical device due to potential impact on the privacy, well-being, safety or integrity of an information subject. For example, protection against identity fraud or counterfeit. SICKLE http://terminology.hl7.org/CodeSystem/v3-ActCode sickle cell Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. DEMO http://terminology.hl7.org/CodeSystem/v3-ActCode all demographic information sensitivity Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. DOB http://terminology.hl7.org/CodeSystem/v3-ActCode date of birth information sensitivity Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. GENDER http://terminology.hl7.org/CodeSystem/v3-ActCode gender and sexual orientation information sensitivity Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. LIVARG http://terminology.hl7.org/CodeSystem/v3-ActCode living arrangement information sensitivity Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. MARST http://terminology.hl7.org/CodeSystem/v3-ActCode marital status information sensitivity Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. PATLOC http://terminology.hl7.org/CodeSystem/v3-ActCode patient location Policy for handling information related to an individual's location, which is deemed sensitive when the disclosure could impact the privacy, well-being, or safety of that subject, and requires additional protection. Usage Note: If there is a jurisdictional, organizational, or individual mandate, then use the applicable ActPrivacyLaw or ActConsentDirective code from the ActCode system to and specify the law in addition to this more generic code. RACE http://terminology.hl7.org/CodeSystem/v3-ActCode race information sensitivity Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. REL http://terminology.hl7.org/CodeSystem/v3-ActCode religion information sensitivity Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. B http://terminology.hl7.org/CodeSystem/v3-ActCode business information sensitivity Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality. 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. Usage Notes: No patient related information may ever be of this confidentiality level. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. EMPL http://terminology.hl7.org/CodeSystem/v3-ActCode employer information sensitivity Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee. Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. LOCIS http://terminology.hl7.org/CodeSystem/v3-ActCode location information sensitivity Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. SSP http://terminology.hl7.org/CodeSystem/v3-ActCode sensitive service provider information sensitivity Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services. Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. ADOL http://terminology.hl7.org/CodeSystem/v3-ActCode adolescent information sensitivity Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy. An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. Usage Note: For use within an enterprise in which an adolescent is the information subject. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. CEL http://terminology.hl7.org/CodeSystem/v3-ActCode celebrity information sensitivity Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality. Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location. Usage Note: For use within an enterprise in which the information subject is deemed a celebrity or very important person. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. VIP http://terminology.hl7.org/CodeSystem/v3-ActCode celebrity information sensitivity Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality. Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location. Usage Note: For use within an enterprise in which the information subject is deemed a celebrity or very important person. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. DIA http://terminology.hl7.org/CodeSystem/v3-ActCode diagnosis information sensitivity Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality. Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality. Usage Note: For use within an enterprise that provides heightened confidentiality to diagnostic, health condition or health problem related information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. DRGIS http://terminology.hl7.org/CodeSystem/v3-ActCode drug information sensitivity Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality. Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. EMP http://terminology.hl7.org/CodeSystem/v3-ActCode employee information sensitivity Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. Usage Note: Policy for handling information related to an employee, which will be afforded heightened confidentiality. Description: When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. PDS http://terminology.hl7.org/CodeSystem/v3-ActCode patient default information sensitivity Policy for specially protecting information reported by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive for another reason.) For example information reported by the patient about another person, e.g., a family member, may be deemed sensitive by default. Organizational policy may allow the sensitivity tag to be cleared on patient's request. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. For example, VA deems employee information sensitive by default. Information about a patient who is being stalked or a victim of abuse or violence may be deemed sensitive by default per a provider organization's policies. PHY http://terminology.hl7.org/CodeSystem/v3-ActCode physician requested information sensitivity Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the provider, this may trigger alerts for follow up actions according to organizational policy or jurisdictional law. Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a physician as sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. Use cases in which this code could be used are, e.g., in systems that lack the ability to automatically detect sensitive information and must rely on manual tagging; a system that lacks an applicable sensitivity tag, or for ad hoc situations where criticality of the situation requires that the tagging be done immediately by the provider before coding or transcription of consult notes can be completed, e.g., upon detection of a patient with suicidal tendencies or potential for violence. PRS http://terminology.hl7.org/CodeSystem/v3-ActCode patient requested information sensitivity Policy for specially protecting information reported by or about a patient, which the patient deems sensitive, and the patient requests that collection, access, use, or disclosure of that information be restricted. For example, a minor patient may request that information about reproductive health not be disclosed to the patient's family or to particular providers and payers. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. COMPT http://terminology.hl7.org/CodeSystem/v3-ActCode compartment This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk." ACOCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode accountable care organization compartment A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who coordinate care for reimbursement based on quality metrics for improving outcomes and lowering costs, and may be authorized to access the consumer's health information because of membership in that group. Security Compartment Labels assigned to a consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a an accountable care workflow who is requesting access to that information CDSSCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode CDS system compartment This compartment code may be used as a field value in an initiator's clearance to indicate permission for its Clinical Decision Support system (CDSS) to access and use an IT Resource with a security label having the same compartment value in the security category label field. This code permits a CDS system to algorithmically process information with this compartment tag for the purpose of alerting an unauthorized end user that masked information is needed to address an emergency or a patient safety issue, such as a contraindicated medication. The alert would advise the end user to "break the glass", to access the masked information in an accountable manner, or to ask the patient about possibly masked information. For example, releasing a list of sensitive medications with this compartment tag means that while the CDS system is permitted to use this list in its contraindication analysis, this sensitive information should not be shared directly with unauthorized end-users or end-user-facing Apps. Based on the results of the CDS system analysis (e.g., warnings about prescriptions) the end-user (e.g., a clinician) may still have the ability to access to the sensitive information by invoking "break-the-glass protocol". Usage Note: A security label with the CDS system compartment may be used in conjunction with other security labels, e.g., a label authorizing an end user with adequate clearance to access the same CDS system compartment tagged information. For example, a patient may restrict sharing sensitive information with most care team members except in an emergency or to prevent an adverse event, and may consent to sharing with their sensitive service care team providers, e.g., for mental health or substance abuse. CTCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode care team compartment Care coordination across participants in a care plan requires sharing of a healthcare consumer's information specific to that workflow. A care team member should only have access to that information while participating in that workflow or for other authorized uses. Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information FMCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode financial management compartment Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows. Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a financial management workflow who is requesting access to that information. HRCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode human resource compartment A security category label field value, which indicates that access and use of an IT resource is restricted to members of human resources department or workflow. LRCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode legitimate relationship compartment Providers and care givers who have an established relationship per criteria determined by policy are considered to have an established care provision relations with a healthcare consumer, and may be authorized to access the consumer's health information because of that relationship. Providers and care givers should only have access to that information while participating in legitimate relationship workflows or for other authorized uses. Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information. PACOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode patient administration compartment Patient administration members who have access to healthcare consumer information as part of a patient administration workflows. Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a patient administration workflow who is requesting access to that information. RESCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode research project compartment A security category label field value, which indicates that access and use of an IT resource is restricted to members of a research project. RMGTCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode records management compartment A security category label field value, which indicates that access and use of an IT resource is restricted to members of records management department or workflow. ANNUITY http://terminology.hl7.org/CodeSystem/v3-ObservationValue annuity Indicator of annuity ownership or status as beneficiary. PROP http://terminology.hl7.org/CodeSystem/v3-ObservationValue real property Indicator of real property ownership, e.g., deed or real estate contract. RETACCT http://terminology.hl7.org/CodeSystem/v3-ObservationValue retirement investment account Indicator of retirement investment account ownership. TRUST http://terminology.hl7.org/CodeSystem/v3-ObservationValue trust Indicator of status as trust beneficiary. ASSET http://terminology.hl7.org/CodeSystem/v3-ObservationValue asset Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program. CHILD http://terminology.hl7.org/CodeSystem/v3-ObservationValue child support Indicator of child support payments received or provided. DISABL http://terminology.hl7.org/CodeSystem/v3-ObservationValue disability pay Indicator of disability income replacement payment. INVEST http://terminology.hl7.org/CodeSystem/v3-ObservationValue investment income Indicator of investment income, e.g., dividend check, annuity payment; real estate rent, investment divestiture proceeds; trust or endowment check. PAY http://terminology.hl7.org/CodeSystem/v3-ObservationValue paid employment Indicator of paid employment, e.g., letter of hire, contract, employer letter; copy of pay check or pay stub. RETIRE http://terminology.hl7.org/CodeSystem/v3-ObservationValue retirement pay Indicator of retirement payment, e.g., pension check. SPOUSAL http://terminology.hl7.org/CodeSystem/v3-ObservationValue spousal or partner support Indicator of spousal or partner support payments received or provided; e.g., alimony payment; support stipulations in a divorce settlement. SUPPLE http://terminology.hl7.org/CodeSystem/v3-ObservationValue income supplement Indicator of income supplement, e.g., gifting, parental income support; stipend, or grant. TAX http://terminology.hl7.org/CodeSystem/v3-ObservationValue tax obligation Indicator of tax obligation or payment, e.g., statement of taxable income. INCOME http://terminology.hl7.org/CodeSystem/v3-ObservationValue income Code specifying income indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay or pension check, child support payments received or provided, and taxes paid. CLOTH http://terminology.hl7.org/CodeSystem/v3-ObservationValue clothing expense Indicator of clothing expenses. FOOD http://terminology.hl7.org/CodeSystem/v3-ObservationValue food expense Indicator of transportation expenses. HEALTH http://terminology.hl7.org/CodeSystem/v3-ObservationValue health expense Indicator of health expenses; including medication costs, health service costs, financial participations, and health coverage premiums. HOUSE http://terminology.hl7.org/CodeSystem/v3-ObservationValue household expense Indicator of housing expense, e.g., household appliances, fixtures, furnishings, and maintenance and repairs. LEGAL http://terminology.hl7.org/CodeSystem/v3-ObservationValue legal expense Indicator of legal expenses. MORTG http://terminology.hl7.org/CodeSystem/v3-ObservationValue mortgage Indicator of mortgage amount, interest, and payments. RENT http://terminology.hl7.org/CodeSystem/v3-ObservationValue rent Indicator of rental or lease payments. SUNDRY http://terminology.hl7.org/CodeSystem/v3-ObservationValue sundry expense Indicator of transportation expenses. TRANS http://terminology.hl7.org/CodeSystem/v3-ObservationValue transportation expense Indicator of transportation expenses, e.g., vehicle payments, vehicle insurance, vehicle fuel, and vehicle maintenance and repairs. UTIL http://terminology.hl7.org/CodeSystem/v3-ObservationValue utility expense Indicator of transportation expenses. LIVEXP http://terminology.hl7.org/CodeSystem/v3-ObservationValue living expense Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program. ADOPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue adoption document Indicator of adoption. BTHCERT http://terminology.hl7.org/CodeSystem/v3-ObservationValue birth certificate Indicator of birth. CCOC http://terminology.hl7.org/CodeSystem/v3-ObservationValue creditable coverage document Indicator of creditable coverage. DRLIC http://terminology.hl7.org/CodeSystem/v3-ObservationValue driver license Indicator of driving status. FOSTER http://terminology.hl7.org/CodeSystem/v3-ObservationValue foster child document Indicator of foster child status. MEMBER http://terminology.hl7.org/CodeSystem/v3-ObservationValue program or policy member Indicator of status as covered member under a policy or program, e.g., member id card or coverage document. MIL http://terminology.hl7.org/CodeSystem/v3-ObservationValue military identification Indicator of military status. MRGCERT http://terminology.hl7.org/CodeSystem/v3-ObservationValue marriage certificate Indicator of marriage status. PASSPORT http://terminology.hl7.org/CodeSystem/v3-ObservationValue passport Indicator of citizenship. STUDENRL http://terminology.hl7.org/CodeSystem/v3-ObservationValue student enrollment Indicator of student status. ELSTAT http://terminology.hl7.org/CodeSystem/v3-ObservationValue eligibility indicator Code specifying eligibility indicators used to assess or establish eligibility for coverage under a policy or program eligibility status, e.g., certificates of creditable coverage; student enrollment; adoption, marriage or birth certificate. DISABLE http://terminology.hl7.org/CodeSystem/v3-ObservationValue disabled Indication of disability. DRUG http://terminology.hl7.org/CodeSystem/v3-ObservationValue drug use Indication of drug use. IVDRG http://terminology.hl7.org/CodeSystem/v3-ObservationValue IV drug use Indication of IV drug use . PGNT http://terminology.hl7.org/CodeSystem/v3-ObservationValue pregnant Non-clinical report of pregnancy. HLSTAT http://terminology.hl7.org/CodeSystem/v3-ObservationValue health status Code specifying non-clinical indicators related to health status used to assess or establish eligibility for coverage under a policy or program, e.g., pregnancy, disability, drug use, mental health issues. RELDEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue relative dependent Continued living in private residence requires functional and health care assistance from one or more relatives. SPSDEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue spouse dependent Continued living in private residence requires functional and health care assistance from spouse or life partner. URELDEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue unrelated person dependent Continued living in private residence requires functional and health care assistance from one or more unrelated persons. LIVDEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue living dependency Code specifying observations related to living dependency, such as dependent upon spouse for activities of daily living. ALONE http://terminology.hl7.org/CodeSystem/v3-ObservationValue alone Living alone. Maps to PD1-2 Living arrangement (IS) 00742 [A] DEPCHD http://terminology.hl7.org/CodeSystem/v3-ObservationValue dependent children Living with one or more dependent children requiring moderate supervision. DEPSPS http://terminology.hl7.org/CodeSystem/v3-ObservationValue dependent spouse Living with disabled spouse requiring functional and health care assistance DEPYGCHD http://terminology.hl7.org/CodeSystem/v3-ObservationValue dependent young children Living with one or more dependent children requiring intensive supervision FAM http://terminology.hl7.org/CodeSystem/v3-ObservationValue live with family Living with family. Maps to PD1-2 Living arrangement (IS) 00742 [F] RELAT http://terminology.hl7.org/CodeSystem/v3-ObservationValue relative Living with one or more relatives. Maps to PD1-2 Living arrangement (IS) 00742 [R] SPS http://terminology.hl7.org/CodeSystem/v3-ObservationValue spouse only Living only with spouse or life partner. Maps to PD1-2 Living arrangement (IS) 00742 [S] UNREL http://terminology.hl7.org/CodeSystem/v3-ObservationValue unrelated person Living with one or more unrelated persons. LIVSIT http://terminology.hl7.org/CodeSystem/v3-ObservationValue living situation Code specifying observations related to living situation for a person in a private residence. ABUSE http://terminology.hl7.org/CodeSystem/v3-ObservationValue abuse victim Indication of abuse victim. HMLESS http://terminology.hl7.org/CodeSystem/v3-ObservationValue homeless Indication of status as homeless. ILGIM http://terminology.hl7.org/CodeSystem/v3-ObservationValue illegal immigrant Indication of status as illegal immigrant. INCAR http://terminology.hl7.org/CodeSystem/v3-ObservationValue incarcerated Indication of status as incarcerated. PROB http://terminology.hl7.org/CodeSystem/v3-ObservationValue probation Indication of probation status. REFUG http://terminology.hl7.org/CodeSystem/v3-ObservationValue refugee Indication of refugee status. UNEMPL http://terminology.hl7.org/CodeSystem/v3-ObservationValue unemployed Indication of unemployed status. SOECSTAT http://terminology.hl7.org/CodeSystem/v3-ObservationValue socio economic status Code specifying observations or indicators related to socio-economic status used to assess to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. A0 http://terminology.hl7.org/CodeSystem/v3-ObservationValue no reaction **Description:**Patient exhibits no reaction to the challenge agent. A1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue minimal reaction **Description:**Patient exhibits a minimal reaction to the challenge agent. A2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue mild reaction **Description:**Patient exhibits a mild reaction to the challenge agent. A3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue moderate reaction **Description:**Patient exhibits moderate reaction to the challenge agent. A4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue severe reaction **Description:**Patient exhibits a severe reaction to the challenge agent. ALLORNONESCR http://terminology.hl7.org/CodeSystem/v3-ObservationValue All-or-nothing Scoring Code specifying that the measure uses all-or-nothing scoring. All-or-nothing scoring places an individual in the numerator of the composite measure if and only if they are in the numerator of all component measures in which they are in the denominator. LINEARSCR http://terminology.hl7.org/CodeSystem/v3-ObservationValue Linear Scoring Code specifying that the measure uses linear scoring. Linear scoring computes the fraction of component measures in which the individual appears in the numerator, giving equal weight to each component measure. OPPORSCR http://terminology.hl7.org/CodeSystem/v3-ObservationValue Opportunity Scoring Code specifying that the measure uses opportunity-based scoring. In opportunity-based scoring the measure score is determined by combining the denominator and numerator of each component measure to determine an overall composite score. WEIGHTSCR http://terminology.hl7.org/CodeSystem/v3-ObservationValue Weighted Scoring Code specifying that the measure uses weighted scoring. Weighted scoring assigns a factor to each component measure to weight that measure's contribution to the overall score. ADC http://terminology.hl7.org/CodeSystem/v3-ObservationValue adult child **Description:**Child over an age as specified by coverage policy or program, e.g., student, differently abled, and income dependent. CHD http://terminology.hl7.org/CodeSystem/v3-ObservationValue child **Description:**Dependent biological, adopted, foster child as specified by coverage policy or program. DEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue dependent **Description:**Person requiring functional and/or financial assistance from another person as specified by coverage policy or program. DP http://terminology.hl7.org/CodeSystem/v3-ObservationValue domestic partner **Description:**Persons registered as a family unit in a domestic partner registry as specified by law and by coverage policy or program. ECH http://terminology.hl7.org/CodeSystem/v3-ObservationValue employee **Description:**An individual employed by an employer who receive remuneration in wages, salary, commission, tips, piece-rates, or pay-in-kind through the employeraTMs payment system (i.e., not a contractor) as specified by coverage policy or program. FLY http://terminology.hl7.org/CodeSystem/v3-ObservationValue family coverage **Description:**As specified by coverage policy or program. IND http://terminology.hl7.org/CodeSystem/v3-ObservationValue individual **Description:**Person as specified by coverage policy or program. SSP http://terminology.hl7.org/CodeSystem/v3-ObservationValue same sex partner **Description:**A pair of people of the same gender who live together as a family as specified by coverage policy or program, e.g., Naomi and Ruth from the Book of Ruth; Socrates and Alcibiades CRITH http://terminology.hl7.org/CodeSystem/v3-ObservationValue high criticality Worst case result of a future exposure is assessed to be life-threatening or having high potential for organ system failure. CRITL http://terminology.hl7.org/CodeSystem/v3-ObservationValue low criticality Worst case result of a future exposure is not assessed to be life-threatening or having high potential for organ system failure. CRITU http://terminology.hl7.org/CodeSystem/v3-ObservationValue unable to assess criticality Unable to assess the worst case result of a future exposure. Employed http://terminology.hl7.org/CodeSystem/v3-ObservationValue Employed Individuals who, during the last week: a) did any work for at least 1 hour as paid or unpaid employees of a business or government organization; worked in their own businesses, professions, or on their own farms; or b) were not working, but who have a job or business from which the individual was temporarily absent because of vacation, illness, bad weather, childcare problems, maternity or paternity leave, labor-management dispute, job training, or other family or personal reasons, regardless of whether or not they were paid for the time off or were seeking other jobs. NotInLaborForce http://terminology.hl7.org/CodeSystem/v3-ObservationValue Not In Labor Force Persons not classified as employed or unemployed, meaning those who have no job and are not looking for one. Unemployed http://terminology.hl7.org/CodeSystem/v3-ObservationValue Unemployed Persons who currently have no employment, but are available for work and have made specific efforts to find employment. Homozygote http://terminology.hl7.org/CodeSystem/v3-ObservationValue HOMO Description: An individual having different alleles at one or more loci regarding a specific character DecrIsImp http://terminology.hl7.org/CodeSystem/v3-ObservationValue Decreased score indicates improvement Improvement is indicated as a decrease in the score or measurement (e.g. Lower score indicates better quality) IncrIsImp http://terminology.hl7.org/CodeSystem/v3-ObservationValue Increased score indicates improvement Improvement is indicated as an increase in the score or measurement (e.g. Higher score indicates better quality) COHORT http://terminology.hl7.org/CodeSystem/v3-ObservationValue cohort measure scoring A measure in which either short-term cross-section or long-term longitudinal analysis is performed over a group of subjects defined by a set of common properties or defining characteristics (e.g., Male smokers between the ages of 40 and 50 years, exposure to treatment, exposure duration). CONTVAR http://terminology.hl7.org/CodeSystem/v3-ObservationValue continuous variable measure scoring A measure score in which each individual value for the measure can fall anywhere along a continuous scale (e.g., mean time to thrombolytics which aggregates the time in minutes from a case presenting with chest pain to the time of administration of thrombolytics). PROPOR http://terminology.hl7.org/CodeSystem/v3-ObservationValue proportion measure scoring A score derived by dividing the number of cases that meet a criterion for quality (the numerator) by the number of eligible cases within a given time frame (the denominator) where the numerator cases are a subset of the denominator cases (e.g., percentage of eligible women with a mammogram performed in the last year). RATIO http://terminology.hl7.org/CodeSystem/v3-ObservationValue ratio measure scoring A score that may have a value of zero or greater that is derived by dividing a count of one type of data by a count of another type of data (e.g., the number of patients with central lines who develop infection divided by the number of central line days). COMPOSITE http://terminology.hl7.org/CodeSystem/v3-ObservationValue composite measure type A measure that is composed from one or more other measures and indicates an overall summary of those measures. EFFICIENCY http://terminology.hl7.org/CodeSystem/v3-ObservationValue efficiency measure type A measure related to the efficiency of medical treatment. EXPERIENCE http://terminology.hl7.org/CodeSystem/v3-ObservationValue experience measure type A measure related to the level of patient engagement or patient experience of care. INTERM-OM http://terminology.hl7.org/CodeSystem/v3-ObservationValue intermediate clinical outcome measure A measure that evaluates the change over time of a physiologic state observable that is associated with a specific long-term health outcome. PRO-PM http://terminology.hl7.org/CodeSystem/v3-ObservationValue patient reported outcome performance measure A measure that is a comparison of patient reported outcomes for a single or multiple patients collected via an instrument specifically designed to obtain input directly from patients. OUTCOME http://terminology.hl7.org/CodeSystem/v3-ObservationValue outcome measure type A measure that indicates the result of the performance (or non-performance) of a function or process. APPROPRIATE http://terminology.hl7.org/CodeSystem/v3-ObservationValue appropriate use process measure A measure that assesses the use of one or more processes where the expected health benefit exceeds the expected negative consequences. PROCESS http://terminology.hl7.org/CodeSystem/v3-ObservationValue process measure type A measure which focuses on a process which leads to a certain outcome, meaning that a scientific basis exists for believing that the process, when executed well, will increase the probability of achieving a desired outcome. RESOURCE http://terminology.hl7.org/CodeSystem/v3-ObservationValue resource use measure type A measure related to the extent of use of clinical resources or cost of care. STRUCTURE http://terminology.hl7.org/CodeSystem/v3-ObservationValue structure measure type A measure related to the structure of patient care. DENEX http://terminology.hl7.org/CodeSystem/v3-ObservationValue denominator exclusions Patients who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator. DENEXCEP http://terminology.hl7.org/CodeSystem/v3-ObservationValue denominator exceptions Denominator exceptions are those conditions that should remove a patient, procedure or unit of measurement from the denominator only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories: Medical reasons Patient reasons System reasons DENOM http://terminology.hl7.org/CodeSystem/v3-ObservationValue denominator It can be the same as the initial patient population or a subset of the initial patient population to further constrain the population for the purpose of the eMeasure. Different measures within an eMeasure set may have different Denominators. Continuous Variable eMeasures do not have a Denominator, but instead define a Measure Population. IPP http://terminology.hl7.org/CodeSystem/v3-ObservationValue initial patient population The initial patient population refers to all patients to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs. Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods. IP http://terminology.hl7.org/CodeSystem/v3-ObservationValue initial population The initial population refers to all entities to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs. MSRPOPL http://terminology.hl7.org/CodeSystem/v3-ObservationValue measure population Measure population is used only in continuous variable eMeasures. It is a narrative description of the eMeasure population. (e.g., all patients seen in the Emergency Department during the measurement period). NUMER http://terminology.hl7.org/CodeSystem/v3-ObservationValue numerator Numerators are used in proportion and ratio eMeasures. In proportion measures the numerator criteria are the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator. In ratio measures the numerator is related, but not directly derived from the denominator (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period). NUMEX http://terminology.hl7.org/CodeSystem/v3-ObservationValue numerator exclusions Numerator Exclusions are used only in ratio eMeasures to define instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion.) _ObservationPopulationInclusion http://terminology.hl7.org/CodeSystem/v3-ObservationValue ObservationPopulationInclusion Observation values used to assert various populations that a subject falls into. G http://terminology.hl7.org/CodeSystem/v3-ObservationValue Great extent Value for Act.partialCompletionCode attribute that implies 81-99% completion LE http://terminology.hl7.org/CodeSystem/v3-ObservationValue Large extent Value for Act.partialCompletionCode attribute that implies 61-80% completion ME http://terminology.hl7.org/CodeSystem/v3-ObservationValue Medium extent Value for Act.partialCompletionCode attribute that implies 41-60% completion MI http://terminology.hl7.org/CodeSystem/v3-ObservationValue Minimal extent Value for Act.partialCompletionCode attribute that implies 1-20% completion N http://terminology.hl7.org/CodeSystem/v3-ObservationValue None Value for Act.partialCompletionCode attribute that implies 0% completion S http://terminology.hl7.org/CodeSystem/v3-ObservationValue Some extent Value for Act.partialCompletionCode attribute that implies 21-40% completion ABSTRED http://terminology.hl7.org/CodeSystem/v3-ObservationValue abstracted Security metadata observation values used to indicate the use of a more abstract version of the content, e.g., replacing exact value of an age or date field with a range, or remove the left digits of a credit card number or SSN. AGGRED http://terminology.hl7.org/CodeSystem/v3-ObservationValue aggregated Security metadata observation values used to indicate the use of an algorithmic combination of actual values with the result of an aggregate function, e.g., average, sum, or count in order to limit disclosure of an IT resource (data, information object, service, or system capability) to the minimum necessary. ANONYED http://terminology.hl7.org/CodeSystem/v3-ObservationValue anonymized Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by used to indicate the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject. No key to relink the data is retained. MAPPED http://terminology.hl7.org/CodeSystem/v3-ObservationValue mapped Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another. Usage Note: "MAP" code does not indicate the semantic fidelity of the transformed content. To indicate semantic fidelity for maps of HL7 to other code systems, this security alteration integrity observation may be further specified using an Act valued with Value Set: MapRelationship (2.16.840.1.113883.1.11.11052). Semantic fidelity of the mapped IT Resource may also be indicated using a SecurityIntegrityConfidenceObservation. MASKED http://terminology.hl7.org/CodeSystem/v3-ObservationValue masked Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by indicating the mechanism by which software systems can make data unintelligible (that is, as unreadable and unusable by algorithmically transforming plaintext into ciphertext) such that it can only be accessed or used by authorized users. An authorized user may be provided a key to decrypt per license or "shared secret". Usage Note: "MASKED" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has been further encrypted, and may be accessed only by an authorized user or receiver to which a decryption key is provided. PSEUDED http://terminology.hl7.org/CodeSystem/v3-ObservationValue pseudonymized Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability), by indicating the mechanism by which software systems can strip portions of the resource that could 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. Rationale: Personal data which has been processed to make it impossible to know whose data it is. Used particularly for secondary use of health data. In some cases, it may be possible for authorized individuals to restore the identity of the individual, e.g.,for public health case management. Based on ISO/TS 25237:2008 Health informatics-Pseudonymization REDACTED http://terminology.hl7.org/CodeSystem/v3-ObservationValue redacted Security metadata observation value used to indicate the mechanism by which software systems can filter an IT resource (data, information object, service, or system capability) to remove any portion of the resource that is not authorized to be access, used, or disclosed. Usage Note: "REDACTED" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has filtered and not included in the content accessed or received. SUBSETTED http://terminology.hl7.org/CodeSystem/v3-ObservationValue subsetted Metadata observation used to indicate that some information has been removed from the source object when the view this object contains was constructed because of configuration options when the view was created. The content may not be suitable for use as the basis of a record update Usage Note: This is not suitable to be used when information is removed for security reasons - see the code REDACTED for this use. SYNTAC http://terminology.hl7.org/CodeSystem/v3-ObservationValue syntactic transform Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another. Usage Note: "SYNTAC" code does not indicate the syntactical correctness of the syntactically transformed IT resource. TRSLT http://terminology.hl7.org/CodeSystem/v3-ObservationValue translated Security metadata observation value used to indicate that the IT resource has been translated from one human language to another. Usage Note: "TRSLT" does not indicate the fidelity of the translation or the languages translated. The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation. To indicate languages, use the Value Set:HumanLanguage (2.16.840.1.113883.1.11.11526) VERSIONED http://terminology.hl7.org/CodeSystem/v3-ObservationValue versioned Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) which indicates that the resource only retains versions of an IT resource for access and use per applicable policy Usage Note: When this code is used, expectation is that the system has removed historical versions of the data that falls outside the time period deemed to be the effective time of the applicable version. CRYTOHASH http://terminology.hl7.org/CodeSystem/v3-ObservationValue cryptographic hash function Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit. Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit. The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit. Examples: SHA-1 SHA-2 (Secure Hash Algorithm) DIGSIG http://terminology.hl7.org/CodeSystem/v3-ObservationValue digital signature Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. Rationale: This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature: Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient. HRELIABLE http://terminology.hl7.org/CodeSystem/v3-ObservationValue highly reliable Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be very high. RELIABLE http://terminology.hl7.org/CodeSystem/v3-ObservationValue reliable Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be adequate. UNCERTREL http://terminology.hl7.org/CodeSystem/v3-ObservationValue uncertain reliability Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be uncertain. UNRELIABLE http://terminology.hl7.org/CodeSystem/v3-ObservationValue unreliable Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be inadequate. CLINAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue clinician asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a clinician. DEVAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue device asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a device. HCPAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue healthcare professional asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a healthcare professional. PACQAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue patient acquaintance asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient acquaintance. PATAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue patient asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient. PAYAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue payer asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a payer. PROAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue professional asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a professional. SDMAST http://terminology.hl7.org/CodeSystem/v3-ObservationValue substitute decision maker asserted Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a substitute decision maker. CLINRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue clinician reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a clinician. DEVRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue device reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a device. HCPRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue healthcare professional reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a healthcare professional. PACQRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue patient acquaintance reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient acquaintance. PATRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue patient reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient. PAYRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue payer reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a payer. PRORPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue professional reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a professional. SDMRPT http://terminology.hl7.org/CodeSystem/v3-ObservationValue substitute decision maker reported Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a substitute decision maker. TRSTACCRDOBV http://terminology.hl7.org/CodeSystem/v3-ObservationValue trust accreditation observation Values for security trust accreditation metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. TRSTAGREOBV http://terminology.hl7.org/CodeSystem/v3-ObservationValue trust agreement observation Values for security trust agreement metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] [ISO IEC 10181-1] TRSTCERTOBV http://terminology.hl7.org/CodeSystem/v3-ObservationValue trust certificate observation Values for security trust certificate metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] For example, a Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. A particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. Another example is Cross Certification with Federal Bridge. LOAAN1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low authentication level of assurance Indicator of low digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] Low authentication level of assurance indicates that the relying party may have little or no confidence in the asserted identity's validity. Level 1 requires little or no confidence in the asserted identity. No identity proofing is required at this level, but the authentication mechanism should provide some assurance that the same claimant is accessing the protected transaction or data. A wide range of available authentication technologies can be employed and any of the token methods of Levels 2, 3, or 4, including Personal Identification Numbers (PINs), may be used. To be authenticated, the claimant must prove control of the token through a secure authentication protocol. At Level 1, long-term shared authentication secrets may be revealed to verifiers. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAN2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic authentication level of assurance Indicator of basic digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] Basic authentication level of assurance indicates that the relying party may have some confidence in the asserted identity's validity. Level 2 requires confidence that the asserted identity is accurate. Level 2 provides for single-factor remote network authentication, including identity-proofing requirements for presentation of identifying materials or information. A wide range of available authentication technologies can be employed, including any of the token methods of Levels 3 or 4, as well as passwords. Successful authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, and online guessing attacks are prevented. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are required. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAN3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium authentication level of assurance Indicator of medium digital quality or reliability of the digital reliability of verification and validation of the process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] Medium authentication level of assurance indicates that the relying party may have high confidence in the asserted identity's validity. Level 3 is appropriate for transactions that need high confidence in the accuracy of the asserted identity. Level 3 provides multifactor remote network authentication. At this level, identity-proofing procedures require verification of identifying materials and information. Authentication is based on proof of possession of a key or password through a cryptographic protocol. Cryptographic strength mechanisms should protect the primary authentication token (a cryptographic key) against compromise by the protocol threats, including eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks. A minimum of two authentication factors is required. Three kinds of tokens may be used: "soft" cryptographic token, which has the key stored on a general-purpose computer, "hard" cryptographic token, which has the key stored on a special hardware device, and "one-time password" device token, which has symmetric key stored on a personal hardware device that is a cryptographic module validated at FIPS 140-2 Level 1 or higher. Validation testing of cryptographic modules and algorithms for conformance to Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules, is managed by NIST. Authentication requires that the claimant prove control of the token through a secure authentication protocol. The token must be unlocked with a password or biometric representation, or a password must be used in a secure authentication protocol, to establish two-factor authentication. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are used for all operations. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAN4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high authentication level of assurance Indicator of high digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] High authentication level of assurance indicates that the relying party may have very high confidence in the asserted identity's validity. Level 4 is for transactions that need very high confidence in the accuracy of the asserted identity. Level 4 provides the highest practical assurance of remote network authentication. Authentication is based on proof of possession of a key through a cryptographic protocol. This level is similar to Level 3 except that only “hardâ€? cryptographic tokens are allowed, cryptographic module validation requirements are strengthened, and subsequent critical data transfers must be authenticated via a key that is bound to the authentication process. The token should be a hardware cryptographic module validated at FIPS 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. This level requires a physical token, which cannot readily be copied, and operator authentication at Level 2 and higher, and ensures good, two-factor remote authentication. Level 4 requires strong cryptographic authentication of all parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks are prevented. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Strong approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAP1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low authentication process level of assurance Indicator of the low digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] Low authentication process level of assurance indicates that (1) long-term shared authentication secrets may be revealed to verifiers; and (2) assertions and assertion references require protection from manufacture/modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAP2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic authentication process level of assurance Indicator of the basic digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] Basic authentication process level of assurance indicates that long-term shared authentication secrets are never revealed to any other party except Credential Service Provider (CSP). Sessions (temporary) shared secrets may be provided to independent verifiers by CSP. Long-term shared authentication secrets, if used, are never revealed to any other party except Verifiers operated by the Credential Service Provider (CSP); however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 1 requirements, assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAP3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium authentication process level of assurance Indicator of the medium digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] Medium authentication process level of assurance indicates that the token can be unlocked with password, biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication. Long-term shared authentication secrets are never revealed to any party except the Claimant and Credential Service Provider (CSP). Authentication requires that the Claimant prove, through a secure authentication protocol, that he or she controls the token. The Claimant unlocks the token with a password or biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication (through proof of possession of a physical or software token in combination with some memorized secret knowledge). Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 2 requirements, assertions are protected against repudiation by the Verifier. LOAAP4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high authentication process level of assurance Indicator of the high digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] High authentication process level of assurance indicates all sensitive data transfer are cryptographically authenticated using keys bound to the authentication process. Level 4 requires strong cryptographic authentication of all communicating parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the Claimant prove through a secure authentication protocol that he or she controls the token. All protocol threats at Level 3 are required to be prevented at Level 4. Protocols shall also be strongly resistant to man-in-the-middle attacks. Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. Approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAS1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low assertion level of assurance Indicator of the low quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. Assertions and assertion references require protection from modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAS2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic assertion level of assurance Indicator of the basic quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. Assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required for all assertion protocols. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAS3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium assertion level of assurance Indicator of the medium quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. Assertions are protected against repudiation by the verifier. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOAAS4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high assertion level of assurance Indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. Strongly resistant to man-in-the-middle attacks. "Bearer" assertions are not used. "Holder-of-key" assertions may be used. RP maintains records of the assertions. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] LOACM1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low token and credential management level of assurance Indicator of the low digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Little or no confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include weak identity binding to tokens and plaintext passwords or secrets not transmitted across a network. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOACM2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic token and credential management level of assurance Indicator of the basic digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Some confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verification must prove claimant controls the token; token resists online guessing, replay, session hijacking, and eavesdropping attacks; and token is at least weakly resistant to man-in-the middle attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOACM3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium token and credential management level of assurance Indicator of the medium digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it's binding to an identity. High confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Ownership of token verifiable through security authentication protocol and credential management protects against verifier impersonation attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOACM4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high token and credential management level of assurance Indicator of the high digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it's binding to an identity. Very high confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verifier can prove control of token through a secure protocol; credential management supports strong cryptographic authentication of all communication parties. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOAID1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low identity proofing level of assurance Indicator of low digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires that a continuity of identity be maintained but does not require identity proofing. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOAID2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic identity proofing level of assurance Indicator of some digital quality or reliability in the process of ascertaining that that an individual is who he or she claims to be. Requires identity proofing via presentation of identifying material or information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOAID3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium identity proofing level of assurance Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOAID4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high identity proofing level of assurance Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOANR1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low non-repudiation level of assurance Indicator of low digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] LOANR2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic non-repudiation level of assurance Indicator of basic digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] LOANR3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium non-repudiation level of assurance Indicator of medium digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] LOANR4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high non-repudiation level of assurance Indicator of high digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] LOARA1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low remote access level of assurance Indicator of low digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2] LOARA2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic remote access level of assurance Indicator of basic digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2] LOARA3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium remote access level of assurance Indicator of medium digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2] LOARA4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high remote access level of assurance Indicator of high digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2] LOATK1 http://terminology.hl7.org/CodeSystem/v3-ObservationValue low token level of assurance Indicator of the low digital quality or reliability of single and multi-token authentication. Permits the use of any of the token methods of Levels 2, 3, or 4. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOATK2 http://terminology.hl7.org/CodeSystem/v3-ObservationValue basic token level of assurance Indicator of the basic digital quality or reliability of single and multi-token authentication. Requires single factor authentication using memorized secret tokens, pre-registered knowledge tokens, look-up secret tokens, out of band tokens, or single factor one-time password devices. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOATK3 http://terminology.hl7.org/CodeSystem/v3-ObservationValue medium token level of assurance Indicator of the medium digital quality or reliability of single and multi-token authentication. Requires two authentication factors. Provides multi-factor remote network authentication. Permits multi-factor software cryptographic token. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] LOATK4 http://terminology.hl7.org/CodeSystem/v3-ObservationValue high token level of assurance Indicator of the high digital quality or reliability of single and multi-token authentication. Requires token that is a hardware cryptographic module validated at validated at Federal Information Processing Standard (FIPS) 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. Level 4 token requirements can be met by using the PIV authentication key of a FIPS 201 compliant Personal Identity Verification (PIV) Card. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] TRSTMECOBV http://terminology.hl7.org/CodeSystem/v3-ObservationValue none supplied 6 Values for security trust mechanism metadata observation made about a security architecture system component that supports enforcement of security policies. H http://terminology.hl7.org/CodeSystem/v3-ObservationValue High Indicates the condition may be life-threatening or has the potential to cause permanent injury. L http://terminology.hl7.org/CodeSystem/v3-ObservationValue Low Indicates the condition may result in some adverse consequences but is unlikely to substantially affect the situation of the subject. M http://terminology.hl7.org/CodeSystem/v3-ObservationValue Moderate Indicates the condition may result in noticable adverse adverse consequences but is unlikely to be life-threatening or cause permanent injury. LLD http://terminology.hl7.org/CodeSystem/v3-ObservationValue left lateral decubitus Lying on the left side. PRN http://terminology.hl7.org/CodeSystem/v3-ObservationValue prone Lying with the front or ventral surface downward; lying face down. RLD http://terminology.hl7.org/CodeSystem/v3-ObservationValue right lateral decubitus Lying on the right side. SFWL http://terminology.hl7.org/CodeSystem/v3-ObservationValue Semi-Fowler's A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees. SIT http://terminology.hl7.org/CodeSystem/v3-ObservationValue sitting Resting the body on the buttocks, typically with upper torso erect or semi erect. STN http://terminology.hl7.org/CodeSystem/v3-ObservationValue standing To be stationary, upright, vertical, on one's legs. RTRD http://terminology.hl7.org/CodeSystem/v3-ObservationValue reverse trendelenburg Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered. TRD http://terminology.hl7.org/CodeSystem/v3-ObservationValue trendelenburg Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised. SUP http://terminology.hl7.org/CodeSystem/v3-ObservationValue supine ACT http://terminology.hl7.org/CodeSystem/v3-ObservationValue active coverage Definition: Coverage is in effect for healthcare service(s) and/or product(s). ACTPEND http://terminology.hl7.org/CodeSystem/v3-ObservationValue active - pending investigation Definition: Coverage is in effect for healthcare service(s) and/or product(s) - Pending Investigation ELG http://terminology.hl7.org/CodeSystem/v3-ObservationValue eligible Definition: Coverage is in effect for healthcare service(s) and/or product(s). INACT http://terminology.hl7.org/CodeSystem/v3-ObservationValue inactive Definition: Coverage is not in effect for healthcare service(s) and/or product(s). INPNDINV http://terminology.hl7.org/CodeSystem/v3-ObservationValue inactive - pending investigation Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Investigation. INPNDUPD http://terminology.hl7.org/CodeSystem/v3-ObservationValue inactive - pending eligibility update Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Eligibility Update. NELG http://terminology.hl7.org/CodeSystem/v3-ObservationValue not eligible Definition: Coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. DS http://terminology.hl7.org/CodeSystem/v3-ObservationValue daytime shift A person who is scheduled for work during daytime hours (for example between 6am and 6pm) on a regular basis. EMS http://terminology.hl7.org/CodeSystem/v3-ObservationValue early morning shift Consistent Early morning schedule of 13 hours or less per shift (between 2 am and 2 pm) ES http://terminology.hl7.org/CodeSystem/v3-ObservationValue evening shift A person who is scheduled for work during evening hours (for example between 2pm and midnight) on a regular basis. NS http://terminology.hl7.org/CodeSystem/v3-ObservationValue night shift Scheduled for work during nighttime hours (for example between 9pm and 8am) on a regular basis. RSWN http://terminology.hl7.org/CodeSystem/v3-ObservationValue rotating shift with nights Scheduled for work times that change periodically between days, and/or evenings, and includes some night shifts. RSWON http://terminology.hl7.org/CodeSystem/v3-ObservationValue rotating shift without nights Scheduled for work days/times that change periodically between days, but does not include night or evening work. SS http://terminology.hl7.org/CodeSystem/v3-ObservationValue split shift Shift consisting of two distinct work periods each day that are separated by a break of a few hours (for example 2 to 4 hours) VLS http://terminology.hl7.org/CodeSystem/v3-ObservationValue very long shift Shifts of 17 or more hours. VS http://terminology.hl7.org/CodeSystem/v3-ObservationValue variable shift Irregular, unpredictable hours scheduled on a short notice (for example, less than 2 day notice): inconsistent schedule, on-call, as needed, as available.
Cross-version VS for R5.SecurityCategoryObservationValue for use in FHIR R4B
This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-SecurityCategoryObservationValue|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B.
implied consent with opportunity to dissent
military sexual trauma information sensitivity
sickle cell anemia information sensitivity
sexual assault, abuse, or domestic violence information sensitivity
sexuality and reproductive health information sensitivity
specially protected information sensitivity
behavioral health information sensitivity
cognitive disability information sensitivity
developmental disability information sensitivity
emotional disturbance information sensitivity
psychiatry disorder information sensitivity
psychotherapy note information sensitivity
substance use disorder information sensitivity
alcohol use disorder information sensitivity
opioid use disorder information sensitivity
sexually transmitted disease information sensitivity
gender and sexual orientation information sensitivity
living arrangement information sensitivity
sensitive service provider information sensitivity
physician requested information sensitivity
patient requested information sensitivity
accountable care organization compartment
patient reported outcome performance measure
medium authentication level of assurance
low authentication process level of assurance
basic authentication process level of assurance
medium authentication process level of assurance
high authentication process level of assurance
low token and credential management level of assurance
basic token and credential management level of assurance
medium token and credential management level of assurance
high token and credential management level of assurance
low identity proofing level of assurance
basic identity proofing level of assurance
medium identity proofing level of assurance
high identity proofing level of assurance
basic non-repudiation level of assurance
medium non-repudiation level of assurance