STU 3 Ballot
TerminologyThis page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4 R3 R2
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/security-labels |
| Name: | All Security Labels |
| Definition: | A single value set for all security labels defined by FHIR. |
| Committee: | ?? |
| OID: | 2.16.840.1.113883.4.642.2.security-labels (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 11 Aug 2016
This value set contains 180 concepts
| Code | System | Display | Definition |
| U | http://hl7.org/fhir/v3/Confidentiality | unrestricted | Definition: Privacy metadata indicating that the information is not classified as sensitive. Examples: Includes publicly available information, e.g., business name, phone, email or physical address. Usage Note: This metadata indicates that the receiver has no obligation to consider additional policies when making access control decisions. Note that in some jurisdictions, personally identifiable information must be protected as confidential, so it would not be appropriate to assign a confidentiality code of "unrestricted" to that information even if it is publicly available. |
| L | http://hl7.org/fhir/v3/Confidentiality | low | Definition: Privacy metadata indicating that the information has been de-identified, and there are mitigating circumstances that prevent re-identification, which minimize risk of harm from unauthorized disclosure. The information requires protection to maintain low sensitivity. Examples: Includes anonymized, pseudonymized, or non-personally identifiable information such as HIPAA limited data sets. Map: No clear map to ISO 13606-4 Sensitivity Level (1) Care Management: RECORD_COMPONENTs that might need to be accessed by a wide range of administrative staff to manage the subject of care's access to health services. Usage Note: This metadata indicates the receiver may have an obligation to comply with a data use agreement. |
| M | http://hl7.org/fhir/v3/Confidentiality | moderate | Definition: Privacy metadata indicating moderately sensitive information, which presents moderate risk of harm if disclosed without authorization. Examples: Includes allergies of non-sensitive nature used inform food service; health information a patient authorizes to be used for marketing, released to a bank for a health credit card or savings account; or information in personal health record systems that are not governed under health privacy laws. Map: Partial Map to ISO 13606-4 Sensitivity Level (2) Clinical Management: Less sensitive RECORD_COMPONENTs that might need to be accessed by a wider range of personnel not all of whom are actively caring for the patient (e.g. radiology staff). Usage Note: This metadata indicates that the receiver may be obligated to comply with the receiver's terms of use or privacy policies. |
| N | http://hl7.org/fhir/v3/Confidentiality | normal | Definition: Privacy metadata indicating that the information is typical, non-stigmatizing health information, which presents typical risk of harm if disclosed without authorization. Examples: In the US, this includes what HIPAA identifies as the minimum necessary protected health information (PHI) given a covered purpose of use (treatment, payment, or operations). Includes typical, non-stigmatizing health information disclosed in an application for health, workers compensation, disability, or life insurance. Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations. Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable jurisdictional privacy law or disclosure authorization. |
| R | http://hl7.org/fhir/v3/Confidentiality | restricted | Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment. Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual, e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer. Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.. Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization.. |
| V | http://hl7.org/fhir/v3/Confidentiality | very restricted | . Privacy metadata indicating that the information is extremely sensitive and likely stigmatizing health information that presents a very high risk if disclosed without authorization. This information must be kept in the highest confidence. Examples: Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient. May also include information held under “legal lock� or attorney-client privilege Map: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. Usage Note: This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject. |
| _InformationSensitivityPolicy | http://hl7.org/fhir/v3/ActCode | InformationSensitivityPolicy | A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description: Types of Sensitivity policy that apply to Acts or Roles. A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy). These criteria may in turn be used for the Policy Decision Point in a Security Engine. A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy. When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information. This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations. Usage Note: Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an employee's sensitivity code would make little sense for use outside of a policy domain. 'Taboo' would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable InformationSensitivityPolicy Act.code may be useful in some scenarios if used in combination with a sensitivity identifier and/or Act.title. |
| _ActInformationSensitivityPolicy | http://hl7.org/fhir/v3/ActCode | ActInformationSensitivityPolicy | 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. |
| ETH | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| PSY | http://hl7.org/fhir/v3/ActCode | psychiatry information sensitivity | Policy for handling psychiatry information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to psychiatry 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. |
| SOC | http://hl7.org/fhir/v3/ActCode | social services sensitivity | Information about provision of social services. Usage Note: This is a temporary addition to FHIR to be proposed in harmonization. |
| SCA | http://hl7.org/fhir/v3/ActCode | sickle cell anemia | 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://hl7.org/fhir/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. 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://hl7.org/fhir/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. |
| STD | http://hl7.org/fhir/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://hl7.org/fhir/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. |
| SICKLE | http://hl7.org/fhir/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. |
| _EntitySensitivityPolicyType | http://hl7.org/fhir/v3/ActCode | EntityInformationSensitivityPolicy | Types of sensitivity policies that may apply to a sensitive attribute on an Entity. Usage Note: EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." |
| DEMO | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| RACE | http://hl7.org/fhir/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://hl7.org/fhir/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. |
| _RoleInformationSensitivityPolicy | http://hl7.org/fhir/v3/ActCode | RoleInformationSensitivityPolicy | Types of sensitivity policies that apply to Roles. Usage Notes: RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." |
| B | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/v3/ActCode | patient default sensitivity | Policy for handling information reported by the patient about another person, e.g., a family member, which will be afforded heightened confidentiality. Sensitive information reported by the patient about another person, e.g., family members may be deemed sensitive by default. The flag may be set or cleared on patient's request. Usage Note: For sensitive information relayed 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.) 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. |
| PRS | http://hl7.org/fhir/v3/ActCode | patient requested sensitivity | For sensitive information relayed 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.) 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. Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a patient 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. |
| COMPT | http://hl7.org/fhir/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." |
| HRCOMPT | http://hl7.org/fhir/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. |
| RESCOMPT | http://hl7.org/fhir/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://hl7.org/fhir/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. |
| _SECALTINTOBV | http://hl7.org/fhir/v3/ObservationValue | alteration integrity | Abstract security metadata observation values used to indicate mechanism used for authorized alteration of an IT resource (data, information object, service, or system capability) |
| ABSTRED | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| _SECDATINTOBV | http://hl7.org/fhir/v3/ObservationValue | data integrity | Abstract security observation values used to indicate data integrity metadata. Examples: Codes conveying the mechanism used to preserve the accuracy and consistency of an IT resource such as a digital signature and a cryptographic hash function. |
| CRYTOHASH | http://hl7.org/fhir/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://hl7.org/fhir/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. |
| _SECINTCONOBV | http://hl7.org/fhir/v3/ObservationValue | integrity confidence | Abstract security observation value used to indicate integrity confidence metadata. Examples: Codes conveying the level of reliability and trustworthiness of an IT resource. |
| HRELIABLE | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| _SECINTPRVOBV | http://hl7.org/fhir/v3/ObservationValue | provenance | Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability). Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. |
| _SECINTPRVABOBV | http://hl7.org/fhir/v3/ObservationValue | provenance asserted by | Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability). Examples: Codes conveying the provenance metadata about the entity asserting the resource. |
| CLINAST | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| _SECINTPRVRBOBV | http://hl7.org/fhir/v3/ObservationValue | provenance reported by | Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability). Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. |
| CLINRPT | http://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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://hl7.org/fhir/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. |
| SecurityPolicy | http://hl7.org/fhir/v3/ActCode | security policy | Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent |
| ObligationPolicy | http://hl7.org/fhir/v3/ActCode | obligation policy | Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. |
| ANONY | http://hl7.org/fhir/v3/ActCode | anonymize | Custodian system must remove any information that could result in identifying the information subject. |
| AOD | http://hl7.org/fhir/v3/ActCode | accounting of disclosure | Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested. |
| AUDIT | http://hl7.org/fhir/v3/ActCode | audit | Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. |
| AUDTR | http://hl7.org/fhir/v3/ActCode | audit trail | Custodian system must monitor and maintain retrievable log for each user and operation on information. |
| CPLYCC | http://hl7.org/fhir/v3/ActCode | comply with confidentiality code | Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target. |
| CPLYCD | http://hl7.org/fhir/v3/ActCode | comply with consent directive | Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. |
| CPLYJPP | http://hl7.org/fhir/v3/ActCode | comply with jurisdictional privacy policy | Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. |
| CPLYOPP | http://hl7.org/fhir/v3/ActCode | comply with organizational privacy policy | Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. |
| CPLYOSP | http://hl7.org/fhir/v3/ActCode | comply with organizational security policy | Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. |
| CPLYPOL | http://hl7.org/fhir/v3/ActCode | comply with policy | Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. |
| DECLASSIFYLABEL | http://hl7.org/fhir/v3/ActCode | declassify security label | Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. |
| DEID | http://hl7.org/fhir/v3/ActCode | deidentify | Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. |
| DELAU | http://hl7.org/fhir/v3/ActCode | delete after use | Custodian system must remove target information from access after use. |
| DOWNGRDLABEL | http://hl7.org/fhir/v3/ActCode | downgrade security label | Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. |
| DRIVLABEL | http://hl7.org/fhir/v3/ActCode | derive security label | Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. |
| ENCRYPT | http://hl7.org/fhir/v3/ActCode | encrypt | Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.) |
| ENCRYPTR | http://hl7.org/fhir/v3/ActCode | encrypt at rest | Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. |
| ENCRYPTT | http://hl7.org/fhir/v3/ActCode | encrypt in transit | Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means. |
| ENCRYPTU | http://hl7.org/fhir/v3/ActCode | encrypt in use | Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user. |
| HUAPRV | http://hl7.org/fhir/v3/ActCode | human approval | Custodian system must require human review and approval for permission requested. |
| LABEL | http://hl7.org/fhir/v3/ActCode | assign security label | Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes. |
| MASK | http://hl7.org/fhir/v3/ActCode | mask | Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". |
| MINEC | http://hl7.org/fhir/v3/ActCode | minimum necessary | Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use. |
| PERSISTLABEL | http://hl7.org/fhir/v3/ActCode | persist security label | Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. |
| PRIVMARK | http://hl7.org/fhir/v3/ActCode | privacy mark | Custodian must create and/or maintain human readable security label tags as required by policy. Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." |
| PSEUD | http://hl7.org/fhir/v3/ActCode | pseudonymize | Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. |
| REDACT | http://hl7.org/fhir/v3/ActCode | redact | Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. |
| UPGRDLABEL | http://hl7.org/fhir/v3/ActCode | upgrade security label | Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. |
| RefrainPolicy | http://hl7.org/fhir/v3/ActCode | refrain policy | Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc. |
| NOAUTH | http://hl7.org/fhir/v3/ActCode | no disclosure without subject authorization | Prohibition on disclosure without information subject's authorization. |
| NOCOLLECT | http://hl7.org/fhir/v3/ActCode | no collection | Prohibition on collection or storage of the information. |
| NODSCLCD | http://hl7.org/fhir/v3/ActCode | no disclosure without consent directive | Prohibition on disclosure without organizational approved patient restriction. |
| NODSCLCDS | http://hl7.org/fhir/v3/ActCode | no disclosure without information subject's consent directive | Prohibition on disclosure without a consent directive from the information subject. |
| NOINTEGRATE | http://hl7.org/fhir/v3/ActCode | no integration | Prohibition on Integration into other records. |
| NOLIST | http://hl7.org/fhir/v3/ActCode | no unlisted entity disclosure | Prohibition on disclosure except to entities on specific access list. |
| NOMOU | http://hl7.org/fhir/v3/ActCode | no disclosure without MOU | Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU). |
| NOORGPOL | http://hl7.org/fhir/v3/ActCode | no disclosure without organizational authorization | Prohibition on disclosure without organizational authorization. |
| NOPAT | http://hl7.org/fhir/v3/ActCode | no disclosure to patient, family or caregivers without attending provider's authorization | Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone). |
| NOPERSISTP | http://hl7.org/fhir/v3/ActCode | no collection beyond purpose of use | Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited. |
| NORDSCLCD | http://hl7.org/fhir/v3/ActCode | no redisclosure without consent directive | Prohibition on redisclosure without patient consent directive. |
| NORDSCLCDS | http://hl7.org/fhir/v3/ActCode | no redisclosure without information subject's consent directive | Prohibition on redisclosure without a consent directive from the information subject. |
| NORDSCLW | http://hl7.org/fhir/v3/ActCode | no disclosure without jurisdictional authorization | Prohibition on disclosure without authorization under jurisdictional law. |
| NORELINK | http://hl7.org/fhir/v3/ActCode | no relinking | Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked. |
| NOREUSE | http://hl7.org/fhir/v3/ActCode | no reuse beyond purpose of use | Prohibition on use of the information beyond the purpose of use initially authorized. |
| NOVIP | http://hl7.org/fhir/v3/ActCode | no unauthorized VIP disclosure | Prohibition on disclosure except to principals with access permission to specific VIP information. |
| ORCON | http://hl7.org/fhir/v3/ActCode | no disclosure without originator authorization | Prohibition on disclosure except as permitted by the information originator. |
| PurposeOfUse | http://hl7.org/fhir/v3/ActReason | purpose of use | Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes. |
| HMARKT | http://hl7.org/fhir/v3/ActReason | healthcare marketing | To perform one or more operations on information for marketing services and products related to health care. |
| HOPERAT | http://hl7.org/fhir/v3/ActReason | healthcare operations | To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. |
| DONAT | http://hl7.org/fhir/v3/ActReason | donation | To perform one or more operations on information used for cadaveric organ, eye or tissue donation. |
| FRAUD | http://hl7.org/fhir/v3/ActReason | fraud | To perform one or more operations on information used for fraud detection and prevention processes. |
| GOV | http://hl7.org/fhir/v3/ActReason | government | To perform one or more operations on information used within government processes. |
| HACCRED | http://hl7.org/fhir/v3/ActReason | health accreditation | To perform one or more operations on information for conducting activities related to meeting accreditation criteria. |
| HCOMPL | http://hl7.org/fhir/v3/ActReason | health compliance | To perform one or more operations on information used for conducting activities required to meet a mandate. |
| HDECD | http://hl7.org/fhir/v3/ActReason | decedent | To perform one or more operations on information used for handling deceased patient matters. |
| HDIRECT | http://hl7.org/fhir/v3/ActReason | directory | To perform one or more operation operations on information used to manage a patient directory. Examples: facility enterprise payer health information exchange patient directory |
| HLEGAL | http://hl7.org/fhir/v3/ActReason | legal | To perform one or more operations on information for conducting activities required by legal proceeding. |
| HOUTCOMS | http://hl7.org/fhir/v3/ActReason | health outcome measure | To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions. |
| HPRGRP | http://hl7.org/fhir/v3/ActReason | health program reporting | To perform one or more operations on information used for conducting activities to meet program accounting requirements. |
| HQUALIMP | http://hl7.org/fhir/v3/ActReason | health quality improvement | To perform one or more operations on information used for conducting administrative activities to improve health care quality. |
| HSYSADMIN | http://hl7.org/fhir/v3/ActReason | health system administration | To perform one or more operations on information to administer the electronic systems used for the delivery of health care. |
| MEMADMIN | http://hl7.org/fhir/v3/ActReason | member administration | To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program. |
| PATADMIN | http://hl7.org/fhir/v3/ActReason | patient administration | To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient. |
| PATSFTY | http://hl7.org/fhir/v3/ActReason | patient safety | To perform one or more operations on information in processes related to ensuring the safety of health care. |
| PERFMSR | http://hl7.org/fhir/v3/ActReason | performance measure | To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions. |
| RECORDMGT | http://hl7.org/fhir/v3/ActReason | records management | To perform one or more operations on information used within the health records management process. |
| TRAIN | http://hl7.org/fhir/v3/ActReason | training | To perform one or more operations on information used in training and education. |
| HPAYMT | http://hl7.org/fhir/v3/ActReason | healthcare payment | To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. |
| CLMATTCH | http://hl7.org/fhir/v3/ActReason | claim attachment | To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services. |
| COVAUTH | http://hl7.org/fhir/v3/ActReason | coverage authorization | To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services. |
| COVERAGE | http://hl7.org/fhir/v3/ActReason | coverage under policy or program | To perform one or more operations on information for conducting activities related to coverage under a program or policy. |
| ELIGDTRM | http://hl7.org/fhir/v3/ActReason | eligibility determination | To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment. |
| ELIGVER | http://hl7.org/fhir/v3/ActReason | eligibility verification | To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays. |
| ENROLLM | http://hl7.org/fhir/v3/ActReason | enrollment | To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices. |
| REMITADV | http://hl7.org/fhir/v3/ActReason | remittance advice | To perform one or more operations on information about the amount remitted for a health care claim. |
| HRESCH | http://hl7.org/fhir/v3/ActReason | healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. |
| CLINTRCH | http://hl7.org/fhir/v3/ActReason | clinical trial research | To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge. |
| PATRQT | http://hl7.org/fhir/v3/ActReason | patient requested | To perform one or more operations on information in response to a patient's request. |
| FAMRQT | http://hl7.org/fhir/v3/ActReason | family requested | To perform one or more operations on information in response to a request by a family member authorized by the patient. |
| PWATRNY | http://hl7.org/fhir/v3/ActReason | power of attorney | To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative. |
| SUPNWK | http://hl7.org/fhir/v3/ActReason | support network | To perform one or more operations on information in response to a request by a person authorized by the patient. |
| PUBHLTH | http://hl7.org/fhir/v3/ActReason | public health | To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. |
| DISASTER | http://hl7.org/fhir/v3/ActReason | 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. |
| THREAT | http://hl7.org/fhir/v3/ActReason | 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. |
| TREAT | http://hl7.org/fhir/v3/ActReason | treatment | To perform one or more operations on information for provision of health care. |
| CAREMGT | http://hl7.org/fhir/v3/ActReason | Care Management | To perform one or more operations on information for provision of health care coordination. |
| CLINTRL | http://hl7.org/fhir/v3/ActReason | clinical trial | To perform health care as part of the clinical trial protocol. |
| ETREAT | http://hl7.org/fhir/v3/ActReason | Emergency Treatment | To perform one or more operations on information for provision of immediately needed health care for an emergent condition. |
| POPHLTH | http://hl7.org/fhir/v3/ActReason | population health | To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program. |
| _ActUSPrivacyLaw | http://hl7.org/fhir/v3/ActUSPrivacyLaw | 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://hl7.org/fhir/v3/ActUSPrivacyLaw | 42 CFR Part2 | 42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program. Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent. Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. |
| CommonRule | http://hl7.org/fhir/v3/ActUSPrivacyLaw | Common Rule | U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that 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. Definition: U.S. federal laws governing research-related privacy policies. Usage Note: 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. |
| HIPAANOPP | http://hl7.org/fhir/v3/ActUSPrivacyLaw | HIPAA notice of privacy practices | The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law. Definition: Notification of HIPAA Privacy Practices. Usage Note: 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. |
| HIPAAPsyNotes | http://hl7.org/fhir/v3/ActUSPrivacyLaw | HIPAA psychotherapy notes | The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes. Definition: Authorization that must be obtained for disclosure of psychotherapy notes. Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. |
| HIPAASelfPay | http://hl7.org/fhir/v3/ActUSPrivacyLaw | HIPAA self-pay | Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan. Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full. Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. |
| Title38Section7332 | http://hl7.org/fhir/v3/ActUSPrivacyLaw | Title 38 Section 7332 | Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfill the duties of the contract; and researchers who provide assurances that the information will not be identified in any report. This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes. Definition: Title 38 Part 1 - §1.462 Confidentiality restrictions. (a) General. The patient records to which §§1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(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). Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |
© HL7.org 2011+. FHIR STU3 Ballot (v1.6.0-9663) generated on Thu, Aug 11, 2016 17:06+1000. QA Page
Links: Search |
Version History |
Table of Contents |
Compare to DSTU2 |
|
Propose a change