FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). 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.2.12.null Code System http://hl7.org/fhir/iso-21089-lifecycle

Vocabulary Work Group Maturity Level: 0InformativeUse Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/iso-21089-lifecycle
Name:ISO 21089-2017 Health Record Lifecycle Events
Definition:Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication). This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.
Committee:??
OID: (for OID based terminology systems)
Copyright:These codes are excerpted from ISO Standard, TS 21089-2017 - Health Informatics - Trusted End-to-End Information Flows, Copyright by ISO International. Copies of this standard are available through the ISO Web Site at www.iso.org.
Source ResourceXML / JSON

This Code system is not currently used

Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication). This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.

Copyright Statement: These codes are excerpted from ISO Standard, TS 21089-2017 - Health Informatics - Trusted End-to-End Information Flows, Copyright by ISO International. Copies of this standard are available through the ISO Web Site at www.iso.org.

This code system http://hl7.org/fhir/iso-21089-lifecycle defines the following codes:

CodeDisplayDefinition
2 Amend (Update) - Lifeycle Eventoccurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent)
14 Archive - Lifeycle Eventoccurs when an agent causes the system to create and move archive artifacts containing record entry content, typically to long-term offline storage
4 Attest - 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
27 Decrypt - Lifecycle Eventoccurs when an agent causes the system to decode record entry content from a cipher
10 De-Identify (Anononymize) - 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 may or may not be reversible
17 Deprecate - Lifecycle Eventoccurs when an agent causes the system to tag record entry(ies) as obsolete, erroneous or untrustworthy, to warn against its future use
16 Destroy/Delete - Lifecycle Eventoccurs when an agent causes the system to permanently erase record entry content from the system
7 Disclose - Lifecycle Eventoccurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content
26 Encrypt - Lifecycle Eventoccurs when an agent causes the system to encode record entry content in a cipher
13 Extract - Lifecycle Eventoccurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria
21 Link - Lifecycle Eventoccurs when an agent causes the system to connect related record entries
19 Merge - 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
1 Originate/Retain - Record Lifecyle 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
11 Pseudonymize - 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
18 Re-activate - Lifecycle Eventoccurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated
9 Receive/Retain - Lifecycle Eventoccurs when an agent causes the system to: a) initiate capture of data content from elseware, and b) incorporate that content into the storage considered a permanent part of the health record
6 Report (Output) - Lifecycle Eventoccurs when an agent causes the system to produce and deliver record entry content in a particular form and manner
12 Re-identify - Lifecycle Eventoccurs when an agent causes the system to restore information to data that allows identification of information source and/or information subject
24 Remove Legal Hold - 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”
15 Restore - Lifecycle Eventoccurs when an agent causes the system to recreate record entries and their content from a previous created archive artifact
3 Transform/Translate - Lifecycle Eventoccurs when an agent causes the system to change the form, language or code system used to represent record entry content
8 Transmit - Lifecycle Eventoccurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another
22 Unlink - Lifecycle Eventoccurs when an agent causes the system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again
20 Unmerge - Lifecycle Eventoccurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again
25 Verify - 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:

LevelA 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
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