PHIPA-compliant software: a checklist for Ontario clinics
What Ontario's PHIPA expects of the software and vendors a clinic uses, and the questions to ask before any patient information moves.
Mahmoud ElHewaheyFounder, PulseAI Solutions28 October 2026 · 3 min read
The short version
Under PHIPA, the clinic is the health information custodian and stays accountable for what its vendors do.
A vendor handling patient information is usually the clinic's agent, or a provider of electronic services, and needs a written agreement.
Ask for the data flow, the safeguards, the audit trail and the breach process before you sign.
Ontario's commissioner can impose administrative penalties under PHIPA.
No product is PHIPA compliant on its own; compliance is how the clinic and vendor operate together.
Who is responsible under PHIPA
PHIPA governs personal health information in Ontario. Physicians, clinics and other
health care practitioners are health information custodians: they are accountable for the
information in their custody, including what their vendors do with it. A vendor shares the work
under the custodian's direction, and the responsibility stays with the custodian.
What your vendor is, in PHIPA terms
Three roles a software vendor can play
Role
What it means
What you need
Agent
Acts on the clinic's behalf with patient information, for the clinic's purposes
A written agreement setting out what the agent may do, and the clinic's policies applied to it
Electronic service provider
Supplies services that let the clinic collect, use or store information electronically
Assurance that it will not use or disclose the information except to provide the service
Health information network provider
Enables two or more custodians to share information electronically
A written agreement and the additional duties in PHIPA's regulation, including audit records on request
The roles are defined in PHIPA and its general regulation. Your privacy officer decides which applies.
The checklist
Before you sign
Purpose. The vendor uses patient information only to provide the service
the clinic asked for.
Agreement. A written agreement covering permitted uses, safeguards,
subcontractors, breach notice, return and destruction.
Data flow. A diagram of where information is collected, stored and
processed, and by whom.
Location. Where information is stored and processed. Many Ontario clinics
require Canada by policy.
Training. A written commitment that patient information is never used to
train AI.
Privacy impact assessment. Completed for any new technology, and updated
when it changes.
Safeguards
Encryption in transit and at rest.
Two-step verification for everyone who signs in.
Access limited to the people and processes that need it.
An audit trail of who accessed what, kept for a defined period and available to the clinic.
Infrastructure independently audited, such as ISO/IEC 27001 or SOC 2 Type II.
When something goes wrong
The vendor notifies the clinic at the first reasonable opportunity.
The clinic notifies affected patients, and the commissioner where the regulation requires it.
The clinic records the incident for its annual statistical report to the commissioner.
Penalties
PHIPA was strengthened in recent years. The Information and Privacy Commissioner of Ontario can
now issue administrative monetary penalties, in addition to the fines a court can impose on
conviction. The amounts make vendor choice a governance decision for the clinic.
Patients' rights
Patients can ask to see and correct their information. Every system that holds part of the
record, including vendors' systems, has to support the clinic in answering those requests.
Plain language for patients
PHIPA requires custodians to make a written public statement about their information
practices available. Choose vendors whose practices can be explained simply, and share that
explanation with patients. Our Trust Center is written so a clinic can do
exactly that.
Questions, answered
What makes software PHIPA compliant?
No product is compliant on its own. PHIPA compliance comes from how the clinic, as custodian, and the vendor operate together: a written agreement, use limited to the clinic's purposes, strong safeguards, an audit trail, breach procedures, and support for patients' access and correction rights.
Is a software vendor a PHIPA agent?
Often. A vendor acting on the clinic's behalf with personal health information is generally an agent; one that only supplies electronic services is an electronic service provider. Your privacy officer decides which role applies.
Does PHIPA require patient data to stay in Canada?
PHIPA does not contain a general data residency requirement. Many Ontario clinics require Canadian storage by policy, and should ask every vendor where information is stored and processed.
Is Clinic Conductor PHIPA compliant?
Clinic Conductor is compliant with PHIPA, Québec's Law 25, PIPEDA and HIPAA. Canadian clinics are stored and processed in Canada, every clinic signs a privacy agreement before any data is shared, and patient data is never used to train AI.
This guide is general information about the law as published, written for clinic owners and their teams. It is not legal advice. Your privacy officer or counsel should confirm how it applies to your clinic.
What Canadian privacy law and the 2026 regulator guidance require of a clinic using an AI scribe: consent, assessments, vendor terms, recordings and training.
How a clinic connects its EMR to intake, forms, phones, faxes, labs and a CRM: the five ways to integrate, what each EMR exposes, and what to ask a vendor.