More services

EMR and pharmacy system integration

Yes, a Monograph site works with the booking system, EMR or pharmacy software your practice already runs, in one of five ways: a link or button to the tool the vendor hosts, an embed of the tool inside your site where the vendor supports one, a link to a patient tool your system is already connected to, a request form that routes into your system, or a direct connection through the tool's interface where the vendor allows it. The table below names the systems, the professions that run them, the methods and whether Monograph has delivered each one.

From $2,000 for a direct connection CAD, before tax. Final price quoted after discovery.

Each proposal says which method applies to each tool, and why. A link and an embed are part of every build, and so is linking to a patient tool your system is already connected to. A routed request form is part of Signature and Platform builds. A direct connection is scoped and quoted separately, because what a vendor allows depends on the system, the version and the contract your practice has with them.

What each vendor allows changes over time, so the options for your system are confirmed at discovery, and nothing is described as integrated until it has been scoped and tested for your practice.

Every connection is reviewed for privacy before launch: what data moves, where it is stored, and who can see it.

The five ways a site connects

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.

1. Link or buttonThe website sends the patient to the booking page, refill tool, intake form or portal the vendor already hosts. Works with any tool that has a public address, and with the button code some vendors generate. Confirmed at proposal: The address your practice approves for patients, and any rule about new or existing patients.
2. Vendor supported embedThe vendor's own booking or intake component runs inside your page, so the patient does not leave your site. Only where the vendor documents an embed, and only when it works with a keyboard and on a phone, with a plain link as the fallback. Confirmed at proposal: The vendor's current embed documentation, the module enabled on your account, and a test on a phone.
3. Existing vendor connectorYour clinical system already connects to a patient tool (an EMR to Ocean, a practice system to an exercise platform). The website links to that tool; the connection between the two systems is the vendor's, not ours. Confirmed at proposal: The exact product, edition and module on each side, what the connector is permitted to do, and your vendor's confirmation.
4. Routed requestA form Monograph builds sends a refill, transfer, intake or registration request into your own system or a Canadian hosted intake tool, not to a shared inbox and never by plain email. A clinician at your practice still reviews every request. Available in Signature and Platform builds. Confirmed at proposal: The destination your team will work from, who owns it, and where it stores what it receives.
5. Direct connectionNew, authenticated data exchange between the website and your system through the vendor's own interface. Only where the vendor grants access, and always scoped, quoted and tested separately before patients use it. Confirmed at proposal: Vendor access or approval, a suitable contract, the defined data flow, a test environment, and who maintains it.

Systems, methods and status

Researched examples, checked against each vendor's current public documentation. Naming a product here does not mean the vendor endorses Monograph or that a connection has been built for a client. What a vendor allows depends on the product, the edition, the enabled modules and your contract with them, so each route is confirmed for your practice at proposal.

Status as of 1 October 2026. A system not listed here can usually be linked or embedded; ask and we will confirm before you buy. Product names belong to their vendors and appear here to describe compatibility, not endorsement.

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.

What integration does not mean

• No form on a site we deliver asks for personal health information, and the message field asks patients not to include it. Forms collect contact details and a short message; refill, transfer, intake and booking requests are routed into your own system or a Canadian hosted intake tool, never by plain email.
• Monograph does not hold your appointment data, your patient records or your prescriptions. What a patient can do inside the booking or request step is set by your system, not by the website.
• A click on a booking button is counted by the website as a click, in your own first party analytics. A completed booking is counted only where the vendor permits it; some booking tools, Cortico among them, do not run third party scripts inside the booking flow, so the website never claims to know what happened after the click.
• A website does not replace your clinical record, your province's prescribing infrastructure or your insurer's adjudication. Claims tools such as TELUS Health eClaims and CDAnet are used by your staff inside your practice software; the site only explains your billing policy.
• Nothing is described as connected until it has been scoped for your system and version and tested with non patient data. Vendor fees for portals, interfaces or add on modules are yours and are listed in the proposal.

What you get

• A written review of what your system and vendor allow
• The simplest connection that does the job, chosen with you
• A privacy review of each data flow before launch
• Testing with real scenarios before patients use it
• Documentation of how it works, for your team and your vendor

What it does not do

• We do not claim a direct connection to any vendor until it is scoped and tested for your practice.
• Vendor fees for portals, interfaces, or add on modules are yours and are listed in the proposal.
• Vendors change their terms. When they do, a connection may need work, covered within Care's monthly hours or quoted separately.

Where it sits. Links and embeds are part of every build. Request forms that route into your system are in Signature. Direct connections are scoped and quoted separately. See the three build tiers.

Related: Booking through what you already use, Refill and transfer requests.