On this page

Outside HIPAA is not the end of the scope review

HIPAA, the Health Insurance Portability and Accountability Act, governs specified covered healthcare entities and their business associates. The Federal Trade Commission (FTC), the U.S. consumer-protection agency, describes a separate Health Breach Notification Rule for covered vendors of personal health records, related entities and their third-party service providers.

A personal health record (PHR) is the defined electronic record of identifiable health information with the technical capacity to draw information from multiple sources, managed, shared and controlled by or primarily for the individual. The FTC guidance explains that a health app able to combine consumer inputs and a fitness tracker can qualify even if a particular user never turns on the tracker connection.

Sources: Federal Trade Commission: Selected source provisions read across the data-owner guides: Full substantive guide read; Who’s Covered, trigger definitions, service-provider notice chain and FAQs on technical capacity, solely HIPAA and mixed public PHR/business-associate services. Notice amounts/timetable and penalties not relied on.

Record the product’s sources and role

The following is an original scoping exercise for a proposed service. It is not a finding that a particular app falls within the rule. Medical-sounding branding, server location or a signed software contract does not answer the actual definition.

Product factScope evidence to establish
Information heldActual identifiable health information and how it can identify or be linked to a person.
Technical source capacityConsumer inputs and any available device, application or other information connection.
Who the record servesWhether it is managed/shared/controlled by or primarily for the individual.
Your rolePHR vendor, related entity, relevant service provider, solely HIPAA work or a mixture.
Client/vendor chainWho is covered and which designated contact receives required notices.

A company can need more than one assessment

The FTC distinguishes a company acting solely as a HIPAA business associate from one that also offers personal health record services to the public. Its guidance says the latter may be subject to both HHS and FTC breach-notification rules for the relevant activities. HHS is the U.S. Department of Health and Human Services. Classify each actual service rather than assume one contract controls every product.

The FTC also explains that a covered breach is not limited to hacking: an unauthorised disclosure can raise the rule’s notice question. This page establishes the product/party scope review, not an incident determination or notice timetable. Other privacy, security, state and sector duties require their own assessment.

Sources: Federal Trade Commission: Selected source provisions read across the data-owner guides: Full substantive guide read; Who’s Covered, trigger definitions, service-provider notice chain and FAQs on technical capacity, solely HIPAA and mixed public PHR/business-associate services. Notice amounts/timetable and penalties not relied on.

Scope

  • Selected FTC Health Breach Notification Rule guidance and role definitions only. Actual product coverage, exceptions, incident/reportability, notification content/timing and other laws require specialist review; no health service is approved.

Next step

Use Launch planner to assign the product-role and data-source scope review before offering the health-data service. Keep real health records and legal assessments in restricted company systems.

Sources & review notes

Access dates show when a source was retrieved. Review dates show when its meaning was checked. Editing this guide does not recheck the law.

Complying with FTC’s Health Breach Notification Rule

Federal Trade Commission

Passage, dates and research notes

official-guidance · Selected source provisions read across the data-owner guides: Full substantive guide read; Who’s Covered, trigger definitions, service-provider notice chain and FAQs on technical capacity, solely HIPAA and mixed public PHR/business-associate services. Notice amounts/timetable and penalties not relied on.

Accessed: 2026-11-16T20:12:35.940157+00:00 · Meaning reviewed: 2026-11-16T20:24:54.728906+00:00 · Next review target: 2026-12-16

AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.

Detailed rule records (1)
Health-product scope extends beyond a HIPAA label Depends on the facts

Assess actual PHR technical capacity and party role; covered FTC responsibilities can coexist with separate HIPAA activities.

When to check: Before designing a public health-record product or relying on a HIPAA-only scope conclusion. Source review: 2026-11-16.

Complying with FTC’s Health Breach Notification Rule
Your learning

Bookmark this guide or mark it as read.

Learning library
Progress privacy

Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.

This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.