Mr. Chair and members of the committee, thank you for the invitation. I appreciate the opportunity to be here in person.
We provided a technical expert for the April 21 meeting, but given the tight timelines, I appreciate that several important questions remained. I am here today to provide the clear, factual account the committee requires, and I will try to keep my remarks brief to allow maximum time for your questions.
To understand our work, it is helpful to view PrescribeIT not just as a piece of software but as a managed digital highway.
Over the nine-year life of this program, Telus Health received an average of approximately $10.9 million per year to build, operate and maintain the national highway. This annual fee was not a one-time purchase; it was the cost of a managed service and ensured that the highway was open 24 hours a day, with continuous security patrolling, 24-7 technical monitoring and the rigorous auditing required for national health data.
Our work covered two areas.
First, we built and operated the highway itself, the core system that allows different health care providers to talk to one another. Second, a much smaller portion supported our role as one of the many users on that highway, where we adapted our own electronic medical record systems and pharmacy products to meet the precise specifications designed by Canada Health Infoway.
From a technical perspective, the highway was a success. We delivered a 99.9% uptime record. The road was always open, it was secure and it worked exactly as intended and designed by the program owner. Over the course of the program, more than 181 million prescriptions travelled along this highway safely and securely.
We were able to launch this system effectively because Telus Health brought significant pre-existing assets to the table. Roughly 85% of the underlying technology was already built. This saved the government the time and the expense of building a new road from scratch.
I should also note that the entire team managing this project has been based in Canada, and anyone accessing personal health information would have had protected B clearance.
Finally, I want to address the challenge of adoption, or the traffic on the highway.
Telus Health was contracted to build a high-performance, six-lane managed highway. We were asked to build this capacity to meet Infoway's aggressive forecasts of 300 million annual prescriptions and 50,000-plus prescribers. We delivered that six-lane capacity, and we maintained it with 99.9% reliability for nearly a decade. However, as the technology partner, we did not control the traffic. The traffic generators—the policy mandates, the clinical workflow rules and the clinician onboarding process—were the responsibility of the program owner—Infoway and the government.
We operated the service to the specifications we were given. However, when we saw that the lanes were sitting empty and the projected traffic was not materializing, we proactively raised our concerns. We shared our technical observations through a clinical advisory board and in discussions with our partners at Infoway and Health Canada. Our message was consistent: To get traffic moving on a national scale, you need to make things easier for prescribers and mandate integration and common national standards.
We are proud of the technical integrity of the managed service we provided. We built a world-class highway that proved that national e-prescribing is technically viable.
I look forward to your questions.
