Compliance
Compliance with Practice Fusion: bookings and demographics write into the EMR; insurance, ID and clinical details go to staff as a summary. BAA available.
By MedReception AI, physician-built by Paul Toomey, MDPublished
MedReception is HIPAA compliant, verified by Compliancy Group, and signs a BAA, which is available to all clients. Bring your compliance lead to the demo and review the agreement before go live. If you practice in Canada, MedReception supports PIPEDA and PHIPA, and in Australia it supports the Privacy Act and the Australian Privacy Principles.
Appointment bookings are written into Practice Fusion, and new patients are created there with name, date of birth and phone number. Insurance details, photo ID and all clinical content, such as medical history, allergies, medications, symptoms and chief complaint, are not written back. They are captured on the call or uploaded in the portal, then returned as a structured, EMR-pasteable summary that your staff review and file themselves.
Katie answers right away and finds out why the patient is calling. A new patient gives their name, date of birth and phone number, and Sallie books the visit. After hours, Annie takes the call, and Victoria turns any voicemail into a summary. Staff come in to a booked appointment and a summary of whatever needs a human check.
MedReception makes no clinical decisions and never approves, denies or changes a prescription. Calls are routed and escalated by provider, urgency and triage. Refill requests go to the provider as a message, or, where the EHR supports it, a pending refill is prepared for the prescriber to sign.
MedReception is independent of any one EMR. If you change EMRs later, you keep your AI and its setup rather than starting over. Launch takes about a week from signup.
Bookings and demographics write in
Appointments, new patients, name, DOB and phone go into Practice Fusion
Staff review sensitive details
Insurance, photo ID and clinical content come as a summary to file, not a chart write
Clinicians decide
The AI routes and escalates, and never makes clinical decisions
Yes. A BAA is available to all clients, and you can review it during your demo before go live. For Canadian practices MedReception supports PIPEDA and PHIPA, and for Australian practices the Privacy Act and the Australian Privacy Principles. Sensitive details such as insurance, ID and clinical content are returned for staff review rather than written into the chart.
Appointment bookings, new patient creation and demographics (name, date of birth and phone number) are written into Practice Fusion. Insurance information, photo ID and clinical content such as medical history, allergies, medications, symptoms and questionnaires are not. Those are captured on the call or uploaded in the portal and come back as a structured, EMR-pasteable summary for your staff to review and file.
No. The AI routes and escalates, and clinicians decide. It never approves, denies or changes a prescription. A refill request goes to the provider as a message, or is prepared as a pending refill for the prescriber to sign where the EHR supports it.
Launch takes about a week from signup. The EHR connection and your practice phone number are ready in 1 to 3 days, and registering the number for patient texting takes about 5 business days. Setup is free, and billing is month to month to start, cancelled with 30 days' written notice.
MedReception is independent of any one EMR, so you keep your AI when you change systems. If your new EMR is on our integration list, we reconnect it. If it is not, Katie still answers every call, handles intake and sends booking requests for staff to enter. Want MedReception integrated with your new EMR? We build custom EHR integrations; book a demo and we will scope yours.
Related Topic
HIPAA and compliance
Full guide to MedReception compliance and data security standards
Related Integration
AI receptionist for Practice Fusion
Complete integration guide and Practice Fusion setup
Related Topic
EMR and EHR integrations
Full list of EMR integrations and data security practices
Related
Virtual receptionist that protects patient data
Healthcare-only AI receptionist: bookings and demographics write to connected EHRs, while insurance, ID and clinical content return as a summary for…
Related
Dental AI Receptionist: Phone Workflow and Data Security
Dental AI receptionist for new patient calls, urgent toothache routing, insurance capture and recalls, with clear rules on what writes to your EMR.
Related
AI Receptionist Data Security and Patient Privacy
How MedReception handles patient calls and privacy: a BAA for every client, Canadian and Australian privacy laws, and AI that routes but never…
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