Biological Evaluation Report (BER) for Medical Devices

What a Biological Evaluation Report Is—and Is Not

The Biological Evaluation Report, usually shortened to BER, records the evaluation of biological safety for a defined medical device configuration. Under the current ISO 10993-1:2025 framework, biological safety is evaluated within risk management. The BER therefore needs to show the reasoning from device-specific hazards and exposure through the available evidence to the remaining biological risks. It is not simply a bundle of laboratory reports.

The distinction matters. A passing cytotoxicity report answers a test-specific question. A chemical-characterization report identifies and, where needed, quantifies constituents under its study conditions. A toxicological risk assessment evaluates constituent exposure. The BER has the broader job of deciding how those inputs—and literature, clinical or post-market information, prior-device data, material knowledge, and any justified data gaps—support conclusions for the finished device as used.

A BER also does not replace the Biological Evaluation Plan. The plan defines the prospective strategy and evidence needs; the report evaluates what was actually obtained. If the device or evidence changed after the plan was approved, the BER should make that change visible rather than silently forcing the final package into the original strategy.

Freeze the Device Scope Before Evaluating the Evidence

The first practical step is a configuration snapshot. FDA states that it evaluates the whole device in its final finished form, including sterilization where applicable. A BER should therefore identify the exact model or family, patient-contacting components, joining materials, processing aids, cleaning, sterilization, packaging, shelf-life state, nature and duration of contact, and relevant variants. A raw-material trade name alone cannot establish that boundary.

For a device family, the report should explain which configuration each evidence item represents. The largest device is not automatically worst case for every question: one variant might maximize patient-contacting surface area, another might contain the highest additive loading, and another might receive the most challenging processing or sterilization exposure. If multiple representatives are needed, that is better documented explicitly than hidden behind one broad “worst-case” statement.

A Practical, Reviewer-Traceable BER Structure

There is no value in copying a standard into a long template. A useful structure instead lets a reviewer move from scope to evidence to conclusion without reconstructing the logic:

1. Scope and configuration: identify the device, variants, intended purpose, users, patient population, contact tissues, exposure duration, manufacturing state, sterilization, packaging and shelf-life assumptions covered by the report.
2. Biological-risk context: summarize the relevant biological hazards, foreseeable exposure routes, known material or process concerns, and links to the risk-management file. State the applicable regulatory pathway and the standards or guidance versions used.
3. Evidence inventory: list each test report, literature review, chemical study, toxicological assessment, clinical or post-market source, and comparison record with document number, revision, date and represented configuration.
4. Endpoint-by-endpoint evaluation: for every relevant biological effect, state the question, evidence relied upon, applicability and limitations, gap status, conclusion, and any related risk control. “Addressed” may mean direct testing, other existing evidence, or a justified rationale; it should not be used as a synonym for “tested.” FDA makes this distinction explicit in its endpoint tables.
5. Integrated conclusion and lifecycle actions: explain whether the combined evidence supports biological safety for the defined use, identify unresolved uncertainty, and state any controls, post-market monitoring, or change triggers needed to keep that conclusion valid.

Build an Evidence Map, Not a Test List

A compact working matrix can prevent important reasoning from disappearing between reports. Use one row per biological question and record at least six fields:

• Question: the endpoint or device-specific biological hazard being evaluated.
• Source: controlled report, literature record, chemistry dataset, TRA section, complaint trend, or other evidence identifier.
• Representativeness: which device configuration, lot, sterilization state and exposure scenario the evidence covers.
• Interpretation: what the evidence demonstrates and what it does not demonstrate.
• Gap or uncertainty: any missing analyte identification, protocol deviation, changed supplier, limited follow-up, or other boundary on the conclusion.
• Disposition: conclusion, additional evaluation, risk control, or documented rationale for why no further assessment is needed.

This map should point to controlled source documents rather than copy every result into the BER. For chemistry-driven conclusions, show the chain from the ISO 10993-18 chemical-characterization information to the ISO 10993-17 toxicological assessment, then to the endpoint and overall biological-risk conclusions. The chemistry-to-TRA-to-BER decision chain should remain visible rather than leaving the reviewer to integrate disconnected appendices.

Common Reviewer Failure Modes

The following patterns do not automatically mean a device is unsafe, but they commonly make the evaluation harder to verify:

• Configuration drift: the BER names the current device while key evidence represents an earlier formulation, supplier, coating, sterilization cycle, or shelf-life state.
• Unsupported family coverage: one test article is applied to all variants without comparing formulation, geometry, contact, processing, surface area and chemical exposure.
• Endpoint closure by assertion: a row says “not applicable” or “covered by literature” without a device-specific rationale and traceable sources.
• Orphaned chemistry or toxicology: extractables and leachables are reported, but unidentified compounds, exposure assumptions, analytical limitations, or toxicological conclusions are not carried into the BER.
• Data summary without critical appraisal: the report repeats a laboratory conclusion but does not address test-article relevance, extraction conditions, deviations, acceptance criteria or clinical relevance. FDA’s test-report resource illustrates the underlying information reviewers need to interpret submitted studies.
• File inconsistency: contact duration, device materials, sterilization, warnings or residual risks differ between the BER, BEP, risk-management file, labeling and other technical-documentation sections.
• An overbroad conclusion: evidence for one configuration is used to declare an entire platform “biocompatible” without stating the limits of that conclusion.

Hypothetical, Anonymized-Style Example: Mapping a Changed Catheter Adhesive

This is a fictionalized example using no client data; it is not a client outcome or a recommendation for any specific device. Assume a sterile, limited-contact delivery catheter receives a new adhesive supplier while the nominal adhesive chemistry remains the same. The BER should not merely say “same material.” It could identify the affected joint and patient-contact route; compare the old and new formulation specifications, impurities and processing; document whether the adhesive is directly or indirectly contacting; link the finished-device chemical comparison and any toxicological interpretation; and explain which prior biological tests remain representative.

The endpoint map might then retain some existing evidence, flag a chemistry uncertainty for resolution, and identify whether focused additional work is necessary. The conclusion would be limited to the named configurations and supplied evidence. It would not claim that every future adhesive, process or catheter variant is covered. This style of reasoning is consistent with FDA’s expectation that processing, sterilization or formulation comparisons provide enough detail for an independent assessment, as illustrated in its device-comparison documentation examples.

FDA and EU Framing Should Stay Visible

For an FDA submission, confirm the current recognized-standard status and any limitations rather than assuming that an ISO edition is accepted without qualification. FDA’s database currently lists ISO 10993-1:2025 with partial recognition; the supplementary information and transition details should be checked for the specific submission timing.

For EU technical documentation, the BER should be readily traceable to the relevant General Safety and Performance Requirements and risk-management evidence. The consolidated Regulation (EU) 2017/745 Annex I Section 10 addresses chemical, physical and biological properties, while Annex II requires clear, organized and unambiguous technical documentation. The same scientific evidence may support multiple markets, but the report should make the pathway-specific claims and cross-references explicit.

When You Need BER Drafting, Review, or Broader Remediation

If no coherent report exists and the controlled evidence is available, the BER drafting service is usually the direct route. If a report already exists and the question is whether its device scope, evidence mapping, endpoint logic and conclusions will withstand review, a BER review is more proportionate.

Sometimes the BER exposes upstream problems: an outdated BEP, incomplete chemistry, a TRA that uses the wrong exposure scenario, unresolved device-family coverage, or contradictions across the submission. Use the free BEP–BER evidence traceability diagnostic to locate plan-to-report breaks, then start with a submission gap review when the problem spans the wider file.