HHS panel advises on data glitches that affect patient safety

Digital record systems should include feedback buttons to spur reporting

Hospitals and doctors should be required to report data glitches that create “hazards and near-misses” that affect patient safety to a national patient safety organization starting in 2013, according to recommendations proposed today by a Health and Human Services Department advisory workgroup.

In addition, patients also should be encouraged to report errors, omissions and other mistakes in their medical records, and electronic health record (EHR) systems should include “feedback” buttons to quickly report data problems that occur when using the systems.

The Adoption/Certification Workgroup of the HHS Health Information Technology Policy Committee considered a draft proposal today that outlined best practices for electronic reporting of patient safety hazards and near misses. The practices are expected to be included in the second phase of “meaningful use” of EHR systems, starting in fiscal 2013.

Under the economic stimulus law, Congress approved $17 billion to be distributed to hospitals and doctors who demonstrate meaningful use of EHR systems. The first phase of the distribution begins Oct. 1.

Although using digitized records can lead to improved patient safety, it also has been associated with some safety risks that may affect patient care. These include technology problems such as hardware failures, software bugs, and incompatibility between applications and interfaces. Implementation and training deficiencies also create risks.

Workgroup members said the goal is to establish a “patient-centered” approach to health IT safety, which includes confidential reporting, liability protections, whistle-blower protections, patients engaged in the system and transparency.

“Most unsafe conditions are not the result of a single software error. Instead, multiple factors are involved, including challenges with usability, processes, and interoperability,” the draft proposal states.

The reporting system would cover usability, processes, and training, and would span all software, including that software sold by vendors, self-developed and open-source software.

To encourage reporting, vendors should include feedback buttons that appear on the screens allowing quick and easy reporting of data errors, omissions, or other data problems. Certification of record systems should include a requirement for this functionality, the draft report recommended.

Vendors also should maintain records on all patient safety concerns reported by their customers and provide safety alerts to customers on such concerns. They should also build in patient safety testing into their products.

Patients also should be encouraged in finding errors and mistakes in their electronic records, either by accessing their provider’s EHR system or by downloading the information to a personal health record. Feedback buttons to report errors also are recommended for those applications.

For a more comprehensive picture of patient safety issues related to data errors, the panel recommended that the Office of the National Coordinator for Health IT commission a formal study to thoroughly evaluate health IT patient safety concerns and to look into the possibility of audit trails for health information exchange activities.

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

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