Two-way sync
Changes in eClinicalWorks or Full Enrich instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and Full Enrich in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two tools in the daily stack often hold overlapping information: the same people, the same companies, or the same pieces of work, described twice. The tools do different jobs, so consolidating is not the answer; the overlap just needs to stop drifting.
Stacksync syncs Practitioners, Observations, Medications, Allergies in eClinicalWorks with Enrichment results, Emails, Phone numbers, Credits in Full Enrich in real time. You choose which records overlap, map the fields that should match, and pick a direction or let changes flow both ways. From then on, an update made in either tool is reflected in the other within seconds, without exports or copy-paste.
Because the sync is field-level, each tool keeps its own extras; only the shared data is held in agreement.
Information that originates in eClinicalWorks stays current in Full Enrich instead of going stale after a one-time paste.
When work started in one tool continues in the other, the shared fields travel with it automatically.
Contact and company details corrected in either tool update the other, so nobody works from the old version.
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 | Full Enrich objects | |
|---|---|---|
| Diagnostic reports Structured result reports grouping observations for a study or panel. | Enrichment results Completed records fetched by request ID or delivered via webhook. | |
| Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | Emails Returned addresses with verification status, written back to the CRM or database. | |
| Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. | Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | |
| Encounters Visit records tying diagnoses, providers, and billing context together. | Credits Account balance consumed on successful finds; monitored to pace sync jobs. | |
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Contacts The person inputs (name plus company or domain) sent for enrichment. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Full Enrich connection.
Changes in eClinicalWorks or Full Enrich instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Full Enrich 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 Full Enrich record.
Track your eClinicalWorks ⇄ Full Enrich sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Full Enrich.
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 Full Enrich 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 Full Enrich 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 Full Enrich: 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.
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 Full Enrich: Where Full Enrich is where the team documents or plans: keep its data fed; Handoffs between teams; Where both tools track people or companies: one consistent record. Information that originates in eClinicalWorks stays current in Full Enrich instead of going stale after a one-time paste.
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. Full Enrich: REST API with asynchronous bulk enrichment endpoints. Authentication: API key (Bearer token). Stacksync manages authentication, retries, and rate limits on both sides.
eClinicalWorks: Traditional integrations run over HL7 v2 interfaces (ADT for demographics, SIU for scheduling, ORU for results), which are push-based message feeds rather than request/response APIs. Full Enrich: Enrichment is asynchronous: batches are submitted, run through a waterfall of upstream data providers, and results arrive by webhook or a later fetch, so syncs must handle pending states. Stacksync's field mapping accounts for these differences between eClinicalWorks and Full Enrich 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 Full Enrich 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 eClinicalWorks and Full Enrich.