Study guide
9.6 CDM, DNFB, and A/R Management
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
9.6 CDM, DNFB, and A/R Management
Key Takeaways Explain This Topic AI
Task 5 explicitly names CDM maintenance, DNFB analysis, and A/R management as claims-management activities.
The charge description master (CDM) links each service to its CPT/HCPCS code, charge, revenue code, units, and department; errors replicate across every claim until fixed.
DNFB (discharged not final billed) measures accounts past discharge that have not reached a final bill; sort it by root cause and owner, not just total dollars.
A/R management uses aging buckets, days in A/R, and denial data to reveal follow-up priorities, underpayment risk, and process failures.
Last updated: June 2026
The Charge Description Master (CDM)
The charge description master (CDM) , or chargemaster, is the master file listing every billable item a facility provides. Each line ties a service or supply to its CPT/HCPCS code, charge amount, revenue code, units, modifier defaults, and owning department . Because the CDM feeds every claim automatically, a single wrong line is a systemic error: an outdated CPT code or a missing revenue code on one chargemaster row generates the same edit or denial on thousands of claims until someone fixes the master, not the individual claims.
CDM maintenance is a revenue integrity control with a coordinated owner group — HIM, clinical departments, finance, and compliance. Maintain it on a schedule and at code-update boundaries.
- CDM element Why it matters Failure mode
- CPT/HCPCS code Must be current each year Deleted/invalid code rejects claims
- Revenue code Required field for institutional claims Missing/incorrect revenue code denials
- Charge amount Consistency and defensibility Pricing transparency and audit exposure
- Units / multiplier Drives MUE compliance Unit overcharges, MUE rejections
- Department Accountability and analytics Misrouted charges, lost charges
Update the CDM at least annually with the new CPT (January) and ICD-10 (October) code sets, and any time a payer or CMS rule changes. Never let clinical departments add or edit chargemaster lines without revenue-integrity review.
DNFB: Discharged Not Final Billed
DNFB (discharged not final billed) counts accounts that have been discharged but have not produced a final bill. The related metric is days not final billed — the average age of those accounts. A rising DNFB ties up cash and signals an upstream bottleneck. The RHIA does not just watch the dollar total; the administrator sorts DNFB by root cause and owner so the right team fixes the right delay.
Typical DNFB root causes and owners:
Incomplete coding / coder backlog — HIM coding.
Open queries awaiting provider response — CDI / medical staff.
Missing documentation or unsigned reports — clinical departments.
Charge-capture lag — ancillary/clinical departments.
Claim edits not yet resolved — billing / revenue integrity.
A Worked Example
A hospital's DNFB jumps from $4M to $9M in two weeks. The wrong response is to push coders to bill faster. The RHIA stratifies the DNFB: 70% of the increase is accounts held for unanswered provider queries. The true bottleneck is provider query turnaround, so the fix is escalating query response time with the medical staff — not coding speed. Stratifying DNFB by cause turned a vague "cash problem" into a specific, owned action.
Accounts Receivable (A/R) Management
Accounts receivable (A/R) is money owed for billed services not yet collected. The headline metric is days in A/R (also called days sales outstanding), and accounts are grouped in aging buckets — commonly 0-30, 31-60, 61-90, 91-120, and over 120 days. Older buckets are harder to collect and signal process failure; payers also impose timely-filing and appeal windows that make aged A/R a loss risk.
Use A/R and denial data to drive follow-up:
Aging buckets prioritize which accounts to work first (oldest at-risk, highest-dollar).
Days in A/R trended over time reveals whether the cycle is speeding up or slowing.
Denial rate and denial reason codes point to the upstream defect — eligibility, authorization, coding, or medical necessity.
Underpayment review compares paid amounts to the expected contractual rate to catch payer underpayments.
Common Exam Traps
Wrong answers fix a chargemaster problem on individual claims instead of the master file, respond to rising DNFB by pressuring coders regardless of the real cause, write off aged A/R to clean the report, or read A/R as a single total instead of stratified buckets and denial reasons. The defensible answer maintains the CDM at the source with revenue-integrity oversight, stratifies DNFB by root cause and owner, and works A/R by aging bucket and denial reason while reviewing for underpayment and timely-filing risk.
How the Three Metrics Connect
CDM, DNFB, and A/R are not separate worlds; they are three checkpoints on one cash timeline, and the exam expects you to trace a problem from one to the next. A defective chargemaster line creates claim edits, which hold accounts in DNFB, which eventually age into A/R if forced through unresolved, which then generate denials and underpayments. Fixing the symptom at the wrong checkpoint never works: appealing the denial does not repair the CDM line that caused it.
The administrator reads a denial reason code backward to its source — a missing revenue code denial traces to a CDM field, an authorization denial traces to patient access, an unbundling denial traces to coding logic — and assigns the correction to the checkpoint where the defect originates.
A simple way to remember the sequence: the CDM determines whether the charge is captured correctly, DNFB measures whether the account can reach a bill, and A/R measures whether the bill gets paid. Each metric answers a different question, so reporting only one hides the others.
Governance, Cadence, and Worked Targets
These controls run on a governed cadence. Maintain the CDM at every annual code update and at any payer rule change, with revenue integrity as gatekeeper so no clinical department edits a line unreviewed. Review DNFB at least weekly, stratified by cause and owner, with a target days-not-final-billed figure the revenue cycle committee tracks over time. Work A/R continuously by aging bucket, prioritizing the highest-dollar accounts closest to a timely-filing or appeal deadline, and trend days in A/R monthly.
Consider a worked target: if a facility bills $3 million per day and carries $135 million in net A/R, days in A/R is roughly 45. If a peer benchmark is 40 days, the five-day gap represents about $15 million of cash tied up longer than necessary, and the administrator drills into aging buckets and denial reasons to find where it is stuck.
That is the analytic move Domain 4 rewards — turning a single number into a stratified, owned action plan rather than pressuring staff to "collect faster." The recurring exam lesson across CDM, DNFB, and A/R is identical: fix the source, stratify the data, assign the owner, and never clear a metric by writing the problem off.