ContactBook a callGet My Score
AnswerEvery call picked up, triaged, and routed — including the ones outside office hours.
ScheduleSlots filled, cancellations backfilled, and recalls that actually go out.
IntakeDemographics, insurance, consents and history captured before the visit, not at the window.
ProcessFaxes, referrals, records and prior auth — the paperwork nobody sees and everybody drowns in.
CollectCoverage verified before the visit and balances collected after it.
GrowThe digital front door: getting found, getting booked, and getting reviewed.
ContactStaff & OperationsFront Desk Score

Compliance

Compliance for AI Phone Coverage

HIPAA, PHIPA, PIPEDA, consent, and the documentation your auditor will ask for before you automate the phone.

Book a MedReception.ai demoSee pricing

Automating a medical phone line means a vendor handles PHI on your behalf. That triggers real obligations, and the time to understand them is before signature rather than during an audit.

These pages cover what to require contractually, how consent and recording rules differ by jurisdiction, and what evidence to keep on file.

Part of ProcessFaxes, referrals, records and prior auth — the paperwork nobody sees and everybody drowns in.See the whole pillar →

Compliance

HIPAA and an AI Front Desk

The baseline question every practice asks before automating the phone. An AI system that handles patient calls is handling PHI.

Compliance

The BAA: What to Require

The contract that makes PHI handling lawful. Without a signed BAA, sharing PHI with a vendor is itself a violation, regardless of how secure the vendor is technically..

Compliance

Call Recording and Consent

The rules differ by state, and getting them wrong is expensive. One-party and two-party consent states have different requirements, and a multi-state practice has to satisfy the strictest one it touches..

Compliance

PHI Handling and Redaction

What gets stored, for how long, and who can read it. Transcripts of medical calls are PHI.

Compliance

Access Controls and Audit Trails

Who touched which record, and can you prove it. An auditor will ask who accessed a given patient's call record and when.

Compliance

Breach Response Expectations

What happens, and how fast, if something goes wrong. Breach notification timelines are statutory.

Compliance

PHIPA and Ontario Practices

Ontario's health privacy statute and what it requires of a phone vendor. PHIPA imposes obligations distinct from HIPAA, including specific rules on custodianship and agent relationships..

Compliance

PIPEDA and Canadian Practices

The federal privacy baseline for Canadian practices outside provincial health statutes. PIPEDA governs commercial handling of personal information and applies alongside provincial health privacy law..

Compliance

Data Residency for Canadian Clinics

Where your patients' call data physically lives. Several provinces expect health information to remain in Canada, and some practices commit to it contractually regardless..

Compliance

Telling Patients They Are Talking to AI

Disclosure practice, and why it works better than concealment. Patients react badly to discovering they were deceived.

Compliance

Running a Vendor Risk Assessment

The diligence your compliance officer will ask for. Adding a vendor that touches PHI triggers a risk assessment.

Compliance

The Minimum Necessary Standard

Collect what the workflow requires and nothing more. Systems that hoover up every detail 'just in case' expand your breach surface without improving care..

Compliance

Emergency Calls and Liability

The single highest-stakes design decision in phone automation. If a caller describes a stroke, the system's behavior in the next ten seconds is what matters.

Compliance

Documentation Your Auditor Will Want

The evidence file to assemble before you are asked for it. Audits go badly when documentation is assembled reactively.