Real-time
Two-way sync
Changes in eClinicalWorks or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Storage
eClinicalWorks to Sharepoint integration — real-time, two-way sync
Keep eClinicalWorks and Sharepoint 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 eClinicalWorks and Sharepoint
Land the records and documents that build up in eClinicalWorks into Sharepoint as they are created, and surface Sharepoint's file details on the eClinicalWorks records that point to them, without an export job to maintain.
eClinicalWorks and Sharepoint hold different kinds of data. eClinicalWorks carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Sharepoint holds files and the metadata that describes them. Where the two meet is narrow but real: much of what eClinicalWorks produces has to be kept somewhere durable, and many of the files Sharepoint stores are the very documents eClinicalWorks's records point to.
Stacksync syncs Diagnostic reports, Patients, Appointments, Encounters in eClinicalWorks with Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages in Sharepoint in real time. Records and attachments created in eClinicalWorks are written into Sharepoint as objects or files within seconds of being created. In the other direction, the metadata Sharepoint keeps about those files — name, location, owner, modified date — flows back onto the matching record in eClinicalWorks, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.
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 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.
- 04 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.
Common sync patterns
Archive what eClinicalWorks produces into Sharepoint
Records and events from eClinicalWorks — tickets, messages, orders, or issues — are written into Sharepoint as objects or files as they change, giving you a durable, addressable copy for retention and audit.
Where eClinicalWorks generates attachments: keep the files in Sharepoint
Documents attached to records in eClinicalWorks land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.
Where Sharepoint holds the source documents: file details on the record
A file's name, location, owner, and modified date from Sharepoint sync onto the matching record in eClinicalWorks, so whoever is working there sees the current version without switching tools.
What you can sync between eClinicalWorks and Sharepoint
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 | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Medications Prescription and medication-list data within the patient record. | Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. | Medications is specific to eClinicalWorks and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| Allergies Allergy and intolerance entries in the clinical record. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Allergies is specific to eClinicalWorks and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Immunizations Vaccination history exposed for registries and patient apps. | Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. | Immunizations is specific to eClinicalWorks and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Documents Clinical notes and attachments referenced from the chart. | Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. | Documents is specific to eClinicalWorks and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Diagnostic reports Structured result reports grouping observations for a study or panel. | List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. | Diagnostic reports is specific to eClinicalWorks and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. | Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. | Patients is specific to eClinicalWorks and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side. |
How changes propagate between eClinicalWorks and Sharepoint
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.
eClinicalWorks Sharepoint 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 Sharepoint through its API, with automatic retries and rate-limit backoff.
Sharepoint eClinicalWorks Sub-second propagation
DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.
DeliveryEach detected change is written to eClinicalWorks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
- Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with eClinicalWorks ⇄ Sharepoint
Connect eClinicalWorks and Sharepoint for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Sharepoint connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever eClinicalWorks or Sharepoint 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 eClinicalWorks or Sharepoint record.
Observability
Monitoring
Track your eClinicalWorks ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Sharepoint.
How the eClinicalWorks and Sharepoint connectors work
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
Sharepoint
- Integration surface
- Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
- Authentication
- OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
- Change detection
- Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
- Capabilities
- read · write · webhooks
- Rate limits
- SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works
How to connect eClinicalWorks to Sharepoint — 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.
- 01
Connect your apps
Authenticate eClinicalWorks and Sharepoint with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
eClinicalWorks
connected
Sharepoint
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the eClinicalWorks and Sharepoint 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.
objects · eClinicalWorks ⇄ SharepointCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
eClinicalWorks SharepointCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
eClinicalWorks and Sharepoint 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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 430 integrations available for eClinicalWorks and Sharepoint.
Popular · 7 of 430
-
eClinicalWorks ⇄ Egnyte -
eClinicalWorks ⇄ Amazon S3 -
eClinicalWorks ⇄ Box -
Sharepoint ⇄ Front -
Sharepoint ⇄ Amazon Seller Central -
Sharepoint ⇄ SendGrid -
Sharepoint ⇄ Twilio
No integrations match .
