HL7 Terminology (THO)
6.1.0 - Publication International flag

This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: SecurityDataIntegrityObservationValue

Official URL: http://terminology.hl7.org/ValueSet/v3-SecurityDataIntegrityObservationValue Version: 3.1.0
Active as of 2024-02-28 Responsible: Health Level Seven International Computable Name: SecurityDataIntegrityObservationValue
Other Identifiers: OID:2.16.840.1.113883.1.11.20483

Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made."

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)

Generated Narrative: ValueSet v3-SecurityDataIntegrityObservationValue

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ObservationValue v4.0.0 (CodeSystem)

This value set contains 3 concepts

LevelCodeSystemDisplayDefinition
1  _SECDATINTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuedata 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.

2    CRYTOHASHhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuecryptographic 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)
2    DIGSIGhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuedigital 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.

Explanation of the columns that may appear on this page:

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

History

DateActionCustodianAuthorComment
2024-07-12reviseSecurityJohn MoehrkeSecurity ValueSets need hierarchy; up-530
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26