HubSpot use-case / reference pattern

HubSpot healthcare integration built on trust.

Turn a patient enquiry into a thoughtful relationship. This Connect by MediRecords reference integration pattern shows how HubSpot and MediRecords can support acquisition, consent-aware nurture and recall — without asking clinical data to leave its home.

Launch the HubSpot Integration Application Trial access required Follow a patient journey See what stays protected

Consent-aware Non-clinical data only

New enquiry09:14

Ari Morgan

Looking for a first visit

Matching against MediRecords

Relationship

A welcome that knows when to arrive.

Consent checked before nurture

Read the pattern accurately

A clear boundary between what runs, what is documented, and what needs to be built.

Live now

Patient reads and secure receiver

With configured credentials, the demo can read FHIR Patients and receive signed patient events. The player displays a synthetic event; it never sends one.

Documented / buildable

Consent, registration and status

FHIR Consent reads and consent events, REST patient create/update, and appointment CRUD/status are documented capabilities. A connector must implement the policy and data flow.

Illustrative demo

The journey around the APIs

Matching, suppression, recall scans, HubSpot timeline events, lists, workflows, retries and replay are reference patterns—not live demo features.

The front door, extended

The best patient marketing does not feel like marketing.

01 / KEEP CURRENT

MediRecords keeps engagement current

A signed MediRecords patient event can inform a production Contact synchronisation path with approved non-clinical details. The player displays an unsigned synthetic event; its only optional live action is a bounded HubSpot sandbox test-contact update.

02 / ARRIVE

An enquiry feels seen

A production connector can apply an approved matching policy before it calls the documented MediRecords patient create or update API.

03 / EARN TRUST

Consent sets the pace

A production connector needs an approved consent source and policy before it sends any contact into marketing. FHIR Consent reads and consent events are documented; the current demo uses a synthetic decision.

04 / STAY CLOSE

Care keeps moving

A connector can collect documented appointment REST statuses and apply a policy before configured HubSpot activity or workflows run. This is not a current MediRecords appointment-webhook integration.

One relationship, many useful signals

A patient journey you can actually follow.

The demo pattern connects the moments a practice already cares about. It gives teams a clearer view of where a person is — and a more human reason to reach out.

New enquiry

09:14

Reference connector matching policy

Consent checked

09:15

Approved consent source required

Gate passed

Appointment status

09:19

Connector reads configured REST source

HubSpot activity

10:06

Portal template and workflow required

Contact view

Ari Morgan

Active patient

Latest activity

Appointment attended

An illustrative non-clinical status signal can be used for communication and timeline context after a connector reads a configured REST source.

MediRecords REST → connector → HubSpot

The activity shown is illustrative. Live API calls depend on the configured credentials and integration workflow.

Demo available · Conditional live calls

Technical scope and data boundaries

A reference integration pattern for connecting MediRecords with HubSpot while keeping clinical records in MediRecords. The patient-engagement player displays an unsigned synthetic FHIR event and an illustrative minimum-necessary data boundary; it does not emit a MediRecords event. With configured credentials, the console can read FHIR Patients and receive signed patient events. Its only optional live player action is a HubSpot update to a server-pinned sandbox test Contact. A production practice must approve its own minimum-necessary data set and communication policy.

The demo also illustrates three buildable workflows. New patient acquisition can use a connector-owned matching policy and the documented MediRecords patient create/update APIs; registration, matching and consent handling are not live demo calls. Appointment lifecycle can use documented Connect REST appointment status data through connector logic—MediRecords' published FHIR webhook catalogue does not list appointment events. HubSpot timeline events, custom properties, lists, workflows, retry/replay and recall scans all require portal-specific configuration and additional connector development. FHIR Consent reads and consent events are documented, but the demo's consent decisions are synthetic; FHIR Consent creation is not supported.

Only an approved, minimum-necessary set of non-clinical data may be sent to HubSpot. The walkthrough labels live API calls, documented capabilities and illustrative patterns separately; it describes possible operational goals rather than guaranteed business outcomes.

From activity to action

Helpful nudges. Not a noisy funnel.

Welcome with context

A configured connector can use an approved consent decision before a contact enters a marketing workflow.

Communicate on time

Appointment REST status can inform approved reminders, follow-up and timeline context through connector logic.

Reconnect thoughtfully

A connector can create consent-aware recall segments with portal-specific suppression controls.

Keep the trail clear

Connector retry, queueing and replay are implementation patterns that need to be built and operated.

A clear boundary keeps trust intact.

HubSpot supports the relationship layer. MediRecords remains the system of record for the clinical record.

May be shared with HubSpot

Only an approved, minimum-necessary set of non-clinical demographic and appointment-status information.

Stays in MediRecords

Clinical records and clinical detail remain in MediRecords.

Consent is a gate, not a footnote

Suppression reasons help teams understand why a person was not included.

See the reference pattern

Make every welcome worth remembering.

Start with the MediRecords-led patient engagement example, then explore enquiry matching, consent gates, appointment-status handling and recall suppression.

Launch the HubSpot Integration Application Trial access required