Carcinome colorectal (CRC) · ligne 1 · Aucune

Vue déterministe de l'entité source de la LJAM. L'autorité clinique demeure avec les ID de la source cités et l'état d'approbation de l ́examinateur.

Contenu clinique provisoire : il ne s'agit pas d'une ordonnance. Un oncologue doit vérifier les sources originales, l'applicabilité et le statut de révision.

Source YAML: dossier complet

Ligne thérapeutique	1
Voie	standard
Régime lié	`None`

ID	`IND-RECTAL-TNT-LONG-COURSE-PRODIGE23`
Type	Indication
État	reviewed 2026-05-08 \| pending_clinical_signoff \| actionability review required
Maladies	`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...

Utilisé par

Algorithmes

ALGO-RECTAL-LOCALLY-ADVANCED-TNT - ALGO-RECTAL-LOCALLY-ADVANCED-TNT