Compliance module
Conflict of interest software for research institutions
Collect significant financial interests, assign project-based disclosures, run the review, and report on all of it, inside the same system that holds the proposal and the award the disclosure is about.
The failure this replaces
"Conflict-of-interest review that depended on who remembered to ask."
That is how NJIT described its process before Streamlyne, a $190M research enterprise where COI disclosure and review were, in their words, inconsistent and difficult to track. It isn't an unusual description. COI is the compliance function most often run on a spreadsheet, because nothing visibly breaks until an audit.
What it does
Disclosure, review, and the paper trail
Disclosure collection
Faculty, students and staff who design, conduct or report research keep their significant financial interests in one place and update them when something changes, instead of once a year from memory.
Project-based disclosure
Disclosures are assigned electronically against the specific project, so the record answers the question a sponsor asks: did this person disclose for this award?
Review workflow
Assignment, completion and review all happen inside the system. A committee sees what is outstanding without anyone keeping a spreadsheet of who has been chased.
Reporting
Compliance metrics come through Streamlyne Reporting, alongside every other module, so COI status appears next to the award it belongs to instead of in a separate report nobody runs.
Linked to the rest of the record
COI lives in the same system as the proposal, the award and the protocols, so the disclosure and the project it is about share a record.
Consistent against NIH and NSF expectations
NJIT assigns, completes and reviews project-based disclosures in the system, consistently against NIH and NSF guidelines. It replaced a process they described as inconsistent and difficult to track.
The product itself
What the screens look like
Disclosure collection
Project-based disclosure
Review workflow
Why not buy it separately
A disclosure is about a project
If the disclosure lives in a COI product and the project lives in your eRA system, somebody at your institution is reconciling the two by hand, usually at the worst possible moment, which is when a sponsor asks.
In Streamlyne, COI is one of twelve modules in a single codebase. The disclosure, the proposal, the award and the protocols share a record. Nobody re-enters anything, and nothing drifts apart.
- IRBHuman-subjects protocols, amendments, continuing review
- IACUCAnimal care and use protocols
- IBCBiosafety, on the same committee machinery
- COIFinancial disclosure for faculty, students and staff
- Export controlActivity tracking wired into Negotiations
Questions
What procurement and the COI committee both ask
What is conflict of interest software in research administration?
The system that collects financial interest disclosures from everyone involved in designing, conducting or reporting research, routes them for institutional review, records the determination, and reports on all of it. The question it has to answer on demand is whether, for this award, right now, every required disclosure is in place and reviewed.
Do we need a standalone COI system?
You need the function. We don't think it should be a separate product. A disclosure is about a project, and if the disclosure lives in one system and the project in another, somebody is reconciling the two by hand. Streamlyne's COI module is part of the same system as the proposal and the award.
Does it handle project-based disclosure, or only annual?
Project-based. Disclosures are assigned electronically against the specific project, then completed and reviewed in the system. Annual disclosure is the easier half. Per-project is where manual processes usually break down.
How does this relate to the other compliance modules?
IRB, IACUC and IBC share the same submission, review and committee machinery, and COI sits alongside them with export control. A coordinator who learns one already knows the shape of the next, and protocols link to the proposals, institutional proposals and awards they belong to.
Can we start with COI alone?
Yes. Institutions commonly begin with whichever module is costing them the most time and add the rest later. Because it is one codebase, adding another module afterwards is configuration work, with no second implementation.
Does Streamlyne check disclosures automatically?
No. Automated disclosure checking is not a shipping capability, and we won't claim it is. What the system does is make the process consistent, assigned, tracked and reportable, which is what was failing when institutions describe COI review as depending on who remembered to ask.