Beta — Core Patient/Appointment Data

CaseFlow + NextGen

FHIR R4 Patient Access API · OAuth 2.0 · USCDI v1

NextGen's FHIR R4 Patient Access API lets us pull patient demographics and appointment data securely via OAuth 2.0. We're currently in beta with core patient/appointment data working. Clinical notes integration is in development — we'll update this page when it's available. Setup is straightforward: you authorize CaseFlow in your NextGen Office admin panel, and we handle the rest. Most beta practices go live in under 30 minutes.

Join the NextGen beta → Get a setup walkthrough

What's synced — and what stays in NextGen

Synced to CaseFlow

✓ Patient demographics (name, phone, DOB)
✓ Appointment data and schedules
✓ Provider assignments
✓ Appointment cancellations
✓ Waitlist flag triggers

Not accessed / In development

✗ Clinical notes Pending
✗ PHI beyond messaging scope
✗ Billing records
✗ Clinical documentation
✗ E-prescribing data

Most beta practices go live in under 30 minutes

We handle the API connection — you just approve it in your NextGen Office admin panel. No middleware, no IT involvement required. After approval, CaseFlow immediately begins pulling scheduled appointments and sending automated SMS confirmations to surgical patients. Beta setup may require coordination with your NextGen administrator.

Security & Compliance

HIPAA BAA is signed before any connection is made. Data is encrypted at rest (AES-256) and in transit (TLS 1.3). Connection is established via OAuth 2.0 — no shared credentials.

✓

HIPAA BAA signed pre-connection

✓

AES-256 encryption at rest

✓

TLS 1.3 in transit

✓

View full security posture →

⚠️

Beta status — what this means in practice

Core patient/appointment data is working and stable. Clinical notes integration is in development and not yet available. We'll update this page when clinical notes are ready. Beta setup may take slightly longer as we coordinate with NextGen's platform team.

Frequently asked questions

Does this require IT involvement? +

For the beta, there may be some coordination with your NextGen administrator — especially if you need to confirm OAuth permissions are enabled. Most practices get through this in under an hour. We're actively working to make this self-serve.

Will staff see double appointments in NextGen? +

No. The integration is writeback-aware — when a patient confirms via SMS in CaseFlow, the status updates in NextGen without creating a duplicate appointment. Staff see the same single record they've always seen, now with real-time confirmation status.

Can we turn off the sync? +

Yes — instantly. You can pause or disconnect the integration from the CaseFlow dashboard at any time. No data is retained beyond what you've explicitly configured, and disconnection takes effect immediately.

Is beta stable enough for production use? +

The core patient/appointment data sync is stable and we've been running beta practices successfully. The main limitation is that clinical notes aren't yet available — if your workflow relies heavily on clinical notes data for patient communication, you may want to wait for that release. For practices primarily needing appointment confirmation SMS, the beta is production-ready.

When will clinical notes integration be available? +

We're actively developing clinical notes integration. There's no hard date yet — we'll update this page and notify beta participants when it's ready. If clinical notes are critical for your workflow, join the waitlist and we'll reach out personally.