How we handle patient data

A prior auth packet is some of the most sensitive paperwork your clinic produces. This page says in plain language what we do with it and who is accountable at each step.

  • HIPAA Built to support HIPAA requirements
  • BAA BAA signed with every clinic
  • Encrypted in transit and at rest
  • A staff member approves every submission
  • Patient data hosted in the United States
  • Every approval recorded by name and time
  • Reserved for independent attestations [NEEDS: SOC 2 / HITRUST status]

Built for US therapy clinics. Patient data hosted in the United States. BAA with every clinic.

Where your data lives

Patient data is stored and processed on servers in the United States. It is encrypted in transit and at rest.

[NEEDS: cloud provider and US region name]

[NEEDS: who can access patient data and from where]

Business associate agreement

Under HIPAA, a vendor that handles protected health information for your clinic is a business associate. We sign a business associate agreement with every clinic before any patient data comes into Zephy.

You can read the draft BAA before you sign up.

Encryption

Patient data is encrypted in transit, between your browser and Zephy, and at rest, where it is stored.

[NEEDS: Encryption specifics to state publicly (for example TLS version and AES-256).]

Access control

Each person at your clinic signs in with their own account, so access belongs to a named individual and can be removed when someone leaves. Inside Zephy, access to clinic data is limited to the people who need it to run the service.

[NEEDS: Roles and permissions available to clinics, whether multi-factor authentication or single sign-on is supported, and how Zephy staff access is restricted and reviewed.]

Audit trail

Every approval is recorded with the name of the staff member and the time. So are submissions and each follow-up with the payer. If a payer or an auditor asks who signed off on a request, the answer is on the request.

[NEEDS: Confirm which events are logged, how long logs are kept, and whether clinics can export them.]

Minimum necessary

HIPAA asks that a disclosure include only what is needed for its purpose. A packet contains what that payer requires for that request, and the reviewer sees exactly what will be sent before approving it.

[NEEDS: Which AI model providers or other subprocessors receive patient data, and confirmation that each is covered by a BAA and does not train on clinic data.]

Data retention

Your clinic's data is yours. We keep it to provide the service and return or delete it when you leave.

[NEEDS: Retention period for packets and logs, the deletion or export process at cancellation, and backup retention.]

Human approval is a security control

Zephy cannot send anything to a payer on its own. A member of your staff has to read the packet and approve it first. That keeps a person accountable for every disclosure of patient information, and it is the point at which mistakes get caught.

See the approval step in how Zephy works

Questions and reports

If you have a security question, or want to report a concern, write to us.

[NEEDS: Security contact email, and the process for reporting a suspected incident.]