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-SecurityIntegrityProvenanceObservationType |
Version: | 2.0.0 |
Name: | SecurityIntegrityProvenanceObservationType |
Status: | Active |
Title: | SecurityIntegrityProvenanceObservationType |
Definition: | Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness or workflow status of an IT resource, such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness. |
OID: | 2.16.840.1.113883.1.11.20466 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/v3-ActCode
where concept is-a SECINTPRVOBS
This value set contains 2 concepts
Expansion based on ActCode v2.0.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ActCode
Lvl | Code | Display | Definition |
0 | SECINTPRVOBS | security integrity provenance observation | Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness. **Examples:** Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: * completeness or workflow status, such as authentication * the entity responsible for original authoring or informing about an IT resource * the entity responsible for a report or assertion about an IT resource relayed “second-hand� * the entity responsible for excerpting, transforming, or compiling an IT resource |
1 | SECINTPRVABOBS | security integrity provenance asserted by observation | Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource. **Examples:** Types of security integrity provenance asserted by observation metadata, which may value the observation, including: * assertions about an IT resource by a patient * assertions about an IT resource by a clinician * assertions about an IT resource by a device |
1 | SECINTPRVRBOBS | security integrity provenance reported by observation | Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource. **Examples:** Types of security integrity provenance reported by observation metadata, which may value the observation, include: * reports about an IT resource by a patient * reports about an IT resource by a clinician * reports about an IT resource by a device |
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 |