Difference between revisions of "Electrophysiology Report Content"

From IHE Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 5: Line 5:
  
 
==Benefits==
 
==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.>''
+
This content profile is motivated by EP physicians, who face an increasing demand from patient-care, data-quality and legislative perspectives to increase the usefulness of (discrete) clinical data across the various care-settings and stakeholders.  
 +
 
 +
The aim is to enable collection and distribution of the most clinically-relevant discrete data on the EP Implant/Explant procedures common in cardiology.
 +
 
 +
The usage of the discrete data is three-fold:
 +
*To enable individual Implant/Explant procedure related information to be more easily shared and used between care givers and systems
 +
*To enable population-based outcomes-based research on procedure effectiveness
 +
*To provide the ability to interact with data registries for data exchange.
  
 
==Details==
 
==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.  
 
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.>''
+
This profile specifies the use of an HL7 Clinical Document Architecture (CDA) format for the EP physician clinical report. This format supports both the human readable narrative historically used for clinical reports, as well as a substantial set of discrete data elements that may be used for longitudinal or population analysis or other computer processing.  It provides the framework of high level section titles and a set of discrete data elements. Within that framework reports can be created with the clinical content desired by their authors, including additional discrete data elements.
  
''<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.>''
+
This profile codifies representative areas of procedure indications, procedures, medications, observations, complications and findings for electrophysiology procedures and specifies how this discrete data can be organized to be used by both care-providers and automated data processing systems.
  
''<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==
 
==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.>''
+
The EPRC profile is a content profile, which defines the content of a Cardiac Electrophysiology Report. The means of interchanging the report is not detailed in this profile but addressed in other profiles like DRPT, XDS or PDI. In general two types of systems would be relevant: A reporting workstation, Cardiovascular Information System or an EP Analysis workstation which creates a report and distributes it via one of the mechanism mentioned above. A workstation or system which is receiving and displaying the report. This could be an EMR/EHR System or any type of reporting workstation.
  
* ''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:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[image:CIRC_ACT_Trans.jpg]]
  
 
==Specification==
 
==Specification==
Line 35: Line 37:
 
:* [http://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_EPRC-IE.pdf EPRC Supplement]
 
:* [http://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_EPRC-IE.pdf EPRC Supplement]
  
 
''<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.>''
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
:* [http://www.hl7.org HL7]
 
 
:* HL7 CDA Release 2.0  
 
:* HL7 CDA Release 2.0  
:* HL7 Implementation Guide for CDA® Release 2: IHE Health Story Consolidation, Release 1
+
:* HL7 Implementation Guide for CDA® Release 2: IHE Health Story Consolidation, Release 1.1 - US Realm
 
+
:* Systematized Nomenclature of Medicine – Clinical Terms
 +
:* Logical Observation Identifiers Names and Codes
 +
:* NCDR ICD Registry v1.2 Coder’s Data  Dictionary
  
 
==See Also==
 
==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'''
 
'''Related Profiles'''
  
As a content integration profile EPRC provides the payload for any of the exchange mechanisms of the following profiles
+
As a content integration profile EPRC provides the payload for any of the exchange mechanisms of the following profiles:
 
* [[Displayable Reports | Displayable Reports (DRPT)]] for the creation, exchange and management of cardiac imaging reports within an enterprise
 
* [[Displayable Reports | Displayable Reports (DRPT)]] for the creation, exchange and management of cardiac imaging reports within an enterprise
 
* [[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
 
 
'''Consumer Information'''
 
 
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>''
 
 
'''Implementer Information'''
 
 
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>''
 
 
'''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 Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
 
 
  
  
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
  
[[Category:Template]]
+
[[Category:Profiles]]
 +
[[Category:Cardiac Profile]]
 +
[[Category:DocShare]]
 +
[[Category:CDA]]

Latest revision as of 14:33, 4 November 2019

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

This content profile is motivated by EP physicians, who face an increasing demand from patient-care, data-quality and legislative perspectives to increase the usefulness of (discrete) clinical data across the various care-settings and stakeholders.

The aim is to enable collection and distribution of the most clinically-relevant discrete data on the EP Implant/Explant procedures common in cardiology.

The usage of the discrete data is three-fold:

  • To enable individual Implant/Explant procedure related information to be more easily shared and used between care givers and systems
  • To enable population-based outcomes-based research on procedure effectiveness
  • To provide the ability to interact with data registries for data exchange.

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.

This profile specifies the use of an HL7 Clinical Document Architecture (CDA) format for the EP physician clinical report. This format supports both the human readable narrative historically used for clinical reports, as well as a substantial set of discrete data elements that may be used for longitudinal or population analysis or other computer processing. It provides the framework of high level section titles and a set of discrete data elements. Within that framework reports can be created with the clinical content desired by their authors, including additional discrete data elements.

This profile codifies representative areas of procedure indications, procedures, medications, observations, complications and findings for electrophysiology procedures and specifies how this discrete data can be organized to be used by both care-providers and automated data processing systems.

Systems Affected

The EPRC profile is a content profile, which defines the content of a Cardiac Electrophysiology Report. The means of interchanging the report is not detailed in this profile but addressed in other profiles like DRPT, XDS or PDI. In general two types of systems would be relevant: A reporting workstation, Cardiovascular Information System or an EP Analysis workstation which creates a report and distributes it via one of the mechanism mentioned above. A workstation or system which is receiving and displaying the report. This could be an EMR/EHR System or any type of reporting workstation.


Actors & Transactions:

CIRC ACT Trans.jpg

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.1 - US Realm
  • Systematized Nomenclature of Medicine – Clinical Terms
  • Logical Observation Identifiers Names and Codes
  • NCDR ICD Registry v1.2 Coder’s Data Dictionary

See Also

Related Profiles

As a content integration profile EPRC provides the payload for any of the exchange mechanisms of the following profiles:


This page is based on the Profile Overview Template