Zapier, Make, and patient information

Every connection into QR Rx carries a patient's name and a way to reach them. Under HIPAA, any company that handles that information on your behalf must sign a Business Associate Agreement with your clinic first. QR Rx signs one. Zapier does not.

Why QR Rx does not connect through Zapier

Zapier states in its own documentation that it does not sign a Business Associate Agreement and does not support HIPAA workloads, on any plan. A Zap that copies a completed appointment into QR Rx would pass the patient's name, phone, and procedure through Zapier's servers without that agreement. That is your clinic's exposure, not Zapier's, so QR Rx will not route patient information through it and does not publish Zapier recipes.

What works instead

• A direct connection from your booking system. Vagaro, Open Dental, and Mangomint send completed visits straight to QR Rx. Each has its own guide in this section.
• Your software's own webhook. If your system can send a webhook itself, paste the private QR Rx URL from Settings → Integrations → Another system. Nothing sits in between.
• CSV import. Export the day's completed visits and drop the file into the Patients tab. Each row becomes a draft for review.
• The patient intake page. Hand patients the clinic intake link on a QR card at checkout.

If your software only offers Zapier

Some systems, Aesthetic Record among them, publish no API and offer Zapier as their only outbound connection. QR Rx cannot connect those automatically today. Use CSV import or the intake page, and tell QR Rx which system you use. We ask vendors for a direct webhook or a partner integration, and the more clinics that name a system, the sooner it moves.

Other connection tools

A connection tool that will sign a Business Associate Agreement with your clinic, or one you run yourself inside your own systems, can be reviewed. Contact QR Rx support before sending patient information through it so we can confirm the agreement and the setup together.