How it works
One episode, five steps
From the moment an episode arrives to the moment it's final, here's what MEDIKODI does, and where your team decides.
What happens at each step
Each step does one job and stops one kind of mistake. A person signs off at the end.
-
Step 1: Received
The episode arrives from your hospital system, or your coder uploads the discharge summary. Nobody retypes anything.
Stops Episodes that sit untouched
-
Step 2: Coded
The whole record is read. Every diagnosis and procedure is coded, with the sentence that supports it beside the code.
MEDIKODI Coding →Stops Care that never reaches the claim
-
Step 3: Grouped
Codes are sequenced to the coding standards and the episode groups as the codes change, not after.
Stops An episode grouped below the care it records
-
Step 4: Routed
Routine episodes go straight to sign-off. Complex ones go to the right coder, with the reason and a due date.
Stops Hard cases rushed, easy ones waiting
-
Step 5: Checked
A reviewer checks the episode at the rate you set, and every change is recorded with its reason. Then it's final.
Stops Codes an insurer or auditor would challenge
Two ways in
Nothing to rip out
MEDIKODI works alongside the systems you already run. However an episode arrives, the steps after it are the same.
-
Straight from your systems
Episodes flow in from your hospital information system and final codes flow back. Scoped with your IT and security teams.
-
Upload to start
Your coder uploads discharge summaries directly. Nothing to integrate, so you can begin before any integration work.
After step 5
Checked before it's final, and after
Your reviewers check episodes inside Coding before they're final. Lens gives an independent read afterwards, and anyone on either side of the claim can run it.
Audit in Coding
Part of your own workflow. Reviewers change codes before an episode is final, with a recorded reason and the grouping impact shown first.
Audit in Coding →MEDIKODI Lens
Independent of the workflow. Upload one episode or a whole extract, coded by anyone, and see what the record supports and what it doesn't.
Explore Lens →What changes from the way you code today
-
Who codes the routine episode
- Manual
- A coder, every time
- Assisted
- A coder, with suggestions
MEDIKODI · Coded for you, your coder signs off
-
Evidence for each code
- Manual
- In the coder's head
- Assisted
- Sometimes shown
MEDIKODI · The source sentence, every time
-
Complex cases
- Manual
- Same queue as everything else
- Assisted
- Same queue as everything else
MEDIKODI · Routed to a coder, with the reason
-
Grouping
- Manual
- After coding is finished
- Assisted
- After coding is finished
MEDIKODI · Live, while codes change
-
Measuring quality
- Manual
- A sample, when there's time
- Assisted
- A sample, when there's time
MEDIKODI · Every episode, with Lens
| Aspect | Manual coding | Computer-assisted | MEDIKODI |
|---|---|---|---|
| Who codes the routine episode | A coder, every time | A coder, with suggestions | Coded for you, your coder signs off |
| Evidence for each code | In the coder's head | Sometimes shown | The source sentence, every time |
| Complex cases | Same queue as everything else | Same queue as everything else | Routed to a coder, with the reason |
| Grouping | After coding is finished | After coding is finished | Live, while codes change |
| Measuring quality | A sample, when there's time | A sample, when there's time | Every episode, with Lens |
Questions about the process
How long does it take to get started?
You can start with uploads straight away, with nothing to integrate. Most hospitals begin with a retrospective review of closed episodes, then connect their systems once they've seen the results.
Who signs off the final codes?
Your coders. MEDIKODI codes the episode and shows its evidence, and a person signs it off. Reviewers can check any episode before it's final.
What happens to a complex case?
It's routed to a coder with the reason it needs them and a due date. The coder can ask MediqAssist about the standards, or query the clinician, without leaving the episode.
How is Lens different from the check in step 5?
Step 5 is your own review, inside Coding, before the episode is final. MEDIKODI Lens is a separate, independent check on coded data, done any time afterwards, by your hospital, a health fund or an auditor.
How is patient data handled?
Sensitive details are de-identified before AI processing, data is encrypted in transit and at rest, and hosting is agreed with your IT and security teams. See security & trust.