Security
How MedReception handles patient calls and privacy: a BAA for every client, Canadian and Australian privacy laws, and AI that routes but never decides.
By MedReception AI, physician-built by Paul Toomey, MDPublished
MedReception is HIPAA compliant, verified by Compliancy Group, and signs a BAA. The BAA is available to every client, so your privacy officer has a signed agreement in place before patient calls begin.
Canadian practices are supported under PIPEDA and PHIPA. Australian practices are supported under the Privacy Act and the Australian Privacy Principles (APP). Practices in the US are covered by the BAA.
The AI routes and escalates calls. Clinicians make every clinical decision. For refills, where your EHR supports it, including eClinicalWorks, a pending refill is prepared for the prescriber to sign. Otherwise the request goes to the provider as a message.
Katie captures intake during the call and routes it by provider, urgency and triage. On the named EHR integrations, appointment bookings and new patient records with name, DOB and phone go into the EHR. Insurance information, photo ID and clinical content such as history, allergies, medications, symptoms and chief complaint do not write to the EHR. They arrive as a structured, EMR-pasteable summary that staff review and file, so details stay out of sticky notes and personal inboxes. Victoria produces the same kind of summary from voicemail.
MedReception is custom-built for each client rather than plug-and-play. Your routing, urgency rules and escalation contacts are set up to match how your practice handles calls and patient information.
Bookings and demographics go to the EHR
On the named integrations, including name, DOB and phone
Insurance, ID and clinical details are filed by staff
Returned as a structured summary for review
Routes and escalates only
Clinicians make every clinical decision
Prescriptions stay with the prescriber
Pending refills for signature, or a message to the provider
Yes. A BAA is available to all clients. Your practice can review it as part of the demo and onboarding process, before calls go live.
For Canadian practices, MedReception addresses PIPEDA and PHIPA. For Australian practices, it addresses the Privacy Act and the Australian Privacy Principles (APP). A BAA is available to all clients in every country we serve.
Katie captures intake on the call and routes it by provider, urgency and triage. For the named EHR integrations, appointment bookings and new patients, with name, DOB and phone, go into the EHR. Insurance information, photo ID and clinical details such as history, allergies, medications, symptoms and chief complaint do not write to the EHR; they come back as a structured, EMR-pasteable summary for staff to review and file. Victoria turns voicemail into a similar summary.
MedReception integrates with athenahealth, eClinicalWorks, Elation, Cerbo, Hint, Tebra, ModMed, Practice Fusion, Jane, Office Ally, SimplePractice, TherapyNotes, Accuro, pMD, PS Suite, Nextech, ChARM, Amazing Charts, Azalea Health, Eye Cloud Pro and HealthQuest. On those, bookings and new patient demographics go into the EHR. For an EHR outside that list, such as MEDITECH, OSCAR, Valant or WebPT, we do not integrate today; Katie still answers every call, handles intake and sends booking requests that staff enter. Want MedReception integrated with your EHR? We build custom EHR integrations; book a demo and we will scope yours.
No. MedReception never approves, denies or changes a prescription. Where your EHR supports it, including eClinicalWorks, it prepares a pending refill for the prescriber to sign. Otherwise it sends the request to the provider as a message.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
Want the numbers first? See plans and pricing