NDIS Medication Management Requirements: What Providers Must Hold

Providers ask this question in two directions at once. Some want to know the minimum they can get away with. Others want to know if there is a single named course that, once completed, closes the file. Neither question has a clean answer, because the NDIS framework is built around risk and role, not a fixed checklist.

Who it applies to

In short: any registered provider whose workers assist with or administer medication, for any person, at any level of risk. The obligation scales with what the worker actually does.

If a worker's role touches medication in any way, from reminding someone it is time to take a tablet through to administering an injection, the provider carries the obligation. It does not matter whether the provider calls itself a medication provider or sees medication support as incidental to the main service. The moment a worker's duties include a medication task, the Practice Standards obligation switches on for that worker.

• Providers delivering Supported Independent Living, where medication support is a daily task for most workers
• Providers delivering community access or in-home support, where medication assistance happens occasionally rather than as a core function
• Providers delivering high intensity supports, where medication administration by a clinical route is part of the registered service

Scale does not exempt a provider either. A sole trader supporting one person with a daily tablet carries the same documented-competency obligation as a large provider running a 24/7 house.

The legal anchor

In short: the obligation sits in the NDIS Practice Standards, Core Module, Support Provision Environment. It requires systems for safe, person-centred medication support, not a named course.

The Practice Standards do not list a medication course by name. What they set is a standard: workers must be competent for the supports they deliver, and the provider must have systems in place to make that true. For medication, those systems mean organisational policy, a current care plan or medication chart for each person, documentation of every medication event, and secure, appropriate storage. None of that exists because a worker once sat through an induction video. It exists because a provider built it and keeps it current.

What "required" actually means

In short: a documented decision about what training each worker needs, evidence it happened, and a system to prove it on demand. Five things, held together, not five separate projects.

Strip away the compliance language and the requirement is a short list. A provider needs all five of the following, for every worker who touches medication:

• A written medication policy that says what workers in each role may and may not do
• A documented decision about what training each worker needs, matched to the medication tasks in their actual role
• Evidence the training happened, who delivered it, and when
• Competency sign-off for any task that carries clinical risk, by someone qualified to give it
• A record of every medication event: given, refused, missed, or anything that did not go to plan

Two levels, one framework

In short: assistance and administration are not the same task and do not carry the same training requirement. Confusing the two is the most common provider mistake. See awareness versus administration, and which your workers actually need for the full breakdown.

Prompting someone to take a pre-packed dose is medication assistance. Giving an injection, or medication through a feeding tube, is medication administration by a clinical route. Both sit inside the same NDIS medication management framework, but they do not carry the same training requirement, and treating them as interchangeable is where the framework gets misapplied. A worker trained to assist is not automatically authorised to administer, no matter how long they have worked with a person or how confident they feel.

The high intensity trigger

In short: subcutaneous injections and medication via an enteral feeding tube sit inside the High Intensity Daily Personal Activities framework. Training must be competency-based, delivered by an appropriately qualified health practitioner, and completed before the worker provides the support.

Once a medication task crosses into a clinical route, the general Practice Standards obligation is joined by a more specific one. The high intensity framework requires:

• Training that is competency-based, not knowledge-based. Finishing an online module does not satisfy this on its own
• Delivery by an appropriately qualified health practitioner, matched to the specific support
• Completion before the worker provides the support, not during a trial shift or "as soon as we can arrange it"
• Reassessment at least annually, when the person's needs or plan change, and after a gap of three months or more without providing that support

The full detail on what counts, who can deliver it, and the required-versus-recommended distinction in the Commission's own wording is in CORA's high intensity supports knowledge base.

Competency is the real test

In short: a completion certificate shows a worker finished a module. It does not show they would recognise a wrong dose in front of them. That gap is where real risk sits, and it is covered in depth in medication competency for support workers.

Every part of this framework, policy, training, sign-off, documentation, exists to answer one question: can this worker actually do the task safely, not just attend a session about it. A provider that treats "the worker did the course" as the end of the obligation has stopped one step short. Who decides a worker is competent, what a course can and cannot establish, and what that leaves for the provider to do in person, is its own question and deserves its own answer rather than a paragraph here.

What an auditor checks

In short: auditors cross-reference medication incident records against training files, looking for training matched to the actual role, sign-offs for high-intensity tasks, and a documented refresh cycle.

When an auditor reviews medication management, they are rarely looking at one document. They are checking that several things agree with each other:

• Training records match the medication tasks each worker actually performs, not a generic induction everyone did on day one
• Competency sign-offs exist for every worker doing high-intensity administration, naming who delivered and confirmed it
• Medication incident records, including refusals and missed doses, are contemporaneous and complete
• There is a documented refresh cycle, and someone can explain why that interval was chosen
• The organisational medication policy is current and matches what workers describe doing on shift

Common gaps

In short: generic training not matched to role, records spread across folders and inboxes, and a plan change that never triggered a training review. All three are fixable with one system rather than five habits.

The same three gaps turn up at almost every provider that gets caught out. Training that is generic rather than tied to the medication tasks a worker actually performs, so a worker administering insulin holds the same certificate as a worker who only ever prompts a pre-packed dose. Records that cannot be produced quickly, scattered across folders, inboxes and a spreadsheet nobody has opened in months. And training that never gets refreshed when something changes, a new medication, a reviewed plan, a worker who has not done the task in months. Build a trigger so a plan change starts a training review automatically, rather than relying on someone remembering.

Sources and further reading

• NDIS Practice Standards, NDIS Quality and Safeguards Commission
• High intensity daily personal activities: supplementary module and skills descriptors, NDIS Quality and Safeguards Commission
• Medication administration training in the NDIS: required vs best practice, CORA
• NDIS medication administration course: awareness versus administration, CORA
• Medication competency for support workers, CORA
• High intensity supports knowledge base, CORA

This guide is general information for NDIS providers, not legal or clinical compliance advice. Always verify current requirements directly with the NDIS Quality and Safeguards Commission, as the detail does change.