Difference between revisions of "Electrophysiology Report Content"
Line 50: | Line 50: | ||
* [[Portable Data for Imaging | Portable Data for Imaging (PDI)]] for storage and exchange of cardiac imaging Reports on exchangeable media | * [[Portable Data for Imaging | Portable Data for Imaging (PDI)]] for storage and exchange of cardiac imaging Reports on exchangeable media | ||
* [[Cross Enterprise Document Sharing | Cross Enterprise Document Sharing (XDS)]] for storage and retrieval of cardiac imaging reports in a cross enterprise setting | * [[Cross Enterprise Document Sharing | Cross Enterprise Document Sharing (XDS)]] for storage and retrieval of cardiac imaging reports in a cross enterprise setting | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 12:15, 21 July 2017
Summary
This profile specifies the content structure for a clinical report of an electrophysiology procedure recorded in an EP Lab. Such procedures include Implantable Cardioverter Defibrillator (ICD) Implant, Permanent Pacemaker (PPM)/Implantable Pulse Generator (IPG) Implant, Implantable Cardiac Monitor Implant, Lead Implant, ICD Explant, Generator Change, Lead Explant, Lead Abandonment, and Imaging associated with Implant/Explant (e.g., Venogram).
Benefits
<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>
Details
This profile provides an HL7 CDA Implementation Guide for an Electrophysiology Implant/Explant Procedure Report, derived from the Procedure Note specifications as defined in the IHE Health Story Consolidation, Release 1. The content is based on the ACC NCDR ICD Registry version 1.2 data set.
<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
<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: Trial Implementation
Documents:
Underlying Standards:
- HL7 CDA Release 2.0
- HL7 Implementation Guide for CDA® Release 2: IHE Health Story Consolidation, Release 1
See Also
Related Profiles
As a content integration profile EPRC provides the payload for any of the exchange mechanisms of the following profiles
- Displayable Reports (DRPT) for the creation, exchange and management of cardiac imaging reports within an enterprise
- Portable Data for Imaging (PDI) for storage and exchange of cardiac imaging Reports on exchangeable media
- Cross Enterprise Document Sharing (XDS) for storage and retrieval of cardiac imaging reports in a cross enterprise setting
This page is based on the Profile Overview Template