EHR Integration
AI agents for ModMed
Caesar Health runs the administrative work around ModMed: the phone, the fax line, intake, scheduling, follow-up and the revenue-cycle work. Results are written back through ModMed’s own API, and EMA stays the system of record.
Your patient record
Your administrative workAPI connection
ModMed stays your system of record.
About ModMed
ModMed (Modernizing Medicine) is a specialty-focused EHR and practice-management platform, strong in dermatology, ophthalmology, orthopedics, and more.
ModMed’s EMA and gGastro systems are built around specialty workflows — dermatology, ophthalmology, orthopedics, plastics, and GI — where documentation and coding are highly specialized. Caesar Health is an official ModMed marketplace partner, so the agents slot into those specialty workflows rather than working around them.
Does Caesar write back into ModMed, or does my staff re-key it?
It writes back. Nothing lands in the chart without a person accepting it.
The note. ModMed built a supported path for this. Its API documentation describes sending transcribed or textual content into an unfinalized visit note or as a standalone chart note. It's a road ModMed paved, not a workaround.
Caesar posts the visit note as a FHIR Composition against the encounter, typed as a LOINC 11488-4 consult note in preliminary status. A firm administrator turns on "Enable Transcription Status" to allow it. If the provider marks the encounter held for transcription, the text lands in the visit note; otherwise it becomes a new chart note. Either way the physician reviews and edits before anything is incorporated.
Sections map to their LOINC codes, so the note arrives structured, not as one block:
| Section | LOINC |
|---|---|
| Chief complaint | 10154-3 |
| History of present illness | 10164-2 |
| Review of systems | 10187-3 |
| Physical findings | 29545-1 |
| Evaluation note | 51848-0 |
Documents. Generated PDFs, such as requisitions, summaries or an inbound fax matched to a patient, upload to the patient's chart through ModMed's Binary then DocumentReference sequence.
Scheduling. Slot search, booking, rescheduling, cancellation and confirmation run against ModMed's Appointment and Slot resources. The phone agent books into real availability, not a mirrored calendar.
What stays in EMA: ModMed's procedure and treatment-plan forms, the ones that drive CPT and ICD generation for billing. ModMed doesn't expose them through its API, so no third party can fill them. Your physicians keep completing them in EMA.
How the ModMed integration works
ModMed has two APIs, and the difference decides whether anything can write to your chart.
1. The Certified FHIR API. Free, self-service registration, FHIR R4, OAuth 2.0 with SMART App Launch. ModMed documents it as read and search only. Anything built only on it can look at your chart and can't put anything in it.
2. The EMA Proprietary API. This is the one with write access, and the one Caesar runs on. ModMed documents read, search, create and update on it. Access is partner-gated through ModMed's synapSYS program. Caesar Health is listed in the synapSYS Marketplace.
Auth. OAuth2 tokens against ModMed's token endpoint, with an API key issued for your practice and a firm URL prefix that identifies it on every call. You control the key and can revoke it.
Documentation. ModMed's developer portal is at portal.api.modmed.com. Certified FHIR base URLs for every practice are published, each on its own subdomain.
What the proprietary API exposes to Caesar, and what it doesn't:
| Capability | Read | Write | Notes |
|---|---|---|---|
| Patient | Yes | Yes | Search, create, update |
| Appointment and slot | Yes | Yes | Book, reschedule, cancel, confirm |
| Practitioner, location, appointment types and reasons | Yes | — | Reference data |
| Coverage | Yes | — | Insurance on file |
| DocumentReference | Yes | Yes | Via Binary upload first |
| Composition (visit note) | — | Yes | preliminary status |
| ServiceRequest (orders) | Yes | No | Orders can't be placed by API |
| Procedure | Yes | No | |
| Encounter | Yes | No | Caesar attaches to an existing encounter |
The three read-only rows are the boundary of any ModMed integration, ours included. A technical buyer finds them in week one of a pilot anyway.
More on the mechanics: how the EMR integration layer works.
ModMed ships ModMed Scribe 2.0. Caesar works around the visit.
ModMed Scribe 2.0 is ModMed's ambient documentation product, built into EMA. It listens to the visit and suggests note content and ICD-10 codes in near real time. Because it's inside the EHR, it reaches fields a third-party API can't.
So Caesar doesn't sell a competing scribe on ModMed. Its surface is the work around the visit:
- The call at 4:50 pm that nobody answered.
- The pathology result that arrived by fax and sat in a queue.
- The intake that should have happened before the patient sat down.
- The recall nobody made.
Keep EMA. Keep ModMed Scribe 2.0. Caesar still has a full day's work.
Caesar also includes ambient documentation for practices that want one system across phone, fax and the room: see the AI Scribe and clinical documentation. On ModMed it writes through the same Composition path. How Caesar compares to a scribe.
Where Klara fits
ModMed sells Klara as ModMed Patient Engagement. If you're on ModMed, patient messaging may already be in your stack.
Klara's published phone features move a caller into a text thread and transcribe voicemails into the patient conversation. Caesar's phone agent answers the call, holds the conversation, searches real ModMed availability and books the appointment. Practices running both keep staff messaging where it is and put Caesar on the line. Klara and Weave alternatives for ModMed.
What your staff stops doing
| Today | With Caesar |
|---|---|
| Answering the phone through lunch and after hours | The phone agent answers every call, 24/7 |
| Reading availability off the EMA schedule to a caller | Slot search runs against ModMed's live Slot data |
| Retyping a faxed pathology report into the chart | The Document Inbox reads, extracts, matches and files it |
| Calling patients back about a form they didn't fill | Intake is collected before the visit |
| Sending reminder and follow-up texts by hand | Reminders, no-show follow-up and balance reminders go out by SMS, on a per-clinic cadence with quiet hours |
| Typing the visit note into EMA from a transcript | The note posts as a Composition for review |
| Sorting which messages need a clinician | Anything ambiguous becomes a task with the context attached |
How Caesar Health connects to ModMed
ModMed is API-forward, so Caesar Health connects through its FHIR and API surface — reading patient, scheduling, and billing context and writing every result back. ModMed stays the system of record. No rip-and-replace, no migration — the agents run alongside the system your clinicians already use.
FHIR API
Modern, standards-based read/write where the EMR exposes FHIR.
HL7 v2 messaging
The interface standard most EMRs already speak for orders, results, and ADT.
Direct database
Secure direct access where APIs don’t reach the data.
Interface-level layer
For legacy or no-API systems — connects at the screen level, no vendor cooperation required.
Every Caesar Health agent, on ModMed
All 14 agents read from and write back to ModMed. Here’s what each one does inside your workflow, with the Revenue Cycle agent broken out by function.
Communication
Answers and places patient calls and books, reschedules, and cancels appointments directly in ModMed.
Reads inbound faxes, classifies each one, and files it to the right chart in ModMed.
Triages patient and provider email, drafts replies, and logs the thread against the patient in ModMed.
Runs two-way patient texting — reminders, confirmations, and rescheduling — synced to the ModMed schedule.
Answers questions on your website and books visits straight into the ModMed schedule, 24/7.
Clinical
Patient Experience
Collects intake and insurance, verifies eligibility, and writes the new patient and visit into ModMed.
Sends diagnosis- and medication-specific education based on the encounter recorded in ModMed.
Optimizes scheduling, fills cancellations from the waitlist, and keeps the ModMed calendar full.
Revenue Cycle
Codes the encounter, scrubs the claim, and posts charges to ModMed for a clean first-pass submission.
Detects when a PA is required, pulls the clinical detail from ModMed, submits it, and tracks it to approval.
Catches denials, finds the root cause, corrects the claim in ModMed, and files the appeal.
Auto-posts EDI 835 remits and patient payments against the right claims in ModMed, and flags underpayments.
Care Coordination
Reads ModMed data to find open quality-measure gaps and runs the outreach to close them.
Sends and tracks referrals end to end and closes the loop with results back in ModMed.
Runs chronic-care and remote-monitoring check-ins and keeps the care plan and readings updated in ModMed.
Built for healthcare
- HIPAA-compliant, BAA available
- SOC 2 Type II in progress
- End-to-end encryption, in transit and at rest
- Full audit log of every AI action
- Human-in-the-loop review where you want it
- ModMed remains the system of record
ModMed + Caesar Health — FAQ
Does Caesar Health replace ModMed?+
No. ModMed stays the EHR and the system of record. Caesar runs the administrative work around it and writes results back through ModMed's API. No migration, no data conversion.
Does the note write back into ModMed automatically?+
It posts automatically; it doesn't file automatically. Caesar sends the note as a FHIR Composition in preliminary status, and it appears in EMA for the physician to review and accept.
We already use ModMed Scribe 2.0. Why would we add Caesar?+
A scribe documents the visit. Caesar answers the phone, works inbound fax, runs intake, books appointments and handles follow-up, the work before and after the room. Keep ModMed Scribe; the two do different jobs.
How does Caesar connect to ModMed?+
Through ModMed's EMA Proprietary API, the one with write access, using an API key and firm URL prefix issued for your practice. Caesar reads and writes Patient, Appointment, Slot and DocumentReference, reads Coverage, and writes the visit note as a Composition. ModMed's free Certified FHIR API is read and search only.
Is Caesar Health a ModMed partner?+
Yes. Caesar Health is listed in ModMed's synapSYS Marketplace. Your practice's API key and firm prefix are issued against your practice and you can revoke them.
Is it HIPAA compliant?+
Yes. Caesar signs a BAA. PHI is encrypted in transit and at rest with customer-managed keys, access is role-based with tenant isolation per organization and location, and access to PHI is logged. SOC 2 Type II is in progress.
Related
- Nextech and eClinicalWorks: the other platforms specialty practices weigh against ModMed
- athenahealth: the deepest write-back surface Caesar runs, and a reference for what an EHR API can expose
- All EMR integrations · How the EMR integration layer works
- Agents: phone · Document Inbox · SMS · AI Scribe · patient intake
See Caesar Health run alongside ModMed
Book a live demo on your own ModMed workflows and watch the agents execute real administrative work end to end.
ModMed and all other product names, logos, and brands are trademarks of their respective owners, shown here to indicate compatibility. Their use does not imply endorsement or an official partnership unless explicitly stated.