Security & compliance

Patient data is held to a
clinical standard.

Rxcript is built for Indian healthcare data from the ground up - local residency, strict per-user isolation, recognised clinical coding, and no commercial conflicts of interest.

India data residency
Row-level isolation
WHO ICD-11 ยท NRCES / SNOMED coding
No pharma partnerships
๐Ÿ‡ฎ๐Ÿ‡ณ

India data residency (DPDP)

Patient data is stored in-region (India), and Rxcript is built around the principles of India's Digital Personal Data Protection Act, 2023 - purpose-limited processing of health data, with privacy and consent considered from the start.

๐Ÿ”’

Per-user isolation

Every record is protected by database row-level security - patients see only their own data, and physicians see only the patients and prescriptions they're authorised for. Shared-care access is explicit and revocable.

๐Ÿ“

Recognised clinical coding

Diagnoses use WHO ICD-11; medicines use the NRCES / SNOMED CT drug coding that India's ABDM is built on. Interaction data is sourced from a structured, citable interaction database - not free text.

โš–๏ธ

Medico-legal documentation

Every encounter is recorded as an immutable, point-in-time prescription: who diagnosed, who prescribed, what was adjusted or stopped, and why - defensible if it's ever questioned.

๐Ÿšซ

No conflicts of interest

Rxcript has no pharmaceutical arrangements and no incentivised prescribing. Drug suggestions are driven by clinical guidelines and safety - never by who pays.

๐Ÿ”‘

Authentication & access

Secure sign-in with role-based access for physician, clinic-staff and patient, plus optional two-step verification (a one-time code by email) and self-service password reset. Sensitive clinic-to-clinic notes are never exposed to patients, regardless of sharing tier.

Have a compliance or data-residency question?

We're happy to walk your clinic or IT team through exactly how Rxcript stores, isolates and protects patient data.

Talk to us