EU MDR GSPR 10: Biological Evaluation Pressure Points

Why GSPR 10 Creates Pressure

Under EU MDR, the biological evaluation is not reviewed in isolation. A notified body can read the BER beside the GSPR checklist, risk-management file, design dossier, chemical characterization, sterilization validation, labeling, and PMS signals. If those sections disagree, the biological evaluation may look weak even when testing was performed.

Pressure Points Notified Bodies Often Check

• Material rationale: why the selected material is suitable for the intended body contact and clinical use.
• Chemistry-to-risk link: whether extractables/leachables or composition data are interpreted in the biological evaluation.
• Risk management alignment: whether biological hazards and residual risks are reflected in ISO 14971 documentation.
• Change control: whether supplier, formulation, process, sterilization, or packaging changes trigger biological re-evaluation.
• CMR and endocrine-disruptor rationale: whether applicable substance concerns are addressed in the technical file, not buried in one appendix.

What a Strong File Should Show

• A GSPR 10 checklist that points to real evidence, not generic statements.
• A BER that explains why endpoint conclusions are supported by the finished-device evidence package.
• Chemical characterization and TRA conclusions that are traceable to risk-management decisions.
• A change-impact process that explains when biological re-evaluation is needed.
• Clear routing between BEP, BER, TRA, test reports, PMS/PMCF signals, and technical-file sections.

How to Audit the Cross-References

A practical GSPR 10 audit is a traceability exercise. Start with each biological safety claim in the GSPR checklist and ask where the supporting evidence lives. Then check whether the same claim is expressed consistently in the BER, risk-management file, chemical characterization summary, labeling rationale, and change-control records.

• If the GSPR checklist cites the BER, the BER should contain a clear endpoint conclusion, not only a list of tests.
• If the BER cites chemistry or TRA, the toxicological interpretation should be easy to find and should support the endpoint position being claimed.
• If risk management cites biological hazards, the residual-risk language should match the biological evaluation conclusion.
• If variants are grouped, the file should explain why the biological evidence applies across the grouped devices.

When GSPR 10 Becomes Commercially Urgent

This becomes high priority before notified-body submission, before responding to a biological safety question, before adding a new supplier or material variant, and before using one technical-file structure across multiple device families. In those moments, the risk is not only a weak paragraph. The risk is that several parts of the file disagree in a way that slows certification or remediation.

What Not to Hide in Appendices

Appendices are useful for evidence, but they should not carry the whole argument. If the notified body has to hunt through test reports, chemistry tables, risk files, and legacy rationales to understand the GSPR 10 position, the file is harder to review than it needs to be.

• Bring the conclusion forward: state what the biological evaluation concludes for the finished device and why.
• Use appendices as support: let reports and tables prove the claim, but do not make them the only place where the reasoning exists.
• Make exceptions visible: if a variant, supplier, material, or sterilization state has a limitation, explain it in the main file logic.
• Keep the risk file synchronized: the same biological concern should not be described differently in separate technical-file sections.

Best Next Step

For an EU MDR file, start by checking whether GSPR 10 evidence is traceable across the BER, chemical characterization, risk management, and change-control records. That targeted review usually finds the issues faster than rewriting the biological evaluation from scratch.