DoD Ditches Open Source Medical Records System In $4.3B Contract
dmr001 writes: The US Department of Defense opted not to use the Department of Veterans Affairs' open source VistA electronic health record system in its project to overhaul its legacy systems, instead opting for a consortium of Cerner, Leidos and Accenture. The initial $4.3 billion implementation is expected to be the first part of a $9 billion dollar project. The Under Secretary for Acquisition stated they wanted a system with minimum modifications and interoperability with private sector systems, though much of what passes for inter-vendor operability in the marketplace is more aspirational than operable. The DoD aims to start implementation at 8 sites in the Pacific Northwest by the end of 2016, noting that "legacy systems are eating us alive in terms of support and maintenance," consuming 95% of the Military Health Systems IT budget.
Jesus Christ what a waste of money and to the worst possible people.
It's interesting how they see integrating legacy systems any differently integrating just as many differently implemented commercial record systems. The data integrators will make the same money either way. By abandoning the open-source solution, you're just losing the possibility others might benefit from the work. Likewise, I'm curious how much those 3 vendors have lobbied in Washington DC.
As far as I can tell, any IT project costing a billion or more is 100% guaranteed to fail.
Also, it sounds like they decided to source IT from Lufier, Mephistopheles and Satan, which incidentally also guarantees it to fail.
SJW n. One who posts facts.
Project already failed.
wow fuck. imagine how much advancement in software libre could be had for $4.3 billion if the contract had been awared. hell, even 1% of that would make a big fucking difference. someone - such as the gnumed developers to take even one random example - could, with help, have developed a medical records system for ohhh i dunno... the U.S. Dept of Defense, with that kind of money. just to take a random example, y'ken.
That is part of the problem .. trying to design a drop in replacement that replicates the current functionality and interoperability with other systems.
With government especially, you have lists of exceptions and custom one-off code to get something working, that it becomes impracticable to replace it without an equal or additional number of exceptions.
It's the kind of system that benefits from a "flush it all away" mentality of defining new standards and sticking to them.
And who, in the gnu community, is going to take on the responsibility for all the enterprise scale stuff that needs to be done. I can see lots of folks wanting to scratch their particular itch by coding up some piece, but who's going to do the architecture design, ride herd on the developers, etc.; make sure that the documentation gets done and is usable and readable (because, ya know, all those packages out on github and sourceforge are ever so well documented)..
I mean responsibility as in "be willing to stand up in front of Congress and explain your progress or lack thereof". I don't see a Linus or Theo or Eric or, gods forbid, Richard, filling that role.
Exactly. This is just more disgusting Republican corporate welfare.