Back to writing
§clinical documentationJune 5, 2026

The chart review that should happen before sign-off

Retrospective coding review helps, but the highest-leverage documentation check happens while the physician can still fix the note.


Most practices review charts after the visit. A coder finds missing specificity, sends a query, and the physician revisits the note days or weeks later.

That workflow is normal. It is also too late.

Retrospective review creates rework

When a query comes back after sign-off, the physician has to reload the encounter from memory. What did the patient say? What changed in the plan? Why was the condition relevant that day?

The note may technically be editable, but the clinical context is already gone.

The best review happens in the note

The more useful check happens before sign-off, while the physician is still documenting and still has the encounter in working memory.

That is when missing MEAT language, unsupported diagnosis specificity, HCC capture gaps, and quality-measure prompts are easiest to fix.

What the check should catch

A pre-signoff review should flag a small number of high-value issues:

  • chronic conditions mentioned but not assessed
  • diagnoses that need more specificity
  • risk-adjustment opportunities that are clinically supported but undocumented
  • quality gaps tied to the visit
  • prior-auth or referral language that is likely to matter later

It should not become another inbox.

Why Cortex Lens is built this way

Cortex Lens is designed as an overlay on the physician's existing workflow. It reads the chart while the note is being written and points out documentation issues before the note leaves the physician's hands.

The goal is not to replace coders. It is to reduce avoidable rework and make the signed chart cleaner the first time.

The bottom line

After-the-fact review will always have a place. But if the practice wants fewer queries, cleaner claims, and less after-hours charting, the documentation check needs to move upstream.