Open AccessUsing the IHE Scheduled Work Flow Integration Profile to Drive Modality Efficiency
Author(s) -
Stephen Moore
Publication year - 2003
Publication title -
radiographics
Language(s) - English
Resource type - Journals
eISSN - 1527-1323
pISSN - 0271-5333
DOI - 10.1148/rg.232025709
Subject(s) - modality (human–computer interaction) , work flow , computer science , software , process (computing) , system integration , component (thermodynamics) , work (physics) , negotiation , identification (biology) , software engineering , process management , medicine , human–computer interaction , database , industrial engineering , programming language , biology , law , political science , engineering , business , thermodynamics , mechanical engineering , physics , botany
The IHE (Integrating the Healthcare Enterprise) Scheduled Work Flow integration profile describes a communication and work flow environment that provides benefits for radiology departments who want to standardize system software. The IHE technical framework defines this environment by specifying the systems involved and the messages exchanged by those systems. The Modality Worklist is a key component of the Scheduled Work Flow integration profile that allows an operator at each modality in the department to retrieve a list of scheduled procedure steps to perform and to automate the process of entering the correct patient identification information in all the images created with the modality. The IHE technical framework defines two transactions used by the modality to tell the Image Manager and Order Filler what was performed and how many images were acquired: the Modality Procedure Step in Progress and Modality Procedure Step Completed. Users who specify the Scheduled Work Flow integration profile will benefit immediately by achieving a certain baseline of functionality. However, users will derive further benefits of increased operational efficiency through negotiation with the providers of software solutions. The integration profile defines features that are optional; users should evaluate these features and request those that are determined to be beneficial.