Five tips to ensure HAC, POA, and never event compliance
Briefings on Coding Compliance Strategies, October 1, 2010
This is an excerpt from a member only article. To read the article in its entirety, please login or subscribe to Briefings on Coding Compliance Strategies.
The POA indicator, hospital-acquired conditions (HAC), and never events have been around for a while. However, they still seem to cause compliance conundrums, says Shannon McCall, RHIA, CCS, CCS-P, CPC, CPC-I, CCDS, director of HIM and coding at HCPro, Inc., in Marblehead, MA.
This is an excerpt from a member only article. To read the article in its entirety, please login or subscribe to Briefings on Coding Compliance Strategies.
Related Products
Most Popular
- Articles
-
- CMS seeks comment on quality measures
- Practice the six rights of medication administration
- Note similarities and differences between HCPCS, CPT® codes
- Don't forget the three checks in medication administration
- OB services: Coding inside and outside of the package
- ICD-10-CM coma, stroke codes require more specific documentation
- Nursing responsibilities for managing pain
- Q&A: Primary, principal, and secondary diagnoses
- Skills of effective case managers
- Clearing up the confusion: CPT codes 76376 and 76377
- E-mailed
-
- Coronavirus vaccination: 4 best practices for communicating with patients
- Grievances, Complaints, and Patients’ Rights
- Keyes Q&A: Generator lighting, fire dampers, eyewash stations, ISLM fire drills
- Including 46600 in E/M leveling systems
- Five keys to creating a CHF disease management program
- Fetal non-stress tests represent important part of maternal and fetal health
- Coding, billing, and documentation tips for teaching physicians, interns, residents, and students
- Coding tip: Know how to correctly code each procedure an otolaryngologist can perform on turbinates
- Coding Clinic reiterates guidelines for provider documentation
- CMS creates web portal for questions about 1135 waivers, PHE
- Searched