FHIR Extensions Pack
5.3.0-ballot-tc1 - (September 2025 Ballot) International flag

FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.3.0-ballot-tc1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions

ValueSet: ObjectLifecycleEvents

Official URL: http://hl7.org/fhir/ValueSet/object-lifecycle-events Version: 5.3.0-ballot-tc1
Standards status: Trial-use Maturity Level: 3 Responsible: HL7 International / Security Computable Name: ObjectLifecycleEvents
Other Identifiers: OID:2.16.840.1.113883.4.642.3.3009

Copyright/Legal: This is an 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.

This 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;

References

Changes since version 5.2.0:

  • No changes

    • Logical Definition (CLD)

    Last updated: 2023-01-31 07:07:38+1100

    Profile: Shareable ValueSet

    This value set includes codes based on the following rules:

     

    Expansion

    This value set contains 42 concepts

    SystemCodeDisplay (en)DefinitionJSONXML
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  1Origination / Creation
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  2Import / Copy
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  3Amendment
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  4Verification
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  5Translation
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  6Access / Use
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  7De-identification
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  8Aggregation / summarization / derivation
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  9Report
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  10Export
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  11Disclosure
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  12Receipt of disclosure
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  13Archiving
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  14Logical deletion
    http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle  15Permanent erasure / Physical destruction
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  accessAccess/View Record Lifecycle EventOccurs when an agent causes the system to obtain and open a record entry for inspection or review.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  holdAdd 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”.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  amendAmend (Update) Record Lifecycle EventOccurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent).
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  archiveArchive 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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  attestAttest 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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  decryptDecrypt Record Lifecycle EventOccurs when an agent causes the system to decode record entry content from a cipher.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  deidentifyDe-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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  deprecateDeprecate 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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  destroyDestroy/Delete Record Lifecycle EventOccurs when an agent causes the system to permanently erase record entry content from the system.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  discloseDisclose Record Lifecycle EventOccurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  encryptEncrypt Record Lifecycle EventOccurs when an agent causes the system to encode record entry content in a cipher.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  extractExtract Record Lifecycle EventOccurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  linkLink Record Lifecycle EventOccurs when an agent causes the system to connect related record entries.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  mergeMerge 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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  originateOriginate/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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  pseudonymizePseudonymize 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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  reactivateRe-activate Record Lifecycle EventOccurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  receiveReceive/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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  reidentifyRe-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.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  unholdRemove 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”.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  reportReport (Output) Record Lifecycle EventOccurs when an agent causes the system to produce and deliver record entry content in a particular form and manner.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  restoreRestore Record Lifecycle EventOccurs when an agent causes the system to recreate record entries and their content from a previous created archive artefact.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  transformTransform/Translate Record Lifecycle EventOccurs when an agent causes the system to change the form, language or code system used to represent record entry content.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  transmitTransmit Record Lifecycle EventOccurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  unlinkUnlink Record Lifecycle EventOccurs when an agent causes the system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  unmergeUnmerge Record Lifecycle EventOccurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again.
    http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle  verifyVerify 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.

    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