Guide

Documenting MDM: problems, data, risk — in your own sentences

Summary

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

How Do You Document MDM Without Checkbox Bloat?

Write one or two sentences for each of the three MDM elements — the problems you addressed, the data you reviewed, and the risk involved in managing the patient — instead of relying on a checkbox grid to imply all three at once. A sentence that states what you found, what you reviewed, and what you decided demonstrates actual clinical reasoning; a fully checked template box demonstrates only that something was clicked, which is a much weaker showing under review 1Ref 1American Medical Association (2023).CPT evaluation and management (E/M) revisions.That the AMA publishes and periodically corrects the operative MDM table defining what qualifies at each complexity level..

Checkbox bloat happens when a template's every field gets marked to be safe, regardless of whether it reflects the actual visit — every data source checked as reviewed, every risk factor checked as considered, whether or not any of it was true for this particular patient. The fix isn't abandoning structure; it's using the structure to organize sentences you actually wrote, not to replace writing them.

The Three Elements of MDM, in Plain Terms

Under the current framework, an office visit's level is set by medical decision making or by total time, and MDM itself is scored across three elements: the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications, morbidity, or mortality from the patient's management 2Ref 2Centers for Medicare & Medicaid Services (2023).Evaluation and Management Services Guide.That E/M level is set by MDM or total time, and what the three MDM elements mean and require to be documented.. Two of the three elements have to meet or exceed a given level for the visit to qualify at that level.

The AMA's operative MDM table defines exactly what qualifies at each tier, and it's worth reading directly rather than trusting a paraphrase — vendors and templates sometimes drift from the table's actual language over time as it's periodically refined with technical corrections 1Ref 1American Medical Association (2023).CPT evaluation and management (E/M) revisions.That the AMA publishes and periodically corrects the operative MDM table defining what qualifies at each complexity level.. Your documentation's job is to give a reviewer enough narrative detail to place the visit on that table themselves, without you naming the level explicitly.

Problems Addressed: Name What You're Managing and Why

State each problem you addressed at the visit and its status — new, established, stable, worsening — in a sentence, not a diagnosis code sitting alone in a list. "Depression, established, worsening despite current treatment" tells a reviewer something a bare ICD-10 code never can: that you assessed the trajectory of the condition, not just its presence.

A chronic condition that's stable and requires no changes is genuinely a lower-complexity problem than one that's acutely worsening, and your sentence should reflect that difference honestly rather than defaulting to the same phrasing for every visit regardless of how the patient is actually doing. The alignment check that connects your note to your code starts here — with problems documented specifically enough that the complexity is visible on the page, not just in your head.

Data Reviewed: Show What You Actually Looked At

Name the specific data you reviewed and what you did with it — a lab result you interpreted, a prior note you read before the visit, an outside record you requested, a conversation with a collateral source — rather than checking a generic "records reviewed" box that could mean almost anything. "Reviewed prior psychiatric hospitalization records; findings consistent with current presentation" earns its complexity credit; a checked box next to "external records" with nothing else does not.

This is also where medication reconciliation belongs when it happened at the visit: naming the list you reconciled and what changed is data-review documentation in its own right, not a separate administrative task disconnected from the MDM you're building toward. The same specificity that makes med rec defensible makes the data element of MDM defensible too.

Risk: The Element Checkboxes Handle Worst

Risk is the hardest MDM element to document honestly with checkboxes, because risk lives in your clinical judgment about a specific patient, not in a generic list of risk factors that applies to everyone. A sentence stating what concerned you and why supports the risk element far better than a checked box next to "suicidal ideation assessed" with no elaboration on what you found or how you weighed it.

This is exactly where structure over checkbox matters most — documenting suicide risk, prescribing a medication with known interactions, or managing a patient who's declining recommended treatment are all risk-bearing decisions that deserve a sentence explaining your reasoning, not a symbol implying you thought about it. The busier your day, the more tempting the checkbox becomes, and the more that specific element is what a reviewer will scrutinize first.

Let the Level Follow the Sentences, Not the Reverse

Write the clinical narrative first, then let the coding level fall out of what you actually documented — never start from the level you want and build sentences to justify it after the fact. That sequence matters because coverage review checks whether the documentation supports the code billed, not the other way around, and it checks against the coverage conditions tied to the specific service, not just the E/M table in isolation 3Ref 3Centers for Medicare & Medicaid Services (2026).Medicare Benefit Policy Manual (Pub. 100-02).That coverage review checks documentation against the coverage conditions tied to the specific service, not the E/M table alone..

Some payers publish their own worked examples of what they expect an MDM note to contain — a named payer's provider policies are worth reading as one example of what a reviewer looks for, with the caveat that your own contract, not any single payer's public page, ultimately controls what your specific plan requires 4Ref 4Anthem (2026).Anthem Provider Policies.Named as one payer's published example of MDM documentation expectations, with contract terms controlling over any single payer's public page..

Keeping the Habit Sustainable Across a Full Day

Three sentences per visit — one per MDM element — is a realistic target that doesn't blow up your schedule, especially once it's a habit rather than something you're consciously constructing each time. A short structured template with three open fields, one per element, gives you the organization of a checklist and the substance of a narrative at the same time.

Build in a periodic check on your own notes — reading a handful cold, as if you were the reviewer — as part of your own CDI loop. That's the fastest way to notice if your MDM sentences have quietly drifted back toward boilerplate, before an actual audit notices it for you.

Common questions

The number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications or management decisions involved. Two of the three have to meet or exceed a given level for the visit to qualify at that MDM level under the current framework.

A checked box shows that something was clicked, not that clinical reasoning happened — and templates checked the same way for every patient regardless of what actually occurred are exactly what a coverage reviewer flags. A short sentence per element shows the reasoning a box can't.

Often just one or two sentences per element — what problem you addressed and its status, what data you reviewed and what you concluded, and what risk you weighed in the management decision. Specificity matters more than length; a precise short sentence beats a vague long paragraph.

Write the clinical narrative first, and let the level follow from what you actually documented. Starting from a target level and writing sentences to justify it afterward is exactly the pattern coverage reviewers are trained to notice, even when the underlying care was entirely appropriate.

Every visit's MDM is scored across all three elements, but a genuinely simple visit may have a straightforward answer for each — a stable problem, minimal data, low risk. The goal is an honest sentence for each element, not maximizing complexity where none exists.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.American Medical Association (2023). CPT evaluation and management (E/M) revisions. American Medical Association (AMA). link ✓That the AMA publishes and periodically corrects the operative MDM table defining what qualifies at each complexity level.
2.Centers for Medicare & Medicaid Services (2023). Evaluation and Management Services Guide. CMS Medicare Learning Network (MLN006764). link ✓That E/M level is set by MDM or total time, and what the three MDM elements mean and require to be documented.
3.Centers for Medicare & Medicaid Services (2026). Medicare Benefit Policy Manual (Pub. 100-02). Centers for Medicare & Medicaid Services (CMS). linkThat coverage review checks documentation against the coverage conditions tied to the specific service, not the E/M table alone.
4.Anthem (2026). Anthem Provider Policies. Anthem provider portal. link ✓Named as one payer's published example of MDM documentation expectations, with contract terms controlling over any single payer's public page.

https://www.gale.care/for-providers/cdn-mdm-documentation · 4 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers