applaud
← Check another system

Modernizing Medicine, Inc. (ModMed)

Can applaud connect to Modernizing Medicine (ModMed)?

YesReady: automatic connection

How it connects

Best way

Connects automatically

Modernizing Medicine (ModMed) sends each visit to applaud as it happens. Nothing for your team to do day to day.

Certified FHIR R4 API ((g)(10)): Bulk FHIR app the practice's Admin consents to; read finished Encounters and their Patients

Connects automatically: Modernizing Medicine (ModMed)

  1. applaud registers once as a Certified FHIR API vendor in ModMed's FHIR Vendor Dashboard (linked from the portal's registration page) and creates a Bulk FHIR app: no per-user sign-in, a signing key (ES384 private-key JWT) and system scopes for Patient and Encounter only. New apps are created Disabled and ModMed reviews and enables them daily. Read the Certified FHIR API Terms of Use before registering: that page was blocked to automated reading on 2026-10-01.
  2. The practice signs applaud's BAA, then its Admin adds applaud's ClientId under Admin > Manage Bulk FHIR, once. Each practice's FHIR base URL is in ModMed's public endpoint directory.
  3. Daily, applaud reads the practice's finished visits with Encounter?status=finished&date=ge<yesterday> (Encounter search by date, status and patient is in the live CapabilityStatement; whether the patient parameter is mandatory is unconfirmed), then reads each Patient for given name, family name and Patient.telecom. Alternative: POST {fhir-base}/$export?_type=Patient,Encounter&_since=<last run>, poll the Content-Location status URL and download the NDJSON; types outside the app's scopes are skipped.
  4. applaud keeps finished visits, takes the first name and a mobile number and POSTs them with the visit date to https://applaud.you/api/v1/contacts. Everything else in the Patient and Encounter resources (an Encounter can carry reason and diagnosis fields) is discarded on receipt.
  5. Caveats: there is no public sandbox (production only), no webhook, and Patient.telecom may not say which number is a mobile, so check before texting. Confirm with ModMed that an app limited to Patient and Encounter scopes is enabled.

Resources

Other ways, in order

Option 2

Connects by export

Recent patients are exported from Modernizing Medicine (ModMed) and uploaded to applaud. A couple of minutes, and we can set it up with you.

Practice staff export completed visits, or an applaud user seat (report export not publicly documented; the full EHI export is not suitable)

Connects by export: Modernizing Medicine (ModMed)

  1. The practice signs applaud's BAA.
  2. Ask the practice's ModMed administrator whether a report of completed appointments with first name and mobile number (no notes) can be exported to CSV from EMA or ModMed Practice Management, and which user role may run it. ModMed's help centre (ModMed Central) is login-only, so none of this could be read.
  3. If it can, the practice either uploads the file to applaud daily or creates a named applaud user with only the access that report needs and multi-factor login switched on (an authenticator app, no extra fee).
  4. Don't use the EHI export: ModMed says the population export is started by a support case and is the whole chart in CSV, so it carries clinical data.

Resources

Option 3

Connects through a partner tool

A connector tool links Modernizing Medicine (ModMed) to applaud.

NexHealth Synchronizer API (ModMed, all cloud): appointment webhook to applaud

Connects through a partner tool: Modernizing Medicine (ModMed)

  1. The practice becomes a NexHealth customer and applaud creates a NexHealth Developer Portal account so the practice shows up as an institution it can call. NexHealth installs its Synchronizer for ModMed using the practice's ModMed login URL, its locations and two ModMed user accounts (a Clinical user and a Management administrator user).
  2. applaud registers an HTTPS webhook endpoint with NexHealth and subscribes to appointment_created and appointment_updated for that institution.
  3. When an appointment is updated to completed, applaud fetches the patient record and posts first name and mobile to https://applaud.you/api/v1/contacts.
  4. Unconfirmed: NexHealth's example payload carries patient_id, start and end times, confirmed, cancelled and check-in time, so how a completed visit shows, and whether the patient record returns a mobile number for ModMed, still has to be tested. Pricing is not in the docs opened.

Resources

Questions about connecting Modernizing Medicine (ModMed)? We set it up with every new practice.

Ask us about your system

Tell us where to reach you and we'll come back with how applaud connects.

Book a demo