Medication management depends on accurate information and clear responsibilities at each handover. The care team needs to know the current order, what was administered, what changed and what still needs review. This guide focuses on the records and decisions your software should support. Guidance reviewed 25 September 2026.
Start with the clinical and jurisdictional requirements
The Commission’s safe and quality use of medicines guidance explains the role of systems supporting safe medicines use. Apply the Quality Standards relevant to your service and the person’s care needs.
The Department’s residential medication-management principles place controlled-medicine storage and handling within state and territory requirements. Do not treat a generic digital register as proof that every local requirement is met. Confirm procedures, authorised roles, witnessing, corrections and notifications for your jurisdiction.
Follow one medication change
In a software evaluation, use a fictional person whose medication has changed after a hospital visit. Review the new order alongside the earlier record, administration history and clinical notes.
Check how the team distinguishes active, held and ceased orders. Confirm who records the change, who reviews it and how the next person knows which instruction applies. Include allergies and adverse-reaction information in the review. Software records support clinical judgement; they do not establish that a medicine is appropriate.
Review controlled-drug transactions and discrepancies
Follow a controlled-drug movement through the register. Inspect the recorded quantity, balance, performer and witness information. Then introduce a fictional discrepancy and review the investigation and resolution steps.
Check how the workflow handles a correction, recount and any required external notification. Keep the distinction between recording that a notification occurred and actually submitting it. Confirm the evidence your organisation needs to retain.
Keep reconciliation and PRN review explicit
At a care transition, identify the sources used to reconcile the medication list and record discrepancies requiring follow-up. The reviewed list should be understandable to the people responsible for the next administration.
For an as-needed medicine, inspect how staff record the reason, administration and subsequent response under the approved clinical process. Agree who reviews repeated use or unresolved concerns. Do not assume that an alert replaces that responsibility.
Assess incidents against the reporting rules
A medication error or adverse reaction needs an appropriate clinical response and incident review. Serious harm alone is not the full legal definition of a SIRS reportable incident. Assess the applicable category, circumstances and priority using the Commission’s current SIRS guidance.
Preserve when the provider became aware. Where notification is required, follow the applicable deadline and external reporting process. A medication record or internal alert is not evidence that the Commission has been notified.
What Statura Care supports
The Medications module brings medication records, administration outcomes, adverse reactions and S8 transactions into the clinical workflow. The S8 workspace includes discrepancy review; the reconciliation form records pre-event and reconciled lists, discrepancies and notes.
These records give clinicians a shared basis for review. Do not treat a medication-count flag as the quarterly Quality Indicator calculation. Use your approved clinical medicines resources for interaction assessment; the inspected medication profile does not provide a connected interaction check.
Bring a fictional medication change and an S8 discrepancy to a tailored demonstration. Review the routine workflow and exceptions, then confirm roles, jurisdictional requirements and any retained pharmacy systems in the implementation scope.