QLD Health Clinical Incident or Patient Safety Report
Populated clinical incident and patient safety records from Queensland Hospital and Health Services: RiskMan and PRIME CI clinical incident notifications, patient safety incident reports, severity assessment code (SAC) ratings, sentinel event notifications, clinical reviews and root cause analysis (RCA) reports under the Hospital and Health Boards Act 2011 (Qld). They identify the patient harmed or at risk, the incident and its SAC or harm rating, and often the staff involved, contributing factors and open disclosure. Boundary: pharmacovigilance and trial adverse event reports belong to global-top500-339-adverse-event-reports; aged care SIRS notifications to au-aged-care-serious-incident-notification; NDIS reportable incidents to au-ndis-reportable-incident.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- Medium: clinical incident, RiskMan, PRIME CI and SAC wording is specific to health incident management, and enforce tiers need a populated patient field and a populated incident field. Root cause analysis and incident numbers also appear in IT and WHS reporting, which lack a patient field and stay at 65. Staff-only incidents without a patient are not covered.
- Jurisdictions
- au, au-qld
- Regulations
- Hospital and Health Boards Act 2011 (Qld), Information Privacy Act 2009 (Qld), Privacy Act 1988 (Cth), NDB Scheme (Cth)
- Frameworks
- ISO 27001, ISO 27701, QGISCF
- Data categories
- phi, health, pii
- Scope
- narrow
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?i)\b(?:clinical\s+incident(?:\s+(?:report|notification|record|form|review|analysis))?|patient\s+safety\s+(?:incident|event)(?:\s+report)?|RiskMan|PRIME\s+CI|sentinel\s+event|root\s+cause\s+analysis|severity\s+assessment\s+code)\b
Corroborative evidence keywords
SAC rating, incident number, contributing factors, open disclosure, clinical review, harm level
Proximity: 300 characters
Should match
RiskMan clinical incident notification Incident ID: 000000 Date of incident: 08/10/2026 Patient: Jordan Teston URN: 334102 SAC rating: 2 Summary: unwitnessed fall in ensuite, fractured left wrist Contributing factors: bed alarm not activated overnight; open disclosure completed with daughter.— 85 tier - RiskMan notification with incident ID, date, patient, SAC rating, contributing factors and open disclosurePatient safety incident report Incident number: CI-2026-000000 Patient name: Riley Teston Incident type: Medication error - insulin dose omitted Harm level: Minor Open disclosure completed 10/10/2026 by the nurse unit manager; findings referred to the medication safety committee.— 85 tier - patient safety incident report with incident number, patient, type, harm level and open disclosureClinical incident form Patient: Morgan Teston Incident date: 03/10/2026 Location of incident: Ward 4A— 75 tier - clinical incident form with patient, date and location only
Should not match
This guideline describes clinical incident management in Hospital and Health Services: notify in RiskMan within 24 hours, assign a severity assessment code, and commission a clinical review or root cause analysis for SAC 1 events.— Clinical incident management guideline (65 at most)Root cause analysis Incident number: INC0012345 Service: payroll API Impact: 40 minutes of failed batch jobs; contributing factors were an expired certificate and no alerting.— IT root cause analysis with incident number but no patient (65 at most)Clinical incident form Patient: ____________________ URN: ____________________ Incident date: __/__/____ SAC rating: ____ Description: ____________________— Blank clinical incident form (65 at most)Statewide clinical incident data: 312 SAC 1 incidents were reported in 2025-26, a 4 percent fall on the previous year.— Aggregate patient safety statistics (65 at most)
Known false positives
- Clinical incident management policies, RiskMan user guides and patient safety training. Mitigation: No populated patient or incident field, and guideline, policy, training and media framing is excluded from enforce tiers.
- IT, cyber and WHS root cause analyses and incident reports. Mitigation: They carry incident numbers but no patient field, so they stay at 65.
- Published patient safety statistics and annual reports. Mitigation: Aggregate figures carry no patient field and stay at 65.