Skip to content
Business productivity ⇄ Database

eClinicalWorks to TiDB integration — real-time, two-way sync

Keep eClinicalWorks and TiDB 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 TiDB

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

Stacksync mirrors Immunizations, Documents, Diagnostic reports, Patients from eClinicalWorks into Sequences, Databases, Tables, Views in TiDB 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.
  • Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge

Read eClinicalWorks with a query

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

Automate eClinicalWorks from your codebase

Write to the synced tables in TiDB 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 TiDB, so triggers, jobs, and services can respond in near real time.

What you can sync between eClinicalWorks and TiDB

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 TiDB objects
Allergies Allergy and intolerance entries in the clinical record. Sequences Server-side ID generation relevant when external systems write rows.
Immunizations Vaccination history exposed for registries and patient apps. Databases MySQL-style schemas addressed by any MySQL-compatible client.
Documents Clinical notes and attachments referenced from the chart. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC.
Diagnostic reports Structured result reports grouping observations for a study or panel. Views Logical views for shaping reads before syncing outward.
Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Columns MySQL-compatible types mapped to fields in the paired system.
Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Indexes Secondary indexes that keep incremental sync queries efficient.
What ships with eClinicalWorks ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

How to connect eClinicalWorks to TiDB — 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 TiDB 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
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the eClinicalWorks and TiDB 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 ⇄ TiDB
    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 TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

eClinicalWorks and TiDB 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 TiDB.

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