Canopy. The next generation of AI EMR and clinic OS. Natively FHIR.

Work before, during and after care comes together around one clinical record.

Thoughtfully taking shape for Saskatchewan and beyond.

Illustrative interface · fictional patient and clinic

Where clinic software falls short, and how Canopy is designed instead.

  • A clinic spread across tools

    One clinic. One system.

    Scheduling, portals, operations, the EMR, billing and follow-up all work from one foundation.

  • AI bolted onto old systems

    AI-native by design

    Intelligence built into the workflow—not bolted on as another layer.

  • Records locked inside the software

    Your clinic’s data shouldn’t be trapped

    Built natively on FHIR. Stored in FHIR. Ready for a connected future.

Before, during and after the visit, around one record.

Scheduling, portals, operations, the EMR, billing and follow-up all work from one foundation.

  1. Before the visit

    • Scheduling Booking and the clinic's day, in the same system as the chart.

    • AI front desk Replies to patients and sends intake before the visit.

    • AI-assisted intake Intake collects the history before the visit.

  2. During the visit

    • AI-assisted documentation Documentation support at the point of care.

    • Draft plans Next steps, drafted for clinician review.

    • Patient-data ontology Brings relevant context from the record into AI-assisted workflows.

  3. After the visit

    • Billing-code suggestions Codes suggested from the visit, for review.

    • Patient portal Patients reach the clinic through the same foundation.

    • Clinic-operations portal Administrators run the clinic from the same data.

The clinical record An AI-native EMR at the centre of everything else.

Explore the platform

Trusted AI

AI agents that answer to the clinic.

Only the access a task needs, a clinician’s review for clinical work, and patient information kept to the task.

See how it works

Connected Canopies

One patient. One chart. Every clinic under the canopy.

Every clinic in a health authority works from the same chart.

See how it works

The thinking behind Canopy

Our Philosophy

  • The Record Is Not the Product

    Why the medical record should outlive the software used to write it — and why OpenOrchid treats interoperability as architecture, not compliance.

  • Every Pixel Accounted For

    Healthcare software is the most consequential software most of us will ever depend on. It is also, too often, the least considered. This is the philosophy we bring to changing that.

Privacy and compliance

Built to Canada’s health‑privacy rules from the first line of code.

Canopy is designed around the laws and professional standards that govern health information in Saskatchewan. Compliance is part of the architecture, not a layer added later.

  • PIPEDA

    Personal Information Protection and Electronic Documents Act

    Federal

  • HIPA

    The Health Information Protection Act

    Saskatchewan

  • CPSS

    College of Physicians and Surgeons of Saskatchewan

    Regulator

More than an EMR.

Thoughtfully taking shape for Saskatchewan and beyond.