Alberta Clinic Security & HIA Compliance

Cybersecurity for Alberta Medical Clinics

Your EMR holds everything the Health Information Act makes you responsible for. We secure the systems Alberta clinics actually run, Wolf, Med Access, Accuro, Healthquest, Netcare, and handle the OIPC paperwork that comes with them. Trusted by Silverado Medical Clinic in Calgary.
Book a 20-Minute HIA Risk Review
A nurse at a secured clinic workstation talking with an IT security lead

Where Alberta Clinics Actually Get Breached

Not zero-days. These four, over and over — each mapping to a safeguard the HIA already requires.

The EMR Is the Crown Jewel

Whether your clinic runs TELUS Health Wolf or Med Access, QHR Accuro, or Microquest Healthquest, the EMR holds every patient record you are legally responsible for. Weak passwords, shared logins, and unmonitored remote access are the standard findings — and the standard breach paths.

Affiliate Snooping Is Prosecuted

Alberta actively prosecutes healthcare workers who look up records without a work purpose. As the custodian, the physician owner answers to the OIPC for every affiliate's access — which means audit-log review can't be something nobody owns.

Phishing Hits the Front Desk First

Clinic breaches rarely start in the EMR — they start in a front-desk mailbox, a fake e-transfer notice, or a spoofed lab result. One compromised Microsoft 365 account exposes referral letters, billing exports, and everything patients ever emailed you.

PIAs Before New Tools — Including AI Scribes

The HIA requires a Privacy Impact Assessment submitted to the OIPC before you implement systems that handle health information. That includes the AI scribes, online-booking tools, and patient portals clinics are adopting fastest right now.

Clinic-Sized, Alberta-Regulated

GuardsArm works with Silverado Medical Clinic in Calgary and custodians across Alberta. Our clinic program is built around the Health Information Act and the OIPC's processes — not US HIPAA templates with the acronyms swapped. Engagements are fixed-price and sized for independent practices, and we work alongside your existing IT provider rather than replacing them.

If your practice also handles US patient data or works with US covered entities, we scope HIPAA alongside HIA — but we will never sell you the wrong statute first.

The Clinic Security Program

Start with the assessment, or with the PIA your new system needs.

Clinic Security Assessment

A fixed-price review of your EMR access controls, Microsoft 365 tenant, backups, Wi-Fi, and remote-access setup — mapped to HIA safeguard obligations and delivered with a prioritized fix list your IT provider can execute.

HIA Privacy Impact Assessments

PIAs prepared for OIPC submission when you adopt a new EMR, portal, AI scribe, or Netcare connection — structured to the OIPC requirements, with the data-flow mapping reviewers expect.

Audit-Log & Snooping Reviews

Periodic review of EMR access logs for the patterns OIPC investigators look for — after-hours access, record views without appointments, staff viewing family members — with documented findings.

24/7 Monitoring & Incident Response

Canadian SOC monitoring of your email tenant and endpoints, sized for clinic budgets, plus a breach-response procedure that meets the HIA s.60.1 notification duties if the worst happens.

The five controls we check first in every clinic

Individual (not shared) EMR logins with MFA on remote access
MFA on the Microsoft 365 / email tenant — where phishing lands
Encrypted, tested backups that survive a ransomware event
EMR audit logging turned on, retained, and actually reviewed
Off-boarding that removes departed staff from EMR and Netcare same-day

Health Information Act

What the HIA actually asks of a clinic

Alberta clinics answer to the Health Information Act, not a US checklist. These are the duties that shape a clinic security program, in plain language.

Custodians and affiliates

Under the Health Information Act, regulated health professionals such as physicians are custodians of the health information they collect. Front-desk staff, nurses, locums, contractors and students act as affiliates of a custodian, and everything they do with patient information is done on the custodian’s authority.

In a group practice that matters more than it sounds. Someone has to be the custodian of record for the EMR, sign the privacy impact assessment and answer the Office of the Information and Privacy Commissioner (OIPC) after an incident. If that has never been written down, it is the first thing to settle.

What it looks like in practice

  • A named custodian for each information system
  • Affiliate confidentiality agreements on file
  • A privacy officer or contact patients can reach
  • Training for affiliates when they start and yearly

Reasonable administrative, technical and physical safeguards

The Act requires custodians to protect health information with reasonable safeguards against loss, unauthorized access, use, disclosure and modification. Its regulation expects written policies and procedures, a record of the safeguards in place, and periodic assessment of whether they still work.

“Reasonable” is judged after the fact, usually by the OIPC reading your file. Unique logins, multi-factor authentication on remote access, encrypted laptops, tested backups and reviewed audit logs are the controls an investigator expects a clinic to be able to show.

What it looks like in practice

  • Written privacy and security policies, actually followed
  • Unique EMR accounts, never shared logins
  • Encryption on laptops, phones and removable media
  • Audit logs kept and reviewed on a schedule
  • Same-day removal of access when staff leave

PIAs submitted to the OIPC before you change systems

Before a custodian puts in place new administrative practices or information systems that collect, use or disclose individually identifying health information, the Act requires a privacy impact assessment to be prepared and submitted to the Commissioner for review and comment.

In practice that means a new or migrated EMR, a patient portal, online booking that pulls from the chart, virtual care platforms, AI scribes and Netcare access. A PIA describes the data flows, the risks and the safeguards, and it is far easier to write before go-live than to reconstruct after a complaint.

What it looks like in practice

  • A PIA for each system that touches health information
  • Updates when a system, vendor or hosting location changes
  • Data-flow diagrams that show where information is stored
  • Evidence the safeguards described are really in place

Loss or unauthorized access with a risk of harm

If health information is lost, or accessed or disclosed without authority, the custodian must assess whether there is a risk of harm to the individual. Where there is, the custodian must notify the Commissioner, the Minister of Health and the affected individual as soon as practicable.

The regulation lists the factors to weigh, such as whether the information could be used for identity theft or fraud, whether it could cause embarrassment or damage to reputation or relationships, and whether it was protected or recovered. The assessment and its reasoning belong in writing, whichever way it goes.

What it looks like in practice

  • A breach procedure staff know how to start
  • A documented risk of harm assessment for every incident
  • Notice templates for the OIPC, the Minister and patients
  • A breach log the custodian reviews

Information managers and the agreements behind them

When an EMR vendor, hosting company or IT provider stores or processes health information for you, the HIA treats them as an information manager. The custodian must have a written agreement that meets the requirements of the regulation, and stays responsible for the information.

A hosted EMR moves server patching, data centre security and backups to the vendor, but not account management, workstation security, email or what your staff do with exported reports. Most clinic incidents happen on the clinic’s side of that line.

What it looks like in practice

  • An information manager agreement with every vendor that holds data
  • Know where data is hosted and who can reach it for support
  • Confirm how the vendor will tell you about their own incidents
  • Review vendor support access, especially remote tools

Netcare access comes with its own conditions

Alberta Netcare gives clinics access to provincial records such as lab results and dispensing history. Before access is granted, a clinic typically needs a PIA that covers its Netcare use and signed access agreements with Alberta Health, and each user needs their own credentials.

Netcare access is logged and can be audited. Looking up a record without a care purpose, including a family member’s or a colleague’s, is a recurring theme in OIPC investigations and HIA prosecutions, so Netcare accounts belong in the same joiner, mover and leaver process as the EMR.

What it looks like in practice

  • One named Netcare account per user, never shared
  • Access removed the day someone leaves
  • Periodic review of who holds Netcare access
  • Staff briefed that lookups are audited

This is a practical summary, not legal advice. For the statute in more depth, see Alberta HIA compliance.

Threat picture

Four clinic incidents, step by step

Clinic breaches follow a few well-worn paths. Each one below shows how it starts, what it means under the HIA, and the control that breaks the chain.
The most common start to a clinic incident

Phishing on the front-desk mailbox

A fake shared-document or voicemail email asks a receptionist to sign in. The attacker now holds a working Microsoft 365 or Google login and reads years of referral letters, lab notifications and patient emails.
What it means under the HIA
Every email with health information the attacker could read is potentially an unauthorized access. Without mailbox audit logs, you cannot show what was or was not opened, so the risk of harm assessment has to assume the worst.
The control that breaks the chain
MFA on every mailbox, with legacy sign-in blocked, mailbox auditing turned on, and alerts on new forwarding rules and sign-ins from unusual places.
Money, not records, is the target

Business email compromise on billing and payments

From inside a compromised mailbox, or from a look-alike domain, the attacker asks to change the banking details for a physician’s payment, a landlord, an EMR invoice or payroll. The request arrives in a real thread and looks routine.
What it means under the HIA
The money loss may not be a health information breach on its own, but the mailbox access behind it usually is. Clinics then face two problems at once: recovering funds and assessing the privacy breach.
The control that breaks the chain
A written rule that bank changes are confirmed by phone to a known number, never by reply, plus two-person approval for new payees and MFA on finance mailboxes.
The incident that closes the clinic

Ransomware on the EMR or the clinic network

An attacker gets in through remote access without MFA, an unpatched firewall or a vendor support tool. They spread to the server, file shares and backups, steal data, then encrypt everything they can reach.
What it means under the HIA
Encrypted and stolen records are both an availability problem and a disclosure problem. Data theft before encryption is now the norm, which usually means notifying patients.
The control that breaks the chain
MFA on all remote access, EDR on every workstation and server, backups an attacker cannot delete, and 24/7 monitoring so the intrusion is caught before encryption.
Still common, and the easiest to prevent

A lost or stolen laptop, phone or USB key

A physician’s laptop is stolen from a car, or a USB key with a billing export goes missing. Whether this becomes a notifiable breach often comes down to one fact: was it encrypted, and was the password with it?
What it means under the HIA
Strong encryption with a safe key is one of the factors that lowers the risk of harm. A readable device with patient data on it usually means notification.
The control that breaks the chain
Full-disk encryption enforced on every device, a screen lock, remote wipe through device management, and a ban on unencrypted USB keys.

Shared responsibility

Your EMR vendor secures the platform. You secure how it is used.

A hosted EMR takes a lot off a clinic’s plate, but not the custodian’s responsibility. This is how the work usually divides; your information manager agreement is what actually decides it.
Clinic and EMR vendor security responsibilities
AreaClinic (custodian)EMR vendor or IT provider
User accounts and leaversCreates, changes and removes EMR, email and Netcare access; owns the leaver checklist.Provides the admin console and logs; may run accounts if contracted to.
Multi-factor authenticationTurns it on and enforces it for every user, including physicians and locums.Offers MFA in the product and on support access; should require it for its own staff.
Audit log reviewDecides who reviews logs, how often, and what triggers an investigation.Records access and keeps logs available for the retention period agreed.
Workstations, Wi-Fi and printersClinic side, usually through its IT provider: patching, EDR, encryption, network separation.Not usually in scope for a hosted EMR vendor.
Hosting, servers and backupsFor an on-premises EMR, the clinic and its IT provider. For a hosted EMR, verify the vendor’s arrangements.For a hosted EMR: data centre security, patching, backups and restore testing.
Privacy impact assessmentThe custodian prepares and submits it to the OIPC.Supplies architecture, hosting and security details for the PIA.
Breach notificationThe custodian assesses risk of harm and notifies the OIPC, the Minister and patients.Must tell the custodian promptly about incidents on its side, as the agreement requires.

A question worth asking your vendor this month

“If you had a security incident affecting our data, how and how fast would you tell us, and what would you give us to complete our own risk of harm assessment?” The answer, and whether it is in your agreement, tells you a lot.

Interactive tool

Something went wrong. Do we have to notify?

Walk through the HIA risk of harm questions for a lost device, a misdirected fax, a snooping case or a cyber attack. Guidance, not legal advice; confirm with your privacy officer or counsel.
HIA breach decision helperGuidance, not legal advice

Do we have to notify?

Six questions about what happened. You will get the risk of harm factors the Health Information Act asks custodians to weigh, who must be notified, and what to write down. This is guidance, not legal advice; confirm with your privacy officer or counsel.

Question 1 of 6Nothing you enter leaves this page
1.What happened?

Pick the closest match. The Health Information Act duty covers loss of health information and unauthorized access to or disclosure of it.

Getting started

A clinic’s first 30 days

You do not need a big project to get most of the risk down. This is the order we work in with a new clinic, and most of it your IT provider can do with a clear list.
  1. Week 1: settle ownership and accounts

    Confirm the custodian and privacy officer. List every system with health information. Remove accounts for anyone who has left, end shared logins, and turn on MFA for email and remote access.
  2. Week 2: protect the data

    Check encryption on every laptop and phone. Confirm backups run, that one copy is offline or immutable, and restore a test file. Review who has vendor support access and how it is approved.
  3. Week 3: prepare for the bad day

    Write a two-page breach procedure: who to call, how to contain, how to assess risk of harm, and who notifies. Load notice templates. Make sure staff know how to report a lost device or a suspicious email.
  4. Week 4: check the paperwork and plan

    Find your PIAs and information manager agreements, note what is missing or out of date, run a first audit log review, and agree a 90-day list with your IT provider.

Small clinic or multi-site group: what changes

The duties are the same. The size of the job, and who runs it, is not.

Small clinic compared with a multi-site group
Small clinic (1 to 3 physicians)Multi-site group
Typical setupOne location, a hosted EMR, Microsoft 365 or Google, an IT provider on call.Several locations, shared EMR instance, more staff and locums, often some on-premises systems.
Custodian structureOften a single physician owner. Keep it simple and written down.Several custodians sharing systems. Document who is custodian of record and how decisions are made.
Highest-value first stepMFA, device encryption and a tested backup. Most risk sits in email and laptops.Identity and access: a single leaver process across all sites, EMR and Netcare, plus MFA everywhere.
MonitoringManaged EDR and email protection with alerts to someone who responds.24/7 monitoring across sites, with audit log review that covers every location.
PIAsUsually one EMR PIA plus updates when you add a portal or AI tool.A PIA program: an inventory of systems and a trigger for review when anything changes.
Who runs itThe clinic manager, with an IT provider and occasional specialist help.A named privacy and security lead, often supported by a virtual CISO.

Find what applies

Which laws and frameworks apply to your clinic?

Alberta and Canadian health care are preselected. Add anything else that fits, such as US patients or card payments, and see the full list with a sensible order.
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.

2 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?

Readiness check

How ready is your clinic for an incident?

A short set of questions on the basics that decide how a breach or ransomware event goes. You get a score, your top gaps and a first hour checklist.

0 of 10 answered

  1. 1. Do you have a written incident response plan that people can find?
  2. 2. Has the plan been tested in the last 12 months, for example in a tabletop exercise?
  3. 3. Is there a current contact list for the response: internal leads, IT providers, vendors?
  4. 4. Are backups kept offline or immutable, and has a restore been tested?
  5. 5. Are security logs kept long enough to investigate, ideally 90 days or more?
  6. 7. Is it agreed who can authorise disruptive actions, like shutting down systems or taking the business offline?
  7. 8. Do you have communication templates for staff, customers and regulators?
  8. 9. Is endpoint detection and response (EDR) deployed on all laptops and servers?
  9. 10. Is multi-factor authentication enforced on email, remote access and admin accounts?

Your score appears here as you answer.

It takes about two minutes. “Not sure” is a valid answer.

Alberta Medical Clinic Security FAQs

Common questions from Alberta physicians and clinic managers

Still Have Questions?

Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.

Fifteen Minutes Tells You Where Your Clinic Stands

A scoping call with the physician owner or clinic manager, with plain answers about what you need and what you don't.