Skip to content

Sensitive health records need clear guardrails

Patients control what they share, hospitals control who works on what, and every sensitive action leaves a trail.

In short

  • 01Security audited: Safe to Host
  • 02Each hospital's data stays separate
  • 03Every sensitive action is logged
10 layers of protection

How MedChaaya protects records, layer by layer

Every safeguard between the outside world and a patient's record. Scroll to arm them, one at a time.

  1. Layer 01

    Independent security audit

    Code Decode Labs, a CERT-In empanelled auditor, assessed the MedChaaya web application from 16 to 29 October 2026. Every recommended fix was patched and re-validated, and MedChaaya was certified Safe to Host, valid until 2 November 2027. MedChaaya is also certified compliant with ABDM Milestones 1, 2 and 3.

    • Certificate no. CDL-CSS/VAPT-WATA/COA-STH/26-11-269
    • Re-assessed whenever major changes are made to the code
    • Both certificates are on the certifications page
  2. Layer 02

    Access and sharing

    Patients can share specific documents, a date range, or their complete record with a selected doctor or healthcare provider. Consent is recorded, and patients can revoke access. Sharing, viewing, downloading, revoking, and expiring access are recorded in audit logs.

  3. Layer 03

    Hospital-level separation

    Every hospital-owned record carries that hospital's ID, and every request is scoped to it. A user's hospital membership is verified against the database on each request, not only read from the login token.

  4. Layer 04

    Role and permission based access

    Each action passes a role check, a module check and a permission check. Doctors, hospital staff, hospital administrators and platform administrators receive access according to their assigned role and the care workflow.

    • Staff permissions are managed by group, with per-user overrides
    • An explicit deny always wins
    • Doctors own their own visits and prescriptions
  5. Layer 05

    Approvals and financial integrity

    Money actions need a second person, and numbering cannot be gamed.

    • Voids, discounts and refunds each need a request and a different approver
    • Gap-free invoice and receipt numbering by financial year
    • Goods receipts are immutable once posted
  6. Layer 06

    Audit trail

    A system audit log records who did what, when and from where, with before and after values for changes. A per-patient audit trail shows who accessed a record, and failed logins are recorded.

  7. Layer 07

    Sign-in

    Sign in with a password, an OTP, Google or ABHA.

    • Signed access and refresh tokens
    • Salted password hashing
    • Expiring OTPs, rate-limited requests and limited verification attempts
  8. Layer 08

    Concealed identifiers

    Record IDs sent to the browser are encrypted, and the internal numbering is never exposed.

  9. Layer 09

    Safe calls and ABDM exchange

    Video and audio go directly between doctor and patient and never reach MedChaaya's servers. Only authorised participants can join a call, and knowing a call's link is not enough. Health records exchanged through ABDM are encrypted for transfer.

  10. Layer 10

    Infrastructure and privacy commitments

    MedChaaya is available as a secure cloud service or as an on-premise deployment on the hospital's own infrastructure. Its privacy policy follows the DPDP Act, 2023, and medical records are retained for a minimum of three years. MedChaaya does not claim ISO, SOC or HIPAA certification. Additional details about encryption at rest, internal access controls, deletion, and backup retention will be published after they are confirmed against the deployed configuration.

Want to see it in action?

We'll show you MedChaaya with your own workflows.

Request a demo