Two-way sync
Changes in eClinicalWorks or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and VoltDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 VoltDB.
Stacksync mirrors Appointments, Encounters, Practitioners, Observations from eClinicalWorks into Streams, Export Targets and Topics, Partitioned Tables, Replicated Tables in VoltDB 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.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from eClinicalWorks are ordinary rows in VoltDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in VoltDB and Stacksync propagates the change into eClinicalWorks, replacing custom integration code.
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 | VoltDB objects | |
|---|---|---|
| Diagnostic reports Structured result reports grouping observations for a study or panel. | Stored Procedures Precompiled transactional units that serve as the primary write interface. | |
| Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | Materialized Views Synchronously maintained aggregates over tables, useful as pre-computed read sources. | |
| Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. | Streams Insert-only constructs that feed the export subsystem with committed rows. | |
| Encounters Visit records tying diagnoses, providers, and billing context together. | Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks. | |
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target. | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–VoltDB connection.
Changes in eClinicalWorks or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or VoltDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single eClinicalWorks or VoltDB record.
Track your eClinicalWorks ⇄ VoltDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and VoltDB.
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.
Authenticate eClinicalWorks and VoltDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the eClinicalWorks and VoltDB 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between eClinicalWorks and VoltDB: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Diagnostic reports and Patients), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on eClinicalWorks: HL7 interface feeds push event messages as they occur; the FHIR API is polled. On VoltDB: Export streams and topics push committed changes to configured targets; otherwise polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the eClinicalWorks side: Appointments, Encounters, Practitioners, Observations, plus custom fields where eClinicalWorks exposes them. On the VoltDB side: Streams, Export Targets and Topics, Partitioned Tables, Replicated Tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for eClinicalWorks and VoltDB: One integration pattern for the whole stack; Read eClinicalWorks with a query; Automate eClinicalWorks from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
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. VoltDB: SQL over JDBC plus native client libraries and an HTTP/JSON interface. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for eClinicalWorks and VoltDB.