eClinicalWorks is a cloud-based EHR and practice management platform serving ambulatory practices, FQHCs, hospitals, and specialty clinics, with integrated revenue cycle management, patient engagement through healow, and AI documentation via Sunoh.ai. With an unofficial API, you can sync patients and providers, manage appointments and telehealth visits, retrieve clinical notes and prescriptions, submit and reconcile claims, and orchestrate value-based care workflows without living inside the eClinicalWorks portal.

eClinicalWorks is a cloud-based EHR and practice management platform used by ambulatory practices, hospitals, FQHCs, and specialty clinics across dental, vision, behavioral health, ambulatory surgery centers, and urgent care. The platform combines clinical documentation, scheduling, e-prescribing, labs, telehealth, billing and revenue cycle management, patient engagement through the healow suite, interoperability, and AI assistance via Sunoh.ai (medical scribe), Eva (virtual assistant), and healow Genie (AI contact center).
Core product areas include:
Common data entities:
Practices and health systems rely on eClinicalWorks daily, but turning portal-based clinical, scheduling, and billing workflows into automated pipelines is hard:
Supergood reverse-engineers authenticated browser flows, batch interfaces, and network interactions to deliver a resilient API endpoint layer for your practice or RCM operations.
Use eClinicalWorks with AI agents: eClinicalWorks MCP Server →
Book a 30-minute session to confirm your eClinicalWorks module mix, specialty editions, licensing, and authentication model.
We deliver a hardened eClinicalWorks adapter tailored to your workflows and entitlements.
Go live with continuous monitoring and automatic adjustments as eClinicalWorks evolves.
Authentication
/authenticateAuthenticate against eClinicalWorks or healow with username/password, SSO, and MFA (SMS, email, TOTP); returns a managed session for downstream calls.
Patients
/patientsRetrieve patient demographics, identifiers, and facility/location associations across multi-site tenants and specialty editions.
Scheduling
/appointmentsList in-person and healow telehealth appointments with provider, location, status, and visit-type metadata.
Scheduling
/create_appointmentCreate new appointments respecting provider templates, facility rules, and healow self-scheduling configuration.
Clinical
/encountersPull encounter records, progress notes, and Sunoh.ai-generated draft documentation with sign/lock state.
Billing
/eligibilityRun real-time payer eligibility checks for scheduled or arriving patients.
Billing
/submit_claimSubmit 837P/I claims through the clearinghouse path, with reconciliation hooks for 835 ERAs and payment posting.
Mirror eClinicalWorks patient demographics, provider rosters, and facility/location records into your CRM, data warehouse, or analytics layer in near real time across multi-site tenants and specialty editions.
Programmatically pull encounters, progress notes, and Sunoh.ai-generated draft documentation, route them through downstream review or coding pipelines, and re-post sign/lock actions with the required audit trail.
Drive self-scheduling, digital check-in, telehealth visit creation, secure messaging, and Messenger Campaigns from your own front-end or outreach stack while keeping eClinicalWorks as the system of record.
Run eligibility checks, submit 837P/I claims, retrieve 835 ERAs, reconcile patient payments, and surface KPI data from the RCM Service into your finance dashboards without manual portal work.
Authentication
Username/password, SSO, and MFA (SMS, email, TOTP) across eClinicalWorks and healow; respects role-based permissions and enterprise audit controls
Connectivity
Web portal access with partner API gates; partial FHIR coverage plus HL7 v2 and X12 (837/835) clearinghouse and ERA flows for claims and remittances
Response format
JSON normalized by the Supergood adapter across EHR, healow, and RCM surfaces
Rate limits
Tenant- and module-dependent; managed by the Supergood adapter to stay within eClinicalWorks and healow thresholds
Session management
Automated refresh, MFA challenge handling, and change detection across eClinicalWorks and healow modules
Data freshness
Near real-time on patients, scheduling, encounters, and eligibility; batch cadence on 837/835 claim and ERA flows
Security
HIPAA-aligned handling with TLS in transit, encrypted credential storage, RBAC, and audit-trail preservation on sign/lock and amendments
Webhooks
Not natively exposed; Supergood emits change events via polling and diffing across patient, scheduling, encounter, and claim objects
Latency
Sub-second on read paths for patients, appointments, and eligibility; minutes on claim submission and ERA reconciliation
Throughput
Concurrency tuned per tenant and module entitlement; horizontal scale across multi-site facilities and specialty editions
Reliability
Continuous monitoring with automatic retries, idempotent claim and appointment writes, and managed failover as eClinicalWorks evolves
Adaptation
Adapter tracks eClinicalWorks, healow, Sunoh.ai, and RCM Service UI and interface changes; updates ship without customer code changes
The adapter supports both. For in-house billing, we expose eligibility, claim submission, ERA retrieval, and payment posting endpoints directly. For customers on the eClinicalWorks RCM Service, we surface KPI dashboards, claim status, and reconciliation data while respecting the managed workflow boundaries set by the RCM team.
Yes. healow self-scheduling, digital check-in, telehealth, secure messaging, and Messenger Campaigns are accessible through the same adapter, with session continuity maintained across the eClinicalWorks and healow surfaces.
Yes. We tailor the adapter to each tenant's specialty editions and module entitlements (dental, vision, behavioral health, ASC, urgent care) since schemas and available workflows differ across the same tenant.
Sunoh.ai draft documentation is retrieved alongside encounter and progress note data. Sign/lock actions, amendments with reason codes, and re-signing flows are all handled through the adapter so audit trails stay intact.
The adapter handles username/password, SSO, and MFA (SMS, email, TOTP) securely, maintains session continuity with automated refresh, and respects role-based permissions and audit controls so headless automation does not bypass your security posture.