TRV-2026-1528Certified recordPeer-reviewed

Development and internal validation of a machine learning model for work-related sick leave in Brazilian workers with mental disorders

Background: Mental disorders are a leading cause of work-related sick leave in Brazil, yet routinely collected surveillance data are seldom used to build prediction tools for occupational health services. We aimed to develop and internally validate machine learning models predicting work-related sick leave among individuals notified with work-related mental disorders. Methods: We analyzed 21,601 notifications of work-related mental disorder (ICD-10 F99) from Brazil's national surveillance system (SINAN, 2006-202…

Labor · The Trace — both readings · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

Models trained on routine national surveillance notifications gave moderate-discrimination prediction of sick leave, with positive net benefit across roughly 30-70% decision thresholds.

Current reading — problem

The champion model discriminated markedly worse for Black workers and workers with secondary education, so deployment would need recalibration and fairness auditing.

What this doesn’t fix

Only internal validation was performed, so the model is not ready for deployment and needs external, prospective validation, plus recalibration and fairness auditing for disadvantaged subgroups.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1528, v1: “Development and internal validation of a machine learning model for work-related sick leave in Brazilian workers with mental disorders.” Truvace, 2026-10-16. /record/TRV-2026-1528 (accessed at citation time). sha256 5966b6b792b5b7dc…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv15966b6b792b5…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1528 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.