The Cancer Trials Support Unit (CTSU) is a National Cancer Institute (NCI) service, launched in 1999, that centralizes the regulatory, credentialing, and enrollment infrastructure for NCI-sponsored cooperative-group cancer trials. Rather than each site negotiating separate regulatory paperwork and enrollment procedures with every cooperative group it works with, CTSU gives sites a single point of access for protocol registration, regulatory document submission, IRB-of-record coordination, and — increasingly — the coverage-analysis and billing-compliance resources that determine how a trial’s costs get billed correctly to Medicare, other insurers, and the trial sponsor. This guide covers what CTSU does, how it fits into the National Clinical Trials Network (NCTN), how it centralizes regulatory documentation and IRB reliance, and what it offers research coordinators and billing/finance staff for coverage-analysis and billing-compliance work.
For the clinical-trial-design side of oncology trials — endpoints like RECIST, and how the NCTN’s cooperative-group structure organizes trial conduct — see What Makes Oncology Clinical Trials Different: RECIST, Endpoints, and the NCTN. This guide instead covers the operational and administrative infrastructure that sits underneath those trials: how a site gets registered, credentialed, and connected to the correct IRB of record, and how it accesses the billing-compliance tools that reduce a site’s exposure to the kind of Medicare double-billing risk covered in False Claims Act Liability in Clinical Trial Billing.
What CTSU is and its role within the NCTN
NCI created CTSU to reduce the duplication that previously existed when every cooperative group ran its own separate site-credentialing, regulatory-documentation, and enrollment processes. Instead of a site maintaining a distinct regulatory relationship with each cooperative group whose trials it wanted to open, CTSU gives sites one shared regulatory and enrollment infrastructure that works across groups. It originally centralized support for Phase III cooperative-group trials and has since expanded to support NCI’s full network-trials portfolio: the National Clinical Trials Network (NCTN) — the cooperative groups (such as Alliance for Clinical Trials in Oncology, ECOG-ACRIN, NRG Oncology, and SWOG) that run large, publicly funded, multi-site cancer trials — as well as the NCI Community Oncology Research Program (NCORP), which extends NCTN and cancer-care-delivery trials into community-based practices, and the Experimental Therapeutics Clinical Trials Network (ETCTN), which runs early-phase trials of novel agents. A site that wants to open and enroll patients on a trial run by any of these networks generally works through CTSU rather than negotiating separately with each sponsoring group.
Practically, that means CTSU functions as the shared front door for three related but distinct jobs: (1) confirming that a site and its staff are credentialed to participate in NCI network trials at all, (2) collecting and centralizing the trial- and site-specific regulatory documentation each open protocol requires, and (3) coordinating with the IRB of record — most often NCI’s Central IRB — so that a site doesn’t have to separately track IRB approval status with each cooperative group whose trial it runs. Billing-compliance support, covered below, is a newer addition to that shared infrastructure, built specifically to address the Medicare coverage-analysis burden that NCTN, NCORP, and ETCTN trials otherwise push onto each site individually.
How CTSU centralizes regulatory documentation
Access to CTSU’s regulatory and enrollment systems runs through a CTEP-IAM account (Cancer Therapy Evaluation Program Identity and Access Management) — the credential every site staff member needs before they can use CTSU’s Regulatory application or register patients. Once credentialed, a site’s regulatory documentation is maintained centrally rather than re-collected by every cooperative group: investigator and staff qualifications, training records, and Human Subjects Protection/Good Clinical Practice documentation are submitted through the Registration and Credential Repository (RCR), which functions as the shared roster of who at a site is qualified to work on NCI network trials and in what capacity. That roster feeds a site’s eligibility to register for a given protocol without each investigator re-submitting the same qualifications documentation separately to every group running a trial the site wants to open.
Trial-specific and investigator-specific regulatory documents that would otherwise be tracked separately for each cooperative group — the FDA Form 1572 (Statement of Investigator), the financial disclosure documentation required under 21 CFR Part 54, current curriculum vitae/NCI biosketch, and IRB approval documentation — are submitted and tracked through CTSU’s Regulatory application rather than through parallel, group-specific processes. Site registration status for a given protocol can be checked through the same system, so a coordinator can confirm before activation whether a site’s regulatory packet for a specific trial is complete rather than discovering a gap at the point of trying to enroll a patient.
Patient enrollment itself runs through OPEN (the Oncology Patient Enrollment Network), CTSU’s web-based registration system for NCI network-group trials. OPEN is integrated with the same regulatory and roster data held in the Regulatory application and RCR, so a patient generally cannot be registered onto a protocol until the enrolling site’s own regulatory and credentialing documentation for that protocol is current — which is the mechanism that makes centralized regulatory tracking actually enforce site-level compliance, rather than being a parallel paperwork exercise a site could fall behind on without consequence.
IRB reliance: the NCI Central IRB (CIRB)
A large share of NCTN, NCORP, and ETCTN trials use a single IRB of record model rather than requiring separate local IRB review at every participating site — see Central IRB / Single IRB (sIRB) for the general mechanism. For NCI network trials, that role is most often filled by the NCI Central IRB (CIRB), and CTSU is where that reliance relationship is operationalized for participating sites. CIRB-approved regulatory documents (the approved protocol, consent forms, and related IRB correspondence) for NCTN, ETCTN, and NCORP studies are posted through the CTSU website rather than distributed separately by each cooperative group, and CTSU’s Regulatory application is integrated with the CIRB’s own IRB-management system so that approval and participation data move between the two rather than requiring a site to manually reconcile its local records against the CIRB’s.
This matters operationally because it removes one of the more common bottlenecks in multi-site cooperative-group research: a site that would otherwise need to submit the same protocol to its own local IRB for initial and continuing review can instead rely on the CIRB’s determination, provided the site has executed the appropriate reliance agreement and its own regulatory documentation with CTSU is current. Sites that prefer or are required to use local IRB review instead of the CIRB can still do so, but the CIRB/single-IRB pathway is what CTSU’s regulatory infrastructure is built to support at scale across a large, multi-institution trial network.
How CTSU supports billing compliance
Medicare’s coverage of “routine costs” associated with a qualifying clinical trial is governed by the Medicare Clinical Trial Policy (National Coverage Determination 310.1) — the framework covered in detail in False Claims Act Liability in Clinical Trial Billing. Under NCD 310.1, Medicare may pay for the routine care costs a participant would have incurred regardless of trial enrollment, while the trial sponsor is responsible for costs incurred specifically because the protocol requires them. Determining, item by item, which payer is responsible for which charge on a given protocol is the job of a coverage analysis — and producing one independently, protocol by protocol, is a significant administrative burden for a site, particularly for institutions that don’t have dedicated research-billing-compliance staff.
To reduce that burden across the NCTN, NCI convened a Coverage Analysis Working Group (CAWG), made up of representatives from CTSU, the cooperative groups, NCI, and billing-compliance specialists, to develop a standardized coverage-analysis template and review process for NCI network trials. Coverage analyses produced through that process are posted to the CTSU website for participating protocols, giving sites a starting reference point — reviewed against the NCD 310.1 framework — instead of building a coverage analysis for each NCTN, NCORP, or ETCTN protocol entirely from scratch. CTSU’s site also provides billing-related reference reports (sometimes referred to as Data and Billing Reports) that sites and their billing-compliance staff can use alongside the posted coverage analyses to reconcile what a protocol’s budget and consent documents say against what the site’s billing system is set up to charge to which payer.
It’s worth being precise about the limits of this support: CTSU-posted coverage analyses are a shared starting reference, not a substitute for a site’s own billing-compliance review. A site’s research billing office is still responsible for confirming that its own hospital or clinic billing system correctly codes each protocol-required item as sponsor-billable versus each routine-care item as Medicare/insurer-billable, and for keeping that mapping current as protocol amendments change what’s required. The coverage-analysis and billing-report resources CTSU centralizes reduce duplicated effort across sites; they don’t remove a site’s own obligation to get the sponsor-versus-payer split right for its own patients and its own billing system.
Who uses CTSU
CTSU’s primary users are staff at academic medical centers, community hospitals, and NCORP-affiliated community practices that participate in NCTN, NCORP, or ETCTN trials — most directly, clinical research coordinators and regulatory coordinators who maintain a site’s CTEP-IAM credentials, RCR roster entries, and protocol-specific regulatory submissions, and who register patients through OPEN. Research billing and revenue-cycle staff are a distinct but equally important user group: they’re the ones who use the posted coverage analyses and billing reports to build or update a site’s charge-routing logic for a given protocol, and who need to understand NCD 310.1’s routine-cost framework well enough to defend a billing decision if it’s later questioned. Institutional research administration offices — the units that oversee regulatory compliance and research-billing compliance more broadly — typically rely on both groups’ CTSU-sourced documentation as part of their own institutional audit and compliance record-keeping.
Practical guidance for coordinators and billing staff
- Get credentialed before you need it. A CTEP-IAM account, and current RCR entries for every staff member who will be listed on a protocol’s regulatory documents, should be in place before a site tries to activate a new trial — not requested at the point a protocol needs to open, since account and roster review is not instantaneous.
- Check site registration status per protocol, not just once. Because OPEN checks a site’s regulatory and roster status against the specific protocol being enrolled, a site that is current on one trial isn’t automatically current on another; confirm registration status for each protocol before a projected activation or enrollment date.
- Confirm which IRB pathway a protocol uses early. Determine whether a given NCTN, NCORP, or ETCTN protocol is using the CIRB single-IRB pathway or requires local IRB review before building out a site’s regulatory packet, since the reliance-agreement and documentation requirements differ between the two.
- Treat a posted coverage analysis as a starting point for your own review, not a finished answer. Billing-compliance staff should still walk the posted coverage analysis against the site’s own protocol budget, informed consent document, and billing-system configuration for that specific protocol before charges start flowing, since the coverage analysis is written at the protocol level and doesn’t account for site-specific billing-system quirks.
- Keep regulatory and billing staff coordinated, not siloed. Because OPEN enrollment depends on current regulatory documentation and because coverage analysis depends on protocol-specific budget and consent terms, a site’s regulatory coordinators and its research-billing staff need to be working from the same, current protocol documentation — a lag between the two is a common source of both enrollment delays and billing-compliance gaps.
Frequently asked questions
Is CTSU only for Phase III trials?
No. CTSU originally centralized support specifically for Phase III cooperative-group trials, but it has since expanded to support the NCTN’s full trial portfolio across phases, as well as NCORP and ETCTN trials.
Does every NCI network trial use the NCI Central IRB?
Most, but not all. A substantial share of NCTN, NCORP, and ETCTN protocols use the CIRB single-IRB-of-record model that CTSU’s regulatory infrastructure is built around, but some protocols or sites use local IRB review instead; a site should confirm the IRB pathway for each specific protocol rather than assume.
Does CTSU handle billing for a site, or just provide reference materials?
CTSU centralizes reference materials — protocol-level coverage analyses developed through NCI’s Coverage Analysis Working Group process, plus billing-related reports — that a site’s own research-billing office uses to build and reconcile its charge-routing decisions. It doesn’t submit claims or manage billing on a site’s behalf; that responsibility, and the compliance exposure that comes with it, stays with the site.
Who is eligible to register for a CTEP-IAM account and use CTSU’s systems?
Staff at institutions participating in NCI-sponsored NCTN, NCORP, or ETCTN trials — investigators, clinical research coordinators, regulatory staff, and research-billing/revenue-cycle staff who need access to a site’s regulatory and enrollment records — register for the credentials appropriate to their role.
For adjacent topics: see The Cost of Running a Clinical Trial for how trial budgets are built, Study Start-Up in Clinical Trials for how site activation fits into the broader trial-launch timeline, and Good Clinical Practice (GCP) Certification for the training credential that underlies the Human Subjects Protection/GCP documentation CTSU’s Regulatory application tracks.
