Study guide
10.3 Revenue Integrity Program Design
RHIA Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: RHIA Eligibility, Application, Fees, Format, Scoring, and Retakes
1.1 RHIA Purpose and Administrator-Level Scope 1.2 HIM-Only Eligibility Routes 1.3 MyAHIMA Application, Transcripts, and the 120-Day Scheduling Window 1.4 Fees, Format, and Appointment Time 1.5 Passing Score and Score Interpretation 1.6 Retakes, Certification Maintenance, and Current Statistics
2 2023 RHIA Outline, Exam Functionality, Pretest Items, and Study Strategy
2.1 Current 2023 Outline and Why It Controls Study 2.2 Domain Weights and Study-Time Allocation 2.3 Scored Items, Pretest Items, and Answer Discipline 2.4 Navigation, Flagging, Review, and Submit Workflow 2.5 Test Center Day and No-Resource Requirement 2.6 Official Task-Based Study Strategy
3 Data and Information Governance I: Documentation Integrity and Quality Reporting
3.1 Documentation Integrity as Governance 3.2 Complete, Accurate, and Timely Records 3.3 Documentation Standards and Clarification Workflows 3.4 Clinical Data Elements for Quality Reporting 3.5 Data Quality Validation for Reporting 3.6 Governance Committees, Metrics, and Remediation
4 Data and Information Governance II: Data Dictionaries, Retention, MPI, and Policy
4.1 Data Dictionary Standardization 4.2 Documentation and Data Standards 4.3 Data Analysis to Inform Management 4.4 Policies and Procedures for Information Governance 4.5 Retention and Destruction Policies 4.6 Master Patient Index Integrity
5 Compliance I: Access, Use, Disclosure, Patient Rights, ROI, and HIE
5.1 Domain 2 Compliance Decision Frame 5.2 Patient Access and Portal Governance 5.3 Advocacy for Patients and Families 5.4 ROI Intake, Validation, and Scope Control 5.5 Disclosure Documentation and Audit Trails 5.6 HIE and External Access Governance
6 Compliance II: Security, Breach Workflows, Cybersecurity, and Disaster Recovery
6.1 Request Workflow Controls and Escalation 6.2 Breach Protocols from Report to Resolution 6.3 Privacy and Security Initiatives 6.4 Cybersecurity Risks for HIM Leaders 6.5 Disaster Recovery and Downtime Readiness 6.6 Monitoring, Metrics, Tabletops, and Continuous Improvement
7 Data Analytics and Informatics I: EHR Support, Reporting, Databases, and Dashboards
7.1 EHR Support and HIM Administration 7.2 Reporting Lifecycle and Data Requests 7.3 Visualizations, Dashboards, and Executive Views 7.4 Database Management and Data Dictionaries 7.5 Data Mining and Analytics Workflows 7.6 Statistics Validation for Stakeholders
8 Data Analytics and Informatics II: CDI, Workflows, HIE, Integrations, and SDLC
8.1 Focused Documentation Audits for CDI, Quality, and Safety 8.2 CDI Workflows and Query Governance 8.3 Workflow Optimization Through Health Information Technology 8.4 HIE Governance and Exchange Controls 8.5 Software Integrations and Health Information Impact 8.6 Systems Development Life Cycle and HIM Participation
9 Revenue Cycle Management I: Reimbursement, Coding Validation, CDI, and Claims
9.1 Domain 4 Revenue Cycle Management Frame 9.2 Reimbursement Models and Provider Education 9.3 Coding Accuracy Validation Controls 9.4 HHS Documentation Requirements and CDI 9.5 Claims Workflow and Clean-Claim Controls 9.6 CDM, DNFB, and A/R Management
10 Revenue Cycle Management II: Revenue Integrity, Denials, Fraud, and Official Guidelines
10.1 Official Guidelines and Code Assignment 10.2 Groupings and Payment Data Validation 10.3 Revenue Integrity Program Design 10.4 Coding Audits, Monitoring, and Corrective Action 10.5 Denials Management and Appeals 10.6 Fraud Prevention and Compliance Escalation
11 Management and Leadership: Strategy, HR, Work Design, Training, Budgeting, and Projects
Strategy, Goals, and Change Management Contracting and Outsourcing Governance Human Resources, Staffing, and Performance Work Design and Process Improvement Training and Development Budgets, Accreditation, Compliance, and Projects
12 Final RHIA Review: Domain Integration, Exam Week, and Career Next Steps
Integrated Scenario Patterns Across Domains Final Week Domain-Weighted Review Test-Center Day, Functionality, and Pacing Results, Retakes, and RHIA Maintenance RHIA, RHIT, CHDA, CHPS, and CCS Career Map Readiness Checklist and Next-Step Plan
10.3 Revenue Integrity Program Design
Key Takeaways Explain This Topic AI
Domain 4 names revenue integrity through coding audits, denials management, and fraud prevention; it aligns documentation, coding, charge capture, claims, payment, and audit response.
Revenue integrity protects in two directions: it prevents lost legitimate revenue AND prevents unsupported billing that creates compliance exposure.
A program needs defined ownership, a cross-functional committee, risk-based monitoring, and traceable corrective action with reaudit.
Key metrics include DNFB (discharged-not-final-billed), discharged-not-submitted, A/R days, denial rate, and clean-claim rate.
Last updated: June 2026
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.
Component Main question Example control
Documentation integrity Does the record support coded and billed services? Compliant query policy, provider education, record-completion monitoring
Coding integrity Are codes assigned under official guidelines? Coding audits, accuracy metrics, second-level review
Charge integrity Are services, supplies, units, revenue codes captured? Chargemaster (CDM) review, department charge audits, reconciliation
Claim integrity Are edits resolved with evidence and ownership? NCCI edits, scrubber workqueues, root-cause categories
- Payment integrity Did the payer process correctly? Underpayment review, denial analysis, appeal tracking
- Compliance integrity Are risk patterns escalated? Referral thresholds, audit-trail requirements
- 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.