Microquest HealthQuest EMR support in Canada: the complete guide (2026)

What "HealthQuest support" means in practice

1. Microquest vendor support. The HealthQuest application, database engine, billing modules, conformance updates, Netcare integration in Alberta, and core feature bugs.
2. Local clinic IT support. Workstations, the HealthQuest client install and updates, the Windows server hosting the database for on-premise deployments, the network, printing, scanning, lab integrations, eHealth / PIP / Netcare connectivity, backups, and the helpdesk that answers when something is slow or broken.
3. Practice / training support. Templates, workflow design, billing rules — sometimes Microquest, sometimes a third-party trainer, sometimes a clinic super-user.

HealthQuest on-premise vs hosted — and why it matters for support

HealthQuest historically ships as an on-premise install: a Windows server in the clinic running the database, with HealthQuest clients on each workstation. Microquest also offers hosted deployments. The split changes who owns what:

The most common HealthQuest support issues

• "HealthQuest is slow this morning." Almost always local — disk pressure on the database server, antivirus scanning the database file, or a switch / cabling issue. Rarely a Microquest problem.
• HealthQuest client won't launch after a Windows update. Local — re-register the client, check .NET / runtime versions.
• Label printer or lab requisitions printing wrong tray. Local — printer driver, default tray, or HealthQuest print profile.
• Lab results not coming in. Shared — check the local HL7 / interface workstation first, then escalate to Microquest with the message ID.
• Netcare lookup failing in Alberta. Shared — token expiry and certificate issues are common; the vendor needs the diagnostic data the local partner pulls.
• Backup of the on-prem database is failing. Local — image-based backup with a HealthQuest-aware quiesce step is the right pattern.

What a good local HealthQuest support partner does

• Maintains a documented HealthQuest server runbook: version, install path, backup config, restore procedure tested at least quarterly.
• Excludes the HealthQuest database files from real-time antivirus while keeping EDR on the rest of the system.
• Runs an image-based backup with an immutable / offsite copy, not just Microquest's native backup.
• Opens vendor tickets with the clinic — attaching event logs, screenshots, and message IDs — so Microquest can act on the first response.
• Maintains the workstations on a 3–4 year refresh cycle to avoid the gradual slowdowns that get blamed on HealthQuest.
• Owns Netcare / PIP token health monitoring so integration breaks are caught proactively.

HealthQuest downtime procedure — the minimum viable plan

1. Confirm scope: one workstation, all workstations, or server.
2. If server-side: pull patient lists for today and the next two days before rebooting anything.
3. Switch to paper encounter templates kept at every workstation.
4. Notify reception and waiting room; do not send patients home in the first 30 minutes.
5. Open a ticket with the IT partner and, if application-side, with Microquest in parallel.
6. On restoration, back-enter visits in date order and reconcile billing the same day.

What to look for in a HealthQuest support partner

• Named technicians who have actually touched a HealthQuest install — not a generalist MSP that will learn on your ticket.
• A signed information management service provider agreement consistent with HIPA / PHIPA.
• A 15-minute response SLA during clinic hours and a documented after-hours path.
• Backups they will show you restoring, not just describe.
• Familiarity with the Saskatchewan PIP environment if you are in Saskatchewan, or Netcare if you are in Alberta.

We support HealthQuest installs across Saskatchewan and coordinate directly with Microquest on behalf of our clinic clients. Book a 30-minute review and we'll send back a written assessment of your current HealthQuest setup.