Two-way sync
Changes in eClinicalWorks or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep eClinicalWorks and Ukg Pro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in eClinicalWorks keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Ukg Pro is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Diagnostic reports, Patients, Appointments, Encounters in eClinicalWorks with Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details in Ukg Pro bi-directionally and in real time. A person added, moved, or offboarded in Ukg Pro creates or updates the matching user in eClinicalWorks within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where eClinicalWorks captures details of its own, such as a corrected contact or a login identity, those can flow back to Ukg Pro in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Department, team, and reporting-line changes from Ukg Pro keep the groups, queues, or projects in eClinicalWorks assigned to the right people.
When someone changes teams or managers in Ukg Pro, the queues, ownership, or approvals in eClinicalWorks update to match, so work reaches whoever holds the role now.
A new hire recorded in Ukg Pro creates the matching user in eClinicalWorks with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
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 | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. | Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. | Appointments is specific to eClinicalWorks and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Encounters Visit records tying diagnoses, providers, and billing context together. | Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. | Encounters is specific to eClinicalWorks and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Practitioners Provider records used to keep directories and scheduling systems consistent. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Practitioners is specific to eClinicalWorks and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. | Configuration Setup (Code Tables) Reference data such as jobs, locations, positions, earnings, and deduction codes; used to resolve and validate field values when mapping records during sync. | Observations is specific to eClinicalWorks and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Medications Prescription and medication-list data within the patient record. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Medications is specific to eClinicalWorks and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Allergies Allergy and intolerance entries in the clinical record. | Employee (Person Details) Core worker record with demographics and identifiers; read by listing employee IDs then fetching each profile, and created on hire via the personnel/onboarding endpoints. | Allergies is specific to eClinicalWorks and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. |
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.
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 Ukg Pro through its API, with automatic retries and rate-limit backoff.
DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to eClinicalWorks through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Ukg Pro connection.
Changes in eClinicalWorks or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Ukg Pro 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 Ukg Pro record.
Track your eClinicalWorks ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Ukg Pro.
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 Ukg Pro 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 Ukg Pro 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 Ukg Pro: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Appointments and Encounters), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the eClinicalWorks side: Diagnostic reports, Patients, Appointments, Encounters, plus custom fields where eClinicalWorks exposes them. On the Ukg Pro side: Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details. 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 Ukg Pro: Org and team structure kept current; Where eClinicalWorks routes or assigns work by person: assignments follow the org; Onboarding: access ready on day one. Department, team, and reporting-line changes from Ukg Pro keep the groups, queues, or projects in eClinicalWorks assigned to the right people.
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. Ukg Pro: REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services. Authentication: Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint. 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. Ukg Pro: UKG does not publish numeric rate limits; the gateway throttles per client per rolling window and returns HTTP 429, with a recommended roughly one-second looping backoff before resuming. Stacksync's field mapping accounts for these differences between eClinicalWorks and Ukg Pro without custom code.
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 439 integrations available for eClinicalWorks and Ukg Pro.