On May 29, 2026, Canada shut down a national digital prescription program that had been running for nine years and had received $298 million in federal funding. The platform worked. The technology was functional. Fewer than 5 percent of Canadian prescriptions had ever flowed through it.

That ratio is not a performance metric. It is a diagnostic.

What the program was actually asking

PrescribeIT was framed from inception as a technology delivery initiative — an "axe the fax" modernization project replacing paper-based prescription transmission with digital alternatives. Canada Health Infoway, the federally funded not-for-profit overseeing the program, structured its mandates, its vendor relationships, and its consulting engagements accordingly.

The framing was wrong from the beginning.

Achieving national e-prescribing adoption does not require building pipes. Pipes are the straightforward part. Achieving national e-prescribing adoption requires changing the daily workflows of thousands of fiercely independent physicians who operate under no centralized authority, integrating seamlessly with dozens of fragmented and proprietary electronic medical record systems, aligning the financial incentives of community pharmacies, and building sufficient trust across a system whose participants had no shared governance structure and no shared timeline.

Applying the Cynefin Framework's diagnostic logic: the technical build — designing a secure, interoperable transmission architecture — was a Complicated challenge. Expensive, technically demanding, but knowable. Expert-driven delivery was the right tool for it. The adoption challenge was categorically different. It was a Complex problem: multiple autonomous actors with divergent incentives, no established best practice, and a solution that could only emerge through direct stakeholder engagement and iterative co-creation. No consulting mandate was ever structured to address it.

What the money actually bought

Infoway contracted Telus Health as the primary technology vendor, ultimately directing approximately $98 million toward the technical build.

Telus Health received approximately $98 million toward the technical build — while retaining 85 percent of the underlying intellectual property from a platform constructed entirely with public funds.House of Commons Health Committee testimony, 2026

For the broader program, Infoway assembled an extensive consulting roster: $2.7 million to Accenture, $1.27 million to Deloitte, $2 million to INQ Consulting, $1.5 million to Sussex Strategy Group, and over $1 million to Crestview Strategy, among others. In under three years, Infoway issued more than 100 contracts totalling over $23 million.

Telus Health executives testified before Parliament with precision about their mandate: they built the pipes. Adoption and policy integration were Infoway's responsibility. That testimony is accurate — and it precisely describes the structural gap that produced the failure. The technical delivery was contracted. The behavioral coordination challenge was not.

Infoway's own clinical advisory board identified this gap. The board recommended embedding PrescribeIT directly into existing physician EMR workflows — reducing friction to near-zero at the point of prescribing — and providing direct financial incentives for physician onboarding. Neither recommendation was fully implemented.

The 20-cent charge that tells the whole story

In 2025, Infoway introduced a 20-cent per-prescription fee charged to pharmacies for transactions processed through PrescribeIT.

In a system already characterized by thin pharmacy margins and low adoption inertia, a 20-cent per-prescription fee introduced a direct financial disincentive for the very end-users the platform depended on. Adoption stalled further.Canada Health Infoway, 2025

The decision to introduce that fee reflects the core misclassification precisely. In a Complex system — one involving thousands of independent actors making daily workflow decisions under their own economic constraints — incentive structures are the terrain. They cannot be identified through desktop analysis after the platform is built. They can only be understood by convening the actors who face them, surfacing the real barriers before commitments are made, and designing the system around the actual behavioral reality rather than the assumed one.

No external consulting mandate operating on a fixed deliverable framework can perform that function. The stakeholders who hold the adoption constraints were not in the room when the critical architectural decisions were made.

The question the investigations are not asking

The fallout from PrescribeIT's failure has been extensive. CEO Michael Green was dismissed on May 6, 2026, having earned nearly $900,000 annually — including $215,845 in performance bonuses — for a program that never achieved meaningful scale. Over $418,000 in executive travel was documented across a 33-month period. The House of Commons health committee has launched a probe. Conservative MPs have called for an Auditor General investigation.

These investigations are asking the right operational questions. Were expenses justified? Was procurement conducted appropriately? Was executive compensation proportionate to outcomes?

The prior question is more important and is not being asked: was the problem correctly classified before the first dollar was spent?

PrescribeIT did not fail because the consultants were incompetent or the technology vendor underperformed. It failed because a multi-stakeholder behavioral coordination challenge — the kind that can only be resolved by convening the actors who hold the constraints and co-creating the conditions for adoption — was treated as a technology delivery project. The strategic architecture of the intervention was wrong before the RFP was issued.

The $298 million does not represent waste through mismanagement. It represents waste through misclassification. The distinction matters because mismanagement is corrected by better oversight. Misclassification is corrected by asking a different question before the contract is signed.

Frequently Asked Questions

Why did PrescribeIT fail if the technology actually worked?

Because the binding constraint was never technological. Achieving national e-prescribing adoption required changing the daily workflows of thousands of independent physicians, aligning fragmented EMR systems, and resolving financial disincentives for pharmacies — a multi-stakeholder behavioral coordination challenge with no centralized authority to mandate compliance. The Cynefin Framework classifies this as a Complex problem: one whose solution can only emerge through stakeholder convening and iterative co-creation. No consulting mandate structured around fixed technical deliverables can address it.

What did Infoway's clinical advisory board recommend, and why wasn't it implemented?

The advisory board recommended two interventions with direct bearing on the adoption failure: embedding PrescribeIT directly into existing physician EMR workflows to reduce friction at the point of prescribing, and providing direct financial incentives for physician onboarding. Neither was fully implemented. The 2025 introduction of a 20-cent per-prescription fee charged to pharmacies moved in the opposite direction — introducing a financial disincentive for the end-users the platform depended on.

What should have been done differently at the outset?

Before structuring PrescribeIT as a technology delivery mandate, the program required a rigorous diagnosis of the adoption challenge as a stakeholder coordination problem. That diagnosis would have involved convening physicians, pharmacists, EMR vendors, and provincial health authorities around the actual behavioral barriers to adoption — not after the pipes were built, but before the architecture was specified. The technical build and the adoption strategy are not sequential. In a Complex system, they are interdependent, and the stakeholder reality must shape the technical design, not follow it.