EHR integration
Designed around your system of record
Your EHR remains the system of record. Spark operates around it, coordinating the work required to move patients through the practice. Compatibility, API access, and writable scopes are confirmed during qualification.
Current integrations
EHR integration
Availity
Voice and messaging
Data flow
What may sync and where staff work
The integration method depends on the EHR and enabled APIs, using FHIR-based access where available. Qualified workflows include retries, sync logs, reconciliation, and escalation instead of silent failure.
Integration surfaces
- Provider, facility, and location mapping per clinic
- Appointment book, reschedule, and cancel when supported, with conflict checks
- Medication refill capture with RxNorm normalization and staff review
- Roster sync and patient matching with uncertain-match escalation
- Eligibility results from Availity written into the staff workflow
- Failed-sync visibility in staff settings and operations tools
- Per-clinic feature flags to pause voice bookings or EHR writes
Scheduling ownership
Where Spark scheduling is enabled, your EHR remains the authoritative calendar. During onboarding, we define which system owns each patient notification and prevent duplicate confirmations where the available integration supports that control.
Onboarding requirements
- A compatible EHR and approved API access for the integration environment
- Mapped providers, facilities, and appointment types
- Transfer numbers and escalation paths for voice
- Staff roles and dashboard invitations via Clerk
- Daily Spark-vs-EHR reconciliation for the first seven days post-launch