Difference between revisions of "Cardiac Cath Workflow"

From IHE Wiki
Jump to navigation Jump to search
Line 60: Line 60:
 
==Details==
 
==Details==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
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.
  
''<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.>''
 
''<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.>''

Revision as of 08:45, 22 December 2009

This profile integrates ordering, scheduling, imaging acquisition, storage and viewing for Cardiac Catheterization procedures

Summary

Cardiac Catheterization is complex, especially from a workflow perspective. Evidence-gathering activities may begin before an order is placed; in fact, orders are often not created for a cardiac catheterization procedure due to its frequent emergency nature. There may be a variety of imaging, measurement, and reporting systems that need to coordinate to use the same patient identifier, and to assure that the evidence produced is all associated with the same procedure. Further, the procedure itself may include both diagnostic and interventional or therapeutic aspects, and may extend over a long time period (several hours).

The Cardiac Catheterization Workflow Integration Profile establishes the continuity and integrity of basic patient data in the context of the cardiac catheterization procedure. This profile deals specifically with consistent handling of patient identifiers and demographic data, including that of emergency patient presentation where the actual patient identity may not be established until after the beginning of the procedure, or even a significant time after the completion of the procedure. It also specifies the scheduling and coordination of procedure data across a variety of imaging, measurement, and analysis systems, and its reliable storage in an archive from where it is available to support subsequent workflow steps, such as reporting. It also provides central coordination of the completion status of steps of a potentially multi-phase (diagnostic and interventional) procedure.

CATH.jpg

Benefits

Cardiologists

Patient care is improved and cardiologists’ time is saved by:

  • Making sure the patient is cared for immediately without concern for completing the proper paperwork first
  • Reducing delays in charge posting
  • Automatically synchronizing time on all systems within a cath lab so that data can be time tagged to at least 1/10th second accuracy, so that simultaneous events recorded on different systems can be identified
  • Providing cath measurement and hemodynamic procedure log interoperability – complete the preliminary cath measurements on a workstation or transfer the procedure log as structured data to the reporting workstation for the final report

Cardiology Administrators and Technologists

Cath lab workflow is improved and time is saved by:

  • Reducing time and errors from entering data into multiple systems in the cath lab
  • Assuring correct patient demographics and procedure code information
  • Automating the correction of demographics in cases such as patient identified mid- or post-procedure (reduces or negates the need to a person to “fix” studies and data)
  • Maintaining the status of the procedures real-time so that the cath lab flow manager can better utilize the facilities
  • Accurately identifying data to facilitate data collection later (e.g., registries

or outcomes analysis)

  • Managing and simplifying RFP’s and purchases
  • Allowing selection of the “best solutions” from multiple vendors and reducing vendor integration issues, rather than the restriction of a single vendor all-encompassing solution

'Cardiology IT Staff

Other IT projects can come to fruition when time is saved in the cath lab by:

  • Automatically assuring that all images are securely stored to the archive prior to deletion at the angio system
  • Avoiding the implementation and maintenance costs for “one-off” integration interfaces to each device
  • Ensuring proper functioning of a multi-vendor environment
  • Reducing “switching costs” when new equipment is purchased

Patient

The patient also benefits from systems integration in the cath lab by:

  • Removing the need to wait while demographics are entered into the various cath lab systems and old reports are pulled.
  • Enabling better patient care because the interpreting physician can more accurately assess interim changes.
  • Providing cath reports more readily to other care team members within and outside a hospital or office network.

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

<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.>

  • 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:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<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.>

IHE Radiology Technical Framework:

  • Vol. 1 - Section 5 (SWF Profile)
  • Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
  • Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

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

<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.>


Consumer Information

The [[

Cardiac Catherization Workflow]] answers typical questions about what the Profile does.  <Replace the link with a link to the actual FAQ page for the Profile>

The [[

Cardiac Catherization Workflow]] 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 [[

Cardiac Catherization Workflow]] provides additional information about implementing this Profile in software.  <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or something. You might be surprised. >


This page is based on the Profile Overview Template


[[Category:

Domain Committee ]]