ModMed and HubSpot Integtration

Develop, Build & Integrate APIs & Integrations
1

A client of ours that uses HubSpot recently adopted ModMed (Modernizing Medicine) EHR/PM, and they are moving their primary lead conversion point from a HubSpot Form to the ModMed Scheduler embedded on our website. They use HubSpot for all their ROI reporting, so accurate attribution is critical.

Because the ModMed Scheduler runs in an iFrame, we understand that standard HubSpot tracking won’t work and that a two-phase, API-based integration is required.

I am looking to confirm with anyone who has successfully implemented this integration:

Phase 1: Capturing the Source Data (The Bridge)

We believe we must run a custom script on our website before the ModMed Scheduler iFrame loads. This script must:

  1. Read the visitor’s HubSpot cookie (hubspotutk) and URL parameters (e.g., utm_source, gclid).
  2. Inject these values as hidden fields into the ModMed Scheduler form/booking process, ensuring they are saved in the new appointment/patient record in ModMed.

Q1: Can anyone confirm this is the necessary approach for the iFrame? Has ModMed provided native functionality to capture these source/UTM parameters, or did you have to rely on a custom script?

Phase 2: Sending the Conversion to HubSpot (The Push)

The conversion event (appointment booked) now lives in ModMed. We plan to use an iPaaS tool (like Zapier or a HIPAA-compliant alternative like Keragon) to monitor ModMed and push the conversion data back into HubSpot. The flow is:

  1. ModMed saves the appointment, including the hidden tracking fields.
  2. The Integration Tool calls the ModMed API to detect the new appointment.
  3. The Integration Tool extracts patient data AND the hidden source fields (including the hubspotutk).
  4. The Integration Tool uses the HubSpot API to create or update the contact, using the hubspotutk to ensure accurate attribution, and records a new Deal (the scheduled appointment).

Q2: ModMed API Pricing Confirmation When asking ModMed about enabling API access for this push, they quoted a cost of $25 per provider per month, citing “interoperability standards.” Has anyone else encountered this specific pricing structure, and is this cost accurate for enabling the API endpoints needed to read appointment and patient data? Any help or feedback would be appreciated.

2

Hi there, @Blink_Jared -
I’m going to tag in a few of our Community Champions here for some feedback, and will circle back to ensure you’re getting a response to this.
@SteveHTM, @TomM2, @ashleyidesign - any thoughts on how you might approach this?

3

Thank you.

4

Hi @Blink_Jared

Your proposed architecture is sound and aligns with industry best practices. Additionally, the API pricing you were quoted is consistent with what other organizations have experienced.
If you need any assistance with the HubSpot API integration or implementation, please feel free to reach out—we’d be happy to help and support you through the process.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.

Thanks!

5

Hi @Blink_Jared
Your approach is pretty much aligned with how these integrations are usually handled, especially with the scheduler running inside an IFrame.
What we did with a client is HubSpot tracking data needs to be captured before the handoff happens and then pushed back into HubSpot after the appointment is created to preserve attribution properly. and the API pricing that was mentioned is consistent with what we’ve heard from others using ModMed APIs as well.
We are also exploring something similar to HubSpot ↔ ModMed integration at HubXpert too. Will be really happy to share more.