OIATC Ontario Indigenous AI & Technology Council
Council position · PrescribeIT

When the system is chosen for you: the PrescribeIT lesson

An OIATC position. Russell Jones on behalf of OIATC, independent of the bodies named here. Corrections welcome. Last updated 2026-06-02.

00

The short version

Ottawa spent more than a quarter of a billion dollars on a national e-prescribing system, then shut it off after fewer than five in a hundred prescriptions ever ran through it. The technology was not the problem. The system was chosen at the top, built by a vendor that kept the rights to it, and pushed down toward the people who were supposed to use it, including First Nations communities, who had no hand in choosing it and no say in ending it. That is the failure OIATC exists to name, and the principle we hold against it: protocol before product, consent before architecture.

01

What happened

PrescribeIT was a federal "axe the fax" program meant to replace fax machines for sending prescriptions from doctors to pharmacies. Canada Health Infoway, a government-funded non-profit, launched it in 2017 and ran it until 2026. Telus Health won the build contract and supplied the underlying technology.

Canada Health Infoway announced the program would go offline on May 29, 2026. The reasons given were plain. Adoption never arrived: fewer than five per cent of prescriptions in Canada were sent through it. Starting in 2025, the government began charging pharmacies twenty cents per prescription to help fund the service, and some pharmacists abandoned it rather than pay.

The money grew as the story did. The early figure was about $250-million. At a House of Commons hearing, Health Canada officials put actual spending at more than $298-million, of which roughly $98-million went to Telus Health. A Telus executive said the company kept about 85 per cent of the intellectual property behind PrescribeIT and is considering relaunching it. Health Canada confirmed the government holds no intellectual property in the program it paid to build. The executive who led the agency was later removed from the role, and Conservative MPs have asked the Auditor General to investigate the spending.

The stated path forward is a "national e-prescribing standard" that Ottawa hopes private health-technology companies will adopt.

02

The First Nations layer

This is not a story that happened next to Indigenous communities. It happened to them.

Canada Health Infoway's own Indigenous health program lists First Nations-led deployment of PrescribeIT as one of its partnership lines, alongside Indigenous electronic medical record systems. Even where the local rollout was First Nations-led, the system itself was not. It was selected federally, built by a vendor that retained the rights, and switched off from the centre. A community can lead a deployment and still hold no authority over the architecture, the data, or the off-switch. The communities served by the system were never the communities governing it. When it was cancelled, that decision arrived the same way the system did: from above.

There is a well-established field that already names the underlying right here. Indigenous data sovereignty, the principle that Indigenous Peoples govern their own data, is treated in the medical and policy literature as essential to self-determination and to better health outcomes. The First Nations principles of Ownership, Control, Access, and Possession (OCAP®) are the recognized standard, and the First Nations Information Governance Centre maintains a national data governance strategy that Infoway itself has partnered on.

OIATC does not restate that work and does not speak for those bodies. We point to it because it shows the principle is mainstream, not fringe, and because it sets the line OIATC adds to: not only who owns the data, but who chooses, governs, and can end the systems that the data moves through.

03

Why this is an OIATC matter

The headline invites the wrong lesson. The wrong lesson is that fax machines won, or that digital health is too hard, or that one vendor charged too much. None of those is the real failure.

The failure is one of governance. Nearly $300-million bought a system that fewer than five per cent of prescriptions ever used, because adoption was assumed instead of earned, and mandated from outside instead of grown from the people who had to live with it. A pricing change made in Ottawa drove users away. The rights to the public investment ended up in private hands. And the communities the system was meant to serve were treated as recipients of a decision, not authors of one.

That is the same diagnosis behind OIATC's work at the community scale. The pattern that fails a single Nation's portal is the pattern that fails a national program. It just costs more at the top.

04

What OIATC takes from it

Three things, each a way of stating the same conviction.

01

A system imposed is a system unused.

Adoption is not a marketing problem to be solved after launch. It is a governance outcome that is decided before the first line of code, by whether the people who must use the system had real authority over choosing it.

02

Public money should buy public control.

When governments fund the build, the communities served should hold the rights, the data, and the off-switch. A program the public paid for should not leave the public holding none of the intellectual property.

03

A standard is not a substitute for consent.

Replacing a cancelled product with a national standard is reasonable, but a standard adopted by vendors is still a decision made above the communities it reaches. The question OIATC keeps asking does not change: who chose this, and who can change it.

05

The solution: the Nation holds the controls.

The fix for a system chosen from above is not a better system chosen from above. It is digital self-determination: a community chooses and governs its own systems, and holds the controls, the data, the rights, and the off-switch, instead of receiving them on someone else's terms.

Most of that is decided before anything is signed. Here is a checklist a Nation can run on any vendor or system before it commits. If the answers come back wrong, the time to learn that is now, not after the data is already inside.

  • Ownership Do we own our data, and where is it stored?
  • Exit Can we leave at any time with all of our data, and at what cost?
  • Kill switch Who can change, suspend, or switch it off, and can anyone outside the Nation?
  • Governance Does it meet OCAP, who decides how our data is used, and can it be used to train someone else's model?
  • Consent Whose consent is required to add or share member data?
  • Lock-in Are we stranded if the vendor vanishes or raises the price, and is it open or a single supplier?
  • Transparency Can we see what it does with our data, and is there an audit log we control?
  • True cost What is the real total cost, including the cost to leave?

Anokii is OIATC's reference answer to this checklist, built so a community can answer yes down the whole list. The checklist also stands on its own: a Nation can run it against any vendor, including ones OIATC has nothing to do with.

06

What we are not saying

We are not saying any individual acted in bad faith. This memo names a structure, not a person. We are not saying electronic prescribing is wrong; clinicians have real reasons to want off the fax. We are not speaking for the First Nations Information Governance Centre or for any community. We are saying that when systems are chosen for communities rather than by them, they fail, and that the cost of that failure is paid first by the communities with the least say.

07

Sources