Healthcare security

Healthcare cybersecurity for Canadian and US organizations

Clinics, health authorities and health technology companies answer to different laws depending on where they operate. Choose your path: Canadian health information laws such as Alberta’s HIA and Ontario’s PHIPA, or HIPAA in the United States.

Choose your path

Which rules do you answer to?

Most organizations start with the law that governs the health information they hold. If you serve patients or clients in both countries, either path works; tell us in the form.

Canada

Canadian custodians and health technology companies

For physicians, clinics, health authorities and their vendors working under provincial health information law.

  • Alberta HIA: privacy impact assessments, information manager agreements, access logging and breach procedures
  • Ontario PHIPA: logging and auditing of access to electronic records, agent agreements and breach notification
  • PIPEDA and other provincial laws for health technology companies and multi-province services
  • A check of whether day-to-day systems match the privacy documentation on file

Delivered case study

HIA compliance scoping assessment for two Alberta medical clinics

Two clinics under shared ownership had a Privacy Impact Assessment and security manual on file, but no independent check of whether day-to-day systems matched them. Our team reviewed the documentation against what was deployed and went on site at both locations. Practice and documentation diverged in four areas: endpoint protection, access management, network design and email security. The clinics received a findings report, an executive summary and a costed remediation plan.

Read the Alberta clinics case study

More detail: Alberta HIA, Ontario PHIPA, Alberta medical clinics.

United States

US healthcare, and Canadian vendors serving it

For US providers and health plans, and for Canadian companies that handle protected health information as a business associate.

  • A documented HIPAA Security Rule risk analysis covering every system with patient data
  • Administrative, physical and technical safeguards, mapped to what is actually deployed
  • Business associate obligations for Canadian vendors that serve US providers or health plans
  • Breach assessment and notification procedures to the covered entity

More detail: HIPAA readiness, HIPAA compliance services.

Dealing with an active incident? Call +1 (587) 821-5997 at any time.

Healthcare threat landscape

Why attackers target clinics, health authorities and their vendors

Health information is valuable, care cannot pause, and the systems behind it are spread across clinics, labs, vendors and home devices. That combination gives attackers leverage. These are the patterns we see most in the sector.

Ransomware that stops care

Attackers encrypt EMR, scheduling and imaging systems and threaten to publish patient records. Clinics feel pressure to pay because appointments, prescriptions and results stop.
  • Backups reachable from the same admin accounts
  • Remote access without MFA

Phishing and stolen credentials

A single compromised mailbox or EMR login exposes referrals, lab results and billing data, and becomes a launch point for fraud against patients and partners.
  • Shared logins at front desks
  • Mailbox rules nobody created

Vendors and service providers

Billing companies, EMR hosts and managed IT providers hold access to many clinics at once. A breach at one supplier becomes a breach at all its customers.
  • No information manager or agent agreements
  • Vendor remote access left always on

Snooping by insiders

Staff looking up a neighbour, colleague or celebrity in the record system is one of the most common breaches reported to Canadian privacy commissioners, and one that audit logs exist to catch.
  • Access logs that nobody reviews
  • Broad roles that see every patient

Medical devices and legacy systems

Imaging, lab and monitoring devices often run unsupported operating systems that cannot be patched or take an agent, and sit on the same flat network as email.
  • No device inventory
  • Devices on the office network

Misdirected and exposed information

Faxes and emails sent to the wrong number, cloud folders shared by link, and lost laptops are everyday incidents. Most are preventable with simple controls.
  • Unencrypted laptops
  • Public file sharing links

Regulations

The health privacy laws Canadian organizations work under

Canada has no single health privacy law. Provincial health information acts govern custodians, PIPEDA covers commercial activity where provincial law does not, and HIPAA reaches Canadian vendors that serve US healthcare clients.

Alberta Health Information Act

Applies to: Custodians such as physicians, pharmacists, dentists, Alberta Health Services and others named in the Act, plus their affiliates. Vendors act as information managers.

The HIA sets rules for collecting, using and disclosing health information, and requires custodians to protect it with reasonable administrative, technical and physical safeguards.

Custodians must prepare privacy impact assessments for new systems or changes to existing ones and submit them to the Information and Privacy Commissioner. Breaches that create a risk of harm must be reported to the Commissioner, the Minister and the affected individuals.

Alberta HIA compliance services

What it expects in practice

  • Privacy impact assessments for new systems such as a new EMR
  • Information manager agreements with IT and software vendors
  • Role-based access and audit logs of who viewed what
  • Breach assessment and notification procedure

Ontario Personal Health Information Protection Act

Applies to: Health information custodians in Ontario, their agents, and electronic service providers and health information network providers.

PHIPA requires custodians to take reasonable steps to protect personal health information against theft, loss and unauthorized use or disclosure, and to ensure records are retained and disposed of securely.

Patients must be notified of privacy breaches, and certain categories, such as snooping, breaches involving a group of records or those that trigger discipline, must also be reported to the Information and Privacy Commissioner. Electronic access must be logged and audited.

Ontario PHIPA compliance services

What it expects in practice

  • Logging and auditing of access to electronic records
  • Agent agreements and staff confidentiality undertakings
  • Breach notification to patients, and to the IPC where required
  • Annual statistical breach reporting to the IPC

Personal Information Protection and Electronic Documents Act

Applies to: Private-sector organizations in commercial activity, including many health technology and service companies, except where a province has a substantially similar law for that activity.

Ontario, New Brunswick, Nova Scotia and Newfoundland and Labrador have health information laws recognized as substantially similar to PIPEDA for custodians. Health technology companies, private clinics outside those regimes, and data moving across borders often still fall under PIPEDA.

PIPEDA requires safeguards appropriate to the sensitivity of the information, and health information is among the most sensitive. Breaches with a real risk of significant harm must be reported to the federal Commissioner and the people affected, and every breach must be recorded.

PIPEDA compliance services

What it expects in practice

  • Safeguards matched to sensitivity
  • Breach records kept for 24 months
  • Accountability for data handled by service providers
  • Meaningful consent for collection and use

Other provincial health information laws

Applies to: Custodians and trustees in each province, under that province’s law.

Saskatchewan’s Health Information Protection Act and Manitoba’s Personal Health Information Act set similar duties for trustees. In British Columbia, public health bodies fall under FIPPA and private practices under BC PIPA. Quebec added its Act respecting health and social services information in 2024, alongside Law 25.

Organizations that work in several provinces, such as virtual care providers and health software vendors, have to meet the strictest common requirements and track the differences.

Multi-province compliance

What it expects in practice

  • A map of which law applies to each service and province
  • Breach procedures that meet each regime’s timing and recipients
  • Data residency and transfer rules where they apply

HIPAA, when you serve US healthcare

Applies to: Canadian vendors that create, receive, keep or transmit protected health information for US providers or health plans, as business associates.

A US client will ask you to sign a business associate agreement. That brings the HIPAA Security Rule with it: a documented risk analysis, administrative, physical and technical safeguards, and breach notification to the client.

HIPAA readiness

What it expects in practice

  • Risk analysis covering every system with US patient data
  • Business associate agreements, including with your own subcontractors
  • Breach reporting to the covered entity

This is general information, not legal advice. Your privacy officer or counsel should confirm which laws apply to each service you provide.

What good looks like

A maturity ladder for healthcare security

Most organizations are somewhere between the first and third rung. Use the signs below to place yourself, then aim one level up rather than trying to jump to the top.
  1. Level 1: Reactive

    Security depends on the IT provider and good luck. Nobody owns privacy or security risk.

    • Shared logins at reception
    • Backups never restore-tested
    • No privacy impact assessment for the EMR
    • Incidents handled ad hoc
  2. Level 2: Foundational

    The basics are in place and someone is accountable for privacy and security.

    • Named privacy officer
    • MFA on email and remote access
    • Encrypted laptops and phones
    • Vendor agreements signed
  3. Level 3: Managed

    Controls are monitored, access is reviewed and incidents follow a plan.

    • EMR access logs reviewed for snooping
    • Medical devices inventoried and segmented
    • 24/7 monitoring of endpoints and identity
    • Yearly risk assessment and tabletop
  4. Level 4: Resilient

    The organization expects incidents and can keep care running through them.

    • Downtime procedures tested with clinical staff
    • Immutable, isolated backups with recovery times known
    • Vendor risk reviewed before contracts
    • Security reported to leadership with metrics

Getting started

A sensible first 90 days

Where we usually start with a healthcare organization, so effort goes where risk is highest.
  1. Inventory health data

    Where patient information lives, who can reach it, which vendors hold it.
  2. Close the quick wins

    MFA, device encryption, removing shared logins and checking backups restore.
  3. Turn on monitoring

    Endpoints, identity and email under 24/7 watch, and EMR access logs reviewed.
  4. Document and rehearse

    Privacy impact assessment updated, vendor agreements checked, a ransomware tabletop run.

Find what applies to you

Which health privacy laws and frameworks apply to you?

Answer eight questions about where you operate and what you handle. You will see the laws and frameworks that likely apply, why, and an order of work.
Compliance framework finderGuidance, not legal advice

Which frameworks and laws apply to you?

Answer eight quick questions. You will get the laws and frameworks that likely apply, why, and a sensible order to tackle them.

0 of 8 answeredAbout 2 minutes
Where does your organization operate?

Pick every place you have offices, staff or customers you serve directly.

Select all that apply.

Do you collect, use or store personal health information?

Health information includes diagnoses, test results, prescriptions and health card numbers.

Select all that apply.

Do you take card payments?
Do you sell software or services to larger businesses?

Enterprise buyers usually send security questionnaires before they sign.

Are you a regulated financial organization?
Are you a public body?
Whose personal data do you handle beyond Canada?

Select all that apply.

What is pushing compliance up the list right now?

Healthcare security questions

Do you work with both Canadian and US healthcare organizations?

Yes. Our team is based in Calgary, with an office in Austin, Texas. Canadian custodians and health technology companies usually start from the provincial health information law that applies to them, such as Alberta’s HIA or Ontario’s PHIPA. US providers, and Canadian vendors serving them, start from the HIPAA Security Rule.

What does a review involve?

It starts with a scoping call about your systems, obligations and what prompted the review. We then agree the scope in writing. A review typically compares your privacy and security documentation with what is actually deployed, and ends with findings and a prioritized remediation plan.

Will security work disrupt patient care?

We plan changes with your clinical and IT staff and schedule anything disruptive in agreed maintenance windows. Where a device or system cannot safely take an agent or a scan, we say so and agree another approach, such as network segmentation and monitoring.

Do you look at medical devices?

Yes, as part of a review or a monitoring engagement: how connected devices are inventoried, which network they sit on, and how they are watched. Many medical devices run software that cannot be patched or take an agent, so segmentation is usually the main control.

What happens if we are hit by ransomware?

For an active incident, call +1 (587) 821-5997 at any time. For clients we monitor, the escalation path, who authorizes containment and the response commitments are agreed during scoping and set out in the service agreement.

Request a healthcare security review

Tell us which rules you answer to and what prompted the review. We reply within one business day to arrange a scoping call.