recommended reading

No Defense-VA integrated electronic health record until 2017

Manuel Balce Ceneta/AP

The Defense and Veterans Affairs departments will not deploy an integrated electronic health record until 2017, eight years after President Obama kick-started the project, according to Defense Secretary Leon Panetta and VA Secretary Eric Shinseki.

Panetta noted an initial version of iEHR will be deployed by 2014 to medical facilities in San Antonio and Norfok, Va., -- a plan announced in April by VA Chief Information Officer Roger Baker -- but Panetta did not provide any new details.

Panetta and Shinseki spoke to reporters Monday at the James A. Lovell Federal Health Care Center, a jointly operated North Chicago Defense-VA hospital that serves as a showcase for iEHR projects.

“This center is the first-of-a-kind partnership between our two departments,” Panetta said. “This really is a unique demonstration effort to try to bring together the DoD and VA systems.”

The reason for the long delay from concept to execution for the iEHR has been partly bureaucratic. Defense and VA did not agree on the basic structure and management of the iEHR until May 2011, and top officials from both departments deferred signing the charter for the Interagency Program Office, which will manage deployment of iEHR until October 2011.

The two departments put off until February selecting a director of the Interagency Program Office, Barclay Butler, a former vice president of Harris Healthcare who also served as the chief information officer for the Army Medical Department in 2001 and 2002, until this February.

Panetta said when it’s completed, iEHR will stand out as “the world's largest electronic health record system” and Shinseki said a project of such scale and importance requires a deliberate approach so “we can get it right.”

Shinseki added, “We'll go as fast as we can without accepting risk that's not tolerable. 2017 is a target. We're going to begin rolling out the initial capabilities of iEHR in 2014 at those two sites we indicated. If we can go faster, we will. But quality and safety are the standards we measure ourselves by.”

Development of iEHR is a “significant challenge” he added. “I think the folks who work here can provide you insights on that.”

Shinseki did not specify the iEHR challenges the staff at Lovell faces, but Lt. Cmdr. Donna Poulin, the hospital’s chief information systems officer, detailed them in an internal presentation obtained by Nextgov, which highlights problems Defense and VA face as they develop the joint record.

Poulin said the iEHR graphical user interface for clinicians that the VA medical center in Honolulu developed and piloted at Lovell functions in a read-only mode, meaning clinicians cannot input data. Clinicians at Lovell must access three separate networks -- VA, Defense and Navy -- all of which use different methods to authenticate end users, and each has different cybersecurity policies.

Shinseki emphasized iEHR will be “open in architecture and nonproprietary in design to expand information sharing [and to] eliminate gaps between our two robust health care systems,” in keeping with the use of open source software that he backed in April.

This approach conflicts with Defense plans to use commercial software in developing iEHR, according to a Pentagon report submitted to Congress in April -- the opening salvo in what a former top VA official, who declined to be identified, called a battle between the two departments over the basic structure of the iEHR.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.