Colorectal carcinoma (CRC) · line 1 · None
Deterministic view of the source YAML entity. Clinical authority remains with the cited source IDs and reviewer sign-off state.
Knowledge-base record for audit. Provisional clinical content: this is not a prescription. An oncologist must verify original sources, applicability and review status. Full rules and constraints are in the YAML.
| Line of therapy | 1 |
|---|---|
| Track | standard |
| Linked regimen | None |
| ID | IND-RECTAL-TNT-LONG-COURSE-PRODIGE23 |
|---|---|
| Type | Indication |
| Status | reviewed 2026-05-08 | pending_clinical_signoff | actionability review required |
| Diseases | DIS-CRC |
| Sources | SRC-ESMO-CRC-2024 SRC-NCCN-COLON-2025 SRC-PRODIGE-23-CONROY-2021 |
Notes
GI-3 wave C4 chunk (gi3-c4-rectal-tnt-prodige23-2026-05-08-2200). Fourth §17 phased indication after IND-GASTRIC-PERIOP-FLOT4 (GI-2 C1), IND-ESOPH-RESECTABLE-CROSS-NEOADJUVANT (GI-2 C2), and IND-RECTAL-TNT-SHORT-COURSE-RAPIDO (GI-3 C3). Sister rectal-TNT indication to RAPIDO short-course; pair forms the two NCCN cat 1 TNT backbones for locally advanced rectal cancer. The CRT phase uses type=chemoradiation with radiation_id only (XOR) — the concurrent capecitabine 825 mg/m² PO BID on RT days is documented in the RadiationCourse RC-LCCRT-504-28-RECTAL `schedule:` and `notes:` fields, not as a phase regimen_id, because the §17 XOR rule permits exactly ONE foreign key per phase and concurrent CRT is by convention modeled on the RadiationCourse side (planning doc §2.3, mirroring RC-CROSS-NEOADJ pattern from C2). Engine routing from `algo_rectal_*` (D-prefix algorithm extension) to this indication is out of C4 scope — flagged for the D-wave algorithm chunks. The `recommended_regimen` field is left null intentionally because TNT is multi-modality; consumers should iterate `phases:` rather than dereferencing a single regimen ID. Follow-up: a dedicated REG-CAPECITABINE-CRT-CONCURRENT regim...
Used By
Algorithms
ALGO-RECTAL-LOCALLY-ADVANCED-TNT- ALGO-RECTAL-LOCALLY-ADVANCED-TNT