Skip to main content

September 2026: Share a result with any doctor, by link

The headline this month is shareable result links: a patient can now show their results to any doctor, whether or not that doctor has ever heard of us.

Sharing a result used to require the recipient to already be an organisation on the platform. That works for a clinic you found through us, and not at all for the GP you have seen for fifteen years.

From Shared results, Share now offers two paths: share with a clinic (the existing flow, unchanged) or create a link. A link gives the recipient a clean, read-only page with no account and no sign-up.

  • Pick exactly what to share, biomarker by biomarker.
  • A link plus a 6-character access code, so the two can travel separately.
  • Any expiry from 1 to 30 days. There is no "forever" option.
  • Revoke whenever you like, including for someone who has the page open.
  • Decide what identifies you. Name, date of birth and sex are three separate choices.
  • Email it, with the access code included only if you tick the box.

Your Shared results page keeps the history: every link, its access code, who it was emailed to, and every attempt to open it. If somebody guesses repeatedly at a code, the link locks itself and then disables itself permanently, and we email you when it happens.

Deleting a result you uploaded also kills any links to it.

Add and edit clients​

You can now add a client and correct their details from the Clients section, instead of waiting for them to arrive through an order. Both sit behind the existing Edit clients permission, which you manage through Roles & Permissions.

For developers​

A busy month for integrations. The full detail, field by field, is in the API changelog.

Manage webhooks over the API​

You can now create, list, update and delete webhooks with /v1/webhooks, and list the events you can subscribe to with GET /v1/webhook-events, so an integration no longer needs someone to set its webhooks up in the portal. Webhooks created either way are the same webhooks. Saving one is also checked now, in the portal and over the API: the URL must use https and must not point at a private address, and an event can be sent to a given URL by only one of your webhooks, so nothing is delivered twice. And when a webhook is created, re-pointed or deleted over the API, your owners and webhook managers get an email saying so. See Webhooks.

Medicare provider records over the API​

Register a doctor's provider number, referral details and signature against your organisation with /v1/providers, without the doctor needing an account with us, and request that their results route back to you. Records created this way show up in Settings > Result routing alongside your practitioners' own. See Providers.

A directory of collection centres​

GET /v1/collection-centres returns about 5,900 collection centres across Australia, with opening hours, so you can show a patient where to go once a referral is ordered. Search near a location or within a map viewport, and subscribe to collection_centres.updated to hear when the list changes. See Collection Centres.

More on every test​

GET /v1/tests now says which tests can be ordered under Medicare (medicareListed), can include the biomarkers each test is expected to report, and carries the price in cents (priceCents) so you are not doing arithmetic on dollars.

Developer MCP server​

There is now a developer MCP server at https://mcp.staging.eirly.health/dev/v1. Point your AI coding assistant at it and it answers from our real API contract: endpoints, request and response shapes, error codes and webhook events. It holds no patient or customer data. See MCP to connect one.

Also for integrations​

  • referral.issued arrives immediately, rather than up to a minute after the referral is issued.
  • Paging works the same on every list endpoint, and a bad paging parameter now tells you what is wrong. See Pagination.
  • Pathology provider ids use one spelling everywhere, for example douglass-hanly-moir, including on results.
  • The Swagger documentation now lets you pick the API version to try, and describes what each endpoint actually returns.

Coming soon​

  • Ordering for your clients. An Orders section for building an order on behalf of a client and tracking it through to results, with favourites for the tests you reach for constantly.
  • Organisation subscriptions. A Subscription tab in Settings, with its own card and 30 days notice on cancellation.

Smaller fixes​

  • The assistant can now link you to the documentation when it answers, and its panel can be resized by dragging the divider.
  • An Administrator can no longer remove, demote or grant Owner.
  • The Shared with me page has moved onto the same list framework as the rest of the portal, with the same search, filtering and sorting.
  • The API now refuses an ambiguous client identifier rather than guessing which client you meant.
  • When a webhook can't be saved, the portal now says why (for example, that the URL must use https) instead of a generic error.
  • Buying a test with an email address that already has an account no longer changes that account's details.
  • A few API referral lookups that could fail on older records now return them.

Questions? Reach out to our team at support@eirly.health.