Now that Labor Day has come and gone, I’ve thought about the months ahead and the major challenges I’ll face.
1. Mergers and Acquisitions
Healthcare in the US is not a system of care, it’s a disconnected collection of hospitals, clinics, pharmacies, labs, and imaging centers. As the Affordable Care Act rolls out, many accountable care organizations are realizing that the only way to survive is to create “systemness” through mergers, acquisitions, and affiliations. The workflow to support systemness may require different IT approaches than we’ve used in the past. We’ve been successful to date by leaving existing applications in place and building bidirectional clinical sharing interfaces via “magic button” viewing and state HIE summary exchange. Interfacing is great for many purposes. Integration is better for others, such as enterprise appointment scheduling and care management. Requirements for systemness have not yet been defined, but there could be significant future work ahead to replace existing systems with a single integrated application.
2. Regulatory uncertainty
Will ICD10 proceed on the October 1, 2014 timeline? All indications in Washington are that deadlines will not be changed. Yet, I’m concerned that payers, providers and government will not be ready to support the workflow changes required for successful ICD10 implementation. Will all aspects of the new HIPAA Omnibus rule be enforced including the “self pay” provision which restricts information flow to payers? Hospitals nationwide are not sure how to comply with the new requirements. Will Meaningful Use Stage 2 proceed on the current aggressive timeline? Products to support MU2 are still being certified yet hospitals are expected to begin attestation reporting periods as early as October 1. With Farzad Mostashari’s departure from ONC, the new national coordinator will have to address these challenging implementation questions against a backdrop of a Congress which wants to see the national HIT program move faster.
3. Meaningful Use Stage 2 challenges
Although attestation criteria are very clear (and achievable), certification is quite complex, especially for a small self development shop like mine. One of my colleagues at a healthcare institution in another state noted that 50 developers and 4 full analysts are hard at work at certification for their self built systems. I have 25 developers and a part time analyst available for the task. I’ve read every script and there are numerous areas in certification which go beyond the functionality needed for attestation. Many EHR vendors have described their certification burden to me. I am hopeful that ONC re-examines the certification process and does two things – removes those sections that add unnecessary complexity and makes certification clinically relevant by using scenarios that demonstrate a real world workflow supporting the functionality needed for attestation.



So, 