Skip to main content
Emma implements the same FHIR R4 resources and operations an EHR integration relies on in production. Use this reference to validate that integration end-to-end, ahead of a live health-system connection: match patients, check provider availability, book and manage appointments, and write clinical documentation back to the chart. This is Emma’s own reference EMR, shaped like Epic’s FHIR R4 API. It is not a connection to Epic. This covers:
  • Patient matching, Schedule and Slot availability search, Appointment booking and lifecycle, and clinical DocumentReference write-back.
  • A configuration endpoint to enable this environment for your clinic.
  • The live-call tools Emma’s voice agent uses mid-conversation for registration, intake, booking, and abandonment follow-up — useful to exercise directly against the same sandbox data.
All endpoints require an authenticated Emma dashboard session. There is no separate API key or OAuth flow, see Authentication. The Live-Call Tools pages use a separate x-vapi-secret header instead — see each of those pages for details.

​
Base URL

Your Emma contact will provide your instance’s real domain.

​
Who this is for

Clinic and tenant technical teams validating EHR interoperability ahead of a production connection.

​
Reference

Authentication

Bearer JWT authentication using your Emma dashboard session.

Patient Matching

POST /Patient/$match

Finding Availability

GET /Schedule and GET /Slot

Managing Appointments

Search, book, reschedule, and cancel appointments.

Clinical Documentation

POST /DocumentReference

Environment Setup

Enable this environment for your clinic.

Patient Journey Tools

The live-call tools behind new-patient registration and billing.

Patient Intake Tools

The live-call tools behind intake validation and submission.

EMR Scheduling Tools

The live-call tools behind patient verification and booking.

Abandonment Recovery Tools

The live-call tools behind abandoned-checkout follow-up.