HL7 Terminology (THO)
6.0.1 - Publication International flag

This page is part of the HL7 Terminology (v6.0.1: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: SecurityIntegrityObservationValue

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

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 integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.

References

Logical Definition (CLD)

Generated Narrative: ValueSet v3-SecurityIntegrityObservationValue

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ObservationValue v3.1.0 (CodeSystem)

This value set contains 43 concepts

LevelCodeSystemDisplayDefinition
1  _SECINTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuesecurity integrity

Abstract security observation values used to indicate security integrity metadata.

Examples: Codes conveying integrity status, integrity confidence, and provenance.

2    _SECALTINTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuealteration 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)

3      ABSTREDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueabstracted

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.

3      AGGREDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueaggregated

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.

3      ANONYEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueanonymized

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.

3      MAPPEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuemapped

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.

3      MASKEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuemasked

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.

3      PSEUDEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepseudonymized

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

3      REDACTEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueredacted

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.

3      SUBSETTEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuesubsetted

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.

3      SYNTAChttp://terminology.hl7.org/CodeSystem/v3-ObservationValuesyntactic 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.

3      TRSLThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuetranslated

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)

3      VERSIONEDhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueversioned

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.

2    _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.

3      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)
3      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.

2    _SECINTCONOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueintegrity confidence

Abstract security observation value used to indicate integrity confidence metadata.

Examples: Codes conveying the level of reliability and trustworthiness of an IT resource.

3      HRELIABLEhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuehighly 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.

3      RELIABLEhttp://terminology.hl7.org/CodeSystem/v3-ObservationValuereliable

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.

3      UNCERTRELhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueuncertain 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.

3      UNRELIABLEhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueunreliable

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.

2    _SECINTPRVOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueprovenance

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.

3      _SECINTPRVABOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueprovenance 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.

4        CLINASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueclinician 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.

4        DEVASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuedevice 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.

4        HCPASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuehealthcare 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.

4        PACQASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepatient 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.

4        PATASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepatient 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.

4        PAYASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepayer 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.

4        PROASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueprofessional 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.

4        SDMASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuesubstitute 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.

4        AIASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueArtificial Intelligence asserted

Security provenance metadata observation value used to indicate that an IT resource (data, or information object) was asserted by a Artificial Intelligence (e.g. Clinical Decision Support, Machine Learning, Algorithm).

4        DICTASThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueDictation asserted

Security provenance metadata observation value used to indicate that an IT resource (data, or information object) was asserted by a Dictation algorithm transforming human communications (e.g. speech).

3      _SECINTPRVRBOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueprovenance 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.

4        CLINRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueclinician 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.

4        DEVRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuedevice 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.

4        HCPRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuehealthcare 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.

4        PACQRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepatient 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.

4        PATRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepatient 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.

4        PAYRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuepayer 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.

4        PRORPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValueprofessional 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.

4        SDMRPThttp://terminology.hl7.org/CodeSystem/v3-ObservationValuesubstitute 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.

2    _SECINTSTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValueintegrity status

Abstract security observation values used to indicate integrity status metadata.

Examples: Codes, such as those in the HL7 DocumentClassification code system conveying the workflow status of resource as authenticated, legally authenticated, and in progress.


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

DateActionAuthorCustodianComment
2024-07-12reviseJohn MoehrkeSecuritySecurity ValueSets need hierarchy; up-530
2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26