If a Meta Pixel or Google tag fires on your booking or contact page, you may be sending patient-related data to companies that never agreed to protect it. You can still measure what your marketing produces without that setup.

“HIPAA-compliant tracking” is not a product you can buy. It is a configuration and a set of contracts that keep patient information inside systems covered by a business associate agreement (BAA) and send ad platforms nothing that reveals who sought care. HHS does not endorse or recognize private HIPAA certifications, so a vendor’s “HIPAA-compliant” label proves little.

The short answer: what to avoid, what’s possible, and what’s unsettled

What you are doingOur assessmentWhy
Ad pixels on booking, form, or portal pagesAvoidThese pages collect or imply a request for care, and the companies receiving the data generally have not agreed to handle patient information.
Google Analytics on those pagesAvoidGoogle does not sign a BAA for it.
Ad pixels or analytics on general information pagesDecide with counselLower exposure than booking pages, not zero.
Search ads on generic search termsLower exposure (our analysis)The searcher supplies the intent. Conversion setup still matters.
Measuring clicks, calls, and form starts in first-party analyticsPossible with conditionsNothing goes to ad platforms. The tool still needs appropriate terms.
Call tracking with a signed BAA and restricted recordingPossible with conditionsConfirm settings and which numbers the BAA covers.
Uploading qualified-call, booked, or attended conversions to ad platformsUnsettledThe strongest signals and the most sensitive.
Uploading patient lists to Google or MetaAvoid until counsel approvesPlatform policy and HIPAA both apply.
Review requests sent by a vendorPossible with conditionsRequires a BAA and the same request to every patient.
Public replies to reviews that mention careAvoidOCR has enforced this.

These are risk assessments, not compliance determinations.

Three things decide where you land: what data is sent, who receives it, and which rules apply to your practice. This guide starts with the rules, follows your funnel and every channel you pay for, then shows what to measure instead. If you want to find problems first, go to the leak checklist. If you are comparing agencies, go to the ten questions.

Quick answers

Is Google Analytics HIPAA compliant?

No. Google does not sign a business associate agreement for Google Analytics, including GA4, so it should not run on any page that can collect or reveal patient information. Anonymizing IP addresses or adding a consent banner does not change that. On public information pages, after Becerra, using it is a risk decision for you and counsel.

Is the Meta Pixel HIPAA compliant?

Not on pages that collect or imply a request for care. Meta’s business tool terms prohibit sending it health information, so a pixel on booking or form pages is hard to defend under HIPAA or under Meta’s own rules. A server-side connection changes the route, not the content.

Is Google Ads HIPAA compliant?

Running search ads is not a HIPAA problem by itself, because the searcher supplies the intent. The risks are conversion tags on pages that collect patient information, uploads of patient data, and remarketing, which Google’s health policy restricts.

Do I need a BAA with my marketing agency?

If the agency can see patient lists, call recordings, lead details that include health information, or CRM data, treat it as a business associate and sign a BAA first. If it truly never touches patient information, write that down and enforce it with account permissions.

Is CallRail HIPAA compliant?

Not by default. Call-tracking vendors, CallRail among them, offer HIPAA-oriented plans with a BAA and restricted features. Compliance depends on configuration and on which accounts or numbers the BAA covers. Get the scope in writing and keep recording and AI summaries off until you decide otherwise.

Can we reply to Google reviews under HIPAA?

Yes, with a generic reply. Don’t confirm the person was a patient, mention a service, or defend your care. OCR has penalized practices for doing otherwise. Sample replies are in the reviews section.

Does HIPAA apply to your practice? Four rule sets to check first

Most guides skip this step because they assume every practice is covered. Not every practice is.

Are you a covered entity?

  1. Do you, or a billing company working for you, send insurers claims, eligibility checks, or similar standard transactions electronically? If yes, you are almost certainly a covered entity, and coverage attaches to the whole practice. If you bill insurance electronically for any service, treat all patient information as covered, including cosmetic work, unless counsel structures it otherwise.
  2. If not, do you take only cash and cards? You may not be covered. Some IV therapy, med spa, and dermatology and cosmetic medicine practices fall here. Counsel should confirm, because the definition turns on what you actually transmit.
  3. Where do your patients live? State law adds obligations HIPAA does not.
  4. Does a vendor handle patient information for you? If you are covered, it is likely a business associate, and you need a BAA first.

Being outside HIPAA does not put you outside the rules. It changes which ones lead.

Four rule sets, and why they differ

Rule setWho it reachesWho enforcesWhat matters for tracking
HIPAACovered entities and their business associatesHHS Office for Civil Rights (OCR)Governs PHI. HIPAA itself does not let patients sue.
FTC Act and state health-data lawsPractices that are not covered, and some data of practices that areFTC, state attorneys general, private plaintiffs in WashingtonWashington’s My Health My Data Act exempts PHI, not the covered entity. Nevada’s law exempts HIPAA-regulated entities and has no private right of action.
State wiretap and privacy statutesSites that share visitor data with third partiesPrivate plaintiffsThe legal theory behind many pixel lawsuits. California’s is the best known.
Platform policyAnyone advertising on Google or MetaThe platformsCan be stricter than the law and is enforced automatically.

A setup can pass one layer and fail another. A configuration defensible under HIPAA can still violate Google’s health advertising policy or give a plaintiff’s lawyer a wiretap claim.

The chain behind most of this advice

  1. HIPAA lets a covered practice share PHI with a vendor that signs a BAA.
  2. In the sources reviewed, Google and Meta do not sign BAAs for their advertising and analytics products, and Meta’s terms prohibit sending health information at all.
  3. So anything you send them must not be PHI, or must be authorized by the patient.
  4. A tracking tag cannot collect that authorization.
  5. So the compliant design keeps PHI inside BAA systems and sends platforms only what is not PHI.

What this guide does not cover

State medical and dental board advertising rules (testimonials, specialist titles, before-and-after photos), FDA and FTC rules on drug and device claims in aesthetics, and federal fraud and abuse rules on offers to Medicare or Medicaid patients, such as free or discounted services. Each has its own requirements. Take them to counsel before you run those campaigns.

Where your marketing tracking leaks patient data: three zones and twelve leak points

Tracking becomes a problem when three things travel together:

  • An identifier: an IP address, cookie, device ID, ad click ID, or hashed email.
  • Health context: a URL, page title, event name, or form field that reveals something about care.
  • A recipient with no legal basis to hold it.

Remove any one and exposure drops sharply. Most guides focus on identifiers. Context is where practices get caught, because marketers create it without noticing. An event called BookedImplantConsult is context. So is a thank-you page at /thank-you-anxiety-treatment.

When a page loads, a tag (a small script) can send its vendor the page URL and title, the referring page, a cookie or device ID, the visitor’s IP address, browser details, and any events you configured.

Which data elements become sensitive

This is analysis, not a legal test.

Data elementOn its ownWhat makes it worse
IP addressWeak identifierA service page or form submission. Booking and portal pages remain higher risk even after Becerra.
Ad click IDTies a click to an ad accountAny conversion event: it tells the platform that click became a lead or patient.
Cookie or device IDIdentifierURLs and events, which build a health-interest profile over time.
Hashed email or phoneStrong identifierAny event. Platforms use hashes to match accounts.
URL, page title, referrerContextAn identifier. Service or condition names reveal care sought.
Event, campaign, or parameter nameContext you wrote yourselfAn identifier. Easy to fix and often overlooked.
Form field valuesHighest-risk contextAnything, especially free-text “reason for visit.”
Call number and durationIdentifier plus contextA recording or transcript. The fact of calling a particular practice may itself be health information.

Why “we only send hashed data” is not an answer

HIPAA recognizes two ways to de-identify data. Safe Harbor requires removing 18 listed categories of identifiers, including IP addresses, URLs, device identifiers, email addresses, phone numbers, and other unique identifying codes.

Expert Determination requires a qualified statistician’s analysis (45 CFR 164.514(b)). Click IDs, cookies, and hashed emails are identifiers or codes derived from them, so data carrying them is not de-identified under Safe Harbor. “De-identified” and “aggregated,” which competing guides use freely, mean something specific here, and a tag firing per visitor does not meet it.

Three zones

ZoneWhat lives thereTracking rule
Zone 1: anonymous informationHomepage, service explainers, blogA risk decision for you and counsel. Keep it minimal.
Zone 2: intent and conversionBooking pages, forms, insurance lookups, scheduler, confirmation pages, phone-click buttonsNo ad pixels. No session replay. Generic URLs and event names. Vendors under BAA only.
Zone 3: patient systemsPMS or EHR, patient portal, practice email and textingNo third-party marketing tags. Vendors under BAA.
Diagram of three zones: public information pages, booking and form pages where ad pixels should not run, and patient systems under a BAA.

The contamination rule: a Zone 1 page with an embedded form, chat widget, or scheduler is a Zone 2 page. A “dental implants” explainer with a “request a consult” form is a booking page with a blog’s URL.

Twelve leak points

  1. Thank-you page URLs and titles that name the service.
  2. Event, campaign, and parameter names that name a service or condition.
  3. Ad pixels or tags on booking, form, confirmation, or portal pages.
  4. Third-party schedulers and insurance verification widgets, common on dental practice sites, which may run on another company’s domain with code you have never seen.
  5. Tag manager auto-listeners that capture form field text or button labels.
  6. Website plugins that install tags automatically.
  7. Chat widgets, including AI chat, that store conversations with a vendor.
  8. Session replay and heatmap tools, such as Hotjar or Microsoft Clarity, on forms.
  9. Call tracking with recording, AI summaries, or an AI receptionist switched on.
  10. Server-side events or enhanced conversions that send hashed email or phone with a service-specific event.
  11. Patient lists sent to a vendor without a BAA, or uploaded to an ad platform.
  12. Public review replies that reference care or confirm someone was a patient.

A 30-minute self-check

This is a screening, not an audit.

  1. Open your booking or contact page. Using a tag-detection extension or your browser’s network panel, list every outside domain that loads.
  2. Submit a test inquiry with obviously fake information and a clearly labeled test name. Never use a real patient’s details.
  3. Note the URL and page title you land on, and read the event names sent to advertising and analytics domains.
  4. Repeat on your scheduler and on one general information page.
  5. Record each domain in an inventory, then ask your developer and vendors for the server-side flows in writing.
DomainVendorWhat it receivesZoneBAA or contractAction
(example) connect.facebook.netMetaPage URL, event names, cookie ID2NoneRemove

This will not see what happens on servers, which is why step 5 matters.

HIPAA-compliant tracking by channel: Google Ads, Meta, reviews, calls, and email

Google search ads

Do not put the Google tag on booking, form, or confirmation pages. Capture the click ID in a hidden field or first-party cookie, store it with the inquiry in your CRM or PMS, and measure there (steps below). If you want Google to learn from outcomes, import a low-sensitivity signal from a system you control, after counsel signs off.

Name any conversion generically: “Lead” tells Google what it needs, and “Implant consult booked” tells it more than it should have. Enhanced conversions send hashed contact details, so treat them like any identifier plus event.

Google’s health policy restricts personalized advertising for flagged health content, including audience uploads like Customer Match. Which services count depends on the category, so check each account instead of assuming. You give up remarketing and some automation signal.

Meta ads

Meta’s business tool terms bar advertisers from sending health information through its pixel, server events, and custom audiences. The platform does not technically stop you, so responsibility sits with the advertiser.

Meta also removed detailed targeting by health conditions in 2022, and industry reports say it now scans for and disables audiences and conversion events that look health-related. TikTok and other social pixels follow the same logic: an identifier plus an event, sent to a recipient with no BAA.

This matters most in mental health. For psychologists and psychiatrists, even a generic-looking event can imply a condition. A safer design uses broad geographic and age targeting, creative that does the selecting, and measurement outside the platform: new patients counted in your PMS and a “how did you hear about us” field at intake.

Meta lead forms are different but not clearly safe. The person gives data to Meta before it reaches you. Keep fields to name and phone, with no free-text reason for the visit. You give up retargeting, lookalike audiences built from lists, and optimization on deep-funnel events.

Local search and Google Business Profile

There is little tracking to worry about here. Two things go wrong:

  • Link destinations. Use generic parameters such as utm_source=gbp, never ones that name a condition. The same applies when you start connecting Business Profile products to service pages.
  • Posts and replies. For a covered practice, patient names, photos, and stories generally require written authorization before use in marketing, and replying in a way that confirms someone is a patient is a disclosure. The same discipline applies to organic social and Business Profile posts.

Measuring SEO without analytics tags. Search Console and Bing Webmaster Tools report on searches inside the search engines, not on visitors’ behavior on your site, which makes them a lower-exposure substitute for site analytics (our analysis).

Verifying ownership uses a file, meta tag, or DNS record, but no tracking script runs for your visitors. Pair them with Business Profile performance data and your own call and form counts. This is why local SEO for clinics is the easiest channel to measure with little compliance friction.

Reviews

Reviews have two surfaces, and most practices audit neither.

Asking. A list of patients is PHI. If a vendor sends review requests for you, it is a business associate and you need a BAA. Ask everyone the same way. Google’s review policy prohibits discouraging negative reviews and selectively soliciting positive ones.

A common software pattern asks patients how the visit went, sends happy ones to Google, and routes unhappy ones to private feedback. That is the practice the policy describes, so if your tool works that way, check it.

The FTC’s consumer review rule (16 CFR Part 465) separately bans fake reviews, incentives conditioned on sentiment, and certain review suppression. It does not treat every gating pattern as a rule violation, so keep Google’s policy and the FTC rule apart.

Replying. OCR has enforced this repeatedly, with settlements in the tens of thousands of dollars and a $50,000 civil money penalty tied to replies to online reviews. In one case a patient posted under a pseudonym and the practice answered with the patient’s real name and treatment details. A patient may describe their own care publicly. You cannot confirm it.

Review (illustrative)Risky replySafer reply
“The root canal hurt.”“We’re sorry the root canal was painful. Your treatment followed standard care.”“Thank you for your feedback. We take every concern seriously. Privacy rules keep us from discussing any individual’s care publicly, but we’d like to hear more. Please call [number].”
A glowing review naming a treatment“Thanks, Maria! Glad your implants turned out great.”“Thank you for the kind words. We’re grateful for your trust.”

A safe reply does not confirm the person was a patient, mention a service, or defend your work. Put one trained person in charge of replies.

Website, forms, and scheduling

  • Forms. If a form collects anything about a condition, host it with a vendor that signs a BAA. Keep fields to what you need to call back: name, phone, preferred time. Skip free-text “reason for visit.”
  • Schedulers. Ask the vendor for its tag list and BAA before sending paid traffic to it. Conversions often fire on the scheduler’s domain, which you do not control. Moving to a scheduler often breaks click-based attribution, which is why practices add more tags. Resist, and count booked patients in the PMS.
  • Plugins and builders. Check what your CMS plugins install automatically and what your developer or website design partner has added to booking and form pages.
  • Banners and policies. A cookie banner is not a HIPAA authorization. Your privacy policy should describe what your site actually does, because state-law claims often focus on the gap between a policy and the real data flow.

Phone calls

For many practices, the phone is where new patients are won or lost. It is also where compliance and conversion pull against each other.

Call tracking uses dynamic number insertion: a script on your site swaps the number a visitor sees for a tracking number tied to the source, and the platform logs duration and may record and transcribe. Settle three points:

  1. The BAA and its scope. A vendor handling patient calls needs a BAA, and BAAs can be limited to specific accounts or lines. Confirm in writing which numbers are covered.
  2. Call data is more than audio. A recording of a caller describing symptoms can contain health information tied to an identifiable person. Even without a recording, the fact that someone called a particular practice may be health information.
  3. Recording consent is mostly state law. Federal law generally allows recording with one party’s consent, but some states require every party to agree, and a notice at the start of the call is the usual practice.

HIPAA-oriented configurations often turn off recording and transcription, which removes your best material for coaching the front desk. You can record under a BAA with notice, access limits, and a retention schedule, or skip recording and measure what happens after the call: answered or missed, booked or not, attended or no-show.

Some practices use two numbers, a recorded marketing line and an unrecorded existing-patient line. AI receptionists and AI call summaries are each another vendor handling call content, so each needs the same BAA question. If you define a “qualified call” by minimum duration, set the threshold from your own call data.

Tracking numbers also touch your listings. Keep the numbers on your Business Profile and directories consistent with your name, address, and phone data across listings.

Hypothesis: in phone-driven specialties, missed calls may cost more than the tracking gaps most practices worry about. Test it by counting missed and unreturned calls for four weeks before buying another tag.

Email, text, and reactivation

HIPAA’s marketing rule requires written authorization before using PHI for marketing communications, with exceptions. HHS guidance treats a practice’s communications about its own products or services as generally outside the definition unless a third party pays you to send them. So recall and reactivation messages to your own patients about your own services often fall outside the rule.

The exposure is the data path. If an email or text vendor handles the list, it needs a BAA. If someone uploads the list to Google or Meta for matching or lookalikes, you are giving patient data to companies that do not sign BAAs, and platform policy restricts these uploads for health content anyway. Texts and emails also carry consent rules outside HIPAA, such as the Telephone Consumer Protection Act and CAN-SPAM.

The safer design sends from systems under BAA, such as your PMS or a vendor that signs one. You give up paid reach to past patients on Google and Meta, but owned channels reach the right people directly, which is what the list upload was trying to approximate.

Four ways to build tracking: client-side, server-side, privacy layer, or PMS-first

Server-side tagging is a control point, not a conclusion. It lets you inspect and strip data before forwarding it. It changes who sends the request, not who receives it.

ApproachWhat it controlsWhat it does notBest fit (our analysis)
Client-side tags (pixels, tag managers in the browser)Nothing beyond configuration. Vendors receive what the browser sends.Context and identifiers go straight to vendors.Zone 1 only, if at all
Server-side taggingFiltering before forwardingThe legal status of what you forward. Adds cost and setup.Practices with a developer or agency that documents its filters
Privacy-focused data layer or customer data platform under a BAACentral filtering, consent logic, vendor routingStill needs a decision on what each destination may receiveMulti-location and multi-specialty groups with volume
PMS-first measurementKeeps the truth in systems that already hold patient data. You import spend and compute results there.Less signal for ad-platform optimization. Requires source capture at intake.Most small and mid-size practices

What you can still measure: the Signal Ladder

Ad platforms learn from conversion signals. The further down your funnel a signal sits, the better it predicts real patients, and the more it says about a real person. That tension runs through every compliant measurement decision.

RungSignalWhere it is measuredSent to an ad platform?
L0Impressions and clicksThe platform’s own reportingAlready there
L1Engagement on information pagesYour first-party analyticsNo
L2Click-to-call or form startYour first-party analyticsNo
L3Qualified callBAA call platform and your CRMUnsettled. The fact of calling a practice may itself be health information.
L4Booked appointmentYour PMSUnsettled. Higher than L3, because it signals a patient relationship.
L5Attended new patient and valueYour PMSKeep inside by default
Six-step ladder from clicks to attended new patients, showing that higher steps are more useful but more sensitive, with calls and booked appointments unsettled for upload.

A three-question test

Before any signal leaves your systems, ask:

  1. Is an identifier attached (click ID, cookie, hashed email, phone number)?
  2. Does the event reveal care sought or a patient relationship?
  3. Is the recipient outside your BAA systems, or restricted by its own health policy?

If two or more answers are yes, keep the signal inside. This is a decision aid, not a legal test, and it is why L1 and L2 stay in your own analytics.

The offline conversion trade-off

Offline conversion uploads are often recommended as the compliant way to tell Google which clicks became patients. They are better than tagging booking pages. They are not free of risk.

The signal that trains an algorithm best is the one that says a real person became a patient, and that is also the signal that most clearly says a real person became a patient.

Whether uploading de-identified or aggregated qualified-call or booked signals counts as sharing PHI is not settled in the sources reviewed for this guide. If you use them, do it deliberately, with counsel’s input. Options include uploading a qualified-lead flag instead of a booked flag, or keeping uploads off for sensitive specialties.

When less tracking costs little

This is a hypothesis, not a result: for low-volume accounts, a rich pixel feed may add little optimization value compared with fixing call handling, booking friction, and how you count booked patients. You can test it. Over eight to twelve weeks, compare platform-reported conversions with new patients counted in your PMS. If they diverge widely, the platform number is not what you should optimize against.

How to measure cost per new patient without ad-platform tracking

The practice system already holds patient data under a BAA. It is the one place that knows who booked and who showed up. So bring spend into the PMS and calculate there, instead of sending patient events out so platforms calculate for you.

Cost per new patient = (ad spend + management fees + tools) ÷ new patients who attended and are attributed to that channel

How to capture the source without an ad tag

  1. Add hidden fields (source, medium, campaign, click ID) to your inquiry form. Fill them from the URL with a script you control, not a third-party tag.
  2. Store the values in a first-party cookie for a limited time.
  3. Pass them into your CRM or PMS record with the inquiry. The form vendor must be under a BAA.
  4. For calls, use a BAA call platform that records which number the visitor saw, and map call source in your system.
  5. Add a “how did you hear about us” question at intake as a cross-check.
  6. Use a lift test as a last resort: pause a channel in one area or time window and watch new patient counts.

Lag varies by specialty. An emergency dental visit may convert in hours, while elective or surgical consults take weeks or months. Measure your own before judging a channel.

A worked example (hypothetical)

Two channels, each with $4,000 of spend including fees:

MetricChannel AChannel B
Leads reported by the platform5080
Cost per lead$80$50
New patients attended108
Cost per new patient$400$500

Channel B looks better on cost per lead and worse on what you pay for each patient. A platform dashboard shows the first number. Only your PMS shows the second.

Is that number good?

There is no reliable public benchmark, so compare it to what a new patient is worth to you:

Break-even cost per new patient ≈ expected net collections from a new patient over a period you choose × the share you are willing to spend on acquisition

Use net collections, what you actually collect, not production or charges. Payer mix, contracted insurance rates, no-show rates, and cancellations all move the inputs. Hypothetically, if a new patient yields $1,800 in first-year net collections and you will spend 25% to acquire them, break-even is $450. Channel A at $400 clears it. Channel B at $500 does not.

How constraints change your channel mix

This is reasoned interpretation, not data.

  • Insurance-based practices: lean on search, Business Profile, correctly run reviews, and referrals. Insurance verification and booking tools are the main leak risk.
  • Mental health and other sensitive specialties: favor local search and referrals, and limit paid social.
  • Cash-pay aesthetics: HIPAA may not apply, but FTC rules, state health-data laws, and platform policy do.
  • Multi-location groups: measure in the PMS, and keep a vendor inventory per location.

Referrals and directories sit outside your tag stack, which makes them easier to measure with an intake question. Referral relationships matter most in specialties such as chiropractic. Directories, including Healthgrades and Zocdoc listings, have their own data practices, so check their terms before sending them patient information.

HIPAA tracking rules in 2026: what still applies after AHA v. Becerra

OCR’s guidance. OCR issued a bulletin on tracking technologies in 2022 and updated it in 2024. In June 2024, a federal court in Texas ruled in American Hospital Association v. Becerra that OCR overreached when it said an IP address plus a visit to a public page about a condition or a provider search counts as PHI.

The court vacated that part, and OCR later dropped its appeal. The ruling concerned unauthenticated public pages. It did not address authenticated pages such as patient portals, and it did not touch state laws or private lawsuits.

Beyond HIPAA. For non-covered practices, the FTC has pursued health companies for sharing data with advertising platforms. Washington’s My Health My Data Act allows private lawsuits, and the first private actions under it were filed in 2025. Other states, including California, Connecticut, Maryland, and Texas, have their own health-privacy or consumer health data rules.

California. The state’s wiretap statute (the California Invasion of Privacy Act, or CIPA) is behind many pixel lawsuits. Plaintiffs argue that a third-party tag receiving visitors’ data without consent is an interception. Whether consent defenses succeed is contested.

Businesses subject to California’s consumer privacy law must also honor browser opt-out signals such as Global Privacy Control, and whether that reaches a medical practice depends on its size and on how California treats HIPAA-covered data.

Platform policy. Google restricts personalized ads and audience uploads for flagged health content, and Meta’s terms bar sending health information through its business tools. Both change often, so check current text on the day you act.

Litigation. On October 30, 2026, a federal judge certified classes of Facebook users in the consolidated healthcare pixel litigation against Meta. Reported settlements have largely involved hospitals and health systems, and published tallies differ, so this guide quotes no total.

The research for this guide found no reliable public data on how often small practices face tracking suits. Our analysis: the legal theories do not depend on a practice’s size, and exposure likely rises with traffic from strict-privacy states and with trackers on sensitive pages.

How to evaluate a HIPAA-compliant marketing agency: ten questions

QuestionA good answerA warning sign
Who owns the ad, tag manager, and analytics accounts?You do, with admin access.The agency does.
Do you sign BAAs, with which vendors, and for which accounts or phone lines?A specific list, signed agreements, and stated scope.“Our tools are HIPAA-compliant.”
What is the full list of tags and scripts on my booking page?A written inventory you can verify.“We’ll check.”
Which vendors touch patient data on our behalf?A named register.No list.
How do you define a “new patient,” and from what system?From your PMS, with a definition you approve.The ad platform’s lead count.
What happens to call recordings and transcripts?Off by default, or under a BAA with retention rules.Recorded and transcribed by default.
How do you ask patients for reviews?The same request to every patient.Happy patients go to Google, unhappy ones to private feedback.
What do you upload to Google or Meta, and why?Nothing from patient lists. Conversion uploads reviewed by counsel.Customer lists for “lookalikes.”
What documentation could you give me if OCR or a plaintiff asked?A data-flow map, vendor register, and risk analysis.A certificate or badge.
What would you refuse to do?A specific example.“Nothing.”

What to fix first

Fix what carries the most risk for the least effort first.

  1. Remove ad pixels and analytics from booking, form, confirmation, and portal pages.
  2. Rename URLs and conversion events so they carry no service or condition.
  3. Get BAAs, or stop sending data, for every vendor that touches patient lists, calls, or form submissions.
  4. Write a review reply policy and fix how you ask for reviews.
  5. Align your privacy policy and notices with what your site actually does.
  6. Add server-side controls or a privacy-focused data layer if you need more than these steps provide.
  7. Rebuild measurement around the PMS: cost per new patient, call answer rate, and a source field at intake.

If you find a leak

  1. Stop the flow by removing the tag, then preserve records of how it was configured, when, and which vendors received what.
  2. Assess it as a possible breach. For a covered practice, an impermissible disclosure of PHI is presumed to be a breach unless a documented risk assessment shows a low probability that the information was compromised. Notice deadlines run from discovery and are no later than 60 days.
  3. Feed it into your security risk analysis. The HIPAA Security Rule requires covered entities and business associates to conduct and document an accurate and thorough analysis of risks to patient information. Your tag inventory belongs in it.
  4. Know the consequences. OCR civil penalties are tiered by level of culpability, with amounts adjusted annually (check HHS’s current figures). Private suits proceed under other laws, and state attorneys general can act too.
  5. Avoid public statements about the leak until counsel reviews them.

Questions to take to counsel

  1. Are we a covered entity, and does that cover all our services?
  2. Which of our booking, form, and confirmation pages count as sensitive under current OCR guidance after Becerra?
  3. Does a call to our practice, or a qualified-call or booked flag, count as PHI when sent to an ad platform?
  4. May we upload any conversion or list data to Google or Meta?
  5. Which state laws apply given where our patients live, including California wiretap and consent rules and Washington and Nevada health-data laws?
  6. What call-recording notice do callers in each state require?
  7. Is our review request flow consistent with Google’s policy and the FTC review rule?
  8. Is it safe to preserve current configuration records and to run test submissions on live forms?

If you would like a second set of eyes

You can run this checklist yourself. If you would rather have help, the first stage of Pracxcel’s P.A.T.I.E.N.T. Framework is Plan & Audit, a review of your online presence and ad accounts. Bring the leak checklist and the ten questions above and book a Plan & Audit conversation to ask how the audit would cover them. Pracxcel is a marketing agency, not a law firm, so legal conclusions go to your counsel.

FAQs