This section is for clinic IT staff, lab admins, integration partners, and developers connecting external systems to Qliva.
Who this section is for
Most clinic staff won't need to read this section. If you're a practitioner, receptionist, or clinic manager, the Clinical and Admin sections cover everything you need day to day.
The Developer section is for people who need to connect Qliva to an external system — whether that's a pathology lab, a prescribing network, an SMS provider, or a custom integration you've built in-house.
That includes:
- Clinic IT staff setting up or managing technical integrations
- Lab admins routing HL7 messages from Medical Objects or similar networks
- Integration partners building on top of Qliva's webhook infrastructure
- Developers automating workflows with tools like Zapier, Make, or custom code
What this section covers
| Topic | What it's about |
|---|---|
| Webhooks | Event notifications sent to your systems when things happen in Qliva |
| Pathology HL7 | Receiving structured results and clinical correspondence via HL7 v2 |
| eRx (Parchment) | Electronic prescriptions via the Parchment Health network |
| SMS Sender ID | Registering a custom sender name for your clinic's SMS messages |
| Data Sovereignty | Where your data lives, how it's protected, and which third-party services are used |
You don't need to read this section to use Qliva. If you're looking for day-to-day guidance, start with the Clinical or Admin sections instead.
Getting help
If you're setting up an integration and run into something that isn't covered here, contact Qliva support. For HL7 endpoint credentials or custom compliance requirements, support is the right starting point — some configuration is handled on our side.