Architecture
Spark is designed to connect through approved EHR APIs, using FHIR-based interfaces where available. Your EHR remains the authoritative clinical record. Exact read and write capabilities depend on the EHR, API access, and scopes confirmed during pilot qualification.
Onboarding sequence
- Confirm EHR compatibility, credentials, and approved scopes
- Map the organization, clinics, providers, locations, and appointment types
- Configure the voice agent, greetings, and transfer rules
- Invite staff and validate role-scoped dashboard access
- Enable qualified workflows behind per-clinic feature flags
- Run daily Spark-vs-EHR reconciliation for seven days
Where staff work
Calls appear in the Inbox. Refills, uncertain matches, and schedule changes appear in Requests with ownership and service targets. Integration health is visible under Settings → Integrations.
Reliability and rollback
Per-clinic flags can pause voice scheduling or EHR writes without redeploying. Failed syncs stay visible for staff review, and low-confidence matching escalates instead of acting.