Alberta telehealth launch guide · 2026

Start a telehealth company in Alberta

Start here

For an Alberta telehealth business, clinical continuity and privacy assessment belong in the project schedule before launch. CPSA sets virtual-care expectations, and health information custodians need to assess their obligations under the Health Information Act. Choose the first service by the care you can safely complete, then build the technology and commercial arrangements around that service.

This guide covers Alberta. Check the rules for your profession, service, business location, and patients. Confirm Bask availability separately.

Published by Bask Health · Editorial process

Updated

The essentials

Alberta launch requirements at a glance

Start with the decisions that shape your legal structure and clinical workflow.

Selected requirements and planning decisions for Alberta. Read the linked steps for conditions and exceptions.
Launch decision Alberta
Provincial population4,262,635 residents in the 2021 Census.
Medical regulatorApply CPSA virtual-care expectations to the planned service.
Privacy planningAssess Health Information Act custodian and PIA obligations.
Clinical continuityConfirm an appropriate examination and referral pathway.
Roster ruleReview patient and practitioner locations before assignment.
Patient chargesObtain model-specific insured-service and fee advice.
Pharmacy checksVerify the legal dispensing business and clarification process.
Vendor diligenceCanadian Bask support remains subject to direct confirmation.

Summary only, not legal advice. Confirm the requirements for your business with Alberta counsel.

Find a launch step and its sources

These references support the discussion in each step. Operational suggestions are separate from legal requirements.

Local planning

Plan a telehealth service in Alberta

Alberta had 4,262,635 residents in the 2021 Census. Calgary and Edmonton account for large municipal populations, but neither city represents the province's whole care environment. The Statistics Canada table supports population comparisons; it does not measure unmet demand for a paid telehealth product.

Make a narrower research question useful to operations. For the intended patient group, what information is missing before an appointment? Which tests or examinations would make the remote offer incomplete? Where does responsibility sit after the initial consultation? Answers to those questions determine staffing and partner costs.

Avoid building an Alberta launch around an assumed national medical licence or a generic privacy certificate. The provincial professional and information frameworks require a review of the actual people, organizations, and work involved. A documented small service is a better starting point than a broad promise that relies on unresolved exceptions.

Step by step

How to start a telehealth company in Alberta

The eight steps below produce a practical decision record. Apply current rules with Alberta clinical, privacy, and business advisers before starting patient care.

  1. 1

    Translate the care proposition into an Alberta operating model

    Write down the problem the service addresses and the limits of the first offer. Specify which patients can join, which professional sees them, and the circumstances that require care elsewhere. This makes later legal and technical reviews concrete.

    Identify the organization delivering medical care separately from technology, marketing, and administrative services. The Canadian business registration guide describes incorporation options, while provincial registration and professional arrangements need local assessment.

    Ask advisers to examine ownership, professional independence, compensation, and the responsibilities in each contract. A management company should not quietly acquire clinical decision-making authority through software permissions or sales incentives. Check the actual operating behaviour alongside written terms.

    Create a cost model for the complete episode, including care that needs another setting. Account for document requests, pharmacy questions, and follow-up after an inconclusive remote assessment. Treat these as service work rather than exceptional overhead. A business model that works only when every patient receives the requested medicine needs revision before launch.

  2. 2

    Use CPSA authority as an assignment rule

    The CPSA virtual-care standard sets expectations for regulated members and addresses specified circumstances for out-of-province care. Read the relevant provisions against the planned service. Do not turn an exception into an unrestricted national staffing strategy.

    Collect evidence of each doctor's registration, conditions, clinical scope, and indemnity. Record the locations where the professional may work and where patients may receive the proposed care. A marketing statement about Canadian coverage cannot replace the credential record.

    Use those decisions when constructing the appointment roster. Test an Alberta patient, a patient temporarily outside Alberta, and a professional working from an unexpected location. The scheduling result should follow the approved rules, with a clear alternative when the proposed match is unsuitable.

    Assign an owner for registration renewals and changes. Pause new bookings when a material question is unresolved, and transfer unfinished clinical work through an approved process. Removing a calendar slot does not answer who reviews a result ordered during a previous encounter. Keep both responsibilities visible in the operating manual.

    Confirm the availability and integrations your Alberta service would need.

  3. 3

    Prepare the privacy impact assessment before implementation

    Alberta's Health Information Act guidance describes obligations for covered custodians. The privacy commissioner explains privacy impact assessments and the circumstances in which submission is required. Determine the relevant custodian and assessment obligations early in the project.

    A privacy impact assessment should describe the proposed information system, not a generic vendor brochure. Map collection, access, disclosure, retention, support, backups, and deletion. Explain why the service needs each category of information and which organization remains responsible.

    Include administrative practices as well as software. Staff may export records, discuss cases with a pharmacy, or contact a patient through another channel. Those actions can change the real information flow even when the underlying product is unchanged.

    Check the commissioner's current process and document what has been submitted or reviewed. Do not advertise regulatory approval merely because an assessment exists or has been sent. Keep legal compliance, regulator process, and vendor security evidence as separate facts. Revisit the assessment when a material feature or data arrangement changes.

  4. 4

    Build an examination option into the pathway

    CPSA's clarification of the virtual-care standard explains that necessary in-person care may be provided by another healthcare provider when continuity is appropriate. The practical task is to establish that continuity, not to attach a general clinic list to every message.

    Ask the medical director which findings require examination or testing. Identify the receiving service, its acceptance process, and the information it needs. Do not assume a local organization has agreed to take patients simply because its public website lists the relevant specialty.

    Test the handoff from both sides. Can the virtual team send the necessary record? Does someone confirm receipt? Who contacts the patient if the referral is declined or the appointment cannot occur? Those questions should have named owners before the first live case.

    A Calgary arrangement does not automatically establish a workable option for every Alberta community. Set the offer's geography according to the confirmed pathway. When expanding, assess local travel and access conditions with the proposed patients and partners. Treat a broader territory as an operational change that needs evidence.

  5. 5

    Validate insured-service and patient-fee assumptions

    Before accepting payments, have the proposed services reviewed against Alberta insurance administration and professional rules. List the provider, service, payer, and basis of the fee. Keep uncertain classifications out of the public price list.

    The national Canada Health Act explanation describes the federal framework. The Services Policy letter adds context for doctor-equivalent medically necessary services from April 2026. Neither page replaces a review of the actual Alberta transaction.

    Examine subscriptions and employer agreements by what they purchase. An administrative label cannot settle whether a charge is permitted or whether it affects access to insured care. Explain any approved uninsured services in plain terms without implying a guaranteed clinical outcome.

    Rehearse the payment response when a consultation is cancelled, redirected, or clinically unsuitable. Decide how staff handle a duplicate charge and a disputed renewal. Retain the service version associated with the receipt so a later complaint can be assessed against the offer the patient actually accepted.

  6. 6

    Connect the prescription to a verified dispensing process

    Determine what clinical evidence is needed before each proposed treatment. An online form can collect information, but it should not promise a prescription before a professional assessment. Keep prescribing rules and medicine-specific precautions within the clinical team's governance.

    Verify the dispensing organization using Health Canada's online-pharmacy guidance and the appropriate provincial register. Record the pharmacy's legal identity, address, and agreed service area. A national shipping claim is not a substitute for those checks.

    Have the pharmacy rehearse a clarification request with synthetic information. Decide whether the answer returns to the original doctor or a covering professional, and how the change reaches the patient. Track unresolved requests as work that can block care.

    Separate prescription transmission from dispensing and delivery. A successful technical response does not demonstrate that the medicine was appropriate, available, or received. Keep the patient informed about the actual stage. Review financial arrangements so a clinical refusal or pharmacy concern is supported without pressure to complete a commercial order.

  7. 7

    Test the patient journey under ordinary constraints

    Invite representative users to test the explanation and navigation with safe records. Ask them to identify the service limits, expected follow-up, and route for urgent concerns. Look for misunderstanding before measuring whether the interface converts visits into sales.

    The federal virtual-care framework highlights access and integration. Translate that into tests for interrupted connectivity, inaccessible forms, limited private space, and a need for language support. Avoid assuming that one device test represents every patient.

    Create a clinically approved fallback when the preferred connection fails. The professional should decide whether another method provides enough information. Some encounters should be rescheduled or redirected rather than completed through a degraded channel.

    Check reminder and support messages for unnecessary health details. A notification may appear on a shared device even when the clinical application has strong access controls. Give patients clear communication choices and review those choices as part of the information arrangement, not only as a marketing preference.

  8. 8

    Review the pilot before adding Alberta volume

    Use a limited first release with enough staff to investigate failures. Track wrong assignments, uncompleted referrals, outstanding results, pharmacy delays, and unclear charges. These measures reveal whether the care pathway works beyond the intake screen.

    Set criteria for pausing acquisition when clinical or operational capacity is exceeded. Ask the medical lead to review incentives, including whether staff feel pressure to shorten necessary work. Appointment speed is not a sufficient measure of appropriate care.

    Recheck the source register at each material expansion. Confirm current CPSA expectations, privacy assessment responsibilities, payment rules, and partner arrangements. Keep a record of the decision and the implementation change it produced.

    For a Bask evaluation, bring the Alberta workflow and its unresolved integration requirements. Ask about Canadian contracting, data processing, prescribing support, and local service dependencies. This guide does not confirm Alberta product availability or authorize an international clinical arrangement. Obtain the relevant evidence before setting patient-facing expectations.

    Sources: CPSA virtual care standard.

What to launch

Telehealth categories to evaluate in Alberta

These are service design examples for professional assessment. They are not approved clinical protocols or evidence of local demand.

Coordinated remote follow-up

A follow-up service should show what information arrives before the encounter and what reaches the patient's continuing care team afterward. Test the handoff when the original professional is unavailable. The operating benefit to demonstrate is continuity, not simply an additional appointment channel.

Clinically supervised monitoring

Monitoring creates obligations between consultations. Identify who reviews incoming measurements and who handles missing or concerning information. Confirm the assessment route if the data cannot support a safe remote decision. Include that staffed response in both the service price and capacity plan.

Employer-supported navigation

An employer may help people reach a reviewed service, but the employment relationship creates privacy questions. Decide what the employer can receive and prevent unnecessary clinical disclosure. Review the payment structure separately from the convenience of the distribution channel.

Built for telehealth

Discuss international requirements with Bask

A practical Bask brief should include the Alberta privacy assessment requirements and clinical handoffs. Evaluate software against those documented needs with synthetic encounters before relying on an implementation estimate.

Built with Bask

Trusted by telehealth teams

Amble Logo
Locklab Logo
Layla Logo
Mojoon Logo
Good Life Logo
Piper Logo

Customer experiences supplied with permission. These are individual testimonials, not independently audited results or evidence of Bask availability in another country.

“We’ve been through four telehealth platforms — including a homegrown solution — and Bask Health is the first one that truly works the way it should. The platform is intuitive, reliable, and has materially improved both our patient intake flow and conversion rates. What really sets Bask apart is the team. They’re responsive, open to feedback, and genuinely willing to build new features that support the business while improving the patient experience. It feels like a partnership, not just software. I can’t say enough good things about the platform or the people behind it.”
Jeff Strauss · CEO & Founder, GetMyStride

Read all eight customer testimonials →

Alberta telehealth FAQ

Does every Alberta virtual service need a privacy assessment?

The answer depends on the entity, information, and proposed practices. Covered health information custodians should assess the Health Information Act and current commissioner guidance before implementing changes. Do not assume an existing vendor document settles the custodian's obligations.

Must the same doctor provide the later examination?

CPSA guidance recognizes appropriate continuity through another healthcare provider in relevant circumstances. The service must establish a workable handoff. A list of clinics without confirmed access or information transfer does not demonstrate that arrangement.

Can another Canadian registration cover Alberta patients?

Review the current CPSA standard and the specific circumstances. Out-of-province provisions are not a universal national licence. Document the authority relied on before making the doctor available for the proposed Alberta service.

Can a subscription make an insured service privately billable?

The subscription label does not determine the service's status. Have the actual charge and access conditions reviewed under Alberta rules and the relevant national framework. Publish only the offer supported by that assessment.

What evidence should accompany a Bask evaluation?

Bring the clinical scope, location rules, privacy data map, partner handoffs, and billing decisions. Ask Bask to confirm support for the precise Canadian arrangement. Customer experience in another jurisdiction cannot establish Alberta authorization.

Your next step

Ready to launch in Alberta?

Bring your treatment plan, target patient group, and launch dependencies. Discuss the software and integrations your service needs.

We’ll save your details to our waitlist so the Bask team can follow up, then open the calendar to choose a time.

Open the booking calendar directly

See our Privacy Policy.

Alberta launch guide