Skip to content
Data warehouse ⇄ Business productivity

Apache Druid to eClinicalWorks integration — real-time, two-way sync

Keep Apache Druid 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.

  • 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 Apache Druid and eClinicalWorks

Get the data locked inside eClinicalWorks into Apache Druid as live tables, and send results back where eClinicalWorks can use them, without writing a pipeline.

Whatever eClinicalWorks is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.

Stacksync syncs Immunizations, Documents, Diagnostic reports, Patients from eClinicalWorks into tables in Apache Druid continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Apache Druid can also be written back into fields in eClinicalWorks where the tool can use them.

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.
  • Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
  • Sync Druid query results into a warehouse to combine real-time aggregates with historical models.

History that outlives the tool

A continuously synced copy in Apache Druid preserves a queryable record even as data ages out of eClinicalWorks or gets changed inside it.

Analytics on eClinicalWorks's data

Records and events from eClinicalWorks land in Apache Druid as queryable tables, current within seconds and ready to join with the rest of the warehouse.

Cross-tool reporting

Combine eClinicalWorks's data with data from every other synced system to answer questions no single tool can.

What you can sync between Apache Druid and eClinicalWorks

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.

Apache Druid objects eClinicalWorks objects
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Medications Prescription and medication-list data within the patient record.
Lookups Key-value mappings joined at query time, refreshable from external systems. Allergies Allergy and intolerance entries in the clinical record.
Tasks Batch ingestion and compaction jobs monitored during data loads. Immunizations Vaccination history exposed for registries and patient apps.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Documents Clinical notes and attachments referenced from the chart.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Diagnostic reports Structured result reports grouping observations for a study or panel.
What ships with Apache Druid ⇄ eClinicalWorks

Connect Apache Druid and eClinicalWorks for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Apache Druid ⇄ eClinicalWorks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Druid and eClinicalWorks.

How the Apache Druid and eClinicalWorks connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

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
How it works

How to connect Apache Druid to eClinicalWorks — 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 Apache Druid 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Druid connected
    eClinicalWorks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Druid ⇄ eClinicalWorks
    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
    Apache Druid eClinicalWorks
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and eClinicalWorks 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 Apache Druid and eClinicalWorks.

Popular · 8 of 386
All Apache Druid integrations All eClinicalWorks 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