9.6 CDM, DNFB, and A/R Management

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.

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:

1. Incomplete coding / coder backlog — HIM coding.
2. Open queries awaiting provider response — CDI / medical staff.
3. Missing documentation or unsigned reports — clinical departments.
4. Charge-capture lag — ancillary/clinical departments.
5. 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.