According to researchers at the University of Texas at Houston Health Sciences Center, developers of electronic health records (EHRs) have created products that enable healthcare facilities to meet the safety recommendations of the EHR Resilience Safety Guide Factor Insurance (SAFER). Or need to change. (UTHealth) and Baylor College of Medicine.
The Treaty “Policies to Promote Shared Responsibility for Safer Electronic Health Records” Today Journal of the American Medical Association (JAMA).
NOT. PLUS SR Guide A comprehensive overview of security practices organized as a checklist and designed to help health Healthcare organizations and EHR developers perform an EHR self-assessment. Their goal is to proactively optimize the safety and safe use of the EHR. The guide is sponsored by Office of the National Coordinator of Medical Information Technology (ONC) Within the Ministry of Health and Social Welfare.
“Earlier this year, the Medicare & Medicaid Service Center (CMS) announced new payment rules that require all qualified hospitals to use SAFER guides,” said a professor of biomedical informatics at UT Health School of Biomedical Informatics. said Dr Dean Sittig. Co-author of the treaty. “This new rule required DSE developers to use the SAFER guide. Therefore, EHR system developers are also encouraged to evaluate their products annually, which allows customers to subsequently evaluate the EHR. It will be implemented and used according to the recommendations of the SAFER guide. “
“We believe the new CMS regulations are a breakthrough in EHR safety affecting all hospitals in the United States,” said the article’s co-author, Baylor Professor of Medicine and Quality Manager. , Efficiency, Safety (IQuESt) and Michael E. Devakey VA Medical Center. “Nevertheless, Hospitals to achieve the quality and safety improvements promised by a leading EHR You should also involve DSE developers in the implementation of security practices. ”
The new CMS policy, which requires hospitals to conduct annual self-assessments using the SAFER guide, creates a solid foundation, but the author states that responsibilities for safety should be shared with EHR developers. ..
Sittig and Singh recommend three specific strategies that complement the new CMS rules. They propose:
- EHR developers self-assess their products annually against SAFER recommendations and indicate whether the EHR can be configured to meet each SAFER recommendation.
- ONC should conduct an annual review of SAFER recommendations to take into account changes in the design, development and configuration of the EHR.
- EHR developers should disseminate guidance to their customers on how to implement security practices related to their products.
They say these strategies reinforce the solid foundation of EHR security built by the new CMS regulations and more evenly distribute the responsibility for creation. Improved security Between those who design and develop EHRs and those who configure, implement and use these systems.
“Some EHRs have already used the SAFER guide to evaluate their products and create tips for their customers,” says Sittig. “In most cases, EHRs work well. No one expects a computer or its use to cause errors, but if it does, it can cause serious harm to the patient. The joint use of the SAFER guide can prevent such a situation. Problem. ”
Dean F. Sittig et al, Policy to Promote Shared Responsibility for Safer Electronic Health Records, JAMA (2021). DOI: 10.1001 / jama.2021.13945
University of Texas Health Sciences Center
Quote: Experts found safer electronic health record (9 2021) obtained on September 10, 2021 from https://medicalxpress.com/news/2021-09-experts-policies-safer-electronic-health.html. We have a policy for the (March 10)
This document is subject to copyright. No part may be reproduced without written permission, except for fair dealings for the purposes of personal investigation or research. The content is provided for informational purposes only.