There is a version of this scenario in almost every residential aged care facility. A medication incident occurs. It is documented. The MAR shows the administration. The progress note exists. And when the question arrives, whether it’s from a Commission reviewer, from a SIRS investigation, from a board risk conversation, the record cannot answer it.
Not because something was hidden. Because the system was never configured to answer the question being asked.
The question a reviewer asks is not whether medication was administered. It is whether the facility can reconstruct, from the system alone, the complete sequence of decisions that surrounded that administration. Who administered it. When the documentation decision was made relative to when the medication was given. Whether the S8 count was verified at the point of signing. Whether the chart was current or approaching expiry at the time. Whether the progress note was generated at the moment of administration or entered after the fact.
Each of those questions requires a different data point. A system that captures administration but not sequence, timing, count linkage, and documentation order cannot answer them. That is not a training failure. It is a configuration one.
What chain of custody actually means in a medication record
Chain of custody is a term borrowed from legal and forensic contexts. Its application to residential aged care medication governance is straightforward: for any given medication decision, the system should be able to show what was decided, by whom, at what point in the clinical sequence, with what supporting documentation, and in what order relative to the administration itself.
A system that records the outcome, such as medication given, nurse identifier, time, satisfies the administration standard. It does not satisfy the chain-of-custody standard. The gap between the two is where most facilities find their exposure, and it is almost always invisible until external scrutiny arrives.
The eight points where the record is most likely to break
The chain-of-custody gap tends to appear at predictable points across residential aged care facilities. These are not edge cases. They are routine medication governance functions that the system either captures or does not.
The first is progress note linkage. When a nurse administers a medication, the clinical record should reflect that decision at the same moment. If the progress note is a separate manual entry, the timing gap between administration and documentation becomes visible to a reviewer, and visible timing gaps are reviewable.
The second is S8 visibility. When a controlled substance is packed or unpacked, that action needs a timestamp and a staff identifier in the medication record itself. A separate register is not wrong. It is simply not sufficient when a reviewer is working from the medication record as the primary source.
The third is count display at signing. The current count of each S8 medication on hand should be visible to the nurse at the point of signing, without requiring a separate count or manual entry. If it is not, the record cannot confirm that count verification occurred at administration.
The fourth is chart currency. A medication chart grouped by clinical category, with expiry tracking visible before expiry occurs, gives clinical staff the information they need to act before a chart lapses. A chart that expires without a system prompt creates a documentation gap a reviewer will find.
The fifth is renewal governance. If the system permits a renewal to be initiated before the existing chart is approaching expiry, early renewals and duplicate orders can be created without a clinical trigger. The record then contains multiple active entries for the same medication, and the reviewer must determine which one governed the administration in question.
The sixth is pre-signing prevention. If the signing sheet allows an entry before the administration date has been reached, pre-signing is structurally possible. A system that allows pre-signing cannot confirm that documentation followed administration.
The seventh is created-time visibility. The time a medication entry was created, separately from the time it was administered, is the single most important data point for reconstructing documentation sequence. If the system cannot display created time separately, the reviewer cannot confirm the order of events from the record alone.
The eighth is integration. Partial coverage across these seven points does not produce a chain-of-custody record. It produces a record with gaps. And gaps are what reviewers find.
Three things worth checking this week
These are not system changes. They are checks that tell you where your current configuration stands.
First: Ask your clinical team to reconstruct the documentation sequence for an administration that occurred in the last 72 hours. Not the fact of administration – the sequence. When was the progress note created relative to when the medication was given? Can the system show that without manual cross-referencing?
Second: Confirm whether your system displays the created time for each medication entry separately from the administered time. If the answer requires checking with IT or your software contact, the answer is effectively no.
Third: Pull the last three S8 entries and confirm whether the system shows the count at signing, the pack or unpack action with a timestamp, and the staff identifier all from the medication record itself, without reference to a separate register. Any field that requires a separate lookup is a break in the chain.
What this means for facilities on Acredia
Acredia’s Medication Management module captures each of the chain-of-custody indicators natively. From automatic progress note generation at point of administration, to S8 pack and unpack visibility with timestamp and staff identifier, count display at signing, chart expiry tracking, pre-signing prevention, all the way to created-time display in the MAR.
Several of these capabilities were introduced or updated across the December 2025 and March 2026 releases. Facilities that implemented before those releases may have the module active but not all capabilities switched on. If you are unsure whether your current configuration reflects the full set, your Acredia helpdesk contact can confirm this in a single check.
A few questions answered
What is the difference between a medication administration record and a chain-of-custody record?
A MAR records that medication was administered, by whom, and when. A chain-of-custody record can additionally show the sequence of documentation decisions, the count verification at signing, the chart currency at the time of administration, and the linkage between administration and progress note. Most facilities have the first. Fewer have the second.
Does this apply to facilities that have not had a medication incident?
The chain-of-custody standard is not triggered by an incident. It is the standard a Commission reviewer applies to any medication governance assessment. Facilities without a recent incident are not exempt; they are simply less likely to have tested their system against it.
Is this a software problem or a configuration problem?
For some facilities it is a configuration problem: the capability exists in their current system but has not been activated. For others the capability is absent entirely. The distinction matters because the resolution pathway is different. A configuration gap can be closed without a system change. A structural gap cannot.
How does this relate to SIRS?
A medication incident that results in a SIRS notification places the medication record under formal review. The notification requires the facility to demonstrate governance of the event, including that the documentation at the time of the incident was complete and reconstructable. A system that records administration but not sequence, count, and documentation timing does not satisfy that standard.
Test your current position
The Medication Chain-of-Custody Scorecard tests all eight indicators against your current system configuration. It takes ten minutes. It will show you exactly where your documentation position holds and where it does not.
