Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.4.1.662 Value Set http://hl7.org/fhir/ValueSet/object-lifecycle-events

Security Work Group Maturity Level: 3Trial Use Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/object-lifecycle-events
Version:4.0.1
Name:ObjectLifecycleEvents
Title:
Definition:

This example FHIR value set is comprised of lifecycle event codes. The FHIR Actor value set is based on DICOM Audit Message, ParticipantObjectDataLifeCycle; ISO Standard, TS 21089-2017;

Committee:Security Work Group
OID: (for OID based terminology systems)
Copyright:

This is an example FHIR value set based on ASTM Standard, E1762-95 (2013) HL7 RoleClass OID 2.16.840.1.113883.5.110, HL7 Role Code 2.16.840.1.113883.5.111, HL7 ParticipationType OID: 2.16.840.1.113883.5.90, HL7 ParticipationFunction codes at OID: 2.16.840.1.113883.5.88, and HL7 Security and Privacy Domain Analysis Model roles classes. These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.

Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.662.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.1.662.2 Expansion

This expansion generated 01 Nov 2019

This value set contains 42 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle version 20100826

CodeSystemDisplayDefinition
1http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleOrigination / Creation
2http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleImport / Copy
3http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleAmendment
4http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleVerification
5http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleTranslation
6http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleAccess / Use
7http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleDe-identification
8http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleAggregation / summarization / derivation
9http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleReport
10http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleExport
11http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleDisclosure
12http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleReceipt of disclosure
13http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleArchiving
14http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycleLogical deletion
15http://terminology.hl7.org/CodeSystem/dicom-audit-lifecyclePermanent erasure / Physical destruction
accesshttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleAccess/View Record Lifecycle EventOccurs when an agent causes the system to obtain and open a record entry for inspection or review.
holdhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleAdd Legal Hold Record Lifecycle EventOccurs when an agent causes the system to tag or otherwise indicate special access management and suspension of record entry deletion/destruction, if deemed relevant to a lawsuit or which are reasonably anticipated to be relevant or to fulfill organizational policy under the legal doctrine of “duty to preserve”.
amendhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleAmend (Update) Record Lifecycle EventOccurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent).
archivehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleArchive Record Lifecycle EventOccurs when an agent causes the system to create and move archive artifacts containing record entry content, typically to long-term offline storage.
attesthttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleAttest Record Lifecycle EventOccurs when an agent causes the system to capture the agent’s digital signature (or equivalent indication) during formal validation of record entry content.
decrypthttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleDecrypt Record Lifecycle EventOccurs when an agent causes the system to decode record entry content from a cipher.
deidentifyhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleDe-Identify (Anononymize) Record Lifecycle EventOccurs when an agent causes the system to scrub record entry content to reduce the association between a set of identifying data and the data subject in a way that might or might not be reversible.
deprecatehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleDeprecate Record Lifecycle EventOccurs when an agent causes the system to tag record entry(ies) as obsolete, erroneous or untrustworthy, to warn against its future use.
destroyhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleDestroy/Delete Record Lifecycle EventOccurs when an agent causes the system to permanently erase record entry content from the system.
disclosehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleDisclose Record Lifecycle EventOccurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content.
encrypthttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleEncrypt Record Lifecycle EventOccurs when an agent causes the system to encode record entry content in a cipher.
extracthttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleExtract Record Lifecycle EventOccurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.
linkhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleLink Record Lifecycle EventOccurs when an agent causes the system to connect related record entries.
mergehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleMerge Record Lifecycle EventOccurs when an agent causes the system to combine or join content from two or more record entries, resulting in a single logical record entry.
originatehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleOriginate/Retain Record Lifecycle EventOccurs when an agent causes the system to: a) initiate capture of potential record content, and b) incorporate that content into the storage considered a permanent part of the health record.
pseudonymizehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecyclePseudonymize Record Lifecycle EventOccurs when an agent causes the system to remove record entry content to reduce the association between a set of identifying data and the data subject in a way that may be reversible.
reactivatehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleRe-activate Record Lifecycle EventOccurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated.
receivehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleReceive/Retain Record Lifecycle EventOccurs when an agent causes the system to a) initiate capture of data content from elsewhere, and b) incorporate that content into the storage considered a permanent part of the health record.
reidentifyhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleRe-identify Record Lifecycle EventOccurs when an agent causes the system to restore information to data that allows identification of information source and/or information subject.
unholdhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleRemove Legal Hold Record Lifecycle EventOccurs when an agent causes the system to remove a tag or other cues for special access management had required to fulfill organizational policy under the legal doctrine of “duty to preserve”.
reporthttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleReport (Output) Record Lifecycle EventOccurs when an agent causes the system to produce and deliver record entry content in a particular form and manner.
restorehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleRestore Record Lifecycle EventOccurs when an agent causes the system to recreate record entries and their content from a previous created archive artefact.
transformhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleTransform/Translate Record Lifecycle EventOccurs when an agent causes the system to change the form, language or code system used to represent record entry content.
transmithttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleTransmit Record Lifecycle EventOccurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another.
unlinkhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleUnlink Record Lifecycle EventOccurs when an agent causes the system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again.
unmergehttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleUnmerge Record Lifecycle EventOccurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again.
verifyhttp://terminology.hl7.org/CodeSystem/iso-21089-lifecycleVerify Record Lifecycle EventOccurs when an agent causes the system to confirm compliance of data or data objects with regulations, requirements, specifications, or other imposed conditions based on organizational policy.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code