HHS seeking solutions to address FISMA compliance for health exchange

Health and Human Services Department official calls FISMA a hurdle to patient data exchange

Health and Human Services Department officials are looking for information technology solutions that comply with a key federal cybersecurity law while also allowing for exchange of federal health data with private entities, a senior health data exchange official said today.

Currently, federal medical agencies that handle patient data must comply with the Federal Information Security Management Act. If they want to share that data, the recipients also may need to comply with FISMA, according to Vish Sankaran, program director of HHS’ Federal Health Architecture. Similar issues apply to compliance with the Health Insurance Portability and Accountability Act , he added.

Sankaran said federal agencies are looking for guidance and solutions to enable them to exchange patient data while also maintaining compliance with FISMA.

One possibility being considered is a legal mechanism that may involve the patient authorizing transfer of the data so that it is no longer federal data, he suggested. The department also is considering technical solutions, such as use of intermediaries, cloud computing or Software as a Service, which might allow for FISMA compliance with both sender and recipient.

The federal health architecture office, which is part of HHS’ Office of the National Coordinator for Health IT, has been working to develop health data exchange with 20 federal agencies on the Nationwide Health Information Network, currently a pilot project. The office also has developed free open-source software, known as Connect, enabling parties to connect to the NHIN.

Next year, the office will release the third update of Connect, which can be used, in conjunction with Electronic Health Records, to fulfill the meaningful use standards of the economic stimulus law, Sankaran said.

Currently, the Social Security Administration is demonstrating secure exchange on the NHIN, and Sankaran said his office is preparing to offer several contracts for NHIN technical support that will help move the NHIN to full production.

In December, the national coordinator’s office will begin distributing $564 million in grants for state-based Health Information Exchanges, which will eventually be linked with the NHIN as well.

In early 2010, the office will release Connect 3.0, which can be used, in conjunction with electronic health records, to fulfill the meaningful use standards of the economic stimulus law, Sankaran said. Under the law, HHS will distribute $19 billion to doctors and hospitals that purchase certified electronic record systems and demonstrate meaningful use of those systems.

About the Author

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

The Fed 100

Save the date for 28th annual Federal 100 Awards Gala.

Featured

  • Social network, census

    5 predictions for federal IT in 2017

    As the Trump team takes control, here's what the tech community can expect.

  • Rep. Gerald Connolly

    Connolly warns on workforce changes

    The ranking member of the House Oversight Committee's Government Operations panel warns that Congress will look to legislate changes to the federal workforce.

  • President Donald J. Trump delivers his inaugural address

    How will Trump lead on tech?

    The businessman turned reality star turned U.S. president clearly has mastered Twitter, but what will his administration mean for broader technology issues?

  • Login.gov moving ahead

    The bid to establish a single login for accessing government services is moving again on the last full day of the Obama presidency.

  • Shutterstock image (by Jirsak): customer care, relationship management, and leadership concept.

    Obama wraps up security clearance reforms

    In a last-minute executive order, President Obama institutes structural reforms to the security clearance process designed to create a more unified system across government agencies.

  • Shutterstock image: breached lock.

    What cyber can learn from counterterrorism

    The U.S. has to look at its experience in developing post-9/11 counterterrorism policies to inform efforts to formalize cybersecurity policies, says a senior official.

Reader comments

Fri, Nov 13, 2009

Well, unfortunately, HHS is required to comply with FISMA for any and all of its information systems, so this is a valid challenge. FISMA in of itself isn't the problem - the problem is that you can create all the security frameworks you want for the government, but until they provide the funding to enable implementation, and enforce repercussions to those agencies that don't comply, nothing will work. FISMA in the hands of unqualified personnel results in a battle for "perceived compliance" rather than true security. Any other security framework would suffer the same fate.

Fri, Nov 13, 2009

FISMA? FISMA has nothing to do with the transfer of Health data, that is the sole realm of HIPPA. FISMA relates to the security of systems not the type of data being transfered. Also FISMA in and of itself is NOT a secure approach. As can be seen in several newsworthy examples, agencies can score very high on FISMA and not be secure. Compliance does not equate to Security - if it did, we would not have so many notable breeches.

Thu, Nov 12, 2009 Jeremy Engdahl-Johnson Seattle, WA

Federal funding may be encouraging a move toward EHR, but there's more to it than just installing systems. How can healthcare data pooling lead to a better system? More at http://www.healthcaretownhall.com/?p=1499

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