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

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

ValueSet: R5V3SecurityClassificationObservationTypeForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-SecurityClassificationObservationType-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V3SecurityClassificationObservationTypeForR4

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-SecurityClassificationObservationType|2.0.0 for use in FHIR R4.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-SecurityClassificationObservationType|2.0.0 as defined in FHIR R5 in FHIR R4.

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

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-SecurityClassificationObservationType|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4

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)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActCode version 📍8.0.0
    CodeDisplayDefinition
    SECCLASSOBSsecurity classification observationType of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure.

    *Rationale:* A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue. This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality.

    **Examples:** Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, secret, and confidential.

    *Usage Note:* Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the "security label tag".

 

Expansion

This value set expansion contains 1 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  SECCLASSOBSsecurity classification observation

Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure.

Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue. This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality.

Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, secret, and confidential.

Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the "security label tag".

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