Real-time
Two-way sync
Changes in eClinicalWorks or Reltio instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
eClinicalWorks to Reltio integration — real-time, two-way sync
Keep eClinicalWorks and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect eClinicalWorks and Reltio
Mirror eClinicalWorks's data into Reltio so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Engineers integrate with tools like eClinicalWorks through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Reltio.
Stacksync mirrors Immunizations, Documents, Diagnostic reports, Patients from eClinicalWorks into Interactions, Matches (Potential Matches), Activity Log, Data Change Requests (DCR) in Reltio and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into eClinicalWorks, so the tool and the database never disagree.
Common use cases
- 01 Keep provider directories consistent between eClinicalWorks and scheduling or marketing systems.
- 02 Push referral or intake data captured in external forms into the EHR via HL7 interfaces.
- 03 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
- 04 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
Common sync patterns
Automate eClinicalWorks from your codebase
Write to the synced tables in Reltio and Stacksync propagates the change into eClinicalWorks, replacing custom integration code.
React to changes as they happen
Updates in eClinicalWorks arrive as row changes in Reltio, so triggers, jobs, and services can respond in near real time.
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
What you can sync between eClinicalWorks and Reltio
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Patients is specific to eClinicalWorks and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Appointments is specific to eClinicalWorks and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| Encounters Visit records tying diagnoses, providers, and billing context together. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Encounters is specific to eClinicalWorks and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Practitioners is specific to eClinicalWorks and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Observations is specific to eClinicalWorks and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Medications Prescription and medication-list data within the patient record. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Medications is specific to eClinicalWorks and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between eClinicalWorks and Reltio
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
eClinicalWorks Reltio Interval-based propagation
DetectionStacksync polls eClinicalWorks for changes on an incremental schedule, reading only records changed since the previous pass. HL7 interface feeds push event messages as they occur.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio eClinicalWorks Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to eClinicalWorks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with eClinicalWorks ⇄ Reltio
Connect eClinicalWorks and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever eClinicalWorks or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single eClinicalWorks or Reltio record.
Observability
Monitoring
Track your eClinicalWorks ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Reltio.
How the eClinicalWorks and Reltio connectors work
eClinicalWorks
- Integration surface
- 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
- Change detection
- HL7 interface feeds push event messages as they occur; the FHIR API is polled
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and interface throughput agreements
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect eClinicalWorks to Reltio — three steps, no code
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.
- 01
Connect your apps
Authenticate eClinicalWorks and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
eClinicalWorks
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the eClinicalWorks and Reltio 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.
objects · eClinicalWorks ⇄ ReltioCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
eClinicalWorks ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
eClinicalWorks and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between eClinicalWorks and Reltio: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Patients and Appointments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed eClinicalWorks and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom eClinicalWorks–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both eClinicalWorks and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on eClinicalWorks: HL7 interface feeds push event messages as they occur; the FHIR API is polled. On Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the eClinicalWorks side: Immunizations, Documents, Diagnostic reports, Patients, plus custom fields where eClinicalWorks exposes them. On the Reltio side: Interactions, Matches (Potential Matches), Activity Log, Data Change Requests (DCR). Stacksync auto-detects both schemas and converts types between the two systems.
-
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.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 364 integrations available for eClinicalWorks and Reltio.
Popular · 8 of 364
-
eClinicalWorks ⇄ Google AlloyDB -
eClinicalWorks ⇄ Dynamo DB -
eClinicalWorks ⇄ IBM Db2 -
eClinicalWorks ⇄ Firebase -
Reltio ⇄ GitHub -
Reltio ⇄ Atlassian -
Reltio ⇄ Braze -
Reltio ⇄ ConnectWise
No integrations match .
