Slashdot Mirror


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.

11 of 186 comments (clear)

  1. A consortium of Cerner, Leidos and Accenture by Anonymous Coward · · Score: 5, Insightful

    Jesus Christ what a waste of money and to the worst possible people.

    1. Re:A consortium of Cerner, Leidos and Accenture by arglebargle_xiv · · Score: 5, Insightful

      A large-scale medical records system, a multibillion-dollar IT project, and companies like Accenture doing it, it's like combining herpes, syphillis, and gonorrhea and hoping you'll get a cure for cancer. Any of of those in isolation is pretty much pre-ordained to fail, and they're combing them all into one massive clusterfsck... why don't they just declare failure in advance and save the years of effort (and money).

  2. Trading one for the other by grilled-cheese · · Score: 4, Insightful

    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.

    1. Re:Trading one for the other by phantomfive · · Score: 5, Insightful

      Regardless of whether they are starting with open source software, or closed source software........if I ever paid $4.3 billion for some software, I guarantee I would be getting the source for it. If the government pays that much for a system, one of the requirements should be that it ends up open source.

      --
      "First they came for the slanderers and i said nothing."
  3. follow the money by Lead+Butthead · · Score: 4, Interesting

    follow the money and the answer is in front of you.

    --
    ELOI, ELOI, LAMA SABACHTHANI!?
  4. $4.3 billion == guaranteed failure. by serviscope_minor · · Score: 5, Insightful

    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.
    1. Re:$4.3 billion == guaranteed failure. by wonkavader · · Score: 4, Insightful

      Tom DeMarco talks about the air traffic control software project in one of his books. The description of the hopeless situation in that case supports your idea.

      I think when you have a lot of people's butts on the line and so failure is not an option but stagnation IS, what we would perceive as failure is almost certainly coming. You can retire without any fallout so long as you make sure nothing happens for 15 years. It's easy to do: Just make the specs vague, self-contradictory, and long. Very, very, long.

      The project won't fail, but it won't succeed either. And you're safe, which is all that matters.

      They would do much better to set up a few small teams and have them compete to build something with enough in common so one can be replaced by the other. And starting with the open source base would make sense there.

    2. Re:$4.3 billion == guaranteed failure. by dinfinity · · Score: 5, Insightful

      As far as I can tell, any IT project costing a billion or more is 100% guaranteed to fail.

      No kidding.

      If you pay everybody $200 000 per year, that equates to 21 500 man-years (!) of work. I don't know what kind of problems in record keeping they're going to solve, but for that kind of money it'd better involve employees doing that in gold plated jets flown by an artificially engineered unicorn that continually snorts prime-grade cocaine.

  5. $4.3 billion by lkcl · · Score: 4, Insightful

    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.

  6. gnu project? really? by Anonymous Coward · · Score: 4, Insightful

    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.

  7. VistA is a nightmare by Gravis+Zero · · Score: 5, Interesting

    i was interested in VistA and what all the fuss was about, so i decided to check it out. turns out the backend is nightmare code that would would swear was machine generated. after some investigation i found out it's MUMPS (Massachusetts General Hospital Utility Multi-Programming System) code. a lot of useful stuff started way back in the 1970s... but MUMPS is a 1960s nightmare come to life.

    think i'm exagerating? here's a module from VistA's code which was apparently updated in 1989.

    DENTA1 ;ISC2/SAW,HAG-DENTAL TREATMENT DATA SERVICE REPORTS ; 1/10/89 11:08 AM ; ;;1.2;DENTAL;**24**;JAN 26, 1989
      D:'$D(DT) DT^DICRW S %O="OPT",U="^",S=";",O=$T(@(%O)),DENTV=$$VERSION^XPDUTL("DENT") I $D(^DOPT($P(O,S,5),"VERSION")),(DENTV=^DOPT($P(O,S,5),"VERSION")) G IN
      K ^DOPT($P(O,S,5))
      F I=1:1 Q:$T(@(%O)+I)="" S ^DOPT($P(O,S,5),I,0)=$P($T(@(%O)+I),S,3),^DOPT($P(O,S,5),"B",$P($P($T(@(%O)+I),S,3),"^",1),I)=""
      S K=I-1,^DOPT($P(O,S,5),0)=$P(O,S,4)_U_1_U_K_U_K K I,K,X S ^DOPT($P(O,S,5),"VERSION")=DENTV
    IN I $P(O,S,6)'="" D @($P(O,S,6))
    PR S O=$T(@(%O)),S=";" S IOP=$I D ^%ZIS W:IOST'["PK-" @IOF K IOP
      I $P(O,S,7)'="" D @($P(O,S,7))
      E W !!,$P(O,S,3),":",!,$$VERSION^XPDUTL("DENT")," ",$P($T(+1),S,1),!!,$P(O,S,4),"S:",!
      F J=1:1 Q:'$D(^DOPT($P(O,S,5),J,0)) S K=$S(J0 S Z2=Z1
      G:Z3=0 W I Z3>1 S DIC="^DENT(225,",DIC(0)="AEMNQ",DIC("A")="Select STATION.DIVISION: " S:$D(DENTSTA) DIC("B")=$S(DENTSTA[" ":+DENTSTA,1:DENTSTA) D ^DIC Q:Y

    --
    Anons need not reply. Questions end with a question mark.