Can a practice keep its EMR, pharmacy system or booking tool when it replaces its website?

Yes. A practice can replace its website and keep every piece of software it runs. The website does not hold the record, the schedule or the billing; it connects to the part of your software that patients touch, and only in the ways the vendor supports. This page explains the two layers, the five routes, what the common Canadian vendors document, and what to confirm before anyone promises a connection.

Most practices run two layers of software. The clinical system holds the record, the schedule and the billing. The patient facing tool is what a patient touches: booking, a refill request, an intake form or a portal. A website connects to the second layer, through whatever the vendor supports, and never replaces the first.

Researched examples, not a list of clients. Each profession's page carries the full table with what a patient does and the website route for each product. Industries.

What the common vendors document

These are the conditions the vendors themselves publish, read on 1 October 2026. They change; the current version is checked for your practice at proposal.

Jane

Jane documents booking buttons and links to Jane hosted booking, by practitioner, location or service. It does not offer an open API, and its integration program is a vetted partner route that excludes clinic built or single use integrations and direct calendar posting. A full calendar iframe is not a supported route. Jane also sells its own website builder; the case for a separate site rests on profession specific content, design, migration and clinical review, not on the booking button, which any site can carry.

Ocean

Ocean generates a booking link for each clinic, connected to a supported EMR. Its setup guidance discourages placing that link in an HTML iframe, so on a website Ocean is a link, not an embed. Compatibility is feature by feature and EMR by EMR.

The TELUS EMRs

PS Suite and Med Access route patient booking through a connected tool such as Ocean or Pomelo. The Collaborative Health Record has its own eBooking and the Connect patient app, and TELUS lists an Enterprise API as a separate, subscribed add on. That listing shows a route exists; it does not show that a given clinic's contract includes it or that any agency has access.

Cliniko and Practice Better

Both document an embed: Cliniko provides iframe code and custom booking pages filtered by practitioner, location or appointment type, and Practice Better provides service, package and program links, public booking pages and an embedded booking widget. Cliniko also documents a REST API with private keys, which belongs on a server and never in a page. An embed proves that booking can sit inside your site; it does not prove any clinical write back.

Pharmacy systems

Kroll's patient side is PharmaConnect, TELUS Health's add on for refills, prescription photos and appointments. Propel Rx is McKesson's current system, formed from PharmaClik Rx and Nexxsys; its documentation names web refill channels through banner programs, and it is not offered in Quebec. Fillware pharmacies may have a refill portal or the FillAssist app. WinRx documents booking through its Pharmacy Dashboard package. MedMe recommends a booking link per service; MedEssist documents an embed for existing pharmacy websites. None of these establishes a public API for a generic website form to write into the dispensing system, and a refill request remains a request a pharmacist reviews.

Dental systems

ABELDent, ClearDent, Tracker, Dentrix, Open Dental, Curve Hero, MaxiDent, Paradigm, and Dentitek and Progident in Quebec each sell online booking or a patient service, usually as an add on with plan conditions. Several treat a new patient booking as a request the practice accepts. Claims move through CDAnet and ITRANS inside the certified practice software, by staff, and are not a website feature.

PrescribeIT

PrescribeIT, the e-prescribing service operated by Canada Health Infoway, ended on 29 May 2026. We do not describe it as an integration, and we confirm a clinic's current prescribing workflow with the clinic and its EMR vendor rather than relying on older vendor pages.

How Monograph handles it

Every Monograph proposal names the route for each tool the practice runs, using the five routes above, and lists the vendor conditions and fees beside it. Nothing is described as connected until it has been scoped for your system and tested with non patient data. The register of systems, routes and status is public on the integration page, and each profession's page shows the tools that profession may already use. Where a vendor's documentation changes, the register changes with it.