You asked for the estimated cost per pathology request, and whether it includes follow-ups.
$20 per asynchronous request.
What that covers
- A nurse practitioner or doctor reviews the member's intake asynchronously
- The pathology request is issued where clinically appropriate
- No telehealth appointment for your member to book or wait for
The rest of the price list
You asked for any API documentation you can scope out.
We'll take your engineers through it directly.
We don't run a public developer portal. Partner integrations work on an agreed contract that sits in front of our clinical system, so your team builds against a stable interface and never against our internals. The quickest way to scope it is a technical session with your engineers, and we can hold one this week.
These are the patterns we already run in production across payments, claiming, pathology, prescribing, pharmacy fulfilment and patient messaging.
REST and JSON
Structured patient and clinical payloads with validation and clear business errors.
Webhooks
Near real time events for status changes, results, prescriptions and messages.
HL7
Electronic pathology orders out and results back in.
OAuth 2.0
Client credentials at the integration edge, with signed webhooks where supported.
Correlation and idempotency
One request stays traceable end to end, through retries and repeated events.
Secure file transfer
Clinical documents and attachments through private, signed access.
What we'd agree with you first
You asked how we support partners with treatments like GLP-1s and HRT, with Hone Health as the reference.
Test, consult, treat, retest. We run that loop every day.
The Hone model is a loop, and it is the one our own clinics already run. We see up to 3,000 weight loss patients a week, and our women's health service covers perimenopause and menopause care. For a partner, our nurse practitioners and doctors become the clinical layer behind your brand. Both prescribe and both request tests.
Test
Your member completes their baseline bloods through Vively.
Consult
A nurse practitioner or doctor assesses the member and prescribes where appropriate.
Treat
The eScript goes to pharmacy and medication is delivered to the door, cold chain included.
Retest
Follow-up bloods track progress and keep the member active in your app.
Where the revenue sits
You raised Sonic's private pathology costs, and your need for raw results as structured data.
Sonic is what we run today. Bloody Good Tests is the route we're building towards.
Sonic Healthcare
A two-way HL7 integration. Orders go out electronically and results come back into the patient record.
38,000+
tests ordered electronically through this integration
Bloody Good Tests
We are exploring a deeper integration with Bloody Good Tests as our pathology route outside Sonic. This is the option we'd put forward for Vively.
We understand Sonic's private pricing doesn't work for your model, so we are not asking you to adopt it.
How the Sonic integration works
One thing worth clearing up: it is not PDF only. Results arrive as HL7 and are parsed into individual analyte values, with the lab's PDF report stored beside them.
Order
The clinician selects tests inside our clinical system.
Send
The request goes to the lab as an HL7 e-order. No paper form.
Collect
The patient attends a collection centre.
Receive
The result returns over HL7 and is matched to the patient automatically.
Structure
Each analyte is stored as its own value. The PDF sits alongside as the source report.
Acknowledge
The clinician marks the result as seen and an acknowledgement goes back to the lab.
What we want the Bloody Good Tests route to give you
You asked how quickly we can move, with a transition away from NewDoc planned for the end of the year.
A firm date, straight after a technical session.
We know the end of year target matters. The pathology route and the data contract decide the build, so we'll commit to a go-live date as soon as we have scoped both with your team. We can start this week.
- This week
Technical session
Your engineers and ours. Request system, lab connections, data and event contract.
- Next
Scope and commercials
Agree the interface, the follow-up model and the pathology route. We confirm the go-live date here.
- Then
Build and integration test
Mapping, build and end to end testing in a staging environment.
- Then
Clinical review and UAT
Our clinical team signs off the asynchronous protocol. Your team tests the member journey.
- Go-live
Members move across
Requests switch to My Digital Health on the agreed date.
For context
Who you'd be working with.
~100
AHPRA-registered nurse practitioners, working nationally
450,000
unique patients across the group
10,000
patients seen each week
QIP
accredited health service
Let's find a time this week.
You suggested another conversation later this week, and that suits us. Send through two times that work and we'll bring the right people from our clinical and technical teams.
Christopher O'Donnell
CEO, My Digital Health
with Tim Irving