Canada just funded 10,000 AI scribes. The scribe is the wedge. The workflow layer is the business.

Canada Health Infoway announced a publicly-funded program in June 2025 to deploy AI-scribe technology to roughly 10,000 Canadian physicians, with the deployment running through 2025-2026. The program is operationally significant on its own terms (the scribe technology genuinely saves physician time, reduces documentation burden, and improves workflow capacity in a healthcare system that has documented capacity shortages elsewhere). The program is also strategically interesting because it is one of the largest publicly-funded AI-in-healthcare deployments to date and signals a regulatory-and-funding posture that supports continued AI deployment at the workflow layer.

The strategic misread on the program is to treat the AI scribe as the solution rather than the wedge. The scribe is the wedge into the clinical workflow. The workflow layer that sits on top of the scribe is the actual business. The operator-class building in this category has a window, probably 24 months, before the scribe vendors themselves move up the stack and capture the workflow layer. This essay walks the wedge framing, the workflow layer that becomes accessible, the 24-month window, and what to build inside it.

What the scribe deployment actually does

The AI-scribe technology, in its 2024-2025 generation, listens to the clinical encounter (with patient consent), produces a draft clinical note that captures the substance of the encounter, and presents the note to the physician for review and finalization. The deployment runs in the physician's existing EHR-and-clinical-workflow environment, with the integration handled through partnerships between the scribe vendor and the major EHR providers.

The operational impact is real. Physicians using deployed AI scribes report time savings on documentation work, with the savings ranging from 30 minutes to 2 hours per clinical day depending on the practice mix and the physician's pre-deployment documentation pattern. The savings translate to additional patient-facing capacity, reduced after-hours documentation time, or some combination. The Canada Health Infoway program is funding this deployment at scale because the operational benefit has been substantiated through the early-deployment cohorts.

Why it is a wedge, not a solution

The scribe deployment addresses one specific friction in the clinical workflow: the time the physician spends on documentation. The deployment does not address the broader workflow inefficiencies that the documentation-burden was symptomatic of. The clinical referral process, the prior-authorization workflow, the patient-communication-and-follow-up cycle, the prescription-and-medication-management workflow, the care-coordination across the multi-disciplinary team, the longitudinal-care-management for chronic conditions: all of these are workflow surfaces that the AI scribe leaves substantially untouched.

The wedge framing is that the scribe gets AI deployed into the clinical-workflow context, with the patient-consent-and-data-handling infrastructure cleared, the EHR-integration-and-deployment plumbing built, and the physician adoption-and-training pathway established. Once the wedge is in place, the addressable workflow surface for additional AI tooling expands substantially. The scribe deployment is a foothold, not the destination.

The workflow layer that becomes accessible

With the scribe wedge deployed, several workflow-layer opportunities become accessible to operators building products that integrate with the scribe-and-EHR infrastructure.

The encounter-data-and-context layer becomes accessible. The scribe captures the clinical encounter in structured form. Products that operate on the captured-encounter data (clinical-quality monitoring, billing-code suggestion, care-gap identification, follow-up-task generation, longitudinal-pattern-recognition for chronic-condition management) can integrate with the scribe-output stream and produce operational value the scribe alone does not produce.

The communication-layer becomes accessible. Products that automate the post-encounter communication (patient-follow-up messaging, referral-letter generation, prior-authorization-request drafting, prescription-routing) can integrate with the scribe-output and the EHR-integration to produce operational efficiency the scribe alone does not produce.

The coordination-layer becomes accessible. Products that route the encounter into broader care-team workflows (specialist referrals with structured context, social-work-referral when SDOH issues surface, care-management-team escalation for high-risk patterns, longitudinal-program-enrollment) can integrate with the scribe-deployment infrastructure and produce coordination-class value the scribe alone does not produce.

Each of these workflow-layer products requires the scribe-and-EHR infrastructure to be in place. The Canada Health Infoway program puts the infrastructure in place at scale. The workflow-layer products become deployable to a population of 10,000 Canadian physicians who already have the scribe-and-EHR integration running.

The 24-month operator-class window

The window for operators to build the workflow-layer products before the scribe vendors themselves move up the stack is roughly 24 months. The pattern from adjacent enterprise-AI categories is that the wedge-vendor (in this case the AI-scribe vendor) eventually expands its product to capture the workflow-layer value, particularly when the wedge-vendor has the customer-relationship and the data-pipeline that the workflow-layer products would otherwise need to build separately.

The scribe vendors (Abridge, Heidi, Suki, DeepScribe, the various other vendors competing in this space) are building the platform-tier capability that will, over the next 24 months, expand from the scribe-only product into the broader workflow surface. Operators with workflow-layer products that are deployed in the wedge-window (mid-2025 through mid-2027) will be either acquired by the scribe vendors as they expand, or will have established sufficient customer-relationships to defend their position against the scribe-vendor expansion. Operators that wait beyond the window will face scribe-vendor competition that has the wedge-customer relationship and the data-pipeline already in place.

What to build inside the window

For Canadian healthcare-AI operators with the right capability set, the practical advice is to build for one of the workflow-layer surfaces above and to integrate cleanly with the major scribe-vendor APIs. The integration work is meaningful but not capability-prohibitive, and the customer-acquisition work runs through the existing scribe-deployment relationships rather than through the harder cold-start customer-acquisition that pre-wedge healthcare-AI products faced.

For investors evaluating Canadian healthcare-AI through 2025-2026, the structural read is to weight the workflow-layer opportunities heavily. The wedge-vendor space is largely captured by the existing scribe vendors. The workflow-layer space is open and has a 24-month window before the wedge vendors expand into it.

For Canadian health systems and provincial agencies, the part that holds is to support workflow-layer integration with the deployed AI-scribe infrastructure rather than treating the scribe as the endpoint of the AI-deployment conversation. The scribe is the wedge. The workflow layer that the wedge enables is where the operational impact actually lives, and the 24-month window for capturing it is open now.

The Canada Health Infoway program is significant because it deploys the wedge at scale. The strategic question is what gets built on top of the wedge during the 24-month window the deployment opens. Operators who recognize the wedge framing and build accordingly will produce the durable products. Operators who treat the scribe as the solution will be either captured by the scribe vendors or displaced by the workflow-layer products other operators build during the window.

—TJ