Skip to content
Business productivity ⇄ Database

eClinicalWorks to InterSystems IRIS integration — real-time, two-way sync

Keep eClinicalWorks and InterSystems IRIS 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 InterSystems IRIS

Mirror eClinicalWorks's data into InterSystems IRIS 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 InterSystems IRIS.

Stacksync mirrors Allergies, Immunizations, Documents, Diagnostic reports from eClinicalWorks into Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS 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

  • Keep provider directories consistent between eClinicalWorks and scheduling or marketing systems.
  • Push referral or intake data captured in external forms into the EHR via HL7 interfaces.
  • Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
  • Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools

React to changes as they happen

Updates in eClinicalWorks arrive as row changes in InterSystems IRIS, 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.

Read eClinicalWorks with a query

Records from eClinicalWorks are ordinary rows in InterSystems IRIS; join them, index them, and use them in application logic without touching the vendor API.

What you can sync between eClinicalWorks and InterSystems IRIS

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 InterSystems IRIS objects
Practitioners Provider records used to keep directories and scheduling systems consistent. Namespaces Namespaces partition databases and determine the connection context for integrations.
Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations.
Medications Prescription and medication-list data within the patient record. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs.
Allergies Allergy and intolerance entries in the clinical record. Views SQL views expose curated slices of data for outbound replication.
Immunizations Vaccination history exposed for registries and patient apps. Schemas Schema organization scopes which tables a sync connection can see.
Documents Clinical notes and attachments referenced from the chart. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL.
What ships with eClinicalWorks ⇄ InterSystems IRIS

Connect eClinicalWorks and InterSystems IRIS for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–InterSystems IRIS connection.

Real-time

Two-way sync

Changes in eClinicalWorks or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever eClinicalWorks or InterSystems IRIS 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 InterSystems IRIS record.

Observability

Monitoring

Track your eClinicalWorks ⇄ InterSystems IRIS 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 InterSystems IRIS.

How the eClinicalWorks and InterSystems IRIS 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

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits
How it works

How to connect eClinicalWorks to InterSystems IRIS — 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.

  1. 01

    Connect your apps

    Authenticate eClinicalWorks and InterSystems IRIS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    eClinicalWorks connected
    InterSystems IRIS connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the eClinicalWorks and InterSystems IRIS 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · eClinicalWorks ⇄ InterSystems IRIS
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    eClinicalWorks InterSystems IRIS
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

eClinicalWorks and InterSystems IRIS integration FAQ

SECURITY

Security teams love 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for eClinicalWorks and InterSystems IRIS.

Popular · 8 of 386
All eClinicalWorks integrations All InterSystems IRIS integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own