The chart QA layer for independent practices.
Cortex Lens reads the chart while you write it. It catches HCC gaps, MEAT-criteria misses, claim-killing code conflicts, prior-auth risk, and E/M leveling issues — and gives you the exact fix — before sign-off. No new EMR, no migration, no after-hours pajama time.
01 · First flag
CKD code that's drifted.
Maria's eGFR is 38 — stage 3b territory — but her problem list still says stage 3a. Cortex flags the source line and proposes the precise replacement code.
02 · HCC capture
Diagnosis mentioned, never coded.
"Reports occasional foot tingling at night" — neuropathy, narrative-only. Cortex pulls G63.2 with the source phrase highlighted, ready to add to the problem list.
03 · E/M leveling
Documented work supports a 99214.
MDM elements already in the chart support level 4. Cortex shows the one missing data review that closes the gap, and ticks the chip when you accept.
Dose review needed at eGFR 38.
Stage too vague — labs support 3b.
Neuropathy mentioned, code absent.
DM2 not addressed this visit.
Needs one more data review for L4.
The EMR is not going away. The waste around it can.
Lens is a thin overlay on top of the chart-entry screens clinicians already use. It does three things, and only three things.
- 01
Reads the chart in context.
Watches the same chart-entry workflow clinicians already use, in PracticeFusion, Athena, eClinicalWorks, or any FHIR-connected EMR. Sees what was documented, what's on the problem list, and what's missing.
- 02
Recommends concrete fixes.
Not vague "documentation gaps." Specific suggestions: "N18.31 needs to be N18.32 — labs show eGFR 38." "I12.9 and I15.0 are mutually exclusive — payers deny this pair." Each fix tied to the source data.
- 03
Stays inside the practice.
A read-only overlay that respects the EMR of record. No new login, no migration, no six-month implementation. The PHI never leaves the practice's environment.
Physicians finish seeing patients at 5:30. They don’t close their last chart until 10 or 11. They call it pajama time. Not affectionately.
The thing that keeps a clinician up isn’t usually “did I do the right thing for this patient.” That gets resolved in the room. The question is “did I document the right thing in the right way so that a coder in two weeks, or a payer in three months, doesn’t deny this claim or ding us on a quality metric.”
Read the full essayCortex starts with chart QA and compounds into practice memory.
Every accepted suggestion teaches the workflow where clinical intent, payer requirements, and practice standards diverge. Over time, Cortex becomes the connective tissue between documentation, operations, and patient follow-through — without replacing the EMR underneath.
- Year 1
- Chart QA
- spellchecker for the note
- Year 2
- Owner visibility
- revenue captured, coding lift, adoption
- Year 3
- Coding workflow
- back-office surface around the chart
- Year 4+
- Operating layer
- scheduling, intake, RCM