#1 in AI Orthopaedic Coding
The single biggest source of lost orthopaedic reimbursement is not aggressive payer behavior or coder error; it is documentation that fails to support the level of service actually provided. When an operative note omits the specific findings that justify a higher-complexity code, or an office note lacks the elements needed to support a level-4 visit, the practice gets paid for less than it delivered, and the loss is invisible because the claim still gets paid. Closing these gaps is the fastest, lowest-risk way to raise revenue per surgeon without seeing a single additional patient.
This article walks through the documentation gaps we see most often in orthopaedic practices, quantifies what they cost, and gives you concrete language and workflow changes to close them.
Why Documentation Gaps Are So Expensive in Orthopaedics
Orthopaedics is uniquely exposed to documentation-driven revenue loss because of the density of its coding rules. A single knee case can hinge on whether the note specifies compartment, laterality, the exact procedure performed, and whether a second procedure was separately identifiable.
The AMA's E&M framework rewards documented medical decision-making, not the volume of text, which means a surgeon can do complex work and still bill low if the decision-making is not captured. Every unsupported element is money the practice earned but cannot defend.
Gap 1: Insufficient Medical Decision-Making Detail
Since the E&M guideline overhaul, the level of an office visit is driven largely by medical decision-making (MDM) or total time. The most common gap is a note that describes the exam thoroughly but barely documents the complexity of the problems addressed, the data reviewed, and the risk of the management options.
A surgeon evaluating a patient for possible surgery, reviewing imaging, and weighing operative versus conservative management is performing high-complexity MDM, but if the note does not say so, it codes as a level 3. Closing this gap means explicitly documenting the problems addressed, the data reviewed, and the risk considered.
Gap 2: Missing Elements in the Operative Report
Operative reports frequently omit details that determine whether a procedure can be coded at full value or whether a second procedure is separately billable. Common omissions include failing to state laterality, not describing a distinct additional procedure performed through a separate incision, or omitting the indication that supports a modifier. When these details are missing, coders must either query the surgeon, which delays the claim, or code conservatively, which loses revenue.
Gap 3: Documentation That Doesn't Support Modifiers
Modifiers such as 25, 58, 78, and 79 can significantly affect reimbursement, but each requires specific documentation to survive an audit. A modifier 25, for example, requires documentation of a significant, separately identifiable E&M service on the same day as a procedure. If the note does not make that separateness clear, the modifier is indefensible and the E&M portion is at risk. Closing this gap means training surgeons on the handful of phrases that establish medical necessity and separateness.
Gap 4: Time and Global Period Ambiguity
When billing by time, the note must state total time and confirm it reflects qualifying activities on the date of service. Vague references to a lengthy visit do not qualify. Similarly, care delivered during a global period must be documented as related or unrelated to the original procedure, because that distinction determines whether it is separately billable. Ambiguity here defaults to non-payment.
How to Close Documentation Gaps at Scale
Point-of-care education helps, but it does not scale across a busy group and it fades between audits. The durable fix is to surface documentation gaps in real time, while the surgeon is still in the note, and to prompt for the specific missing element rather than sending a query days later. This is precisely where AI documentation support changes the equation: instead of a retrospective audit that finds losses after claims are submitted, the gap is flagged and closed before the note is finalized.
Maia's documentation and coding tools work together to identify the elements a note needs to support the level of service delivered and prompt for them at the point of documentation, so the justification is captured while it is fresh and accurate.
Frequently Asked Questions
What is the most common orthopaedic documentation gap?
Insufficient medical decision-making detail in office notes. Surgeons routinely perform high-complexity decision-making but document it as if it were routine, causing systematic downcoding of level-4 visits to level 3.
How much do documentation gaps actually cost a practice?
It varies by volume, but even a small average downcode across thousands of annual encounters commonly adds up to six figures of unrecovered, legitimately earned revenue per year.
Do I need to document total time or medical decision-making?
Either can support the E&M level; you choose whichever reflects the visit better. If you bill by time, the note must state total time and confirm it covers qualifying same-day activities. If you bill by MDM, document the problems, data, and risk.
What documentation supports a modifier 25?
A significant, separately identifiable E&M service performed on the same day as a procedure. The note must make clear the E&M work was distinct from the procedure, not just the routine pre-procedure evaluation.
Can AI help close documentation gaps?
Yes. AI can flag missing documentation elements in real time as the note is written and prompt for the specific language needed, closing gaps before submission rather than discovering them in a retrospective audit.
The Bottom Line
Documentation gaps are the quietest and most recoverable form of orthopaedic revenue leakage. The practices that fix them do not work harder; they capture what they already earned by making sure every note supports the service delivered.
See how Maia's AutoCoder handles this automatically for orthopaedic practices. Book a demo at usemaia.com.




