Security

Data at rest: the free-text machine configuration in a patient's profile is additionally encrypted by the application before it is stored. Structured treatment settings (such as blood and dialysate flow, heparin, dialyzer and machine brand) and all other data are stored in database columns protected by the storage layer's encryption at rest.

Data in transit: encrypted on all connections. HTTP is redirected to HTTPS.

Nephra uses role-based access control (RBAC) with six distinct roles: Admin, Doctor, Nurse, Secretary, Operator, and Patient. Each role has a least-privilege set of permissions enforced at the API layer; secretaries have scheduling access only: they never see prescriptions or referral snapshots, but they do see appointment details, including any notes added to a booking.

Write operations on clinical, billing and account data, and reads of patient records, are recorded in an audit log with user ID, timestamp, action type and a redacted summary of the change. The application never edits or deletes audit entries, and they are retained for the life of the account and beyond it.

If you discover a security vulnerability, please report it responsibly to [email protected]. We aim to acknowledge reports within 2 business days and provide a fix timeline within 10 business days for critical issues.

We do not pursue legal action against researchers who act in good faith under this policy.