Difference between revisions of "Scheduled Workflow"

From IHE Wiki
Jump to navigation Jump to search
Line 56: 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_tf_rev8.pdf Vol. 1] - Section 3  
:* [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_tf_rev8.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_tf_rev8.pdf Vol. 3] - Sections 4.42, and 4.48 to 4.49.  
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''

Revision as of 14:05, 21 March 2008

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.
  • Specifies semantic mappings that bridge the gap between the HL7-based systems (like RIS systems) and the DICOM-based systems (like acquisition modalities and PACS) within the radiology department.
  • 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
  • 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

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one>

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.

<< Incorrect example>>: The Cross-Enterprise Document Sharing Implementation provides additional information about implementing this Profile (well XDS actually) in software.


Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >


This page is based on the Profile Template