In briefA compliant note states what you considered, what you decided, and why, and it names every condition you actually managed. That is what an auditor reads for, and it is also what the hospital's coder needs.

A note that protects the claim and the care

Whoever audits a claim, a commercial payer, a CMS Recovery Audit Contractor, or your own compliance team, asks one question: does this note support the code that was submitted? The same note carries the diagnoses that set the patient's complexity and, in the hospital, what the admission pays.

A cautionary habit
I have older colleagues who still write "PERRLA" and a full cranial-nerve examination on a patient who came in for knee pain. I am not convinced those elements were always checked. They add nothing to the level under current rules, and if an auditor asks whether you truly examined the cranial nerves of a patient with isolated knee pain, "it is in my template" is not a comfortable answer. Document what you did, not what the template defaults to.

A compliant note is not a longer note. It says what you did and why.

What a Compliant Note Looks Like Under Audit

What Auditors Actually Look For

An auditor looks for two of three MDM elements (problems, data, risk, scored as in the MDM guide) or documented time, and asks whether the note shows the work.

Problems addressed: "Patient has hypertension" says the condition exists. "Reviewed blood pressure control; hypertension remains well-managed on current regimen; no medication changes at this time" says you managed it.

Data reviewed: "Reviewed labs" is weaker than "Reviewed today's CMP and CBC, no significant changes; potassium remains stable on current diuretic dose," which names the data and your interpretation.

Risk: "Continue current medications" is weaker than "Continuing metformin at current dose; will recheck renal function in 3 months given mild CKD," which shows monitoring for drug toxicity, a moderate-risk element.

The Specificity Principle

Audits are lost on vagueness. "Discussed at length," "reviewed records," and "ongoing management" give an auditor nothing to credit. "Reviewed outside rheumatology note from ***, consistent with our current management plan" is creditable.

The copy-paste problem
Pulling forward a prior visit's note text is one of the highest-risk documentation practices. Identical notes across visits raise the question of whether the care occurred and whether the code reflects this encounter. Use templates to prompt documentation, not to generate it.

The Medical Necessity Foundation

Every service coded must be medically necessary: clinically appropriate for the condition and consistent with standards of care. It is not a separate documentation requirement; a note that accurately describes a complex patient with several actively managed conditions establishes it. A thin note under a high code, or a pattern of high-complexity visits for minor complaints, is where audits find problems.

Time-Based Documentation: The Non-Negotiable

If you code on time, the note must state total time; without that sentence an auditor treats the level as unsupported and the claim cannot be defended. The attestation sentence and what counts toward total time are in the time-based billing guide.

A note about your story in the note
A note communicates your thinking to other providers, documents the care for medico-legal purposes, and supports the code. One habit serves all three: write the honest, specific story of what you did and why.

Part of that story is the list of conditions the patient brought into the room, and the diagnosis codes physicians forget to document are the ones that quietly cost the most.

Diagnoses, Comorbidities, and the Codes Physicians Forget to Document

Diagnosis codes feed the MDM level, stratify risk, and in the hospital help determine what the admission pays. The next physician also inherits a more honest chart.

Diagnosis Codes and MDM: The Outpatient Connection

Outpatient MDM is set by the problems you evaluate or manage, not by the number of ICD-10 codes on the claim. Ten listed diagnoses with one addressed is one problem; a single diagnosis can be a severe, high-complexity problem. If you manage hypertension, type 2 diabetes, and hypothyroidism at one visit, document and list all three. Listing without addressing adds nothing to MDM; addressing without listing undersells the visit.

Specificity matters as well. "Type 2 diabetes mellitus without complications" (E11.9) and "type 2 diabetes mellitus with chronic kidney disease stage 3" (E11.22) describe different patients. The specific code is accuracy, not upcoding.

Present on Admission: The Inpatient Revenue Dimension

Medicare groups hospitalizations into Diagnosis Related Groups (DRGs), and the DRG sets payment for the entire admission. Major comorbid conditions move the admission into a higher-paying DRG, but only if they are documented and coded, and for certain conditions only if they were Present on Admission (POA) rather than acquired during the stay. Leave a known comorbidity out of the note and the hospital collects less than the patient's condition justifies.

POA documentation: the provider's role
Your H&P, operative note, and progress notes drive the codes the coder can assign. If you do not document a comorbidity, the coder cannot code it, and the DRG does not reflect it. At admission, list every relevant comorbidity the patient brought with them, not just the diagnosis you are treating.

The Most Commonly Under-Documented Comorbidities

In clinical documentation improvement work across surgical practice, the most frequently missed are:

None of these are fabricated; they are conditions your patient has that affect care. Leaving them out is an incomplete record and lost institutional revenue.

All of this has to be remembered on every patient by a physician already at capacity, and new cognitive steps create friction that leads to abandonment. Durable improvements are built into the workflow so the right prompt appears at the right moment.

AI and Documentation Templates: Making Better Coding Automatic

What a Documentation Template Can Do

A documentation template is a shortcut that expands into a block of text when you type its trigger (".MYVISIT" in a note field). The useful kind is built from structured pick-lists: dropdowns within the note that prompt you to choose, for each MDM element, from clinically accurate options for your practice type. Used consistently, it produces complete MDM documentation on every visit, and coding accuracy follows. It should prompt you to choose the true option for today's encounter, not pre-fill last visit's answer.

Building Your Own Documentation Template

Build it around the MDM table. Start with your most common visit types (the chronic disease visit, the post-injury evaluation, the post-op complication visit), identify the MDM elements most often present and most often omitted, build pick-lists that prompt for them, and give the time-based visit its own line so the total-time sentence is never left out.

Rules to embed for orthopaedic and sports medicine practice:

AI-Assisted Coding Tools

A growing category of tools, from EHR-embedded modules to standalone applications, reads a completed note and suggests the E/M code it supports. The Note Coding Assistant at PhysicianCodingGuide.com/chartcode returns an MDM-scored level with reasoning and APSO structure feedback. It is not a substitute for a qualified coder, but run a few recent notes through it and you will see in minutes which habits in this guide your template should be prompting for.

Sources and Further Reading for This Chapter

Put it to workGrab the documentation templates
Previous