Year-End Medical Coding: What Leaders Should Address Before the Books Close

Whether a hospital’s year-end falls in September, December or another month, an existing coding backlog can make the close more difficult. This article outlines when PRN coding support or a focused coding review may help organizations address aging accounts, staffing gaps and unresolved risk before entering a new fiscal or calendar year.

Year-end does not occur at the same time for every healthcare organization. Some facilities follow the calendar year, while others close their fiscal year in September or another month. Regardless of when it falls, year-end provides a natural point to evaluate coding operations, outstanding accounts and unresolved risk.

If volumes are under control, staffing is stable and quality indicators are where they should be, adding resources simply because the year is ending may not make sense.

But when a coding backlog already exists, the approaching fiscal or calendar year-end can make an unresolved problem harder to carry forward.

Staffing gaps, scheduled time off, competing projects and aging accounts can all place additional pressure on the coding team. Meanwhile, uncoded or delayed accounts remain outside the billing cycle, leaving organizations to begin a new reporting period while still working through unfinished business from the prior one.

For hospital and health system leaders, the better year-end question is not, “Do we need more coders?” It is:

Why an Existing Coding Backlog Matters More at Year-End

A coding backlog is not merely a productivity issue. Coding sits between the clinical record and the claim. When charts are waiting to be coded, billing may also be waiting.

That can contribute to higher discharged not final billed (DNFB) levels, slower claim submission and delayed cash flow. It may also place more pressure on internal coders, who are expected to manage aging accounts while keeping pace with current discharges and encounters.

The year-end date itself is not the problem. The concern is the compounding effect of closing one reporting period—and beginning another—with unfinished work already in the queue.

Leaders should look beyond the total number of charts and ask:

• How old are the accounts in the backlog?
• Which patient types, facilities or specialties are driving it?
• Is the backlog growing, stable or shrinking?
• Are documentation gaps or unresolved queries slowing completion?
• Are high-dollar or complex cases aging alongside routine accounts?
• Is the team maintaining coding quality while working through the volume?

A queue can appear manageable until its age, complexity and financial value are considered together.

When Temporary Coding Support May Be Appropriate

Not every staffing challenge requires a long-term outsourcing arrangement. Temporary or PRN coding support may be more appropriate when an organization needs to address a defined gap without changing its permanent operating model.

Common year-end situations include:

A Backlog Is Not Declining Fast Enough

If current staff can keep up with daily volume but cannot meaningfully reduce older accounts, additional capacity may help separate backlog work from ongoing production.

Scheduled Time Off Will Reduce Capacity

Planned time off is predictable, but its effect can be significant when the team is already operating close to its limit. Short-term coverage can help prevent a manageable queue from becoming a larger problem in the next reporting year.

Vacancies or Leave Have Created a Temporary Gap

Recruiting experienced coders takes time. PRN support can provide coverage while a position remains open or a team member is away, without forcing a permanent staffing decision.

A Conversion, Upgrade or Special Project Is Competing With Production

System work often draws experienced staff away from routine coding. Bringing in targeted support can protect daily operations while internal subject-matter experts focus on the project.

Certain Account Types Require Specialized Expertise

A backlog concentrated in complex inpatient, outpatient, interventional radiology, facility or professional-fee work may require a more specific skill set than general overflow coverage.

The goal should be clearly defined. “More help” is difficult to measure. A better engagement has a target: reduce accounts older than a certain age, stabilize turnaround time, provide coverage through a known period or clear a specific service-line queue.

Year-End Review: A Different Kind of Opportunity

Some organizations approach year-end with remaining funds allocated to compliance, education, revenue integrity or operational improvement. Whether those funds carry forward depends on the organization, but allowing them to lapse by default is not necessarily the most thoughtful choice.

This does not mean ordering a broad audit simply to spend what remains. It means asking whether there is a focused question leadership has not had the time or data to answer.

For example:

• Did a denial trend point to a possible coding or documentation issue?
• Has a new coder, team or service line received an independent quality review?
• Are high-risk diagnoses, procedures or quality indicators being reported accurately?
• Did a change in case mix index, severity, CC/MCC capture or procedure volume go unexplained?
• Is leadership relying on internal accuracy data that has not been independently validated?
• Were this year’s code changes translated into consistent coding practice?

A focused review can be scoped around a specific risk, specialty, diagnosis, procedure, payer trend or group of accounts. That makes the work more useful than a generalized exercise and gives leaders findings they can act on in the next fiscal or calendar year.

Coding Support and Coding Review Solve Different Problems

Although they can complement each other, coding support and coding review should not be treated as interchangeable.

Coding support addresses capacity. It helps move accounts through the coding workflow when volume exceeds available internal resources.

Coding review addresses confidence. It evaluates whether coding and documentation accurately support the claim, reported quality data and reimbursement.

If the problem is a growing queue, an audit alone will not clear it. If production is current but leaders are uncertain about accuracy or risk, adding coders may not answer the underlying question.

In some cases, both are appropriate—but the objectives, teams and measures of success should remain distinct.

Five Questions Leaders Should Ask Before the Year Closes

1. What Would Happen if We Made No Change?

Project the backlog, staffing capacity and account aging into the next fiscal or calendar year. Doing nothing may be reasonable, but it should be a decision rather than a default.

2. Where Is the Actual Constraint?

Determine whether accounts are delayed by coding capacity, missing documentation, unresolved queries, charge issues, system edits or another workflow dependency. Additional coders will not solve a bottleneck that sits elsewhere.

3. Which Work Should Internal Staff Retain?

Organizations often obtain better results by keeping specialized institutional knowledge in-house while assigning well-defined overflow or backlog work to external coders.

4. What Outcome Would Justify the Investment?

Set a measurable objective, such as reducing aging accounts, restoring a target turnaround time, reviewing a defined risk area or delivering actionable education based on findings.

5. How Quickly Can Support Begin?

Contracting, access, security, system orientation and account assignment all take time. Waiting until the backlog becomes urgent can narrow the available options.

The Goal Is a Cleaner Start to the Next Reporting Year

Year-end planning should not create artificial urgency. It should create visibility.

An organization that is current, adequately staffed and confident in its coding quality may need no additional intervention. But when a backlog is already aging, available coverage is tightening or leadership has unresolved coding concerns, carrying those issues into the next fiscal or calendar year may make them more difficult to address.

A practical year-end assessment can help determine whether the right next step is temporary coding support, a focused coding review, both or neither.

HIA provides PRN contract coding support for backlogs, overflow, vacancies, leave coverage, conversions and special projects. HIA also performs inpatient and outpatient coding reviews designed around compliance, revenue and education objectives. The scope can be tailored to the operational question an organization needs to answer—without forcing a larger engagement than the situation requires.

What Will Your Facility Carry Into the Next Year?

If a coding backlog, staffing gap or unanswered risk area is likely to cross into your organization’s next fiscal or calendar year, now is the time to define the problem. HIA can help determine whether targeted coding support, a focused review or no outside intervention is the right next step.

FAQ

For more than 30 years, HIA has been the leading provider of compliance audits, coding support services and clinical documentation audit services for hospitals, ambulatory surgery centers, physician groups and other healthcare entities. HIA offers PRN support as well as total outsource support.

The information contained in this coding advice is valid at the time of posting. Viewers are encouraged to research subsequent official guidance in the areas associated with the topic as they can change rapidly.