Two-way sync
Changes in Cloudera Data Platform or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Keep Cloudera Data Platform 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.
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 Allergies, Immunizations, Documents, Diagnostic reports from eClinicalWorks into tables in Cloudera Data Platform continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Cloudera Data Platform can also be written back into fields in eClinicalWorks where the tool can use them.
Combine eClinicalWorks's data with data from every other synced system to answer questions no single tool can.
Segments, scores, or reference values computed in Cloudera Data Platform sync back onto records in eClinicalWorks, putting analysis where the work happens.
A continuously synced copy in Cloudera Data Platform preserves a queryable record even as data ages out of eClinicalWorks or gets changed inside it.
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.
| Cloudera Data Platform objects | eClinicalWorks objects | |
|---|---|---|
| Iceberg tables Open table format tables in newer CDP versions, with snapshot metadata usable for incremental reads. | Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | |
| Views SQL views that can present curated, sync-ready projections of raw lake data. | Medications Prescription and medication-list data within the patient record. | |
| Partitions Table partitions (often by date) that incremental extraction jobs use to scope reads. | Allergies Allergy and intolerance entries in the clinical record. | |
| Object store / HDFS files Underlying Parquet or ORC files on HDFS or cloud storage backing the tables. | Immunizations Vaccination history exposed for registries and patient apps. | |
| Databases Logical namespaces in the shared Hive Metastore that group tables for access control and syncs. | Documents Clinical notes and attachments referenced from the chart. | |
| Hive tables Warehouse tables queried over JDBC/ODBC; classic managed tables are append-oriented. | Diagnostic reports Structured result reports grouping observations for a study or panel. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cloudera Data Platform–eClinicalWorks connection.
Changes in Cloudera Data Platform or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Cloudera Data Platform or eClinicalWorks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Cloudera Data Platform or eClinicalWorks record.
Track your Cloudera Data Platform ⇄ eClinicalWorks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Cloudera Data Platform and eClinicalWorks.
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 Cloudera Data Platform 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.
Pick the Cloudera Data Platform 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.
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 Cloudera Data Platform and eClinicalWorks: authenticate both systems, choose the objects to sync (such as Cloudera Data Platform's Iceberg tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Cloudera Data Platform and eClinicalWorks: Cross-tool reporting; Where eClinicalWorks accepts updates: operational write-back; History that outlives the tool. Combine eClinicalWorks's data with data from every other synced system to answer questions no single tool can.
Cloudera Data Platform: JDBC/ODBC over Hive and Impala SQL endpoints, plus REST management APIs. Authentication: Kerberos, LDAP, or workload user credentials, often brokered through the Knox gateway. 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. 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. Cloudera Data Platform: Tables can live in multiple storage engines with different update semantics: Kudu and Iceberg tables support row-level updates, while classic Hive tables are append-oriented. Stacksync's field mapping accounts for these differences between Cloudera Data Platform and eClinicalWorks 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 Cloudera Data Platform and eClinicalWorks records are not retained after a sync operation.
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 Cloudera Data Platform and eClinicalWorks.