Compliance module
Biosafety review on machinery your coordinators already know
Electronic submission, committee review, amendments and renewals — with training records imported from your own systems and protocols linked to the proposals and awards they cover.
The failure this replaces
Biosafety is the committee that got left on paper.
Most institutions electronified human-subjects review first and animal care second. Biosafety, being smaller, is frequently still a form emailed to a chair, tracked in a shared calendar, and remembered by one person who has been doing it for eleven years.
It works until that person is on leave in the week a protocol expires, or until an auditor asks for the amendment history and the answer is a folder. The volume is lower than IRB; the consequences of a lapse are not.
What it does
Submission, review, and the record afterwards
The committee functions, all of them
Streamlyne IBC contains the user and committee functions needed to support an institution's biosafety review process — the same submission, review and determination machinery IRB and IACUC run on, rather than a cut-down version of it.
Training data from where it already lives
IBC uses Streamlyne's integrations with your own data stores to import relevant information, such as training records held in an LMS or data warehouse. A reviewer checks a completion status instead of asking for a certificate.
Protocols linked to the work they cover
The Streams function links a protocol to other documents — proposals, institutional proposals and awards. Biosafety approval and the funded project it applies to are one lookup apart.
Amendments and versions on one record
The approved protocol and its change history are the same record rather than two folders that disagree, which is the difference an auditor notices.
Renewals before they lapse
Renewals and impending expirations are tracked by the system. An expiring protocol is something the software knows about before the coordinator does.
Familiar to anyone who runs IRB or IACUC
A coordinator who has learned one of the three compliance modules already knows where things are in this one. That is the practical value of shared machinery, and it shows up in training time rather than in a feature list.
Why it is not a separate purchase
The third committee costs the least to add
IBC is the newest of the three compliance modules and the clearest illustration of why shared machinery matters. It is not a separate product with its own conventions — it is biosafety running on the submission, review and committee functions IRB and IACUC already use.
For an office that runs all three, the saving is not licence cost. It is that a coordinator learns one system, and that all three link to the proposals, institutional proposals and awards through the same Streams function.
- IBCBiosafety, the newest of the three
- IRBHuman-subjects protocols and continuing review
- IACUCSpecies, procedures and protocol exceptions
- COIFinancial disclosure, assigned per project
- Export controlActivity tracking wired into Negotiations
Questions
What a biosafety office asks
What is IBC software?
The system an Institutional Biosafety Committee uses to run its review: the investigator submits a protocol, the committee reviews it, and the record holds the determination, the amendments and the expiration date. As with IRB and IACUC, the job that matters is answering whether approval is current and covers what is actually being done — without a search.
How mature is the IBC module?
It is the most recent addition to the compliance suite, and we would rather say that than imply otherwise. What it inherits is not new: the user and committee functions come from the same machinery IRB and IACUC have been running on for years. Ask us directly about anything specific to your biosafety process and we will tell you whether it is built.
Can it pull our training records?
Yes. IBC uses Streamlyne's integrations with institutional data stores to import relevant information, including training data held in an LMS or data warehouse. It is the least glamorous integration in the system and the one committee members notice first.
How does it relate to IRB and IACUC?
Same submission, review and committee machinery; different subject matter. IACUC adds species, procedures and protocol exceptions for animal work; IRB carries the human-subjects criteria. IBC is biosafety on the same foundation. A coordinator moving between them is not learning a new system.
Can we run IBC without the other compliance modules?
Yes. Institutions usually start with whichever area is costing them the most time and add the others later, and because it is one codebase that is a configuration exercise rather than a second implementation.
Which interface does IBC use?
The compliance modules run in the classic Streamlyne interface today. You get the full protocol lifecycle on the same records as the rest of your research administration; you do not get the newer UI that pre-award has. If a modern interface for compliance is a requirement rather than a preference, raise it with us before you evaluate anything else.