Skip to content
Assyro AI
Back to Glossary
General

BIMO(Bioresearch Monitoring)

BIMO is FDA's inspection program for the entities that generate research data, covering clinical investigators, sponsors, CROs, IRBs and nonclinical laboratories, and auditing study conduct and data integrity rather than manufacturing.

Usage Examples

  • FDA scheduled a BIMO inspection at our two highest-enrolling sites during the NDA review.
  • Get the trial master file inspection-ready now; BIMO will ask for it, not for the batch records.
  • The BIMO inspection of our GLP contract lab closed with no observations.

What is BIMO (Bioresearch Monitoring)?

BIMO is FDA's inspection program for the entities that generate research data, covering clinical investigators, sponsors, CROs, IRBs and nonclinical laboratories, and auditing study conduct and data integrity rather than manufacturing.

BIMO exists because FDA approves products on data it did not generate and cannot reproduce. A reviewer reading a pivotal trial report has no way to know from the report whether consent was actually obtained, whether the adverse event was actually recorded, or whether the toxicology numbers came from the animal they claim. BIMO is the agency going to look for itself.

BIMO covers the entities that produce that data: clinical investigators and their sites, sponsors, CROs and monitors, institutional review boards, nonclinical GLP laboratories, and in vivo bioequivalence facilities. BIMO does not cover manufacturing. A cGMP or pre-approval inspection of your drug substance plant is a separate program, run against separate compliance programs, with a separate failure mode. The two get confused constantly and prepared for jointly almost never.

BIMO inspections are tied to the data in a specific application, so the sites are chosen out of your own submission: highest enrollment, largest treatment effect, most protocol deviations, or a foreign site FDA has never seen. BIMO investigators then work backwards, asking for source documents and comparing them line by line against the case report forms and study reports you filed.

Not to be confused with

PAI (Pre-Approval Inspection)
a PAI examines the manufacturing site and the CMC data behind the application. BIMO examines the clinical and nonclinical study conduct behind the same application. One NDA can trigger both, run by different FDA programs on different timelines.
GCP
GCP is the standard the trial is held to. BIMO is the mechanism that checks whether you met it. You comply with GCP and ICH E6; you get inspected by BIMO.
Form 483
a 483 is a possible output, not the program. A BIMO inspection may close with no observations at all. Saying "we got a BIMO" when you mean "we got observations" confuses the event with its result.
A sponsor audit or CRO monitoring visit
those are quality activities you commissioned and control. A BIMO inspection is a regulatory action with statutory access rights, and you cannot scope it, schedule it away, or keep the findings internal.

BIMO has no single rule of its own. The obligations come from the part that governs whichever entity is being inspected.

What you must do

  1. 1Conduct and report nonclinical laboratory studies that support applications for research or marketing permits under good laboratory practice, because those studies are what BIMO audits21 CFR 58.1
  2. 2Permit an authorized FDA employee, at reasonable times and in a reasonable manner, to inspect the testing facility and to inspect and copy all records and specimens required to be maintained for studies within scope21 CFR 58.15(a)
  3. 3As a clinical investigator, permit an authorized FDA officer or employee to have access to, and copy and verify, any records or reports made in connection with the study21 CFR 312.68
  4. 4Keep IRB minutes detailed enough to show attendance, actions taken, the vote with numbers for, against and abstaining, the basis for requiring changes or disapproving research, and a written summary of controverted issues and their resolution21 CFR 56.115(a)(2)
  5. 5Retain IRB records for at least 3 years after completion of the research and keep them accessible for FDA inspection and copying21 CFR 56.115(b)

Common mistakes

  • Preparing the site and forgetting the sponsor

    teams rehearse the investigator site and leave the sponsor's own monitoring reports, deviation log, and vendor oversight file undocumented. Sponsor and CRO inspections are a separate leg of BIMO, and the sponsor is where systemic findings surface, because a sponsor finding implicates every site rather than one.

  • Over-reading the QA shield

    Part 58 exempts quality assurance unit records of findings and problems, and actions recommended and taken, from FDA's inspection and copying rights. That carve-out is narrow. Teams who stretch it to cover the entire QA file turn a legitimate scope argument into a refusal to permit inspection, which is a worse finding than anything inside the file.

  • Reconstructing source data while the investigator is on site

    BIMO compares source documents against what you submitted. Backfilling a binder mid-inspection converts a documentation observation into a data integrity finding, and data integrity is the one category that can put the application itself at risk rather than just the site.

When This Matters

  • FDA scheduled a BIMO inspection at our two highest-enrolling sites during the NDA review.
  • Get the trial master file inspection-ready now; BIMO will ask for it, not for the batch records.
  • The BIMO inspection of our GLP contract lab closed with no observations.

Frequently Asked Questions

BIMO inspects the entities that generate research data for an FDA application: clinical investigators and their sites, sponsors, CROs and monitors, institutional review boards, nonclinical GLP laboratories, and in vivo bioequivalence facilities. Manufacturing sites are inspected separately under cGMP programs, not under BIMO.

Related Use Cases

Related Regulatory Intelligence

Related Actions

Sources & References

Share this page
Agent CTA Background

Simplify Bioresearch Monitoring compliance