Qliva connects to a range of external platforms to keep your clinic's tools in sync. This page covers each available integration, what it does, and how to set it up.


Stripe

Purpose: online appointment payments, patient portal checkout, and membership subscriptions.

Note: Stripe is not a per-clinic connection — there's no OAuth flow to complete. It's provisioned platform-wide by Qliva via a single API key, and is already active for your clinic.

Tyro Health

Purpose: in-clinic EFTPOS, HICAPS health fund claiming, Medicare online claiming, and payment links.

Go to Admin Portal → Settings → Tyro and configure your terminal settings and practice ID.

  • HICAPS claiming — patients tap their health fund card at the Tyro terminal and the claim is processed on the spot
  • Medicare — requires practitioner Medicare provider numbers set on each practitioner's profile, and patient Medicare card numbers saved on the patient record

Xero

Purpose: sync invoices, payments, and patient contacts to Xero for accounting.

Go to Admin Portal → Settings → Integrations → Xero → Connect. You'll be redirected to Xero to authorise the connection.

What syncs to Xero:

  • Invoices (with line items)
  • Payments
  • Patient contacts

What doesn't sync:

  • Appointments
  • Clinical notes
  • Prescriptions

To disconnect, go to Settings → Integrations → Xero → Disconnect. Existing data already synced to Xero is not deleted.

Note: Xero is for accounting only — it does not process payments. Stripe and Tyro handle payment collection.

Parchment Health (eRx)

Purpose: electronic prescription issuance and dispensing status tracking.

Go to Admin Portal → Settings → Integrations → Parchment and enter the credentials provided to your clinic by Parchment Health.

Once connected, practitioners can issue eRx tokens from within Qliva. Patients receive a QR code and alphanumeric token that pharmacies scan to dispense the prescription.

For technical detail, see eRx (Developer).


Bloody Good Tests (BGT)

Purpose: private pathology ordering and lab result retrieval — an alternative to Medical Objects for clinics using BGT as their lab provider.

Go to Admin Portal → Settings → Private Pathology Providers and enter the BGT credentials provided to your clinic. Once connected, Qliva caches the BGT test catalogue so practitioners can select BGT tests directly from the pathology request form, and results/webhooks come back into Qliva the same way Medical Objects results do.

iScreen

Purpose: private pathology ordering and lab result retrieval with iScreen as the lab provider.

Go to Admin Portal → Settings → Private Pathology Providers and enter your iScreen credentials. As with BGT, Qliva caches the iScreen catalogue for use on pathology request forms, and configures the webhook needed to bring results back into the Pathology Inbox automatically.

Medical Objects (Pathology HL7)

Purpose: receive structured pathology results and clinical correspondence from labs directly into Qliva.

Go to Admin Portal → Settings → HL7 and enter your Medical Objects configuration details.

Labs send HL7 v2 messages to your Qliva endpoint. Results appear in the Pathology Inbox; clinical letters appear in Clinical Mail.

For technical detail, see Pathology HL7 (Developer).


Shopify

Purpose: embed your Shopify store in the patient portal, or sync Shopify products into Qliva.

Go to Admin Portal → Settings → Storefront → Shopify and enter your store domain and API tokens.

For full setup instructions and a comparison of Full vs Partial modes, see Storefront.


Squarespace

Purpose: link your Squarespace store, sync products into Qliva, or enable post-purchase booking automation.

Go to Admin Portal → Settings → Storefront → Squarespace and enter your store URL and Commerce API key.

For full setup instructions and the post-purchase booking flow, see Storefront.


Calendar Sync

Purpose: pull busy blocks from your external calendar into Qliva, and push Qliva appointments back to your external calendar.

For setup instructions and supported providers (Google, Microsoft, Apple), see Calendar Sync.