Frequently asked questions
Clear answers before implementation.
Learn how we support clinic workflows, assess EMR integration planning, and keep staff review essential.
Product and teams
How Book Health works
What does Book Health do?
Book Health helps Canadian clinics organize referral intake, patient outreach, scheduling requests, and front-office calls. It prepares clear, reviewable work so staff can move faster while keeping clinical and operational decisions with the clinic.
Does Book Health replace front-desk staff?
No. Book Health is designed to reduce repetitive administrative work and help staff focus on patients, exceptions, and higher-value decisions. Your team defines the workflow, review points, and escalation rules.
Does Book Health automatically send every result into an EMR?
No. EMR connection and write-back availability is not universal. It depends on the clinic, system, workflow, and implementation requirements. Where a connection is not available or appropriate, Book Health can prepare organized outputs for staff review and follow-up.
EMR and integrations
Planning around clinic systems
Which EMRs is Book Health planning around?
Book Health's roadmap research includes systems used by Canadian clinics, such as OSCAR Pro, Accuro, TELUS PS Suite, PointClickCare, Meditech, Ava, Epic, and Cerner. Naming a system here supports integration planning and research; it does not indicate a live, verified, partnered, or generally available integration.
How do I know whether my clinic's EMR workflow can be supported?
We review the system you use, the queues and handoffs involved, available connection options, privacy requirements, and where staff need to remain in control. We confirm the implementation scope and availability with your clinic before deployment.
What does "integration planning" mean?
It means mapping how Book Health could fit around your existing tools, assessing available technical pathways, and defining a safe implementation plan. Planning is not the same as claiming that a production connection is already available.
Privacy and security
Responsible implementation
How is patient information protected?
Security, access controls, data handling, and staff responsibilities are reviewed as part of implementation. The exact safeguards and data flows are confirmed for the workflow being deployed rather than assumed across every system.
How does Book Health approach Canadian healthcare requirements?
Book Health is designed for Canadian clinic workflows and implementation requirements. During planning, we review privacy, residency, access, and operational considerations with the clinic so the proposed workflow can be evaluated clearly.
Can staff review work before anything moves forward?
Yes. Review steps, exception handling, and escalation paths are defined with your team. Book Health is built to prepare work for action while keeping staff oversight where the clinic requires it.
Getting started
From workflow to plan
What happens during a demo?
We walk through the front-office work slowing your team down, the systems involved, and the outcomes you want to improve. The goal is to identify a focused starting point, not to make a blanket integration promise.
What does onboarding involve?
Onboarding begins with workflow mapping. We document the queues, review steps, handoffs, and implementation requirements, then confirm what can be supported before a workflow is activated.
Can we start with one workflow?
Yes. Clinics can begin with a focused use case, define success and oversight requirements, and expand only after the first workflow is understood.
Have a clinic-specific question?