Difference between revisions of "Retrieve ECG for Display"
Line 64: | Line 64: | ||
'''Underlying Standards:''' | '''Underlying Standards:''' | ||
− | :* [http:// | + | :* [http://www.faqs.org/rfcs/rfcl1738.html IETF RFC 1738]: Uniform Resource Locators (URL), Dec 1994. |
− | :* [http://www. | + | :* IETF RFC 2616: Hypertext Transfer Protocol HTTP 1.1 |
+ | :* [http://www.w3.org/TR/REC-xml Extensible Markup Language (XML)]: 1.0 (Second Edition). W3C recommendation, Oct. 2006 | ||
+ | :* [http://www.w3.org/TR/wsdl Webservices Description Language (WSDL)]: 1.1. W3C Note March 2001 | ||
+ | :* [http://www.w3.org/TR/xhtml1 Extensible Hypertext Markup Language (XHTML)]: 1.0 (Second Edition). W3C Recommendation Jan. 2000 | ||
+ | :* [http://www.w3.org/TR/xhtml-basic XHTML Basic]: W3C Recommendation Dec. 2000 | ||
==See Also== | ==See Also== |
Revision as of 03:28, 23 December 2009
This integration profile provides access throughout the enterprise to electrocardiogram (ECG) documents for review purposes
Summary
Clinicians need a simple means to access and view electrocardiograms (ECGs) from anywhere within and beyond the hospital enterprise. The ECGs should consist of “diagnostic quality” waveforms, measurements, and interpretations. The primary goal is to retrieve resting 12- lead ECGs, but retrieving ECG waveforms gathered during stress, Holter, and other diagnostic tests is also desirable. Typically, these ECGs are already stored in an ECG management system. The focus of this Profile is on retrieval and display, not the process of ordering, acquiring, storing, interpreting, or analyzing the ECGs.
Benefits
IHE provides benefits to clinicians and administrative staff focusing on patient care and reducing inefficiencies, specifically:
- Make ECG viewing available in many locations, increasing the access to the ECG information
- Simplify and standardize the ECG access and viewing process
- Remove the need to “find the printed ECG” (lost on a piece of paper or moving to a special ECG-only workstation)
- Allow multiple clinicians to view the ECG simultaneously for real-time conferencing
- Provide diagnostic display resolution
- Allow clinicians to view ECGs from outside of the physical hospital walls (in coordination with hospital security policies)
- Reduce the need for duplicate procedures
- Ensure that a multi-vendor environment will function correctly
- Manage and simplify the purchasing process
- Reduce “switching costs” when a new system is purchased
- Select the “best solutions” from multiple vendors and reduce vendor integration issues rather than restriction to a single vendor allencompassing solution
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.>
<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
The key Actors in ECG Display and examples of real-world products which might implement these roles are:
- Display – Electronic Healthcare Record, Echo or Cath Imaging Viewing workstation, Cardiology Information System, any simple web application which understands how query the Information Source
- Information Source – ECG Management and Archiving System
Actors & Transactions:
Specification
Profile Status: Final Text
Documents:
IHE Cardiology Technical Framework:
Underlying Standards:
- IETF RFC 1738: Uniform Resource Locators (URL), Dec 1994.
- IETF RFC 2616: Hypertext Transfer Protocol HTTP 1.1
- Extensible Markup Language (XML): 1.0 (Second Edition). W3C recommendation, Oct. 2006
- Webservices Description Language (WSDL): 1.1. W3C Note March 2001
- Extensible Hypertext Markup Language (XHTML): 1.0 (Second Edition). W3C Recommendation Jan. 2000
- XHTML Basic: W3C Recommendation Dec. 2000
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 [[
Retrieve ECG for Display ]] answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The [[
Retrieve ECG for Display ]] 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 [[
Retrieve ECG for Display ]] 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 ]]