Difference between revisions of "Resting ECG Workflow"
|Line 7:||Line 7:|
Revision as of 06:29, 28 July 2011
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
<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>
<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.>
<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>
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