NighteengaleBuilt for confidentiality — honestly.
Each practice owns its own private instance. Here is exactly what we implement in the product, and what still has to happen operationally before going live with real patients.
Implemented in the product
Explicit consent & privacy acknowledgement
Every intake captures treatment consent and a HIPAA / PIPEDA / GDPR acknowledgement with a typed e-signature, timestamp, and IP address.
Practice-level data isolation
Each practice is a private tenant. Patients belong to one practice; no practice can access another's records. Your data stays within your own practice — never shared with a competing platform.
Role-based access control
Patients can only ever see their own records. Providers see only their own practice's patients, intakes, and appointments.
PHI audit logging
Every view, export, or erasure of patient data is recorded with user, action, and timestamp — reviewable in the provider Compliance tab.
Data-subject rights (GDPR / PIPEDA)
Patients can export a full copy of their data or permanently erase their account and health records at any time, directly from the portal.
Encryption in transit
All traffic is served over TLS/HTTPS.
Operational steps before go-live
- A signed Business Associate Agreement (BAA) with the hosting provider.
- Compliant, audited hosting with encryption-at-rest and managed keys.
- Chosen data residency (e.g. US for HIPAA, Canada for PIPEDA, EU for GDPR).
- The AI assistant uses an external LLM processor — for zero-third-party confidentiality, swap in a self-hosted or BAA-covered model.