Two-way sync
Changes in eClinicalWorks or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Pigment holds the financial truth: who the customers are, what they were billed, what they paid. eClinicalWorks is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Metrics, Dimension lists, Tables, Scenarios in Pigment and Encounters, Practitioners, Observations, Medications in eClinicalWorks in sync, bi-directionally and in real time. Whatever records eClinicalWorks keeps and whatever events it produces, the overlap with Pigment is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
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 | Pigment objects | |
|---|---|---|
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Medications Prescription and medication-list data within the patient record. | Users and permissions Access controls governing which model areas a sync can touch | |
| Allergies Allergy and intolerance entries in the clinical record. | Applications Planning models organized by domain such as finance, sales, or workforce | |
| Immunizations Vaccination history exposed for registries and patient apps. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | |
| Documents Clinical notes and attachments referenced from the chart. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Pigment connection.
Changes in eClinicalWorks or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Pigment 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 Pigment record.
Track your eClinicalWorks ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Pigment.
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 Pigment 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 Pigment 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 Pigment: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Practitioners and Observations), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both eClinicalWorks and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on eClinicalWorks: HL7 interface feeds push event messages as they occur; the FHIR API is polled. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Pigment side: Metrics, Dimension lists, Tables, Scenarios, plus custom fields where Pigment exposes them. On the eClinicalWorks side: Encounters, Practitioners, Observations, Medications. 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 Pigment: Where eClinicalWorks collects payments or triggers charges: events land in Pigment; Where eClinicalWorks tracks people or companies: one identity; Where eClinicalWorks handles customer conversations: billing context in view. Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
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 Pigment.