10.3 Revenue Integrity Program Design

Designing Revenue Integrity Controls

AHIMA's RHIA Domain 4 includes revenue integrity — coding audits, denials management, and fraud prevention. Revenue integrity is the bridge between accurate health information and accurate reimbursement. It protects the organization in two directions: preventing missed legitimate revenue and preventing unsupported billing that creates compliance risk. It is not the same as revenue maximization.

A revenue integrity program must not be a loose pile of cleanup tasks. It defines governance, ownership, monitoring, escalation, and corrective action. The RHIA partners with revenue integrity leaders, compliance, billing, patient financial services, finance, clinical departments, CDI, coding, and IT. The program is strongest when every stakeholder knows which data or control it owns.

Metrics That Reveal Program Health

A mature program watches a dashboard, not anecdotes. Core indicators:

• DNFB (discharged-not-final-billed) — accounts discharged but not yet billed, often held for coding or documentation; high DNFB ties up cash.
• Discharged-not-submitted / bill-hold days — lag between coding completion and claim submission.
• Clean-claim rate — percentage passing edits on first submission.
• Initial denial rate and denial overturn rate.
• A/R days and aged-A/R buckets (e.g., > 90 days).
• Net collection rate and cost to collect.

These tie back to other RHIA domains: data governance supplies standard definitions, analytics supplies the dashboards, and leadership supplies staffing and accountability.

A Worked Scenario

A hospital launches a new interventional cardiology service and three months later sees a spike in denials and write-offs. A strong revenue integrity response reviews the CDM build (correct CPT/HCPCS, revenue codes, units), the charge-capture workflow, provider documentation, coding rules, payer prior-authorization requirements, claim scrubber edits, and the specific denial reasons — then assigns a named owner to each corrective action and reaudits. A weak response tells staff to "work faster" or to appeal every denial without fixing the front-end.

Risk-Based Governance

Revenue integrity must be risk-based, not exhaustive. Focus controls where exposure justifies effort: high-dollar services, new technology, high-denial procedures, complex modifier use, government-payer volume, and areas with recent OIG or RAC (Recovery Audit Contractor) findings. A governance structure typically includes:

• A cross-functional revenue integrity committee with charter and decision rights.
• Standard definitions for errors, denials, underpayments, and write-offs.
• Dashboards for CDM changes, coding audits, DNFB, denial trends, and A/R aging.
• Policies stating when revenue integrity, compliance, HIM, or finance leads a review.
• Documentation of decisions, education, system changes, and follow-up audits.

For the exam, choose answers that balance revenue and compliance: collect what was legitimately earned, but refund or correct unsupported billing when policy requires.

Chargemaster Governance as a Worked Control

The charge description master (CDM) is the file that maps each billable service to a code, description, revenue code, and price. A single bad CDM line replicates across thousands of claims, so CDM maintenance is a high-leverage revenue integrity control. Example: a hospital adds a new infusion drug but the pharmacy builds the CDM line with the wrong HCPCS J-code and no units. Every claim for that drug now either denies or pays incorrectly — a defect that no individual coder will catch because coding never touched it.

The RHIA control is a structured CDM review with pharmacy, revenue integrity, and IT, plus an annual reconciliation against the latest code updates. The lesson the exam tests: not every revenue defect is a coding defect; many are front-end charge-capture or CDM problems that demand a different owner.

Connecting Revenue Integrity to the RHIA Domains

Revenue integrity is where several RHIA domains converge, and the exam rewards candidates who see those links:

• Information governance supplies the standard definitions (what counts as a denial, a write-off, an underpayment) so dashboards are comparable across departments.
• Data analytics supplies the trend detection — without analytics, a 2% denial creep on one payer hides inside aggregate numbers.
• Compliance supplies the escalation thresholds and the audit-trail requirements.
• Leadership supplies staffing, change management, and accountability so corrective actions actually close.

Two Directions, One Discipline

A recurring exam theme: revenue integrity protects the organization in both directions. Under-billing for legitimately rendered, documented services loses earned revenue and can even raise Stark/AKS concerns if it looks like inducement. Over-billing unsupported services creates False Claims Act and 60-day-rule exposure. The credible RHIA answer never optimizes one direction at the expense of the other. Revenue integrity is the discipline of making the claim match the documented, coded, charged, and payable reality — and proving it with an audit trail.