VistA to be saved as open source

By | May 10, 2010, 9:04am PDT

Summary: The report is filled with praise not just for open source software but the open source process.

A working group representing both government and contractor interests has recommended that VistA, the Veteran Administration’s aging Electronic Health Records (EHR) system, be rewritten, but that the effort be done under open source licence and the result be backward-compatible with the current VistA.

Thw 101 page VistA Modernization Report has been posted to the site of the American Council for Technology.

VistA, first written in the 1980s using a technology called MUMPS, has been under fire for years. It is said to be obsolete, although it’s probably the most-used Electronic Health Record (EHR) program in the world.

It has been assumed for years VistA would be replaced, but the question is how and by what. The new report shows a 180 degree turnaround in attitudes on the how and what.

The report is filled with praise not just for open source software but the open source process. Here is what I consider the “nut graph,” from page 88 of the report:

The open source market and open solutions strategy are are growing modestly and can be stimulated to grow rapidly across different markets.

This is a sea change in attitudes from a few years ago, when the previous Administration was starving VistA of resources and handed its lab work to Cerner under contract. Now open source is “obviously” the way to go and private companies involved in contracting for the government agree. Oh, and backward compatibility is essential.

With this kind of consensus it seems momentum for an open source VistA replacement seems well underway. The key question now is how many people will be hired, full-time, to build the VistA 2.0 community, how transparent that process will be, and how much of the work will still be done by contractors.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Disclosure

Dana Blankenhorn

Dana Blankenhorn has been a journalist, writer and part-time futurist for over 30 years. At the present moment I run only a personal blog in addition to my ZDNet open source blog. DanaBlankenhorn.Com has the subtitle The War Against Oil. In the past I have used it to write about political history, e-commerce, personal matters, some ideas related to open source, and The World of Always On, which is the idea of using sensors, motes and RFID to turn WiFi links into platforms for applications which live in the air. My IRA account at Schwab holds a few tech shares, most notably some Intel and Applied Materials, but there are no open source companies in it. I don’t even own any CBS stock.

Biography

Dana Blankenhorn

Dana Blankenhorn has been a business journalist since 1978, and has covered technology since 1982. He launched the Interactive Age Daily, the first daily coverage of the Internet to launch with a magazine, in September 1994.
7
Comments

Join the conversation!

Just In

Funny how people keep talking about rewrites:
bobtran Updated - 14th May 2010
when what they really mean is putting a GUI front-end on a mainframe application. However, if I'm not mistaken the VA patient record input system is actually running on NT. People have become used to accessing data using browser based systems for years now and very few actually realize what is involved in a rewrite of a back end system. Most rewrites consist of putting lipstick on the pig and pretending that putting just one more layer of interface is really change. IT IS NOT. This system is actually very functional and stable, It just doesn't have the modern GUI that people have come to identify as New and Different. Change for changes sake is a failed business model and the people who have to maintain these systems realize this little fact. It doesn't matter how the data is stored as long as there is a way to access and present it. This is what most people consider a rewrite and for the life of me I really can't understand why we as tax payers want to pay a subcontractor a huge amount of money to make the presentation of the data pretty because thats all we are really going to get.
0 Votes
+ -
Rewritten? In what I wonder, did they say? It's all MUMPS as I understand.
Dietrich T. Schmitz,Your Linux Advocate 10th May 2010
nt
0 Votes
+ -
That is one of the open questions
DanaBlankenhorn 10th May 2010
What language or form it's rewritten in has yet to be decided. MUMPS is not going to be it.
0 Votes
+ -
Wow, someone wrote a paper.
willswords@... 11th May 2010
Nice, but doesn't mean anything without any $ behind it.
0 Votes
+ -
While the system may be "out of date" it holds a massive amount of patient information. Basic medical records, lab reports, imaging reports as well as the actual images.

It would finally appear that people are finally looking at what is actually in use everyday and the challenge of "converting" data and information to a new system.

I'll vote for updating VistA, increasing the Vet's access to it, simplifying it's use for new medical personnel who need to learn the system. Effective development and certainly not a major interruption in the delivery of health care to Vets.
0 Votes
+ -
Rather than re-write what I already wrote on LMN:

"...Overall this report appears to be progressive in its embrace of open source when in reality it is highly regressive by its inclusion of proprietary EHR software and a massive re-engineering approach instead of limited refactoring. The UK experience has shown that this approach can be disastrous. The VA's VistA EHR is successful because it consciously eliminated proprietary EHR software to a large degree. The report attempts a utopian picture of open source and proprietary EHR software standing shoulder to shoulder and singing kumbaya. This is a highly unlikely scenario that would greatly jeopardize and fly in the face of VA's long open source software history and track record of success..."

http://linuxmednews.com/1273200424/index_html
0 Votes
+ -
RE: VistA to be saved as open source
martymen 11th May 2010
Obsolete - not! The MUMPS database technology, whether Cach???? or GT.M, is faster, more scalable and logically comprehensible than any RDBMS I've ever seen. I say this after 30 years of working with both varieties. I can devise and instantiate a MUMPS database in half the time it takes in a relational, and since both major MUMPS implementations can be exposed to SQL they are accessible even to non-MUMPS programmers. People... new and improved is a myth!
0 Votes
+ -
Funny how people keep talking about rewrites:
bobtran Updated - 14th May 2010
when what they really mean is putting a GUI front-end on a mainframe application. However, if I'm not mistaken the VA patient record input system is actually running on NT. People have become used to accessing data using browser based systems for years now and very few actually realize what is involved in a rewrite of a back end system. Most rewrites consist of putting lipstick on the pig and pretending that putting just one more layer of interface is really change. IT IS NOT. This system is actually very functional and stable, It just doesn't have the modern GUI that people have come to identify as New and Different. Change for changes sake is a failed business model and the people who have to maintain these systems realize this little fact. It doesn't matter how the data is stored as long as there is a way to access and present it. This is what most people consider a rewrite and for the life of me I really can't understand why we as tax payers want to pay a subcontractor a huge amount of money to make the presentation of the data pretty because thats all we are really going to get.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix