Integration Products | Campaign Creators

eClinicalWorks HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:21:02 AM
Integration Assessment
Integration Assessment · Healthcare

eClinicalWorks × HubSpot

How a practice on eClinicalWorks can bring appointment status, completed visits, provider and location context, and referral sources into a HIPAA-configured HubSpot portal, so patient acquisition, recall outreach and patient experience run on real scheduling data, with only the minimum necessary information leaving the EHR.

eClinicalWorks EHR & PMFHIR R4 APIsSMART on FHIRBulk FHIR exportHL7 scheduling interfaceHIPAA-configured HubSpot
Platform ownereClinicalWorks
Integration typeCustom build on FHIR R4 and HL7 interfaces
Primary directioneClinicalWorks → HubSpot
FeasibilityBuildable, practice-enabled
API accessOpen with conditions
01 — Summary

Does eClinicalWorks integrate with HubSpot?

eClinicalWorks runs the EHR and practice management work for many ambulatory practices. Scheduling, registration and the clinical record live there. Growth and patient experience teams need a small part of that data in HubSpot: did the person who asked for an appointment book one, did they come in, which referral source sent them, and who is due to come back.

API access
Open APIOpen with conditionsGated API

Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.

Open with conditions. The certified FHIR APIs are documented publicly. The practice activates them through On-Demand Activation, and HL7 scheduling interfaces are ordered from eClinicalWorks.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

eClinicalWorks publishes certified FHIR R4 APIs and standard HL7 interfaces, so HubSpot can track each patient from appointment request to completed visit, once the practice enables access and the portal is set up for HIPAA.

Campaign Creators assessment

eClinicalWorks offers provider-facing FHIR R4 APIs (SMART on FHIR apps, backend services and bulk multi-patient export) through its FHIR developer portal, patient-facing FHIR APIs through healow, and HL7 interfaces for demographics, scheduling and provider directories. Each practice turns on FHIR APIs in its own eClinicalWorks system, so access is enabled practice by practice. The certified FHIR APIs carry a published limit of 25 calls per minute per base URL, so CC designs around bulk export and the HL7 scheduling feed rather than per-patient polling. Every patient record that comes from eClinicalWorks is protected health information (PHI). The HubSpot portal must be on an Enterprise subscription with Sensitive Data turned on, the HIPAA options selected and HubSpot's terms and BAA accepted, before any patient data arrives. The client's privacy officer decides what is stored and how it is used.

Scorecard
Data richnessHigh
Real-time changesVia HL7 feed
API accessPractice-enabled
Build complexityMod–High

Ratings are CC judgments from eClinicalWorks' public interoperability and certification materials and HubSpot's Sensitive Data documentation. Interface availability, costs and limits for the client's practice are confirmed with eClinicalWorks during discovery.

Strength

Standards on both sides

Certified FHIR R4 APIs cover patients, providers, locations and visits, and eClinicalWorks supports HL7 scheduling messages for new, changed and cancelled appointments. Both are open standards CC builds on directly.

Plan for

A tight API rate limit

The certified FHIR endpoints allow 25 calls per minute per base URL and return HTTP 429 above that. The sync module uses bulk export for nightly refresh and the HL7 feed for real-time appointment changes.

Gate

Practice enablement and HIPAA setup first

The practice activates FHIR APIs and the app in eClinicalWorks and orders the scheduling interface. In HubSpot, a Super Admin turns on Sensitive Data, selects the HIPAA options and accepts the terms and BAA before any patient data is written.

02 — API modules

Which eClinicalWorks APIs does the integration use?

Seven areas matter to HubSpot. Three carry the integration, two add context, one is a compliance gate, and one stays in eClinicalWorks by design.

Core

FHIR R4 APIs (provider-facing)

Certified FHIR R4 · SMART on FHIR · backend services

Standards-based read access to patient demographics, practitioners, organizations, locations and encounters, through eClinicalWorks' FHIR developer portal.

  • Backend services apps for server-to-server sync
  • Certified APIs offered to developers at no cost today; eClinicalWorks commits to 30 days' notice of any fee
  • Practice enables FHIR APIs in its own system
Core

Bulk FHIR export

Multi-patient backend export

One export request returns many patients' approved resources, so the nightly refresh does not spend the per-minute call budget patient by patient.

  • Patients, encounters, providers and locations in one job
  • Completed visits update deals and last-visit dates
  • Patient groups for export confirmed in discovery
Core

HL7 scheduling interface

HL7 v2 SIU · S12, S14, S15

eClinicalWorks sends a message when an appointment is booked, modified or cancelled. This is the real-time trigger that moves the HubSpot patient acquisition deal.

  • New appointment, modification and cancellation messages
  • Provider and location on each appointment
  • Ordered for the practice through eClinicalWorks; confirm cost and lead time
Booking

healow patient-facing APIs & Open Access

healow FHIR developer portal · online booking

healow covers patient-facing apps, including scheduling platforms, and Open Access lets patients book online from the practice website, patient portal or healow app.

  • HubSpot landing pages can link to Open Access booking
  • Online bookings arrive through the same scheduling feed
  • Booking from HubSpot through healow is optional, confirmed in discovery
Context

Providers, locations & referrals

FHIR Practitioner, Location · HL7 MFN

Who the patient sees and where, plus the outside clinicians who send patients. eClinicalWorks keeps referring provider lists in sync through HL7 provider directory messages.

  • Providers and locations as HubSpot custom object records
  • Referring providers as contacts, their practices as companies
  • Referral source on each appointment confirmed in discovery
Compliance gate

HubSpot HIPAA configuration

Enterprise · Sensitive Data · BAA

HubSpot supports HIPAA-covered data through its Sensitive Data feature. Patient properties are created as Sensitive Data and flagged as PHI.

  • Enterprise subscription required
  • Sensitive properties cannot be used in personalization tokens
  • Privacy officer approves fields and uses in writing
Stays in eClinicalWorks

Clinical record

Problems, results, medications, notes

Diagnoses, lab and imaging results, medications, orders and progress notes stay in eClinicalWorks. HubSpot receives none of them by default.

  • No clinical detail in HubSpot unless approved
  • Recall outreach uses due dates, not diagnoses
  • Any exception is documented by the privacy officer
03 — Framework

How does the eClinicalWorks HubSpot integration work?

eClinicalWorks sends HL7 scheduling messages to a CC-hosted listener as appointments change, and a nightly bulk FHIR export refreshes patients, visits, providers and locations within the published rate limit. The integration layer keeps only the approved fields, matches each patient to one HubSpot contact and writes in batches. HubSpot sends appointment requests back to the practice's scheduling team; booking from HubSpot is optional.

eClinicalWorks
HL7 scheduling feedSIU new, modified, cancelled
Bulk FHIR exportpatients, encounters, nightly
FHIR R4 APIsPractitioner, Location, Organization
healow & Open Accessonline booking
CC integration layer
Secure intakeHL7 listener and rate-aware FHIR client
Minimum-necessary filterdrops clinical and unapproved fields
Identity resolvereCW patient ID · email · mobile
Stage engineappointments and visits → deal stages
HubSpot writerSensitive Data properties, batch upserts, replay
HubSpot
Contactspatients and referring providers (PHI flagged)
Dealspatient acquisition pipeline
Provider & Location (custom objects)who and where
Companiesreferring practices
Lists, workflows & reportsbooking follow-up, recall, satisfaction
eClinicalWorks → HubSpot (appointment status, visits, approved patient fields, providers, referrals)HubSpot → eClinicalWorks (appointment requests to the scheduling team; optional booking)
Principle

eClinicalWorks owns the patient chart

Scheduling, registration and every clinical fact are worked in eClinicalWorks. HubSpot never edits a chart or an appointment unless booking is in scope.

Principle

Minimum necessary, by field

Each field that reaches HubSpot is on a list the privacy officer signed. The filter in the integration layer drops everything else before it is written.

Principle

PHI is protected in HubSpot

Patient properties are Sensitive Data flagged as PHI, access is limited by team, and messages are designed without sensitive personalization tokens.

04 — Process

What does eClinicalWorks HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Compliance comes first: no patient data is written until HubSpot's HIPAA setup and the field list are approved.

1

Compliance & HubSpot HIPAA setup

Work with the privacy officer to define permitted uses (scheduling follow-up, recall, satisfaction, marketing) and the minimum necessary field list. Confirm the Enterprise subscription; a Super Admin turns on Sensitive Data, selects the HIPAA options and accepts the terms and BAA.

Gate to next phaseSigned data use memo and HubSpot HIPAA settings on
2

eClinicalWorks access

Register the backend services app on eClinicalWorks' FHIR developer portal. The practice turns on FHIR APIs through On-Demand Activation and activates the app, then orders the HL7 scheduling interface from eClinicalWorks.

Gate to next phaseTest export and test scheduling messages received
3

Identity & message ownership

Agree the match order: eClinicalWorks patient ID, then email, then mobile. Decide, per message type, whether healow or HubSpot sends it (reminders, recall, surveys).

Gate to next phaseSigned match rules and sender-of-record matrix
4

HubSpot data model

Create PHI-flagged Sensitive Data properties, the Provider and Location custom objects, the patient acquisition pipeline, referral associations and team permissions in the production portal, since sandboxes do not support Sensitive Data.

Gate to next phaseSchema and permissions approved
5

Build

Build the HL7 listener, the rate-aware FHIR client and bulk export job, the minimum-necessary filter, identity resolver, stage engine, HubSpot writer and error replay.

Gate to next phaseAll agreed messages and exports flowing end to end with test data
6

Backfill

Load upcoming appointments, providers, locations, referring providers and the agreed set of active patients, within the approved field list.

Gate to next phaseCounts reconcile to eClinicalWorks reports for the agreed window
7

Workflows, parallel run & launch

Build booking follow-up, recall and satisfaction workflows with sends paused, have the privacy officer review each message, run two weeks in parallel, then switch on.

Gate to next phasePrivacy officer sign-off and five days with no unresolved sync errors
05 — Data mapping

What does the eClinicalWorks HubSpot integration sync?

FHIR resource names follow the FHIR R4 standard and HL7 message types follow eClinicalWorks' published scheduling support. Exact element paths and segment fields are confirmed against the practice's interface specification in discovery. Every row is subject to the privacy officer's field list.

eCW fieldHubSpot propertyObjectDirectionNotes
Patients · FHIR Patient (bulk export)
Patient IDecw_patient_idContactECW → HSMatch key #1. Sensitive Data; uniqueness enforced in the integration layer.
Namefirstname, lastnameContactECW → HSPHI once linked to the practice. Fill blanks only.
EmailemailContactECW → HSMatch key #2. Links the patient to the person who enquired.
Mobile phonemobilephoneContactECW → HSNormalize to E.164. Match key #3.
Postal codezipContactECW → HSFor location reporting. Full address left in eClinicalWorks.
Primary providerProvider associationContactECW → HSAssociated to the Provider record. Element confirmed in discovery.
Contact preferences and consentecw_contact_consentContactECW → HSSource field confirmed in discovery. Feeds HubSpot subscription types.
Appointments · HL7 scheduling feed
Appointment IDecw_appointment_idDealECW → HSOne deal per new-patient appointment request.
New appointment (S12)dealstage = BookedDealECW → HSRequested to booked. Online bookings arrive the same way.
Modification (S14)ecw_appointment_status, ecw_next_appointment_dateDealECW → HSUpdates date and status.
Cancellation (S15)dealstage, ecw_appointment_statusDealECW → HSCancelled appointments enter a rebooking workflow.
Appointment dateecw_next_appointment_dateContactECW → HSSensitive Data. Not used in personalization tokens.
Visit typeecw_service_lineDealECW → HSMapped to a service-line category. Raw visit type left in eClinicalWorks.
Provider, locationProvider and Location associationsDealECW → HSFor location and provider reporting.
Visits · FHIR Encounter (bulk export)
Completed encounterdealstage = CompletedDealECW → HSMarks the acquisition deal complete; can trigger a survey.
Encounter dateecw_last_visit_dateContactECW → HSDrives recall timing. No reason for visit or diagnosis.
Providers, locations & referrals
Practitioner ID, name, specialtyecw_provider_id, name, ecw_specialtyProviderECW → HSCustom object, refreshed nightly.
Location ID, name, addressecw_location_id, name, addressLocationECW → HSCustom object for each office.
Referring providerContact (referring provider)ContactECW → HSFrom the referring provider directory. Not a patient record.
Referring practiceCompanyCompanyECW → HSReferring provider associated to their practice.
Referral countecw_referrals_countContactECW → HSComputed per referring provider. Referral field on appointments confirmed in discovery.
Acquisition & outreach
Appointment request (HubSpot form)Deal (Requested)DealHS → ECWRouted to the scheduling team. Free-text symptoms are not collected.
Online booking linkhealow Open AccessDealHS → ECWOptional. HubSpot pages link to the practice's online booking.
Recall due dateecw_recall_due_dateContactECW → HSLast visit plus an agreed interval, or eClinicalWorks recall data if available. Confirmed in discovery.
Post-visit surveyHubSpot feedback surveyContactECW → HSSent after a completed visit, unless healow is the agreed sender.
New-patient indicatorecw_new_patientDealECW → HSSeparates acquisition from returning visits. Logic confirmed in discovery.
06 — Auth & API

How are authentication and API limits handled?

eClinicalWorks grants API access through its developer portals and practice-level activation; HubSpot holds PHI only in a HIPAA-configured Enterprise portal. Values eClinicalWorks does not publish are marked for confirmation.

TopiceCWHubSpot
Access modelProvider-facing and bulk/backend apps register on eClinicalWorks' FHIR developer portal; patient-facing apps on healow's. The practice enables FHIR APIs through On-Demand Activation. HL7 interfaces are ordered through eClinicalWorks; confirm cost.Self-serve in the client portal. Sensitive Data and custom objects need an Enterprise hub.
InterfacesCertified FHIR R4 APIs (SMART on FHIR, backend services, bulk export); HL7 v2 interfaces for demographics, scheduling (SIU) and provider directories (MFN).REST APIs: CRM objects, associations, custom objects, imports.
AuthenticationOAuth 2.0 under the SMART on FHIR profile, with backend services for server-to-server sync. HL7 transport and credentials are agreed with eClinicalWorks. Confirm in discovery.Private app access token, approved by the user to read Sensitive Data, or OAuth 2.0 public app.
Rate limitsPublished: no more than 25 calls per minute per base URL for the FHIR resource, authorize and token endpoints. Above that, the app is blocked for the rest of the minute with HTTP 429.Per-10-second burst and daily limits by subscription tier.
Change detectionNo event subscription for the FHIR APIs is described in public materials. The HL7 scheduling feed carries appointment changes in real time; bulk export refreshes the rest nightly. Confirm in discovery.Writes are immediate; batch endpoints handle volume.
Write accessCertified FHIR APIs are used read-only. Booking from HubSpot, if in scope, goes through healow scheduling. Confirm with eClinicalWorks.Workflows create tasks or tickets for the scheduling team.
PHI handlingData leaves eClinicalWorks only through the activated app, the ordered interface and the approved field list.Sensitive Data with the HIPAA options and BAA; PHI-flagged properties; no sensitive personalization tokens; not available in sandboxes.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

HubSpot must be HIPAA-configured firstHigh

Sensitive Data needs an Enterprise subscription, and the HIPAA options, terms and BAA are accepted before any patient data is written. Make this a client-owned dependency in the SOW.

Permitted uses are the privacy officer's callHigh

Whether a message is a treatment or operations communication, or marketing that needs patient authorization under HIPAA, is decided by the client's privacy officer, message by message.

A 25-calls-per-minute FHIR limitHigh

Per-patient polling cannot scale under the published limit. The design uses bulk export for refresh and the HL7 feed for real-time changes, and the FHIR client throttles itself to stay under the limit.

Appointment data comes through an interfaceMedium

Real-time appointment status comes from the HL7 scheduling interface, which the practice orders through eClinicalWorks. Confirm cost and lead time before the SOW is final.

Two systems can message the same patientMedium

healow includes patient engagement tools such as online booking and outreach. Each message type gets one sender, recorded in the SOW.

Visit types can reveal conditionsMedium

A visit type or location can imply a diagnosis. The integration maps visit types to broad service lines the privacy officer approves.

Opportunities in HubSpot

Request-to-visit attributionHigh value

Each appointment request from a HubSpot form, ad or landing page is tracked to booked and completed, so marketing is judged on visits, not form fills.

Referral source reportingHigh value

Referring providers and their practices are HubSpot records with referral counts, so physician liaisons see who sends patients and who has stopped.

Recall and preventive outreachHigh value

Patients past their recall date enter an approved outreach workflow that invites them to book, without naming a condition.

Cancellation recoveryMedium value

A cancellation message starts a rebooking task or approved message, so the slot and the patient are not lost.

Patient satisfaction after each visitMedium value

A completed visit triggers a HubSpot feedback survey, and low scores open a ticket for the office manager.

Location and provider growth viewsMedium value

New patients, booked visits and referral volume by location and provider in one set of HubSpot dashboards.

Core patient journey

From appointment request to the next visit.

The integration follows one patient through acquisition and return, with eClinicalWorks running scheduling and care, and HubSpot running outreach and reporting within the privacy officer's rules.

  1. A HubSpot form or online booking captures the request; the appointment is booked in eClinicalWorks.
  2. The scheduling message moves the HubSpot deal to Booked; the completed encounter marks it Completed and can trigger a survey.
  3. The referring provider and the marketing source are both credited for the new patient.
  4. When the recall date passes without a booking, an approved workflow invites the patient back.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the ecw_ prefix in an eClinicalWorks property group. Patient properties are created as Sensitive Data and flagged as PHI. HubSpot does not allow unique values on Sensitive Data properties, so the integration layer enforces uniqueness.

Internal nameLabelObjectTypeSource / logic
ecw_patient_ideClinicalWorks Patient IDContactSingle-line text (Sensitive, PHI)FHIR Patient ID; match key
ecw_contact_consentContact ConsentContactDropdown (Sensitive, PHI)Patient contact preferences
ecw_next_appointment_dateNext AppointmentContactDate (Sensitive, PHI)Earliest future booked appointment
ecw_last_visit_dateLast VisitContactDate (Sensitive, PHI)Latest completed encounter
ecw_recall_due_dateRecall DueContactDate (Sensitive, PHI)Last visit plus agreed interval
ecw_appointment_ideClinicalWorks Appointment IDDealSingle-line text (Sensitive, PHI)Scheduling message appointment ID
ecw_appointment_statusAppointment StatusDealDropdown (Sensitive, PHI)Booked, modified, cancelled, completed
ecw_service_lineService LineDealDropdown (Sensitive, PHI)Approved mapping of visit types
ecw_provider_ideClinicalWorks Provider IDProviderSingle-line textFHIR Practitioner ID; unique
ecw_specialtySpecialtyProviderDropdownPractitioner record
ecw_location_ideClinicalWorks Location IDLocationSingle-line textFHIR Location ID; unique
ecw_referrals_countReferralsContactNumberReferring providers only; computed in the integration layer
09 — Scope builder

Interactive scope builder

Choose the data and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Every field is subject to the privacy officer's approval. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
eCW × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

eClinicalWorks HubSpot integration FAQ

Does eClinicalWorks integrate with HubSpot?

Yes. eClinicalWorks publishes certified FHIR R4 APIs (SMART on FHIR apps, backend services and bulk multi-patient export) through its developer portal, plus HL7 v2 interfaces for scheduling, demographics and provider directories. Campaign Creators builds a custom integration layer on these standards once the practice activates API access and HubSpot is HIPAA-configured.

What data syncs between eClinicalWorks and HubSpot?

Appointment requests, bookings, modifications, cancellations and completed visits sync from eClinicalWorks to HubSpot deals, alongside approved patient fields, providers, locations and referral sources on contacts and custom objects. HubSpot can send appointment requests back to the scheduling team, and online booking through healow Open Access is optional.

Which system owns which data?

eClinicalWorks owns the patient chart: scheduling, registration and every clinical fact are worked there, and HubSpot never edits a chart or appointment unless booking is in scope. HubSpot owns outreach and reporting, holding only the minimum-necessary fields the privacy officer approves, flagged as Sensitive Data and PHI.

What does setting up the eClinicalWorks HubSpot integration involve?

Seven phases, each closed by a client sign-off: HIPAA compliance setup, eClinicalWorks API and HL7 interface access, identity and message-ownership rules, the HubSpot data model with Sensitive Data properties and Provider and Location custom objects, the build, backfill, and a two-week parallel run before workflows switch on.

How long does the integration take and what does it cost?

Timeline and cost depend on the practice's eClinicalWorks interfaces, the approved field list and the HubSpot HIPAA setup in scope. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.