VCUHS Health Overcomes Interoperability Challenges on Way to eCQM Success

Read this case study to learn how VCUHS was able to submit its first eCQMs months before the deadline.

resource cover imageLike most providers, the Virginia Commonwealth University Health System (VCUHS) in Richmond, Va., experienced a lot of pressure and uncertainty in preparing for its first mandatory Electronic Clinical Quality Measure (eCQM) submissions. Unlike most, VCUHS also felt frustration due to two previous unsuccessful attempts at eCQM implementations.

VCUHS was an early adopter of electronic health records (EHR) and first attempted eCQM implementation in 2012 with help from its quality reporting vendor, using the vendor’s reporting software. In that project, the health system and vendor together were unable to extract the data necessary for eCQMs from VCUHS’ systems. In an attempt to solve that problem, VCUHS contracted with its EHR provider. While strides were made in data abstraction, this effort was not a full success due to lack of flexibility and data source interoperability. VCUHS met the submission criteria because it could attest that it could run a report. However, the actual data in the report was incomplete and largely inaccurate. VCUHS was not satisfied with the result. Because VCUHS is on a journey to become America’s safest and most caring health system, with a strong commitment to quality, its goal was to produce meaningful data that could be used to evaluate and improve the quality of care and services.

“Capturing the required data elements for accurate eCQMs is a very different world from what everyone is used to,” says Jill Bradford Shuemaker, a clinical informaticist who specializes in quality measures at VCUHS. She notes that providers, solution specialists, and even the regulators that developed the program and make the rules are struggling with the complexities and technical immaturity surrounding eCQM abstraction and submission. “It seemed logical for existing manual reporting vendors and EHR solution providers to come into the space, but it isn’t natural for either of them. Many of the first vendors to come into the market are no longer eCQM vendors.”

Here is one example of why eCQM quality reporting can be so challenging. VCUHS is an early adopter of electronic health records and implemented with a strategy to gain 100 percent user acceptance. To meet that goal it has made many modifications to its EHR system over the years. VCUHS uses multiple modules of the EHR, and they are not all interoperable. Data nomenclature is not standard or consistent across the different modules and system versions. For example, instead of creating one field for blood pressure that could be utilized in multiple applications, VCUHS has multiple fields for documenting blood pressure based on clinical needs; therefore, instead of being straightforward, extracting blood pressure data to report is complex and challenging.

“Lots of vendors can get to data, but knowing if the data is appropriate for a specific measure is critical,” says Wendy Sale, VCUHS’s eCQM project manager. “You need someone who understands the specifications and complexities of each eCQM, and who understands your organization and its systems. Due to all the complexities, we approach eCQMs as a quality endeavor that relies heavily on collaboration with our information technology (IT) partners; both quality and IT expertise are essential for success.”

Download this case study to learn how VCUH selected Medisolv and its ENCOR quality reporting solution to help produce accurate, meaningful, actionable eCQM data.