Trust comes fromshowing the work
Every coding decision can be explained, reviewed and defended. Your patients' data is handled on terms you set.
Before anything is processed
The AI never needs to know who the patient is
Names, dates of birth, record numbers and addresses are removed before AI processing begins. What's left is what coding needs: the clinical story.
It happens in your environment or a dedicated secure instance, as agreed with your IT and security teams.
How data is handled, start to finish
Before processing
-
De-identified first
Identifiers are removed before AI processing begins.
-
Only what's needed
Processing uses the minimum information required to code the episode.
-
Hosting you agree
Where data is hosted is agreed with your IT and security teams before go-live.
While it's coded
-
Encrypted
In transit and at rest, and processed in isolated environments.
-
Access by role
Each person sees and does only what their role allows.
-
Evidence on every code
Suggestions are grounded in the record, with the source sentence attached.
Afterwards
-
Versioned submissions
Every submission of an episode is kept, so any version can be compared.
-
A reason for every change
A recorded reason is required before a code change commits.
-
Reviewable later
Any episode can be traced back to who did what, when and why.
Access by role
Everyone sees what their job needs
What's visible and what's allowed changes with each role, from the administrator who sets the rules to the coder who signs off.
A clinician answering a coding query doesn't need an account. They get a secure link to that one question, and nothing else.
MEDIKODI Lens
Sharing coded data for a check
Lens checks coding for hospitals and health funds alike. Here's how an upload is handled.
Explore Lens →-
Only the episode in question
Lens assesses what you upload for that admission, not a patient's wider history.
-
De-identified before assessment
Sensitive details are reduced before Lens looks at anything.
-
Each customer kept separate
Hospitals and health funds can both use Lens. Their data never mixes.
-
Nothing to install
Lens runs in the browser, with no integration into your systems.
What security teams ask
Does patient data leave our environment?
That's agreed with you. Hosting and processing locations are set with your IT and security teams before go-live, including options to run in your own environment or a dedicated secure instance.
Who at our organisation can see patient data?
Access is by role. Administrators, coders, auditors and CDI specialists each see what their work needs. Clinicians answering a query only see that query, through a secure link.
Can we trace what happened on an episode?
Yes. Submissions are versioned and every code change carries a recorded reason, so you can see who changed what, when and why.
Who is accountable for the final codes?
Your coders. MEDIKODI suggests codes and shows its evidence, but it isn't the authority and doesn't guarantee reimbursement or compliance. A person signs off every episode.
Which certifications do you hold?
Certification status is confirmed with current evidence during your security assessment. Request our security documentation and we'll share what applies to your deployment.
Bring us your security questionnaire
We'll confirm the documentation, hosting location, contractual terms and controls that apply to your deployment. Certification status is confirmed with current evidence during your assessment.