HL7.TERMINOLOGY\SecurityIntegrityProvenanceObservationValue

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

SecurityIntegrityProvenanceObservationValue

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityProvenanceObservationValue

Version:

2.0.0

Name:

SecurityIntegrityProvenanceObservationValue

Status:

Active

Title:

SecurityIntegrityProvenanceObservationValue

OID:

2.16.840.1.113883.1.11.20485 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

This value set includes codes based on the following rules:

Include codes from http://terminology.hl7.org/CodeSystem/v3-ObservationValue where concept is-a _SECINTPRVOBV

Exclude these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ObservationValue

Code	Display
_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.

Expansion

This value set contains 16 concepts

Expansion based on ObservationValue v2.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ObservationValue

Code	Display	Definition
_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.

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