Security and privacy
How Ayulex HMIS protects your patients' data.
A plain account of the controls built into Ayulex HMIS: what each one does, how it is enforced, and where the responsibility sits.
Trust Center: sub-processors, data location and vulnerability reporting
At a glance
The short version.
For your IT team, your auditors and anyone filling in a vendor questionnaire.
- Hosting
- India, Mumbai region: application and database
- Outside India
- E-mail, WhatsApp, the sign-in bot check and the optional AI scribe, each listed in the Trust Center
- In transit
- TLS on every connection, HSTS with preload
- At rest
- Database and backups encrypted
- Backups
- Automated, daily: a recovery point of up to 24 hours
- Staff sign-in
- Password plus authenticator-app code (TOTP); bot protection
- Patient sign-in
- UHID and date of birth, then a one-time code e-mailed to the patient
- Idle sessions
- Signed out after 15 minutes without activity
- Access
- Role-based, 37 permissions, custom roles, checked on the server
- Audit trail
- Append-only, enforced by the database
- Aadhaar
- Never stored or logged
- Availability target
- 99.95% a month
Access
People see what their work requires. Nothing more.
Every account has a role. Ayulex HMIS comes with standard roles, and administrators can build custom roles from 37 individual permissions.
The server checks permissions on every request, so hiding a button is never the only protection. Staff sign in with a password and an authenticator-app code, and idle sessions end after 15 minutes.
| Permission | Administrator | Doctor | Nurse | Front office | Lab technician | Pathologist | Pharmacist | Ward assistant |
|---|---|---|---|---|---|---|---|---|
| View patient records | Administrator: allowed | Doctor: allowed | Nurse: allowed | Front office: allowed | Lab technician: allowed | Pathologist: allowed | Pharmacist: allowed | Ward assistant: not allowed |
| Prescribe medicines | Administrator: allowed | Doctor: allowed | Nurse: not allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Record medicines given | Administrator: allowed | Doctor: not allowed | Nurse: allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Enter lab results | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: not allowed | Lab technician: allowed | Pathologist: allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Verify and release lab reports | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Dispense medicines | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: allowed | Ward assistant: not allowed |
| Create bills, collect payments | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Approve discounts and refunds | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: not allowed |
| Update bed status | Administrator: allowed | Doctor: not allowed | Nurse: allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: allowed |
| Read the audit trail | Administrator: allowed | Doctor: not allowed | Nurse: not allowed | Front office: not allowed | Lab technician: not allowed | Pathologist: not allowed | Pharmacist: not allowed | Ward assistant: not allowed |
Accountability
Every action leaves a trace that cannot be erased.
The audit trail records who opened a patient's chart and who changed what, with the time, IP address and device. It is append-only, and the database itself rejects any attempt to edit or delete an entry.
- Chart openings logged, not just edits
- Filter by date, user, action or record
- Built for NABH and DPDP accountability reviews
Privacy by design
Built around the Digital Personal Data Protection Act, 2023.
Collect what is needed, use it for its purpose, and keep proof of consent. These are the parts of the system that put those principles to work.
Consent on record
Consents are recorded with their purpose and, where needed, a witness. Patients can withdraw consent, and the withdrawal is recorded too.
Only what a screen needs
The waiting-area display shows token numbers, never names. Each role sees the parts of the record its work requires.
Identifiers removed for AI
Before the optional AI scribe sends any text, the names on the patient's record and identifying numbers are removed automatically. That can miss an identifier that is not on the record, so doctors should not dictate them.
Aadhaar is never kept
For ABHA verification, identifiers are encrypted with ABDM's public key before they leave our server. Aadhaar numbers and OTPs are not stored or logged.
No copies in browsers
Responses carrying patient data are marked no-store, so browsers and proxies keep no copy of them.
Clean error reports
When something fails, the error report is stripped of e-mail addresses, phone and ID numbers and tokens before it is stored.
Application security
Defences in every layer.
- A strict Content Security Policy; the application cannot be embedded in other sites
- HTTPS only, with HSTS preload
- Every input validated on the server before it reaches the database
- Rate limits and bot protection on sign-in and public forms
- Patient portal codes work once and expire after 5 minutes; sign-in pauses for 15 minutes after five wrong attempts
- Each hospital's records kept separate; every request is limited to the signed-in hospital
- Every change runs automated security, workflow and clinical test suites, with 290+ end-to-end checks against a real database
Reliability
Targets we publish.
- Availability
- 99.95% a monthAt most about 22 minutes of downtime in a month
- Server response
- Under 500 ms95th percentile, on the APIs behind every screen
- Backups
- DailyAutomated and encrypted at rest
- Recovery point
- Up to 24 hoursThe most recent data a restore can bring back today. Point-in-time recovery, to within minutes, is being introduced.
- Downtime
- Agreed procedureBefore go-live we agree with each hospital how to keep working on paper if the system cannot be reached, and how to enter that work afterwards.
- Location
- Mumbai, IndiaApplication and database in the same region
A note on certification
NABH accreditation is awarded to hospitals, not to software, and the DPDP Act places duties on your hospital as well as on us. Ayulex HMIS gives you the controls and the records those obligations call for. If your evaluation needs our security documentation or a completed vendor questionnaire, ask us.
Reporting a vulnerability
If you believe you have found a security issue in Ayulex HMIS, write to admin@ayulex.com with “Security” in the subject line, and give us reasonable time to fix it before disclosing it.
See Ayulex HMIS on your own workflows.
Tell us about your hospital and we will tailor the demonstration to your departments, your tariffs and the way your teams work today.
Write to us
We reply by e-mail.
TiLi Center, 2nd Floor, MV119 JL BuildingMission Veng, AizawlMizoram 796005, IndiaAlready a customer? Sign in to your hospital