Partner Integrations
Qliva's approved integrations are reference implementations — each one demonstrates what is possible within the platform for a particular category of clinical or operational data. New partners in similar categories can use these as a model for what a well-integrated partnership looks like.
Medical Objects / Capricorn
Category: Inbound clinical data (HL7 v2)
What it does: Medical Objects is Australia's primary clinical messaging network. The Medical Objects / Capricorn integration delivers structured pathology results, clinical correspondence, and specialist letters directly into the Qliva practitioner inbox.
Clinical problem solved: Pathology results previously arrived by fax or as scanned PDFs — unstructured, manual, and error-prone. The Medical Objects integration delivers results as structured HL7 v2 data: individual test values with units, reference ranges, and flags. This enables trending, AI analysis, and integration with the longitudinal biomarker dashboard — things that are impossible with PDF-based result delivery.
What it demonstrates: A pathology laboratory, radiology practice, or specialist network that wants to deliver results to Qliva clinics electronically can follow this pattern. The integration uses HL7 v2 over mTLS — the Australian clinical standard. See HL7 Integration for detailed guidance.
Parchment Health
Category: Outbound clinical data (electronic prescriptions)
What it does: Parchment Health is an ADHA-approved eRx provider. The integration allows Qliva practitioners to issue electronic prescriptions that are immediately available for dispensing at any eRx-enabled pharmacy in Australia. Parchment notifies Qliva when a prescription is dispensed.
Clinical problem solved: Paper prescriptions create friction for patients and can be lost or damaged. eRx tokens are delivered instantly to the patient via the portal or SMS. The closed-loop dispensing notification means practitioners know whether a prescription has been collected — without a phone call.
What it demonstrates: Any platform operating within Australia's electronic prescribing ecosystem — pharmacy management systems, dispensing networks, or prescription benefit platforms — can integrate with Qliva at this layer. The integration is webhook-based: Parchment sends event notifications to Qliva, and Qliva sends prescription data to Parchment.
Tyro Health
Category: Payments (EFTPOS, HICAPS, Medicare)
What it does: Tyro is used for in-clinic billing only — EFTPOS terminal payments, HICAPS private health fund claiming, and Medicare Online Claiming. Online patient payments via the booking page or patient portal use Stripe, not Tyro. Tyro is Australia's leading health payments provider. The Tyro integration enables Qliva clinics to collect EFTPOS payments via physical terminal, process private health fund claims via HICAPS, and submit Medicare Online claims — all from within Qliva.
Clinical problem solved: Health payments in Australia involve multiple streams: patient co-payments, private health fund rebates, Medicare bulk billing, and private billing. Tyro unifies these through a single terminal and API, eliminating the need for separate billing software.
What it demonstrates: A payment or billing platform that wants to integrate with Qliva's invoicing and billing workflow. The integration is bidirectional: Qliva sends payment requests to Tyro, and Tyro sends payment confirmation events back via webhook to automatically update invoice status.
Xero
Type: Accounting sync (OAuth 2.0) Direction: Qliva → Xero (one-way push)
Qliva connects to Xero via OAuth 2.0. Once connected, invoices and payments are pushed to Xero automatically when created or updated in Qliva. Patients are created as Xero contacts on first invoice.
OAuth scopes requested:
accounting.contacts— create/update patient contactsaccounting.transactions— create invoices and record paymentsaccounting.settings.read— read organisation settings (currency, tax)
Callback URL: https://{subdomain}.qliva.com.au/api/xero/callback
Key behaviour:
- Invoice sync fires on invoice create and on payment status change
- Xero is an accounting record only — it does not initiate or collect payments
- Disconnecting Xero stops future syncs but does not delete data already in Xero
Stripe
Category: Payments (subscription and card billing)
What it does: Stripe handles recurring membership billing. When a patient subscribes to a clinic membership, Stripe manages the subscription lifecycle — card storage, billing cycles, payment retry (dunning), and cancellation — and notifies Qliva of all subscription events via webhook.
Clinical problem solved: Running recurring wellness programs and memberships requires reliable subscription billing infrastructure. Stripe provides this with strong fraud protection, global card support, and a comprehensive dunning system that reduces involuntary churn.
What it demonstrates: A platform offering any form of recurring or subscription-based billing integration with clinic software. The integration uses Stripe Checkout for patient-initiated subscriptions and the Stripe API for admin-initiated enrolments.
Deepgram
Category: Clinical AI (speech-to-text transcription)
What it does: Deepgram powers the AI Ambient Scribe — Qliva's real-time clinical transcription feature. Audio from a consultation is sent to Deepgram's nova-2 model server-side, returning a timestamped transcript with speaker diarisation (distinguishing between the practitioner and patient voices).
Clinical problem solved: Clinical documentation is one of the largest sources of practitioner burnout. The Scribe listens to the consultation and produces a draft note mapped to the practitioner's chosen template — dramatically reducing post-consultation documentation time.
What it demonstrates: A clinical speech recognition or AI documentation platform that wants to integrate with Qliva's note-taking workflow. The integration is a server-side API call — audio chunks are forwarded from Qliva's backend to the transcription service, and the resulting transcript is stored against the consult note.
Resend
Category: Communications (transactional email)
What it does: Resend is Qliva's email delivery infrastructure. All transactional emails to patients and practitioners — appointment confirmations, result notifications, magic links, invoice emails, form assignments — are delivered via Resend.
Clinical problem solved: Reliable email delivery is critical for clinical communication. Resend provides high deliverability, domain authentication (DKIM, SPF, DMARC), and detailed delivery analytics — ensuring patients receive time-sensitive clinical notifications.
What it demonstrates: A communications platform (email, SMS, push notification) that wants to serve as the delivery layer for Qliva's patient and practitioner communications. The integration is an outbound API call from Qliva to the delivery service, with webhook callbacks for delivery events (opened, clicked, bounced, unsubscribed).
Last updated 2026-05-15