Aged Care Banning Order
A banning order stops a person from working in aged care. The Aged Care Quality and Safety Commission can issue a banning order against someone who poses a risk, and it keeps a public register of those orders. An Aged Care Banning Order check matches a worker against that register.
Where a credential confirms someone is cleared, this check does the opposite: it makes sure a worker isn't someone who has been banned from aged care work.
Who needs it
Workers in aged care settings — anyone involved in providing aged care services. It's usually run alongside a worker's other checks as part of building a complete picture of their compliance.
What Oho needs
There's no number to enter. The register carries no reference numbers, so this is the one check that matches on the person rather than on a card: Oho uses each worker's legal name, date of birth, and the location held on their record.
Name alone is a weak match on a national register — common names produce possible matches that a person then has to sift. Date of birth is what makes the match meaningful, so fill it in for anyone working in aged care even though nothing forces you to. See Spreadsheet columns if you're importing.
Before you start
Nothing to set up. The register is a public file that Oho downloads, with no login to provide. You can narrow which workers the source covers if only part of your workforce is in aged care.
How Oho verifies it
Oho downloads the Commission's register on the cadence you set in the Verification Sources tab and compares it against your workers' details. Weekly is the fastest cadence available: the Commission republishes the file at most a few times a week, and each download re-compares the whole register against every worker you've scoped in, so checking more often only repeats work. Because matching is on personal details rather than a reference number, Oho weighs how closely they line up: a strong match is flagged clearly, and a weaker or partial match is raised for a person to confirm before anything is acted on.
Reading the result
Every check resolves to one of these outcomes. Note that green means the opposite of what it means on a credential — here it means Oho found nothing:
| Status (as shown in the app) | Colour | What it means | API value |
|---|---|---|---|
| May engage | Green | No match — the worker isn't on a ban register. | MAY_ENGAGE |
| May not engage | Red | A match — the worker appears on a ban register. | MAY_NOT_ENGAGE |
| Under review | Yellow | A possible match, worth confirming it's the same person before relying on it. | REVIEW_REQUIRED |
| In progress | Grey | Still being checked. | IN_PROGRESS |
| Error | Grey | The register couldn't be reached; Oho will try again. | ERROR |
When it doesn't verify
| What you see | What it means | What to do |
|---|---|---|
| Under review — a possible match | Some of the worker's details line up with a banning order, but not enough to be certain it's them | Open the check and compare the details. Confirm it if it's the same person, dismiss it if it isn't |
| Under review on a worker with a common name | Name matched, but there was no date of birth to narrow it | Add the worker's date of birth and let the next run reassess |
| May not engage | A confirmed match — this person is on the register | Act on it. A confirmed match flags the worker as non-compliant automatically |
| Error | Oho couldn't download the register file | Nothing. Oho retries on the next run |
Renewals & monitoring
Nothing renews here — there's no card and no expiry. What matters is that the check keeps running: an order made against someone months into their employment only shows up because Oho re-reads the register on your schedule.
That makes the cadence the thing to get right. A worker who was clear at onboarding is only still known to be clear as often as you re-check — so weekly, the fastest setting, is also the one most tenants want. The history records one set of entries per scheduled scan, so it reads as a record of your cadence. The worker's profile keeps a history of every run, and a new match raises a notification rather than waiting to be found.
Related
- Ban Checks overview
- How monitoring works — why the repeat check is the one that matters
- Aged Care Quality and Safety Commission — Banning Orders Register