What Can a Clinic Contact Form Collect Under PHIPA?
What Ontario clinics can and cannot collect through a website contact form under PHIPA, where the data actually goes, and the checks worth running on your own site.
If you run a clinic in London, Ontario (a dental practice, an optometry office, a physiotherapy or massage therapy clinic), your website almost certainly has a contact form. And that form is probably collecting more than it should.
This is the question we get asked most often by practice owners, usually once the site is already built: what are we actually allowed to ask for?
The short answer
A clinic contact form should collect the least it can get away with: a name, a way to reply, and a general reason for getting in touch. The moment it invites a patient to describe a symptom, a diagnosis or a medication, the form is collecting personal health information, and everything downstream of it is now holding health information too.
That includes the notification email, the inbox it lands in, the form provider's logs, and any automation you have wired into it. Most clinics have never looked at that chain.
Does PHIPA apply to a website at all?
Ontario's Personal Health Information Protection Act applies to health information custodians, which covers most regulated practitioners running a practice, along with hospitals, pharmacies and labs. The obligations follow the information, not the medium. There is no separate, gentler rule for websites.
Two consequences matter for a practice owner:
Your web developer is usually your agent. So is your hosting provider, your form service and your booking vendor. Work done on your behalf does not transfer the responsibility: it stays with the practice. That is an argument for knowing exactly what each of those services stores, and for having it written down.
Safeguards are an ongoing obligation, not a launch task. The Information and Privacy Commissioner of Ontario has been explicit that custodians are expected to review their safeguards periodically to confirm they are still reasonable. A decision that was defensible when the site launched in 2021 is not automatically defensible now.
What counts as personal health information on a website?
The line is less obvious than people expect, because context does a lot of the work.
A name and an email address on their own are ordinary personal information. The same name and email attached to "I'd like to discuss treatment for my TMJ pain" is personal health information: identifying information about an individual that relates to their health or to health care provided to them.
Which means the field that creates the exposure is almost always the same one: the free-text box labelled "How can we help?" Patients use it honestly. They describe the problem. That is what a message box is for.
What a clinic contact form should ask
A form that does its job without collecting health information looks like this:
Name. First name is enough for a callback.
One contact method, chosen by the patient: phone or email, not both by default.
Reason, as a category rather than a description: new patient enquiry, existing patient, billing question, something else. A dropdown routes the enquiry without inviting a symptom.
Preferred time to be reached, if your front desk will use it.
And what to leave off:
Health card numbers. There is no reason a website form needs one, and health numbers carry restrictions of their own on top of the general rules. Collect it at the point of care.
Date of birth. Rarely needed before the first conversation, and it materially raises the value of the record if the inbox is compromised.
An open "describe your symptoms" field. If you genuinely need clinical detail before an appointment, that belongs in your practice management system behind a login, not in a form that emails a general inbox.
If you do keep a free-text box, and plenty of clinics reasonably decide to, put a short line under it: "Please don't include medical details here. We'll take those securely when we speak." It will not stop everyone, but it changes what most people type.
The part most clinic sites get wrong: where the data goes
The form is the visible half. The invisible half is the chain behind it, and that is where the real exposure sits.
Where does the submission land? A shared inbox that four people access from personal phones is a different risk from a monitored account with two-factor authentication and a retention rule. The IPC has published specific guidance on communicating personal health information by email, and it is worth reading before deciding your front desk is fine as it is.
Who else sees it in transit? Many clinic sites use a third-party form service that stores every submission on its own servers, often indefinitely, often outside Canada. If you cannot say where your submissions are stored and for how long, that is the first thing to find out.
How long do you keep it? Most practices have a retention policy for clinical records and nothing at all for the website inbox. Enquiries from 2019 are frequently still sitting there.
What else is on the page? This is the one that surprises people. Advertising and analytics scripts fire on the pages they are installed on, including a booking confirmation page. A tracking pixel on a page whose URL or title names a service can transmit more than the practice intended. If you run ad pixels, keep them off confirmation and patient-facing form pages.
Booking widgets and embedded scheduling
If you embed Jane, Cliniko, Acuity or similar, the patient is usually entering their information into the vendor's system rather than yours, which is generally the safer arrangement: that software is built for it and your site never touches the data.
Two things still need checking. First, that you have a written agreement with the vendor covering their handling of the information. Second, that your own site is not quietly capturing the same data alongside the embed, which happens more often than you would think when a form was added first and the booking system second.
If something does go wrong
Worth knowing before you need it: under PHIPA, a custodian must notify the affected individual at the first reasonable opportunity, and must report certain breaches to the Information and Privacy Commissioner of Ontario in prescribed circumstances. Custodians are also required to keep annual statistics on breaches for the IPC.
The IPC publishes guidance on both responding to and reporting a health privacy breach. If your website collects anything at all from patients, somebody at the practice should have read it before an incident rather than during one.
A checklist for your own site
You can run most of this yourself in twenty minutes:
Open your contact form and list every field. Ask of each one: do we act on this before the first phone call? If not, remove it.
Submit a test enquiry. Follow where it lands, who can open that inbox, and from what devices.
Find out whether your form provider also stores submissions, where, and for how long.
Check which scripts load on your booking and confirmation pages.
Search the inbox for the oldest enquiry still in it. If you are surprised by the date, you need a retention rule.
Write down which vendors touch patient information, and confirm you have an agreement with each.
One honest caveat
We build websites; we are not lawyers, and this is not legal advice. What is written here reflects published IPC guidance and how it applies to the parts of a clinic's web presence we work on every week. For anything specific to your practice, particularly a live incident or an unusual data flow, your professional college and legal counsel are the right call, and the IPC's own guidance is the authoritative source.
What we can tell you with confidence is this: almost every clinic site we audit collects more than the practice needs, keeps it longer than anyone intended, and sends it somewhere nobody has checked. Fixing that is usually an afternoon's work, and it is much cheaper done before an incident than after one.
Frequently asked questions
- Does PHIPA apply to my clinic's website?
- PHIPA applies to you as a health information custodian, and that follows the information rather than the medium. If your website collects, stores or transmits personal health information (through a contact form, a booking embed, or an email address that patients reply to with symptoms), those obligations apply to it in the same way they apply to your paper files. Your web developer and your hosting provider generally act as your agents, which means responsibility stays with the practice.
- Can a clinic contact form ask what the appointment is about?
- It can, but it is rarely worth it. The moment a form field invites a patient to describe a symptom, a diagnosis or a medication, the submission becomes personal health information and everything downstream of that form (the email it generates, the inbox it lands in, the form provider's logs) is holding health information. Most clinics get everything they need from a name, a preferred contact method and a general reason category such as 'new patient' or 'existing patient'.
- Should a clinic contact form ask for a health card number?
- No. There is no reason for a website form to collect a health number, and health numbers carry specific restrictions under PHIPA on top of the general rules for personal health information. Collect it at the point of care, in the system built to hold it, not through a web form that emails it to a general inbox.
- Is it a privacy breach if a patient emails symptoms to the clinic's general inbox?
- Not in itself. A patient can choose to send you whatever they like. The question is what happens next. Once that message is in your inbox it is personal health information you are holding, so it needs the same safeguards as any other record: controlled access, retention that matches your policy, and a plan for what happens if the account is compromised. The IPC has published specific guidance on communicating personal health information by email.
- Does PHIPA require my clinic website to be hosted in Canada?
- PHIPA does not impose a blanket rule that all data must be stored in Canada, which is a common misconception. It focuses instead on having reasonable safeguards and on your accountability for what your service providers do with the information. Canadian hosting can make that conversation simpler, but it is not a substitute for knowing what each vendor stores and for having that set out in a written agreement.