Proudly Canadian flag Canadian

Solutions

Ready to optimize your mobile device strategy?

Speak with a mobility expert to find the right solution for your organization.

Contact us

Products

Ready to optimize your mobile device strategy?

Speak with a mobility expert to find the right solution for your organization.

Contact us

Industries

Ready to optimize your mobile device strategy?

Speak with a mobility expert to find the right solution for your organization.

Contact us

Partners

Resources

Want to learn about enterprise mobility?

Read expert insights, reports, and action plans from Canada's leading mobility experts.

Browse the Blog

Reports

Want to learn about enterprise mobility?

Read expert insights, reports, and action plans from Canada's leading mobility experts.

Browse the Blog

Company

PHIPA compliance for mobile devices: a checklist for Ontario hospitals and health teams

PHIPA compliance for mobile devices means Ontario health information custodians take reasonable steps to protect personal health information on every phone, tablet and handheld that holds it. In practice, the Information and Privacy Commissioner of Ontario (IPC) expects strong encryption, controlled access, protection through repair and disposal, and prompt reporting when a device holding health information is stolen.

If you run IT or privacy for a hospital, long-term care home or home care organization, this checklist covers who PHIPA applies to, what the IPC expects on mobile devices, how to handle shared devices, repairs and disposal, when a lost or stolen device must be reported, and how to prepare for an IPC review. It’s practical guidance, not legal advice, so confirm how it applies with your privacy officer or legal counsel.

Definition

PHIPA is Ontario’s Personal Health Information Protection Act, the law that governs how health information custodians collect, use, protect and dispose of personal health information. Custodians include hospitals, long-term care homes and health care practitioners. Their agents and IT service providers have obligations too, but the custodian stays accountable.

Key takeaways

  • The IPC has required strong encryption of health information on mobile devices since 2010. Identifiable, unencrypted health information on a mobile device isn’t acceptable.
  • Encryption also changes your breach reporting duty. Stolen health information must be reported to the IPC unless it was encrypted or de-identified.
  • Custodians stay accountable when providers handle devices. Repair, staging and disposal providers must protect health information on the custodian’s behalf.
  • The device lifecycle is where most gaps sit. Shared sign-in, repairs, spares and disposal need the same controls as the MDM console.
  • Penalties are real. The IPC can issue administrative monetary penalties of up to $500,000 for organizations.

Who PHIPA applies to when mobile devices hold health information

PHIPA applies to health information custodians and the people and organizations that handle personal health information for them. For mobile devices, three roles matter.

Custodians such as hospitals, long-term care homes and clinics are accountable for the health information on their devices. Agents act on the custodian’s behalf, which can include staff, contractors and some service providers. Electronic service providers supply IT services, and the IPC says they must not use the personal health information for anything other than what’s necessary to provide the service, while the custodian remains ultimately accountable.

Which role a mobile device provider plays depends on the arrangement, so confirm it with your privacy officer and put it in the contract. Other provinces have their own health information laws, so organizations outside Ontario should check theirs.

What the IPC expects for health information on mobile devices

The IPC expects health information on mobile devices to be strongly encrypted, protected by strong authentication, and removable remotely if a device is lost. Those expectations come from IPC orders and guidance going back to 2007.

Strong encryption: what the IPC’s orders and fact sheet say

The IPC’s 2010 fact sheet Health-Care Requirement for Strong Encryption sets out what strong encryption means for health information on mobile devices, following orders on stolen and lost devices. In Order HO-008 (June 2010), a hospital laptop that was believed to be encrypted was stolen without encryption in place, and the Commissioner wrote that “personal health information must either be de-identified or encrypted.”

The lesson from HO-008 is that encryption has to be verified, not assumed. MDM compliance reports that confirm encryption on every enrolled device are the evidence you’ll want if a device goes missing.

Passwords, auto-lock and remote wipe on clinical devices

Passwords, auto-lock and remote wipe are the IPC’s other baseline expectations for mobile devices. Its guide Safeguarding Privacy on Mobile Devices recommends strong passwords, encryption, automatic locking, remote locate and wipe, and reporting lost or stolen devices immediately. The IPC’s 2025 privacy handbook also tells health organizations to encrypt data on all mobile and portable storage devices, both in transit and at rest.

PHIPA mobile device checklist for hospitals and health teams

A PHIPA mobile device checklist turns the IPC’s expectations into controls you can check and evidence you can show. The two tables below cover the controls hospitals and health teams most often need. They’re a starting point, so add anything your own privacy program requires.

Device security controls for PHIPA

Device security controls for PHIPA are set and reported through your MDM platform.

Control What to check Evidence to keep
Encryption Every device holding health information is encrypted, verified by MDM MDM encryption compliance report
Authentication Strong passcodes or badge sign-in, no shared generic logins MDM passcode policy and sign-in configuration
Auto-lock Devices lock after a short idle period MDM policy setting
Remote lock and wipe Every device can be locked or wiped, and staff know how to report a loss Lost-device procedure and wipe logs
App control Only approved clinical and work apps can access health information Approved app list and MDM app policy
Shared-device sessions Users sign out between shifts, with no data left from the last user Shared-device configuration
OS and security updates Devices are on supported versions and receive security updates MDM update report and model support dates

Lifecycle and record-keeping controls for PHIPA

Lifecycle and record-keeping controls for PHIPA cover what happens to devices and information outside the MDM console.

Control What to check Evidence to keep
Asset records Every device is tracked by serial number, location and status Asset register
Repair and spares Devices are wiped or protected before repair, with custody tracked Repair chain-of-custody records
Disposal Retired devices are securely sanitized or destroyed Certificate of destruction per serial number
Provider agreements Device and IT providers’ roles and obligations are in writing Signed agreements
Breach log Every lost or stolen device is recorded, whether or not it’s reported Breach log for annual statistics

Shared clinical devices and sign-in under PHIPA

Shared clinical devices need sign-in controls that tie each session to one person and clear data between users. Phones and tablets that stay on a unit and pass between nurses across shifts are common in hospitals, and they’re where generic logins and auto-login settings tend to creep in.

Check that each user signs in with their own credentials or badge, that sessions end when a shift ends, and that clinical apps don’t keep data on the device after sign-out. Review shared-device settings after every app or OS update, because updates can reset them.

Protecting health information when devices are repaired or swapped

Protecting health information during repairs and swaps means knowing where every device is and what’s on it until it comes back or is destroyed. A device sent for repair still holds whatever was on it unless it was wiped first.

Repair and chain of custody for clinical devices

Repair and chain of custody for clinical devices starts before the device leaves the unit. Wipe it remotely where possible, record the serial number and handoff, and confirm who handles it at each step and where the repair happens. Read more about chain of custody for IT assets.

Spare devices and residual data

Spare devices need the same care in reverse. A spare that was used before must be wiped and restaged before it goes to a new unit, so no data from the previous user or unit stays on it. Check that your spare pool process includes a wipe and a fresh enrolment every time.

Disposing of mobile devices that held health information

Mobile devices that held health information should be securely sanitized or physically destroyed before they leave your control, with a record for each one. A basic factory reset isn’t enough evidence on its own that health information can’t be recovered.

The US National Institute of Standards and Technology publishes NIST SP 800-88 Revision 2 (2025), Guidelines for Media Sanitization, which many Canadian organizations use as their standard. Ask for a certificate of destruction for every serial number, and keep it with your asset records. Read about certificates of data destruction in Canada.

When a lost or stolen device must be reported under PHIPA

A stolen device holding health information must be reported to the IPC unless the information was encrypted or de-identified. The IPC’s breach reporting guidelines for the health sector list theft as one of the situations that require reporting, and state that no report is needed when the stolen information was encrypted or de-identified.

A lost device isn’t automatically reportable to the IPC, but it can be in other situations the guidelines list, such as a significant breach or a pattern of similar breaches. Separately, custodians have a duty to notify the individuals whose privacy was breached. Custodians must also submit statistics on privacy breaches to the IPC every year, including ones that weren’t reported, so log every lost or stolen device.

PHIPA penalties and enforcement

PHIPA penalties include administrative monetary penalties and offence fines. Since January 1, 2024, the IPC can issue administrative monetary penalties of up to $50,000 for individuals and $500,000 for organizations. Offences under PHIPA can bring fines of up to $200,000 for individuals and $1,000,000 for organizations.

The IPC says penalties are issued for the purposes of encouraging compliance with PHIPA. For device programs, the practical point is that unencrypted devices and missing records are now more expensive to defend.

Preparing mobile devices for an IPC review

Preparing mobile devices for an IPC review means being able to show, not just say, that your safeguards work. If a breach or complaint leads to questions about your device program, you’ll want the evidence in the checklist above ready to share.

Start with five records. The current mobile device policy, an MDM report showing encryption and passcode compliance across the fleet, the asset register with every device’s status, repair and disposal records with certificates, and the breach log. Gaps in any of these are worth fixing before anyone asks.

Questions to ask a mobile device provider under PHIPA

Questions to ask a mobile device provider under PHIPA should confirm how they protect health information at every step they touch.

  1. Will you act as our agent or electronic service provider, and is that written into the agreement?
  2. How do you confirm devices are encrypted before they reach clinical staff?
  3. Where are devices staged, repaired and stored, and who handles them?
  4. How do you wipe and restage spare and repaired devices?
  5. What sanitization standard do you use, and do we get a certificate for every serial number?
  6. How quickly do you lock or wipe a lost device, and how do you tell us?
  7. What reports can you give us for an IPC review?

Where PiiComm fits in PHIPA-ready mobile device management

PiiComm supports Ontario health organizations across the device lifecycle. Our MDM as a Service team configures and enforces encryption, passcode and shared-device policies, and our Canadian team stages devices before they reach clinical units.

Repairs and spare pool management are tracked by serial number, and Secure Decommissioning ends each device’s life with NIST 800-88 sanitization or destruction and a certificate. See how MDM as a Service works.

For a major Canadian research hospital, PiiComm sourced clinical-grade mobile devices compatible with the hospital’s current and future electronic health record system. Read the healthcare case study.

It doesn’t fit everyone, though. If you’re a small clinic looking for PHIPA-compliant software rather than device management, a software vendor is the better place to start.

Questions Ontario health teams ask about PHIPA and mobile devices

Does PHIPA require mobile devices to be encrypted?

PHIPA requires custodians to take reasonable steps to protect health information, and the IPC has said since 2010 that health information on mobile devices must be strongly encrypted or de-identified. In Order HO-008, the Commissioner said identifiable, unencrypted health information on mobile devices shouldn’t happen under any circumstances.

Does PHIPA apply to shared hospital phones and tablets?

Yes, PHIPA applies to shared hospital phones and tablets whenever they hold or access personal health information. The custodian is accountable for that information, so shared devices need individual sign-in, encryption and sessions that clear between users.

Is a factory reset enough before disposing of a device?

A factory reset on its own isn’t strong evidence that health information can’t be recovered. Use a recognized sanitization standard such as NIST SP 800-88, or physical destruction, and keep a certificate of destruction for every serial number.

Do we have to report a lost hospital phone to the IPC?

A stolen hospital phone holding health information must be reported to the IPC unless the information was encrypted or de-identified. A lost phone is reportable in some situations, such as a significant breach. Either way, log it for your annual breach statistics and notify affected individuals as required.

What are the penalties for a PHIPA breach?

The IPC can issue administrative monetary penalties of up to $50,000 for individuals and $500,000 for organizations, and has been able to since January 1, 2024. Offences under PHIPA can bring fines of up to $200,000 for individuals and $1,000,000 for organizations.

Is a device repair provider our agent under PHIPA?

Whether a device repair provider is your agent or an electronic service provider under PHIPA depends on what it does and what your agreement says. In either case, you remain accountable, so put the provider’s role and safeguards in writing and confirm it with your privacy officer.

Does PHIPA require health information to stay in Canada?

PHIPA doesn’t simply require health information to stay in Canada, but custodians remain accountable wherever it’s handled. Ask providers where devices are staged, repaired and wiped, and where any device data is stored, and have your privacy officer confirm the arrangement meets PHIPA.

Where to start with PHIPA mobile device compliance

Run the checklist against your fleet, starting with an encryption report from your MDM platform and your lost-device procedure. Then check repair, spare and disposal records, and confirm your providers’ roles in writing. To see how we support Ontario hospitals and health teams, visit our healthcare industry page.

References