Government  Health IT
TwitterFacebookLinkedIn
  • Home
  • Topics
    • Cloud Computing
    • Election 2012
    • Electronic Health Record
    • ePrescribing
    • Health Information Exchange (HIE)
    • Meaningful Use
    • Medicaid
    • Medicare
    • Military Health
    • Mobile/ Wireless
    • NHIN
    • Policy & Legislation
    • Population Health
    • Privacy and Security
    • Quality and Safety
    • Telehealth
    • Workforce Management
  • Issues
    • Sept/Oct 2011
    • July/August 2011
    • May/June 2011
    • March/April 2011
    • Jan/Feb 2011
    • Nov/Dec 2010
  • Webinars
    • Upcoming Webinars
    • On Demand Webinars
  • White Papers
  • Blog
  • Events
  • Jobs
  • RSS
  • Slideshows
  • Videos
  • Podcasts
  • Newsletters
  • Advertise
  • LOGIN
  • REGISTER
  • SUBSCRIBE
Home » News » Cloud Computing | Policy & Legislation | Population Health | Privacy and Security | Quality and Safety
Receive News
By Email

  • del.icio.us
  • Digg
  • Facebook
  • Google
  • Reddit
  • StumbleUpon
  • RSS Icon
  

Tweet

Mostashari assures patient safety plan sooner than 12 months

November 09, 2011 | Mary Mosquera

Suggested Content

  • Perspective: HIE, 'omics' and personalized medicine
  • Alzheimer's connection project wins HHS innovation award
  • HIE 2.0 closer than it might appear
  • Mostashari tells EHR makers to sort out safety event reporting
  • HHS already a federal cloud leader
  • i2b2 open source software boosts HIE, biomedical research
  • Datapalooza spotlights public, private hunger for health innovation
  • Tapping big data for early identification of preventable conditions

Related Resources

  • QualSight LASIK Achieves HIPAA Compliance After Attempted Hack
  • Cloud Services Leverage Provider IT Resources and Ensure Continued Service Levels
  • Saving Lives Virtually – A Day in the Life of Today’s Physician
  • Sizing Up Your Cloud Options - Is Now the Time?
  • Proactive Security and Privacy Monitoring for Modern Healthcare Networks

Dr. Farzad Mostashari, the national health IT coordinator, said that agencies in the Health and Human Services Department will work closely to craft a surveillance and action plan to keep patients safer through health IT, and it will be done sooner than called for by the Institute of Medicine.

An IOM report published this week directed ONC as the office that oversees health IT to complete its plan within 12 months.

“We appreciate the IOM’s recommendations in making sure that we really do have a coherent structure for reporting, analyzing and acting on the information about EHR-related safety incidents,” he said at the Nov. 9 meeting of the advisory Health IT Policy Committee. 

He added that the committee will be an important part of bringing health IT stakeholders together for discussions about patient safety. The IOM calls for the freer flow of safety-related information and action by all stakeholders. 

Mostashari said that the Office of the National Coordinator for Health IT will coordinate with the Food and Drug Administration (FDA), which regulates medical devices, and the Agency for Healthcare Research and Quality (AHRQ), which sponsors patient safety organizations, and the National Institute for Standards and Technology (NIST).

[Related: NIST's 10 cloud computing requirements.]

ONC has worked with AHRQ and FDA to promote reporting by EHR vendors on adverse events through patient safety organizations and with NIST to develop standards for EHR testing, measuring and usability.

In its report, IOM reaffirmed its faith in the potential for health IT to improve safety, Mostashari said. But it also made important recommendations to make sure that health IT’s potential is fully realized. The report becomes part of ONC’s long-term strategy for building in safety from the beginning as adoption of health IT moves forward, he said. 

Safety is not just about reliable EHR system software product performance. Mostashari said that the report emphasized that “safety is a system.”

“Successful use of health IT means that we have to understand safety as part of the systematic approach. It means, system usability issues, having the right relationship between design of EHRs and the workflows,” he said.

In response to questions about whether FDA should be regulating EHRs as devices, Mostashari said that it was “clearly one of the most controversial issues that the committee struggled with.”

”My understanding of the report is that one of the key issues was the recognition that a broader set of issues needs to be addressed, not just the devices, but the entire system of how care is delivered, how training is done, and how workflows are done,” he said.

The report cites the need to balance the innovation agenda, and some of the concerns they expressed around the expertise needed for this may be different from device regulation in general, he said.

According to the IOM recommendations released Nov. 8, HHS should establish some mechanism for both technology vendors and users to report health IT-related deaths, injuries or unsafe conditions. Adverse event reporting related to patient safety should be required for vendors and voluntary, confidential, and non-punitive for healthcare providers, according to the report, “Health IT and Patient Safety: Building Safer Systems for Better Care.”

Also, Congress should establish an independent federal entity, similar to the National Transportation Safety Board for health IT, to investigate patient deaths, injuries, or potential unsafe conditions associated with health IT and make non-binding recommendations that allow for HHS, providers and vendors to determine the best course forward.

IOM also recommended that HHS fund a Health IT Safety Council to evaluate criteria and develop methods for assessing and monitoring safety and measuring impacts of health IT on safety.

That includes making sure that health IT vendors support the free exchange of information and not discourage health care providers from sharing patient safety concerns, including screen shots. Nondisclosure agreements in contracts between vendors and healthcare providers and "hold harmless" clauses that shift the liability of unsafe health IT features to care providers greatly discourage information sharing, the report said.

HHS should also establish quality management principles and risk management processes in designing and implementing health IT products, which can be complex and difficult for doctors and nurses to use. Alerts in technology systems should be designed to have lower false-alarm rates and computer interfaces need to be more intuitive for users.

 

Mary Mosquera
Senior Editor for Healthcare Finance News
Follow Mary on Twitter @GovHITreporter
Related Topics:
  • Online Only
  • Cloud Computing
  • Policy & Legislation
  • Population Health
  • Privacy and Security
  • Quality and Safety
  • Quotation
  • Building Safer Systems
  • Institute of Medicine
  • National Institute
  • computing
  • healthcare
  • Congress
  • Farzad Mostashari
  • Food and Drug Administration
  • http://www.iom.edu/Reports/2011/Health-IT-and-Patient-Safety-Building-Safer-Systems-for-Better-Care.aspx

Reader Comments (1)Login to Post a Comment

Jsparco says: Establish better control
December 05, 2011 | 7:52AM GMT
I'm glad to see a plan sooner than 12 months is in the work. These should have been established long ago. The management process needs to be more secure and implemented across more health IT products. Our Orlando Physicians Funds help secure our money, now we need better alerts for our technology.

Most Popular

Latest Headlines
Most Popular
  • Is big data the new oil?
  • MGMA finds practices in the dark about ICD-10
  • 3 patient engagement lessons
  • Integrating social services IT brings benefits, risks
  • MHS, Navy CIOs open up about iEHR
  • 10 health reform benefits at risk in the election
  • Would Romney kill meaningful use?
  • CMS circulates final 2014 MU clinical quality measures
  • HIE is critical public utility in Sandy disaster
  • HIMSS: The intangibles of HIT employee retention
more news

WEBINARS AND WHITE PAPERS

  • WHITE PAPERS
    A Reference Architecture for Healthcare Benefit Exchange
  • WHITE PAPERS
    Your Cloud in Healthcare - How to Use the Cloud to Achieve Greater Business Agility
  • WHITE PAPERS
    Key Benefits to a Secure & Elastic Private Cloud
  • WHITE PAPERS
    Cloud Computing in the Healthcare Environment
  • WHITE PAPERS
    Beyond the EHR: Seamlessly Connecting Nurses and Physicians Using an EHR-Extender (EHR-e)
More Resources
Syndicate content

HIMSS JOBMINE

  • Senior Consultant- Payer Strategy- Data Analytics (SAS) - Navigant Consulting - Chicago, Illinois
  • Managing Consultant- Payer Strategy- Data Analytics (SAS) - Navigant Consulting - Chicago, Illinois
  • Chief Solutions Architect - Harris Healthcare Solutions - Melbourne, Florida
  • Sr. Manager, Interoperability Initiatives - HIMSS - Cleveland, Ohio
  • Executive Consultant - Revenue Cycle and ICD-10 - Beacon Partners - New York
more jobs
receive news by email

Marketplace

  • Home
  • Resource Central
  • Blog
  • Events
  • Jobs
  • Mobile Site
  • Advertise
  • RSS
  • About
  • Site map
  • Privacy Policy
Follow Government Health IT on TwitterLike Government Health IT on FacebookJoin Government Health IT on LinkedInRSS Subscriptions
BlogEvents
JobsMobile SiteMobile App
 
Healthcare IT NewsHealthcare Finance NewsHealthcare Payer NewsHIEWatch ICD10Watch mHIMSS PhysBizTech
©2013 MedTech Media Government Health IT is a publication of MedTech Media
Advertise About Us Privacy Policy