Orthopaedic Charge Lag: Why Days-to-Bill Is the Revenue Cycle Metric You're Not Tracking

Charge lag, also called days to bill, is the number of days between the date of service and the date a clean claim is submitted to the payer. In orthopaedic practices, charge lag is usually driven by surgical cases waiting on signed operative notes and coding review, and it matters because every day of lag delays cash, inflates true AR, and pushes claims closer to timely filing limits. Most orthopaedic groups track AR days closely but do not measure charge lag at all, which means a significant share of their revenue cycle delay is invisible on the dashboard.

Why Charge Lag Hides Inside Your AR Days

Most practice management systems start the AR clock when the claim is created or submitted, not when the service was performed. That means if a total knee is performed on the 1st, the operative note is signed on the 4th, the case sits in the coding queue until the 11th, and the claim drops on the 12th, your AR report shows zero days of age on the 12th. The first 11 days are not counted anywhere.

This is why two orthopaedic groups with identical AR days can have very different cash positions. The group with a 3-day charge lag and 35 AR days is collecting faster than the group with a 12-day charge lag and 32 AR days. If you want the complete picture, add average charge lag to your AR days to get total days from service to cash.

MGMA and HFMA both emphasize measuring the full revenue cycle, not just post-submission AR. For physician groups, charge lag is the most practical way to measure the front half.

How to Measure Orthopaedic Charge Lag

Charge lag is simple to calculate and most practice management systems can produce it with a standard report or a basic export.

• Formula: For each claim, subtract the date of service from the claim submission date. Average the result across all claims for the period.
• Segment it by encounter type. E&M visits, office procedures and injections, surgical cases, and ancillaries (imaging, DME, therapy) behave very differently. A single blended number will hide your surgical backlog behind fast-moving clinic visits.
• Segment it by surgeon and location. Charge lag often concentrates in a few surgeons who sign notes late or in one ASC or hospital where documentation flows through a separate system.
• Break it into stages. Separate the time from service to note signature (documentation lag) from the time from note signature to claim submission (coding and billing lag). They have different owners and different fixes.
• Weight it by dollars. A 20-day lag on a $9,000 spine case matters more than a 20-day lag on a $120 follow-up visit. Dollar-weighted charge lag tells you where the cash actually is.

What Drives Charge Lag in Orthopaedics

1. Unsigned operative notes

Coders cannot code a surgical case without a signed operative note. Surgeons who dictate or sign in batches at the end of the week create a lag that no billing team can fix downstream. This is the single most common driver we see in orthopaedic groups.

2. Surgical coding backlogs

Orthopaedic surgical coding is complex. Arthroscopy bundling rules, spine add-on codes, fracture care global packages, laterality, and modifiers 51, 59, 58, 78, and 79 all require careful review. When coders are short-staffed, surgical cases pile up in the queue because they take the longest per chart.

3. Coder turnover and vacancies

Experienced orthopaedic coders are hard to recruit and slow to replace. A single open coding position can add days of lag across an entire service line until it is filled and the new hire is up to speed.

4. Missing information and front-end holds

Claims held for missing authorization numbers, incorrect insurance, missing referring provider information, or implant invoices (for some payer contracts) all add lag. Many of these originate at scheduling or check-in.

5. Multi-system documentation

Surgeons operating at hospitals or ASCs often document in a different system than the practice EHR. Getting that documentation into the coding workflow adds manual steps and delay.

6. Pre-bill edits and scrubber rejections

Claims that fail internal scrubber edits sit in a work queue until someone corrects them. High scrubber rejection rates usually point back to upstream coding or registration errors.

What Charge Lag Actually Costs

Charge lag costs an orthopaedic practice in four ways.

• Working capital. Every day of lag is roughly one day of net collections sitting uncollected. For a group collecting $50 million a year across about 250 business days, one day of charge lag represents roughly $200,000 in delayed cash. Cutting surgical lag by five days is a one-time release of close to $1 million.
• Timely filing write-offs. Medicare allows 12 months from the date of service to file, but many commercial and Medicare Advantage contracts allow 90 to 180 days, and some are shorter. Long-lag claims that then get rejected and need correction can miss those windows entirely.
• Authorization and eligibility risk. The longer a claim waits, the more likely a patient's coverage has changed or an authorization window has closed, which makes the claim harder to get paid.
• Reduced appeal runway. Payer appeal windows run from the denial date, but a late first submission compresses the overall timeline for correcting and resubmitting problem claims before year-end.

What Good Looks Like: Practical Charge Lag Targets

There is no single published standard for orthopaedic charge lag, and benchmarks vary by practice model. These are practical targets we see high-performing orthopaedic groups use internally:

• E&M visits: 1 to 2 days from service to claim submission.
• Office procedures and injections: 1 to 3 days.
• Surgical cases: 3 to 5 days, measured from date of surgery, with most of that time attributable to note signature rather than coding.
• Operative note signature: within 24 to 48 hours of surgery.

If your surgical charge lag is running above 10 days, it is almost certainly one of your largest recoverable sources of cash.

How to Reduce Charge Lag in Your Orthopaedic Practice

Set and publish a note signature standard

Adopt a clear policy for signing operative notes and clinic notes, such as within 48 hours, and report compliance by surgeon every week. Peer visibility changes behavior faster than reminders from the billing office.

Report charge lag by stage and by surgeon

Add documentation lag and coding lag to your monthly revenue cycle dashboard alongside AR days, denial rate, and clean claim rate. What gets measured gets managed.

Clear the front-end holds before the date of service

Verify eligibility, confirm prior authorization, and capture referring provider details at scheduling. Every hold you prevent upstream is a day of lag you do not have to chase later.

Code surgical cases the day the note is signed

This is where AI coding changes the math. When an autonomous coding agent inside the EHR reads the signed operative note and populates CPT, ICD-10, modifiers, and clinical justification immediately, the coding queue stops being a queue. The coder reviews and approves rather than building the claim from scratch. Maia reports roughly a 50% efficiency gain on surgical coding with this approach, which directly compresses the coding stage of charge lag.

Tighten your scrubber feedback loop

Track the top scrubber rejection reasons each month and fix them at the source. If the same modifier or diagnosis pointer error appears repeatedly, it is a training or workflow problem, not a billing problem.

Build a process for facility documentation

For surgeons operating at outside hospitals and ASCs, set up a reliable feed or retrieval process for operative notes so that documentation arrives in the coding workflow automatically rather than by request.

Charge Lag and AI Coding: What Changes

AI coding does not fix late note signature. That remains a physician behavior and policy issue. What it does fix is everything after the signature: the queue time, the chart-by-chart build of each surgical claim, and the variability that comes from coder availability. Practices using autonomous coding typically see the coding stage of charge lag shrink to same day or next day, and the remaining lag becomes almost entirely a documentation metric that leadership can manage directly.

Orthopaedic groups use Maia inside their existing EHR workflows, including Athena, and coming soon, Epic, ModMed, eClinicalWorks, NextGen, and Tebra, so the change happens without a separate coding platform or a second login for coders.

Frequently Asked Questions

What is charge lag in medical billing?

Charge lag is the number of days between the date a service is performed and the date the claim is submitted to the payer. It measures how quickly a practice turns clinical work into a billable claim, and it is a leading indicator of cash flow problems.

What is a good charge lag for an orthopaedic practice?

High-performing orthopaedic groups generally target 1 to 2 days for E&M visits and 3 to 5 days for surgical cases, with operative notes signed within 24 to 48 hours. Surgical charge lag above 10 days usually signals a documentation or coding backlog worth addressing.

Is charge lag included in AR days?

Usually not. Most practice management systems start counting AR days when the claim is created or submitted, so the time before submission is invisible in AR reports. Add average charge lag to AR days to see the full time from service to payment.

How does charge lag affect timely filing?

Every day of charge lag uses up part of the payer's timely filing window. Medicare allows 12 months from the date of service, but many commercial and Medicare Advantage contracts allow 90 to 180 days, so long-lag claims that also need correction are at real risk of being written off.

Can AI coding reduce charge lag?

Yes, for the coding portion. AI coding inside the EHR can code a surgical case as soon as the operative note is signed, which removes queue time. It does not solve late note signature, which needs a physician documentation policy.

Who should own charge lag in an orthopaedic practice?

Ownership should be split by stage. Physician leadership owns documentation lag (time to note signature), and the revenue cycle leader owns coding and billing lag (time from signature to claim submission). Both should appear on the same monthly dashboard.

The Bottom Line

If you only track AR days, you are missing the front half of your revenue cycle. Measure charge lag by encounter type, by stage, and by surgeon. Set a note signature standard. Then remove the coding queue so that surgical claims go out the day documentation is ready.

See how Maia's AutoCoder handles this automatically for orthopaedic practices. Book a demo at usemaia.com.