Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-object-lifecycle-events-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 3 | Responsible: Security | Computable Name: R3ObjectLifecycleEventsForR4 | |
| This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/object-lifecycle-events | 1.1.0 for use in FHIR R4 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/object-lifecycle-events|4.0.1. |
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/object-lifecycle-events|1.1.0 as defined in FHIR STU3
in FHIR R4.
The source value set is bound to the following FHIR STU3 elements:
AuditEvent.entity.lifecycleNote that there are 30 concepts not included in this cross-version definition because they have valid representations.
Following are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source value set has fewer active concepts (40) than the target (42), so the source is narrower than the target.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/iso-21089-lifecycle version 📍3.0.2| Code | Display | Definition |
| 1 | Originate/Retain - Record Lifecyle Event | occurs 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 |
| 10 | De-Identify (Anononymize) - Lifecycle Event | occurs 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 |
| 11 | Pseudonymize - Lifecycle Event | occurs 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 |
| 12 | Re-identify - Lifecycle Event | occurs when an agent causes the system to restore information to data that allows identification of information source and/or information subject |
| 13 | Extract - Lifecycle Event | occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria |
| 14 | Archive - Lifeycle Event | occurs when an agent causes the system to create and move archive artifacts containing record entry content, typically to long-term offline storage |
| 15 | Restore - Lifecycle Event | occurs when an agent causes the system to recreate record entries and their content from a previous created archive artifact |
| 16 | Destroy/Delete - Lifecycle Event | occurs when an agent causes the system to permanently erase record entry content from the system |
| 17 | Deprecate - Lifecycle Event | occurs when an agent causes the system to tag record entry(ies) as obsolete, erroneous or untrustworthy, to warn against its future use |
| 18 | Re-activate - Lifecycle Event | occurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated |
| 19 | Merge - Lifecycle Event | occurs when an agent causes the system to combine or join content from two or more record entries, resulting in a single logical record entry |
| 2 | Amend (Update) - Lifeycle Event | occurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent) |
| 20 | Unmerge - Lifecycle Event | occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again |
| 21 | Link - Lifecycle Event | occurs when an agent causes the system to connect related record entries |
| 22 | Unlink - Lifecycle Event | occurs when an agent causes the system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again |
| 24 | Remove Legal Hold - Lifecycle Event | occurs 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†|
| 25 | Verify - Lifecycle Event | occurs 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 |
| 26 | Encrypt - Lifecycle Event | occurs when an agent causes the system to encode record entry content in a cipher |
| 27 | Decrypt - Lifecycle Event | occurs when an agent causes the system to decode record entry content from a cipher |
| 3 | Transform/Translate - Lifecycle Event | occurs when an agent causes the system to change the form, language or code system used to represent record entry content |
| 4 | Attest - Lifecycle Event | occurs when an agent causes the system to capture the agent’s digital signature (or equivalent indication) during formal validation of record entry content |
| 6 | Report (Output) - Lifecycle Event | occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner |
| 7 | Disclose - Lifecycle Event | occurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content |
| 8 | Transmit - Lifecycle Event | occurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another |
| 9 | Receive/Retain - Lifecycle Event | occurs 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 |
This value set expansion contains 25 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 1 | Originate/Retain - Record Lifecyle Event | occurs 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://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 10 | De-Identify (Anononymize) - Lifecycle Event | occurs 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 | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 11 | Pseudonymize - Lifecycle Event | occurs 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://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 12 | Re-identify - Lifecycle Event | occurs when an agent causes the system to restore information to data that allows identification of information source and/or information subject | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 13 | Extract - Lifecycle Event | occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 14 | Archive - Lifeycle Event | occurs when an agent causes the system to create and move archive artifacts containing record entry content, typically to long-term offline storage | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 15 | Restore - Lifecycle Event | occurs when an agent causes the system to recreate record entries and their content from a previous created archive artifact | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 16 | Destroy/Delete - Lifecycle Event | occurs when an agent causes the system to permanently erase record entry content from the system | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 17 | Deprecate - Lifecycle Event | occurs when an agent causes the system to tag record entry(ies) as obsolete, erroneous or untrustworthy, to warn against its future use | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 18 | Re-activate - Lifecycle Event | occurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 19 | Merge - Lifecycle Event | occurs 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://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 2 | Amend (Update) - Lifeycle Event | occurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent) | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 20 | Unmerge - Lifecycle Event | occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 21 | Link - Lifecycle Event | occurs when an agent causes the system to connect related record entries | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 22 | Unlink - Lifecycle Event | occurs when an agent causes the system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 24 | Remove Legal Hold - Lifecycle Event | occurs 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://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 25 | Verify - Lifecycle Event | occurs 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 | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 26 | Encrypt - Lifecycle Event | occurs when an agent causes the system to encode record entry content in a cipher | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 27 | Decrypt - Lifecycle Event | occurs when an agent causes the system to decode record entry content from a cipher | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 3 | Transform/Translate - Lifecycle Event | occurs when an agent causes the system to change the form, language or code system used to represent record entry content | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 4 | Attest - Lifecycle Event | occurs when an agent causes the system to capture the agent’s digital signature (or equivalent indication) during formal validation of record entry content | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 6 | Report (Output) - Lifecycle Event | occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 7 | Disclose - Lifecycle Event | occurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 8 | Transmit - Lifecycle Event | occurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another | ||
http://hl7.org/fhir/iso-21089-lifecycle | 3.0.2 | 9 | Receive/Retain - Lifecycle Event | occurs 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 |
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 |