Security
Built to HIPAA requirements, in plain English.
Here is exactly what protects patient data in Vital Dispatch and where each safeguard lives. No certifications we do not hold, no vague promises.
Your own database, with a BAA
Each client runs on a dedicated, encrypted database hosted in the United States on a plan that supports a Business Associate Agreement. Your patient data is not pooled with anyone else's, and we sign a BAA with you.
Sign-in controls
Two-factor sign-in is built in and switched on per client. Admins can set a temporary password or reset a second factor from the staff record, every login is on record there, and signing out signs out only that device.
Role-based access, enforced in the database
Admin, dispatcher, nurse, nurse practitioner and medical director each see only what their job needs. The rules live in the database itself (row-level security), not just in the app's screens, so a dispatcher cannot read chart content from any screen or API call.
Signed records with every version kept
A signed chart keeps its signature and signed time forever. A correction within 60 days, or after an admin unlocks it, needs a reason, keeps every previous version and writes a chart note. Treatment notes are permanent; changes are amendments.
Audit trail
Every change to a patient record is logged with who made it and when. The log is append-only.
No PHI in notifications
A push says who sent a message and which chat to open, or what kind of item needs you. Client texts carry the business name, the nurse's first name, the time and a link. Patient names and clinical details stay inside the app.
Encrypted storage for photos and documents
Photos and documents live in private, encrypted storage and are served through short-lived links. There is no public bucket.
Credential lockout
A nurse whose license or required credential has lapsed loses access to patient records until it is current.
Retention
Charts are kept for seven years after the patient's last service. Team chat is kept for thirty days.
Roles
Minimum necessary, enforced in the database
Access rules are row-level security policies in the database. A screen cannot show a record the role is not allowed to read, and an API call cannot fetch it either.
| Role | Sees |
|---|---|
| Admin / owner | Everything for their units: staff, services, forms, QuickBooks, chart approval and corrections. |
| Dispatcher | Board, calendar, patients and visits. No chart content, no chart approval. |
| Nurse | Visits, patient records, consents and their own calendar while credentials are current. A training-only nurse sees the training library alone. |
| Nurse practitioner | Charts awaiting review and the Good Faith Exams they perform; can be flagged to dispatch as well. |
| Medical director | Charts routed for review: every Good Faith Exam, the sample, and anything sent manually. No booking or calendar access. |
What we say and what we do not
We say Vital Dispatch is built to HIPAA requirements and that we sign a Business Associate Agreement with every client. We do not say “HIPAA certified”, because there is no such certification, and we do not claim third-party attestations we have not completed.
HIPAA compliance is a property of your business, not of any single piece of software. Vital Dispatch supplies the technical safeguards described above; your policies, training and risk analysis complete the picture. We are happy to walk your compliance officer through the details.
Where the data lives
Each client runs on a dedicated, encrypted Postgres database and private encrypted file storage hosted in the United States on a plan that supports a BAA. The web application runs on Vercel. Push notifications travel through the phone platforms’ own relays (Apple, Google and Microsoft) with payloads that carry no patient data: a sender’s name and which chat to open, or what kind of item needs attention.
Questions
Ask for our subprocessor list or a walkthrough of any control at info@vital-dispatch.com, or book a demo.
Walk your compliance officer through it.
We will show the audit trail, the review chain and the access rules live, on a demo database.