Real-time
Two-way sync
Changes in eClinicalWorks or Google Pubsub instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Developer tools
eClinicalWorks to Google Pubsub integration — real-time, two-way sync
Keep eClinicalWorks and Google Pubsub 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 Google Pubsub
Connect the tickets, records, and events in eClinicalWorks to the systems engineering runs in Google Pubsub, kept current in real time and in both directions.
eClinicalWorks is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Google Pubsub is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.
Stacksync syncs Appointments, Encounters, Practitioners, Observations in eClinicalWorks with Snapshots, Message attributes, Dead-letter topics, Ordering keys in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.
Common use cases
- 01 Sync patient demographics and appointments into a CRM so patient outreach and intake teams work from current data.
- 02 Land encounter and billing-context data in a warehouse for utilization and revenue-cycle reporting.
- 03 Fan out CRM record changes to a topic and let billing, analytics, and notification subscriptions each react without coupling to the source.
- 04 Bridge order or billing events off a topic into an ERP or ticketing system as they arrive, mapping message attributes to target fields.
Common sync patterns
One shared record across both systems
Where both systems keep records for the same contacts, items, or users, a correction in either updates the other, ending dual maintenance and keeping IDs aligned for every other flow.
Where Google Pubsub tracks engineering work: requests become issues
A ticket or request raised in eClinicalWorks opens or updates a matching issue in Google Pubsub, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.
Where Google Pubsub moves messages between services: activity lands on the stream
Records created or changed in eClinicalWorks publish to the queue or topic in Google Pubsub as they happen, so downstream services react to real events rather than polling for them.
What you can sync between eClinicalWorks and Google Pubsub
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 | Google Pubsub objects | How this pairing syncs | |
|---|---|---|---|
| Immunizations Vaccination history exposed for registries and patient apps. | Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. | Immunizations is specific to eClinicalWorks and Dead-letter topics to Google Pubsub — each maps to any object or custom field on the other side. | |
| Documents Clinical notes and attachments referenced from the chart. | Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. | Documents is specific to eClinicalWorks and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side. | |
| Diagnostic reports Structured result reports grouping observations for a study or panel. | Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. | Diagnostic reports is specific to eClinicalWorks and Topics to Google Pubsub — each maps to any object or custom field on the other side. | |
| Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. | Patients is specific to eClinicalWorks and Subscriptions to Google Pubsub — 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. | Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. | Appointments is specific to eClinicalWorks and Messages to Google Pubsub — each maps to any object or custom field on the other side. | |
| Encounters Visit records tying diagnoses, providers, and billing context together. | Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. | Encounters is specific to eClinicalWorks and Schemas to Google Pubsub — each maps to any object or custom field on the other side. |
How changes propagate between eClinicalWorks and Google Pubsub
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 Google Pubsub 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 Google Pubsub through its API, with automatic retries and rate-limit backoff.
Google Pubsub eClinicalWorks Sub-second propagation
DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.
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.
- Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with eClinicalWorks ⇄ Google Pubsub
Connect eClinicalWorks and Google Pubsub for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Google Pubsub connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever eClinicalWorks or Google Pubsub 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 Google Pubsub record.
Observability
Monitoring
Track your eClinicalWorks ⇄ Google Pubsub 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 Google Pubsub.
How the eClinicalWorks and Google Pubsub 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
Google Pubsub
- Integration surface
- REST and gRPC (Cloud Pub/Sub API v1)
- Authentication
- Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
- Change detection
- Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
- Capabilities
- read · write · webhooks
- Rate limits
- Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works
How to connect eClinicalWorks to Google Pubsub — 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 Google Pubsub 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
Google Pubsub
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the eClinicalWorks and Google Pubsub 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 ⇄ Google PubsubCustomers 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 Google PubsubCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
eClinicalWorks and Google Pubsub integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between eClinicalWorks and Google Pubsub: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Immunizations and Documents), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for eClinicalWorks and Google Pubsub: One shared record across both systems; Where Google Pubsub tracks engineering work: requests become issues; Where Google Pubsub moves messages between services: activity lands on the stream. Where both systems keep records for the same contacts, items, or users, a correction in either updates the other, ending dual maintenance and keeping IDs aligned for every other flow.
-
eClinicalWorks: 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. Google Pubsub: REST and gRPC (Cloud Pub/Sub API v1). Authentication: Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber. Stacksync manages authentication, retries, and rate limits on both sides.
-
eClinicalWorks: All patient data is PHI, so integrations must run under HIPAA business associate agreements with appropriate access controls. Google Pubsub: Push subscriptions deliver as HTTPS POSTs with base64-encoded data and can carry an OIDC JWT for authentication; the endpoint must return a 2xx (or 102) to ack. Stacksync's field mapping accounts for these differences between eClinicalWorks and Google Pubsub without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means eClinicalWorks and Google Pubsub records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed eClinicalWorks and Google Pubsub connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom eClinicalWorks–Google Pubsub integration in-house.
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
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 251 integrations available for eClinicalWorks and Google Pubsub.
Popular · 7 of 251
-
eClinicalWorks ⇄ Rabbitmq -
eClinicalWorks ⇄ Azure Service Bus -
eClinicalWorks ⇄ Datadog -
eClinicalWorks ⇄ Ldap -
Google Pubsub ⇄ Microsoft 365 -
Google Pubsub ⇄ Microsoft Dynamics 365 -
Google Pubsub ⇄ Microsoft Teams
No integrations match .
