EHR or medical practice management
eClinicalWorks
eClinicalWorks is listed here as an electronic health record or medical practice management system.
eClinicalWorks sells a cloud-based electronic health record, called V12, for medical practices and other care settings, with specialty versions for dental, vision, behavioral health, ambulatory surgery, urgent care and health centers. Around the core record the maker offers an inpatient EHR, a pharmacy management system, Value-Based Care for population health, Patient Engagement with self-scheduling, check-in and healow TeleVisits, and Revenue Cycle Management. Its dental version is organised around an Electronic Dental Record. Its cloud hosting is sold as a separate offering called The Cloud.
What these workflow templates do
Every workflow template below works from an export from an electronic health record or medical practice management system and changes nothing in it.
Workflows for electronic health record and medical practice management systems
No workflow template names eClinicalWorks yet. The templates below are not written for eClinicalWorks by name; each is written for an electronic health record or medical practice management system.
Claim denial work list Workflow template
Works from an export from an electronic health record or medical practice management system.
Can see: denied claim lines from the remittance export. Can change: nothing.
Prior-authorization follow-up list Workflow template
Works from an export from an electronic health record or medical practice management system.
Can see: pending referrals and authorization status, to check the list against. Can change: nothing.
Teams that run these workflow templates:
How it connects
Each connector below is one we know of, with who publishes it, where and when we found it, and its trust level.
Published by its maker
Programming interface from the maker of eClinicalWorks
A programming interface for software developers.
Published by eClinicalWorks, as the maker's own page states.
Found in the maker's own documentation on 13 November 2026. Last checked on 13 November 2026.
ListedFound in a named public source on a stated date. We have not reviewed or used it.
What setup takes, and who approves it
Connecting a workflow to eClinicalWorks is agreed when the work is scoped: a person who looks after eClinicalWorks at your company approves how the workflow signs in and what it may see and change.
No time is promised here. Where no connector exists, the workflow works from an export.
What was checked, and when
- The maker's own pages: read on 13 November 2026.
- The workflow templates above: each link was read from the template's own text and reviewed, most recently on 12 November 2026.
Next step
Want a workflow above built for your team? Open it and choose how to start, or book a fit call.
Technical details
- eClinicalWorks FHIR APIs · Public APIFound in the maker's own documentationeClinicalWorks describes FHIR APIs that let third-party developers build applications connected to its EHR, with a developer portal for registration and sandbox testing.The maker’s page