How do I manage Single Assessment System data and the eight Support at Home classification levels?

• The Single Assessment System (SAS) replaces earlier pathways (ACAT, RAS, CHSP assessment) as the single way older Australians enter the aged care system, including Support at Home.
• Every participant entering SAH is classified into one of eight ongoing classification levels, each associated with a published quarterly budget envelope.
• Providers must hold a current copy of the participant's support plan — the output of the assessment — and use it to inform care planning.
• When a participant's needs change materially, a reassessment must be triggered. Providers are not the assessors, but they are the party most likely to notice a change-of-condition in practice, so the responsibility to initiate reassessment sits with the provider in most cases.
• The classification level and support plan are official records and must be retained for the period specified in the Department's records retention framework.

Reference: Aged Care Act 2024 Chapter 2 (assessment framework and classification); Support at Home Program Manual — assessment and classification sections; Department of Health Single Assessment System guidance; Services Australia operational material for SAH budgets per classification level.

• Not capturing the support plan as structured data. It sits as a PDF in a folder, never drives care planning, and can't be queried when an assessor asks how service decisions relate to the assessed needs.
• Missing the reassessment trigger because no one is monitoring change-of-condition flags. A participant who's deteriorating is still on the same classification level months after their needs outgrew it.
• Treating classification as static. The classification is set when the participant enters the program and never reconciled against actual service delivery or observed change — so a participant whose function has improved stays on the same budget envelope as when they were more impaired.
• Not retaining a copy of the support plan locally. When an assessor asks to see the support plan, the provider has to go to the participant to retrieve it — which looks unprofessional and is a sign the operational workflow never digested the document.
• Treating the Single Assessment System as synonymous with My Aged Care. The SAS is the single assessment pathway; My Aged Care is the front door and gateway — they're related, not the same.

• Structured classification record per participant — level (1–8), effective date, assessed needs summary, linked support plan document, and reassessment schedule.
• Quarterly budget envelope derived automatically from the classification level, refreshed when the classification changes. The budget flows through to the quarterly budgets dashboard and the care management 10% cap calculation.
• Support plan storage with version history — when a reassessment produces a new support plan, the previous version is retained and the current version is surfaced in care planning workflows.
• Change-of-condition workflow — when a carer, Care Partner, or clinical review flags a material change, an action is created to initiate a reassessment request. The workflow tracks the request from initiation through to the updated assessment.
• Reassessment prompts driven by time since last assessment, change-of-condition flags, and upcoming schedule triggers. Nothing silently drifts past an overdue reassessment.
• Note: Statura consumes classification and support plan data but does not perform or submit assessments — those functions are the Department's. Where the Department opens a consumer-facing API for providers to receive assessment outputs directly, Statura will integrate with it. Today, classification data is entered or imported by the operator from the support plan document.

When an assessor asks for evidence on this obligation, here's what the platform produces on request — date-stamped, user-attributed, and exportable:

• Classification history per participant — every classification change with effective date, source document, and the operator who recorded it.
• Support plan version history with the document itself, the source (e.g. SAS assessment date), and the effective dates.
• Change-of-condition flag log showing who raised the flag, the observed change, the clinical context, and the action taken.
• Reassessment request log — when requested, by whom, what triggered it, what outcome was received, and how the classification updated.
• Budget envelope history showing how the quarterly budget changed as classification changed over time.