Patient data, protected by design
Here is exactly what SwasthyaSync does to keep clinical data safe — and, just as plainly, what is not finished yet.
Six layers of protection
A separate database for every clinic
Each clinic's records live in its own database, and every service takes the clinic from the signed-in user's token — never from something the browser can change.
- One database per clinic for OPD, and one per clinic per module (lab, radiology, IPD, pharmacy)
- Clinic identity taken from the signed token on every request
- Branch scoping: staff see only the branches they are assigned to
- Patients in the app can see and book only for themselves
Clinical text encrypted at rest
Clinical free text is sealed with AES-256-GCM before it is written, in the OPD, IPD, pharmacy, lab and radiology services alike.
- Visit notes, IPD clinical entries, radiology report narrative and versions
- Lab notes, rejection reasons, correction notes and microbiology comments
- Patient email and phone encrypted; queue priority reasons too
- Services refuse to start in production without an encryption key and real secrets
Roles and sign-in
Eight built-in roles decide what each person can see and do; one person can hold several, such as an owner who is both admin and doctor.
- Admin, doctor, lab doctor, staff, nurse, lab technician, receptionist, pharmacist
- Role checks on sensitive actions, such as lab verification and approval
- Session refresh kept in an HttpOnly cookie, out of reach of page scripts
- Login lockout and rate limits on sign-in and one-time-code endpoints
Audit trails
Who opened, changed or completed a record is logged — the log stores which fields changed, never the clinical values themselves.
- OPD: visit create, update, complete and read; patient record reads
- Lab: full order, sample and result history with chain of custody
- Radiology: per-investigation audit including report versions
- IPD: audit panel per admission
Ayushman Bharat Digital Mission
SwasthyaSync implements the health-information-provider side of ABDM. It goes live for your clinic once your facility is registered with ABDM and its credentials are configured.
- ABHA linking of patient records
- Care-context discovery and linking
- Consent requests and health-information sharing
- Available on Professional and Enterprise plans
FHIR R4 export
Clinical records can be exported as HL7 FHIR R4 resources for exchange with other systems.
- Patient, Encounter, Condition, Observation
- MedicationRequest and AllergyIntolerance
- Lab orders available as FHIR too
- Final diagnoses coded with WHO ICD-11 or ICD-10
Run with care
Health checks
Every service checks its database and reports outages
Backup & restore
Scripted database backups and restores
Request tracing
A request ID follows each action across services
Secrets enforced
Placeholder keys block a production start
What we don't claim yet
SwasthyaSync has not yet completed formal certifications or audits such as ISO 27001, SOC 2, a third-party penetration test, or ABDM certification. We'll list each one here when it is done. HIPAA is a US law and does not apply to Indian clinics.
Security FAQs
Where is patient data stored?
Each clinic's data is kept in its own databases on SwasthyaSync's servers. Talk to us about hosting location and on-premise options for your organisation.
Can we get our data out?
Yes. Lists can be exported to Excel (Starter and above), and clinical records can be exported as FHIR R4 on Professional and Enterprise.
Is SwasthyaSync certified for ABDM, ISO 27001 or similar?
Not yet. The ABDM integration is built, but certification and audits such as ISO 27001 have not been completed, and we don't claim them. Ask us for the current status.
Who can see a patient's records?
Only signed-in staff of that clinic, limited by their role and branch. A patient using the app sees only their own records.
Does SwasthyaSync help with the DPDP Act 2023?
The platform provides building blocks — encryption, access control, audit logs and per-patient opt-outs for alerts — that support your obligations as a data fiduciary. Compliance also depends on how your clinic uses it.
Have security questions?
We'll walk your team through how data is stored, encrypted and accessed.
Talk to Us