Skip to content
Cyberphore

Privacy law and breach response

HIPAA vs PHIPA: What Health Tech Vendors Owe on Each Side

HIPAA vs PHIPA for health tech selling across the border: who each law covers, consent, breach notice clocks and business associate versus agent roles.

Published
Updated
Read time
5 min
On this page · 10 sections, 5 min read

If your health software serves clinics in Ontario and providers in the United States, you answer to two different models. HIPAA regulates US health plans, clearinghouses and providers that conduct standard electronic transactions, plus the vendors handling their data; Ontario's PHIPA regulates health information custodians and those acting for them. Consent, vendor contracts and breach clocks differ enough that a program built for one market leaves gaps in the other.

This is general information, not legal advice. Our healthcare and technology and SaaS pages cover the security side.

Who Each Law Reaches

HIPAA applies to covered entities: health plans, clearinghouses, and health care providers who transmit health information electronically in a covered transaction (eCFR, 2026). A vendor that "creates, receives, maintains, or transmits" protected health information for a covered entity is a business associate, and so is its subcontractor.

The definition turns on function, not location, so in our view a Canadian host for a US clinic should plan on business associate duties.

PHIPA centres on the health information custodian, such as a practitioner, group practice, hospital or long-term care home (PHIPA, 2026). A vendor usually holds one of three roles:

  • Agentacts for the custodian, for the custodian's purposes "and not the agent's own purposes" (PHIPA, 2026, s. 2).
  • Electronic service provider that is not an agentmay use the information only as necessary to provide the services, and may not disclose it (O. Reg. 329/04, 2026, s. 6(1)).
  • Health information network providerserves two or more custodians, primarily so they can share information electronically, whether or not it is also an agent (O. Reg. 329/04, 2026, s. 6(2)).

Your role depends on what you do with the data and what the contract says; have Ontario privacy counsel confirm it.

Consumer apps are where the laws split. In the US, a personal health record vendor outside HIPAA falls under the FTC's Health Breach Notification Rule (eCFR, 2026). PHIPA's section on consumer electronic service providers is still marked "not in force" on e-Laws (PHIPA, 2026).

The OPC lists PHIPA as substantially similar to PIPEDA for personal health information (Office of the Privacy Commissioner of Canada, 2020), but its duties attach to custodians and those acting for them, so a direct-to-consumer app should confirm with counsel whether PIPEDA governs it.

EMR access monitoring that flags after hours chart access by a former clinic employee. Sample screen; data is illustrative.

Business Associate Versus Agent

HIPAA prescribes the paperwork. A covered entity needs "satisfactory assurance" from a business associate, documented in a written contract (eCFR, 2026) that sets permitted uses, requires Security Rule safeguards and requires the vendor to report breaches (eCFR, 2026).

PHIPA keeps the custodian responsible for its agents' handling of the information, while an agent must tell the custodian "at the first reasonable opportunity" of theft, loss or unauthorized use or disclosure (PHIPA, 2026, s. 17).

For network providers the regulation goes further: a written agreement, a plain language description of services and safeguards that is also made public, access and transfer logs on request, and a written threat and privacy assessment for each custodian (O. Reg. 329/04, 2026, s. 6(3)).

HIPAA lets a covered entity use or disclose protected health information for treatment, payment and health care operations without consent (eCFR, 2026). PHIPA allows implied consent for providing care, but a disclosure to someone who is not a custodian, or to a custodian for purposes other than health care, needs express consent (PHIPA, 2026, s. 18).

That bites in features that share data with an employer wellness program, an insurer or a research partner: in Ontario, build an express consent flow the custodian controls. Since an agent acts only for the custodian's purposes, reusing client records for your own analytics or model training does not fit that role.

Breach Notice: Thresholds and Clocks

Step HIPAA (eCFR, 2026) PHIPA and O. Reg. 329/04
Trigger Unsecured information; presumed a breach unless a risk assessment shows low probability of compromise Any theft, loss or unauthorized use or disclosure; no harm threshold (s. 12)
Individuals Without unreasonable delay, no later than 60 calendar days after discovery First reasonable opportunity, with notice of the right to complain to the Commissioner
Regulator HHS at the same time for 500 or more people; annually for fewer IPC at the first reasonable opportunity in seven listed circumstances; annual statistics by March 1 (reg. ss. 6.3, 6.4)
Vendor to client No later than 60 calendar days First reasonable opportunity (s. 17)

Ontario offence fines reach CAD 1,000,000 for organizations (PHIPA, 2026, s. 72), and administrative penalties are capped at CAD 500,000 for organizations, plus any economic benefit gained (O. Reg. 329/04, 2026, s. 35).

CAD 1,000,000
Maximum PHIPA offence fine for organizations in Ontario (s. 72)
Source: PHIPA, 2026

Two US Changes to Track, as of November 21, 2026

  • HHS published a Privacy Rule final rule on November 19, 2026 (91 FR 74848), effective January 19, 2027, with compliance required by July 19, 2027. Access must come "in no case later than 15 calendar days after receipt of the request", with one extension of up to 30 days (HHS, 2026). PHIPA allows 30 days, also extendable by 30 (PHIPA, 2026, s. 54). Plan portal exports around the US clock.
  • The Security Rule overhaul proposed on January 6, 2025 is still a proposal; the federal agenda lists it as a long-term action with final action in July 2027 (reginfo.gov, 2026), and we found no final rule. Treat it as direction, not law.

A Worked Example

For example, a Canadian remote monitoring vendor serves an Ontario family practice and a US physician group that bills insurers electronically. The US group is a covered entity, the vendor its business associate and the vendor's cloud host a subcontractor: two agreements.

The Ontario practice is a custodian and the vendor likely its agent; if clinics share records through the platform, the network provider rules may apply too. One incident touching both means notifying both clients at the first reasonable opportunity.

What to Do Now

  1. Map every customer on both sides, and your role for each.
  2. Keep two contract templates: a business associate agreement and a PHIPA schedule naming your role.
  3. Ban secondary use in writing unless the client can authorize it.
  4. Prepare a privacy impact assessment and threat assessment for Ontario custodians.
  5. Run one breach runbook on the fastest clock, with prewritten client notices and an incident log.
  6. Get assurance both markets recognize; see ISO 27001 versus SOC 2.
  7. Diarize July 19, 2027 and recheck the Security Rule quarterly.

How Cyberphore Can Help

Every Cyberphore team member holds industry certifications such as CISSP, CISM, OSCP or GIAC, and monitoring data stays in Canadian data centres by default. Pricing is quoted after a free scoping call. To map your HIPAA and PHIPA duties, start with our privacy compliance service.

Services for this topic

Share this article

Questions and Answers

Does HIPAA apply to a Canadian health tech company?

It can. HIPAA defines a business associate by what it does for a covered entity: creating, receiving, maintaining or transmitting protected health information on its behalf. In our reading, it turns on that function, not on where the vendor is based. If your platform hosts or processes data for a US health plan or provider, expect to sign a business associate agreement and meet its terms.

Is a business associate the same as a PHIPA agent?

Not quite. Both act for a regulated health organization, but HIPAA prescribes the contract terms, while PHIPA keeps the custodian responsible for its agents and requires agents to report theft, loss or unauthorized use at the first reasonable opportunity. Ontario vendors may instead, or also, be non-agent service providers or network providers, which carry separate duties under the regulation.

How fast must a PHIPA breach be reported?

A custodian must notify affected individuals at the first reasonable opportunity, and the notice must say they can complain to the Information and Privacy Commissioner of Ontario. The Commissioner must also be told at the first reasonable opportunity in seven listed circumstances, such as theft or a significant breach. Custodians also file annual breach statistics with the Commissioner by March 1.

Can one breach response plan cover both HIPAA and PHIPA?

Yes, if it is built around the stricter rule at each step. Use PHIPA's lack of a harm threshold to decide when to escalate, notify Ontario custodians at the first reasonable opportunity, and treat HIPAA's 60 calendar days as an outer limit, not a target. Keep a log of every incident so clients on both sides can meet their own reporting duties.

Sources (10, primary and official first)

  1. Personal Health Information Protection Act, 2004, S.O. 2004, c. 3, Sched. A (consolidated from January 1, 2026) (opens in a new tab) · Government of Ontario, e-Laws,
  2. O. Reg. 329/04: General, under the Personal Health Information Protection Act, 2004 (consolidated from October 31, 2026) (opens in a new tab) · Government of Ontario, e-Laws,
  3. 45 CFR 160.103: Definitions (opens in a new tab) · Electronic Code of Federal Regulations (US),
  4. 45 CFR Part 164, Subpart D: Notification in the Case of Breach of Unsecured Protected Health Information (164.402 to 164.410) (opens in a new tab) · Electronic Code of Federal Regulations (US),
  5. 45 CFR 164.504: Uses and disclosures: Organizational requirements (opens in a new tab) · Electronic Code of Federal Regulations (US),
  6. 45 CFR 164.506: Uses and disclosures to carry out treatment, payment, or health care operations (opens in a new tab) · Electronic Code of Federal Regulations (US),
  7. 16 CFR Part 318: Health Breach Notification Rule (opens in a new tab) · Electronic Code of Federal Regulations (US),
  8. HIPAA Privacy Rule: Changes To Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens (91 FR 74848) (opens in a new tab) · US Department of Health and Human Services, Federal Register,
  9. HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (RIN 0945-AA22), Unified Agenda entry (opens in a new tab) · Office of Information and Regulatory Affairs, reginfo.gov,
  10. Provincial laws that may apply instead of PIPEDA (opens in a new tab) · Office of the Privacy Commissioner of Canada,

General information for Canadian organizations, not legal advice.

Written by

Cyberphore Security Team

Certified security analysts and consultants

  • CISSP
  • CISM
  • OSCP
  • OSCE
  • GIAC GCIH
  • GIAC GCIA
  • GIAC GPEN
  • Microsoft SC-200

Articles are researched and written by Cyberphore's security team. Every team member, from analysts to leadership, holds industry certifications, and the team monitors and responds to threats for Canadian organizations 24/7/365. Every article is fact-checked against its sources and reviewed before publishing.

How we research, fact-check and update articles: editorial standards. Spotted an error? Email Use our contact form.

Incident happening now? Our team answers 24/7: +1 236 665 1165

Keep reading

Continue Reading

Book free assessment