athenahealth × HubSpot
How a provider group on athenaOne can bring appointment status, 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 athenahealth integrate with HubSpot?
athenaOne is the EHR and practice management platform for many provider groups. Scheduling, registration and the clinical record live there. Growth and patient experience teams need some of that data in HubSpot: did the person who asked for an appointment book one, did they show up, 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. Developer Portal registration and the Preview environment are self-serve. Production access to a practice follows athenahealth's onboarding steps; confirm steps and any fees.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
athenahealth publishes standards-based and proprietary APIs with event notifications, so HubSpot can track each patient from appointment request to completed visit, provided the portal is set up for HIPAA first.
Campaign Creators assessment
athenahealth offers FHIR R4 APIs, more than 800 proprietary athenaOne API endpoints, and FHIR Event Notifications that push an ID-only message when an appointment, patient, provider or referring provider changes. CC builds the integration on these: events tell the integration what changed, it fetches only the fields agreed with the client's privacy officer, and writes them to HubSpot. Every patient record that comes from athenaOne is protected health information (PHI), including a name next to an appointment. So 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 athenaOne data arrives. The client's compliance or privacy officer decides what is stored and how it may be used.
Ratings are CC judgments from athenahealth's public developer materials and HubSpot's Sensitive Data documentation. API access, fees, limits and event availability for the client's athenaOne contract are confirmed with athenahealth during discovery.
Standards-based change events
FHIR Event Notifications cover appointment schedule, reschedule, cancel, check-in and check-out, plus patient, provider and referring provider changes, delivered by signed rest-hook with retries.
Everything that leaves the EHR is PHI
Name, contact details and appointment dates from athenaOne are PHI in HubSpot. The field list follows the minimum necessary standard, and clinical detail stays in athenaOne unless the privacy officer approves it.
HubSpot's HIPAA setup comes first
Sensitive Data is an Enterprise feature. A Super Admin turns it on, selects Health/Medical Data and the HIPAA-covered entity or business associate option, and accepts the terms and BAA before the build writes any patient data.
Which athenahealth APIs does the integration use?
Seven areas matter to HubSpot. Four carry the integration, one adds context, one is a compliance gate, and one stays in athenaOne by design.
FHIR Event Notifications
FHIR R4 Subscriptions · rest-hookathenaOne pushes a notification when a subscribed resource changes. The payload is ID-only; the integration then fetches what it needs.
- Appointment.schedule, .reschedule, .cancel, .check-in, .check-out
- Patient, Provider and ReferringProvider create and update
- HMAC signature in the X-Hub-Signature header
Appointments
FHIR R4 · athenaOne appointments APIsAppointment status, date, department, provider and appointment type. Status moves the HubSpot patient acquisition deal from requested to booked to completed.
- Booked, rescheduled, cancelled, checked in, checked out
- Appointment type mapped to a service line, not a condition
- Changed Data Subscription as a polling fallback
Patients
FHIR Patient · athenaOne patients APIsThe demographic and contact fields the privacy officer approves, so HubSpot can match a patient to the person who first enquired.
- Name, email, mobile phone, postal code
- Primary department and provider
- Contact preferences and consent, confirmed in discovery
Providers & departments
Provider events · athenaOne department and provider APIsWho the patient sees and where. Providers and departments become HubSpot custom object records for location and service-line reporting.
- Provider name and specialty
- Department (location) name and address
- Growth reporting by location and provider
Referring providers
ReferringProvider eventsThe outside clinicians who send patients. They become HubSpot contacts with their practices as companies, so referral volume is measurable.
- Referring provider on each new-patient appointment
- Referral counts rolled up per provider and practice
- Physician liaison outreach in HubSpot
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 encounter notes stay in athenaOne. 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 athenahealth HubSpot integration work?
athenaOne sends signed, ID-only event notifications to a CC-hosted endpoint. The integration layer verifies each one, fetches the resource through the FHIR R4 or athenaOne APIs, keeps only the approved fields, matches the patient to one HubSpot contact and writes in batches. HubSpot sends appointment requests back to the practice's scheduling team, and booking into athenaOne is optional.
athenaOne owns the patient chart
Scheduling, registration and every clinical fact are worked in athenaOne. HubSpot never edits a chart or an appointment unless booking write-back 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 athenahealth 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.
athenahealth access
Register the app in athenahealth's Developer Portal, build against the Preview environment, request the event subscription scopes, and complete the steps athenahealth sets for production access to the practice.
Identity & message ownership
Agree the match order: athenaOne patient ID, then email, then mobile. Decide, per message type, whether athenaOne's patient engagement tools or HubSpot sends it (reminders, recall, surveys).
HubSpot data model
Create PHI-flagged Sensitive Data properties, the Provider and Department 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 signed event endpoint, resource fetcher, minimum-necessary filter, identity resolver, HubSpot writer, Changed Data Subscription fallback and error replay.
Backfill
Load upcoming appointments, providers, departments, 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 athenahealth HubSpot integration sync?
FHIR resource and event names follow athenahealth's published subscription guide. athenaOne API field names are confirmed against the client's practice in discovery. Every row is subject to the privacy officer's field list.
| athenaOne field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Patients · FHIR Patient, athenaOne patients | ||||
| Patient ID | ath_patient_id | Contact | ATH → HS | Match key #1. Sensitive Data; uniqueness enforced in the integration layer. |
| Name | firstname, lastname | Contact | ATH → HS | PHI once linked to the practice. Fill blanks only. |
| Contact | ATH → HS | Match key #2. Links the patient to the person who enquired. | ||
| Mobile phone | mobilephone | Contact | ATH → HS | Normalize to E.164. Match key #3. |
| Postal code | zip | Contact | ATH → HS | For location reporting. Full address left in athenaOne. |
| Primary department, provider | Department and Provider associations | Contact | ATH → HS | Associated to the custom object records. |
| Contact preferences and consent | ath_contact_consent | Contact | ATH → HS | Field names confirmed in discovery. Feeds HubSpot subscription types. |
| Appointments · Appointment events and APIs | ||||
| Appointment ID | ath_appointment_id | Deal | ATH → HS | One deal per new-patient appointment request. |
| Appointment.schedule | dealstage = Booked | Deal | ATH → HS | Requested to booked. |
| Appointment.reschedule / .cancel | dealstage, ath_appointment_status | Deal | ATH → HS | Cancelled appointments enter a rebooking workflow. |
| Appointment.check-in / .check-out | dealstage = Completed | Deal | ATH → HS | Check-out triggers the satisfaction survey if in scope. |
| Appointment date | ath_next_appointment_date | Contact | ATH → HS | Sensitive Data. Not used in personalization tokens. |
| Appointment type | ath_service_line | Deal | ATH → HS | Mapped to a service-line category. Raw type left in athenaOne. |
| Department, provider | Department and Provider associations | Deal | ATH → HS | For location and provider reporting. |
| Last completed visit | ath_last_visit_date | Contact | ATH → HS | Drives recall timing. |
| Providers, departments & referrals | ||||
| Provider ID, name, specialty | ath_provider_id, name, ath_specialty | Provider | ATH → HS | Custom object. Provider events keep it current. |
| Department ID, name, address | ath_department_id, name, address | Department | ATH → HS | Custom object for each location. |
| Referring provider | Contact (referring provider) | Contact | ATH → HS | ReferringProvider events. Not a patient record. |
| Referring practice | Company | Company | ATH → HS | Referring provider associated to their practice. |
| Referring provider on appointment | Referral association | Deal | ATH → HS | Confirm the field in discovery. Rolls up referral counts. |
| Referral count | ath_referrals_count | Contact | ATH → HS | Computed in the integration layer per referring provider. |
| Acquisition, outreach & experience | ||||
| Appointment request (HubSpot form) | Deal (Requested) | Deal | HS → ATH | Routed to the scheduling team. Free-text symptoms are not collected. |
| Open slots and booking | athenaOne appointments API | Deal | HS → ATH | Optional. Books a slot from HubSpot only if the practice approves. |
| Recall due date | ath_recall_due_date | Contact | ATH → HS | From athenaOne recall data or last visit plus interval. Source confirmed in discovery. |
| Post-visit survey | HubSpot feedback survey | Contact | ATH → HS | Sent after check-out, unless athenaOne is the agreed sender. |
| New-patient indicator | ath_new_patient | Deal | ATH → HS | Separates acquisition from returning visits. Field confirmed in discovery. |
How are authentication and API limits handled?
athenahealth grants API access through its developer program; HubSpot holds PHI only in a HIPAA-configured Enterprise portal. Values athenahealth does not publish are marked for confirmation.
| Topic | athenaOne | HubSpot |
|---|---|---|
| Access model | Apps are registered in athenahealth's Developer Portal and built against a Preview environment. Production access to a practice follows athenahealth's onboarding steps. Confirm steps and any fees with athenahealth. | Self-serve in the client portal. Sensitive Data and custom objects need an Enterprise hub. |
| Interfaces | FHIR R4 APIs (api.platform.athenahealth.com/fhir/r4) and proprietary athenaOne REST APIs for scheduling and practice data. | REST APIs: CRM objects, associations, custom objects, imports. |
| Authentication | OAuth 2.0. Back-end sync uses a 2-legged app; Event Subscription APIs require it, plus the system/SubscriptionTopic.read, system/Subscription.write and system/Subscription.read scopes, requested from athenahealth. | Private app access token, approved by the user to read Sensitive Data, or OAuth 2.0 public app. |
| Change detection | FHIR Event Notifications: rest-hook channel, ID-only payload, X-Hub-Signature (sha256), retries for up to one hour, dead letter queue kept seven days. Changed Data Subscription offers polling feeds. | Writes are immediate; batch endpoints handle volume. |
| Practice scope | Each subscription filters by practice (ah-practice) and can filter by department. | One portal; departments become custom object records. |
| Rate limits | Per-app limits apply in Preview and Production. Confirm the client's limits with athenahealth. | Per-10-second burst and daily limits by subscription tier. |
| PHI handling | Data leaves athenaOne only through the approved app and 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.
Sensitive Data properties cannot be used in personalization tokens, and some workflow triggers do not support them. Messages are written without PHI in the body.
Production access, event subscription scopes and any API fees are set by athenahealth. Confirm them before the SOW is final.
athenaOne includes outreach messaging, self-scheduling, texting and post-visit feedback. Each message type gets one sender, recorded in the SOW.
An appointment type or department can imply a diagnosis. The integration maps 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 cancelled or missed appointment starts a rebooking task or message, so the slot and the patient are not lost.
Check-out triggers a HubSpot feedback survey, and low scores open a ticket for the location manager.
New patients, booked visits and referral volume by department 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 athenaOne running scheduling and care, and HubSpot running outreach and reporting within the privacy officer's rules.
- A HubSpot form captures an appointment request; the scheduling team books it in athenaOne.
- Appointment.schedule moves the HubSpot deal to Booked; check-out 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 ath_ prefix in an athenahealth 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 |
|---|---|---|---|---|
| ath_patient_id | athenaOne Patient ID | Contact | Single-line text (Sensitive, PHI) | Patient ID; match key |
| ath_contact_consent | Contact Consent | Contact | Dropdown (Sensitive, PHI) | athenaOne contact preferences |
| ath_next_appointment_date | Next Appointment | Contact | Date (Sensitive, PHI) | Earliest future booked appointment |
| ath_last_visit_date | Last Visit | Contact | Date (Sensitive, PHI) | Latest Appointment.check-out |
| ath_recall_due_date | Recall Due | Contact | Date (Sensitive, PHI) | Recall data or last visit plus interval |
| ath_appointment_id | athenaOne Appointment ID | Deal | Single-line text (Sensitive, PHI) | Appointment ID |
| ath_appointment_status | Appointment Status | Deal | Dropdown (Sensitive, PHI) | Appointment events |
| ath_service_line | Service Line | Deal | Dropdown (Sensitive, PHI) | Approved mapping of appointment types |
| ath_provider_id | athenaOne Provider ID | Provider | Single-line text | Provider events; unique |
| ath_specialty | Specialty | Provider | Dropdown | Provider record |
| ath_department_id | athenaOne Department ID | Department | Single-line text | Department ID; unique |
| ath_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, fees, limits, event availability and field names are confirmed with athenahealth and the client's privacy officer during discovery.
- athenahealth API access and Developer Portal
- athenaOne FHIR Subscriptions guide (events, auth, payloads)
- FHIR Event Notifications and Changed Data Subscription
- athenahealth Marketplace program
- athenaOne patient engagement
- HubSpot: Store sensitive data
- HubSpot: Sensitive data in HubSpot tools
- HubSpot Sensitive Data terms and BAA
athenahealth HubSpot integration FAQ
Does athenahealth integrate with HubSpot?
Yes. athenahealth publishes FHIR R4 APIs, more than 800 proprietary athenaOne API endpoints, and FHIR Event Notifications that push an ID-only message when an appointment, patient, provider or referring provider changes. Campaign Creators builds the integration layer that fetches only the approved fields and writes them to a HIPAA-configured HubSpot portal.
What data syncs between athenahealth and HubSpot?
Appointment status, date, department, provider and type move the HubSpot patient acquisition deal from requested to booked to completed, while the approved patient demographic fields, providers, departments and referring providers sync to HubSpot contacts, custom objects and companies. Clinical details such as diagnoses, results, medications and notes stay in athenaOne.
Which system owns which data?
athenaOne owns the patient chart: scheduling, registration and every clinical fact are worked there, and HubSpot never edits a chart or appointment unless booking write-back is in scope. HubSpot owns the patient acquisition deal and marketing activity, built only from the fields the privacy officer approved under the minimum-necessary standard.
What does setting up the athenahealth HubSpot integration involve?
Seven phases, each closed by a client sign-off: HubSpot HIPAA setup with a signed field-use memo, athenahealth developer access and event subscriptions, identity and message-ownership rules, the HubSpot data model with Sensitive Data properties, the integration 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 records, fields and athenaOne APIs in scope, along with athenahealth's own production access and fee requirements. 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)