Security and privacy
Built to hold as little PHI as possible.
The safest patient data is the data you never collect.
Minimum necessary, enforced on import.
Names become initials before anything is saved. Dates of birth, diagnoses and member IDs are never stored, so they can never leak.
Security and privacy
Built to hold as little PHI as possible.
The safest patient data is the data you never collect. stayflow keeps only what a UR team needs to hit a deadline, and the database enforces the rest.
Minimum-necessary by design
Patients are stored as initials and an EMR ID. No names, dates of birth or diagnoses.
Tenant isolation in the database
Row-level security scopes every query to your organization and, where set, to a user's facilities.
Every change audited
Status and clock changes run through server-side functions that log who changed what, and when.
Nothing sensitive leaves the app
No patient data in URLs, error reports or alert emails. Exports are role-gated and logged.
Automatic retention
Raw import rows and integration payloads are cleared on a daily schedule, so source files never linger.
Roles that match the work
Owners, admins, UR coordinators, clinicians, billing and viewers each see and change only what their job needs.

