Two-way sync
Changes in eClinicalWorks or Odoo instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and Odoo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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.
Stacksync syncs Practitioners, Observations, Medications, Allergies in eClinicalWorks with Purchase Orders (purchase.order), Inventory Transfers (stock.picking), Employees (hr.employee), Projects and Tasks (project.project / project.task) in Odoo bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Payment events sync into Odoo as they occur, keeping the enterprise records current without manual entry.
Worker and organization data from Odoo 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.
| eClinicalWorks objects | Odoo objects | |
|---|---|---|
| Encounters Visit records tying diagnoses, providers, and billing context together. | Employees (hr.employee) HR records read for directory and provisioning syncs. | |
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Projects and Tasks (project.project / project.task) Work items synced with external project tools. | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | |
| Medications Prescription and medication-list data within the patient record. | Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | |
| Allergies Allergy and intolerance entries in the clinical record. | Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | |
| Immunizations Vaccination history exposed for registries and patient apps. | Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Odoo connection.
Changes in eClinicalWorks or Odoo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single eClinicalWorks or Odoo record.
Track your eClinicalWorks ⇄ Odoo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Odoo.
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 eClinicalWorks and Odoo 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 eClinicalWorks and Odoo 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 two-way integration between eClinicalWorks and Odoo: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Encounters and Practitioners), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for eClinicalWorks and Odoo: Where eClinicalWorks collects payments: transactions post through; Where Odoo is the HR or people system of record; Master data corrections travel. Payment events sync into Odoo as they occur, keeping the enterprise records current without manual entry.
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. Odoo: XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink). Authentication: Database user credentials or per-user API keys. Stacksync manages authentication, retries, and rate limits on both sides.
eClinicalWorks: All patient data is PHI, so integrations must run under HIPAA business associate agreements with appropriate access controls. Odoo: Custom fields added through Odoo Studio or modules (prefixed x_) are exposed through the same API automatically. Stacksync's field mapping accounts for these differences between eClinicalWorks and Odoo without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means eClinicalWorks and Odoo records are not retained after a sync operation.
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 eClinicalWorks and Odoo.