Biological Evaluation Report (BER) Service
ISO 10993 report support for teams that need endpoint-by-endpoint conclusions, literature and existing-data assessment, chemistry integration, and a clearer scientific narrative for FDA and EU MDR review.
Evidence Synthesis
Literature, existing test data, chemistry, and device context brought together into one coherent report.
Endpoint Conclusions
Clear assessment of which endpoints are addressed, waived, unresolved, or still require more evidence.
Chemistry Integration
Chemical characterization and TRA logic connected back into the biological safety argument.
Residual-Risk Framing
Conclusions written in a form that supports the technical file, FDA summary, and risk-management narrative.
Best for teams that already have evidence, but need a defensible scientific conclusion
The BER is where the biological evaluation becomes reviewer-facing. It needs to explain what evidence exists, how strong it is, what it means for each endpoint, how chemistry fits in, what residual risks remain, and whether the file truly supports biological safety for the finished device.
Testing and Literature Already Exist
You have data, reports, or chemistry outputs, but the package still needs a clear scientific synthesis and endpoint conclusion.
Current BER Reads Too Generically
The draft does not explain device context, endpoint logic, or waiver basis clearly enough for external review.
Legacy BER Needs Updating
You need to reframe older documentation around current ISO 10993 expectations, lifecycle thinking, and benefit-risk language.
Reviewer Asked for Clarification
The evidence may exist, but the conclusions, endpoint treatment, or chemistry framing are not convincing in the current file.
What a strong BER actually needs to do
A BER should not just repeat test results. It needs to evaluate the evidence and explain why the overall biological safety conclusion is defensible.
Finished-Device Framing
The report describes the real patient-contacting device, not an abstract material list disconnected from manufacturing and use.
Evidence Appraisal
Literature, prior test data, chemistry, and equivalence claims are examined for relevance, quality, and limitations.
Endpoint-by-Endpoint Conclusions
Each biological endpoint is addressed clearly, including what evidence supports it and where the reasoning is strongest or weakest.
Waiver and Existing-Data Logic
Endpoints not supported by new testing are backed with explicit scientific reasoning rather than generic statements.
Chemistry and Toxicology Integration
When chemical characterization or TRA exists, the report explains how that chemistry changes the biological safety conclusion.
Residual Risk and Benefit-Risk
The final narrative explains the remaining uncertainty and whether the evidence package supports acceptable biological safety.
Situations where BER quality usually decides reviewer confidence
These are the cases where the report itself often becomes the main issue, not just the data in the appendix.
EU MDR technical-file submission
Where the notified body expects the biological safety story to be tied to the broader device documentation and Annex I context.
FDA 510(k) and AI response support
Where the reviewer needs endpoint conclusions and evidence framing that are much clearer than the current file provides.
Legacy BER remediation
Where old reports rely on outdated structure, weak literature framing, or poor linkage to current device configuration.
Files with scattered supporting data
Where the testing, chemistry, and literature may exist, but the report never brings them into one persuasive narrative.
Implants and prolonged-contact devices
Where endpoint interpretation, chemistry, and residual-risk reasoning usually need more depth than average.
Teams trying to defend waived endpoints
Where the file must show clearly why existing evidence is sufficient and where the real uncertainties still sit.
How a BER scope is usually structured
The work starts with the evidence you already have and ends with a report that tells a clearer scientific story.
Review the Available Evidence
Device description, test reports, chemistry data, literature references, and existing evaluations are reviewed together.
Assess the Endpoints
The available evidence is mapped against the relevant endpoints, with attention to device representation and evidence strength.
Draft the Report
The BER is written to explain the evidence, the gaps, the waiver logic, and the overall biological safety conclusion clearly.
Finalize the Reviewer-Facing Version
The final output is refined for the specific submission or remediation context so it is easier for a reviewer to follow and defend internally.
Questions teams usually ask before starting a BER
Can you work from an existing draft BER?
Yes. Many projects start with an existing draft that needs stronger endpoint logic, better chemistry integration, or clearer scientific writing.
Do you also review literature quality?
Yes. The literature itself is not enough; its relevance, limitations, and connection to the finished device need to be evaluated.
Can the BER include chemistry and TRA conclusions?
Yes. Where chemistry and toxicology are part of the biological safety argument, they should be integrated into the report rather than treated as detached appendices.
Can you update a BER for ISO 10993-1:2025 expectations?
Yes. That is a common use case, especially where lifecycle framing, benefit-risk language, and waiver quality are weak in the current file.
Need a BER that reads like real scientific evaluation?
Send the device type, current evidence package, regulatory pathway, and deadline. I will review the likely scope and tell you the most efficient next step.