Difference between revisions of "Echocardiography Workflow"
Line 64: | Line 64: | ||
==Details== | ==Details== | ||
− | |||
− | '' | + | The '''''Echocardiography Workflow (Echo) 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 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 09:30, 22 December 2009
This integration profile integrates ordering, scheduling, imaging acquisition, storage and viewing for digital echocardiography
Summary
The Echocardiography Workflow Integration Profile describes the workflow associated with digital echocardiography, specifically that of transthoracic echo (TTE), transesophageal echo (TEE), and stress echo. As does the Cath Workflow Integration Profile, this profile deals with patient identifiers, orders, scheduling, status reporting, multi-stage exams (especially stress echo), and data storage. It also specifically addresses the issues of acquisition modality devices that are only intermittently connected to the network, such as portable echo machines, and addresses echo-specific data requirements.
The Echo workflow is focused on the imaging acquisition process, and image-based measurements made either on the modality or on an independent workstation. Items not included would be nursing notes, drug administration documentation, etc. The TEE, TTE, and stress echo workflows are treated identically for the purposes of workflow control.
Benefits
Cardiologists
Patient care is improved and cardiologists’ time is saved by:
- Allowing immediate patient care to be the priority, knowing the system will help manage the ordering and accounting on the back end
- Ensuring that images are created with proper identifiers so that image display is consistent, especially for stress echoCardiologists Patient care is improved and cardiologists’ time is saved
- Allowing immediate patient care to be the priority, knowing the system will help manage the ordering and accounting on the back end
- Ensuring that images are created with proper identifiers so that image display is consistent, especially for stress echo Providing echo measurement interoperability – complete the preliminary echo measurements on the cart and transfer as structured data to the reporting workstation for the final report
- Reducing the need for duplicate procedures
- Reducing delays in charge posting due to improper orders
- Ensuring images and measurements are securely stored
- Uploading echo reports to the hospital or office information system
Cardiology Administrators and Technologists
Echo lab workflow is improved and time is saved by:
- Automatically obtaining correct patient demographics and procedure code information
- Automatically correcting demographics in cases such as patient identification not obtained in advance (reduces the need of personnel to “fix” studies and data)
- Accurately identifying data to facilitate easier data collection later (e.g., disease registries or outcomes analysis)
- Improving the handling of ad hoc echo procedures which might otherwise not get billed due to insufficient or inaccurate information
- Assisting in maintaining the statuses of procedures in real-time for better lab management
- Verifying that all images obtained, even on mobile systems, are securely archived prior to deletion
Cardiology IT Staff
Other IT projects can come to fruition when time is saved in the echo lab by:
- Reducing or eliminating “interface projects”, including specification and testing
- More stable and robust interfaces, including during system upgrades
- Ensuring that a multi-vendor environment will function correctly
- Reduction of “switching costs” when a new system is purchased, including time to configure new ultrasound modalities
- Managing and simplifying RFP’s and purchases by using IHE-specified connectivity profiles
- Selection of the “best solutions” from multiple vendors and reduction of vendor integration issues, eliminating the need for a single vendor all-encompassing solution
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 Echocardiography Workflow (Echo) 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:
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.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
Consumer Information
The [[
Echocardiography Workflow ]] answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The [[
Echocardiography 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 [[
Echocardiography 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:
IHE Cardiology Technical Committee ]]