eClinicalWorks integration guide
How to connect HealthArc to eClinicalWorks
Your eCW administrator does four things in Admin → Product Activation: turn on FHIR APIs, set up Backend Services Apps, add HealthArc with the activation code we send, and activate it once we approve. Our team handles everything after that.
At a glance
The eClinicalWorks integration in six lines
| Connection type | eClinicalWorks FHIR APIs, set up as a Backend Services app |
|---|---|
| Where it runs | Cloud to cloud. Nothing to install on your servers or workstations |
| Who authorizes it | Your eCW administrator, in Admin → Product Activation |
| What you need from us | The HealthArc App Activation Code, sent by your implementation team |
| Bulk data | Optional bulk FHIR access using patient groups you create in eCW |
| Security | HIPAA compliant, SOC 2 compliant, BAA signed before any data moves |
Data flow
What moves between eClinicalWorks and HealthArc
From eClinicalWorks into HealthArc
- Patient demographics and contact details
- Problem list and diagnoses (ICD-10)
- Active medications and allergies
- Appointments and encounters
- Providers and locations
- Vitals and lab results, where available
From HealthArc back to eClinicalWorks
- Monthly care-management notes, where your eCW setup allows write-back
- Care plans and care-plan updates, where write-back is enabled
- Write-back scope confirmed in writing during scoping
Exact fields depend on your eClinicalWorks configuration and the programs you run, and are confirmed in writing during scoping. HealthArc only requests the data those programs need.
Before you start
What you need in place
None of this needs an IT team. Most of it is a decision or a name, and the scoping call covers anything you haven’t settled yet.
- An active eClinicalWorks account
- Administrator access in eCW
- The HealthArc App Activation Code from your implementation team or Customer Success Manager
- A signed HealthArc agreement and business associate agreement
- A list of the providers and facilities that will bill care-management programs
Your time investment4–8 hours
Total time from your team, across the whole setup. HealthArc does the build.
Where your time goes
- Scoping call
- Authorizing HealthArc in eClinicalWorks
- Approving the mapping
- Reviewing the pilot
No IT team neededLive in about 30 days
Setup steps
7 steps from first call to go-live
Most practices are monitoring patients within about 30 days of signing.
- 1Practice + HealthArc
Agreements and scoping
We confirm the programs you want to run, the providers and locations involved, and who owns clinical work and billing on your side. The HealthArc agreement and business associate agreement are signed before any data moves. You also receive the HealthArc App Activation Code at this step.
- 2eCW administrator
Open Product Activation
Admin → Product Activation
Log in to eClinicalWorks with an administrator account and open Product Activation.
In the eClinicalWorks Admin menu, Product Activation sits in the middle column. - 3eCW administrator
Activate FHIR APIs
Admin → Product Activation → FHIR APIs
Find the FHIR APIs section and click Activate to turn on FHIR API access for your eCW environment.
FHIR APIs in the Product Activation list. After activation, its button changes to Settings. - 4eCW administrator
Add HealthArc as a Backend Services app
Product Activation → Backend Services Apps → Set Up
Open Backend Services Apps and click Set Up, then add HealthArc.
- Click Add New App
- Enter the App Activation Code from your HealthArc team
- Save the application
On the FHIR APIs screen, click Set up on the Backend Services Apps card. Enter the HealthArc activation code under Add New App. Once it’s added, HealthArc shows as its own card. - 5HealthArc
HealthArc reviews and approves the app
The request shows up on HealthArc’s side, in the eCW Developer Portal, where our implementation team checks it against your practice details and approves it. You don’t need to do anything.
- 6eCW administrator
Activate the approved app
Return to the app settings in eClinicalWorks, find the HealthArc application and click Activate. That’s the last step on your side.
- 7HealthArc + practice
HealthArc configures, tests and goes live
Once we have access, our implementation team configures the eClinicalWorks connection, validates authentication and data access, maps providers and locations, and tests with a small pilot group. Your Customer Success Manager confirms when the integration is complete, and we train your team before enrollment opens.
- Using bulk data? Create patient groups (cohorts) in eCW for the population HealthArc should sync. We send separate instructions for this.
Who does what
Your team and ours
| Task | Your practice | HealthArc |
|---|---|---|
| Turn on FHIR APIs and add the HealthArc app | Yes | – |
| Provide the App Activation Code | – | Yes |
| Review and approve the app request | – | Yes |
| Activate the approved app in eCW | Yes | – |
| Create patient groups for bulk access (if used) | Yes | – |
| Technical build, mapping and testing | – | Yes |
| Staff training | – | Yes |
| Ongoing monitoring and support | – | Yes |
Security
How patient data is protected
BAA first
A business associate agreement is signed before any patient data moves.
Encrypted
Databases are encrypted at rest, and data in transit uses TLS only.
SOC 2 and HIPAA
HealthArc’s security program follows the SOC 2 framework, and the platform is HIPAA compliant.
U.S. hosting
Data is stored on AWS in the United States.
Full details are on the HealthArc security page.
FAQ
eClinicalWorks integration questions
How do I connect HealthArc to eClinicalWorks?
In eCW, go to Admin → Product Activation, activate FHIR APIs, open Backend Services Apps and click Set Up, then Add New App with the HealthArc App Activation Code. After HealthArc approves the request, return to the app settings and click Activate. HealthArc completes the configuration from there.
Where do I get the HealthArc App Activation Code?
From your HealthArc implementation team or Customer Success Manager. It identifies the HealthArc application when you add it in Backend Services Apps.
What are patient groups for?
They’re only needed for bulk FHIR access. If your organization wants population-level data synced to HealthArc, you create patient groups or cohorts in eCW based on your selection criteria, and HealthArc uses them for bulk data access.
Does HealthArc write data back to eClinicalWorks?
Where your eCW configuration allows it. The write-back scope depends on the eCW APIs enabled for your practice and is confirmed in writing during scoping.
Who do I contact if activation doesn’t work?
Your HealthArc Customer Success Manager or the HealthArc Support Team. We can check whether the app request reached our side and walk your administrator through the activation screens.
Sources
Ready to connect eClinicalWorks?
Book a scoping call. You’ll leave with a written implementation plan for your practice, your programs and your go-live date.
eClinicalWorks and eCW are trademarks of eClinicalWorks, LLC. HealthArc is an independent company.