Stream: terminology
Topic: ISO lifecycle events
John Moehrke (May 17 2019 at 19:13):
Is there a FHIR CodeSystem that represents ISO/HL7 10781 lifecycle events? This is not the same as the ISO 21089 lifecycle events, nor the HL7 v2/v3 lifecycle events.
Grahame Grieve (May 17 2019 at 22:29):
then I don't think I have made one for that
John Moehrke (May 18 2019 at 13:38):
Is there a specific way to do that with ISO terminology?
Grahame Grieve (May 18 2019 at 21:50):
copy the way I did it for the other ISO terminologies?
John Moehrke (May 20 2019 at 13:25):
so, ISO is not being nice like DICOM and IHE are? okay, I guess the hard work will need to be done.
Grahame Grieve (May 20 2019 at 13:31):
no whatever is done, we do.
John Moehrke (Jul 30 2020 at 17:16):
Is there any movement on getting this available for the FHIR core build? It has been asked to include these codes in the valueSet with the other lifecycle events. (FHIR-24907). Those that use these codes do not want to be forced to convert to one of the other lifecycle codeSystems.
Grahame Grieve (Jul 30 2020 at 21:29):
no progress on my part. what's the license?
John Moehrke (Jul 31 2020 at 14:56):
I don't know, or know how to answer that. I simply have a CR asking for it. If the terminology gods want to tell me that licensing prevents it, then that is a fine solution.
Robert McClure (Jul 31 2020 at 16:40):
@John Moehrke Is the set of codes defined for lifecycle events listed in the HL7 specification someplace? Or did ISO do something different with HL7 EHR-System Functional Model, R2 that added the content you want?
John Moehrke (Jul 31 2020 at 16:42):
I don't know, I don't have access to the ISO specification. All I know is "ISO/HL7 10781 lifecycle". are these available inside HL7? I couldn't find them, but I am not good at finding vocabulary.. (word fail me all the time)
Robert McClure (Jul 31 2020 at 17:58):
I don't have the ISO spec either but my assumption is that the ISO publication is exactly the same as the HL7 publication, but I'll admit that sounds foolish. And I agree, I do not think the EHR-S FM defines any specific terminology (hence a functional model). I'll ask HQ but perhaps we need to get more info on the source and use-case leading to the need for this "terminology." I will say there are references in the EHR-S FM to "record lifecycle" and they list "origination, attestation, amendment, access/use, translation, transmittal/disclosure, receipt, de- identification, archive..." but that is apparently not exhaustive nor is it official. It also has "Lifecycle Events include originate, retain, amend, verify, attest, access/view, de-identify, transmit/receive, and more." I suspect you may be looking for something that was alluded to in EHR-S FM (ISO 10781:2015) but not officially defined there. Can you ask the EHR group @Gary Dickinson ?
John Moehrke (Jul 31 2020 at 21:47):
Gary has provided me a draft of the ISO specification. But I have no idea to what extent I can share that, nor if it is sufficient to define a vocabulary. At that time, when life was less complex with licensing issues, I was simply going to do the data entry into a FHIR codeSystem resource myself. But now I am afraid to do that.
Grahame Grieve (Jul 31 2020 at 21:47):
you should do that anyway. The question is where we put it.
Grahame Grieve (Jul 31 2020 at 21:49):
I see a bunch of emails that went nowhere...
Grahame Grieve (Jul 31 2020 at 21:49):
we'll put it in the terminology support package and deal with any issues this creates later
John Moehrke (Jul 31 2020 at 21:50):
so, I should use the draft spec I have, and make a codeSystem file... and give that file to you?
Grahame Grieve (Jul 31 2020 at 21:50):
yes
John Moehrke (Jul 31 2020 at 22:43):
my draft is 2007. nothing resembling a lifecycle vocabulary.
Robert McClure (Aug 03 2020 at 17:03):
@Gary Dickinson Has also provided a glossary pdf to me from an unknown document (pgs 36-37) that seems to have the code system. I've sent him an email to try and clarify and @Grahame Grieve , @John Moehrke are cc'd. I hope we can bring this to closure soon.
Vassil Peytchev (Aug 03 2020 at 18:50):
I think what this is referring to is the reference from the EHR-S FM version 2 (ISO-10781) to ISO 21089. The publicly available details of the 2018 version lists the following:
15.1.2 Record lifecycle event — Originate/retain record entry instance(s)
15.3 Record lifecycle event — Transform/translate
15.4 Record lifecycle event — Attest
15.5 Record lifecycle event — Access/view
15.6 Record lifecycle event — Report (output)
15.7 Record lifecycle event — Disclose
15.8 Record lifecycle event — Transmit
15.9 Record lifecycle event — Receive/retain
15.10 Record lifecycle event — De-identify (anonymize)
15.11 Record lifecycle event — Pseudonymize
15.12 Record lifecycle event — Re-identify
15.13 Record lifecycle event — Extract
15.14 Record lifecycle event — Archive
15.15 Record lifecycle event — Restore (from archive)
15.16 Record lifecycle event — Destroy/delete
15.17 Record lifecycle event — Deprecate
15.18 Record lifecycle event — Reactivate (from delete or deprecate)
15.19 Record lifecycle event — Merge
15.20 Record lifecycle event — Unmerge
15.21 Record lifecycle event — Link
15.22 Record lifecycle event — Unlink
15.23 Record lifecycle event — Add legal hold
15.24 Record lifecycle event — Remove legal hold
15.25 Record lifecycle event — Verify
John Moehrke (Aug 03 2020 at 19:32):
@Vassil Peytchev do you just happen to have the details captured in a FHIR CodeSystem resource?
Vassil Peytchev (Aug 03 2020 at 20:17):
Unfortunately, I don't.
John Moehrke (Jan 04 2021 at 15:06):
Starting off 2021 optimistic that a conclusion will happen on this one. What is the go forward plan for this one? @Gary Dickinson can you help?
Gary Dickinson (Jan 04 2021 at 15:23):
Record Lifecycle Events are now incorporated in the FHIR Record Lifecycle Event Implementation Guide (http://hl7.org/fhir/ehrsrle/ehrsrle.html) (noting that there is an error in the description for RLE #11) and the FHIR RLE Code Set (https://terminology.hl7.org/1.0.0/CodeSystem-iso-21089-lifecycle.html). They are also incorporated in ISO 21089:2018 Health Informatics - Trusted End-to-End Information Flows, ISO/HL7 10781 EHR System Functional Model Release 2.1 (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=528), ISO/HL7 16527 PHR System Functional Model Release 2 (awaiting final publication at HL7).
John Moehrke (Jan 04 2021 at 15:54):
@Gary Dickinson I am confused. I thought the ask was for 10781... not 21089... If they are the same thing, then we can stop... but I have a CR from you explicitly asking for 10781
see https://jira.hl7.org/browse/FHIR-24907
John Moehrke (Jan 04 2021 at 15:55):
given that I don't have access to ISO specifications, due to paywall... I can't evaluate anything other than the numbers 21089 are not equal to 10781. If they are equal, then I can close this as done.
John Moehrke (Jan 04 2021 at 15:57):
what is the codeSystem.system value of this code system? Most of the problem is that we keep referring to specification numbers, not vocabulary managed systems.
John Moehrke (Mar 22 2021 at 13:55):
@Gary Dickinson and vocab leadership... this is a specific confusion on ISO lifecycle events. I would be happy to close the CR as not being needed, but I can't confirm. See my last few questions to Gary
Gary Dickinson (Apr 01 2021 at 00:57):
Here is the full current record lifecycle event list, as incorporated in ISO 21089:2018 (Trusted end-to-end information flows), in alphabetical order with number sequence:
(5) Access/View - Lifecycle Event
occurs when an agent causes the system to obtain and open a record entry for inspection or review
(23) Add Legal Hold - Lifecycle Event
occurs 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”
(2) Amend (Update) - Lifeycle Event
occurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent)
(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
(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
(27) Decrypt – Lifecycle Event
occurs when an agent causes the system to decode record entry content from a cipher
(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
(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
(16) Destroy/Delete – Lifecycle Event
occurs when an agent causes the system to permanently erase record entry content from the system
(7) Disclose – Lifecycle Event
occurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content
(26) Encrypt – Lifecycle Event
occurs when an agent causes the system to encode record entry content in a cipher
(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
(21) Link – Lifecycle Event
occurs when an agent causes the system to connect related record entries
(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
(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
(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
(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
(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
(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
(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
(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”
(15) Restore – Lifecycle Event
occurs when an agent causes the system to recreate record entries and their content from a previous created archive artifact
(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
(8) Transmit – Lifecycle Event
occurs when an agent causes the system to send record entry content from one (EHR/PHR/other) system to another
(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
(20) Unmerge – Lifecycle Event
occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again
(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
Last updated: Apr 12 2022 at 19:14 UTC
