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.
Planned forms workflow · Synthetic demonstration · No CRA connection
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.
- Impairment category
- Markedly restricted
- All or substantially all the time
- Prolonged, 12+ months
- Effects described
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.
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.
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 codesAn 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 → claimRevenue 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 estimateAbout 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.
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
- 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.
A plan you can take home.
Prepared from the encounter. Reviewed by the clinician. Shared through an agreed delivery channel.
The reason for the visit, the clinician’s assessment and the agreed plan, in plain language.
Separate lists for new, changed, continued and stopped medications, based on clinician-approved instructions.
Tests, referrals, preparation instructions, contact responsibility and follow-up expectations.
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.
Proposed workflow. Delivery channels, medication checks, source mappings and portal connections require implementation and validation. No live integration is represented by this illustration.

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.
- 01Choose the plan
Patient, measurement, device or source, and review window.
- 02Define the thresholds
Clinician-approved criteria for routine review, escalation or suppression.
- 03Assign the response
A named person or team, with review responsibilities and follow-up.
- 04Record what happened
The reading, its source, the review and any authorized action.

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.
A reusable summary
Relevant encounter history and an approved plan, with appropriate consent and access.
Visible outstanding work
Forms, referrals and follow-up tasks retain an owner and a next action.
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.
Prepare the packet
Bring the requested form and available supporting information together for review.
Track the administration
Keep submission status, requests for missing information and the next responsible party visible.
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 workflow | AI scribe alone | Align 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.
Source and context
Relevant authorized information, with source and uncertainty visible. FHIR-informed connections remain integration dependent.
Integration statusPreparation and checks
Defined completeness and consistency checks support review. Rule-based processing is not a guarantee of correctness.
Execution and assuranceProfessional authority
The responsible clinician reviews the exact item and proposed action. Approval and provenance controls require implementation evidence.
Physician approvalOur 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 paperMore questions physicians ask about AI scribes, consent, eRx and billing
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

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 playlistBuilt in New Brunswick
Founded in the waiting rooms.
Built around the work.

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 founderClinical 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 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 approachGive 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.