Slashdot Mirror
Stimulus Avoids Serious Solutions For Health IT
ivaldes3 writes in to note his post up on Linux Medical News, pointing out the severe shortcomings of the Health IT provisions of the just-passed stimulus bill. "The government has authorized enough money to purchase EMR freedom for the nation. Instead the government appears set to double down on proprietary lock-down. The government currently appears poised to purchase serfdom instead of freedom and performance for patients, practitioners and the nation. An intellectual and financial servitude to proprietary EMR companies for little or no gain. A truly bad bargain."
I read the article.
The guy's central point is that corporate systems are bad, and open, federally funded systems are good, with the further implication that government is good, and corporations are bad.
Now, the reason, though, that he gives for this is that a private corporation owns his data in the present system, but if the government owned, then, somehow, he'd own it more.
That's the crazy thing. There's no such thing as "public ownership". You own as much of something that is public as you do a car by walking past a Ford factory. Ownership at its most practical is, who controls it, and you really don't have any control over the daily disposition of property managed by the government. In effect, when you argue for publicly owned health care, or publicly owned anything, what you are really arguing for is to pay your own taxes to buy something for some administrator either elected or appointed or a lifelong civil servant. In any case, its not you.
There's a lot of good reasons to adopt open source in health care. For one, the creation of a single standard document for representing a medical history would go a long way towards enabling applications across the medical spectrum to coexist.
This will be easier said than done.
A good example is that there were some efforts to do this in insuring property for catastrophic losses - a build is remarkably complex for insurance purposes, but that specification has essentially died by its own complexity. The industry largely and thankfully essentially resorted to using SQL Server copies of the leading vendor of property and casualty software for CAT. Is it proprietary? Yes. But, it allows all the insurers to exchange books in a way that is relatively practical and easy to use.
The moral here is that its not good enough to say that a standard is open for data interoperability. Ease of use and ease of transportability becomes paramount and if open source wants to drive health insurance, it stands to reason that there needs to be a pervasive application that goes along with it.
This is my sig.
At least down here in Texas, any grant money funded through DSHS as well as HRSA at the federal level have specific sections that state that any system proposed that makes use of the VistA system will receive higher consideration to getting funded above any proprietary solution. Unfortunately the available solutions are still very high risk and many hospitals and other healthcare entities really don't like the look and feel when compared against proprietary browser-based systems.
I use the proprietary systems and had attempts at open systems (there are always "shoot outs" at the medical conferences) and I can say that the proprietary systems suck much less.
It's all about workflow. The open systems fail to understand this concept.