Guardian and proxy consent support built into onboarding
QiXHealth profile
Aged Care
Supervised profileCapacity-aware AI governance for residential care, rest homes, and care coordinators supporting residents with complex consent needs.
Built for facilities where proxy consent, capacity concerns, and mandatory reporting obligations need to be built into the workflow from the start.
What this profile gives you
Default safeguards and workflow shaping for aged care teams.
Capacity concern flags before governed queries proceed
Mandatory reporting gates for elder abuse and unexplained injury signals
Full de-identification defaults for all resident-facing workflows
Roundtable review path available when capacity is in question
How the profile is shaped
The operational decisions this care-setting profile makes up front.
Each profile is designed to reduce setup ambiguity by carrying the most important care-setting assumptions into onboarding from the start.
Proxy and guardian consent
Residential care often involves family members or legal guardians as decision-makers. This profile supports that consent model from the intake step rather than treating it as an edge case.
Mandatory reporting gates
Gates are active for elder abuse indicators and unexplained injury signals. These reflect obligations under the Aged Care Act 2024 and equivalent NZ requirements.
Capacity assessment path
When a resident’s decision-making capacity is in question, the workflow flags this and offers a roundtable review rather than proceeding on assumption.
Coverage and fit
Where this profile is prepared to operate and what posture it assumes.
Jurisdiction coverage
- Australia (Aged Care Act 2024)
- New Zealand
Governance posture
Supervised by default
This is the starting mode attached during onboarding. It helps the clinic begin with a posture that matches the care setting before local admin adjustments are made later.
Open the preselected intake pathNext step
Start with the aged care intake path.
This preselects the care setting in Console so your clinic does not need to restate the same context during the first onboarding conversation.