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.
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.
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.
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.
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.
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.
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.
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.
FHIR R4 APIs (provider-facing)
Certified FHIR R4 · SMART on FHIR · backend servicesStandards-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
Bulk FHIR export
Multi-patient backend exportOne 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
HL7 scheduling interface
HL7 v2 SIU · S12, S14, S15eClinicalWorks 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
healow patient-facing APIs & Open Access
healow FHIR developer portal · online bookinghealow 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
Providers, locations & referrals
FHIR Practitioner, Location · HL7 MFNWho 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
HubSpot HIPAA configuration
Enterprise · Sensitive Data · BAAHubSpot 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
Clinical record
Problems, results, medications, notesDiagnoses, 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
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 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.
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.
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.
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.
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.
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.
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).
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.
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.
Backfill
Load upcoming appointments, providers, locations, referring providers and the agreed set of active patients, within the approved field list.
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.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Patients · FHIR Patient (bulk export) | ||||
| Patient ID | ecw_patient_id | Contact | ECW → HS | Match key #1. Sensitive Data; uniqueness enforced in the integration layer. |
| Name | firstname, lastname | Contact | ECW → HS | PHI once linked to the practice. Fill blanks only. |
| Contact | ECW → HS | Match key #2. Links the patient to the person who enquired. | ||
| Mobile phone | mobilephone | Contact | ECW → HS | Normalize to E.164. Match key #3. |
| Postal code | zip | Contact | ECW → HS | For location reporting. Full address left in eClinicalWorks. |
| Primary provider | Provider association | Contact | ECW → HS | Associated to the Provider record. Element confirmed in discovery. |
| Contact preferences and consent | ecw_contact_consent | Contact | ECW → HS | Source field confirmed in discovery. Feeds HubSpot subscription types. |
| Appointments · HL7 scheduling feed | ||||
| Appointment ID | ecw_appointment_id | Deal | ECW → HS | One deal per new-patient appointment request. |
| New appointment (S12) | dealstage = Booked | Deal | ECW → HS | Requested to booked. Online bookings arrive the same way. |
| Modification (S14) | ecw_appointment_status, ecw_next_appointment_date | Deal | ECW → HS | Updates date and status. |
| Cancellation (S15) | dealstage, ecw_appointment_status | Deal | ECW → HS | Cancelled appointments enter a rebooking workflow. |
| Appointment date | ecw_next_appointment_date | Contact | ECW → HS | Sensitive Data. Not used in personalization tokens. |
| Visit type | ecw_service_line | Deal | ECW → HS | Mapped to a service-line category. Raw visit type left in eClinicalWorks. |
| Provider, location | Provider and Location associations | Deal | ECW → HS | For location and provider reporting. |
| Visits · FHIR Encounter (bulk export) | ||||
| Completed encounter | dealstage = Completed | Deal | ECW → HS | Marks the acquisition deal complete; can trigger a survey. |
| Encounter date | ecw_last_visit_date | Contact | ECW → HS | Drives recall timing. No reason for visit or diagnosis. |
| Providers, locations & referrals | ||||
| Practitioner ID, name, specialty | ecw_provider_id, name, ecw_specialty | Provider | ECW → HS | Custom object, refreshed nightly. |
| Location ID, name, address | ecw_location_id, name, address | Location | ECW → HS | Custom object for each office. |
| Referring provider | Contact (referring provider) | Contact | ECW → HS | From the referring provider directory. Not a patient record. |
| Referring practice | Company | Company | ECW → HS | Referring provider associated to their practice. |
| Referral count | ecw_referrals_count | Contact | ECW → HS | Computed per referring provider. Referral field on appointments confirmed in discovery. |
| Acquisition & outreach | ||||
| Appointment request (HubSpot form) | Deal (Requested) | Deal | HS → ECW | Routed to the scheduling team. Free-text symptoms are not collected. |
| Online booking link | healow Open Access | Deal | HS → ECW | Optional. HubSpot pages link to the practice's online booking. |
| Recall due date | ecw_recall_due_date | Contact | ECW → HS | Last visit plus an agreed interval, or eClinicalWorks recall data if available. Confirmed in discovery. |
| Post-visit survey | HubSpot feedback survey | Contact | ECW → HS | Sent after a completed visit, unless healow is the agreed sender. |
| New-patient indicator | ecw_new_patient | Deal | ECW → HS | Separates acquisition from returning visits. Logic confirmed in discovery. |
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.
| Topic | eCW | HubSpot |
|---|---|---|
| Access model | Provider-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. |
| Interfaces | Certified 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. |
| Authentication | OAuth 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 limits | Published: 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 detection | No 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 access | Certified 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 handling | Data 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. |
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
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.
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.
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.
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.
healow includes patient engagement tools such as online booking and outreach. Each message type gets one sender, recorded in the SOW.
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
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.
Referring providers and their practices are HubSpot records with referral counts, so physician liaisons see who sends patients and who has stopped.
Patients past their recall date enter an approved outreach workflow that invites them to book, without naming a condition.
A cancellation message starts a rebooking task or approved message, so the slot and the patient are not lost.
A completed visit triggers a HubSpot feedback survey, and low scores open a ticket for the office manager.
New patients, booked visits and referral volume by location and provider in one set of HubSpot dashboards.
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.
- A HubSpot form or online booking captures the request; the appointment is booked in eClinicalWorks.
- The scheduling message moves the HubSpot deal to Booked; the completed encounter marks it Completed and can trigger a survey.
- The referring provider and the marketing source are both credited for the new patient.
- When the recall date passes without a booking, an approved workflow invites the patient back.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ecw_patient_id | eClinicalWorks Patient ID | Contact | Single-line text (Sensitive, PHI) | FHIR Patient ID; match key |
| ecw_contact_consent | Contact Consent | Contact | Dropdown (Sensitive, PHI) | Patient contact preferences |
| ecw_next_appointment_date | Next Appointment | Contact | Date (Sensitive, PHI) | Earliest future booked appointment |
| ecw_last_visit_date | Last Visit | Contact | Date (Sensitive, PHI) | Latest completed encounter |
| ecw_recall_due_date | Recall Due | Contact | Date (Sensitive, PHI) | Last visit plus agreed interval |
| ecw_appointment_id | eClinicalWorks Appointment ID | Deal | Single-line text (Sensitive, PHI) | Scheduling message appointment ID |
| ecw_appointment_status | Appointment Status | Deal | Dropdown (Sensitive, PHI) | Booked, modified, cancelled, completed |
| ecw_service_line | Service Line | Deal | Dropdown (Sensitive, PHI) | Approved mapping of visit types |
| ecw_provider_id | eClinicalWorks Provider ID | Provider | Single-line text | FHIR Practitioner ID; unique |
| ecw_specialty | Specialty | Provider | Dropdown | Practitioner record |
| ecw_location_id | eClinicalWorks Location ID | Location | Single-line text | FHIR Location ID; unique |
| ecw_referrals_count | Referrals | Contact | Number | Referring providers only; computed in the integration layer |
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
Sources & verification
Based on public documentation. API access, interface costs, limits and field names are confirmed with eClinicalWorks and the client's privacy officer during discovery.
- eClinicalWorks certified EHR technology (FHIR APIs, developer portals, fees)
- eClinicalWorks interoperability (Platform for Open Development)
- eClinicalWorks FHIR developer portal
- eClinicalWorks practice management integrations (HL7 ADT, SIU, MFN)
- eClinicalWorks certification details and costs disclosure (FHIR rate limits)
- healow Open Access online scheduling
- HubSpot: Store sensitive data
- HubSpot Sensitive Data terms and BAA
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.
Ready to Get More From HubSpot?
Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.
.png?width=1920&height=553&name=cc-logo-color%20(2024).png)