Patients control what they share, hospitals control who works on what, and every sensitive action leaves a trail.
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.
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.
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.
Money actions need a second person, and numbering cannot be gamed.
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.
Sign in with a password, an OTP, Google or ABHA.
Record IDs sent to the browser are encrypted, and the internal numbering is never exposed.
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.
MedChaaya is hosted on Microsoft Azure. Its privacy policy follows the DPDP Act, 2023, and medical records are retained for a minimum of three years. MedChaaya does not claim third-party certifications such as ISO, SOC or HIPAA. Additional details about encryption at rest, internal access controls, deletion, and backup retention will be published after they are confirmed against the deployed configuration.
