Difference between revisions of "Scheduled Workflow"

From IHE Wiki
Jump to navigation Jump to search
m
(20 intermediate revisions by 3 users not shown)
Line 9: Line 9:
 
Scheduled Workflow establishes a seamless flow of information that supports efficient patient care workflow in a typical imaging encounter. It specifies transactions that maintain the consistency of patient information from registration through ordering, scheduling, imaging acquisition, storage and viewing. This consistency is also the foundation for subsequent workflow steps, such as reporting.  
 
Scheduled Workflow establishes a seamless flow of information that supports efficient patient care workflow in a typical imaging encounter. It specifies transactions that maintain the consistency of patient information from registration through ordering, scheduling, imaging acquisition, storage and viewing. This consistency is also the foundation for subsequent workflow steps, such as reporting.  
  
<center>[[Image:Ihe_rad_swf_ip.jpg]]</center>
+
<center>[[Image:Swf-v4.jpg]]</center>
  
 
==Benefits==
 
==Benefits==
Line 15: Line 15:
 
'''Reduce Errors and Enhance Patient Care'''
 
'''Reduce Errors and Enhance Patient Care'''
 
* Prevents manual data entry errors by ensuring that a particular piece of data is entered only once
 
* Prevents manual data entry errors by ensuring that a particular piece of data is entered only once
* Prevents complications from patient allergies or pregnancy status since these details are made available to all systems involved in the radiolgoy workflow
+
* Prevents complications from patient allergies or pregnancy status since these details are made available to all systems involved in the radiology workflow
 
* Prevents delays in patient care by making relevant information available at the point of care.
 
* Prevents delays in patient care by making relevant information available at the point of care.
 
'''Improve Throughput'''
 
'''Improve Throughput'''
Line 30: Line 30:
 
==Details==
 
==Details==
  
''<Editors NOTE: Raw material extracted from the User Handbook. Some additonal massaging is still needed.>''
+
The '''''Scheduled Workflow (SWF) Integration Profile''''':
 
+
* Establishes the continuity and integrity of basic departmental imaging data by profiling specific usage of HL7 messaging across multiple systems including: Patient registration (ADT), Order Placing (CPOE) and Order SCheduling (RIS) systems.
The SWF and PIR Profiles ensure that patient demographics and order and procedural information are correct and consistent. They allow images to be available for review in a timely fashion. Modality operators use the MWL to query and retrieve the relevant patient demographics and scheduled procedure information from the RIS. Patient name changes should not be made on the modality. The RIS is the primary information source and is capable of managing name updates, as long as the modality does not introduce additional unexpected changes. To ensure the most timely and correct patient information, the Worklist should be re-queried just before starting a new exam in case patient or order details have changed. The modality operator should verify that the right patient is selected for each examination.
+
* Bridges the gap between HL7-based systems (like RIS) and DICOM-based systems (like acquisition modalities and PACS) within the radiology department by specifying the semantic mappings between messages.
 
+
* Maintains the consistency of patient demographic and ordering information across multiple systems by making that information available to image acquisition modalities via the DICOM Modality Worklist (MWL) Service.  
In unscheduled cases (e.g., emergency patients), patient names and identification (ID) numbers may be unknown. As these are required to commence the procedure, they will need to be selected from a predefined list of temporary patient and names and IDs and entered at the modality. In such unscheduled cases, the AN, a key identifier for the imaging order, must be left blank. Later, when the correct patient ID, name and Accession Number are known, the RIS and the PACS will reconcile the image information with the correct values.
+
* Ensures that acquired images are not inadvertently lost by specifying that the DICOM Storage Commitment Service is used to transfer the custodianship of images from the modality to the PACS.
 +
* Ensures that the status of acquisition workflow steps are known throughout the department by specifying the use of the DICOM Modality Performed Procedure Step (MPPS) Service to convey that status from the modality to the RIS and the PACS.
  
 
==Systems Affected==
 
==Systems Affected==
Line 55: Line 56:
 
'''Documents:'''  
 
'''Documents:'''  
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 3 documents the profile
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol1.pdf Vol. 1] - Section 3 (SWF profile overview)
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 2] - Sections 4.1 to 4.8, 4.10 to 4.14, 4.16, 4.18, and 4.20 to 4.21, document specific transactions. Appendices A, B and D provide additional requirements and suggestions on mapping information to ensure consistent flow of information throughout the department.
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol2.pdf Vol. 2] - Sections 4.1 to 4.8, 4.10 to 4.14, 4.16, 4.18, 4.20 to 4.21, and Appendices A, B and D.
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 3] - Sections 4.42, and 4.48 to 4.49 document specific transactions.  
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol3.pdf Vol. 3] - Sections 4.42, and 4.48 to 4.49.  
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
Line 64: Line 65:
  
 
==See Also==
 
==See Also==
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
  
 +
'''Related Profiles'''
 +
 +
* [[Patient Information Reconciliation]] [PIR] extends the capability of SWF by handling cases of unidentified (e.g. trauma), or misidentified patients.
  
'''Related Profiles'''
+
* [[Cardiac Cath Workflow]] [CATH] - uses many of the mechanisms of SWF to integrate ordering, scheduling, imaging acquisition, storage and viewing for Cardiac Catheterization procedures.
 +
 
 +
* [[Echocardiography Workflow]] [ECHO] - uses many of the mechanisms of SWF to integrate ordering, scheduling, imaging acquisition, storage and viewing for digital echocardiography
  
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one>''
+
* There are a a number of "content profiles" describing the details of creating and storing various types of image or image related objects, and frequently they would be created in the context of SWF. These content profiles include:
 +
** [[Nuclear Medicine Image]] [NM] specifies how Nuclear Medicine images and result screens are created, exchanged, used and displayed.
 +
** [[Mammography Image]] [MAMMO] specifies how Mammography images and evidence objects are created, exchanged, used and displayed.
 +
** [[Evidence Documents]] [ED] specifies how data objects such as digital measurements are created, exchanged, and used.
 +
** [[Key Image Note]] [KIN] lets users flag images as significant (e.g. for referring, for surgery, etc.) and add notes.
  
 
'''Consumer Information'''
 
'''Consumer Information'''
 
The [[{{{3|Profile FAQ Template}}}]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
 
  
 
The [[Scheduled Workflow FAQ]] answers typical questions about what the Profile does.
 
The [[Scheduled Workflow FAQ]] answers typical questions about what the Profile does.
  
 +
[[Scheduled Workflow Purchasing]] describes considerations when purchasing equipment to deploy this Profile.
  
The [[{{{3|Profile Purchasing Template}}}]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
+
'''Implementer Information'''
  
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.
+
[[Scheduled Workflow Implementation]] provides additional information about implementing this Profile in software.
  
 +
'''Reference Articles'''
  
'''Implementer Information'''
+
* ACR–AAPM–SIIM Technical Standard for Electronic Practice of Medical Imaging. J.T. Norweck, et al., [http://link.springer.com/content/pdf/10.1007%2Fs10278-012-9522-2.pdf SIIM & ACR Publication, Sept. 2012]
 
 
The [[{{{3|Profile Implementation Template}}}]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 
  
'''''<< Incorrect example>>:'''''
+
* Considerations for Setting Up an Order Entry System for Nuclear Medicine Tests, Hara, Narihiro, et al., [http://tech.snmjournals.org/cgi/content/abstract/35/4/259 Journal of Nuclear Medicine Technology, 2007, Vol. 35, Num. 4, pp 259-271]
The [[Cross-Enterprise Document Sharing Implementation]] provides additional information about implementing this Profile (well XDS actually) in software.
 
  
 +
* IHE technical framework and its application (Article in Chinese), Feng JY, et al., [http://www.ncbi.nlm.nih.gov/pubmed/16124630 Chinese Journal of Medical Instrumentation, 2005, May, Vol. 29, Num. 3, pp. 199-201]
  
'''Reference Articles'''
+
* Using the IHE Scheduled Work Flow Integration Profile to Drive Modality Efficiency, Moore, Stephen M., 2003, [http://radiographics.rsnajnls.org/cgi/content/full/23/2/523 Radiographics, Vol. 23, pp 523-529]
  
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >''
 
  
  

Revision as of 14:43, 19 July 2013

Scheduled Workflow (SWF) integrates the ordering, scheduling, imaging acquisition, storage and viewing activities associated with radiology exams.



Summary

Scheduled Workflow establishes a seamless flow of information that supports efficient patient care workflow in a typical imaging encounter. It specifies transactions that maintain the consistency of patient information from registration through ordering, scheduling, imaging acquisition, storage and viewing. This consistency is also the foundation for subsequent workflow steps, such as reporting.

Swf-v4.jpg

Benefits

Reduce Errors and Enhance Patient Care

  • Prevents manual data entry errors by ensuring that a particular piece of data is entered only once
  • Prevents complications from patient allergies or pregnancy status since these details are made available to all systems involved in the radiology workflow
  • Prevents delays in patient care by making relevant information available at the point of care.

Improve Throughput

  • Saves manual data entry time by ensuring that a particular piece of data is entered only once
  • Minimizes "lost" studies by ensuring study identification and status is accurately tracked throughout the department.
  • Reduces staff time wasted identifying and correcting errors (in a coordinated fashion) among the HIS, RIS, PACS and modality

Reduce Deployment Cost/Time

  • Prevents custom interface specification time and expense—IHE TF provides a detailed specification for a powerful interface, supported and tested by many vendors
  • Prevents custom interface implementation time and expense—many IHE Integration Profiles are already supported by many vendor products
  • Reduces interface compliance testing time and expense—many implementation variations have been refined in systems tested at IHE Connectathons
  • Reduces intersystem testing time and expense—many combinations of systems have already been directly tested together at IHE Connectathons
  • Reduces custom interface maintenance time and expense by maintaining a single interface (IHE) instead of multiple custom interfaces

Details

The Scheduled Workflow (SWF) Integration Profile:

  • Establishes the continuity and integrity of basic departmental imaging data by profiling specific usage of HL7 messaging across multiple systems including: Patient registration (ADT), Order Placing (CPOE) and Order SCheduling (RIS) systems.
  • Bridges the gap between HL7-based systems (like RIS) and DICOM-based systems (like acquisition modalities and PACS) within the radiology department by specifying the semantic mappings between messages.
  • Maintains the consistency of patient demographic and ordering information across multiple systems by making that information available to image acquisition modalities via the DICOM Modality Worklist (MWL) Service.
  • Ensures that acquired images are not inadvertently lost by specifying that the DICOM Storage Commitment Service is used to transfer the custodianship of images from the modality to the PACS.
  • Ensures that the status of acquisition workflow steps are known throughout the department by specifying the use of the DICOM Modality Performed Procedure Step (MPPS) Service to convey that status from the modality to the RIS and the PACS.

Systems Affected

Systems involved in this profile are:

  • Enterprise-wide information systems that manage patient registration and services ordering (i.e., admit-discharge-transfer (ADT)/registration system and hospital information system (HIS ))
  • Radiology departmental information systems that manage department scheduling (i.e., radiology information system (RIS))
  • Radiology image management/archiving (i.e., picture archiving and communication system (PACS))
  • Acquisition modalities

Actors & Transactions:

Swf-actor-transaction.JPG

Specification

Profile Status: Final Text

Documents: IHE Radiology Technical Framework:

  • Vol. 1 - Section 3 (SWF profile overview)
  • Vol. 2 - Sections 4.1 to 4.8, 4.10 to 4.14, 4.16, 4.18, 4.20 to 4.21, and Appendices A, B and D.
  • Vol. 3 - Sections 4.42, and 4.48 to 4.49.

Underlying Standards:

See Also

Related Profiles

  • Cardiac Cath Workflow [CATH] - uses many of the mechanisms of SWF to integrate ordering, scheduling, imaging acquisition, storage and viewing for Cardiac Catheterization procedures.
  • Echocardiography Workflow [ECHO] - uses many of the mechanisms of SWF to integrate ordering, scheduling, imaging acquisition, storage and viewing for digital echocardiography
  • There are a a number of "content profiles" describing the details of creating and storing various types of image or image related objects, and frequently they would be created in the context of SWF. These content profiles include:
    • Nuclear Medicine Image [NM] specifies how Nuclear Medicine images and result screens are created, exchanged, used and displayed.
    • Mammography Image [MAMMO] specifies how Mammography images and evidence objects are created, exchanged, used and displayed.
    • Evidence Documents [ED] specifies how data objects such as digital measurements are created, exchanged, and used.
    • Key Image Note [KIN] lets users flag images as significant (e.g. for referring, for surgery, etc.) and add notes.

Consumer Information

The Scheduled Workflow FAQ answers typical questions about what the Profile does.

Scheduled Workflow Purchasing describes considerations when purchasing equipment to deploy this Profile.

Implementer Information

Scheduled Workflow Implementation provides additional information about implementing this Profile in software.

Reference Articles



This page is based on the Profile Template