This page has closed.

This response was available until 17 December 2026. For a current copy, contact Christopher O'Donnell at My Digital Health.

My Digital Health Vively Prepared for Tim Veron and the Vively team · 17 November 2026

Five questions from Vively, answered.

Tim, thanks for the note. Here is where we stand on each point you raised, what we can commit to today, and what we'd like to settle together on a call this week.

  1. 01Cost per request$20 per asynchronous request
  2. 02API documentationWalked through with your engineers
  3. 03GLP-1s and HRT$50 GLP-1 prescriptions, HRT, pharmacy delivery
  4. 04Pathology beyond SonicBloody Good Tests as the route
  5. 05How fast we can moveFirm date straight after discovery
1

You asked for the estimated cost per pathology request, and whether it includes follow-ups.

$20 per asynchronous request.

$20 per asynchronous pathology 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

Asynchronous pathology request$20
GLP-1 prescription$50
Medical certificate$20
Extended HRT consultationAvailable when a member needs onePriced by length
Who does the clinical work Nurse practitioners and doctors. Both prescribe and both request tests for your members.
On follow-ups When a result needs a clinician conversation, that becomes a consult. We'd like to agree with you how those are triggered and priced, so you can model them properly. It is first on our list for the call.
2

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

Data contractThe member and clinical fields we need to issue a request, and the result fields you need back.
Event contractRequest issued, sample collected, result available, follow-up needed.
SecurityCredentials, webhook signing and separate test and production environments.
OwnershipWho monitors, who supports, and how an incident is handed over.
3

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.

  1. Test

    Your member completes their baseline bloods through Vively.

  2. Consult

    A nurse practitioner or doctor assesses the member and prescribes where appropriate.

  3. Treat

    The eScript goes to pharmacy and medication is delivered to the door, cold chain included.

  4. Retest

    Follow-up bloods track progress and keep the member active in your app.

Where the revenue sits

MembershipYours. Testing, the app, coaching and the member relationship stay with Vively.
ClinicalGLP-1 prescriptions are $50. Extended HRT consultations are available when required and priced by length. Medical certificates are $20. You set the price your member pays.
MedicationScripts are filled through our Script2U pharmacy network with national delivery. We treat fulfilment as a margin opportunity for both sides.
For your revenue and LTV model GLP-1 and HRT behave differently on consult cadence and fill frequency. We can work through both with you on the call so the numbers in your model are ours, not estimates.
4

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.

Live today

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

In exploration

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.

  1. Order

    The clinician selects tests inside our clinical system.

  2. Send

    The request goes to the lab as an HL7 e-order. No paper form.

  3. Collect

    The patient attends a collection centre.

  4. Receive

    The result returns over HL7 and is matched to the patient automatically.

  5. Structure

    Each analyte is stored as its own value. The PDF sits alongside as the source report.

  6. 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

PricePrivate pathology at a cost that works inside a membership.
Structured dataResults passed through biomarker by biomarker, so your app can display them and run your analysis.
One flowA single ordering and results path for our nurse practitioners and doctors, with clinical acknowledgement built in.
What we'd like to see from you Your request system and your connections to Healius, 4Cyte and ACL. Seeing how results reach your app today lets us test this route against what you already have, and be straight with you about any gaps.
5

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.

  1. This week

    Technical session

    Your engineers and ours. Request system, lab connections, data and event contract.

  2. Next

    Scope and commercials

    Agree the interface, the follow-up model and the pathology route. We confirm the go-live date here.

  3. Then

    Build and integration test

    Mapping, build and end to end testing in a staging environment.

  4. Then

    Clinical review and UAT

    Our clinical team signs off the asynchronous protocol. Your team tests the member journey.

  5. 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