News: RACs target ventilator supportPRINT THIS PAGE | RETURN TO ARTICLE
July 21, 2011
RACs can easily data-mine for noncompliance related to coding for ventilator support, says Glenn Krauss, BBA, RHIA, CCS, CCS-P, CPUR, C-CDI, CCDS, independent revenue cycle consultant in Madison, WI. For example, patients whose length of stay is fewer than two days can’t possibly be on a ventilator for 96 hours. "Simple math tells you this can't be correct," Krauss says. "Technically speaking, they almost don't even need to look at the record; they can tell by an automated review."
Coders should always refer to the respiratory flow sheet before coding any services related to ventilator support, he says. This flow sheet includes the intubation time, periodic dating and timing of ventilator management services, and the extubation time.
"If coders don't have the flow sheet, they absolutely need to track it down," Krauss emphasizes, adding that a hospital's coding compliance policy should explicitly mandate this.
Coders shouldn't rely entirely on physician orders of intubation and extubation times, agrees Alice Zentner, RHIA, director of auditing and education at TrustHCS in Springfield, MO. "Coders need to go by the actual documentation. They need to have solid documentation of the times," she says.
However, even when documentation exists, counting the number of ventilator hours can sometimes be confusing. Coding Clinic has yet to provide guidance regarding what to do in scenarios where a patient doesn't receive a full hour of ventilator support, says Zentner. For example, should coders report an additional hour of ventilation when the patient receives only 25 minutes? Without definitive guidance, Zentner cautions against it.
Here are a few pointers on what can count when calculating ventilator hours:
Here's what coders can't include when counting ventilator hours and what RACs may look for when trying to identify overpayments:
CDI specialists need to be aware of the expectations and limitations of what coders can and cannot use and help to obtain clarity for such situations when warranted.
Editor’s Note: This article first appeared in the July issue of Briefings on Coding Compliance Strategies.
Copyright © 2013. HCPro, Inc. All rights reserved.