VA sees problems in open-source development for VistA

Potential hurdles eyed in licensing, certification and governance

The Veterans Affairs Department sees advantages in using open-source software to modernize its Veterans Health Information Systems and Technology Architecture (VistA) system, but it anticipates several problems if it takes that step.

The VA issued a request for information Aug. 11 asking for industry to deal with anticipated concerns related to open-source development for VistA.

The request follows a recommendation from an Industry Advisory Council working group in May 2010 that the VA create an open-source development program to update VistA. VA Chief Information Officer Roger Baker has invited the group to submit advice on modernizing VistA.


Related story:

VA moves closer to IT modernization decision


The VA is seriously considering an open-source development program, but it has reservations about configuration management, copyrights and licensing, governance structure and certification and validation of any open-source code developed in the process, the RFI stated.

“The VA is considering an ‘open-source’ model for VistA that would enable VA to benefit from innovations that third parties could make available according to a code-sharing framework,” the RFI stated. The RFI lists three advantages of open source: the possibility of greater innovation and integration of new capabilities; likely improvements in capabilities, quality, reliability, and robustness; and broader proliferation of common electronic health record software and solutions.

Meanwhile, open-source development also presents problems, the RFI stated.

Although the collaboration in the open-source community brings options, it also requires an appreciation for the necessity of effective configuration management; the sensitivities regarding intellectual property such as copyrights and licensing, the necessary governance around dynamic development collaborations essential to code and "kernel" stability and robustness for the long term, and the absolute necessity for certification, validation and review of code before release, according to the RFI.

The RFI asks vendors to respond to a series of questions about a potential open-source system for VistA modernization. The questions included:

  • What role should VA assume in an Open Source VistA Ecosystem, as user, developer, maintainer, certifier, operator, and/or distributor?
  • What role should non-VA sponsored developers assume in an Open Source VistA Ecosystem?
  • What specific functions of VistA Open Source should the VA be prepared to fund?
  • How would the VA go about participating and collaborating in the open-source community?
  • How would the VA implement software components available through open-source or licensed software channels into the mainline of VistA?

Vendors were invited to respond by Aug. 25 and to submit white papers and additional questions.

About the Author

Alice Lipowicz is a staff writer covering government 2.0, homeland security and other IT policies for Federal Computer Week.

FCW in Print

In the latest issue: Looking back on three decades of big stories in federal IT.

Featured

  • Anne Rung -- Commerce Department Photo

    Exit interview with Anne Rung

    The government's departing top acquisition official said she leaves behind a solid foundation on which to build more effective and efficient federal IT.

  • Charles Phalen

    Administration appoints first head of NBIB

    The National Background Investigations Bureau announced the appointment of its first director as the agency prepares to take over processing government background checks.

  • Sen. James Lankford (R-Okla.)

    Senator: Rigid hiring process pushes millennials from federal work

    Sen. James Lankford (R-Okla.) said agencies are missing out on younger workers because of the government's rigidity, particularly its protracted hiring process.

  • FCW @ 30 GPS

    FCW @ 30

    Since 1987, FCW has covered it all -- the major contracts, the disruptive technologies, the picayune scandals and the many, many people who make federal IT function. Here's a look back at six of the most significant stories.

  • Shutterstock image.

    A 'minibus' appropriations package could be in the cards

    A short-term funding bill is expected by Sept. 30 to keep the federal government operating through early December, but after that the options get more complicated.

  • Defense Secretary Ash Carter speaks at the TechCrunch Disrupt conference in San Francisco

    DOD launches new tech hub in Austin

    The DOD is opening a new Defense Innovation Unit Experimental office in Austin, Texas, while Congress debates legislation that could defund DIUx.

Reader comments

Thu, Aug 19, 2010 AC

Open source software is probably the best choice for governments and large corporations to use for infrastructural software for at least one reason: you have full access to the complete source code and the toolchain required to maintain and upgrade it. With closed source, proprietary, software, you're merely setting yourself up for a future disaster: software companies come and go, and there is no way to predict if a particular company will still be in business at any given point in the future. If your agency, of firm, uses proprietary software for a critical part of your mission, you risk being incapable of performing that mission when the software is obsolete or the company behind the software ceases to exist. Open source software is a prudent choice for agencies, or companies, which require software with service longevity and must have the capability to maintain and upgrade their own systems as need dictates.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group