Concept

How the platform uses clinical protocols and standards

Where the clinical content in an encounter comes from, how its currency is shown, and what remains the pharmacist's responsibility.

This article explains where the clinical content in the platform comes from, how it is kept current, and what remains the pharmacist's responsibility. It applies to all clinical encounters and to the guidance provided alongside them.

Where the content comes from

The screening criteria, eligibility rules, medicines, doses, and referral guidance in an encounter are drawn from the protocols, practice standards, authorities, and clinical guidelines that apply to that service in each Australian jurisdiction. Because states and territories authorise and structure pharmacist services differently, content is configured separately for each jurisdiction, using that jurisdiction's own source documents and its own wording and order.

Some services rely on a single protocol; others rely on more than one document – for example, a legal authority together with a clinical guideline. Where more than one document applies, each is listed in the reference panel for that jurisdiction.

How currency is shown

The content reflects the source documents as at a point in time. It is not a live feed. Health departments, boards, and publishers update their protocols, standards, authorities, and guidelines from time to time, and there may be a period between a source being changed and the platform being updated to match.

To make currency visible, each topic in the reference panel shows:

  • the jurisdiction it applies to,
  • a Last reviewed date – when the content was last reviewed and configured, and
  • a Sources list linking to the protocols, standards, or guidelines the content is based on.

Together, these let a pharmacist see what the content is built from and when it was last checked, and decide whether to re-verify against anything more recent. The date is not a guarantee that a source has not since changed.

What the platform does – and does not – do

The platform prompts, references, and records. It surfaces the criteria a pharmacist needs to consider – including the eligibility and screening criteria set by the protocol – provides reference material alongside the encounter, and assembles a clinical record from what the pharmacist records.

It does not diagnose or prescribe, and it does not decide whether a patient is eligible. It presents the protocol's eligibility and screening criteria and records the pharmacist's assessment against them; the judgement – whether the patient is eligible, whether a condition is present, whether to supply or treat, and what to record – is the pharmacist's, made using their own professional judgement. Where the pharmacist records that a criterion is not met, the platform reflects the protocol's consequence (for example, that the patient is not eligible for the service) so it can be recorded – it does not make that determination itself, and it does not prevent the pharmacist from completing the record.

The pharmacist's responsibility

The content in the platform is a guide only. It supports the pharmacist's assessment; it does not replace it, the current published source documents, or the pharmacist's obligations under the legislation and standards that apply in their jurisdiction.

Before relying on the content for a consultation, the pharmacist should confirm it against the current published source. Where the platform and a current source document differ, the source document and the pharmacist's professional judgement prevail.

Authorities, practice standards, and protocols can change at any time, without warning or notice to software vendors. The content in Light may not reflect the most recent version at the time you use it. Always confirm against the current published source before you rely on it.

Telling us about changes or gaps

We keep this content under review, and pharmacist feedback is part of how we keep it accurate. If you notice that a source has been updated and the encounter has not yet caught up, or if there are additional fields, criteria, or supporting elements that would make the encounter more complete or more useful in practice, please let us know. Feedback of this kind helps us keep each jurisdiction's content current and fit for the way pharmacists actually work. In the meantime, the clinical note and file uploads can be used to attach or record any supporting clinical information the structured fields do not capture.

Summary

  • Clinical content is configured per jurisdiction, from that jurisdiction's own source documents.
  • It reflects those sources as at a point in time and is not updated live.
  • Each topic shows the jurisdiction it applies to, a Reference content updated date, and the sources it is based on, so currency can be judged.
  • The platform prompts, references, and records; it presents the protocol's eligibility and screening criteria but does not diagnose, prescribe, or decide eligibility, and does not prevent a lawful action from being recorded.
  • The pharmacist remains responsible for confirming against the current source and exercising clinical discretion.
  • Pharmacist feedback on updates, gaps, or additional fields is welcome and helps keep the content current.