A blank privacy worksheet and closed laptop on a shaded bench with a coral shield card
OntarioPHIPAprivacytherapy softwarecompliance

PHIPA Compliance: A Vendor-Evidence Checklist for Ontario Therapists

Photo of Dr. Sofia Reyes
Dr. Sofia Reyes Clinical Documentation & Compliance Editor 9 min read
Outline

The printable pack adds a monthly cost model, PHIPA vendor question list, documentation and insurer-report fit test, and fictional-data trial checklist that you can reuse during a software review.

Document your software purchase decision

Use the cost, vendor-evidence, workflow-fit, and fictional-data sheets to compare one candidate this week.

  • Monthly Cost Model with separate plan, add-on, quote-only, promotion, tax, and payment rows
  • PHIPA Vendor Question List for data location, access logs, incident notice, retention, and contract evidence
  • Documentation and Insurer-Report Fit Test for notes, receipts, exports, permissions, and payer questions
  • Fictional-Data Trial Checklist and log for recording a pass, fail, evidence location, and hold decision

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

You are not buying a compliance badge. You are deciding whether a proposed information practice, contract, and workflow can support PHIPA compliance work for your Ontario practice.

The Information and Privacy Commissioner of Ontario describes health information custodians as accountable for protecting personal health information even when they use third-party services. The Personal Health Information Protection Act, 2004 (PHIPA) also gives individuals rights to access and request correction of their information. Start with the facts of your proposed workflow, not a vendor’s headline.

This guide is educational, not legal, tax, insurance, registration, or professional advice. Confirm your facts and contract with qualified Ontario privacy counsel and your regulator. The law, guidance, vendor terms, and security practices can change.

Identify the roles before you compare features

Write down who has custody or control of the personal health information, who acts for the practice, who operates the software, and who can access information for support. This role record is the first practical step in your PHIPA compliance review. Do not let a product label decide the legal relationship.

Your role may depend on the services you provide, your professional status, your practice structure, and the specific information activity. Review the current PHIPA text and the regulator guidance for the facts that apply to your practice. A software company may describe itself as a service provider, processor, platform, or vendor. Those words do not answer your Ontario legal analysis.

Use this short role record:

Role questionYour answerEvidence to keep
Who is the health information custodian?[practice or person]Registration, practice structure, service description
Who decides the purposes of collection, use, and disclosure?[role or entity]Privacy policy and internal responsibility record
Who acts for the custodian?[person or company, if applicable]Contract and data-flow description
Who can access the information?[clinicians, staff, support, subcontractors]Role matrix and vendor response

The role record is a working analysis, not a legal conclusion. If the answer changes by feature or workflow, split the record rather than forcing one label across the whole product. That discipline keeps a PHIPA compliance decision tied to the facts you can show.

Map the proposed data flow

Map the smallest complete workflow you expect to use. Include information entered before a session, during a session, after a session, and when someone asks for access, correction, export, or deletion.

Include the client-facing device, clinician device, practice account, vendor environment, support channel, subcontractors, backups, logs, exports, and any integration. If the vendor says it does not sell or use client information for advertising, record that answer and the contract language that supports it. Do not turn a marketing statement into a permission you have not verified.

For a proposed Jane workflow with French-speaking clients, use the Jane French client-surface and intake test to identify which text the platform supplies and which your practice must maintain.

For every step, record:

Data-flow stepWhat to askEvidence to request
CollectionWhat personal health information enters, from whom, and for what purpose?Field list, purpose statement, consent or notice materials
ProcessingIs information transcribed, drafted, scored, indexed, or reviewed by another service?Workflow description and processing terms
StorageWhere is the information stored, backed up, and logged?Storage description, retention terms, access controls
AccessWho can view, change, export, or support the information?Role matrix, authentication, support procedure
Disclosure or exportWhat leaves the service, and to whom?Export format, destination controls, disclosure workflow
DisposalHow are records, backups, and account copies deleted or returned?Deletion schedule, certificate or evidence process

The IPC’s April 2026 PHIPA workshop says custodians should carefully assess vendors and use written agreements that set expectations for privacy protection and compliance monitoring. Keep the vendor’s evidence with the decision record.

If the tool helps create or review a clinical record, Ontario RPs can use the CRPO workflow for disclosing AI’s role in the record to test what they would document before signing. Make the PHIPA decision separately.

Request written vendor evidence

Ask questions that produce evidence you can read, compare, and retain. A vendor that cannot answer a question is not automatically unsuitable, but the unanswered question belongs in your risk record.

Security and access

Request the safeguards that apply to the exact plan and service you would buy. Ask how accounts are protected, how access is limited, how support access is authorized and logged, and what happens when a staff member leaves. Ask whether encryption claims apply in transit, at rest, or both.

If an Ontario RP will share records for clinical supervision, complete the CRPO supervision qualification and confidentiality checks separately; a software permission is not supervisor approval.

Ask for the incident process in plain terms: who is notified, what information is provided, what cooperation is available, and what contractual clock applies. Do not substitute a generic security page for an incident clause that your practice can use.

Subcontractors and service locations

Request a current list or description of subcontractors that may handle the information, including support, hosting, transcription, analytics, backups, and security services. Ask how changes are communicated and what your practice can do if a new subcontractor changes the risk.

Do not treat the country where a server sits as the whole answer. Ask where information is accessed, supported, backed up, and transferred. Confirm the answer against the contract and the workflow you intend to use.

Access, correction, export, and retention

Individuals have rights related to their personal health information, subject to the Act’s exceptions. Your practice needs a practical way to find, review, correct, and provide records when appropriate. Confirm the scope and exceptions in the current PHIPA text, then ask the vendor:

  • Can you search for one client’s records without exporting every client?
  • Can you preserve an access or correction request while it is being handled?
  • What format can you export, and does the export preserve dates, authorship, and revisions?
  • What remains in backups, logs, or support systems after account deletion?
  • How do you document return or secure disposal?

Confirm the retention and disposal plan against the current PHIPA text, your profession’s requirements, and your actual service. Record which source supports each decision and keep the vendor’s answer with the review.

For the record-keeping questions that remain after this purchase decision, compare the Canadian psychotherapy record-keeping guide and the Ontario psychotherapy progress-notes guide. Those guides address record practices; this page focuses on vendor evidence before you buy.

Contract and responsibility

Ask the vendor to identify the contract terms that address confidentiality, permitted handling, access, incident cooperation, subcontractors, return or deletion, and end-of-service support. Save the version you reviewed and the date you reviewed it.

Do not assume a business associate agreement from another jurisdiction answers an Ontario question. Do not assume a vendor’s security certification, audit report, or privacy statement transfers responsibility for your practice’s decisions. If your proposed workflow includes generative software, ask what information is used, where it is processed, whether it is retained for model improvement, and what review the clinician must perform before using any draft.

Record the gaps before you sign

A purchase decision is easier to review when every unresolved answer has an owner and a stop rule. Use plain descriptions rather than a green badge.

GapWhy it mattersOwnerDecision rule
Subcontractor list is incompleteYou cannot finish the data-flow mapVendor and practice privacy leadDo not enter client information until the list is complete
Export omits revision historyAccess or continuity work may be incompleteVendorObtain a usable export or document an alternate process
Incident notice is not definedYou may not know when to actPractice counsel and vendorResolve the notice process in writing
Deletion does not address backupsEnd-of-service risk remains unclearVendorRecord the backup schedule and evidence available
Support can view content without a stated needAccess may exceed the workflowVendor and practiceRequire role limits, authorization, and logging

A gap can be accepted, mitigated, transferred, or rejected. Name the decision and the person who made it. Do not call an unresolved gap compliant because the product is popular.

Test the workflow with fictional material

Use a fictional name, fictional contact details, and fictional clinical details. Test the workflow that you would actually use, not a polished demonstration path.

Ask a second person to follow the record from entry to final review. Check whether the system exposes more information than intended, whether a draft is clearly a draft, whether the clinician can review and sign it, whether an export is readable, and whether access can be removed. Then test the support path without sending real client information.

For a session-documentation workflow, compare the general documentation process on the features page. Treat the clinician’s review and signature as a professional control, not as proof that a product meets PHIPA.

A fictional-data test can show that your proposed process works. It cannot certify a vendor, resolve an unresolved legal question, or make your practice compliant with PHIPA. Keep the test result with the vendor-evidence request.

After the vendor-evidence decision

If the evidence supports the purchase, record the exact plan, terms, workflow, safeguards, decision owner, and review date. If the evidence does not support it, record the stop decision and the missing evidence. Revisit the record when the vendor changes its contract, subprocessors, service, or your practice’s use.

If you evaluate a session-note workflow, start with fictional material and keep the clinician in charge of review and signature. A software product is not an EHR, practice-management system, or PHIPA certification. Your practice remains responsible for its privacy analysis and professional obligations.

Evaluate a session-note draft with fictional material first

Try a fictional session, review the AI-drafted note, and keep the final clinical decision with the clinician.

Try it safely
  • Free plan
  • No credit card
Fictional session
Fictional clinician · Maya R.

Test record

A fictional client describes a difficult week and asks for a coping plan.

Clinician review

Draft ready for review and signature.

Review the session note… →

References

Free PDF: Canadian Practice Software and PHIPA Vendor Checklist

A printable decision pack for Canadian private-practice clinicians budgeting practice software and documenting PHIPA vendor evidence before purchase.

  • Monthly Cost Model with separate plan, add-on, quote-only, promotion, tax, and payment rows
  • PHIPA Vendor Question List for data location, access logs, incident notice, retention, and contract evidence
  • Documentation and Insurer-Report Fit Test for notes, receipts, exports, permissions, and payer questions
  • Fictional-Data Trial Checklist and log for recording a pass, fail, evidence location, and hold decision

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

Ready to transform your practice?

Join 10,000+ therapists using Emosapien.