Security and privacy
Designed so identifiable data stays in your network.
For IT and privacy teams: what runs where, what is sent, and who can see it.
Your hospital network
Incident app and database
Full records, narratives, worker IDs
Full records, narratives, worker IDs
De-identify and package
Manager approval
Approved monthly package →← Peer benchmarksOutbound HTTPS only. No inbound ports.
HIPS Central
Submission service
De-identified data and staffing counts
Benchmarks and reports
What leaves your hospital, and what never does
| Item | What HIPS Central receives |
|---|---|
| Incident narrative | Never sent |
| Worker ID and start date | Never sent; start date becomes a tenure range |
| Event date and time | Year and month; time as a shift block |
| Worker age | An age range |
| Event ID | A one-way code, so corrections update the same record |
| Codes: injury type, unit, job, cause, severity | Sent |
Approval before anything moves
A named manager reviews each monthly package and signs it. Every approval is logged.
Least-privilege roles
Reporters, approvers, facility and system administrators, and report-only users. Up to five administrators per facility.
Hosting options
Run the incident app on your own server, or let us host it for you under a business associate agreement.
Security questions
Email [email protected] for our security overview or to report a concern.
Start with your own numbers.
Three hospitals can join the founding pilot at no cost.