HL7 Terminology
1.0.0 - Publication
HL7 Terminology
1.0.0 - Publication
This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions 
Summary
| Defining URL: | http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityObservationValue |
| Version: | 2.0.0 |
| Name: | SecurityIntegrityObservationValue |
| Status: | Active |
| Title: | SecurityIntegrityObservationValue |
| OID: | 2.16.840.1.113883.1.11.20481 (for OID based terminology systems) |
| Source Resource: | XML / JSON / Turtle |
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _SECINTOBVhttp://terminology.hl7.org/CodeSystem/v3-ObservationValue| Code | Display | |
| _SECINTOBV | security integrity | Abstract security observation values used to indicate security integrity metadata. **Examples:** Codes conveying integrity status, integrity confidence, and provenance. |
This value set contains 33 concepts
Expansion based on ObservationValue v2.0.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ObservationValue
| Code | Display | Definition |
| _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) |
| ABSTRED | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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. |
| _SECINTSTOBV | integrity 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 |
| 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 |
History
| Date | Action | Author | Custodian | Comment |
| 2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
| 2014-03-26 | revise | Vocabulary (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 |
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#1.0.0 based on FHIR 4.0.1. Generated 2020-05-09
Links: Table of Contents |
QA Report | Search
| Version History |
Propose a change