Journeys Through Search

HIPAA CRM integrationsYour systems connected to Salesforce, with patient details kept where they belong.

Healthcare teams need their calls, forms, chat, texting, EMR and billing connected to Salesforce, without patient information leaking into ad platforms or tools that should not hold it. We sign a BAA, give each connection only the access it needs, and send outcomes out instead of details.

  • We sign BAAs for healthcare work
  • Ad platforms get outcomes, not diagnoses or treatment
  • Each integration user gets only the access it needs
  • Texting consent enforced before a message goes out

900+ integrations completed · Salesforce partner · We sign BAAs

How we build it

  1. 1
    Map the data

    What each system sends, what it receives, and which fields hold patient information

  2. 2
    Limit the access

    A dedicated integration user per connection, with permissions for its own fields only

  3. 3
    Send outcomes out

    Ad platforms and analytics get a conversion and its value, nothing clinical

What we do on a HIPAA CRM integration

We sign a business associate agreement (BAA) before we touch patient data. Then we map every connection: which system sends what, which fields hold patient information, and which systems should not receive it at all.

Each integration gets its own integration user in Salesforce, with permissions for the objects and fields it needs and nothing else. Credentials are stored encrypted, and alerts tell your team when a connection fails.

Ad platforms still need to know which ads work. When an insured lead becomes a patient, we send the conversion back as an outcome only: approved, not approved or pending, with a value. No diagnosis, treatment or plan details leave Salesforce.

Texting follows consent. An "Approved to SMS" field on the record is checked before any text goes out, and your web forms carry the opt-in checkbox and consent language to back it up.

We do not certify anyone as HIPAA compliant. We build the integrations the way described here and sign a BAA; your organization stays responsible for its own HIPAA program.

What's included

What hIPAA CRM integrations includes

BAA signed

A business associate agreement in place before we work with patient data.

Data map

Every field each system sends and receives, with patient information marked, signed off before we build.

Least-access integration users

One integration user per connection, with permission sets for its own objects and fields.

Outcome-only conversions

Insured leads sent back to ad platforms as conversions with a status and value, and nothing clinical.

Source tracking without patient details

Five hidden fields on every form, chat and call: first and last click landing page, first and last click referring domain, and the converting page.

Texting consent

An "Approved to SMS" field enforced before sending, opt-in checkboxes on forms, and consent language on the site.

EMR and billing kept separate

Clinical data stays in the EMR. Salesforce gets what admissions and reporting need, like admit and discharge dates.

Login security

Multi-factor authentication and profiles set up so each user sees what their role needs.

Failure alerts

An email when a connection or token fails, so data does not quietly stop flowing.

Works with

All Salesforce integrations

Every system we connect to Salesforce, in one list

Call tracking

CallRail and CallTrackingMetrics native integrations, with recordings and AI call summaries on the lead

Web forms

Gravity Forms, Jotform and Typeform fills create leads with tracking attached

Chat and texting

LiveChat, SnapEngage, Tawk.to and Avochato conversations saved to the lead

EMR

Kipu and Sunwave: admissions in Salesforce, clinical in the EMR, kept in step

Billing and financial

CollaborateMD, AdvancedMD and HiLite, with insurance payments on the patient

Payments

Stripe, PayTrace and PayPal payments recorded on the opportunity

Ad platforms

Google Ads, Microsoft Ads, Meta and TikTok leads in, offline conversions out

Email marketing

ActiveCampaign lists and automations that follow Salesforce

Single sign-on

Open other systems from the Salesforce record with SSO

Reporting

Salesforce data in Google Sheets, BigQuery and Looker Studio

Anything with an API

No app for it? We build the connection with Apex and the APIs

Worried about patient data in your integrations?

Book a free call. We walk through what each of your systems sends to Salesforce and out of it, and tell you honestly what we would change.

Book a free call →

What clients say

900+ integrations completed
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
Jason Landver
CEO, Recovery Beach
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
Mike Kwak
On-Site Adjusting
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
Tarra Boggs
EHS & Compliance Operations Manager

How it works

How hIPAA CRM integrations works

  1. 01

    Free call

    We look at your systems and where patient information flows today.

  2. 02

    BAA and data map

    We sign a BAA, then map each connection and mark the patient fields.

  3. 03

    Build in a sandbox

    Integrations built with their own integration users and tested away from live data.

  4. 04

    Go live with alerts

    Deployed to production, with failure alerts and support after go-live.

Working with us

HIPAA CRM integrations FAQ

Do you sign a BAA?

Yes. We sign BAAs for healthcare work, before we work with patient data.

Can we still send conversions to Google Ads and Meta?

Yes. We send the outcome only: approved, not approved or pending, with a value. No diagnosis, treatment or plan details are sent.

Does this make us HIPAA compliant?

No integration does that on its own. We build the connections with limited access and outcome-only data, and sign a BAA. Your organization stays responsible for its HIPAA program.

What is a least-access integration user?

A Salesforce user created for one integration, with permission to see and change only the fields that integration needs.

How do you handle texting consent?

An "Approved to SMS" field on the record is checked before any text is sent, backed by opt-in checkboxes on your forms.

Should clinical notes live in Salesforce?

Clinical work belongs in the EMR. Salesforce gets what admissions, referrals and reporting need, like admit and discharge dates.

Are you a Salesforce partner?

Yes. Journeys Through Search is a Salesforce partner.

How is it priced?

By project, not by the hour. The first call is free, and you get a project quote after it.

Related