Spruce <> ModMed Integration: Syncing Demographic Information – Spruce Health

The Spruce <> ModMed integration connects Spruce with ModMed, a cloud-based electronic health record (EHR). When enabled, new patients added in ModMed automatically become Spruce contacts, and demographic updates sync between both systems. Contacts created directly in Spruce do not push back to ModMed. Setup requires an active ModMed account, a Spruce Communicator plan, and a Spruce administrator to start the connection, with the Spruce Support team completing the final step.

What's Included in the ModMed-Spruce Integration

Patient Record sync

One-time initial sync of existing ModMed patients into Spruce
New patients added in ModMed will automatically create Spruce contacts
Note: Creating contacts in Spruce will not automatically create patient records in ModMed
Ongoing sync of demographic and contact details between Spruce and ModMed

Updates from ModMed are checked for regularly rather than sent to Spruce the moment they happen, so a change made in ModMed generally appears in Spruce within about 15 minutes.

The Spruce-ModMed integration can only be managed through the Spruce web or desktop app.

While the mobile apps display all synced contacts and conversations, they do not show whether a Spruce contact is linked to a ModMed patient record.

Setting up Your Spruce-ModMed Integration

Before you can use the Spruce-ModMed integration, make sure you have the following:

An active ModMed account
A subscription to the Spruce Communicator Plan
An administrator on your Spruce account who can enable the integration
ModMed API credentials, which are a dedicated username and password created for the integration rather than a staff member's own login. You can request these from ModMed by following Step 1 below.

Step 1: Request the integration from ModMed

Complete ModMed's Integration Request form: https://synapsys.modmed.com/s/contactsupport
For Vendor Name, enter Spruce Health.
For Description, enter Integrate with Spruce Health.
Submit the form.

ModMed will process your request and activate the integration for your practice. They will then send you setup instructions for generating your ModMed API credentials (a username and password). Once you have your credentials, continue to Step 2.

Step 2: Connect ModMed in Spruce

In Spruce, navigate to Settings > Integrations & API > click Connect to ModMed on the ModMed row.
Enter the Username and Password for your ModMed API credentials.
Enter your Firm URL Prefix. This is the unique prefix in your ModMed URL. For example, if your ModMed URL is https://dermassoc.ema.md, your firm URL prefix is dermassoc. If you are not sure what yours is, ModMed can tell you.
Select Connect.

The ModMed row will change to Integration in Progress. At this point your part is done.

To finish the connection, Spruce needs an API key that only ModMed can issue. Our team will request this key from ModMed on your behalf and complete the setup.

We will message you in Team Spruce with questions we'll need answered to complete the activation. Once you respond, our team will follow up when the integration is enabled. If you need assistance with this process or have any questions, please contact Spruce Support.

Integration Preferences

When you submit your integration request, the Spruce support team will follow up with questions to verify your preferred preferences for the Spruce-ModMed integration:

Do you want demographic sync on? If enabled, any changes to the patient record in ModMed will be reflected in Spruce, and vice versa.
Do you want new patients added in ModMed to be created in Spruce automatically?

When demographic sync is turned on, any changes to the patient record in ModMed will be reflected in Spruce, and vice versa. When it is turned off, changes will not be synced. In both cases, an initial import of your patients will occur.

Tagging patients by provider is not currently available for the ModMed integration. You can still apply tags to contacts in Spruce yourself, and those tags are unaffected by the sync.

Initial Sync of Existing ModMed Patients with Spruce

If you already have existing patients in Spruce, the initial sync will attempt to match ModMed records to existing Spruce contacts based on demographic information (first name, last name, and date of birth). During this process, Spruce will check for duplicates using phone numbers and email addresses.

If you communicate with an unsaved phone number in Spruce that matches a phone number in a ModMed patient record, Spruce will automatically convert it into a saved contact linked to that ModMed record.
If multiple Spruce contacts share the same email or phone number, the corresponding ModMed record will not be linked.
If there's only one match, but the demographic details don't align, the ModMed record will not be linked to the Spruce contact.

You can manually link any Spruce contact to a ModMed patient at any time, if needed.

Manually Linking Patients to ModMed

If a Spruce contact is not linked to ModMed, you can manually establish the connection using the link to ModMed option on the Spruce contact profile. To do this, locate the contact in Spruce by using the search bar at the top and switching to the Contacts tab > select the contact > then select Link Contact to ModMed in the sidebar.

You can search for the ModMed patient by name or by their ModMed patient ID.

Once the link is established, refresh the page to see the contact update with the linked information, including any demographic details pulled from ModMed.

Frequently Asked Questions

How do I check the status of my integration?

In Spruce, go to Settings > Integrations & API and look at the ModMed row. Integration in Progress means we have your credentials and are still completing setup. Connected means the integration is live.

My credentials went through. Why isn't my integration enabled yet?

To connect to ModMed, Spruce also needs an API key that only ModMed can issue. Our support team requests that key from ModMed and finishes enabling the integration on our end. They will follow up in the Spruce Support thread in the app once it is complete.

How quickly do changes sync?

Spruce checks ModMed for updates regularly, so a change made in ModMed usually appears in Spruce within about 15 minutes rather than immediately. If you need a specific patient updated right away, you can resync that contact from their profile in Spruce.

Why is my integration not working as expected?

If you received confirmation from the Spruce Support team that your integration was enabled but it is not working as expected, the most common cause is that the ModMed username or password used for the integration has changed. If that password was rotated or the account was disabled, Spruce can no longer reach ModMed.

To resolve this, go to Settings > Integrations & API in Spruce and reconnect using your current ModMed credentials. If this does not resolve the issue, please contact Spruce Support.

Does Spruce integrate with ModMed?

Yes. The ModMed integration is available on the Communicator plan. It auto-syncs patients from ModMed into Spruce as contacts and keeps demographic data updated between both systems.

Will Spruce contacts I create show up automatically in ModMed?

No. The sync is one-way for new patient creation. New patients added in ModMed appear in Spruce, but contacts created directly in Spruce do not push back to ModMed.

Can I manually link a Spruce contact to a ModMed patient?

Yes. On the contact's Spruce profile, select Link Contact to ModMed in the sidebar. This is useful when automatic matching does not find a record, for example when demographic details do not exactly align.

Do messages and conversations sync to ModMed?

No. The ModMed integration syncs patient contacts and their demographic details only. Conversations, messages, and notes in Spruce are not written to the ModMed chart.

Can I use ModMed alongside another EHR integration?

No. Each Spruce account can have one EHR integration active at a time. If your account is already connected to another EHR, contact Spruce Support before setting up ModMed.

IN THIS ARTICLE