Real-time sync
Changes in E2 Shop System or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Keep E2 Shop System and eClinicalWorks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into eClinicalWorks, so eClinicalWorks always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. eClinicalWorks is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Payment events sync into E2 Shop System as they occur, keeping the enterprise records current without manual entry.
Worker and organization data from E2 Shop System stays current in eClinicalWorks, so the tools people use daily reflect the org as it actually is.
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| E2 Shop System objects | eClinicalWorks objects | |
|---|---|---|
| Time tickets Labor collection records used for job costing. | Allergies Allergy and intolerance entries in the clinical record. | |
| Invoices Billing records synced to accounting for AR reporting. | Immunizations Vaccination history exposed for registries and patient apps. | |
| Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. | Documents Clinical notes and attachments referenced from the chart. | |
| Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. | Diagnostic reports Structured result reports grouping observations for a study or panel. | |
| Customers Buyer records synced to CRM or accounting counterparts. | Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | |
| Vendors Supplier records referenced on purchasing documents. | Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–eClinicalWorks connection.
Changes in E2 Shop System or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever E2 Shop System or eClinicalWorks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single E2 Shop System or eClinicalWorks record.
Track your E2 Shop System ⇄ eClinicalWorks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between E2 Shop System and eClinicalWorks.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate E2 Shop System and eClinicalWorks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the E2 Shop System and eClinicalWorks objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between E2 Shop System and eClinicalWorks — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
On the eClinicalWorks side: Encounters, Practitioners, Observations, Medications, plus custom fields where eClinicalWorks exposes them. On the E2 Shop System side: Parts, Routings / Operations, Purchase orders, Time tickets. Stacksync auto-detects both schemas and converts types between the two systems.
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into eClinicalWorks. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for E2 Shop System and eClinicalWorks: Where eClinicalWorks collects payments: transactions post through; Where E2 Shop System is the HR or people system of record; Master data corrections travel. Payment events sync into E2 Shop System as they occur, keeping the enterprise records current without manual entry.
E2 Shop System: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment. Authentication: Database credentials or application-level export access on the on-premises installation. eClinicalWorks: FHIR R4 REST API plus HL7 v2 interfaces (ADT, SIU, ORU) through an interface engine. Authentication: OAuth 2.0 / SMART on FHIR for the FHIR API; site-configured credentials for HL7 interface connections. Stacksync manages authentication, retries, and rate limits on both sides.
eClinicalWorks: Traditional integrations run over HL7 v2 interfaces (ADT for demographics, SIU for scheduling, ORU for results), which are push-based message feeds rather than request/response APIs. E2 Shop System: E2 is a Windows-based job shop ERP from Shoptech, now part of ECI Software Solutions, where it has been rebranded as JobBOSS²; most installations run on premises. Stacksync's field mapping accounts for these differences between E2 Shop System and eClinicalWorks without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for E2 Shop System and eClinicalWorks.