Security
How DeepHealth AI protects hospital and patient data: isolation, access control, audit trail and backups.
Hospitals ask three questions before they trust software with a patient record: where does it live, who can see it, and what happens when something breaks. Here are the answers.
Isolation
Every organisation's records are isolated at the database level with row-level security. Hospitals and groups that want more separation are given a dedicated schema or a dedicated database of their own.
Access control
Roles are defined per department: reception, nursing, laboratory, pharmacy, billing, stores and management. A user sees only the screens and the records their role allows, and a rate or tariff change needs its own permission.
Audit trail
Every read, edit, cancellation and refund is logged with user, timestamp and record. The trail is searchable in the application and exportable for internal audit and NABH.
Deployment
Run it on a server inside the hospital, or on AWS or Oracle Cloud managed by DeepScience Tech's own infrastructure team, which holds partner credentials on both. Consultation, prescription and billing continue on the local network if the internet link drops, and sync when it returns.
Backups
Backups run on a schedule and are restore-tested rather than merely taken. Retention and recovery targets are written into the support agreement.
Reporting an issue
If you believe you have found a security problem, write to info@deepsciencetech.com or call +91 9000 999 505. We will acknowledge it and tell you what we are doing about it.
Let's build a smarter healthcare ecosystem
Tell us how your hospital runs today. We'll show you the same flow inside DeepHealth AI.