Trust and security
Who can act, what is recorded, and what we agree with you before go-live.
A named person approves every submission
mutim drafts. Your staff approve. Nothing is sent to NPHIES without a named person’s approval of that exact draft.
An audit trail that cannot be edited
Every draft, check, approval and submission is recorded with who did it and when. Entries are added, never changed or deleted.
Evidence behind every code
Each code and each line of medical justification shows the sentence of the clinical note it came from.
Rules decide, not the model
A language model reads the note and the payer’s free text. Amounts, statuses and routing are computed by fixed rules, so the same request always gets the same answer.
Patient data and PDPL
Before go-live we agree with your compliance team how patient data is processed under the Personal Data Protection Law: where it is held, and what is de-identified before a model reads it.
Recordings and consent
A consultation is recorded only when the doctor starts it, and recording needs the patient’s consent. How consent is taken, where audio is processed and whether it is kept after the note is signed are agreed with your compliance team before go-live.
Decision support
mutim shows what the payer asks for and names what the consultation has not covered. It does not diagnose and it does not order. The clinician decides.
Data residency
Where patient data is stored is part of that agreement. This website stores no patient data.
NPHIES
Requests are built on the NPHIES FHIR R4 profiles and validated before they are sent.
Access
mutim is in private pilot access. Named accounts and single sign-on with your identity provider are set up with each facility before go-live.
This page describes the product as it is being piloted. Ask us for the current security summary before you sign.