Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - Downloaded Version null See the Directory of published versions

ValueSet: R2SecurityLabelsForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R2-security-labels-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2SecurityLabelsForR4

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/security-labels 1.0.2 for use in FHIR R4 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/security-labels|4.0.1.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/security-labels|1.0.2 as defined in FHIR DSTU2 in FHIR R4.

The source value set is bound to the following FHIR DSTU2 elements:

  • AuditEvent.object.securityLabel as Extensible
  • DocumentReference.securityLabel as Extensible
  • Meta.security as Extensible

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/security-labels|1.0.2
  • http://hl7.org/fhir/ValueSet/security-labels|3.0.2
  • http://hl7.org/fhir/ValueSet/security-labels|4.0.1

Note that there are 325 concepts not included in this cross-version definition because they have valid representations.

Following are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source value set has more active concepts (174) than the target (170), so the source is broader than the target. One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source value set has fewer active concepts (170) than the target (207), so the source is narrower than the target.

References

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

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://hl7.org/fhir/v3/ActCode version 📍1.0.2
    CodeDisplayDefinition
    _ActInformationSensitivityPolicyActInformationSensitivityPolicyTypes 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.
    _EntitySensitivityPolicyTypeEntityInformationSensitivityPolicyTypes 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."
    _InformationSensitivityPolicyInformationSensitivityPolicyA 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.
    _RoleInformationSensitivityPolicyRoleInformationSensitivityPolicyTypes 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."
  • Include these codes as defined in http://hl7.org/fhir/v3/Confidentiality version 📍1.0.2
    CodeDisplayDefinition
    B business Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. However, no patient related information may ever be of this confidentiality level. Deprecation Comment: Replced by ActCode.B
    C celebrity Description: Celebrities are people of public interest (VIP) including employees, whose information require special protection. Deprecation Comment:Replced by ActCode.CEL
    D clinician Description: Only clinicians may see this item, billing and administration persons can not access this item without special permission. Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
    ETH substance abuse related Description: Alcohol/drug-abuse related item Deprecation Comment:Replced by ActCode.ETH
    HIV HIV related Description: HIV and AIDS related item Deprecation Comment:Replced by ActCode.HIV
    I individual Description: Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor type code). Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
    PSY psychiatry relate Description: Psychiatry related item Deprecation Comment:Replced by ActCode.PSY
    S sensitive Description: Information for which the patient seeks heightened confidentiality. Sensitive information is not to be shared with family members. Information reported by the patient about family members is sensitive by default. Flag can be set or cleared on patient's request. Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
    SDV sexual and domestic violence related Description: Sexual assault / domestic violence related item Deprecation Comment:Replced by ActCode.SDV
    T taboo Description: Information not to be disclosed or discussed with patient except through physician assigned to patient in this case. This is usually a temporary constraint only, example use is a new fatal diagnosis or finding, such as malignancy or HIV. Deprecation Note:Replced by ActCode.TBOO
    _Confidentiality Confidentiality A specializable code and its leaf codes used in Confidentiality value sets to value the Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".
    _ConfidentialityByAccessKind ConfidentialityByAccessKind Description: By accessing subject / role and relationship based rights (These concepts are mutually exclusive, one and only one is required for a valid confidentiality coding.) Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
    _ConfidentialityByInfoType ConfidentialityByInfoType Description: By information type, only for service catalog entries (multiples allowed). Not to be used with actual patient data! Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
    _ConfidentialityModifiers ConfidentialityModifiers Description: Modifiers of role based access rights (multiple allowed) Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
  • Include these codes as defined in http://hl7.org/fhir/v3/ObservationValue version 📍1.0.2
    CodeDisplayDefinition
    _SECALTINTOBV 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)
    _SECDATINTOBV 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.
    _SECINTCONOBV 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.
    _SECINTPRVABOBV 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.
    _SECINTPRVOBV 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.
    _SECINTPRVRBOBV 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.

 

Expansion

This value set expansion contains 24 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/ActCode1.0.2  _ActInformationSensitivityPolicyActInformationSensitivityPolicyTypes 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.
http://hl7.org/fhir/v3/ActCode1.0.2  _EntitySensitivityPolicyTypeEntityInformationSensitivityPolicyTypes 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."
http://hl7.org/fhir/v3/ActCode1.0.2  _InformationSensitivityPolicyInformationSensitivityPolicyA 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.
http://hl7.org/fhir/v3/ActCode1.0.2  _RoleInformationSensitivityPolicyRoleInformationSensitivityPolicyTypes 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."
http://hl7.org/fhir/v3/Confidentiality1.0.2  BbusinessDescription: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. However, no patient related information may ever be of this confidentiality level. Deprecation Comment: Replced by ActCode.B
http://hl7.org/fhir/v3/Confidentiality1.0.2  CcelebrityDescription: Celebrities are people of public interest (VIP) including employees, whose information require special protection. Deprecation Comment:Replced by ActCode.CEL
http://hl7.org/fhir/v3/Confidentiality1.0.2  DclinicianDescription: Only clinicians may see this item, billing and administration persons can not access this item without special permission. Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/Confidentiality1.0.2  ETHsubstance abuse relatedDescription: Alcohol/drug-abuse related item Deprecation Comment:Replced by ActCode.ETH
http://hl7.org/fhir/v3/Confidentiality1.0.2  HIVHIV relatedDescription: HIV and AIDS related item Deprecation Comment:Replced by ActCode.HIV
http://hl7.org/fhir/v3/Confidentiality1.0.2  IindividualDescription: Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor type code). Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/Confidentiality1.0.2  PSYpsychiatry relateDescription: Psychiatry related item Deprecation Comment:Replced by ActCode.PSY
http://hl7.org/fhir/v3/Confidentiality1.0.2  SsensitiveDescription: Information for which the patient seeks heightened confidentiality. Sensitive information is not to be shared with family members. Information reported by the patient about family members is sensitive by default. Flag can be set or cleared on patient's request. Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/Confidentiality1.0.2  SDVsexual and domestic violence relatedDescription: Sexual assault / domestic violence related item Deprecation Comment:Replced by ActCode.SDV
http://hl7.org/fhir/v3/Confidentiality1.0.2  TtabooDescription: Information not to be disclosed or discussed with patient except through physician assigned to patient in this case. This is usually a temporary constraint only, example use is a new fatal diagnosis or finding, such as malignancy or HIV. Deprecation Note:Replced by ActCode.TBOO
http://hl7.org/fhir/v3/Confidentiality1.0.2  _ConfidentialityConfidentialityA specializable code and its leaf codes used in Confidentiality value sets to value the Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".
http://hl7.org/fhir/v3/Confidentiality1.0.2  _ConfidentialityByAccessKindConfidentialityByAccessKindDescription: By accessing subject / role and relationship based rights (These concepts are mutually exclusive, one and only one is required for a valid confidentiality coding.) Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/Confidentiality1.0.2  _ConfidentialityByInfoTypeConfidentialityByInfoTypeDescription: By information type, only for service catalog entries (multiples allowed). Not to be used with actual patient data! Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/Confidentiality1.0.2  _ConfidentialityModifiersConfidentialityModifiersDescription: Modifiers of role based access rights (multiple allowed) Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECALTINTOBValteration integrityAbstract security metadata observation values used to indicate mechanism used for authorized alteration of an IT resource (data, information object, service, or system capability)
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECDATINTOBVdata integrityAbstract 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.
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECINTCONOBVintegrity confidenceAbstract security observation value used to indicate integrity confidence metadata. Examples: Codes conveying the level of reliability and trustworthiness of an IT resource.
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECINTPRVABOBVprovenance asserted byAbstract 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.
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECINTPRVOBVprovenanceAbstract 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.
http://hl7.org/fhir/v3/ObservationValue1.0.2  _SECINTPRVRBOBVprovenance reported byAbstract 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.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code