Data residency
USA + Canada
USA infrastructure is ready. Canadian deployments keep patient data in Canada.
Protect patient data. Keep control.
Access controls, staff review, and clear data-handling responsibilities support your front office.
Book a demo →Book Health trust evidence
Our approach.
Clear data handling. Defined access. Staff oversight.
Privacy context
PHIPA + PIPEDA
We address HIPAA requirements for US deployments and PHIPA, PIPEDA, and applicable provincial requirements for Canadian deployments.
Human oversight
Required
People retain clinical decisions, sensitive actions, final approvals, and exception handling.
System of record
Your EMR
We work with the clinic's existing systems rather than replacing the clinic's clinical record.
How the workflow runs
Make security review part of workflow design.
Start with the specific use case and connected systems, then define controls and oversight.
Map systems and information
Document what the agent reads, processes, and returns.
Review controls
Evaluate encryption, access, routing, and human review requirements.
Operate with oversight
Keep exceptions, sensitive actions, and clinical decisions with authorized staff.
Where Book Health fits
Review the control that matters at each workflow boundary.
Know who can access information, what the agent can do, and when staff take over.
Inbound documents
Review receipt, processing, storage, matching, routing, and exception handling for clinical-administrative files.
Patient communication channels
Evaluate the information exposed through SMS, email, and voice workflows and how identity or uncertainty is handled.
EMR access and write-back
Define the scope of connected-system access and which actions require confirmation or staff review.
Operational administration
Clarify user access, role changes, audit needs, escalation, and the responsibilities retained by the healthcare organization.
Questions about Security
No. Keep your EMR. We handle the admin around it.
Continue exploring
Meet your AI front office