Skip to content
MedBrainsBook a demo

AI and data safety

AI that helps, and knows its place.

MedBrains uses AI for clear-cut operational checks and data quality. Diagnosis, treatment and dose always stay with the clinician, a person approves every action, and patient data is protected before AI sees it.

What our AI is for

Clear-cut checks, not clinical decisions

It helps with questions like

  • Is this pre-authorisation packet complete, and which documents are missing?
  • Which discharge clearances are still pending for this patient?
  • Which fields in this record are missing, contradictory or implausible?
  • Which critical results have not been acknowledged yet?
  • Drafting a note from what is already recorded, for a clinician to check and sign

It never does

  • Make a diagnosis
  • Decide a treatment or a dose
  • Create, place or sign an order
  • See or do more than the person signed in

In the product today

How the assistant works now

Only what you can see

The assistant reads through the same screens and permissions as the person using it. It cannot open a record that person could not.

Clinical facts, not identities

When the assistant is given a patient's context, it receives clinical facts such as allergies and active medicines, never the name, UHID or other identifiers.

Mental-health records withheld

Mental-health entries the user may not see are withheld from the assistant too.

Labelled, then signed

Anything the assistant drafts carries an AI label and reaches the case sheet only when a clinician inserts it. It never creates or signs an order.

On the audit trail

Every lookup the assistant makes is recorded on the audit trail, under the user it acted for.

Policy we hold ourselves to

Our AI commitments

No clinical suggestions

New AI features are limited to operational checks and data quality. They do not suggest diagnoses, treatments or doses.

Exactly on point

No more and no less than the task needs. Every fact in an answer traces back to a field in the record.

Flag, don't guess

If the record does not say it, the AI says so instead of filling the gap.

A person approves

A clinician or staff member approves every action. The AI prepares; people decide.

Always labelled

Everything the AI drafts is marked as AI-drafted wherever it appears.

Recorded as AI

Every AI action is recorded in the audit trail as the AI acting on behalf of a named user.

Never more than you

The AI can never see or do more than the person signed in.

Before any AI feature handles patient data

Protecting patient data when AI is used

  • Names, phone numbers, UHID, ABHA, Aadhaar, PAN, bank, card and UPI details and policy numbers are replaced with placeholders before any AI model sees the data.
  • Sensitive categories, including HIV status, mental health, PCPNDT and medico-legal records, are left out entirely.
  • Each task gets only the fields it needs, nothing else from the record.
  • Patient data goes to AI models hosted in India (AWS Mumbai) by default, with no third-party routers in between.
  • No patient data is used to train AI models.
  • If any protection fails, the AI does not run, and says so.

How we check. Every AI feature must pass our test suite for accuracy and data leakage before release: answers checked against the source record for anything added or left out, and every output checked for identifiers that should never be there.

These protections are being built into every AI feature now. An AI feature that handles patient data is released only once they are in place.

Across MedBrains

How we protect hospital data

Every hospital sealed off

Each hospital's data is isolated by row-level security in the database itself, not only in the app.

A restricted database role

The application connects to the database as a restricted role, so even the app itself cannot step around each hospital's row-level rules.

Role-based permissions

Every request is checked on the server against the user's role, with per-user extra or denied permissions.

Two-factor sign-in and SSO

Authenticator-app codes with one-time recovery codes, required by role if the hospital chooses, and single sign-on.

Every access audited

Who saw or changed what, and when.

Daily backups

A full database backup every day, and an hourly check that the latest one landed.

Hosted in India, or on your servers

Our hosting runs in AWS Mumbai. Or install MedBrains on your own servers and patient data never leaves the building.

Being completed now

  • Encrypted off-site copies of every backup, and regular restore tests.
  • A written incident response plan under CERT-In rules, with prompt notice to the hospital so it can meet its DPDP duties.

Our promises

  • Your hospital owns its data. For patient data we are a data processor under the DPDP Act, 2023, working only on your instructions under a data processing agreement.
  • A full export whenever you ask; when you leave, we return your data and delete our copies.
  • We never sell data, and no money from pharmaceutical companies or advertisers reaches the product.

Full details in our commercial terms and privacy policy.

Questions

Does MedBrains AI diagnose or suggest treatment?

No. It does not diagnose, and it never decides, places or signs an order: diagnosis, treatment and dose stay with the clinician. Today the assistant can write out a prescription a clinician asks for, checked against the patient's allergies and drug safety rules, as text the clinician decides whether to use. New AI features are limited to operational checks and data quality, such as a missing pre-auth document or an unacknowledged critical result.

Can the AI see records I cannot?

No. The assistant reads through the same screens and permissions as the person using it, and every lookup is on the audit trail.

Is patient data used to train AI models?

No. We do not use patient data to train AI models.

Where does the AI run?

For patient data our standard is AI models hosted in India (AWS Mumbai), with no third-party routers in between. Each hospital's AI provider is set in its own settings.

What happens if the protections fail?

The AI does not run. You see a message that it could not run safely, and the work carries on without it.

Who owns our hospital's data?

Your hospital does. We process patient data only on your instructions, export it whenever you ask, and return and delete it when you leave.

Is MedBrains certified?

We do not claim certifications we do not hold. MedBrains is built for ABDM, NHCX and UHI but not yet certified by NHA, and we act as a data processor under the DPDP Act, 2023.

Book a demo

See it run on your departments.

Tell us about your hospital. We'll walk through the screens your teams would use — with your workflows, not a slideshow.

  • A 30-minute walkthrough, online or at your hospital
  • Your departments, your tariff, your forms
  • A clear plan and price for going live

Rather talk now? WhatsApp us or write to hello@medbrains.in.

We reply within one working day. We never share your details.