Skip to content

Evidence Checker

Check documentation statements against MEAT before you lock the code.

Copy the exact deidentified excerpts, review support strength, and keep coder verification in view.

Buddy the Bee searching evidence wording
Evidence CompanionDe-identified text onlyA few statements, not a chart

Strength of Evidence Checker

Copy the exact deidentified excerpts for one condition and review MEAT support, weak documentation patterns, missing evidence, and coder-ready next steps.

Tool

Strength of Evidence Checker

Condition

Not entered

ICD-10-CM

Optional

Status

Evidence review pending · 0/2500 chars

Documentation input

Enter documentation statements

PHI screen before evidence review

Do not enter PHI.

Remove names, DOB, MRN, member ID, MBI, claim number, address, phone number, and full patient tied dates.

Nothing you enter here is stored or logged.

0/2500 characters. Text only. No PDFs in V1.

What the Evidence Checker is for

HCC Buddy’s Evidence Checker helps coders review whether the deidentified documentation statements they enter contain MEAT support for a diagnosis. It is designed as a Code Card Companion, meaning the workflow stays close to code review while keeping documentation support, weak evidence patterns, and missing evidence visible in one place.

The result is documentation support guidance, not a final coding, clinical, payment, or CMS compliance determination.

MEAT Review

MEAT documentation criteriaFour panels showing the MEAT review mnemonic: Monitor, Evaluate, Assess or Address, and Treat, each with a coder-facing example of what the evidence looks like in a chart.MMonitorA1c trends, BP readings,weight logs over timeevidenceEEvaluatetest results reviewed,symptoms worsening or notevidenceAAssessseverity or stability call:“stable”, “uncontrolled”evidenceTTreata med, procedure, ortherapy actively orderedevidence

The checker separates monitor, evaluate, assess, and treat findings so a coder can see which support types are present and which are missing.

RADV-Style Risk Flags

HPI-only wording, family history, problem-list-only entries, medication reconciliation, screening-only text, and ruled-out conditions are called out before a coder relies on the diagnosis.

Coder Verification

Every result stays in a verification posture. Coders still need the full record, valid provider documentation, date of service, and current ICD-10-CM rules.

Use Evidence Review With The HCC Workflow

Use the Evidence Checker before relying on a diagnosis found during chart review. Then confirm the exact ICD-10-CM code in the ICD-10 encoder, review documentation patterns in the MEAT criteria guide, and open the RAF Calculator.

Evidence Checker FAQ

What does the Strength of Evidence Checker review?

The checker flags documentation-review signals in the deidentified documentation statements a coder enters, including language that may fit the MEAT mnemonic. It does not decide reportability, assign a final code, or make a RADV determination.

Can HCC Buddy make a final RADV determination?

No. HCC Buddy provides coder support only. A coder still needs to verify the full record, provider signature, date of service, diagnosis specificity, ICD-10-CM guidance, and payer or audit requirements before final coding.

What documentation usually causes a weak SOE result?

Weak support commonly comes from mention-only wording, HPI-only text, family history, problem list only, medication list only, history-only diagnoses, ruled-out conditions, possible or suspected wording, and contradictory statements.