Summarize with:
IRB workflow management at an academic medical center (AMC) means coordinating Institutional Review Board (IRB) review with the reviews that run alongside it: privacy, conflict of interest, radiation safety, biosafety, pharmacy and billing. All of that happens under both Common Rule and FDA requirements. The IRB decision is one step. Study activation depends on every parallel review closing, and on someone seeing which one has not. This post covers where those handoffs break and how to design a workflow that keeps them visible.
Key takeaways
- AMC IRBs carry pressures many university IRBs do not: FDA-regulated trials, HIPAA decisions, sponsor timelines and a long list of ancillary reviews.
- Most delays happen between reviews, not inside them. Ancillary reviews running in separate systems are the usual cause.
- Design each stage around an owner, an input, a system action, a handoff and a known failure mode.
- Leadership needs time-to-activation and ancillary review aging, not just IRB turnaround.
Why Is IRB Work at Academic Medical Centers Different?
A university IRB reviewing social and behavioral studies works mainly under the Common Rule 45 CFR 46 An AMC IRB reviews a large share of clinical investigations under FDA regulations as well (21 CFR 50 and 56). The two frameworks differ in places. FDA-regulated studies, for example, still require continuing review at least once a year (21 CFR 56.109(f)), while many minimal risk Common Rule studies no longer do.
Privacy adds another layer. When researchers need protected health information without each patient's authorization, an IRB or privacy board must approve a waiver or alteration of authorization under the HIPAA Privacy Rule 45 CFR 164.512(i) Many AMC IRBs serve as the privacy board, so that determination sits inside IRB review.
Then there is single IRB reliance. Federally funded cooperative research generally uses a single IRB of record (45 CFR 46.114(b)), and the NIH single IRB policy applies to NIH-funded multi-site studies. An AMC may be the reviewing IRB for its own investigator-initiated trials and the relying site for an industry or network study in the same week. As a relying site, the institution still owns local context review, ancillary reviews and the decision to activate.
These problems show up in offices running older electronic IRB systems as often as in offices still on paper. The common factor is status scattered across systems that do not exchange information.
How Should an Academic Medical Center Design Its IRB Workflow?
An academic medical center IRB workflow holds up when each stage has a named owner, defined inputs, a clear system action, a handoff and a known failure mode. The six stages that matter most are intake, ancillary reviews, privacy determination, IRB review, activation and ongoing review.
A workflow that holds up at AMC volume gives every stage a clear owner and a defined handoff. The table below is a starting framework to adapt to your own standard operating procedures.
The IRB rarely loses track of its own review. Problems appear at the edges, and each carries a cost to the institution.
- Ancillary reviews run in separate systems. Each IRB ancillary review, from radiation safety and pharmacy to nursing and coverage analysis, is tracked somewhere else. Study teams chase status by email, and activation slips while every individual review looks on time.
- Conflict of interest disclosures are not tied to the protocol. When a disclosure changes mid-study, the IRB may not learn of it until the next continuing review, which leaves a management plan gap.
- Amendments outpace ancillary sign-off. The IRB approves a protocol change, but the pharmacy or radiation safety review of the same change is still open. The study team may not know the amendment cannot be implemented yet.
- Reliance status lives in a spreadsheet. Staff cannot answer quickly which studies the institution relies on another IRB for, or whether local requirements were met before activation.
- Biosafety review starts late. Human gene transfer studies need Institutional Biosafety Committee (IBC) review under the NIH Guidelines. When the IBC learns of a study only after IRB submission, it becomes the longest pole.
For reliance studies, add a branch at intake. The reviewing IRB's determination is recorded, local context and ancillary reviews still run, and activation waits on both.
Keeping Study Teams Informed
At an AMC, study coordinators and investigators feel workflow problems first. When they cannot see where a submission stands, they call or email the IRB office, and each inquiry takes coordinator time away from pre-review. Better communication with study teams is a workload measure as much as a service measure.
Show status at the level the team needs. A study coordinator wants to know which reviews are complete, which are open, who holds each one and what is needed from the team. A single "under review" status answers none of those questions.
Make requests for modification specific. When the IRB or an ancillary committee returns a submission, the request should name the document, the section and the change required. Vague requests lead to a second round of revisions and a longer cycle.
Tell teams what can and cannot proceed. After an amendment is approved by the IRB, the team needs to know whether pharmacy, radiation safety or another ancillary review still has to sign off before the change can be implemented. Clear status prevents changes from being implemented early by mistake.
Give sponsors a predictable answer. Industry sponsors and contract research organizations ask for activation timelines. When the office can see every open review in one place, it can give a realistic date and explain what is holding the study, which supports the institution's standing as a trial site.
Offices that invest here usually see fewer inbound status inquiries and fewer resubmissions. Both free staff time without adding headcount.
What Leadership Needs to See
IRB turnaround alone tells an Institutional Official (IO) little about how the clinical research enterprise is performing. At AMC scale, the more useful measures are:
- Time from submission to activation, split into IRB time and ancillary time
- Ancillary reviews open longer than a set threshold, by committee
- Reliance studies by status: agreement pending, local review pending, active
- Amendments approved by the IRB but still awaiting ancillary sign-off
- Continuing reviews and FDA-required annual reviews due in the next 60 days
These measures give leadership a view of where to add staff, where to change a policy and where to have a conversation with an ancillary office.
Evaluating IRB Systems for a Medical Center
Whether you are replacing hospital IRB software or extending what you have, judge it against the workflow you actually run.
- Ancillary review routing. Can reviews open automatically from study attributes, run in parallel and show status in one place?
- Dual regulatory tracking. Can the system hold Common Rule and FDA review schedules side by side for the same office?
- Reliance support. Can staff record reviewing IRB determinations and track local requirements for relying studies?
- Integration. What exchanges data with your clinical trial management system (CTMS), electronic health record or conflict of interest process, and what is a manual step? Confirm this before selection. Integration gaps are not something to resolve during implementation.
- Configuration ownership. Can your staff adjust forms and routing as policy changes, or does each change need a vendor request?
To compare vendors fairly, send each one the same two or three realistic study scenarios in advance and ask for a scripted demonstration against them. For the criteria that matter most, a sandbox or proof-of-concept phase tells you more than any presentation.
Where Key Solutions Fits
The Human Subjects (IRB) module in eProtocol by Key Solutions supports human subjects programs at medical centers, alongside Biosafety (IBC) and Radiation Safety (RSC) for the related reviews many clinical studies require. Key Solutions also offers Conflict of Interest (eCOI) for disclosure management.
The system supports the process. The principal investigator remains responsible for the protocol, and the institution remains responsible for oversight of its human research protection program.
