Skip to content
Data warehouse ⇄ Business productivity

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

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

Get the data locked inside eClinicalWorks into BigQuery 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 Documents, Diagnostic reports, Patients, Appointments from eClinicalWorks into tables in BigQuery continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in BigQuery can also be written back into fields in eClinicalWorks where the tool can use them.

Common use cases

  • 01 Push referral or intake data captured in external forms into the EHR via HL7 interfaces.
  • 02 Sync patient demographics and appointments into a CRM so patient outreach and intake teams work from current data.
  • 03 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools
  • 04 Maintain a customer master table in BigQuery joined across CRM, billing, and support sources

Common sync patterns

Cross-tool reporting

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

Where eClinicalWorks accepts updates: operational write-back

Segments, scores, or reference values computed in BigQuery sync back onto records in eClinicalWorks, putting analysis where the work happens.

History that outlives the tool

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

What you can sync between BigQuery 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.

BigQuery objects eClinicalWorks objects How this pairing syncs
Projects Connection scope: the service account grants access per project. Encounters Visit records tying diagnoses, providers, and billing context together. Projects is specific to BigQuery and Encounters to eClinicalWorks — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Practitioners Provider records used to keep directories and scheduling systems consistent. Tables is specific to BigQuery and Practitioners to eClinicalWorks — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Partitioned tables is specific to BigQuery and Observations to eClinicalWorks — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Medications Prescription and medication-list data within the patient record. Clustered tables is specific to BigQuery and Medications to eClinicalWorks — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Allergies Allergy and intolerance entries in the clinical record. Datasets is specific to BigQuery and Allergies to eClinicalWorks — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and eClinicalWorks

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.

BigQuery eClinicalWorks Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

DeliveryEach detected change is written to eClinicalWorks through its API, with automatic retries and rate-limit backoff.

eClinicalWorks BigQuery 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 applied to BigQuery as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
What ships with BigQuery ⇄ eClinicalWorks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the BigQuery and eClinicalWorks connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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 BigQuery 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 BigQuery 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
    BigQuery connected
    eClinicalWorks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

BigQuery and eClinicalWorks integration FAQ

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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 475 integrations available for BigQuery and eClinicalWorks.

Popular · 7 of 475
All BigQuery 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