Difference between revisions of "Anatomic Pathology Workflow"

From IHE Wiki
Jump to navigation Jump to search
(New page: '''Pathology Workflow (PWF)''' integrates the pathology department in the healthcare institution, and covers these specialties: surgical pathology, clinical autopsy, cytopathology. __TOC...)
 
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
'''Pathology Workflow (PWF)''' integrates the pathology department in the healthcare institution, and covers these specialties: surgical pathology, clinical autopsy, cytopathology.
+
{| 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.'''
 +
|}
 +
'''Anatomic Pathology Workflow (APW)''' integrates the pathology department in the healthcare institution, and covers these specialties: surgical pathology, clinical autopsy, cytopathology.
  
 
__TOC__
 
__TOC__
Line 7: Line 9:
 
==Summary==
 
==Summary==
  
−
The Pathology Workflow Integration Profile establishes the continuity and integrity of basic pathology data acquired during examinations ordered for an identified inpatient or outpatient. This profile covers three main aspects of the workflow:
+
APW establishes the continuity and integrity of basic pathology data acquired during examinations ordered for an identified inpatient or outpatient. This profile covers three main aspects of the workflow:
−
* '''The ordering aspects of the workflow''' - The PWF profile specifies a number of transactions to maintain the consistency of ordering information and specimen management information.
+
* '''The ordering aspects of the workflow''' - APW specifies a number of transactions to maintain the consistency of ordering information and specimen management information.
−
* '''The reporting aspects of the workflow''' - The PWF profile specifies a number of transactions to create and store observations and reports outside the Pathology department and to maintain the consistency of these results.
+
* '''The reporting aspects of the workflow''' - APW specifies a number of transactions to create and store observations and reports outside the Pathology department and to maintain the consistency of these results.
−
* T'''he imaging aspects of the workflow''' - The PWF profile specifies a number of transactions to create and store images and to maintain the consistency of these images. Worklists for image acquisition is generated and can be queried. This Integration Profile also describes evidence creation.
+
* T'''he imaging aspects of the workflow''' - APW specifies a number of transactions to create and store images and to maintain the consistency of these images. Worklists for image acquisition is generated and can be queried. This Integration Profile also describes evidence creation.
  
 
<center>[[Image:Ihe_pat_pwf_ip_last.jpg]]</center>
 
<center>[[Image:Ihe_pat_pwf_ip_last.jpg]]</center>
Line 23: Line 25:
 
==Details==
 
==Details==
  
−
The '''''Pathology Workflow (PWF) Integration Profile''''' is bound to in vitro diagnostic testing (tests performed on in vitro specimen collected from a patient). It supports all laboratory specialties but anatomic pathology.
+
The scope of this profile includes surgical pathology, biopsies pathology, cytopathology, autopsies, and related techniques (immunohistochemistry, molecular pathology, etc).
  
 
'''Use cases:'''<br/>
 
'''Use cases:'''<br/>
−
The LTW Integration Profile covers three major use cases:
+
This profile supports 5 major use cases:
−
* Order placed with specimens collected and identified by the orderer
+
* Use case 1: Surgical pathology – Operative specimen
−
* Order placed with specimens collected by a third party, then identified and labeled by the laboratory information system
+
* Use case 2: Surgical pathology – Biopsies
−
* Order generated by the laboratory and notified to the ordering system to obtain an order number.
+
* Use case 3: Cytology
 +
* Use case 4: Autopsy
 +
* Use case 5: Tissue Micro Array (more than one specimen from more than one patient per container)
  
−
'''Transactions:'''<br/>
+
This profile leverages IT Infrastructure profiles [PAM] for sharing up to date patient and encounter data, and [ATNA] and [CT] for security.
−
LTW Integration Profile defines 5 Transactions, all of which based on HL7 release 2.5 or 2.5.1 messaging standard. Each transaction selects a subset of HL7 message structures (based on OML, ORL, ORU and OUL) and specifies a set of constraints applying to each message structure, as well as the responsibilities of the sender and receiver.
 
−
 
 
−
This profile leverages IT Infrastructure profiles [PAM] or [PDQ] for up to date patient and encounter data, and IT Infrastructure profiles [ATNA] and [CT] for security.
 
−
 
 
−
'''Units of work:'''<br/>
 
−
A laboratory request ordered by a physician for a patient is frequently composed of multiple tests and panels placed to a laboratory. Such a '''laboratory request''' containing several orders is called an '''Order Group''' in the HL7 standard, and uniquely identified by the ordering CIS with a '''Placer Group Number'''. Each of the orders is in turn uniquely identified by the CIS with a '''Placer Order Number'''. Each order accepted by the laboratory as well as each reflex order generated by the laboratory is uniquely identified by the LIS with a '''Filler Order Number'''.<br/>
 
  
 
==Systems Affected==
 
==Systems Affected==
Line 43: Line 41:
 
Systems involved in this profile are:
 
Systems involved in this profile are:
  
−
* One or more Clinical Information Systems ('''CIS'''). Each of these systems is operated by a clinical facility and provides a number of features such as order entry, order placing, placer order management and follow-up, order result tracking, management of patient biologic history, specimen calculation, specimen identification... A CIS usually implements the Actors Order Placer and Order Result Tracker.
+
* The hospital Clinical Information System
−
* One or more Laboratory Information Systems ('''LIS'''). Each of these systems is operated by a number of clinical laboratories inside the institution. The LIS offers features such as order reception, specimen calculation, specimen identification or specimen acceptance, order check, scheduling, filler order management, production of worklists, result manual entry for non connected-tests, clinical validation and interpretation of results, result reporting. Each LIS implements an Order Filler Actor.
+
* The system of the pathology laboratory
−
* One or more Laboratory Automation Systems ('''LAS''') operated in each laboratory. A LAS manages a set of automated laboratory devices (pre-analytical devices, analyzers, post-analytical devices). The LAS receives Work Orders related to a specimen and processes the various steps of a WSork Order on its set of devices, to eventually get the test results, perform the technical validation thereof, and upload them back to the LIS.<br/>
+
* Imaging modalities
 +
* Multimodalities
 +
 
  
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
<center>[[Image:ltw-actor-transaction.JPG]]</center>
+
<center>[[Image:pwf-actor-transaction.JPG]]</center>
 
<br/>
 
<br/>
  
Line 57: Line 57:
 
'''Profile Status:''' [[Comments| Trial Implementation]]   
 
'''Profile Status:''' [[Comments| Trial Implementation]]   
  
−
'''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:]
+
'''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#pathology IHE Pathology Technical Framework:]
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_lab_tf_rel2.pdf Vol. 1] - Section 4 (LTW profile overview)
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_PAT_TF_Rev2-0_Vol1_TI_2010-07-23.pdf Vol. 1 Rev 2.0]
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_lab_tf_rel2-2.pdf Vol. 2] - Sections 4 through 8 (LTW transactions descriptions)
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_PAT_TF_Rev2-0_Vol2_TI_2010-07-23.pdf Vol. 2 Rev 2.0]
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
Line 67: Line 67:
 
'''Related Profiles'''
 
'''Related Profiles'''
  
−
* '''Integration Profiles LTW depends on'''
+
* '''Integration Profiles APW depends on'''
−
:* [[Patient Administration Management]] (PAM) and/or [[Patient Demographics Query]] (PDQ) provide accurate patient demographics used by LTW: An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actors Patient Demographics Consumer and Patient Encounter Consumer from either '''PAM''' or '''PDQ''' Profile or both.
+
:* [[Patient Administration Management]] (PAM) provides accurate patient demographics to APW actors: An application implementing one of the Actors ''Order Placer'', ''Order Result Tracker'', ''Order Filler'' shall also implement the Actors ''Patient Demographics Consumer'' and ''Patient Encounter Consumer'' from the '''PAM''' profile.
  
−
:* [[Audit_Trail_and_Node_Authentication]] (ATNA) to audit creation and access to patient data during LTW. An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actor Secure Node from  '''ATNA'''.
 
−
:* [[Consistent_Time]] (CT) to ensure timestamps in LTW data and audit messages are accurate.
 
  
−
* '''Integration Profiles depending upon LTW'''
+
* '''Integration Profiles depending upon PWF'''
−
:* [[Laboratory_Device_Automation]] (LDA) from the Laboratory Technical Framework: The Actor Automation Manager from the LDA Profile must also be an Automation Manager in the LTW Profile.
+
 
−
:* [[Laboratory_Point_Of_Care_Testing]] (LPOCT) from the Laboratory Technical Framework: The Actor Order Filler from the Laboratory LPOCT Profile must also be an Order Filler in the LTW Profile.
 
−
:* [[Laboratory_Barcode_Labeling]] (LBL) from the Laboratory Technical Framework: The Label Information Provider Actor of the LBL profile shall be grouped with either the Order Filler or the Order Placer from the LTW profile.
 
  
 
'''Consumer Information'''
 
'''Consumer Information'''
  
 
This page is based on the [[Profile Template]]
 
This page is based on the [[Profile Template]]
−
 
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:PaLM Profile]]
 +
[[Category:HL7v2]]
 +
[[Category:DICOM]]

Latest revision as of 10:43, 8 April 2020

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

Anatomic Pathology Workflow (APW) integrates the pathology department in the healthcare institution, and covers these specialties: surgical pathology, clinical autopsy, cytopathology.


Summary

APW establishes the continuity and integrity of basic pathology data acquired during examinations ordered for an identified inpatient or outpatient. This profile covers three main aspects of the workflow:

  • The ordering aspects of the workflow - APW specifies a number of transactions to maintain the consistency of ordering information and specimen management information.
  • The reporting aspects of the workflow - APW specifies a number of transactions to create and store observations and reports outside the Pathology department and to maintain the consistency of these results.
  • The imaging aspects of the workflow - APW specifies a number of transactions to create and store images and to maintain the consistency of these images. Worklists for image acquisition is generated and can be queried. This Integration Profile also describes evidence creation.
Ihe pat pwf ip last.jpg


Benefits

Reduces Errors and Enhances Patient Care

  • Prevents manual data entry errors by ensuring that each piece of information is entered only once, by the person closest to the source of this information, and from there, made available in due time to any system who needs it.


Details

The scope of this profile includes surgical pathology, biopsies pathology, cytopathology, autopsies, and related techniques (immunohistochemistry, molecular pathology, etc).

Use cases:
This profile supports 5 major use cases:

  • Use case 1: Surgical pathology – Operative specimen
  • Use case 2: Surgical pathology – Biopsies
  • Use case 3: Cytology
  • Use case 4: Autopsy
  • Use case 5: Tissue Micro Array (more than one specimen from more than one patient per container)

This profile leverages IT Infrastructure profiles [PAM] for sharing up to date patient and encounter data, and [ATNA] and [CT] for security.

Systems Affected

Systems involved in this profile are:

  • The hospital Clinical Information System
  • The system of the pathology laboratory
  • Imaging modalities
  • Multimodalities


Actors & Transactions:

Pwf-actor-transaction.JPG


Specification

Profile Status: Trial Implementation

Documents: IHE Pathology Technical Framework:

Underlying Standards:

See Also

Related Profiles

  • Integration Profiles APW depends on
  • Patient Administration Management (PAM) provides accurate patient demographics to APW actors: An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actors Patient Demographics Consumer and Patient Encounter Consumer from the PAM profile.


  • Integration Profiles depending upon PWF


Consumer Information

This page is based on the Profile Template

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