Disability assessment records

Identifies individual disability assessment records - disability and functional capacity assessments, NDIS access requests, disability support pension impairment assessments and standardised functional assessment reports - when the phrase sits with populated person identifiers and assessment fields. Health and disability information under applicable privacy law.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: enforce tiers need a populated person identifier; 85 also needs an assessment field and allied-health or support evidence. Scheme guidance, provider brochures and policy text carry the phrases without a person record and stay at 65.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Privacy Act 1988 (Cth), NDB Scheme (Cth), National Disability Insurance Scheme Act 2013 (Cth), Information Privacy Act 2009 (Qld), GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: government-id, pii
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:disability\s+assessment(?:\s+(?:records?|reports?))?|functional\s+(?:capacity(?:\s+assessment)?|assessment)|NDIS\s+access\s+request|access\s+request\s+form|disability\s+support\s+pension\s+(?:claim|assessment)|impairment\s+(?:rating|tables?)|WHODAS|care\s+needs\s+assessment)\b

Corroborative evidence keywords

occupational therapist, physiotherapist, speech pathologist, activities of daily living, assistive technology, personal care

Proximity: 300 characters

Should match

FUNCTIONAL CAPACITY ASSESSMENT REPORT Participant name: Jordan Whitlock NDIS number: 430118274 Date of birth: 09/09/1979 Primary disability: Acquired brain injury Assessor: Priya Ramanathan, occupational therapist Assessment date: 18/08/2026 Findings: needs support with activities of daily living and assistive technology for mobility. — Populated functional capacity assessment with person, assessment fields and allied-health evidence (85)
NDIS access request - supporting evidence Name: Casey Rourke CRN: 204889137K Treating GP letter to follow. — Access request with labelled person identifiers only (75)
Care needs assessment - in-home support review Client number: CN-7720184 Preferred name: Alex Diagnosis: Multiple sclerosis (relapsing-remitting) Assessment tool: WHODAS 2.0 Score: 41 Physiotherapist recommends a mobility aid and home modifications to the bathroom. — Care needs assessment with client number, diagnosis, assessment tool, score and allied-health evidence (85)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
welfare registry — Generic word pair from old broad template should not match
Policy guidance: this procedure explains how disability assessment records are collected, stored and shared, who may access them and how long they are kept. Staff should read the privacy section before completing any form. It contains no details about any individual. — Policy/guidance text naming the topic without any populated record (65 discovery at most)
Functional capacity assessment Participant name: ____________________ NDIS number: ____________________ Primary disability: ____________________ Assessor: ____________________ Signature: ____________ Date: __/__/____ — Blank form with unpopulated labelled fields (placeholder guard keeps it below 75)
News: a new independent functional assessment model was trialled this year, with advocates warning that WHODAS scores alone cannot capture support needs for people with psychosocial disability. — News/training prose about the topic without a populated record (65 discovery at most)

Known false positives

Common words and phrases related to disability assessment records appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.