EHR Integration
AI agents for Veradigm (Allscripts)
Caesar Health runs the administrative work around Veradigm (Allscripts) EHR: the phone, the fax line, intake, scheduling, follow-up and the revenue-cycle work. Results are written back into Veradigm, and it stays the system of record.
Your patient record
Your administrative workAPI and interface connections
Veradigm (Allscripts) stays your system of record.
About Veradigm (Allscripts)
Veradigm, formerly Allscripts, provides ambulatory EHR and health-data products used by independent and specialty practices.
Veradigm (Allscripts) has a long-standing ambulatory footprint across independent and specialty practices, alongside its data and payer businesses. Practices on Veradigm often carry a heavy manual administrative load that autonomous agents can absorb without changing the clinical system.
Which product is this page about?
Worth settling first, because the naming causes confusion.
Veradigm offers two EHRs today: Veradigm EHR and Practice Fusion. Alongside them sit Veradigm Practice Management, Veradigm ePrescribe and FollowMyHealth.
TouchWorks, Sunrise and Paragon are Altera Digital Health products, not Veradigm's. Veradigm's developer portal points to Altera for their endpoints.
This page covers Veradigm EHR, the ambulatory product carried forward from the Allscripts line, and Veradigm Practice Management.
Does Caesar write back into Veradigm, or does my staff re-key it?
It writes back. The route depends on your Veradigm API tier.
Veradigm's FHIR API is read-only, by Veradigm's own documentation. No vendor files a note, a diagnosis or an order into a Veradigm chart through FHIR.
API writes go through Unity, Veradigm's proprietary bidirectional API, which sits behind the paid Integrator tier of Veradigm Connect. So "can it write back through the API?" is partly a question about your Veradigm contract.
Where the API doesn't reach, Caesar's web agent works Veradigm's own screens as a named user, from workflows recorded for your practice.
| Capability | On Veradigm |
|---|---|
| Inbound and outbound calls, warm transfer to staff | Caesar's own telephony |
| Call recording, transcript, summary | In Caesar |
| SMS reminders, no-show follow-up, balance reminders | Caesar's own messaging |
| Inbound and outbound fax | Caesar's own fax line |
| Tasks, review queue, audit trail | In Caesar |
| Reading patients, appointments and clinical data | Veradigm FHIR API |
| Patient search, booking, rescheduling, cancellation, filing documents | Unity at the Integrator tier, or Caesar's web agent |
On athenahealth and ModMed Caesar writes structured notes through the vendor's API, and those pages name the endpoints.
How the Allscripts / Veradigm EHR data integration works
The program. Veradigm Connect, formerly the Allscripts Developer Program, at developer.veradigm.com. Two memberships: Open, free with a click-through agreement, with documentation and sandbox access to the read-only FHIR APIs; and Integrator, paid, adding the Unity API for read and write.
Auth. OAuth 2.0 with SMART App Launch and OpenID Connect. Backend applications authenticate with a JWT client assertion. There are three launch contexts: provider apps against Veradigm EHR credentials, patient apps against FollowMyHealth, and system or backend apps.
FHIR. R4, aligned to USCDI and US Core. Veradigm publishes a directory of production base URLs per client organization. Veradigm EHR is certified to §170.315(g)(10).
Onboarding. Register the app, declare purpose of use and scopes, test in the sandbox, then request production, where Veradigm Connect reviews and approves. Then the practice activates the app through its own License Management Portal. Developers can't license an application on a client's behalf. Budget for that step.
More on the mechanics: how the EMR integration layer works.
Veradigm ships an ambient scribe. Caesar works around the visit.
Veradigm Ambient Scribe is embedded in Veradigm EHR. It uses ambient listening and generative AI to capture the visit and turn it into the clinical note.
So a Veradigm practice has a scribe inside the chart already. Caesar's surface is the work around the visit:
- The calls that come in while everyone is in a room, and the ones after five.
- The faxed results and referrals that arrive as paper.
- The intake and insurance that should be done before the patient arrives.
- The follow-up and the recall nobody made.
Keep Veradigm. Keep its scribe. Caesar still has a full day's work. How Caesar compares to a scribe.
What your staff stops doing
| Today | With Caesar |
|---|---|
| Answering the phone through lunch and after hours | The phone agent answers every call, 24/7 |
| Taking messages that turn into callbacks | The agent handles the request on the call |
| Retyping faxed results and referrals | The Document Inbox reads, extracts, matches and routes them |
| Chasing intake forms and insurance cards | Intake is collected before the visit |
| Sending reminders and follow-ups by hand | Reminders, no-show follow-up and balance reminders go out by SMS, on a per-clinic cadence with quiet hours |
| Sorting voicemails to find what needs a clinician | Anything ambiguous becomes a task with full context |
| Calling down a cancellation list | Freed slots go to patients on the waitlist |
How Caesar Health connects to Veradigm (Allscripts)
Caesar Health uses Veradigm (Allscripts)’s modern FHIR and APIs where available, and the EMR Integration Layer covers everything else. Agents reach the workflows your teams run today — bidirectionally — with Veradigm (Allscripts) as 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 Veradigm (Allscripts)
All 14 agents read from and write back to Veradigm (Allscripts). 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 Veradigm (Allscripts).
Reads inbound faxes, classifies each one, and files it to the right chart in Veradigm (Allscripts).
Triages patient and provider email, drafts replies, and logs the thread against the patient in Veradigm (Allscripts).
Runs two-way patient texting — reminders, confirmations, and rescheduling — synced to the Veradigm (Allscripts) schedule.
Answers questions on your website and books visits straight into the Veradigm (Allscripts) schedule, 24/7.
Clinical
Patient Experience
Collects intake and insurance, verifies eligibility, and writes the new patient and visit into Veradigm (Allscripts).
Sends diagnosis- and medication-specific education based on the encounter recorded in Veradigm (Allscripts).
Optimizes scheduling, fills cancellations from the waitlist, and keeps the Veradigm (Allscripts) calendar full.
Revenue Cycle
Codes the encounter, scrubs the claim, and posts charges to Veradigm (Allscripts) for a clean first-pass submission.
Detects when a PA is required, pulls the clinical detail from Veradigm (Allscripts), submits it, and tracks it to approval.
Catches denials, finds the root cause, corrects the claim in Veradigm (Allscripts), and files the appeal.
Auto-posts EDI 835 remits and patient payments against the right claims in Veradigm (Allscripts), and flags underpayments.
Care Coordination
Reads Veradigm (Allscripts) 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 Veradigm (Allscripts).
Runs chronic-care and remote-monitoring check-ins and keeps the care plan and readings updated in Veradigm (Allscripts).
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
- Veradigm (Allscripts) remains the system of record
Veradigm (Allscripts) + Caesar Health — FAQ
Does Caesar Health replace Veradigm (Allscripts) EHR?+
No. Veradigm stays the EHR and the system of record. Caesar automates the phone, fax, intake and follow-up around it. No migration, no data conversion.
Can a note write back into Veradigm through the API?+
Not through FHIR, which Veradigm documents as read-only. API writes need Unity, behind the paid Integrator tier of Veradigm Connect. Without it, Caesar's web agent works Veradigm's screens as a named user.
Is this for Allscripts Professional, TouchWorks or Sunrise?+
Veradigm EHR and Practice Fusion are Veradigm's two EHRs today. TouchWorks, Sunrise and Paragon belong to Altera Digital Health.
How does Caesar connect to Veradigm?+
Telephony, SMS and fax run on Caesar's own infrastructure. API work goes through Veradigm Connect with OAuth 2.0 and SMART App Launch, using a JWT client assertion for backend access. The web agent covers the rest.
Do you integrate with Genesys?+
Genesys is a contact-center platform, not a Veradigm product. Caesar is the phone layer: you forward your existing line to it, with no number port.
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
- eClinicalWorks: the other large ambulatory installed base
- athenahealth: the deepest API write-back Caesar runs, and a reference for a bidirectional EHR API
- All EMR integrations · How the EMR integration layer works
- Agents: phone · Document Inbox · SMS · AI Scribe · patient intake
See Caesar Health run alongside Veradigm (Allscripts)
Book a live demo on your own Veradigm (Allscripts) workflows and watch the agents execute real administrative work end to end.
Veradigm (Allscripts) 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.