Feature | November 03, 2014| Dave Fornell

Interoperability is Biggest Issue Facing CVIS/Cardiac PACS

CVIS providers have made their systems more vendor-neutral, but a clear outline of what is needed should be presented in RFPs

McKesson Cardiology, cardiac PACS, CVIS

The McKesson Cardiology is an example of a CVIS that allows enterprise access to view and analyze medical images and provide diagnostic reports.

For any cardiology department looking to upgrade or replace its cardiovascular picture archiving and communications system (cardiac PACS), or cardiovascular information system (CVIS), the main questions that should be asked are related to integration and interoperability. These are key to leveraging health IT investments to achieve improved efficiency, help cut costs and accommodate increased patient volume.
 
New technology investments should eliminate the need for separate workstations to access disparate silos of data, including cath reporting systems, various cardiac imaging PACS and reporting systems for different modalities. New CVIS should integrate the cardiology department’s entire workflow into a single system.
 
“U.S. hospitals have made progress in integrating cardiology images with non-image data over the past four years,” said Lorna Young, senior director of market research at market research firm IMV. The firm recently released a report on the state of the CVIS market. “Cardiologists need patient images to be integrated with related non-image patient information and structured reporting to improve diagnostic efficiency.”
 
IMV’s report shows U.S. hospitals are at various degrees of implementation along this path. More than three-quarters of the surveyed hospitals (77 percent) indicated they have both cardiac PACS and CVIS. An additional 17 percent have one system or the other, while only 6 percent of the hospitals have no formal implementation of either system. Of the sites that have both systems, nearly half indicated their cardiac PACS and CVIS are fully integrated, while the rest have not.
 
Ingredients for the Ideal CVIS
An ideal CVIS should be standards-based, vendor-neutral, use structured reporting (to enable comprehensive searches and data mining) and enable the following functionality using a single computer. A CVIS should serve as a comprehensive cardiology PACS to enable image review and sharing capabilities for all cardiovascular imaging modalities on a single workstation. It should have reporting capabilities for all sections of the cardiology department, so all patient data is accessible in one place. A CVIS should enable access to the ECG management system and possibly allow segments of waveforms to be incorporated into reports. For cath lab reporting, the system should be fully integrated with the hemodynamics system. The CVIS also should serve as the department’s image and report archive.
 
As society increasingly transitions to Web-based, mobile computing using tablets and smartphones, cardiology departments need to consider mobile device access to the CVIS. Physicians can leverage this mobile accessibility to become more efficient and improve care. This may include using a tablet to access reports, labs and imaging while on rounds, to enable better patient communication/engagement, to complete reports in-between procedures, or even making a determination from home if the cath lab should be activated at 3 a.m. 
 
Ideally, the system also should meet meaningful use criteria for sharing data and images with the hospital’s EMR and referring physicians outside the cardiology department or the hospital. Future meaningful use requirements should be considered, including expanding two-way access to patient data and images to enable patient engagement. Future meaningful use needs also require integration of computerized physician order entry (CPOE) systems for prescriptions and orders that combine clinical decision support (CDS) software. CDS software will need to document that appropriate use criteria (AUC) has been met for specific tests, imaging exams and procedures. Another component to consider is the use of radiation monitoring software to record the approximate doses patients receive from cardiac CT and diagnostic and interventional angiography. Dose recording software is already required in two states. and it is expected others will follow.
 
However, to enable the types of integration outlined above, the key element is the system’s interoperability between disparate vendors’ equipment, devices and third-party software. Some vendors may integrate better than others, especially with the most recently introduced CVIS platforms. Most of the major CVIS have created more vendor-neutral software, allowing greater accessibility. Even large medical device vendors, which in the past each had their own proprietary CVIS software that did not interface easily with other vendors’ systems, have all recently launched Web-based CVIS that enable much better interoperability. 
 
Despite this, it is always good to trust but verify all interoperability claims and make sure any vendor chosen is held accountable to the department’s specific needs in the final contract language. Outline exactly what your department needs in the request for proposal (RFP) so all integration issues can be discussed before a system is installed. 
 
Interoperability Barriers Still Remain
Two recent reports remind us that healthcare interoperability is still a major concern, regardless of what vendors say. A survey of CVIS end users released in August by IMV shows that while the evolution of these systems has progressed, it is clear respondents do not feel their journey on the cardiology information continuum is complete. When asked where they felt their current implementation of cardiac PACS/CVIS is relative to their ideal, only 33 percent of the respondents reported they were more than three-quarters of the way to their ideal system. Continued investment in cardiovascular IT systems is proceeding, with two-thirds of the sites planning to upgrade or implement a new or replacement CVIS over the next three years.
 
Despite their acknowledgement that the ideal architecture includes integration with the EMR, survey respondents feel their EMR vendor should not necessarily integrate their ideal IT solution. They said EMR vendors’ priorities might not match cardiology’s priority of aligning its IT system with its workflow practices. In fact, a higher proportion of respondents said they are more likely to favor their current cardiac PACS or CVIS vendor, or even their radiology PACS vendor, to be the integrator for their ideal CVIS solution than an EMR vendor. Having an enterprise-wide archive solution that is developed for cardiology, radiology and other hospital departments also is part of the vision, IMV reported from the survey results.
 
The interoperability issue is not limited to cardiology systems. Another survey, released in September and conducted by Premier Inc. and the eHealth Initiative, found the failure of systems to integrate easily is causing major health IT issues for most accountable care organizations (ACOs). Although ACOs were created to improve clinical quality, poor interoperability across systems and providers remains a major barrier, according to the survey. Access to data from external organizations was challenging for 100 percent of respondents. 
 
When announcing the survey results, Premier said compounding the challenge of accessing and sharing data is the fact that 88 percent of the ACOs face significant obstacles in integrating data from disparate sources, and 83 percent report challenges integrating technology analytics into workflow. Interoperability of disparate systems is a significant challenge for 95 percent of organizations and could be limiting the abilities of ACOs to exchange data.   
 

Comparison Chart
This article served as an introduction to the 2014 cardiac PACS comparison chart. Listed below are the companies that participated in the chart. The chart can be accessed by clicking on the "comparison charts" tab at the top of the page.

Agfa HealthCare 
www.agfahealthcare.com

Carestream Health 
www.carestream.com

Cerner
www.cerner.com

Digisonics
www.digisonics.com

DR Systems 
www.drsys.com

Fujifilm
www.cardiovascular.fujimed.com

GE Healthcare
www.gehealthcare.com

Infinitt 
www.infinittna.com

Lumedx Corp. 
www.lumedx.com

McKesson
www.mckesson.com/cardiology

Merge
www.merge.com

Novarad
www.novacardio.com

Philips
www.healthcare.philips.com

RADinfo Systems
www.radinfosystems.com

ScImage
www.scimage.com

Siemens Healthcare
www.usa.siemens.com/CVIS

 
References:
1. MV Report. “2014 Cardiology Information Continuum: Present Access 
and Future Integration Strategies for Cardiovascular Information Technology.” www.imvinfo.com
2. Premier Inc. “Accountable care organizations struggling with HIT interoperability.” Survey of 62 ACOs, including members of Premier’s PACT Population Health Collaborative. Survey fielded in July-August 2014. Published online www.premierinc.com/aco-interoperability-survey-9-24-14. Accessed  Oct. 4, 2014.

Related Content

Spacelabs Debuts Sentinel 11 Cardiology Information Management System
Technology | Cardiac PACS | May 10, 2019
Spacelabs Healthcare debuted Sentinel 11 at the 40th Annual Heart Rhythm Society (HRS) Scientific Sessions, May 8-11,...
Dianna Bardo, M.D., is the vice chair of radiology for clinical development at Phoenix Children’s Hospital.

Dianna Bardo, M.D., is the vice chair of radiology for clinical development at Phoenix Children’s Hospital. 

Webinar | Cardiac PACS | March 06, 2019
 
ScImage’s PICOM365 Enterprise PACS enables cath, echo, vascular, ECG, stress and Holter storage and reporting.

ScImage’s PICOM365 Enterprise PACS enables cath, echo, vascular, ECG, stress and Holter storage and reporting.

Case Study | Cardiac PACS | March 05, 2019 | Anthony Pearson, M.D.
Call nights are by far the worst part of being a clinical cardiologist.
Philips Launches Latest Iteration of IntelliSpace Cardiovascular at HIMSS 2019
Technology | Cardiac PACS | February 13, 2019
Philips announced the launch of IntelliSpace Cardiovascular 4.1, its next-generation cardiovascular image and...
NewYork-Presbyterian Hospital Partners With Philips for Health IT and Clinical Informatics
News | Cardiac PACS | January 16, 2019
Philips announced that NewYork-Presbyterian Hospital has chosen to implement the company’s IntelliSpace Enterprise...
An example of a comprehensive CVIS is the ScImage Picom 365 system, which includes several sub-speciality reporting modules to eliminate the need for several different, disparate reporting systems in the cardiology department. Also called cardiac PACS cardiovascular information and imaging systems.

An example of a comprehensive CVIS is the ScImage Picom 365 system, which includes several subspeciality reporting modules to eliminate the need for several different, disparate reporting systems in the cardiology department. 

Feature | Cardiac PACS | October 05, 2018 | Val Kapitula RT(R), PMP, CIIP
“I don’t trust anything that’s being portrayed in the marketing brochures and will believe it only when the solution
Digisonics Showcases New Functionality at ASE 2018 for Data-driven Decisions
News | Cardiac PACS | June 25, 2018
Digisonics will exhibit its latest functionality for data-driven decisions at the American Society of Echocardiography...
Infinitt Achieves ACC-NCDR Certification for CathPCI Registry
Technology | Cardiac PACS | May 09, 2018
Infinitt North America announced that Infinitt Cardiology Suite-v 1.0.8.1 has achieved certification from the American...
Sligo University Hospital (SUH) uses Change Healthcare's McKesson Cardiology CVIS solution.

Sligo University Hospital (SUH) in Ireland uses Change Healthcare's McKesson Cardiology CVIS solution to improve efficiency.

Case Study | Cardiac PACS | May 04, 2018
Balancing high quality care with efficiency — and avoiding unnecessary procedures — is a priority for any hospital de
Siemens Healthineers Launches Next Generation of syngo Dynamics at ACC 2018
Technology | Cardiac PACS | March 09, 2018
March 9, 2018 — At the American College of Cardiology’s 67th Annual Scientific Session and Expo, March 10-12 in Orlan
Overlay Init