Privacy and preparation
Injury reports, OSHA logs and workers' comp notes in operations records
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Injury reports, OSHA 300 logs and workers' comp notes should be excluded from a licensed manufacturing dataset by default, because each entry ties a worker to a health event. The useful safety signal usually lives elsewhere: hazard observations, near-miss reports, corrective actions and maintenance fixes, which can stay once names and medical details are removed.
Key takeaways
- The OSHA 300 Log, the privacy case list, 301 incident reports and workers' comp claim files are excluded whole, not redacted line by line.
- Injury details leak into CMMS work orders, shift logs, NCRs and email, so those systems need a search before export.
- If a record exists because someone got hurt, exclude it; if it exists because something needed fixing, transform it.
- The EHS manager is the best reviewer, because they know which incidents the whole floor remembers.
- Health-related details in operations records are assessed deal by deal with counsel.
Why are injury records a special case in plant data?#
Injury records are a special case because every entry links a specific worker to a body part, an injury type and often a treatment. In a plant where everyone knows everyone, a date, a shift, a department and a one-line description can identify the person even after the name is gone.
OSHA's own recordkeeping rules signal how sensitive these files are. Under 29 CFR 1904.33, employers save the OSHA 300 Log, the privacy case list if one exists, the annual summary and the 301 Incident Report forms for five years following the end of the calendar year the records cover. During that period, stored 300 Logs must be updated when new recordable cases are discovered or earlier cases change.
OSHA also builds privacy handling into the log itself. For certain sensitive injuries and illnesses, the recordkeeping rule has the employer write privacy case in place of the employee's name and keep the names on a separate, confidential privacy case list. That list exists precisely because some entries should never travel with the log, and it is the clearest signal that the whole set of safety files belongs outside a licensed package.
That combination makes the log a poor fit for a licensed package: it is personal, health-related and still moving. Exposure and medical records go further. OSHA's records-access standard requires medical records of employees exposed to toxic substances or harmful physical agents to be kept for at least the duration of employment plus 30 years, and those belong in the exclude column without exception.
Where do injury and claim details show up outside the safety files?#
Injury and claim details show up in maintenance, quality, HR and email systems, usually in free text written in a hurry at the end of a shift. The safety files are easy to find and exclude; the stray sentences are what slip into an export.
Search free-text fields for terms such as clinic, urgent care, stitches, first aid, restricted duty, light duty, lost time, claim number, adjuster and TPA before you scope any extract. Each hit tells you which record family needs a cleaning rule.
- CMMS work orders: a guard repair that notes the operator was sent to the clinic.
- Shift handover logs and supervisor notes kept in MES comments or shared spreadsheets.
- NCRs and CAPAs where a quality escape and a near-miss share a root cause.
- HR and leave systems: restricted duty, return-to-work notes and accommodation requests.
- Email with the workers' comp carrier or third-party administrator, including adjuster notes.
- Training records that show retraining after an incident, tied to an employee ID.
- Photos attached to incident reports or work orders that show people, badges or injuries.
Exclude or transform: a treatment table for safety records#
The treatment table below sorts safety records into those that leave the dataset entirely and those whose operational lesson can be kept after cleaning. Use it as the starting position for the conversation with counsel, not as the final answer.
A simple rule sits behind every row. If the record exists because someone got hurt, exclude it. If the record exists because a machine, a process or a layout needed fixing, transform it and keep the fix.
| Record or field | Default treatment | What can survive |
|---|---|---|
| OSHA 300 Log and annual summary | Exclude | Nothing at row level |
| Privacy case list | Exclude | Nothing |
| OSHA 301 Incident Report forms | Exclude | Nothing; the hazard lesson is captured from the investigation instead |
| Workers' comp claim files and adjuster notes | Exclude | Nothing |
| Exposure and medical records | Exclude | Nothing |
| Incident investigation and root cause | Transform | Hazard, cause category, corrective action, verification |
| Near-miss and hazard observation reports | Transform | Condition found, area type, fix, recurrence |
| Work orders that mention an injury | Transform | Equipment, failure mode, repair; injury sentence removed |
| Safety training completions | Exclude | Course catalog only, with no names |
What safety signal is worth keeping?#
The safety signal worth keeping is the chain from hazard to fix: what condition was found, what caused it, what changed and whether the change held. Developers building maintenance, quality and operations tools learn from that chain; they do not need to know who was hurt.
Rewrite incident narratives at the level of equipment and process. A note that an operator's hand contacted an unguarded chain drive on the packaging conveyor becomes a record of contact risk at an unguarded chain drive, the guard redesign, the interlock added and the follow-up audit result.
Remove the body part, injury type, treatment, clinic, days away and any job title held by one person. Coarsen the date to a month or quarter when an incident is well known on site, and drop shift references for small crews.
Illustrative: a metal fabricator separates safety from maintenance history#
Illustrative: a fictional metal fabricator runs Epicor for production, a CMMS for maintenance and a QMS for NCRs and CAPAs, and its EHS manager keeps the OSHA logs and 301 forms in a restricted folder. The owners want to license maintenance work orders and corrective action history.
A term search across work orders and NCR narratives finds injury mentions in press brake and saw repairs, plus forwarded threads with the comp carrier in the maintenance supervisor's mailbox. The team excludes the EHS folder and every carrier thread by sender domain, strips injury sentences from work orders and rewrites incident investigations as hazard, cause and fix records.
The EHS manager then reviews a sample and flags incidents that coworkers could identify from the date and machine alone. Those dates are generalized to the quarter. The final package keeps the repair and corrective action history intact, and the privacy record lists every excluded record family.
Who should review safety exclusions before release?#
The EHS manager, HR, counsel and the plant leader should all review safety exclusions, because each sees a different risk. The EHS manager knows which incidents are memorable, HR knows which leave and accommodation records touch health, and counsel weighs which state privacy, employment and health rules may apply.
Give reviewers a short sample, the search terms used and the treatment table, not the whole archive. Record their decisions so a later export follows the same rules.
- Confirm the excluded record families by name and system.
- Review a sample of transformed work orders and investigations.
- Check photos and attachments separately from text.
- Approve the date and shift generalization rules.
- Sign the exclusion list before any file leaves the plant.
| Reviewer | What they check | Typical catch |
|---|---|---|
| EHS manager | Incidents identifiable by date, machine or crew | A well-known accident hidden behind a coded work order |
| HR lead | Leave, accommodation and return-to-work references | Restricted duty notes in shift logs |
| Counsel | Which state privacy, employment and health rules may apply | Carrier correspondence left in a shared mailbox |
| Plant leader | Whether the remaining records still tell the maintenance story | Over-cleaning that strips the repair itself |
How SourceX handles safety and injury records#
SourceX treats injury, claim and medical records as an exclusion category in the Preparation step of the SourceX five-step transaction, after the Rights step has identified which record families are in scope. The supplier approves the final exclusion list in the Approval step, before anything moves to Delivery.
The privacy record in the SourceX Evidence Packet lists the excluded families, the search terms and the cleaning rules applied to free text. In the SourceX Enterprise Data Value Framework, privacy burden reduces net value, which is why removing injury files early rarely costs much: the value sits in the maintenance and quality chain, not the safety log.
Frequently asked questions
Can we license aggregate injury rates instead of the log itself?
Possibly, but aggregate rates add little for most AI developers and still need care. A small department or a rare injury type can point to one person even in summary form. If a buyer asks for safety metrics, counsel should review the level of aggregation before anything is shared.
Does removing the employee name make a 301 form safe to share?
Usually not. The narrative, date, time, department and description of what happened often identify the worker to coworkers and managers. The form also carries treatment details. Capture the hazard and the fix from the investigation record instead, and keep the form itself out of scope.
Are anonymous near-miss reports safe to include?
They are good candidates, but anonymous at submission does not mean anonymous in content. Check the free text for names of other workers, supervisors and contractors, and watch for small crews where the shift and area identify the reporter. Clean them with the same rules as work orders.
How do we keep workers' comp email out of an email archive license?
Filter by the carrier's and third-party administrator's sender domains, then search remaining mail for claim numbers, adjuster and return-to-work language. Exclude whole threads rather than individual messages, because forwards and replies repeat the medical details further down the thread.
Are injuries to contractors' workers treated differently?
Treat them the same way. A contractor's employee is still a person whose health details appear in your records, and your agreement with the contractor may add its own confidentiality terms. Exclude their incident files and clean their mentions in work orders with the same rules.
Sources
- 29 CFR 1904.33 requires employers to save the OSHA 300 Log, the privacy case list (if one exists), the annual summary, and the OSHA 301 Incident Report forms for five years following the end of the calendar year that the records cover; stored 300 Logs must be updated for newly discovered or changed cases during that period. Source
- 29 CFR 1910.1020 requires medical records of employees exposed to toxic substances or harmful physical agents to be preserved for at least the duration of employment plus 30 years, unless a specific OSHA standard provides a different period. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.