EHR Integration
AI agents for Nextech
Caesar Health runs the administrative work around Nextech: the phone, the fax line, intake, scheduling, follow-up and the revenue-cycle work. Results are written back into Nextech, and Nextech stays the system of record.
Your patient record
Your administrative workAPI and interface connections
Nextech stays your system of record.
About Nextech
Nextech is a specialty EHR and practice-management platform for ophthalmology, plastics/aesthetics, and dermatology.
Nextech is built for high-volume specialty practices — ophthalmology, plastics and aesthetics, and dermatology — where scheduling, imaging, and billing move fast. Autonomous agents that handle calls, intake, and the revenue cycle keep those practices full and paid without expanding the front desk.
What the Nextech API allows
This is the section people arrive looking for, so it goes first.
Nextech publishes two API families, both OAuth 2.0, both partner-gated:
| Select API | Practice+ API | |
|---|---|---|
| FHIR | STU3 and R4 | STU3 (3.0.1) |
| Base URL | select.nextech-api.com/api (STU3), /api/r4 | api.pm.nextech.com/api |
| Auth | OAuth2 resource owner credentials with refresh, one-hour tokens | OAuth2 client credentials through Microsoft Entra |
| Required header | nx-practice-id | — |
Two constraints decide what any integration can do on Nextech.
1. The documented write surface is small. Nextech's Getting Started documentation grants read access to demographics, appointments and clinical data, and write access to the appointment confirmed flag. There's no published endpoint that files a visit note into a Nextech chart.
2. There's a daily call cap. Nextech limits API use to 1,000 calls per day, per client, combined across every application the practice runs. Going over returns HTTP 429. A shared budget of a thousand calls a day rules out chatty polling. It's why a Nextech integration is designed, not switched on.
Access. Credentials come from your Nextech representative after a connection request. Nextech Select and NexCloud are certified to §170.315(g)(10), and Nextech publishes FHIR base URLs for its practices.
More on the mechanics: how the EMR integration layer works.
Does Caesar write back into Nextech, or does my staff re-key it?
It writes back, through the route each task allows.
| Capability | On Nextech |
|---|---|
| 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 | Nextech API, within the daily call budget |
| Confirming appointments | Nextech API |
| Patient search, booking, rescheduling, cancellation, filing documents | Caesar's web agent, working Nextech's screens as a named user |
The web agent is part of Caesar's EMR Integration Layer. It works from workflows recorded for your practice, and it doesn't spend your API budget.
On athenahealth and ModMed Caesar writes structured notes through the vendor's API, and those pages name the endpoints. The difference is the API.
Nextech ships Cora Scribe. Caesar works around the visit.
Cora Scribe is Nextech's ambient AI scribe, launched on 27 January 2026 as part of Nextech Cora. Nextech describes it as AI charting that creates structured documentation within the Nextech EHR, and contrasts it with "bolt-on, third-party scribes" because it's embedded in the EHR.
So a Nextech 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 Nextech. Keep Cora 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 Nextech
Caesar Health uses Nextech’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 Nextech 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 Nextech
All 14 agents read from and write back to Nextech. 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 Nextech.
Reads inbound faxes, classifies each one, and files it to the right chart in Nextech.
Triages patient and provider email, drafts replies, and logs the thread against the patient in Nextech.
Runs two-way patient texting — reminders, confirmations, and rescheduling — synced to the Nextech schedule.
Answers questions on your website and books visits straight into the Nextech schedule, 24/7.
Clinical
Patient Experience
Collects intake and insurance, verifies eligibility, and writes the new patient and visit into Nextech.
Sends diagnosis- and medication-specific education based on the encounter recorded in Nextech.
Optimizes scheduling, fills cancellations from the waitlist, and keeps the Nextech calendar full.
Revenue Cycle
Codes the encounter, scrubs the claim, and posts charges to Nextech for a clean first-pass submission.
Detects when a PA is required, pulls the clinical detail from Nextech, submits it, and tracks it to approval.
Catches denials, finds the root cause, corrects the claim in Nextech, and files the appeal.
Auto-posts EDI 835 remits and patient payments against the right claims in Nextech, and flags underpayments.
Care Coordination
Reads Nextech 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 Nextech.
Runs chronic-care and remote-monitoring check-ins and keeps the care plan and readings updated in Nextech.
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
- Nextech remains the system of record
Nextech + Caesar Health — FAQ
Does Caesar Health replace Nextech?+
No. Nextech stays the EHR and the system of record. Caesar automates the phone, fax, intake and follow-up around it. No migration, no data conversion.
Is there an AI scribe for Nextech?+
Cora Scribe is Nextech's own, built into the EHR. Caesar runs the operations around the visit and sits alongside whatever documents your encounters.
Can anything write a clinical note into Nextech through the API?+
Not through the documented API. Nextech's documented write access is the appointment confirmed flag. Caesar confirms appointments through the API and uses its web agent for other work in Nextech.
How does Caesar connect to Nextech?+
Telephony, SMS and fax run on Caesar's own infrastructure. Reads and confirmations use the Select or Practice+ APIs over OAuth 2.0, inside Nextech's 1,000-calls-per-day limit. Other chart work runs through the web agent as a named Nextech user.
Do we need Nextech's permission?+
Yes. Nextech API credentials come from your Nextech representative after a connection request. They're 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
- ModMed: the specialty comparison, with an API that accepts a third-party note
- Tebra: the practice-management alternative for independent specialty practices
- All EMR integrations · How the EMR integration layer works
- Agents: phone · Document Inbox · SMS · AI Scribe · patient intake
See Caesar Health run alongside Nextech
Book a live demo on your own Nextech workflows and watch the agents execute real administrative work end to end.
Nextech 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.