eClinicalWorks
eClinicalWorks is a cloud-based EHR and practice-management platform serving more than 180,000 physicians and 850,000 medical professionals. Its API surface is standards-based rather than proprietary: FHIR R4 served by the eCW FHIR Facade behind SMART on FHIR and OAuth 2.0, split across a provider-facing facade (fhir4.eclinicalworks.com) and a patient-facing healow facade (fhir4.healow.com), each tenant-scoped by a six-character practice code. eClinicalWorks publishes no OpenAPI; the machine-readable contract is the FHIR CapabilityStatement at each tenant's /metadata plus the SMART configuration at /.well-known/smart-configuration, which advertises 486 scopes. Capabilities include SMART EHR Launch and Standalone Launch, Backend Services with Group/$export bulk data, CDS Hooks, a documented writeback catalogue, patient-facing healow Clinical and Scheduling APIs, and a bidirectional healow RPM Vendor (Tracker) API for remote-monitoring device orders and observations. APIs are certified to the ONC 45 CFR 170.315(g)(10) Standardized API for Patient and Population Services criterion.
eClinicalWorks publishes 3 APIs on the APIs.io network. Tagged areas include EHR, FHIR, Healthcare, Electronic Health Records, and Practice Management.
The eClinicalWorks catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 JSON-LD context.
eClinicalWorks’ developer surface includes documentation, engineering blog, pricing, API reference, getting-started guide, support, signup flow, and 31 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
eClinicalWorks FHIR API
Provider-centric, backend and bulk FHIR R4 APIs for integrating with the eClinicalWorks EHR. Supports SMART on FHIR EHR Launch, Standalone Launch, Backend Services (private_key_...
healow Patient-Centric FHIR API
Patient-facing FHIR R4 APIs accessible through the healow developer portal, letting third-party applications connect to the healow network for clinical data and scheduling. Serv...
healow RPM Vendor (Tracker) API
Bidirectional FHIR R4 API for remote-patient-monitoring device vendors. healow sends signed device orders to a vendor-hosted endpoint (POST create, DELETE cancel within a 60-min...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
eClinicalWorks MCP Server
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Eclinicalworks Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Eclinicalworks Finops
FINOPSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Eclinicalworks Context
JSON-LDSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type