Two-way sync
Changes in eClinicalWorks or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Rillet holds the financial truth: who the customers are, what they were billed, what they paid. eClinicalWorks is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Journal Entry, Invoice Payment, Charge, Reimbursement in Rillet and Diagnostic reports, Patients, Appointments, Encounters in eClinicalWorks in sync, bi-directionally and in real time. Whatever records eClinicalWorks keeps and whatever events it produces, the overlap with Rillet is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Payment and charge activity flows into Rillet as it happens, so the books reflect reality without manual reconciliation.
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
Figures teams rely on, like customer status or outstanding balances, stay current wherever eClinicalWorks surfaces them instead of going stale after a one-time paste.
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 | Rillet objects | |
|---|---|---|
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | |
| Medications Prescription and medication-list data within the patient record. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Allergies Allergy and intolerance entries in the clinical record. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Immunizations Vaccination history exposed for registries and patient apps. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Documents Clinical notes and attachments referenced from the chart. | Vendor Synced with incremental and full sync per the Stacksync docs. | |
| Diagnostic reports Structured result reports grouping observations for a study or panel. | Invoice Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Rillet connection.
Changes in eClinicalWorks or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Rillet 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 Rillet record.
Track your eClinicalWorks ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Rillet.
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 Rillet 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 Rillet 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 Rillet: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Observations and Medications), 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 Rillet: Where eClinicalWorks collects payments or triggers charges: events land in Rillet; Where eClinicalWorks tracks people or companies: one identity; Where eClinicalWorks is a docs or knowledge workspace: reference data kept fresh. Payment and charge activity flows into Rillet as it happens, so the books reflect reality without manual reconciliation.
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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. eClinicalWorks: As an ONC-certified EHR, eClinicalWorks exposes FHIR R4 APIs following SMART on FHIR patterns to meet 21st Century Cures requirements, which standardizes patient-level read access. Stacksync's field mapping accounts for these differences between eClinicalWorks and Rillet 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 Rillet 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 Rillet.