Physician in a white coat over pajamas and bunny slippers, representing after-hours administrative work known as pajama time

Canadian clinical workflow automation & post-visit execution

You adopted an AI scribe. Why are you still doing pajama time?

Your scribe made documentation faster.
But documentation was never the whole workload.

There’s still the DTC form waiting until after the kids are asleep, the pharmacy callback between patients, the referral that bounced back, the renewal waiting for approval, and the billing that still has to get done.

Design commitments. Read the Trust Centre for scope and implementation status.

What is Align eCare?

Align eCare is a physician-controlled administrative execution and assurance layer being developed for Canadian healthcare. It is designed to prepare, check, route and track the work a visit creates, including forms, referrals, prescriptions, billing evidence and patient handoffs. Clinical decisions and authorization remain with licensed professionals.

  • Forms and authorizations
  • Billing and claims

Your scribe documents the visit.Align eCare completes the administrative work that follows.

Say goodbye to pajama time. Say hello to real clinical capacity.

Planned forms workflow · Synthetic demonstration · No CRA connection

MedAssist · Disability Tax Credit

The form the visit calls for, assembled from the chart.

The patient completes Part A in their own CRA account. MedAssist links its reference number, assembles Part B from the documented facts, shows the source of every entry, and presents the finished certificate for the physician to review and attest.

Sources in the chart CRA account · patient’s Part A Problem list Encounter note Physiotherapy assessment Encounter transcript Neurology consult letter
T2201 · Part BIllustrative example · synthetic patient
CRA reference number Linked from the patient’s Part ACRA account · patient’s Part A
Diagnosis Multiple sclerosis, relapsing-remittingProblem list + Neurology consult letter
Impairment category WalkingEncounter note
Marked restriction Inordinate time to walk 50 m, even with a canePhysiotherapy assessment
Frequency All or substantially all of the timeEncounter transcript
Duration Since 2019 · expected 12+ monthsProblem list + Neurology consult letter
Effects on daily living Cannot shop or commute unassistedEncounter transcript
Eligibility evidence
5/5
  • Impairment category
  • Markedly restricted
  • All or substantially all the time
  • Prolonged, 12+ months
  • Effects described
Ready for physician review and attestation

To truly offer a solution to a problem it needs to be understood completely

Documentation tools vary. A better note can still leave downstream administrative work for the physician. Then copy paste fatigue takes over: checking it, moving it, and pasting the same information into the chart, the form, the referral, and the billing, again and again. The time the tool saved is spent moving words from one place to another, and the physician is still the one carrying the work across every system.

How is Align eCare different from an AI medical scribe?

Align eCare is being built to prepare and track administrative work after the note: forms, referral packages, prescription review and billing evidence. Scribe capabilities vary by product. Align eCare’s focus is the connected sequence of evidence, professional approval, routing and returned-work handling, rather than documentation alone.

Does Align eCare replace our existing EMR or AI scribe?

No. Align eCare is designed to work alongside a clinic’s existing EMR and documentation tools. Planning considers Canadian environments such as Accuro, TELUS PS Suite, OSCAR Pro and Med Access. These are intended compatibility targets, not confirmed integrations; each connection needs vendor access, agreements, implementation and testing.

How does Align eCare organize multi-physician clinic workflows?

The proposed workflow groups prepared items by responsible physician, patient and clinic day. Missing evidence and discrepancies are brought into review before approval. The design keeps each clinician responsible for the items they authorize, with source information, artifact version, destination and next action available together. Role controls and biometric approval require validation.

How does Align eCare approach Canadian healthcare privacy?

Align eCare’s design is guided by PIPEDA and applicable provincial requirements, including PHIPAA in New Brunswick and PHIPA in Ontario. Patient and clinic information will never be used for AI model training under the founder’s policy commitment. The Trust Centre separates these commitments from controls and processing arrangements that still need deployment verification.

Choose Align eCare if

  • You run a Canadian primary care or multi-physician clinic
  • You already use an AI scribe but still complete forms and billing after hours
  • You need FHIR-grounded data and Canadian data residency
  • You need provincial billing review linked to documented services

Align eCare is not the right fit if

  • You practise outside Canada
  • You run a dental-only or veterinary practice
  • You only need visit transcription and nothing downstream of it

The administrative time tax

Behind the backlog is clinical time.

Independent reports describe the system burden. A clinic pilot must establish how much time Align eCare can actually return.

National figures: CFIB / CMA, 2025 survey, report published 2026. New Brunswick figures: NBMS extrapolations, 2025. These are industry estimates, not Align eCare outcomes.

Billing optimization · Planned workflow

Find the codes you earned. Defend every one. Reclaim the revenue.

Align eCare’s planned billing layer is designed to read the documented visit against the official provincial fee schedule, surface the add-on and premium codes that are easiest to miss, and link every suggested code to the evidence behind it, so each claim can be defended if it is ever audited. The physician reviews and approves every code.

01 · Optimize

Every code the visit supports

Suggested codes, including add-ons and premiums, are drawn from what was actually documented and checked against the provincial fee schedule, for the physician to accept, change or reject.

Fee-schedule rulesAdd-on and premium codes
02 · Defend

An auditable evidence line

Each code is designed to stay linked to its note, the fee-schedule rule it relies on, and the time or service that supports it, as a traceable record from the visit to the claim.

Visit → evidence → rule → claim
03 · Reclaim

Revenue that was already earned

$22,500 /yr

Up to an estimated $22,500 per physician per year, in billings for care that was delivered but never claimed.

Modelled estimate

About this estimate: a modelled, pre-validation estimate, not a measured Align eCare result. It applies the missed-code rate reported for experienced staff physicians in a 2019 Ontario billing study (38.5% of billable codes missed; 64.8% of the misses were add-on and premium codes; Canadian Journal of Surgery, 2019) to average Canadian family-physician billings. That study examined surgeons, so results for other specialties, provinces and practices will differ and must be measured in a pilot. Align eCare does not guarantee payment or eliminate audit risk.

Illustrative task-time ranges · Not measured Align eCare results

Where the time goes

The system drains physicians infragments.

No single task is the problem. Six recurring loops, repeated every clinic day, are what consume the week.

  1. Fax Sorting & Routing

    15-30min/day
    Manual sorting, routing delays, lost documents. Automated classification, chart matching, and encrypted routing.
  2. Pharmacy Callbacks

    20-40min/day
    Clarification requests arriving with missing information. Pre-validated prescriptions with complete clinical context.
  3. Referral Rework

    25-45min/day
    Incomplete forms, missing fields, specialist rejection. Auto-completed referrals with chart context, validated before sending.
  4. Forms & Disability

    30-60min/day
    DTC, EI, CPP and insurance forms completed manually. Intent detection and auto-population from structured chart data.
  5. Billing Review

    15-30min/day
    Audit anxiety, missed billing, lost revenue. Evidence-linked billing with audit-ready provenance.
  6. Pajama Time

    30-90min/night
    After-hours administrative catch-up. Workflows completed during the shift, not after the kids fall asleep.

Privacy and governance design requirements · See the trust centre for implementation status

Privacy, liability, and consent: what physicians search first

Before a physician asks what a tool can do, they ask what it will cost them if it gets it wrong.

When physicians research AI scribes, the first questions are not about features. Does it use patient audio to train AI models? Is there a zero data retention policy, and does the data stay in Canada, under PIPEDA, PHIPAA in New Brunswick, PHIPA in Ontario, and the provincial law that applies to their practice? What do the CMPA guidelines on AI scribes say, and who is responsible for documentation errors, the physician or the vendor? Do patients have to sign consent, what happens if a patient refuses, and what does a listening tool do to patient trust?

Align eCare was built to answer those questions before it asks for anything. Our policy commitment: patient and clinic information will never be used to train AI models. The platform is designed for Canadian data residency. Nothing the platform prepares is final until the physician reviews and attests to the exact artifact, with the evidence it rests on shown beside it, so responsibility is never a guessing game. And consent is handled in the open, in the product, not in fine print a patient never sees.

  • Does it use patient audio to train AI models?
  • What do the CMPA guidelines on AI scribes say, and who is responsible for documentation errors, the physician or the vendor?
  • Do patients have to sign consent, and what happens if a patient refuses?
Paused
Privacy

Does it use patient audio to train AI models?

Patient information does not train AI models, and the platform is designed for Canadian data residency.

Our policy commitment: patient and clinic information will never be used to train AI models. The platform is designed for Canadian data residency, under PIPEDA, PHIPAA in New Brunswick, PHIPA in Ontario, and the provincial law that applies to the practice.

Liability

What do the CMPA guidelines on AI scribes say, and who is responsible for documentation errors, the physician or the vendor?

The physician reviews and attests to the exact finished artifact. What was approved can be proven later, exactly as approved.

Nothing the platform prepares is final until the physician reviews and attests to the exact artifact, with the evidence it rests on shown beside it, so responsibility is never a guessing game.

Consent

Do patients have to sign consent, and what happens if a patient refuses?

Consent is handled in the open, in the product. A patient can refuse, and the visit carries on without the tool.

Consent is handled in the open, in the product, not in fine print a patient never sees.

Illustrative review behavior · Clinical accuracy requires validation

AI scribe hallucinations, accents, and dropped recordings

A note that sounds right is not the same as a note that is right.

Physicians search for the failure points, because they have lived them. AI scribe hallucinations in complex patient visits. Accuracy dropping off with foreign accents and dialects. Performance falling apart in multi-speaker family practice and pediatrics, where a parent, a child, and a physician are all talking. Tools documenting negative symptoms that were never mentioned. And the quiet worst of it, a dropped recording and lost audio, discovered at the end of the day.

That is why Align eCare does not ask a physician to trust a fluent paragraph. Outputs are constrained to source-cited material: no citation, no assertion. Deterministic rules sit between the AI and anything final. Contradictions and unclear input are flagged and shown to the physician, who resolves them. Nothing is silently filled in, and the evidence behind every output is assembled where the physician can see it. The check is structural, not a promise.

Pediatric visit · draft noteIllustrative example
Visit statement · parent“She’s had the cough about three days. No fever, she’s eating fine.”
Draft note · history Cough for 3 days. Eating well. Fever for 3 days.
Evidence · transcript 00:04:12, parent“…No fever, she’s eating fine.” The source contradicts the draft line.
Physician resolved: “Afebrile per parent.” Draft line replaced.
  1. 1Flagged, not hidden: A statement that does not match the source is flagged in place, where the physician can see it.
  2. 2Evidence beside it: The source the output rests on appears next to the output, not buried in a log.
  3. 3Physician resolves: The physician decides. The platform never quietly papers over a contradiction.

Proposed administrative execution sequence · Integration dependent

EMR form automation, referral routing, and the copy paste problem

Are there any Canadian clinical AI platforms that automate disability forms and referral routing, or do current tools only generate SOAP notes?

That question, typed into AI agents by physicians across Canada, is the whole problem in one sentence. Most tools generate a SOAP note and stop. The physician is left with direct integration versus copy paste as a daily reality: carrying the same information by hand into the disability form, the consultation letter, the requisition, and the referral, while EMR form automation, the thing that would actually help, stays missing.

Align eCare is being built for the work after the note. From one encounter, the form the visit calls for is assembled, the referral is prepared and routed as a tracked step, the billing is computed from the official provincial schedule, and the follow up is organized, then the finished set is presented to the physician to review and attest. The physician is not the clipboard. Information is captured once and carried by the platform, not copied from screen to screen by the person whose time the system is supposed to save.

Today, the same information in four places NoteFormLetterChart
Physician attests · on the finished set

FormAssembled from the encounter and presented for attestation.

Align eCare eAttest™ · Illustrative example of the planned interface

Verify first. Attest once. Transmit securely.

Incomplete or inconsistent prescription information can create clarification loops between pharmacy and clinic. eAttest is designed to bring those questions into the prescriber’s review before transmission. Step through the seven-stage protocol below. Every action is simulated with synthetic data.

Assemble

Everything the prescription depends on, in one place, before anyone signs anything.

  • Encounter note: plan to start amlodipine
  • Current medication list
  • Chart allergy list
  • Recent lab results
  • Patient’s chosen pharmacy
eRxDraft v2
  • Patient and encounterSample patient · today’s visit
  • Medication and doseAmlodipine 5 mg tablet
  • Directions1 tablet by mouth once daily
  • Duration and quantity90 days · Qty 30
  • AllergiesNone recorded
  • Destination pharmacyPatient’s chosen pharmacy

Patient execution engine · Planned workflow

The visit ends.
The patient’s next steps begin.

A plain-language after-care document is designed to turn the clinician’s approved plan into clear next steps: what changed, what happens next, who makes contact and when follow-up is needed.

YOUR VISIT. YOUR NEXT STEPS.Illustrative patient copy

A plan you can take home.

Prepared from the encounter. Reviewed by the clinician. Shared through an agreed delivery channel.

01
What happened today

The reason for the visit, the clinician’s assessment and the agreed plan, in plain language.

02
What changed

Separate lists for new, changed, continued and stopped medications, based on clinician-approved instructions.

03
What happens next

Tests, referrals, preparation instructions, contact responsibility and follow-up expectations.

Synthetic demonstration · No clinical advice or patient information
Medication changes, clearly separated

The proposed patient copy distinguishes new prescriptions, dose changes, ongoing medicines and medicines the clinician has stopped. Unclear or conflicting instructions return for professional review.

Referrals with a named next action

Show the destination and whether the patient or receiving service initiates booking. Use confirmed service information and available wait-time information only.

Tests with approved preparation

Include the instructions supplied or approved by the responsible service. Fasting, medication holds and escalation timelines must reflect the actual test and clinical plan.

Clear follow-up and escalation

Separate routine follow-up from urgent instructions that the clinician has reviewed. The platform does not independently determine emergency thresholds.

One approved copy, accessible delivery

Planned delivery options include a patient portal, an accessible printed copy and a secure link, subject to implementation, consent and the clinic’s policies.

PrepareCheck sourcesClinician reviewsPatient receivesFollow-up tracked

Proposed workflow. Delivery channels, medication checks, source mappings and portal connections require implementation and validation. No live integration is represented by this illustration.

Illustrated mother walking with a baby in a stroller
Clear next steps for the people heading home.
Meet the illustrated characters

Remote patient monitoring · Planned

Useful signals.
A defined response.

Align eCare’s proposed monitoring workflow starts with a clinician-selected purpose, a defined observation window and a named reviewer. It is designed to organize incoming information without treating every reading as an alert.

Device access and clinical escalation rules are integration dependent. This is not an emergency monitoring service.

A monitoring plan with boundariesDesign example
  1. 01
    Choose the plan

    Patient, measurement, device or source, and review window.

  2. 02
    Define the thresholds

    Clinician-approved criteria for routine review, escalation or suppression.

  3. 03
    Assign the response

    A named person or team, with review responsibilities and follow-up.

  4. 04
    Record what happened

    The reading, its source, the review and any authorized action.

Illustrated older woman with a walker, blood pressure cuff and pulse oximeter
A defined monitoring plan, with a responsible reviewer.
Meet the illustrated characters

Continuity between encounters · Proposed

Care should carry forward.
Even while attachment is pending.

A proposed continuity layer could help participating care teams carry an agreed summary, outstanding tasks and relevant history between encounters. It is designed to support handoffs for unattached patients and collaborative clinics.

01

A reusable summary

Relevant encounter history and an approved plan, with appropriate consent and access.

02

Visible outstanding work

Forms, referrals and follow-up tasks retain an owner and a next action.

03

A supported handoff

Share appropriate context with a participating receiving team through an authorized channel.

This concept does not provide attachment, replace an official medical record or imply access to NB Health Link, provincial waitlists or controlled-drug databases. Participation and information sharing require agreements and verified connections.

Specialized administration · Roadmap

Complex testing.
Connected paperwork.

The same execution approach could support the administrative work around genetic testing and liquid biopsy: requisition preparation, supporting documents, coverage paperwork and result routing.

This is a roadmap concept. Align eCare does not claim to perform testing, interpret genomic results, establish eligibility or hold laboratory or insurer partnerships.

01

Prepare the packet

Bring the requested form and available supporting information together for review.

02

Track the administration

Keep submission status, requests for missing information and the next responsible party visible.

03

Route to the responsible team

Organize the returned report for clinician review through an authorized connection.

Beyond the AI scribe

The note is one step. Completion is the goal.

Scribe capabilities vary. Compare preparation, review, routing and returned-work handling, then assess the evidence and product stage.

Manual workflowAI scribe aloneAlign eCare planned workflow
Forms and disability
Staff gather context and complete fields manually.
Drafting or form support varies by product.Planned source-linked preparation with practitioner review.
Referral follow-through
Staff assemble, send and chase missing information.
Letters and task support vary by product.Planned completeness review, routing status and returned-work ownership.
Prescription clarification
The clinic reconciles questions across the chart, prescriber and pharmacy.
Prescription-related features vary by product.Proposed eAttest verification and authorization sequence.
Billing evidence
The physician or staff review documentation and provincial rules.
Code suggestions and evidence support vary by product.Planned evidence-linked suggestions for professional review.
Completion and responsibility
People coordinate each handoff across systems.
Workflow tracking depends on the tool and integrations.Designed to make approval, next action, owner and status visible.

Trust centre

Evidence. Review. Professional authority.

Source-supported preparation and explicit approval are design requirements. Their implementation must be demonstrated before a clinical deployment.

01

Source and context

Relevant authorized information, with source and uncertainty visible. FHIR-informed connections remain integration dependent.

Integration status
02

Preparation and checks

Defined completeness and consistency checks support review. Rule-based processing is not a guarantee of correctness.

Execution and assurance
03

Professional authority

The responsible clinician reviews the exact item and proposed action. Approval and provenance controls require implementation evidence.

Physician approval

Our commitment: patient and clinic information will never be used for AI model training. Canadian data sovereignty and PIPEDA-aligned design are requirements to verify for each clinical deployment.

Read the privacy white paper
Frequently asked questions

More questions physicians ask about AI scribes, consent, eRx and billing

Consent

Do I need to obtain consent from the patient before using an AI scribe?

Recording and processing must follow the consent or other lawful authority required for the setting. Align eCare’s design calls for a clear explanation, a documented consent process where needed and an alternative workflow when recording is declined. Exact requirements must be reviewed for each deployment.

Consent

What happens if a patient refuses?

The proposed workflow supports continuing care without the recording tool. Declining optional technology should not be treated as permission to reduce care. The participating clinic must define the alternative workflow and consent process.

Liability

Who is responsible if an AI-generated document contains an error?

Professional review remains essential. The responsible clinician must check the item they authorize, while the vendor and participating organizations retain their own contractual and legal responsibilities. Software does not transfer all liability to one party or guarantee defensibility.

Liability

What record-keeping obligations apply to AI scribe recordings?

Recording, transcript, approved artifact and audit-history retention need separate rules. Applicable law, professional requirements and the clinic’s role must be assessed. Align eCare has not published a clinical retention schedule or a blanket zero-retention claim.

Workload

Why do physicians still work after hours (“pajama time”) if they already have an AI scribe?

A faster note does not necessarily finish forms, pharmacy clarification, referrals, billing review or follow-up. Documentation products vary. Align eCare’s planned focus is the preparation, approval, routing and tracking of that downstream administrative work.

eRx and eAttest

What happened to e-prescribing in Canada when PrescribeIT ended?

Transmission services, standards and vendor availability can change. Align eCare’s proposed eAttest protocol separates verification and prescriber authorization from the transmission channel. No live e-prescribing network connection or standards conformance is asserted by this site.

eRx and eAttest

What is eAttest, and how is it different from an electronic signature?

eAttest is a proposed verification and authorization protocol: assemble the prescription context, check completeness and consistency, present discrepancies for resolution, prepare the exact artifact, obtain prescriber authorization, transmit through an appropriate validated channel and retain the verification record.

eRx and eAttest

What does the physician actually check before attesting?

The planned review includes the patient and encounter, exact item, supporting sources, checks, uncertainty, changes, destination and proposed next action. Biometric-backed authorization requires implementation and validation. The website demonstration does not authorize or transmit a clinical prescription.

eRx and eAttest

What does eAttest prevent?

The objective is to reduce avoidable clarification caused by incomplete or inconsistent prescriptions. The effect must be measured. Verification cannot guarantee that a pharmacist will have no further questions or that every clinical or administrative issue will be detected.

Billing

How much do physicians lose to missed billing codes?

The amount depends on the service, province and practice. Align eCare has no measured revenue-recovery result to report. Its proposed billing workflow stages suggestions with the documented service and applicable rule for professional review. Payment and audit outcomes cannot be guaranteed.

Speech and language

Does Align eCare work in French, and with accented or child speech?

English and French performance, accents, code-switching, speaker separation and child speech need separate evaluation. This website does not assert validated accuracy across those groups. Unclear or conflicting source information should return for professional review.

Dr. Sarah, the illustrated Align eCare avatar, wearing a white coat, pajamas and bunny slippers

Meet Dr. Sarah.

Our illustrated avatar knows the white-coat-and-bunny-slippers routine. She gives a familiar face to the work Align eCare is being designed to help carry.

Meet the characters and hear the playlist

Built in New Brunswick

Founded in the waiting rooms.
Built around the work.

Karolyn Law, Founder of Align eCare, standing with arms crossed in a white blouse and sage-green skirt
Karolyn Law, Founder

Founder Karolyn Law is building Align eCare from firsthand experience navigating fragmented care and the administrative handoffs that consume patients’ and clinicians’ time.

Meet the founder

Clinical governance before clinical deployment

Pilot preparation must establish clinical workflow review, privacy responsibilities, technical validation and the responsible professional at each approval point.

Meaghan Law, Advisor, Technology and Security at Align eCare, head-and-shoulders portrait in a black blazer
Meaghan Law, Advisor, Technology and Security

Meaghan Law brings a background in IT, security systems, AI, programming, and software development. As a technology and security advisor to Align eCare, she helps review its technical plans, privacy safeguards, and security approach. Her review covers Align eCare's core commitments: patient data stays in Canada under Canadian data sovereignty, patient data is never used to train AI models, and all handling meets PIPEDA and New Brunswick's PHIPAA. Meaghan is the daughter of Align eCare founder Karolyn Law, and a proud mom of two beautiful children.

Other external advisors and participating clinicians will be named only with confirmed involvement and permission.

Read the governance approach
New Brunswick pilot cohort

Give the paperwork back to the system that created it.

We are preparing for clinic discovery and potential pilots in New Brunswick. Start with one workflow and an agreed baseline.