What each system records
CEPROSS collects information on diseases included in the schedule approved by Royal Decree 1299/2006. PANOTRATSS collects certain non-traumatic conditions that are not in that schedule but are treated as occupational accidents under Article 156(2)(e) and (f) of the General Social Security Act.
They are not two names for the same database. The distinction reflects legal categories, not whether one disease is more important or deserves less preventive attention.
Who reports and what the company must do
Royal Decree 1299/2006 assigns preparation and processing of the occupational disease report to the entity providing cover for the contingency. The company must supply the requested information in its possession. Medical practitioners have channels for reporting suspected cases under that framework.
The company should not turn a suspicion into its own diagnosis. It does need to retain reliable information about tasks, exposures and preventive measures while respecting medical confidentiality.
Read a table without confusing units
Before comparing, check whether the table counts submitted reports, closed reports or cases, and which period it uses. An administrative record does not automatically represent a different person. Also review whether sick leave is involved and the classification variables.
Record the exact table title, update date and methodological notes. This avoids comparing a recent notification with a closure relating to a case that began in another period.
What the data can and cannot establish
Published data describe notifications within the system and its coverage. They do not directly measure all occupational exposure or all existing harm. An increase may require examining activity, covered population, recognition or recording changes before attributing it to deteriorating prevention.
Comparing sectors requires compatible denominators and equivalent categories. The official series warns of the CNAE classification change applied from January 2026; check that discontinuity before automatically constructing trends.
Turn information into prevention
Use statistics to formulate questions: which agents appear, which tasks might share exposure and which controls should be checked. Then test those questions against your organisation’s assessment, measurements and collective health surveillance.
Avoid ranking sites solely on a few cases. A small number can fluctuate substantially and does not demonstrate absence of risk. The useful outcome is an evidence-based preventive decision with responsibility and follow-up, rather than a ranking without context.
Hypothetical example: reviewing a sector trend
A team observes an increase in notifications associated with an agent in its sector. It first checks the period, coverage and classification. It then reviews tasks involving comparable exposure and consults aggregated health-surveillance results.
The information leads to checking an extraction system and updating the assessment. The team does not conclude that every worker is ill or that its site has the same incidence as the sector. Statistics serve as a signal for investigation.
