MEDIKODI CDI
When the record doesn't add up,
ask the clinician
CDI reads every coded episode for contradictions, gaps and missing detail, shows you the lines that don't agree, and drafts the question for the clinician.
A code is only as good as the note behind it. When the summary says one thing and the echo another, the right answer isn't in coding. It's with the clinician.
What it looks for
Five ways a record goes wrong
Every finding is one of these, with a severity, a confidence score and the lines in the chart that raised it.
-
Contradiction
Two parts of the record say different things.
-
Discrepancy
Details don't line up, such as dates or sites.
-
Gap
Something coding needs isn't documented.
-
Clarification needed
It's documented, but not clearly enough to code.
-
Omission
Care is recorded in one place and missing from another.
The right next step
Not every finding needs a doctor
Each finding comes with a pathway: a provider query, a clarification, a check of records already on file, or nothing to do.
When the answer is already in the chart, CDI says where to look first, so clinicians only hear about what truly needs them.
The query, drafted
A question a clinician can answer
The clinical indicators, one neutral question and clear options, including "clinically unable to determine".
A second check reads every draft before your specialist sees it: no codes, no leading wording, no mention of funding.
Your rules
Decide when CDI holds up coding
Route by what CDI found and what the episode is. Coding can wait for CDI, carry on alongside it, or skip it.
Work goes to the CDI specialist with the most room, with first-action deadlines and reminders so nothing sits in the queue.
Where CDI sits in an episode
The steps in blue are CDI's. The rest is the coding you already run.
-
Coded
The episode is coded with the evidence beside each code.
-
Reviewed
CDI reads the same record for gaps, and holds any code a finding affects.
-
Routed
Your rules decide whether coding waits, carries on, or skips CDI.
-
Queried
Your CDI specialist sends the drafted query, or settles it from the chart.
-
Signed off
The specialist marks CDI complete, and the episode goes back to coding.
Built to ask fairly
-
No leading questions
Queries never suggest a diagnosis, never contain a code and never mention funding. Each asks about one thing.
-
Fewer, stronger findings
CDI would rather raise nothing than raise something weak. Findings that don't change coding are marked as needing no action.
-
A person sends every query
Nothing goes to a clinician on its own. Your CDI specialist reviews, edits and sends, then signs off.
Questions about CDI
When does CDI review an episode?
After the episode is coded, on the same documentation. It reads the record against the codes and the coding standards, so its findings are about what the documentation supports.
Does CDI send queries to clinicians by itself?
No. CDI drafts the query with the clinical indicators and response options. Your CDI specialist reviews it, edits it if needed and sends it. Clinicians reply from a secure link.
What happens to codes while a query is open?
Codes the finding affects are marked as held, so nobody finalises them by mistake. Your coder applies the right code once the answer is in.
Can we choose which episodes go to CDI?
Yes. Routing rules decide by what CDI found and what the episode is, and choose whether coding waits for CDI, runs alongside it, or skips it.
Is CDI a separate product?
CDI is part of MEDIKODI Coding and works on the same episodes, alongside MediqAssist. For an independent check on coding that's already done, see MEDIKODI Lens.