Skip to content
Security and identity ⇄ Business productivity

Active Directory to eClinicalWorks integration — real-time, two-way sync

Keep Active Directory 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Active Directory and eClinicalWorks

Keep the users, groups, and profile details that eClinicalWorks and Active Directory share consistent in real time, so who can work in eClinicalWorks always matches who your directory in Active Directory says belongs there.

Active Directory is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. eClinicalWorks is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.

Stacksync syncs Documents, Diagnostic reports, Patients, Appointments in eClinicalWorks with Service principals & applications, Organizational units, Organizational contacts, Users in Active Directory bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.

That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.

Common use cases

  • 01 Push referral or intake data captured in external forms into the EHR via HL7 interfaces.
  • 02 Sync patient demographics and appointments into a CRM so patient outreach and intake teams work from current data.
  • 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
  • 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.

Common sync patterns

Mirror group and role membership

Moving a user between groups or roles in Active Directory updates their team, permission set, or seat in eClinicalWorks, so what someone can do reflects where they sit in the directory.

One record per person

People matched across both systems on email or an external ID stay linked, so every account and action in eClinicalWorks ties back to the right identity in Active Directory.

Provision access when someone joins

A user added to Active Directory, or moved into a group inside it, gets the matching account or membership created in eClinicalWorks, so a new hire can start working without a separate setup ticket.

What you can sync between Active Directory and eClinicalWorks

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.

Active Directory objects eClinicalWorks objects How this pairing syncs
Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. Diagnostic reports Structured result reports grouping observations for a study or panel. Devices is specific to Active Directory and Diagnostic reports to eClinicalWorks — each maps to any object or custom field on the other side.
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Directory roles is specific to Active Directory and Patients to eClinicalWorks — each maps to any object or custom field on the other side.
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Service principals & applications is specific to Active Directory and Appointments to eClinicalWorks — each maps to any object or custom field on the other side.
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. Encounters Visit records tying diagnoses, providers, and billing context together. Organizational units is specific to Active Directory and Encounters to eClinicalWorks — each maps to any object or custom field on the other side.
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Practitioners Provider records used to keep directories and scheduling systems consistent. Organizational contacts is specific to Active Directory and Practitioners to eClinicalWorks — each maps to any object or custom field on the other side.
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Users is specific to Active Directory and Observations to eClinicalWorks — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and eClinicalWorks

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.

Active Directory eClinicalWorks Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

DeliveryEach detected change is written to eClinicalWorks through its API, with automatic retries and rate-limit backoff.

eClinicalWorks Active Directory Interval-based propagation

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 Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
What ships with Active Directory ⇄ eClinicalWorks

Connect Active Directory and eClinicalWorks for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–eClinicalWorks connection.

Real-time

Two-way sync

Changes in Active Directory or eClinicalWorks instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or eClinicalWorks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Active Directory or eClinicalWorks record.

Observability

Monitoring

Track your Active Directory ⇄ eClinicalWorks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Active Directory and eClinicalWorks.

How the Active Directory and eClinicalWorks connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

eClinicalWorks

Integration surface
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
Change detection
HL7 interface feeds push event messages as they occur; the FHIR API is polled
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and interface throughput agreements
How it works

How to connect Active Directory to eClinicalWorks — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Active Directory 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Active Directory connected
    eClinicalWorks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Active Directory ⇄ eClinicalWorks
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Active Directory eClinicalWorks
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and eClinicalWorks integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 437 integrations available for Active Directory and eClinicalWorks.

Popular · 8 of 437
All Active Directory integrations All eClinicalWorks integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own