How can ROI specialists evolve?
Over the years, the role of the ROI specialist has changed significantly commensurate with increased HIPAA scrutiny and the implementation of EHRs. In a previous post, I discussed the challenges that today’s ROI specialists face when navigating through a hybrid environment. It’s difficult at best to locate information that spans multiple formats and locations, and it requires new skills and an incredible attention to detail. The expertise necessary to ensure compliant ROI (also known as disclosure management) will only continue to increase as new regulations change the ways in which data is created, stored, and exchanged.
New regulations abound
The first few months of 2015 were busy ones in terms of HIM-related regulations. First, the ONC published a draft roadmap for interoperability “that will enable a majority of individuals and providers across the care continuum to send, receive, find and use a common set of electronic clinical information at the nationwide level by the end of 2017.” In addition, HHS announced its proposed criteria for Meaningful Use Stage 3 that places greater emphasis on patient engagement. Finally, the House and Senate confirmed passage of the Medicare Access and CHIP Reauthorization Act, propelling ICD-10 toward an October 1, 2015 implementation deadline.
There is a definite focus on data quality and interoperability, particularly as organizations continue to implement EHRs and prepare for the added specificity in ICD-10. However, what does all of this mean for ROI specialists?
Today’s ROI specialists are the gatekeepers of information. They must know where to find information, how to access it, and what to release based on the organization’s definition of its legal health record. This includes being able to access legacy systems and use a variety of health IT applications. Successful ROI specialists must also be able to troubleshoot when systems are down to ensure timely responses and efficiency. Although these foundational skills don’t change, ROI specialists will need to be able to evolve in a new interoperable environment.