May 17
2018
CMS’ Proposed PI Rule Changes Is A Good Start, But Does It Address Enough?
By Thanh Tran, CEO, Zoeticx.
Federal healthcare organizations, such as CMS, have spent billions of dollars over the years trying to bridge the gap between medical data and quality patient care with interoperability requirements and data integration, the mesh used to try and bridge the gap. Many government rules have been written to address the type of mesh needed and many EHR companies have claimed to meet these government requirements and claim the throne of the ultimate mesh maker.
However, hospitals and clinics found the mesh contained many holes, such as enabling hospitals to customize EHRs, but only if the EHR customers purchased the EHR systems for the manufacturers for millions of dollars that hospitals could ill afford. Also issues such as proprietary connectivity to their own brands that left the hospitals’ other EHR systems to serve as dead-end data silos. Rules and solutions came and went, but few had any teeth until now.
Anyone for A Slice Of PI?
To end the lack of interoperability morass and data duplication, the Department of Health and Human Services (HHS) issued 1,883 pages of proposed changes to Medicare and Medicaid. The changes rename the Merit-Based Incentive Payment System (MIPS) Advancing Care Information performance category to Promoting Interoperability (PI).
CMS announced the change as part of a proposed rule that will transform the EHR Incentive Programs commonly known as meaningful use under the Inpatient Prospective Payment System (IPPS) and the Long-Term Care Hospital (LTCH) Prospective Payment System (PPS). The proposed policies are part of the MyHealthEData initiative, which prioritizes patient health data access and interoperability improvements.
But this time the name change wasn’t just that. For the first time a new CMS rule specifically requires providers to share data to participate in the life blood of hospital reimbursement—Medicare and Medicaid. The rule also floats the idea of revising Medicare and Medicaid co-pays to require hospitals to share patient records electronically with other hospitals, community providers and patients — a clear-cut demand for interoperability.
PI also reduces hospital interoperability requirements from 16 to six, revamping the program to a points-based scoring system and is requiring that hospitals make patients’ EHRs available to them on the day they leave the hospital beginning in 2019.
Does Your EHR Have the Right Stuff?
While this news from CMS appears to be a step in the right direction to solve a problem that has plagued the healthcare industry for many years, it must first be made a reality by those ultimately responsible for its implementation—hospital HIT organizations. The days of data obstruction and silo logic must end with a focus on new EHR markets built on interoperability.
Interoperability requires multiple layers to demonstrate an EHR system can be accessed. Meanwhile, every EHR system claims to support some form of interoperability, ranging from web interfaces to API protocols or to the lowest and highest cost HL7. However, healthcare systems will have to demonstrate their operability to CMS to abide by PI and therefore allow access of their EHR systems. Hospitals and clinics can encounter many challenges with this, such as HIPAA compliance and support for their infrastructure for open secure access, requiring an HIE and the funds to support data synchronization and IT support.
