Skip to main content

Sonic Healthcare

AU

Laboratory integration with Sonic Healthcare, an Australian pathology network. wawa will send lab orders to Sonic and bring the results back onto the patient's record through the order they belong to. A result that matches no order sent from wawa, such as one for an order placed elsewhere, will wait in unmatched results for someone to link it.

What we need from you​

Arrange these with Sonic before setup. There is no Sonic software to install at your clinic: wawa connects to Sonic from its own servers.

InputWhat to give us
Sonic termsSonic's terms for the Fetch API, signed by your clinic
Fetch loginA Fetch API username and password that Sonic issue in your clinic's name, to a named practitioner
Lab codeThe code of the Sonic laboratory your clinic works with. Each laboratory has its own code.

wawa holds the client ID and client secret, so you do not need to request them.

Settings​

An account administrator configures the integration under Settings → Integrations → Sonic Healthcare.

The Configuration tab holds the Enable integration switch. While it is off, no data is exchanged with Sonic. Each station, added on the Stations tab, connects your clinic to one Sonic laboratory:

FieldWhat to enter
Service root addressThe address Sonic issued for your account. It can include a path prefix such as /api.
Fetch usernameThe username of the Fetch login Sonic issued for your clinic.
Fetch passwordThe password for that login.
Lab codeThe code of the Sonic laboratory your clinic works with.
Client IDThe application credential that identifies wawa to Sonic. Sonic issue it to wawa, not to your clinic.
Client secretThe secret that goes with the client ID.

The Fetch password and the client secret are stored encrypted and are never shown again. When you edit a station, leave either field blank to keep the stored value.

Click Test on a station to confirm wawa can reach Sonic and sign in with both the Fetch login and the client ID.

The Events tab lists the exchanges with Sonic, with the batch, the number of files and any error for each, and one row for each check for new results, saying how many were filed. File names and contents are left out, because they can identify a patient.

Results​

While the integration is enabled, wawa checks Sonic for new results every five minutes. It files each result, then confirms to Sonic that it has it, so Sonic do not send it again. A result is confirmed as soon as wawa has stored it, even before wawa can tell which patient it belongs to.

Sonic can also send a report as a PDF or PIT file on its own, outside an HL7 result. wawa keeps such a file and confirms it, but cannot file it automatically: it is marked as failed, for someone to file by hand.

Orders​

The clinician who signs a Sonic order is the one named to Sonic, or the person who requested it if nobody has signed it. Each of them needs a Medicare provider number on a claims provider record marked as a rendering provider. If they have several, wawa uses the one at the patient's clinic. An order wawa or Sonic cannot accept is marked as failed, with the reason shown on the order, so someone can fix it and send it again.

If the patient has a mobile number, Sonic text them a link to the referral to show at the collection centre.