Cardiac Imaging Report Content

Summary

This profile provides an HL7 CDA Implementation Guide for a Cardiac Imaging Report. The content is based on the roughly 100 Key Data Elements defined by the ACC/AHA Key Data Elements for Cardiac Imaging (JACC Vol. 53, No. 1, 2009).

Benefits

Clinically-relevant cardiac imaging data is the key value proposition of this profile. The approach is to:

1. reuse the distribution and structuring work from the XDS ( ITI domain), Medical summaries (PCC domain), and exchangable procedure notes (HL7)
2. extend it through adding and codifying the Key Data Elements for Cardiac Imaging content identified by the American College of Cardiology (ACC) / American Heart Association (AHA) task-force on clinical data standards

Details

The Cardiac Imaging Report Content (CIRC) Profile specifies the content structure for a clinical report of a cardiology imaging exam, recorded in a DICOM Study. Such exams include:

• Echocardiography (transthoracic - TTE, transesophageal - TEE, and TTE stress)
• Cardiac computed tomography (angiography - CCTA, and coronary artery calcium scoring - CACS)
• Cardiac magnetic resonance (angiography - MRA, and MR stress)
• Cardiovascular nuclear medicine (SPECT myocardial perfusion, positron emission tomography - PET)
• Diagnostic coronary catheter based fluoroscopy (interventional coronary angiography - ICA, and left ventriculography - LVG)

The CIRC Profile specifies the use of an HL7 Clinical Document Architecture (CDA) format for the report. Not included in the scope of this profile are non-imaging studies (e.g., ECG), electrophysiology procedures, and non-cardiology procedures (e.g., peripheral angiography). Such use cases may be supported by other similar content profiles.

Cardiac Imaging Report Content (CIRC) is a content profile – it is agnostic with respect to the workflow or data exchange mechanism in which the data is produced and handled.

The CIRC content is intended to be deployed, for example, in the Image Enabled Office (IEO) workflow profile for ambulatory care environments, the Displayable Reports (DRPT) workflow profile for in-patient environments, or the Cross-Enterprise Document Sharing (XDS) profile to propagate the content across organizational boundaries. It is important to note that that key report-generation/distribution workflow aspects such as physician identification, insurance preauthorization, report routing and acknowledgement, and patient consent, are out of scope for this Content Profile.

The aim is to enable collection and distribution of the most clinically-relevant discrete data on the diagnostic imaging procedures common in cardiology. The usage of the discrete data is two-fold:

1. to enable individual test data to be more easily shared and used between care givers and systems
2. to enable population-based outcomes-based research on test effectiveness

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:

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<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.>

IHE Radiology Technical Framework:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• DICOM
• HL7
• ...

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 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