Resting ECG Workflow
Resting Electrogcardiograms (ECGs) are a widely perscribed diagnostic test in Cardiology. Current workflows are based on proprietary communication protocols, which hamper interoperability and clincal workflows.
The profile describes workflows associated with digital electrocardiography. Similar to the Cath and Echo Workflow integration profiles, this profile deals with patient identifiers, orders, scheduling, status reporting, and data storage. It also addresses the issues of acquisition modality devices that are intermittently connected to the network, such as portable electrocardiograph machines, as well as ECG-specific data requirements. The Resting ECG Profile will handle the cases of unordered and urgent ECG tests and ECGs acquired in both hospital and office settings. It also handles ECGs acquired for the purposes of clinical trials and research.
- Allows multi-vendor interoperability between major subsystems:
- Registration and ordering (HIS, CVIS)
- ECG archive (PACS, ECG Management)
- Acquisition devices (Electrocardiographs)
- ECG analysis and reporting workstations (ECG or PACS Workstations)
- ECG report consumers (EMR)
- Uses HL7 transactions for HIS and EMR
- Uses DICOM transactions for acquisition devices and workstations
- ECG waveforms stored as DICOM General ECG Waveform objects
- ECG measurements and interpretations stored as DICOM Structured Reports
- An “Integrated ECG Manager” actor makes it easier for traditional ECG management products to adopt this profile
The Resting ECG Workflow (REWF) 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 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 ))
- Cardiology information systems that manage department scheduling
- Image management/archiving systems (i.e., picture archiving and communication system (PACS))
- Acquisition modalities
<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:
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
<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.>
<list all the standards on which the profile is based; if possible with links to sources>
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<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.
The 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 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>
The 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>
<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 Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template