Difference between revisions of "Specimen Event Tracking"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "Specimen Event Tracking (SET) defines all data elements needed to describe and exchange data about any event that could happen to a specimen. __TOC__ ==Summary== ''<Describe...")
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
Specimen Event Tracking (SET) defines all data elements needed to describe and exchange data about any event that could happen to a specimen.
+
{| style="color: blue;"
 +
| '''This profile is part of the Pathology and Laboratory Medicine (PaLM) domain, which merged the former AP and LAB domains since 2016, January 4th.'''
 +
|}
 +
 
 +
'''Specimen Event Tracking (SET)''' profile is a project of the IHE PaLM Technical committee that was started in 2016. The purpose of this new profile of the PaLM domain is to define a series of use cases and all related events relevant to be tracked, when one or more macro operations involving a specimen occur (i.e., container preparation, collection, movement from one facility to another one, archiving, and so on).  
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
−
''<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''
+
The Specimen Event Tracking (SET) profile covers use cases and transactions related to the tracking of biological specimens in vitro collected for the purpose of diagnostic testing, during their entire lifecycle, from creation to storage inside a laboratory specimen archive or a biobank for future usage, and to final disposal. Specimen workflows can involve a ward and a laboratory in the same hospital, different laboratory facilities inside the same institution, or across different institutions. In the latter case, specimens need to be transferred by a courier service from the sending institution to the receiving institution. Another important use case to be tracked is the specimen creation for the specific purpose of becoming part of a biobank for a research institution or program.
 +
The SET profile tracks macro activities related to specimens, such as collecting, shipping, receiving, accepting... Micro operations part of a macro activity (e.g. decapping a tube) are out of scope of the profile.
 +
<br/>
 +
For most recent information on the SET please see:  http://wiki.ihe.net/index.php/Pathology_and_Laboratory_Medicine_(PaLM)#Current_Activity.
 +
<br/>
 +
<br/>
 +
   
 +
[[File:SET_main_profile_image.jpg|center|]]
 +
 
 +
''Figure 1 - Some of the main events that might occur to a Specimen during its overall lifecycle, and that the SET profile aims to track. Traceability messages are collected at each step by an Informer entity and sent to a tracker entity (repository). Notice that, according to the use case, the trackers may be more than one, if the Collecting Facility and the Laboratory have independent tracking environments.
 +
''
  
−
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+
==Benefits==
 +
* Keep under control the chain-of-custody of the specimen, when operation addressed by all the other profiles occur to the specimen
 +
* Prevent specimen loss, opportunity to raise alerts if some exceptions occurs to the process (i.e., broken container, specimen collection unavailable)
 +
* All events might be collected in a single place and use to improve the overall process
  
−
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
 
  
−
==Benefits==
 
−
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
 
  
 
==Details==
 
==Details==
 +
Four main use cases have been identified for the SET profile, according to the main operation that might be tracked for a specimen, in different contexts:
  
−
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
# Container Delivery and Specimen Collection Tracking
 +
# Specimen Inter and Intra organization transfer
 +
# Specimen tracking within the Laboratory
 +
# Biobank Specimen Tracking
 +
 
 +
Each of these use cases describes a scenario where one or more macro-operations might occur to the specimen. For each operation, a correspondent event is tracked by the SET profile. An event is composed of common attributes and specific attributes. For example, all events carry the specimen identifier and the timestamp of occurrence, while only “movement related” events carry information about the departure and the arrival facilities.
 +
The SET Profile defines a total of 15 different types of events, which in turn are divided into 4 macro-categories, as shown in the following table:
 +
 
 +
 
 +
{| class="wikitable" style="margin: auto;"
 +
!colspan="2"|SET Events List
 +
|-
 +
|rowspan="3"|Tracking specimen container preparation and specimen collection events
 +
|Containers Prepared For Specimen Collection
 +
|-
 +
|Specimen Collection Succeeded
 +
|-
 +
|Specimen Collection Failed
 +
|-
 +
|rowspan="7"|Tracking specimen movements events
 +
|Specimen Departed
 +
|-
 +
|Specimen Arrived
 +
|-
 +
|Specimen Accepted
 +
|-
 +
|Specimen Rejected
 +
|-
 +
|Specimen Archived
 +
|-
 +
|Specimen Retrieved from Archive
 +
|-
 +
|Specimen Disposed Of
 +
|-
 +
|Tracking specimen identification events
 +
|Specimen Identifier Changed
 +
|-
 +
|rowspan="3"|Tracking specimen processing events
 +
|Specimen Procedure Step Successfully Produced a Derived Specimen
 +
|-
 +
|Specimen Procedure Step Succeeded (with no derived specimen)
 +
|-
 +
|Specimen Procedure Step Failed
 +
|}
  
−
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
 
  
−
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 
 
   
 
   
 
==Systems Affected==
 
==Systems Affected==
−
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+
All systems where an operation to a Specimen occurs are expected to implement this profile.  
−
 
 
−
* ''PACS systems may store, manage, and/or display Evidence Documents.''
 
−
* ''Display systems may query, retrieve and display Evidence Documents.''
 
−
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
 
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
 +
From a point of view of the Actors diagram, a Specimen Event Informer (SEI) actor is defined. This actor is paired with the system where the specimen operation occurs. For example, if the operation is related to the production of the labelled containers for the specimen, the SEI will be paired with a labeling machine.
 +
The Actors and the Interactions diagrams are depicted in Fig. 2:
 +
<br/>
 +
<br/>
  
−
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[File:Actors_and_transactions_SET_diagrams.jpg|center ]]
  
−
==Specification==
+
''Figure 2 - Actors (on the left) and Interactions (on the right) diagrams for the SET Profile
 +
''
  
−
'''Profile Status:''' [[Comments| Final Text]] 
 
−
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
−
'''Documents:'''
+
==Specification==
  
−
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+
*'''Profile Status:''' Published for public comment in the period from August 27 through September 27, 2021
 +
*'''Documents:''' [https://www.ihe.net/uploadedFiles/Documents/PaLM/IHE_PaLM_Suppl_SET_Rev1-0_PC_2021-08-27.pdf SET profile proposal (Public comment version)]
 +
*'''Important Note:''' HL7 v2 has been identified as the underlying standard to use. The tracking event information that the HL7v2 message shall carry on strictly depends on the related event type: for example, tracking container preparation for a specimen needs different information than tracking specimen movements or specimen identification. The HL7 v2 messaging standard does not provide a message type that satisfies the needs of all SET event types. For this reason, a CR proposal has been submitted to the HL7 Orders and Observation group, defining a new set of HL7 v2 messages that are specific for Specimen traceability. The last version of the CR proposal is available [https://drive.google.com/file/d/16xqPCiuQem4uJnr-qy6Q9W0vOz8lbyhk/view?usp=sharing here]
  
−
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+
<!--Link to SET matrix with collection of all data elements per use case: https://wiki.ihe.net/index.php/File:2019_01_SET_new_mapping_structure_pre_HL7_call.xlsx
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
−
''<list all the standards on which the profile is based; if possible with links to sources>''
+
:* HL7 v2 - (New messages proposed) [http://www.hl7.org HL7]
−
:* [http://dicom.nema.org DICOM]
 
−
:* [http://www.hl7.org HL7]
 
 
:* ...
 
:* ...
  
Line 62: Line 114:
 
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
 
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
  
−
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
* ''<to be updated[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.>''
−
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
−
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
−
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
−
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
  
  
Line 90: Line 138:
  
 
[[Category:HL7v2]]
 
[[Category:HL7v2]]
 +
-->

Revision as of 09:53, 8 September 2021

This profile is part of the Pathology and Laboratory Medicine (PaLM) domain, which merged the former AP and LAB domains since 2016, January 4th.

Specimen Event Tracking (SET) profile is a project of the IHE PaLM Technical committee that was started in 2016. The purpose of this new profile of the PaLM domain is to define a series of use cases and all related events relevant to be tracked, when one or more macro operations involving a specimen occur (i.e., container preparation, collection, movement from one facility to another one, archiving, and so on).

Summary

The Specimen Event Tracking (SET) profile covers use cases and transactions related to the tracking of biological specimens in vitro collected for the purpose of diagnostic testing, during their entire lifecycle, from creation to storage inside a laboratory specimen archive or a biobank for future usage, and to final disposal. Specimen workflows can involve a ward and a laboratory in the same hospital, different laboratory facilities inside the same institution, or across different institutions. In the latter case, specimens need to be transferred by a courier service from the sending institution to the receiving institution. Another important use case to be tracked is the specimen creation for the specific purpose of becoming part of a biobank for a research institution or program. The SET profile tracks macro activities related to specimens, such as collecting, shipping, receiving, accepting... Micro operations part of a macro activity (e.g. decapping a tube) are out of scope of the profile.
For most recent information on the SET please see: http://wiki.ihe.net/index.php/Pathology_and_Laboratory_Medicine_(PaLM)#Current_Activity.

SET main profile image.jpg

Figure 1 - Some of the main events that might occur to a Specimen during its overall lifecycle, and that the SET profile aims to track. Traceability messages are collected at each step by an Informer entity and sent to a tracker entity (repository). Notice that, according to the use case, the trackers may be more than one, if the Collecting Facility and the Laboratory have independent tracking environments.

Benefits

  • Keep under control the chain-of-custody of the specimen, when operation addressed by all the other profiles occur to the specimen
  • Prevent specimen loss, opportunity to raise alerts if some exceptions occurs to the process (i.e., broken container, specimen collection unavailable)
  • All events might be collected in a single place and use to improve the overall process


Details

Four main use cases have been identified for the SET profile, according to the main operation that might be tracked for a specimen, in different contexts:

  1. Container Delivery and Specimen Collection Tracking
  2. Specimen Inter and Intra organization transfer
  3. Specimen tracking within the Laboratory
  4. Biobank Specimen Tracking

Each of these use cases describes a scenario where one or more macro-operations might occur to the specimen. For each operation, a correspondent event is tracked by the SET profile. An event is composed of common attributes and specific attributes. For example, all events carry the specimen identifier and the timestamp of occurrence, while only “movement related” events carry information about the departure and the arrival facilities. The SET Profile defines a total of 15 different types of events, which in turn are divided into 4 macro-categories, as shown in the following table:


SET Events List
Tracking specimen container preparation and specimen collection events Containers Prepared For Specimen Collection
Specimen Collection Succeeded
Specimen Collection Failed
Tracking specimen movements events Specimen Departed
Specimen Arrived
Specimen Accepted
Specimen Rejected
Specimen Archived
Specimen Retrieved from Archive
Specimen Disposed Of
Tracking specimen identification events Specimen Identifier Changed
Tracking specimen processing events Specimen Procedure Step Successfully Produced a Derived Specimen
Specimen Procedure Step Succeeded (with no derived specimen)
Specimen Procedure Step Failed


Systems Affected

All systems where an operation to a Specimen occurs are expected to implement this profile.

Actors & Transactions: From a point of view of the Actors diagram, a Specimen Event Informer (SEI) actor is defined. This actor is paired with the system where the specimen operation occurs. For example, if the operation is related to the production of the labelled containers for the specimen, the SEI will be paired with a labeling machine. The Actors and the Interactions diagrams are depicted in Fig. 2:

Actors and transactions SET diagrams.jpg

Figure 2 - Actors (on the left) and Interactions (on the right) diagrams for the SET Profile


Specification

  • Profile Status: Published for public comment in the period from August 27 through September 27, 2021
  • Documents: SET profile proposal (Public comment version)
  • Important Note: HL7 v2 has been identified as the underlying standard to use. The tracking event information that the HL7v2 message shall carry on strictly depends on the related event type: for example, tracking container preparation for a specimen needs different information than tracking specimen movements or specimen identification. The HL7 v2 messaging standard does not provide a message type that satisfies the needs of all SET event types. For this reason, a CR proposal has been submitted to the HL7 Orders and Observation group, defining a new set of HL7 v2 messages that are specific for Specimen traceability. The last version of the CR proposal is available here


Retrieved from "http://wiki.ihe.net/index.php?title=Specimen_Event_Tracking&oldid=126037"