Deceased-person records with cultural sensitivity

Identifies documents containing references to deceased-person records with cultural sensitivity in Australian contexts. This information type is classified as personally identifiable information under applicable data protection regulations.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Topic false positive

Jurisdictions

global

Regulations

HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), GDPR

Frameworks

ISO 27001, ISO 27701

Data categories

government-id, pii

Scope

wide

Risk rating

3

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:deceased\s+person|deceased\s+estate|death\s+record|cultural\s+sensitivity|Aboriginal\s+deceased|Torres\s+Strait\s+Islander|sorry\s+business|death\s+notification|next\s+of\s+kin)\b

Corroborative evidence keywords

deceased-person records with cultural sensitivity, deceased, person, records, cultural, sensitivity, personal, identity, demographics, address, age, birthday, citizenship, city, date of birth, [object Object], email, ethnicity, fax, first name (+42 more)

Proximity: 300 characters

Should match

• deceased person — Primary topic phrase match
• deceased estate — Case-insensitive topic phrase match
• death record — Alternative topic phrase match
• cultural sensitivity — Additional topic phrase match
• Aboriginal deceased record: restricted image under community cultural protocol. — Death record and explicit cultural restriction together (reaches the enforcing tiers)

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
• name disability — Generic word pair from old broad template should not match
• Deceased estate notice sent to next of kin. — Generic probate wording without cultural-sensitivity evidence stays discovery-only and must not enforce
• Cultural sensitivity training for customer service. — Culture wording without cultural-protocol evidence for a deceased record must not enforce

Known false positives

• Common words and phrases related to deceased-person records with cultural sensitivity 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.