Clarity Connect integration
eClinicalWorks SQL Server Integration
Get eClinicalWorks data into a SQL Server database you control, through the bulk FHIR APIs and export tools eClinicalWorks certifies, so it can sit next to your other systems' data.
What moves between eClinicalWorks and SQL Server
eClinicalWorks holds the chart, the schedule and the practice's billing. Practices usually want that data in SQL Server to report across locations, or to combine it with finance, CRM or portal data. eClinicalWorks doesn't publish direct database access for outside software. The documented routes are its certified FHIR APIs, its EHI Export and its eBO reports, so a SQL Server feed is built on those.
eClinicalWorks
Where the chart and practice billing live
- Certified FHIR APIs
- Bulk (multi-patient) FHIR exports
- EHI Export files
- eBO reports
SQL Server
Where cross-system reporting happens
- Staging tables
- Reporting tables
- Data joined with finance or CRM
- Load and error logs
eClinicalWorks to SQL Server data map
Plain descriptions on the left, because eClinicalWorks doesn't publish its resource list outside its developer portal. Discovery confirms what your eClinicalWorks version exposes.
| eClinicalWorks | SQL Server | Direction |
|---|---|---|
| Patient demographics | Patient table | eClinicalWorks to SQL Server |
| Problems, medications and allergies | Clinical summary tables | eClinicalWorks to SQL Server |
| Lab results and vitals | Results table | eClinicalWorks to SQL Server |
| Bulk FHIR export files | Staging tables, merged nightly | eClinicalWorks to SQL Server |
| EHI Export package | Archive or migration tables | eClinicalWorks to SQL Server |
How eClinicalWorks data reaches SQL Server
Bulk FHIR exports on a schedule
eClinicalWorks offers bulk (multi-patient) FHIR APIs, certified under ONC's § 170.315(g)(10) criterion, through its FHIR developer portal for backend services. Once the practice authorizes a backend app, Connect can request a population export each night and load the files into SQL Server staging tables.
EHI Export for a complete copy
eClinicalWorks is also certified for EHI Export. Authorized practice users can export all the electronic health information stored for one patient, or request an export for the whole patient population. That suits a migration, an archive or a one-off analysis better than a daily feed. The file format is documented at ehi.eclinicalworks.com.
eBO when a standard report will do
eClinicalWorks Business Optimizer (eBO) is eClinicalWorks' own reporting tool. It has canned financial and clinical reports and dashboards, and any report can be scheduled and emailed. If an eBO report already answers the question, you may not need a SQL Server feed. Build one when the data has to be joined with other systems.
Writing back into eClinicalWorks
eClinicalWorks lists clinical, practice-management and financial integrations among its interoperability options, and patient-facing apps connect through the separate healow developer portal. Anything that has to land in eClinicalWorks goes through one of those routes, agreed with eClinicalWorks, rather than into its database.
See Clarity Connect move an order
Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.
What eClinicalWorks documents for developers
Provider-facing and backend or bulk FHIR APIs are documented on fhir.eclinicalworks.com, part of what eClinicalWorks calls its Platform for Open Development. Patient-facing apps register on connect4.healow.com instead. eClinicalWorks says its certified FHIR APIs are free to developers and customers "at this time", that it may add chargeable value-added services later, and that it will give customers at least 30 days' notice of any API fees.
eClinicalWorks also participates in TEFCA, the national framework for exchanging records between networks. That covers record exchange between providers, not a reporting feed into your own database.
HIPAA once the data is in SQL Server
A SQL Server database holding eClinicalWorks data holds electronic PHI, so the practice's Security Rule risk analysis has to cover it. HIPAA lists encryption at rest and in transit as addressable (45 CFR 164.312): implement it, or document why an equivalent measure is reasonable. SQL Server's Transparent Data Encryption handles the data files, and connections need TLS configured separately. A vendor that hosts or moves the data for the practice needs a business associate agreement (45 CFR 164.502(e)).
How Clarity Connect runs it
Clarity Connect is Clarity's integration platform. It works with APIs, files and databases, and it runs each eClinicalWorks export as a scheduled task with its own queue. If SQL Server is offline when a load runs, the job goes to a retry queue and can be re-queued from the dashboard once the cause is fixed. Connect can run on a server inside the practice's network when SQL Server is on-premises. To see Connect running real tasks, browse our video playlist.
Discovery
A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.
Tasks and mapping
Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.
Testing
Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.
Live, with a dashboard
Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.
Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.
Questions
Can we query the eClinicalWorks database directly?
eClinicalWorks doesn't publish direct database access for outside software. Its documented routes are the certified FHIR APIs (including bulk export), EHI Export and eBO reports. Ask eClinicalWorks about anything beyond those.
Do eClinicalWorks's APIs cost anything?
eClinicalWorks says its certified FHIR APIs are available at no cost at this time. It reserves the right to charge for value-added services later, with 30 days' notice to customers.
How fresh is the data in SQL Server?
It's as fresh as the export schedule, usually nightly for a bulk export. A reporting database rarely needs more. Patient-facing apps that need live data use the FHIR APIs directly.
What does Clarity Connect cost?
Clarity Connect is $599 a month as SaaS, or a one-time license of $15,000 with no ongoing fees. Larger projects are priced to scope. See pricing.
Related resources
Connect eClinicalWorks and SQL Server
Tell us which reports you can't get out of eClinicalWorks today and what they need to be joined with. A Clarity business analyst will work out the export route and the table design with your team before anything is built.
Book a demo