Expert Opinions

Shopify & PHI: Unpacking Telehealth’s Hidden Compliance Risks

Listen to this article · 8 min listen

The movement of protected health information (PHI) within telehealth workflows gets messy fast, involving a whole cast of platforms that live outside the four walls of a traditional clinic. When patient data like a prescription order confirmation ends up on a commercial platform like Shopify, the rules of the game change completely. A compliance lead has to think about more than just HIPAA. You need to grasp the entire framework of consumer health data protection to get a real sense of your company’s risk and exposure.

The Anatomy of a Commerce Platform Leak: When a Receipt Becomes ePHI

A prescription order confirmation seems harmless enough, just a digital receipt. But that little communication can become a massive vector for a PHI leak when it’s pushed through a general-purpose commerce platform. As Paubox has recorded, a telehealth company simply cannot send order confirmations containing PHI through Shopify Paubox article on Shopify and PHI. For most telehealth companies, the hard truth is that these confirmations absolutely do contain PHI. This isn’t a maybe. It’s how they operate. The problem starts with the data itself, Electronic PHI (ePHI), which dictates the kind of regulatory heat it attracts long before you even choose a software vendor. An order confirmation that lists a patient’s medication, their dosage, or even just confirms the existence of a prescription is ePHI. Full stop. The second that ePHI leaves the safety of a HIPAA-covered entity’s controlled systems and travels through a platform like Shopify, which won’t be a Business Associate (BA) under HIPAA, your compliance status gets very questionable. Shopify wasn’t designed or configured to handle PHI in a HIPAA-compliant way, so any ePHI you send through it’s immediately exposed and represents a potential breach. This all proves that the data type question comes before the tool question. You have to know what qualifies as ePHI to have any hope of preventing these leaks.

ePHI Beyond the Covered Workflow: The FTC Health Breach Notification Rule

The second ePHI exits a HIPAA-covered workflow and lands in the world of a non-covered entity or a general commerce platform, the list of regulators who can come after you gets longer. HIPAA still applies to the covered entity’s screw-up, but a different and powerful regulatory framework enters the picture: the FTC Health Breach Notification Rule. Recorded material from companies like Tempus AI demonstrates the rule’s relevance, because it specifically addresses Electronic PHI (ePHI) and frames the FTC Health Breach Notification Rule as the regulation that reaches health data once it moves outside a covered workflow FTC Health Breach Notification Rule overview. This is a critical distinction for any compliance lead. HIPAA is primarily for Covered Entities (CEs) like health plans and providers who transmit health info electronically, and their Business Associates (BAs). But the digital health space is full of companies that don’t fit that old-school definition yet handle enormous amounts of sensitive health data. When patient data flows through a commerce platform, HIPAA isn’t the only rulebook on the table. The FTC Health Breach Notification Rule, which got a major update with a final rule in April 2024 that became effective in July 2024, covers entities that aren’t subject to HIPAA but offer personal health records (PHR) or related services. The rule says these companies must notify individuals, the FTC, and sometimes the media after a breach of unsecured health information. What’s “health information” under the FTC’s rule? It can be much broader than HIPAA’s definition of PHI, covering basically any health-related info collected by these non-HIPAA companies. The 2024 changes made it crystal clear that the rule applies to health apps and similar tech and expanded what a “breach of security” means to include unauthorized disclosures of PHR identifiable health info, not just someone hacking a database. A smart reader has to figure out which rule applies to which actor, and what the FTC rule adds on top of the HIPAA analysis.

The Dual Enforcement Exposure: Mapping Rules to Actors

To really understand your enforcement exposure, you have to precisely map which rule applies to which player in your telehealth data flow.

HIPAA’s Reach: Covered Entities and Business Associates

For a telehealth company that operates as a HIPAA Covered Entity, the main job is staying HIPAA compliant. That means any third-party vendor you use to handle PHI, like a platform for sending those order confirmations, must be a HIPAA Business Associate and sign a Business Associate Agreement (BAA). The Paubox example is a perfect illustration: if a telehealth company pushes PHI through Shopify and Shopify is not a BA, that company is violating HIPAA. It’s a direct failure of their duty to protect PHI. The penalties for that kind of breach aren’t trivial, running from civil monetary penalties all the way to criminal charges depending on what happened and why.

The FTC’s Broad Net: Non-Covered Entities and Consumer Health Data

The FTC Health Breach Notification Rule casts a much wider net, catching companies that aren’t directly under HIPAA’s thumb but are still handling consumer health data. This is especially relevant to the booming market of digital health apps and services collecting info straight from consumers. If a telehealth company, by using a commerce platform, accidentally exposes consumer health data that might not technically be PHI under HIPAA (like general health-related buying habits, or data collected by a non-CE app), the FTC rule can still force a breach notification. The 2024 amendments to the FTC rule were aimed squarely at this, broadening its reach to health apps and clarifying that an unauthorized disclosure of health data is a breach. This reinforces its power in these exact scenarios. The pairing of the commerce platform leak against the recorded Tempus AI material really drives home this dual exposure. A health data leak through a commerce tool is a data type problem and a consumer health breach problem. While the Paubox scenario shows a direct HIPAA violation for a covered entity, the larger context of consumer health data exposure, as the FTC Health Breach Notification Rule sees it, applies to a much wider group of digital health services. So even if a company thinks it has cleverly avoided a HIPAA violation by segmenting its data, a leak of any health-related info through a commerce platform could still trigger FTC notification duties if it’s considered part of a PHR or a related service.

Proactive Compliance: Mapping Data Flows Before Tool Selection

The argument is simple: a commerce platform leak is a data type event first, not a tool failure. The recorded Paubox page shows just how easily Electronic PHI (ePHI) can slip out of the covered workflow in a routine confirmation email. The FTC Health Breach Notification Rule is the recorded frame that will be used to prosecute that kind of consumer health data exposure. I’d argue that telehealth companies must map which rule reaches their data before they ever map which tool sends their email. Compliance leads have to do the hard work of data mapping to identify every single touchpoint where patient data, no matter its classification, interacts with an outside platform. This isn’t just about clinical data. It includes transactional info that seems harmless but, in context, is absolutely PHI. Only when you understand the complete journey of your patient data can you accurately figure out your regulatory duties and head off enforcement actions. This kind of proactive work, built on a real understanding of both HIPAA and the FTC Health Breach Notification Rule, is what it takes to build HIPAA compliant AI health apps and digital platforms that can actually survive the due diligence of big employer and health-plan contracts. Federal Register guidance on FTC Health Breach Notification Rule enforcement

Frequently Asked Questions

When does a prescription order confirmation become a compliance risk on a commerce platform like Shopify?

A prescription order confirmation becomes a compliance risk when it contains Protected Health Information (PHI) and is processed through a general-purpose commerce platform like Shopify. Shopify is not typically a Business Associate under HIPAA and is not configured to handle PHI in a compliant manner, making any ePHI transmitted through it immediately at risk of exposure.

What is the primary regulatory concern when PHI moves from a HIPAA-covered workflow to a commerce platform?

When ePHI exits a HIPAA-covered workflow and enters a general commerce platform, the primary regulatory concern is that the platform is likely not a HIPAA Business Associate. This means the transmission of PHI through such a platform constitutes a potential breach and a violation of HIPAA for the covered entity.

Beyond HIPAA, what other regulatory framework might apply to patient data flowing through commerce platforms, and why?

Beyond HIPAA, the FTC Health Breach Notification Rule might apply. This rule covers entities not subject to HIPAA that offer personal health records or related services, or are vendors of such services, and mandates notification following a breach of unsecured health information, especially when patient data moves outside a HIPAA-covered workflow.

Does the type of data or the platform used determine which privacy rules apply?

The type of data, specifically whether it constitutes Electronic Protected Health Information (ePHI), dictates the regulatory scrutiny it attracts, even before considering the platform used. Understanding what constitutes ePHI is paramount to preventing leaks, as the data type question precedes the tool question.

Share
Was this article helpful?

Editorial Team

The Editorial Team at HIPAA AI Health is a group of writers and editors who cover health, workplace wellness, and everyday care. They research each story and publish under a shared desk byline — experts in their fields, working as one team.