HIPAA is a US law that reaches a Canadian company the moment that company creates, receives, maintains, or transmits protected health information (PHI) on behalf of a US covered entity or another business associate. The company is then a HIPAA business associate under 45 CFR 160.103, bound by a business associate agreement (BAA), while PIPEDA and provincial health laws such as Ontario's PHIPA still apply at home.
At a glance
HIPAA reaches Canadian vendors through the customer relationship, not through geography
- Trigger: handling PHI for a US covered entity or another business associate
- Vendor's role: business associate, or subcontractor business associate
- Contract: a BAA is required before PHI flows (45 CFR 164.308(b), 164.314(a))
- Breach clock: notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery (164.410)
- Certification: HHS does not recognize any private HIPAA certification
- Pending change: the January 2025 Security Rule overhaul is still a proposal, with final action targeted for July 2027
- Canadian side: PIPEDA, plus a provincial health statute (PHIPA in Ontario) when serving custodians
Does HIPAA apply to Canadian companies?
HIPAA applies to a Canadian company that performs a function involving PHI for a US covered entity, wherever the company is incorporated or hosted. The definition in 45 CFR 160.103 turns on the activity: a business associate is a person who, on behalf of a covered entity, creates, receives, maintains, or transmits protected health information.
HIPAA sorts regulated organizations into two groups:
| HIPAA role | Who the role covers | How a Canadian company ends up here |
| Covered entity |
|
Rare. Possible if the company bills US insurers as a provider |
| Business associate | Anyone handling PHI on behalf of a covered entity, including cloud and data-transmission services | The usual route, for vendors selling to US providers or payers:
|
| Subcontractor business associate | Anyone handling PHI on behalf of a business associate | Selling to a US digital-health company that is itself a business associate |
HHS's cloud computing guidance closes two escape routes: a provider storing only encrypted ePHI without the key is still a business associate, and ePHI may be stored on servers outside the United States only under a BAA and the rest of the HIPAA Rules.
Which Canadian health-tech companies are HIPAA business associates?
| Question | If yes | If no |
| 1. Is any customer a US provider, health plan, clearinghouse, or their vendor? | Go to 2 | HIPAA does not apply |
| 2. Will your product or staff handle identifiable patient health information for that customer? | Go to 3 | HIPAA likely does not apply. Confirm in writing |
| 3. Is the customer a covered entity? | You are a business associate | Go to 4 |
| 4. Is the customer a business associate? | You are a subcontractor business associate | Get a legal opinion |
Data de-identified under the HIPAA standard is not PHI, but treat that argument as a documented legal position, not an assumption.
What does a HIPAA business associate agreement commit a Canadian vendor to?
A HIPAA business associate agreement is the contract that makes a Canadian vendor's HIPAA obligations concrete and enforceable by the customer. Under 45 CFR 164.314(a), the BAA must require the vendor to:
- Comply with the Security Rule
- Flow the same terms down to any subcontractor that handles ePHI
- Report security incidents and breaches of unsecured PHI to the covered entity
The flow-down clause catches Canadian vendors. Every sub-processor in a vendor's stack that touches PHI needs a separate BAA with that vendor. Common examples:
- Hosting
- Support desk
- Transcription
- AI inference
In one telehealth company's HIPAA and GDPR gap assessment, discovery found more than 400 applications in use and no record of which held a BAA. One collaboration platform was on a plan tier that did not match the company's use of the platform with sensitive data. Plan tiers decide whether a BAA is available, so tier selection is a compliance decision.
A vendor risk assessment process that tracks BAA status per vendor is the practical control.
Watch out
A signed BAA commits a Canadian vendor to the Security Rule. Only the risk analysis and evidence show the vendor meets the rule
The BAA is a contractual promise. The written risk analysis, the sub-processor BAA list, and incident response records are what show the promise is kept when a customer or OCR asks.
What does the HIPAA Security Rule require of a business associate?
The HIPAA Security Rule requires a business associate to protect the confidentiality, integrity, and availability of ePHI with administrative, physical, and technical safeguards, starting with a documented risk analysis. 45 CFR 164.308(a)(1)(ii)(A) requires an accurate and thorough assessment of the potential risks and vulnerabilities to ePHI held by the covered entity or business associate.
| HIPAA Security Rule safeguard | Citation | What the safeguard covers for a SaaS vendor |
| Administrative safeguards | 45 CFR 164.308 |
|
| Physical safeguards | 45 CFR 164.310 | Mostly inherited from the cloud provider, but documented:
|
| Technical safeguards | 45 CFR 164.312 |
|
OCR's Risk Analysis Initiative targets the written HIPAA risk analysis. The 2025 Comstar and BST & Co. CPAs settlements with business associates both cite the risk analysis.
How fast must a business associate report a HIPAA breach?
A HIPAA business associate must notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery. The covered entity then sends the notices in the table below. A BAA can set a shorter window, so read the contract first.
| HIPAA breach notice | Sender | Deadline | Citation |
| Business associate to covered entity | The vendor | No later than 60 calendar days after discovery | 164.410 |
| Covered entity to individuals | The customer | No later than 60 calendar days after discovery | 164.404 |
| Covered entity to media | The customer | 60 days, when more than 500 residents of a state are affected | 164.406 |
| Covered entity to HHS | The customer | 500 or more: with individual notice. Fewer than 500: within 60 days of year end | 164.408 |
HHS's ransomware fact sheet treats ePHI encrypted by an attacker as a breach unless a low probability of compromise can be shown.
Can HHS enforce HIPAA against a business associate?
HHS can enforce HIPAA directly against business associates. HHS's direct liability fact sheet lists the obligations, including:
- Security Rule compliance
- Breach notice to the covered entity
- Permitted uses and disclosures of PHI
- BAAs with subcontractors
Two 2025 OCR settlements with business associates:
| OCR settlement | Business associate | Outcome |
| Comstar, LLC (May 2025) | Ambulance billing service. Ransomware affected 585,621 individuals | $75,000 and a two-year corrective action plan. OCR found no accurate and thorough risk analysis |
| BST & Co. CPAs (August 2025) | Accounting firm receiving PHI. Ransomware attack | $175,000 and a two-year corrective action plan, under the Risk Analysis Initiative |
Civil money penalties follow four culpability tiers in 45 CFR 160.404, from did not know to willful neglect not corrected, with amounts adjusted each year for inflation. For a Canadian vendor, the first consequence is often contractual: BAAs commonly carry termination rights and indemnities.
What is changing in the HIPAA Security Rule?
HHS proposed a broad rewrite of the HIPAA Security Rule, and as of October 2026 the rewrite remains a proposal. The notice of proposed rulemaking was published in the Federal Register on January 6, 2025 (90 FR 898), comments closed March 7, 2025, and the 2026 Unified Agenda moved the rule to long-term actions and the target for final action from May 2026 to July 2027. No final rule has been published.
| Proposed HIPAA Security Rule change (not yet law) | Why a Canadian vendor should care now |
| Remove the addressable versus required distinction | Every specification becomes mandatory |
| Encrypt all ePHI at rest and in transit, with limited exceptions | No more judgment call on encryption |
| Require multi-factor authentication | Close MFA gaps now |
| Written asset inventory and network map, reviewed every 12 months | Feeds the risk analysis |
| Restore critical systems and data within 72 hours | Needs tested disaster recovery |
| Vulnerability scans every six months, penetration testing, and an annual compliance audit | Testing cadence becomes auditable |
| Written verification from business associates every 12 months that technical safeguards are deployed | Customers collect the verification from vendors every year |
| BAAs require reporting contingency plan activation within 24 hours | A new, short contract clock |
Building toward the proposal is a reasonable hedge, since much of the proposal describes controls US buyers already ask about.
Watch out
Label proposed HIPAA Security Rule controls as proposed in every customer document
The January 2025 HIPAA Security Rule NPRM is not law. Describing the proposed controls as current HIPAA requirements in a questionnaire or trust center misstates the law to the customer.
HIPAA + PHIPA gap assessment for Canadian health-tech
Selling to US providers? Map data flows, BAAs, and safeguards against HIPAA, PHIPA, and PIPEDA, and build one effective security program. See the HIPAA and HITRUST Accelerator.
Is there a HIPAA certification in Canada?
There is no official HIPAA certification in Canada or the United States. The HHS Security Rule FAQ states that no standard requires a regulated entity to certify compliance, and that HHS does not endorse or otherwise recognize private organizations' certifications regarding the Security Rule. A purchased HIPAA certificate does not prevent an OCR finding.
A US hospital asking a Canadian vendor for HIPAA certification is asking for evidence, usually one of three kinds:
| Evidence type | Description | Law or voluntary? | Best fit |
| HIPAA Security Rule risk analysis and policy set |
|
Required by HIPAA law | Always the baseline, usually paired with a questionnaire |
| SOC 2 Type II with HIPAA mapping | Independent CPA attestation over a period, with the Security Rule tested as additional criteria (often called SOC 2+ HIPAA) | Voluntary attestation | Digital-health and mid-market buyers. Reuses SaaS controls |
| HITRUST e1, i1, or r2 | Certifiable assessment on the HITRUST CSF | Voluntary certification | Health systems and payers that name HITRUST in the contract |
HIPAA and PHIPA are laws. SOC 2 and HITRUST are voluntary attestations and certifications that help a company prove compliance with those laws. Related guides:
- The SOC 2 Type II report guide explains what the report tests
- SOC 1 vs SOC 2 covers which report fits
- SOC 2 vs HIPAA shows how one audit firm can test both in the same engagement
- The Type I first post covers starting with a Type I
What is the HIPAA equivalent in Canada?
Canada has no single HIPAA equivalent. Health information falls under:
- PIPEDA, for commercial activity
- Provincial health statutes, for custodians and their service providers
- Public-sector laws, for hospitals and health authorities
The Office of the Privacy Commissioner of Canada lists four provincial health laws as substantially similar to PIPEDA:
- Ontario
- New Brunswick
- Nova Scotia
- Newfoundland and Labrador
PIPEDA still applies to personal information transferred across provincial or national borders.
Which health privacy law applies in each province and territory?
| Province or territory | Health information law | Private-sector law that may also apply |
| Ontario | Personal Health Information Protection Act, 2004 (PHIPA), substantially similar to PIPEDA | PIPEDA |
| Quebec | Act respecting health and social services information (chapter R-22.1), mostly in force since July 1, 2024 | Private Sector Act, as amended by Law 25 |
| British Columbia | E-Health (Personal Health Information Access and Protection of Privacy) Act, for designated health information banks | PIPA (FIPPA covers health authorities) |
| Alberta | Health Information Act | PIPA |
| Manitoba | The Personal Health Information Act (C.C.S.M. c. P33.5) | PIPEDA |
| Saskatchewan | The Health Information Protection Act (HIPA) | PIPEDA |
| New Brunswick | Personal Health Information Privacy and Access Act, substantially similar to PIPEDA | PIPEDA |
| Nova Scotia | Personal Health Information Act, substantially similar to PIPEDA | PIPEDA |
| Newfoundland and Labrador | Personal Health Information Act, substantially similar to PIPEDA | PIPEDA |
| Prince Edward Island | Health Information Act | PIPEDA |
| Yukon | Health Information Privacy and Management Act (HIPMA) | PIPEDA |
| Northwest Territories | Health Information Act, in force since October 1, 2015 | PIPEDA |
PIPEDA adds a separate breach duty (OPC guidance):
- Report a breach of security safeguards that creates a real risk of significant harm to the Privacy Commissioner and affected individuals as soon as feasible
- Keep a record of every breach for two years
Bill C-36, tabled on June 15, 2026, would replace the privacy rules in PIPEDA with a new Protecting Privacy and Consumer Data Act. As of October 31, 2026, the bill is at second reading in the House of Commons, so PIPEDA still applies. The Bill C-27 and Law 25 post covers the earlier federal reform attempt and Quebec's Law 25.
What does PHIPA add for a Canadian vendor serving Ontario health care?
PHIPA regulates Ontario health information custodians (hospitals, clinics, physicians, labs) and reaches their technology vendors in two ways. A vendor acting for the custodian is an agent and must follow the custodian's rules. A vendor that supplies electronic services without acting as agent must meet the requirements in PHIPA s. 10(4) and O. Reg. 329/04, s. 6:
- Use PHI only as necessary to provide the service
- Not disclose the PHI
- Bind the vendor's employees and agents to the same restrictions
A vendor that lets two or more custodians share PHI electronically is a health information network provider, which must also notify affected custodians of unauthorized access at the first reasonable opportunity and publish a plain-language description of the network's safeguards.
| Obligation | HIPAA (US customers) | PHIPA (Ontario customers) |
| Vendor's legal role | Business associate | Agent, electronic service provider, or health information network provider |
| Contract | BAA required | Agent or service agreement written by the custodian. In PHIPA Decision 284, the IPC found a clinic's agreement with an IT provider lacked key provisions |
| Breach notice to individuals | Customer, without unreasonable delay and no later than 60 days after discovery | Custodian, at the first reasonable opportunity (s. 12(2)), plus the IPC where prescribed |
| Maximum fines or penalties | Four-tier civil money penalties, adjusted for inflation |
|
Ontario's Information and Privacy Commissioner made the vendor point explicit in PHIPA Decision 284 (June 2025), on the ransomware attack against TransForm Shared Service Organization, a shared IT provider for five hospitals and a family health team clinic. The IPC found that the lack of privileged account management, including MFA, on the compromised administrator accounts was likely a contributing factor, and that outsourcing does not relieve custodians of responsibility. The cost of a data breach in Canada post puts numbers on incidents like the TransForm attack, and the IPC's AMP announcement sets out the penalty ranges.
Key insight
Ransomware encryption alone triggers notice under both HIPAA and PHIPA
HHS treats ePHI encrypted by ransomware as a presumed HIPAA breach, and the Ontario IPC found in PHIPA Decision 284 that hostile encryption was an unauthorized use and loss of PHI requiring notice under s. 12(2).
What should a HIPAA + PHIPA readiness checklist cover for Canadian health-tech vendors?
A Canadian vendor selling to US providers, Canadian custodians, or both can use one checklist, because the controls overlap far more than the statutes do.
| # | Readiness item | HIPAA reference | PHIPA / PIPEDA reference |
| 1 | Map every data flow touching patient health information, by customer and jurisdiction | 164.308(a)(1) risk analysis |
|
| 2 | Record your role per customer:
|
160.103 | O. Reg. 329/04, s. 6 |
| 3 | Complete and date a written Security Rule risk analysis, then a risk management plan | 164.308(a)(1)(ii)(A)-(B) | PHIPA s. 12 safeguards |
| 4 |
|
164.308(b), 164.314(a) | O. Reg. 329/04 restrictions bind staff |
| 5 | Enforce:
|
164.312 (and the proposed rule) | Lesson from PHIPA Decision 284 |
| 6 | One incident response plan with parallel clocks:
|
164.410 |
|
| 7 | Treat ransomware encryption as notifiable until assessed | HHS ransomware guidance | PHIPA Decision 284 |
| 8 | Name a security official and a privacy officer, and train staff every year | 164.308(a)(2), (a)(5) | PIPEDA accountability principle |
| 9 | Test restoration against a 72-hour target | 164.308(a)(7) (and the proposed rule) | Availability of PHI for custodians |
| 10 | Pick the evidence buyers accept:
|
Not a legal requirement | Not a legal requirement |
Items 1 to 4 decide whether a BAA can be signed honestly. Items 5 to 9 decide whether the security questionnaire that follows goes well.
Can one security program cover HIPAA and PHIPA?
A Canadian company handling PHI for the US health system is a business associate, and the BAA turns that status into obligations the vendor must prove. PHIPA and PIPEDA add Canadian duties to the same data, with different clocks and regulators. A vendor selling into both markets can meet all three regimes with one effective security program: map HIPAA, PHIPA, and PIPEDA onto the same controls, and add SOC 2 or HITRUST when a contract calls for a report.
HIPAA + PHIPA gap assessment for Canadian health-tech selling to US providers
Truvo's security architects map your data flows, BAAs, and safeguards against HIPAA, PHIPA, and PIPEDA and hand back one prioritized remediation plan. See the HIPAA and HITRUST Accelerator, or the privacy program service for Law 25 and PIPEDA work.
Frequently asked questions about HIPAA in Canada
Does HIPAA apply in Canada?
HIPAA applies to a Canadian company that creates, receives, maintains, or transmits protected health information for a US covered entity or business associate. The company becomes a business associate under 45 CFR 160.103, signs a business associate agreement, and is directly liable for the HIPAA Security Rule. Otherwise, only Canadian privacy law applies.
Is there a HIPAA certification in Canada?
There is no official HIPAA certification in Canada or the US, and HHS does not endorse or recognize private organizations' HIPAA certifications. Buyers asking for certification want evidence: a documented Security Rule risk analysis and policies, a SOC 2 Type II report with HIPAA mapping, or a HITRUST e1, i1, or r2 certification for larger health systems.
What is the Canadian equivalent of HIPAA?
Canada has no single equivalent. PIPEDA governs personal information in private-sector commercial activity, and provinces have their own health information statutes, such as Ontario's PHIPA, Alberta's Health Information Act, and Quebec's Act respecting health and social services information. Ontario, New Brunswick, Nova Scotia, and Newfoundland and Labrador have health laws deemed substantially similar to PIPEDA.
Is PHIPA the same as HIPAA?
No. PHIPA is an Ontario law regulating health information custodians and the vendors serving them. HIPAA is a US federal law regulating covered entities and business associates. PHIPA requires breach notice at the first reasonable opportunity, where HIPAA sets a 60-day outer limit. One security program can meet both.
When does the new HIPAA Security Rule take effect?
The updated HIPAA Security Rule has no effective date yet. HHS published the proposal on January 6, 2025, and the 2026 Unified Agenda lists the rule as a long-term action with final action targeted for July 2027. Until a final rule is published, the current Security Rule at 45 CFR Part 164, Subpart C, is the law.
Ready to Start Your Compliance Journey?
Get a clear, actionable roadmap with our readiness assessment.
Contact Us
Sample SOC 2 Control List
Input your email to download the list.
About the Author
Former security architect for Bank of Canada and Payments Canada. 20+ years building compliance programs for critical infrastructure.