Reader feedback: Never events in credentialing
Credentialing Resource Center Connection, July 30, 2009
Want to receive articles like this one in your inbox? Subscribe to Credentialing Resource Center Connection!
Never events is the term those in healthcare give to clinical events that should never happen, such as a wrong site surgery. However, the concept of a never event can apply to other areas of the hospital, including the medical staff services department. Last week we asked readers to tell us which credentialing errors they would deem never events. Here’s what you said:
“For those of us still in the paper credentialing world, a never event would be sending a credential file to off-site storage without having a complete scanned electronic copy as back-up in the event a file becomes irretrievable.”
“As a health care lawyer who frequently works with medical staff coordinators and reviews credentialing files, the occasional file that I see where there is a failure to query the NPDB for a reappointment or the failure to query the NPDB BEFORE the extension of temporary privileges still amazes me. Would seem that this should be a ‘never event’.”
“Physicians reappointment missed due to computer or human error, i.e., reappointment beyond two-year period.”
“I would definitely say making an erroneous report to the NPDB. At our facility, we have two CRNAs, both with the same first name. One last name is Reid and the other Reed. Careful, careful!”
“Our CVO created Red Rules. Red Rules are standards that are akin to never events and could result in disciplinary action up to and including termination. Those are as follows:
Want to receive articles like this one in your inbox? Subscribe to Credentialing Resource Center Connection!
Related Products
Most Popular
- Articles
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- Catch up on what's new with injections and infusions
- Identify potential Medicaid RAC target areas
- HIPAA Q&A: Level of encryption needed for email
- Topic: CMS, OESS post new security compliance review information, checklist
- Capturing all necessary codes for IUD insertion and removal can be challenging
- What does case-mix index mean to you?
- OB services: Coding inside and outside of the package
- QA:Coding multiple initial infusions
- E-mailed
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- HIPAA Q&A: Level of encryption needed for email
- Q&A: Follow CMS' coding guidelines when using modifier -25
- What does case-mix index mean to you?
- Catch up on what's new with injections and infusions
- CMS has reformulated payments for some bilateral procedures
- New conflicts of interest create new challenges
- Q/A. One injection code or two?
- ED-to-inpatient transfers are flawed with safety gaps
- Searched
