News

With 35 percent of rural hospitals losing money and almost two-thirds running a negative operating margin, there’s simply no way rural facilities can invest in health IT without help...It’s clear that CMS understands we can’t leave rural hospitals to fend for themselves. But it also seems clear that a lot of hospitals invested in electronic health records (EHRs) they could ill afford to qualify for Meaningful Use funds—dollars that seldom covered implementation costs for solutions that didn’t yield significant cost savings and required additional technical personnel...“The high capital and operating costs associated with health IT, specifically EHRs, have put some hospitals in a difficult position,” wrote Becker’s Hospital CFO in a prescient January 2014 article. “Do they absorb the financial hit now, even if they know they can't afford it? Most organizations are doing so …”

Read More »

...recently, the ONC Interoperability Roadmap, recognizing that the building blocks of universal interoperability could not be so neatly erected, leans on the idea of “coordinated governance” of networks. While these frameworks have paid homage to the concept of nationwide network as a “network of networks”, we have yet to crisply define the stitching needed to form this nationwide network quilt. This issue hasn’t been so pressing up until now because there were relatively few networks – the “last mile” problem was the bigger concern. Network formation is evolving rapidly, however, which has made more pressing the question of what it means to connect networks in a uniform way.

While preparing for, and participating in, the recent FHIR Connectathon 11 held in Orlando, Florida, yet another benefit of FHIR’s implementer-friendly philosophy became apparent to me – the ability to facilitate Test-Driven Development (TDD). TDD has been defined as “a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards.” Dating back to 2003, TDD is now considered by many developers to represent the state of their art – shining some much-needed light on the darkness might be another way of looking at it!

Read More »