Développeurs

Alignment with the CRF of the French national ovarian-cancer database, asked for by the surgeons (October 2026): points (1) to (8). Points (9) to (14) are not part of the CRF: they come from the project meeting of 2026-10-05 (card in brackets) and, for the label corrections of points (9) and (12), from the testing of this release. (1) Surgery evaluations now name a FIRST and a SECOND operator in place of the single 'Praticien' field: the existing practitioner column holds the first operator (same column, same content: only the form label changes, and only for surgery evaluations), and one NEW column, evaluation_meta_second_operator, holds the second operator. (2) Surgery evaluations also record, for every tumour, the general information the CRF asks for: ASA score, preoperative multidisciplinary validation (RCP), preoperative laparoscopy, and inclusion in a clinical study with the name of the study — five NEW columns, surgery only (null in every radiological file); the three yes/no answers are tri-state booleans (CSV 1 / 0 / empty cell). (3) BREAKING, ovarian cancer: the general-information select the form showed for an ovarian tumour under 'Stade' (French) / 'Grade' (English) never held a stage — its options were histological types. It is replaced by an 'Anatomopathologie' / 'Histology' field in the CRF's list (every role) and, for the surgeon, the preoperative FIGO stage on imaging (I to IV), the homologous-recombination (HR) status and the BRCA status. The column evaluation_meta_primary_tumor_grade is REMOVED and five NEW columns take its place: evaluation_meta_ovarian_histology, evaluation_meta_ovarian_histology_other, evaluation_meta_figo_preop_stage, evaluation_meta_hr_status and evaluation_meta_brca_status, filled for an ovarian tumour only — the histology in every file, the other three in the surgical file only (see the changes below for the legacy → new mapping). The per-operative FIGO stage, now labelled 'Stade FIGO peropératoire' / 'Intraoperative FIGO stage' for a surgery evaluation, stays in scores_figo, unchanged. (4) Ovarian cancer at RECURRENCE ('Récidive' among the aims of surgery of an ovarian tumour): the surgeon records the two criteria of the AGO score the form did not collect — the resection at the initial surgery (complete R0 / incomplete R1-R2) and the ascites at the recurrence work-up (absent < 500 mL / present ≥ 500 mL) — and the iMODEL risk (low / high, ticked by the surgeon, not computed): three NEW columns, evaluation_meta_initial_surgery_resection, evaluation_meta_recurrence_ascites and evaluation_meta_imodel_risk, surgery only. The AGO score itself is COMPUTED by the application from these two criteria and PS-ECOG — positive when the three are favourable (ECOG 0, complete initial surgery, ascites < 500 mL), negative as soon as one is not, null when not applicable or incomplete — and exported in one NEW column, scores_ago, surgery only. PS-ECOG, one of its criteria, can now be cleared: emptying the field stores null instead of keeping the previous value. (5) Operative report, incision section (the CRF items on the laparotomy and the volume of ascites aspirated): the extents of a midline laparotomy gain the code 'other' (a smaller laparotomy, e.g. a mini-laparotomy) in the existing column operative_report_incision_midline_details, whose values are therefore EXTENDED, and the surgeon's precision of it goes to one NEW free-text column, operative_report_incision_midline_other_details. BREAKING, the ascites found at opening: following the surgeons' decision of 2026-10-11, the form records it in the CRF's three classes, a single choice 'Pas d'ascite' / '< 500 cc' / '≥ 500 cc' that replaces the 'Ascite' switch and its free volume. The class is exported in one NEW column, operative_report_incision_ascites_volume_class (none | lt_500 | gte_500); the volume is no longer recorded and its column, operative_report_incision_ascites_quantity, is REMOVED; operative_report_incision_ascites_at_opening keeps its name and is now DERIVED from the class (true for < 500 or ≥ 500 cc, false for no ascites), and empty when no answer is recorded, where it exported false up to 3.9 — an incision section saved before this form with ascites ticked but no volume, which no class can carry, still exports true, its class empty. (6) Operative report, completeness of cytoreduction (the CRF tells the abdominal CC score from an extra-abdominal one, and details the residual disease): scores_cc_score keeps its name, codes and content and is now explicitly the ABDOMINAL CC score (its cards read 'Score CC abdominal' / 'Abdominal CC score'); one NEW column, scores_cc_score_extra_abdominal, holds the EXTRA-ABDOMINAL CC score on the same scale (cc0 | cc1 | cc2 | cc3, surgery only); three NEW free-text columns, operative_report_residual_disease_peritoneal, operative_report_residual_disease_nodal and operative_report_residual_disease_extra_abdominal, hold the surgeon's description of the residual peritoneal, nodal and extra-abdominal disease. The residual PCI (scores_pci_residual_*) still follows the abdominal score alone. (7) Operative report, end of the procedure (the CRF records how the abdominal wall was closed and the procedures associated with the cytoreduction): a NEW section 'Fermeture pariétale' / 'Abdominal wall closure' of the operative report (CRS and laparoscopy flows) is exported in four NEW columns, operative_report_closure_fascia_technique (running | two_hemi_running | interrupted), operative_report_closure_suture_material (free text), operative_report_closure_skin_technique (intradermal | staples | interrupted) and operative_report_closure_comment (free text); a NEW section 'Procédures associées' / 'Associated procedures' records the implantable port (port-a-cath) in one NEW column, operative_report_associated_procedures_implantable_port, a tri-state boolean (CSV 1 / 0 / empty cell). The CRF's two other associated procedures, the abdominal wall resection and the wall prosthesis, keep their existing columns (operative_report_abdominal_wall_* and operative_report_reconstructive_matrix_*). (8) Operative report, intraoperative complications (the CRF ticks the type of each complication and records the intraoperative transfusion): the complication types — vascular | urological | gastrointestinal | neurological | anesthetic, several per record — are exported in one NEW column, operative_report_complications_categories (a list: one CSV cell, the codes joined by ', '), and the transfusion in two NEW columns, operative_report_complications_transfusion (a tri-state boolean, CSV 1 / 0 / empty cell) and operative_report_complications_transfusion_details (the products and number of units, free text, filled for a transfusion only). The complications section, copied raw from the stored form data up to 3.9, is now WHITELISTED like the other operative-report sections: undeclared keys are no longer exported, the JSON always carries its five keys (null when not recorded, categories an empty list), and operative_report_complications_text and operative_report_complications_blood_loss keep their columns and type, an emptied field now exporting null rather than an empty string. (9) PCI scoring and implants, surgery and imaging alike (cards P1 to P3): scores.pci.total and scores.pci.regions_vector are now ENTERED by the practitioner, the lesion score (0 to 3) of each region, instead of being computed from the findings of the region; the size, the morphology and the structures of a region become purely descriptive, and the exact implant count, pci_details.[X].nodules.count, is replaced at the same rank by an optional count by classes, pci_details.[X].nodules.implant_count (none, 1_3, 4_10, gt_10, or empty): the thirteen columns pci_details_N_nodules_count are renamed in place pci_details_N_nodules_implant_count, and this point adds, removes or moves no other column. The residual PCI (scores.pci.residual.*) was entered by the surgeon already and is unchanged. Three structure NAMES change as well, in pci_details_X_involved_structures_Y_name_fr / _name_en: in region 1, 'Diaphragme' / 'Diaphragm' is now 'Péritoine diaphragmatique droit' / 'Right diaphragmatic peritoneum'; in region 8, in French only, 'Côlon droit, descendant' and 'Mésocôlon descendant' are now 'Côlon droit, ascendant' and 'Mésocôlon droit'. (10) PCI, SURGERY ONLY (card L4): a surgical region that could not be explored now records WHY. For a surgery evaluation the 'Non évaluable' / 'Non-assessable' switch of the region page reads 'Région non explorable' / 'Region not explorable' (same field, same effect on the score: the region counts 0, is 'X' in scores.pci.regions_vector and lowers scores.pci.max by 3), and the surgeon picks one of four reasons: extensive_tumor, adhesions, not_explored or other, the last one with a free-text precision. Thirteen NEW columns, one per region, pci_details_N_non_evaluable_cause (N = 0 to 12), each inserted right after pci_details_N_non_evaluable_reason, in EVERY file, surgical AND radiological — always empty in a radiological file, where the switch keeps its 'Non évaluable' label and its free text and no reason is offered. pci_details_N_non_evaluable_reason keeps its name, its rank within the region and its type but, in the surgical file, now holds the precision of the reason other alone (null under any other reason), where up to 3.9 it held the surgeon's free text; a surgical region marked before this version keeps its free text there, with an empty cause. Imaging unchanged. (11) Resectability (cards L1, L2 and T3): a 'Cœlioscopie avec ou sans PIPAC' (evaluation_meta.procedure_title = laparoscopy_pipac) now records on a step after region 12 whether the disease is resectable, exported in one NEW column, scores_surgical_resectability (resectable | unresectable, surgery only), right after scores_cc_score_extra_abdominal; for unresectable, the surgeon ticks the reasons for unresectability in the list the CC section of a cytoreduction report uses, the criteria_* columns. MEANING CHANGE of the criteria_N_items_Y_is_involved, _precision, _laterality and _options columns, unchanged otherwise: a reason is now reported only while the block that holds it is shown (always for imaging; an abdominal CC score of CC-1 to CC-3 for a cytoreduction; the verdict unresectable for a laparoscopy). A reason ticked and then hidden stays stored but exports as not involved; up to 3.9 it exported as involved. (12) Operative report, visceral resections (card S1): the surgeon can now record an ADRENALECTOMY, one item per side, 'Surrénalectomie droite' / 'Right adrenalectomy' and 'Surrénalectomie gauche' / 'Left adrenalectomy', total adrenalectomy implied, a bilateral one being both items. The two items close the kidney group of the urinary resections, whose organ_key stays kidneys and whose heading becomes 'Reins et glandes surrénales' / 'Kidneys and adrenal glands' (the values of its label_fr / label_en, 'Reins' / 'Kidneys' up to 3.9). EVERY SURGICAL file gains eighteen columns, the nine of each item, operative_report_visceral_resections_organs_15_items_4_* (right) then operative_report_visceral_resections_organs_15_items_5_* (left), right after operative_report_visceral_resections_organs_15_items_3_comment; no column is renamed or removed, and the radiological files are unchanged. In the same section, the French labels of the extended right and left colectomies now spell 'côlon transverse' (they read 'colon transverse'): a value change in operative_report_visceral_resections_organs_10_items_2_label_fr and _items_3_label_fr. (13) Operative report, two sets of new VALUES in existing columns, no column added, removed, renamed or moved (cards S2 and S7): the drain sites gain right_hypochondrium ('Hypochondre droit' / 'Right hypochondrium', the right subphrenic space above the liver) in operative_report_drains_X_location, and operative_report_reconstructive_anastomoses_X_montage, which held the limb of a jejunal anastomosis (roux_en_y | omega), now also holds the technique of a colorectal anastomosis after an extended left hemicolectomy, deloyers or toupet. (14) Research-export corrections (card T3), no column added, removed or moved: pci_details.[X].ascites.loculated is now false for a region without ascites, where files up to 3.9 could carry a phantom true; evaluation_meta.procedure_title and evaluation_meta.laparoscopy_aim_of_surgery only accept the codes of their menus; the controlled vocabulary published on /developers and in the XLSX codebook now lists the codes of twenty-one more coded columns of the operative report and of the PCI regions; and the codebook corrects the descriptions of the visceral organ columns, of the diaphragm involvement (codes 0 to 2, not 0 to 3) and of the drain exteriorisation level. DOCUMENTATION ONLY, no column change: the codebook now describes evaluation_meta_aim_of_surgery_details as the 'Résumé de la chirurgie' / 'Surgery summary' field it holds. WARNING, positional consumers: forty-three columns are inserted, two are removed and thirteen are renamed in place in EVERY file, surgical AND radiological (CT / spectral CT / PET-CT / MRI / FAPIT), net +41 columns per file; the SURGICAL file gains eighteen more (point (12)), net +59 columns there. Inserted in every file: evaluation_meta_second_operator right after evaluation_meta_practitioner; the five ovarian columns at the former place of evaluation_meta_primary_tumor_grade, right after evaluation_meta_primary_tumor_other; evaluation_meta_asa_score right after evaluation_meta_ecog_status; evaluation_meta_preop_mdt_validation, evaluation_meta_preop_laparoscopy, evaluation_meta_study_inclusion and evaluation_meta_study_name right after evaluation_meta_ca125_preop; evaluation_meta_initial_surgery_resection, evaluation_meta_recurrence_ascites and evaluation_meta_imodel_risk right after evaluation_meta_aim_of_surgery; scores_ago right after scores_figo_stage_iv_reason; scores_cc_score_extra_abdominal right after scores_cc_score, then scores_surgical_resectability; the thirteen pci_details_N_non_evaluable_cause (N = 0 to 12), each right after pci_details_N_non_evaluable_reason of its region; operative_report_incision_midline_other_details right after operative_report_incision_midline_details; operative_report_incision_ascites_volume_class right after operative_report_incision_ascites_at_opening, at the place of the removed operative_report_incision_ascites_quantity; and, after operative_report_complications_blood_loss, the last column up to 3.9, the eleven columns that now close every file: operative_report_complications_categories, operative_report_complications_transfusion and operative_report_complications_transfusion_details, then the three operative_report_residual_disease_* columns, the four operative_report_closure_* columns and operative_report_associated_procedures_implantable_port. In the surgical file only, the nine operative_report_visceral_resections_organs_15_items_4_* columns then the nine operative_report_visceral_resections_organs_15_items_5_* columns follow operative_report_visceral_resections_organs_15_items_3_comment. Renamed in place in every file: pci_details_N_nodules_count becomes pci_details_N_nodules_implant_count (N = 0 to 12), between pci_details_N_non_evaluable_cause and pci_details_N_nodules_size_mm, its cells holding the text codes none, 1_3, 4_10 or gt_10 (or an empty cell) instead of the integers 0 to 4. Every column from evaluation_meta_patient_name onwards therefore SHIFTS: by one position up to evaluation_meta_primary_tumor_other, by five for evaluation_meta_ecog_status, by six for evaluation_meta_ca125_preop, by ten from evaluation_meta_procedure_title to evaluation_meta_aim_of_surgery, by thirteen from evaluation_meta_aim_of_surgery_details to scores_figo_stage_iv_reason, by fourteen for scores_cc_score, by sixteen from scores_aletti_total to pci_details_0_non_evaluable_reason, then by one more after each pci_details_N_non_evaluable_cause — by seventeen + N from pci_details_N_nodules_implant_count to the pci_details_M_non_evaluable_reason of the next region (M = N + 1), from seventeen in region 0 to twenty-eight in region 11, and by twenty-nine from pci_details_12_nodules_implant_count to operative_report_incision_midline_details —, and by thirty from operative_report_incision_port_sites to operative_report_complications_blood_loss in the radiological files, while in the surgical file the shift is thirty from operative_report_incision_port_sites to operative_report_visceral_resections_organs_15_items_3_comment and forty-eight from operative_report_visceral_resections_organs_16_organ_key to operative_report_complications_blood_loss (operative_report_incision_ascites_volume_class standing where operative_report_incision_ascites_quantity stood). Read the CSV by header name, never by position. WARNING, consumers reading by NAME: fifteen columns DISAPPEAR from every file: evaluation_meta_primary_tumor_grade and operative_report_incision_ascites_quantity, removed, and the thirteen pci_details_N_nodules_count, renamed in place pci_details_N_nodules_implant_count with text codes instead of integers (point (9)); no other column is renamed or removed. Some columns keep their name but not their meaning: scores_pci_total and scores_pci_regions_vector now carry the lesion scores entered (point (9)); operative_report_incision_ascites_at_opening is now derived from the ascites class and can be empty (point (5)); in the surgical file, pci_details_N_non_evaluable_reason now holds the precision of the reason other alone where it held the surgeon's free text (point (10)); and the criteria_N_items_Y_is_involved, _precision, _laterality and _options columns no longer report a reason whose block is hidden: for the same stored answers, a reason that read 1 up to 3.9 may now read 0, its details empty (point (11)). The complications section, now whitelisted, no longer ships a key beyond its five declared ones, which its raw copy could carry undeclared up to 3.9. Labels are translated at export time, so the new label VALUES reach historic records too: operative_report_visceral_resections_organs_15_label_fr / _label_en, the heading of the kidney group, and the French labels of the extended colectomies, operative_report_visceral_resections_organs_10_items_2_label_fr and _items_3_label_fr (point (12)), and the names of three PCI structures in regions 1 and 8 (point (9)): identify an organ group by its organ_key, a procedure by its key and a structure by its position (X, Y), never by a label. Consumers checking codes against a closed list must accept the codes added to existing columns: other in operative_report_incision_midline_details (point (5)), right_hypochondrium in operative_report_drains_X_location and deloyers / toupet in operative_report_reconstructive_anastomoses_X_montage (point (13)), and, in the new columns of the kidney group, the item keys right_adrenalectomy / left_adrenalectomy of the operative_report_visceral_resections_organs_X_items_Y_key vocabulary (point (12)).

• evaluation_meta.second_operator — NEW: name of the second operator of a surgery evaluation, free text (field "Second opérateur" / "Second operator" of the general-information page, shown to surgeons only). Filled for evaluation_type = surgery only: null in every radiological file, where a single practitioner fills in the evaluation, and null when the surgeon left the field empty (an emptied field is saved as null, never as an empty string). Inserted right after evaluation_meta_practitioner, as CSV column 9 of both the surgical and the radiological file: every later column shifts by one. Historic records re-exported after this release carry it empty.
• evaluation_meta.practitioner — unchanged column and values, MEANING MADE EXPLICIT: for a surgery evaluation it is the FIRST operator, its form field being labelled "Premier opérateur" / "First operator" since this version (it read "Praticien" / "Practitioner" before, and up to 3.9 held the single surgeon entered there). For every other evaluation type it remains the practitioner who filled in the evaluation, under the unchanged "Praticien" / "Practitioner" label.
• evaluation_meta.asa_score — NEW: ASA physical status class of the patient (American Society of Anesthesiologists), picked by the surgeon on the general-information page (field "Score ASA" / "ASA score", shown to surgeons only, every tumour), exported as its text code 1 | 2 | 3 | 4 | 5 (1 normal healthy patient, 2 mild systemic disease, 3 severe systemic disease, 4 severe systemic disease that is a constant threat to life, 5 moribund patient) — the raw code only, no _fr / _en companion column. Filled for evaluation_type = surgery only: null in every radiological file, and null when not recorded (putting the select back on its placeholder clears it). Inserted right after evaluation_meta_ecog_status: every later column shifts by one more position.
• evaluation_meta.preop_mdt_validation — NEW: preoperative validation of the case by a multidisciplinary team meeting (field "RCP préopératoire" / "Preoperative multidisciplinary validation (MDT)"), a tri-state BOOLEAN: true = yes, false = no, null = not recorded (CSV: 1 / 0 / empty cell). Surgery only, every tumour: null in every radiological file. Inserted right after evaluation_meta_ca125_preop.
• evaluation_meta.preop_laparoscopy — NEW: laparoscopy performed before the surgery (field "Cœlioscopie préopératoire" / "Preoperative laparoscopy"), a tri-state BOOLEAN: true = yes, false = no, null = not recorded (CSV: 1 / 0 / empty cell). Surgery only, every tumour and both procedure titles: null in every radiological file. Right after evaluation_meta_preop_mdt_validation.
• evaluation_meta.study_inclusion — NEW: patient included in a clinical study (field "Inclusion dans une étude" / "Included in a clinical study"), a tri-state BOOLEAN: true = yes, false = no, null = not recorded (CSV: 1 / 0 / empty cell). Surgery only: null in every radiological file. Right after evaluation_meta_preop_laparoscopy.
• evaluation_meta.study_name — NEW: name of that study, free text (field "Nom de l'étude" / "Study name", offered only once the inclusion reads yes). Null unless study_inclusion is true — answering no, or clearing the inclusion, drops the stored name —, null when the name is left empty, and null in every radiological file. Right after evaluation_meta_study_inclusion: with the three columns before it, every column from evaluation_meta_procedure_title onwards shifts by four more positions.
• evaluation_meta.primary_tumor_grade — REMOVED (BREAKING): up to 3.9 this column held the value of the general-information select an ovarian tumour showed under the label "Stade" (French) / "Grade" (English), whose options were in fact histological types, not a stage nor a grade: serous | mucinous | clearCell | granulosa | others (historic records may carry the legacy numeric codes 1 | 2 | 3 | 4 | 5 of the same options). It is replaced by evaluation_meta.ovarian_histology and evaluation_meta.ovarian_histology_other, at its former position. Reading key for files up to 3.9, as applied to the evaluations in progress at the 3.10 update: mucinous / 2 → ovarian_histology = mucinous; clearCell / 3 → clear_cell; serous / 1 → other, with ovarian_histology_other = "serous (grade not specified)" (the legacy list could not tell high- from low-grade serous carcinoma, so neither is assumed); granulosa / 4 → other, with ovarian_histology_other = "granulosa" (the CRF list has no granulosa entry); others / 5 → other, precision empty. No FIGO stage was ever derived from these values.
• evaluation_meta.ovarian_histology — NEW: histological type of an ovarian cancer (field "Anatomopathologie" / "Histology" of the general-information page, filled in by every role), as an untranslated code in the CRF's order: high_grade_serous | low_grade_serous | clear_cell | endometrioid | mucinous | other | unknown — the raw code only, no _fr / _en companion column. Filled for an ovarian primary tumour only, in EVERY file (surgical and radiological); null for any other tumour and when not recorded (switching the tumour away from ovarian clears it). First of the five columns inserted at the former position of evaluation_meta_primary_tumor_grade, right after evaluation_meta_primary_tumor_other.
• evaluation_meta.ovarian_histology_other — NEW: free-text precision of an "other" histology (field "Préciser le type histologique" / "Specify the histological type"). Null unless ovarian_histology is other — any other histology drops the stored precision —, and null when left empty. Right after evaluation_meta_ovarian_histology.
• evaluation_meta.figo_preop_stage — NEW: preoperative FIGO stage of an ovarian cancer as assessed on imaging (field "Stade FIGO préopératoire (imagerie)" / "Preoperative FIGO stage (imaging)", shown to surgeons only), code I | II | III | IV — main stages, no sub-stage. Filled for evaluation_type = surgery and an ovarian tumour only: null in every radiological file, for any other tumour, and when not recorded. Not to be confused with scores.figo (see below). Right after evaluation_meta_ovarian_histology_other.
• evaluation_meta.hr_status — NEW: homologous-recombination status of an ovarian cancer (field "Statut HR (recombinaison homologue)" / "HR status (homologous recombination)", surgeons only), code deficient (HRD) | proficient (HRP) | unknown. Surgery and ovarian tumour only, null otherwise and when not recorded. Right after evaluation_meta_figo_preop_stage.
• evaluation_meta.brca_status — NEW: BRCA status of an ovarian cancer (field "Statut BRCA" / "BRCA status", surgeons only), code brca1 (BRCA1 mutated) | brca2 (BRCA2 mutated) | wild_type (not mutated) | unknown. Surgery and ovarian tumour only, null otherwise and when not recorded. Right after evaluation_meta_hr_status: with the four columns before it, evaluation_meta_ecog_status and every later column shift by four more positions (one removed, five inserted).
• scores.figo — unchanged column and values, MEANING MADE EXPLICIT: for a surgery evaluation (evaluation_type = surgery) it is, as before, the PER-OPERATIVE FIGO stage staged by the surgeon, with its sub-stages (IA … IVB, the parent stages IC and IIIA included), now labelled "Stade FIGO peropératoire" / "Intraoperative FIGO stage" on every page and document of the surgery evaluation (it read "Classification FIGO" before); for a radiological evaluation it remains the FIGO stage on imaging. The new evaluation_meta.figo_preop_stage is the preoperative stage on imaging recorded by the surgeon, a different field.
• evaluation_meta.initial_surgery_resection — NEW: resection achieved at the initial surgery of an ovarian cancer at recurrence (field "Résection lors de la chirurgie initiale" / "Resection at initial surgery" of the new block "Récidive — scores AGO et iMODEL" / "Recurrence — AGO and iMODEL scores" of the general-information page, shown to surgeons only), code complete (R0) | incomplete (R1/R2) — the raw code only, no _fr / _en companion column. A criterion of the AGO score (scores.ago): complete is favourable. Filled for evaluation_type = surgery, an ovarian primary tumour and "recidive" among evaluation_meta.aim_of_surgery only: null in every radiological file, for any other tumour or aim of surgery (the block closes, and the field is cleared, when the tumour stops being ovarian or "Récidive" is deselected — a laparoscopy, which empties the aims of surgery, included), and null when not recorded. Inserted right after evaluation_meta_aim_of_surgery.
• evaluation_meta.recurrence_ascites — NEW: ascites at the recurrence work-up (field "Ascite au bilan de récidive" / "Ascites at recurrence work-up", same block), code absent (< 500 mL) | present (≥ 500 mL) — the raw code only. A criterion of the AGO score: absent is favourable. Same filling conditions as evaluation_meta.initial_surgery_resection. Not the ascites found at opening in the operative report (operative_report.incision.ascites_volume_class). Right after evaluation_meta_initial_surgery_resection.
• evaluation_meta.imodel_risk — NEW: iMODEL risk ticked by the surgeon (field "Score iMODEL" / "iMODEL score", same block), code low | high — the raw code only. Entered as such: the application does not compute the iMODEL score. Same filling conditions as evaluation_meta.initial_surgery_resection. Right after evaluation_meta_recurrence_ascites: with the two columns before it, evaluation_meta_aim_of_surgery_details and every later column shift by three more positions.
• scores.ago — NEW: AGO score of an ovarian cancer at recurrence, COMPUTED by the application at each export, never entered: positive when its three criteria are favourable — PS-ECOG 0 (evaluation_meta.ecog_status), complete initial surgery R0 (evaluation_meta.initial_surgery_resection = complete) and ascites < 500 mL at the recurrence work-up (evaluation_meta.recurrence_ascites = absent), i.e. the optimal eligibility for a cytoreduction —; negative as soon as one criterion is unfavourable (PS-ECOG 1 to 5, initial surgery R1/R2, or ascites ≥ 500 mL), whatever the others. Null when NOT APPLICABLE (evaluation_type other than surgery, a non-ovarian tumour, or no "recidive" among the aims of surgery) and when INCOMPLETE (no unfavourable criterion, at least one not filled in): a missing criterion never makes the score negative. Inserted right after scores_figo_stage_iv_reason: scores_cc_score and every later column shift by one more position.
• evaluation_meta.ecog_status — unchanged column and values, CLEARING FIXED: emptying the PS-ECOG select of the general-information page now stores null. Up to 3.9 the emptied select kept the previous value, which came back on reload and was exported. PS-ECOG being a criterion of scores.ago, the score never rests on a stale value. Its published vocabulary now lists 0 to 5: the form has always offered PS-ECOG 5, but the list published on /developers up to 3.9 stopped at 4.
• operative_report.incision.midline_details — unchanged column, EXTENDED VALUES: the extents of a midline laparotomy (type = median, several per record) gain the code other — "Autre" / "Other", a smaller midline laparotomy such as a mini-laparotomy, the "other" of the national CRF — next to sus_ombilical | sub_ombilical | xyphopubien; the surgeon's precision of it is the new operative_report.incision.midline_other_details. This vocabulary (sus_ombilical | sub_ombilical | xyphopubien | other) is now published with the codebook. INPUT CHANGE: picking another incision type now empties the extents, as a change of approach already did; up to 3.9 a record could keep, unseen in the form, the extents of an abandoned midline incision under another type, so read this column together with operative_report.incision.type in older files.
• operative_report.incision.midline_other_details — NEW: free-text precision of the extent other of a midline laparotomy (field "Préciser la laparotomie médiane (ex. : mini-laparotomie)" / "Specify the midline laparotomy (e.g. mini-laparotomy)" of the CRS incision form, shown while "Autre" is selected). Null unless type = median and midline_details contains other — deselecting "Autre", picking another incision type or another approach clears it —, and null when left empty; leading and trailing spaces trimmed. Inserted right after operative_report_incision_midline_details: every later column shifts by one more position.
• operative_report.incision.ascites_at_opening — unchanged column, MEANING CHANGE and NULL ALLOWED: no longer the value of an "Ascite" / "Ascites" switch, which the form has not had since the surgeons' decision of 2026-10-11, but DERIVED from the class the surgeon picks, operative_report.incision.ascites_volume_class: true for lt_500 or gte_500, false for none, and null when no answer is recorded (CSV: 1 / 0 / empty cell). An incision section saved before this form reads its switch where no class can be derived from it: ascites ticked without a volume still exports true, as up to 3.9, with an empty operative_report_incision_ascites_volume_class. Up to 3.9 it was always true or false, false meaning "no ascites" as well as "never recorded": the empty cell now tells the second case apart.
• operative_report.incision.ascites_quantity — REMOVED (BREAKING): the volume of the ascites found at opening, in cc, the number the form recorded under the "Ascite" / "Ascites" switch up to 3.9. Following the surgeons' decision of 2026-10-11 (the CRF's three classes instead of a free volume), the form no longer records a volume: read operative_report.incision.ascites_volume_class instead (a volume < 500 cc is lt_500, a volume ≥ 500 cc gte_500). operative_report_incision_ascites_volume_class stands at its position.
• operative_report.incision.ascites_volume_class — NEW: CRF class of the ascites found at opening, PICKED by the surgeon on both incision forms of the operative report (CRS and laparoscopy flows): the single choice "Ascite" / "Ascites" of their additional information, cards "Pas d'ascite" / "No ascites", "< 500 cc" and "≥ 500 cc", which replaces the switch and the free volume of 3.9 (surgeons' decision of 2026-10-11). Codes none | lt_500 | gte_500 — the raw code only, no _fr / _en companion column. Null when no class is recorded (clicking the selected card again deselects it). An incision section saved before this form exports the class of its switch and volume: switch off → none, volume < 500 cc (0 included) → lt_500, volume ≥ 500 cc → gte_500, ascites ticked without a volume → null (operative_report_incision_ascites_at_opening then reads true). Not the ascites at the recurrence work-up (evaluation_meta.recurrence_ascites). Right after operative_report_incision_ascites_at_opening, at the position of the removed operative_report_incision_ascites_quantity: the two changes cancel out, no later column shifts for them.
• scores.cc_score — unchanged column and values, MEANING MADE EXPLICIT: it is the ABDOMINAL completeness of cytoreduction score, the single CC score the operative report recorded up to 3.9 under the heading "Exhaustivité de la Cytoréduction (score CC)" / "Completeness of Cytoreduction (CC score)"; since this version its cards read "Score CC abdominal" / "Abdominal CC score", next to the new extra-abdominal score (scores.cc_score_extra_abdominal). Same codes (cc0 | cc1 | cc2 | cc3), same storage, surgery only as before, and it alone still opens the residual PCI (scores.pci.residual.*, CC-1 to CC-3).
• scores.cc_score_extra_abdominal — NEW: EXTRA-ABDOMINAL completeness of cytoreduction score (cards "Score CC extra-abdominal" / "Extra-abdominal CC score" of the CC section of the operative report, CRS flow), code cc0 | cc1 | cc2 | cc3 on the scale of the abdominal scores.cc_score (cc0 no macroscopic residual disease, cc1 < 2.5 mm, cc2 between 2.5 mm and 2.5 cm, cc3 > 2.5 cm) — the raw code only, no _fr / _en companion column. Surgery only, like scores.cc_score: absent from the JSON and an empty cell in the CSV of every radiological file; null when not recorded (clicking the selected card again deselects it). It never opens the residual PCI, which follows the abdominal score alone. Inserted right after scores_cc_score: every later column shifts by one more position.
• operative_report.residual_disease.peritoneal — NEW: free-text description of the residual peritoneal disease at the end of the cytoreduction (field "Maladie péritonéale résiduelle" / "Residual peritoneal disease" of the new "Maladie résiduelle" / "Residual disease" block of the CC section of the operative report, offered whatever the CC score). Null when left empty; leading and trailing spaces trimmed. The residual PCI scored per region stays in scores.pci.residual.*. Inserted after the complications columns, right after operative_report_complications_transfusion_details, with the two columns below: no column up to 3.9 moves.
• operative_report.residual_disease.nodal — NEW: free-text description of the residual nodal disease (field "Maladie ganglionnaire résiduelle" / "Residual nodal disease", same block). Null when left empty; leading and trailing spaces trimmed. Right after operative_report_residual_disease_peritoneal.
• operative_report.residual_disease.extra_abdominal — NEW: free-text description of the residual extra-abdominal disease (field "Maladie extra-abdominale résiduelle" / "Residual extra-abdominal disease", same block), to be read with scores.cc_score_extra_abdominal. Null when left empty; leading and trailing spaces trimmed. Right after operative_report_residual_disease_nodal; the operative_report_closure_* columns follow.
• operative_report.closure.fascia_technique — NEW: closure technique of the FASCIA (cards "Aponévrose" / "Fascia" of the new section "Fermeture pariétale" / "Abdominal wall closure" of the operative report, CRS and laparoscopy flows, right after the drains), code running (one running suture) | two_hemi_running (two hemi-running sutures) | interrupted (interrupted sutures) — the raw code only, no _fr / _en companion column. Null when not recorded (clicking the selected card again deselects it). Appended at the very END of every file, after operative_report_residual_disease_extra_abdominal, with the four columns below: no existing column moves.
• operative_report.closure.suture_material — NEW: suture material of the fascia closure, free text (field "Fil utilisé" / "Suture material" of the same section, e.g. "PDS 1 bouclé" / "looped PDS 1"). Null when left empty; leading and trailing spaces trimmed. Right after operative_report_closure_fascia_technique.
• operative_report.closure.skin_technique — NEW: closure technique of the SKIN (cards "Peau" / "Skin" of the same section), code intradermal (intradermal running suture) | staples | interrupted (interrupted sutures) — the raw code only, no _fr / _en companion column. Null when not recorded (clicking the selected card again deselects it). Right after operative_report_closure_suture_material.
• operative_report.closure.comment — NEW: free comment on the abdominal wall closure (field "Commentaire" / "Comment" of the same section). Null when left empty; leading and trailing spaces trimmed. Right after operative_report_closure_skin_technique.
• operative_report.associated_procedures.implantable_port — NEW: implantable port (port-a-cath) placed during the operation (Yes / No choice "Pose d'une chambre implantable (PAC)" / "Implantable port placement (port-a-cath)" of the new section "Procédures associées" / "Associated procedures" of the operative report, CRS and laparoscopy flows), a tri-state BOOLEAN: true = yes, false = no, null = not recorded (CSV: 1 / 0 / empty cell; clicking the selected answer again deselects it). The CRF's two other associated procedures get no new column: the abdominal wall resection stays in operative_report.abdominal_wall.* and the wall prosthesis in operative_report.reconstructive.matrix.* (sites wall_r / wall_l, technique prosthetic), the sections the CRS form points the surgeon to. Right after operative_report_closure_comment: the last column of every file.
• operative_report.complications.categories — NEW: types of intraoperative complication ticked by the surgeon (multi-choice cards "Type de complication peropératoire" / "Intraoperative complication type" of the complications section of the operative report, "Complications peropératoires" / "Intraoperative complications", CRS and laparoscopy flows), codes vascular | urological | gastrointestinal | neurological | anesthetic, several per record — the raw codes only, no _fr / _en companion column, in the order of this list whatever the order they were ticked in. A list of scalars, hence ONE CSV column whose cell joins the codes with ", " (e.g. "vascular, urological"); an empty list (empty cell) when no type is ticked. Inserted right after operative_report_complications_blood_loss, the last column up to 3.9: no column up to 3.9 moves.
• operative_report.complications.transfusion — NEW: intraoperative transfusion (Yes / No choice "Transfusion peropératoire" / "Intraoperative transfusion" of the same section), a tri-state BOOLEAN: true = yes, false = no, null = not recorded (CSV: 1 / 0 / empty cell; clicking the selected answer again deselects it). Right after operative_report_complications_categories.
• operative_report.complications.transfusion_details — NEW: free-text details of the transfusion, the products and the number of units (field "Détails de la transfusion (produits, nombre d'unités)" / "Transfusion details (products, number of units)", shown while the transfusion reads yes, e.g. "2 CGR"). Null unless transfusion is true — answering no or deselecting the answer clears it —, and null when left empty; leading and trailing spaces trimmed. Right after operative_report_complications_transfusion; the three operative_report_residual_disease_* columns follow.
• operative_report.complications — WHITELISTED, was a raw copy: up to 3.9 the export copied the stored complications object verbatim, so any key that object carried beyond text and blood_loss reached the files undeclared (an extra JSON key, an extra CSV column). The section is now rebuilt on its declared keys — text, blood_loss, categories, transfusion, transfusion_details —: undeclared keys are no longer exported. The JSON always carries the five keys, null when not recorded (categories: an empty list), where a section never saved exported an empty list ([]) up to 3.9; the CSV already carried empty text and blood_loss cells in that case.
• operative_report.complications.text / operative_report.complications.blood_loss — unchanged columns and type, NORMALISED VALUES: both remain the text the form posts — blood_loss is the number entered, in cc, a numeric string in the JSON (e.g. "250") as before —, now trimmed of leading and trailing spaces, and an emptied field exports null instead of an empty string (CSV: the same empty cell).
• evaluation_meta.aim_of_surgery_details — DOCUMENTATION ONLY, unchanged column and values: the codebook still described it as free-text details on the aim of the surgery, the label of the field until May 2026 ("Détails sur l'objectif de la chirurgie" / "Aim of surgery details"); it now names the field the column holds, "Résumé de la chirurgie" / "Surgery summary" of the general-information page, which opens the narrative of the operative report.
• scores.pci.total / scores.pci.regions_vector — unchanged columns and paths, MEANING CHANGE: the score of each region is now the lesion score (LS, 0 to 3) entered by the surgeon or the radiologist in the first field of the region, "Score lésionnel (LS)" / "Lesion score (LS)" (legend: 0 no tumor · 1 ≤ 0.5 cm · 2 > 0.5 to 5 cm · 3 > 5 cm); the application no longer computes it. Up to 3.9 it was computed from the findings of the region: the size of the largest positive implant (≤ 5 mm → 1, ≤ 50 mm → 2, > 50 mm → 3, counted only once an implant count of at least 1 had been entered), the morphological terms and their qualifiers (surgery: micronodule / nodule / mass → 1 / 2 / 3, confluence → 2, or 3 when mass-sized; imaging: nodule qualifiers, scalloping → at least 2, focal → 2, diffuse → 3, and in region 0 a non-diffuse fat infiltration capping the size contribution at 2) and, in region 0, an involved omental cake (→ 3). A region whose lesion score was not entered counts 0, as an untouched region always did, and the file cannot tell it from a lesion score of 0 entered; a non-evaluable region (for a surgery evaluation, a region marked "Région non explorable" / "Region not explorable", see pci_details.[X].non_evaluable_cause) is still "X" in regions_vector and lowers scores.pci.max by 3, which is otherwise unchanged. A region score may therefore contradict pci_details.[X].nodules.size_mm, pci_details.[X].nodules.implant_count and the morphology of the same region: no rule links them any more. The residual PCI (scores.pci.residual.*) was already entered by the surgeon and is unchanged. Files up to 3.9 carry computed scores: check meta.version before pooling. An evaluation in progress at the update keeps the computed score of its regions scored 1 to 3 as their lesion score.
• pci_details.[X].nodules.count — REMOVED, replaced at the same rank by pci_details.[X].nodules.implant_count: the 13 columns pci_details_N_nodules_count are renamed in place pci_details_N_nodules_implant_count — still right before pci_details_N_nodules_size_mm, now right after the new pci_details_N_non_evaluable_cause; this change alone adds or moves no column — and their cells change from integers (0 to 3, 4 = more than 3) to text codes. The exact implant count gives way to an optional count by classes, "Nb. d'implants péritonéaux (facultatif)" / "No. of peritoneal implants (optional)", picked by the surgeon or the radiologist at the end of the implant section of each region: none (0), 1_3 (1 to 3), 4_10 (4 to 10), gt_10 (more than 10), raw code only. Null when no class is picked, for a region never opened and for a non-evaluable region: null is not none. Not part of the PCI score. No conversion: the values exported up to 3.9 do not map onto the classes — they are counts, 0 to 3 (before 3.8 the form stopped at 3, so a 3 may stand for more than three implants) and, from 3.8, 4 for more than 3 — and some may be lesion scores, the field having been labelled "Lesion score" in the English and German interfaces until early July 2026 and in the Spanish and Italian interfaces until 18 September 2026; do not pool the two columns.
• pci_details.[X].nodules.size_mm — unchanged column, now purely DESCRIPTIVE: it no longer feeds the region score. The size field opens once the region lesion score is at least 1 and is cleared when the lesion score goes back to 0, whatever the implant count (up to 3.9: opened by an implant count of at least 1, cleared when it went back to 0); it may therefore be filled while no implant class is picked.
• pci_details.[X].nodules.morpheus2 / morpheus_extras / morpheus_details and pci_details.[X].involved_structures.[Y].is_involved — unchanged columns and values, now purely DESCRIPTIVE: up to 3.9 the morphological terms, their qualifiers and, in region 0, an involved omental cake could raise the computed region score; they no longer do.
• pci_details.[X].involved_structures.[Y].name_fr / name_en — unchanged columns, VALUES CHANGED for three structures (a surgeon's report during the testing of this release): in region 1 (X = 1), "Diaphragme" / "Diaphragm" is now "Péritoine diaphragmatique droit" / "Right diaphragmatic peritoneum" — the structure of the region that carries diaphragm_score, named like its counterpart of region 3, "Péritoine diaphragmatique gauche" / "Left diaphragmatic peritoneum"; in region 8 (X = 8), in French only, "Côlon droit, descendant" is now "Côlon droit, ascendant" and "Mésocôlon descendant" is now "Mésocôlon droit" (the English "Right colon" and "Right mesocolon" were right and are unchanged). The names are read from the current catalogue at export time: every file exported after this release carries them, historic records included. Same structures at the same positions: match structures by their position (X, Y), not by name.
• pci_details.[X].non_evaluable_cause — NEW: reason why region X could not be explored, SURGERY ONLY: the single choice "Motif" / "Reason" offered under the switch "Région non explorable" / "Region not explorable" of the region page, the name the "Non évaluable" / "Non-assessable" switch takes for a surgery evaluation since this version (same field, same effect: the region scores 0, is "X" in scores.pci.regions_vector and lowers scores.pci.max by 3; only the label changes). Codes extensive_tumor ("Tumeur étendue" / "Extensive tumor") | adhesions ("Adhérences" / "Adhesions") | not_explored ("Région non explorée" / "Region not explored") | other ("Autre" / "Other", whose precision is pci_details.[X].non_evaluable_reason) — the raw code only, no _fr / _en companion column. Null for an evaluable region (is_evaluable = true), for a non-explorable surgical region whose reason is not picked (a region marked before this version included: its free text stays in non_evaluable_reason) and in EVERY radiological file (CT / spectral CT / PET-CT / MRI / FAPIT), where the switch keeps its "Non évaluable" label and its free text and no reason is offered. Cleared, with its precision, when the region is made evaluable again. Thirteen columns, pci_details_0_non_evaluable_cause to pci_details_12_non_evaluable_cause, each inserted right after pci_details_N_non_evaluable_reason of its region, in every file (CSV columns 66, 127, 164, 213, 254, 287, 332, 385, 430, 467, 500, 525 and 550 of a radiological file and of a surgical file without an Aletti breakdown; the Aletti categories of an ovarian surgical file come before them): within the PCI block the columns of region N that follow its cause shift by N + 1 more positions, and every column from criteria_0_key onwards by thirteen more.
• pci_details.[X].non_evaluable_reason — unchanged column, rank within its region and type, MEANING CHANGE on SURGERY: the free-text precision of the reason other alone (field "Préciser le motif" / "Specify the reason", shown while "Autre" is picked), trimmed, null when left empty and null under any other reason — a precision typed under "Autre" then left behind by a change of reason is neither exported nor printed. With no reason picked (pci_details.[X].non_evaluable_cause empty) it still carries, trimmed, the free text typed before this version by an evaluation in progress at the update. Up to 3.9 it held the surgeon's free text "Raisons de la non-évaluabilité" / "Reasons for non-assessability", the only reason recorded. IMAGING UNCHANGED: the radiologist's free text, as typed. Null for an evaluable region, as before.
• pci_details.[X].is_evaluable — unchanged column and values, LABEL CHANGE on SURGERY: false is now the switch "Région non explorable" / "Region not explorable" of the region page of a surgery evaluation (it read "Non évaluable" / "Non-assessable" up to 3.9: same field, same effect on scores.pci.*, only the label changes), its reason being pci_details.[X].non_evaluable_cause. Imaging keeps "Non évaluable" / "Non-assessable".
• scores.surgical_resectability — NEW: resectability verdict of a "Cœlioscopie avec ou sans PIPAC" (laparoscopy with or without PIPAC, evaluation_meta.procedure_title = laparoscopy_pipac), recorded by the surgeon on the "Résécabilité" / "Resectability" step that now follows region 12 of that procedure only ("La maladie est-elle résécable ?" / "Is the disease resectable?"): resectable = "Résécable" / "Resectable", unresectable = "Non résécable" / "Unresectable" — the raw code only, no _fr / _en companion column, and no "potentially": the radiological step keeps its "potential unresectability". Null when not recorded (the step is optional and its choice can be reset) and for every evaluation that does not offer the step: a cytoreductive surgery (surgery_alone, surgery_hipec, or no title) records its reasons for unresectability in the CC section of its operative report and never carries a verdict, not even one entered before its procedure title changed. Filled for evaluation_type = surgery only, like scores.cc_score: absent (not null) from the JSON of a radiological evaluation, an empty cell in its CSV. For unresectable, the reasons ticked are in criteria.* (see the next line). Right after scores_cc_score_extra_abdominal.
• criteria.[X].items.[Y].is_involved / precision / laterality / options — unchanged columns and values, MEANING CHANGE: a reason for unresectability is now reported only while the block that holds it is shown — always for a radiological evaluation, whose step after region 12 always shows the list; for a cytoreductive surgery, with an abdominal CC score of CC-1 to CC-3 (scores.cc_score; the extra-abdominal score alone does not show it); for a laparoscopy, with the verdict scores.surgical_resectability = unresectable. A reason ticked and then hidden (CC score back to CC-0 or cleared, verdict changed or cleared, procedure title changed) stays stored and comes back when its block is shown again, but meanwhile exports as is_involved = false, its precision, laterality and options empty; up to 3.9 it exported as ticked, so a surgical file could report reasons for unresectability next to scores.cc_score = cc0. The list, its order and its columns are unchanged; a laparoscopy now fills it too, from its resectability step (its operative report has no CC section). Files up to 3.9 may carry such hidden reasons: check meta.version before pooling.
• operative_report.visceral_resections.organs.[X].items.[Y] — TWO NEW ITEMS at the end of the kidney group (organ_key = kidneys, the sixteenth group: X = 15 in the CSV), after the four nephrectomies: right_adrenalectomy ("Surrénalectomie droite" / "Right adrenalectomy", Y = 4) and left_adrenalectomy ("Surrénalectomie gauche" / "Left adrenalectomy", Y = 5), which extend the published vocabulary of organs.[X].items.[Y].key. Total adrenalectomy implied (a partial one can only be described in free text); a bilateral adrenalectomy is both items performed; neither item excludes the other nor a nephrectomy. Each item carries the nine columns of every visceral item (key, label_fr, label_en, is_performed, segments, sub_option, measure, lymph_dredging, comment); the form offers them no segment, sub-option, measure nor lymph-node dredging, so segments, sub_option and measure stay null and lymph_dredging false. Inserted in EVERY SURGICAL file as the eighteen columns operative_report_visceral_resections_organs_15_items_4_* then operative_report_visceral_resections_organs_15_items_5_*, right after operative_report_visceral_resections_organs_15_items_3_comment: every later column of the surgical file shifts by eighteen more positions; no column is renamed or removed. The radiological files, whose operative_report_* columns hold only the empty placeholder group organs_0_items_0_*, are unchanged. is_performed is false whenever the item is not ticked, historic records included: up to 3.9 the form had no adrenalectomy item, so false does not mean that no adrenalectomy was performed in an operation recorded before this version — one could only be described in the free comment of the kidney group (operative_report_visceral_resections_organs_15_comment) or of the urinary section (operative_report_visceral_resections_section_comments_c3).
• operative_report.visceral_resections.organs.[X].label_fr / label_en — unchanged columns, VALUES CHANGED for the kidney group (organ_key = kidneys, X = 15 in the CSV): "Reins" / "Kidneys" up to 3.9, now "Reins et glandes surrénales" / "Kidneys and adrenal glands", the heading of the group since it holds the adrenalectomies. The labels are read from the current form at export time: every surgical file exported after this release carries the new values, historic records included. Identify a group by its organ_key, never by its label.
• operative_report.visceral_resections.organs.[X].items.[Y].label_fr — unchanged column, VALUES CHANGED (spelling) for two items of the transverse colon group (organ_key = transverse_colon, X = 10 in the CSV): extended_right_hemi (Y = 2) and extended_left_hemi (Y = 3) now read "Colectomie droite étendue au côlon transverse" and "Colectomie gauche étendue au côlon transverse" (they read "… au colon transverse"); label_en unchanged. Read from the current form at export time, like every label: every surgical file exported after this release carries the new spelling, historic records included. Identify an item by its key, never by its label.
• operative_report.drains.[X].location — unchanged column, EXTENDED VALUES: the drain sites of the operative report gain right_hypochondrium — "Hypochondre droit" / "Right hypochondrium", the right subphrenic space above the liver, offered right before left_hypochondrium; up to 3.9 such a drain could only be recorded as subhepatic (below the liver) or as other with a free-text site, and those records are not converted. operative_report.drains.[X].location_fr / location_en carry its two labels. The code was already listed in the published vocabulary, which no form could produce; the vocabulary now follows the order of the form.
• operative_report.reconstructive.anastomoses.[X].montage — unchanged column, EXTENDED VALUES: the "Montage" field, which held the limb of a gastrojejunal, oesojejunal or duodenojejunal anastomosis (roux_en_y | omega), now also holds the restoration technique of a colorectal anastomosis after an extended left hemicolectomy: deloyers — "Rotation du côlon droit (procédé de Deloyers)" / "Right colon rotation (Deloyers procedure)" — or toupet — "Passage rétro-iléal trans-mésentérique (technique de Toupet)" / "Retro-ileal transmesenteric passage (Toupet technique)". The two families never share a code; read the value together with operative_report.reconstructive.anastomoses.[X].type. Null when no technique is recorded, which every colorectal anastomosis up to 3.9 is. operative_report.reconstructive.anastomoses.[X].montage_fr / montage_en carry the labels. This vocabulary (roux_en_y | omega | deloyers | toupet) is now published with the codebook.
• pci_details.[X].ascites.loculated — unchanged column, CORRECTED VALUES: true only when the region has an ascites (minimal_volume or significant_volume true) whose partition is ticked "Cloisonné" / "Loculated", false otherwise, in particular without ascites, as pci_details.[X].ascites.free always was. Up to 3.9 the region page unticked the partition without saving it when the ascites went back to "Aucun" / "No ascites", and the column exported the stored partition as is: a region without ascites could export loculated = true. The page now saves the cleared partition and the export no longer reads a partition without an ascites. No conversion: the files delivered up to 3.9 keep these phantom values; in those files, read loculated only together with minimal_volume or significant_volume.
• evaluation_meta.procedure_title / evaluation_meta.laparoscopy_aim_of_surgery — unchanged columns and codes, ALLOWLISTED VALUES: the server now refuses any value outside the menus of the general-information page, "Titre de la procédure" / "Title of procedure" (surgery_alone | surgery_hipec | laparoscopy_pipac) and "Objectif de la cœlioscopie" / "Aim of laparoscopy" (diagnostic_biopsies | evaluation_chemo_neoadjuvant | emergency | pipac | other); up to 3.9 the value received was stored as is. The procedure title is still an empty string when the page was saved without a choice (every role but the surgeon) and null when it was never saved. A picked aim stays stored, and exported, if the procedure title later leaves the laparoscopy: read laparoscopy_aim_of_surgery only with procedure_title = laparoscopy_pipac.
• Controlled vocabulary (Notebook tab of /developers, XLSX codebook) — DOCUMENTATION ONLY, no column or value change: the exhaustive list of codes is now published for pci_details.[X].nodules.morpheus2 (the surgical terms, then the imaging ones), pci_details.[X].nodules.morpheus_extras (the 24 qualifiers and complementary descriptions of both forms), pci_details.[X].involved_structures.[Y].diaphragm_score (0, 1, 2), operative_report.reconstructive.matrix.[X].site and .technique, operative_report.reconstructive.anastomoses.[X].configuration, .peristalsis and .location, operative_report.reconstructive.stomas.[X].type, operative_report.reconstructive.urinary.[X].type and .side, operative_report.visceral_resections.small_bowel_details.resections.[X].portion, operative_report.incision.type, .laterality, .port_sites and .trocar_config, operative_report.hipec.technique, operative_report.biopsies.[X].region, operative_report.biopsies_laparo.items.[X].site, and operative_report.visceral_resections.organs.[X].items.[Y].segments and .sub_option. operative_report.reconstructive.stomas.[X].duration now also lists feeding and decompression, the two natures of a gastrostomy, exported all along but missing from the published list. operative_report.reconstructive.anastomoses.[X].type has no vocabulary: it is not a code but the label the surgeon picked among 19 suggestions or typed, in the language of the page; its codebook entry lists the 19 suggested labels.
• Codebook descriptions — DOCUMENTATION ONLY, no column or value change: operative_report.visceral_resections.organs.[X].organ_key, label_fr, label_en and comment were all described as a "General free-text comment on the incision section", a copy error: they hold the technical key of the organ or organ group, its French and English labels, and the comment entered for that organ. pci_details.[X].involved_structures.[Y].diaphragm_score was announced as "0 to 3": its codes are 0 (< 50 %), 1 (> 50 %) and 2 (muscular invasion), and the value 3 never existed. operative_report.drains.[X].exteriorization_level said a subcutaneous drain does not exit through the abdominal wall: only a chest drain does not. pci_details.[X].nodules.morpheus_extras now lists the qualifiers of the surgical form too, and operative_report.visceral_resections.organs.[X].items.[Y].sub_option is typed as the single choice it is.

Two changes on the small-bowel block of the operative report. (1) NEW field: each small-bowel resection now records which PORTION of the small bowel it concerned (duodenum | jejunum | ileum), asked for by the surgeons. (2) DOCUMENTATION CATCH-UP, no data change: small_bowel_details was documented as a single opaque JSON column, but the CSV exporter has always recursed into it — a real export already carried initial_length, resections_X_distance, resections_X_length and remaining_length as separate columns that no codebook row described. Those four columns are now declared, and none of them is renamed, moved or removed. WARNING, positional consumers: portion is inserted after each resection's length, so every column downstream of the first resection SHIFTS — read the CSV by header name, never by position. WARNING, consumers reading by NAME: one column name DISAPPEARS from two kinds of file. In the blank template on /developers and in every RADIOLOGICAL export (CT / PET-CT / MRI / FAPIT), operative_report_visceral_resections_small_bowel_details is REPLACED by the five detailed columns (-1, +5). A SURGICAL export is unaffected on this point and keeps whichever of the two shapes applies (see below).

• operative_report.visceral_resections.small_bowel_details.resections.[X].portion — NEW: portion of the small bowel concerned by resection X, as an untranslated code (duodenum | jejunum | ileum). No portion_fr / portion_en companion column: unlike the anastomosis fields, this value is exported as the raw code only. Empty when the surgeon left the select on "-", and for every report saved before this version. One new column per resection actually recorded (N resections → N new columns).
• operative_report.visceral_resections.small_bowel_details.{initial_length, resections.[X].distance, resections.[X].length, remaining_length} — DOCUMENTATION ONLY, no column change in a real export: these four paths were already emitted by every CSV carrying small-bowel data (CsvExportService flattens the block recursively; only morpheus_details is kept opaque) but the schema declared one aggregate path and the codebook one "JSON" row. They now have their own declaration and description. The aggregate path operative_report.visceral_resections.small_bowel_details is KEPT and documented alongside them, because a surgical export whose block holds no data at all still emits it as its single column (see below). A given file carries one shape or the other, never both.
• COLUMN REMOVED where the block is empty by construction — BLANK TEMPLATE and RADIOLOGICAL exports: the JSON skeleton and the blank CSV on /developers now carry the detailed shape {initial_length, resections:[{distance, length, portion}], remaining_length} in place of the single null leaf, so the column operative_report_visceral_resections_small_bowel_details is GONE from them and the five detailed columns take its place (1 → 5 columns on this block, +4 overall). A radiological export (CT / PET-CT / MRI / FAPIT) has no operative report and ships the untouched skeleton, so it loses that column name and gains the five in exactly the same way. A parser that looks the old name up by header in a radiological file will no longer find it.
• TWO SHAPES on this block in a SURGICAL export, both declared and both documented. (a) Block never filled in — every patient without a small-bowel resection, and every report saved before the block existed: the export emits null for the whole block, a null overwrites the skeleton subtree, and the file carries the single empty column operative_report_visceral_resections_small_bowel_details and NONE of the five detailed ones. (b) Block filled in: the five detailed columns appear (plus 3 more per additional resection) and the aggregate column is absent. Consumers must accept both shapes. Note that (a) is a SURGICAL shape only — a radiological file, having no operative report at all, is in shape (b) with every cell empty.
• THIRD SHAPE RETIRED: up to 3.8 a surgical report whose small-bowel panel had been touched but held no resection (the initial length edited, or a resection added then deleted) exported resections as an empty list, which the CSV flattened into one container column named operative_report_visceral_resections_small_bowel_details_resections. That column no longer exists in any file: the skeleton now supplies resection 0, so this case emits the same five detailed columns as any other filled-in block, all empty. The column was never declared in the schema nor described in the codebook, but it did ship in real files — hence this notice.
• HISTORIC RECORDS re-exported after this release: a report saved before 3.9 stored no portion key at all, and its file carries the portion column EMPTY on every resection — not on the first one only. The exporter rebuilds each resection on the declared key set {distance, length, portion}, so the header of an old record is the same as that of a new one; the block is the last list of objects in this export that was copied verbatim from the stored form data. Do not read an empty portion as "portion not applicable": compare against the meta.version of the file.
• MEDICAL CAVEAT on the pairing of portion and distance: distance is measured from the angle of Treitz, which IS the duodeno-jejunal junction, so it has no meaning for a duodenal resection (the duodenum lies upstream). The form records what the surgeon states and fabricates no consistency between the two fields. Likewise remaining_length is computed as initial_length minus every resected length, and initial_length defaults to 600 cm, the length of the JEJUNO-ILEAL small bowel: a duodenal resection therefore subtracts from a capital that does not contain it. Treat remaining_length with caution on any record carrying a duodenal portion.

Radiological review of the PCI by the validating radiologist. Four reference-data changes: the extraperitoneal inguinal canal moves from region 8 to region 5 (it belongs to the two iliac fossae, 5 and 7); region 2 stops listing the foramen of Winslow twice; the fourth unresectability group is rebuilt from one generic placeholder into the five extraperitoneal regions the surgeon cannot fully visualise; and lateralised iliac nodes are added to the abdominal lymph-node group. No path is added or removed from the schema, but the CSV grows by 26 columns and every column after the first change SHIFTS POSITION — read the CSV by header name, never by position. TWO things keep their name and change meaning: criteria_3_items_0_* (now the retroperitoneum, no longer the generic occult lesion) and pci_details_X_nodules_count (which can now be 4, meaning more than 3).

• pci_details.[2].involved_structures — the duplicate occult "Foramen of Winslow" is removed (the region kept the normal one). The four columns pci_details_2_involved_structures_9_{name_fr,name_en,is_involved,diaphragm_score} disappear; the region drops from 10 to 9 entries. Files exported from 3.3 (when the occult spaces were merged into the anatomic-structure list) to 3.7 carried the foramen twice in region 2, at positions 4 and 9, indistinguishable by label alone: no stable structure identifier is exported.
• pci_details.[8].involved_structures / pci_details.[5].involved_structures — the extraperitoneal "Inguinal canal / Canal of Nuck" moves from region 8 to region 5. The four columns pci_details_8_involved_structures_6_* disappear and pci_details_5_involved_structures_7_* appear. It now sits on the two iliac fossae, region 5 (left) and region 7 (right).
• criteria.[3] (occult_lesions) — the single generic "occult (extraperitoneal) lesion" item is replaced by five named extraperitoneal regions, in this order: 0 retroperitoneum (retroperitoneal fat), 1 abdominal wall, 2 epigastric vessels (lymph node), 3 previous abdominal wall scars and port sites, 4 cardiophrenic and subxiphoid regions. The group grows from 7 to 31 columns. WARNING: criteria_3_items_0_* keeps its name but changes meaning — it now designates the retroperitoneum, not the generic occult lesion. The group key stays occult_lesions.
• criteria.[1] (abdominal_lymph_nodes) — new lateralised "Iliac nodes" item, inserted at its anatomical rank between "Retroperitoneal below the renal pedicle" and "Inguinal nodes". The group grows from 5 to 6 items (+6 columns). WARNING, positional consumers: criteria_1_items_4_* now designates the ILIAC nodes (it used to be the inguinal ones) and the inguinal nodes move to criteria_1_items_5_*. criteria_1_items_4_laterality is the first column of this group to carry right | left | bilateral.
• DOCUMENTATION, no column change: the five leaves name_fr, name_en, precision, laterality and options of criteria groups 1, 2 and 3, plus criteria_1_key and criteria_2_key, are now declared in the schema and described in the codebook. They were already shipped in every CSV (the formatter is generic) but only is_involved was documented, so 72 columns of the current file had no codebook row. The blank template on /developers gains them; no column of a real export is renamed, moved or removed — verified by the CSV header contract test.
• pci_details.[X].nodules.count — unchanged column, EXTENDED VALUES: the form offers "> 3" again next to the exact counts 0-3, encoded as 4. A 4 means "more than 3 implants", not four implants; averaging the column without handling 4 separately now overestimates. No version listed in this changelog (2.0 onwards) ever emitted a value above 3. Files carrying the pre-changelog labels 2.6 / 2.7 may already contain a 4: it meant "more than 3" there too, the original encoding being restored unchanged.

New optional location field on digestive anastomoses: records where a colocolic anastomosis sits along the colon (right / transverse / left), so the operative schema can draw it on the correct segment. Three new columns per anastomosis entry; existing columns are unchanged. Same release: the iso/aniso peristalsis choice is now only offered for a side-to-side (LL) configuration — the peristalsis columns are unchanged but will be null for the other configurations going forward.

• operative_report.reconstructive.anastomoses.[X].location — NEW: coded localization along the colon (right | transverse | left), colocolic anastomoses only; null for other types or when not entered (the schema then infers the segment from the recorded colectomy).
• operative_report.reconstructive.anastomoses.[X].location_fr — NEW: French label of the localization.
• operative_report.reconstructive.anastomoses.[X].location_en — NEW: English label of the localization.
• operative_report.reconstructive.anastomoses.[X].peristalsis — unchanged column, restricted INPUT: the CRO form now offers the iso/aniso choice only for the side-to-side (LL) configuration (it has no meaning for end-to-side/side-to-end/end-to-end). New records under other configurations export null; historic values are kept unless the report is edited again.

Each drain now records where it is exteriorised through the wall: a side (left/right) and a level (upper/middle/lower third). Six new columns per drain entry; existing columns are unchanged. Same release also stops the drain code columns from carrying an untranslated key when the picker was left empty.

• operative_report.drains.[X].exteriorization_side — NEW: coded exteriorisation side (left | right), null when not recorded. There is no midline code: a drain brought out through the laparotomy itself has no value of its own today.
• operative_report.drains.[X].exteriorization_side_fr — NEW: French label of the exteriorisation side.
• operative_report.drains.[X].exteriorization_side_en — NEW: English label of the exteriorisation side.
• operative_report.drains.[X].exteriorization_level — NEW: coded exteriorisation level (upper_third | middle_third | lower_third), null when not recorded.
• operative_report.drains.[X].exteriorization_level_fr — NEW: French label of the exteriorisation level.
• operative_report.drains.[X].exteriorization_level_en — NEW: English label of the exteriorisation level.
• operative_report.drains.[X].type / .location — unchanged columns, corrected VALUES: a picker left on its placeholder was exported as an empty code whose label columns then carried the untranslated key ("OR.drains.types."). Such an entry now exports null in the code column and null in both label columns. In the CSV the code cell was already blank, so what moves there is the label cell, from the literal key to an empty cell.

New optional montage field on digestive anastomoses: records the reconstruction technique when several exist for one anastomosis type (currently the gastrojejunal anastomosis: Roux-en-Y limb vs omega loop). Three new columns per anastomosis entry; existing columns are unchanged.

• operative_report.reconstructive.anastomoses.[X].montage — NEW: coded montage (roux_en_y | omega), null for other anastomosis types or when not entered.
• operative_report.reconstructive.anastomoses.[X].montage_fr — NEW: French label of the montage.
• operative_report.reconstructive.anastomoses.[X].montage_en — NEW: English label of the montage.
• operative_report.reconstructive.anastomoses.[X].type — unchanged column (free text), but the picker now also offers the pancreatico-jejunal anastomosis, so this new label can appear in the data (a Whipple has three anastomoses; the report could previously record only two).

Six CRO sections that were exported as a raw client passthrough (incision, reconstructive, biopsies, biopsies_laparo, surgical_procedures_laparo, planned_treatment_laparo) plus hipec.details are now stable whitelisted structures: they always emit the same documented columns (null when absent) and match ExportSchemaRegistry::SCHEMA one-to-one. This removes the silent drift where real exports carried undocumented columns, omitted documented ones, and varied the column set from one patient to the next.

• operative_report.incision.* — full incision geometry now documented (was only 6 keys): approach/type/laterality with _fr/_en labels, midline_details, port_sites, port_site_other, trocar_config (+labels), trocar_count, mini_laparotomy(+details), robot_assisted(+details), other_description, pre_peritoneal, adhesiolysis, ascites_at_opening, ascites_quantity, comment.
• operative_report.reconstructive.* — anastomoses.[X], stomas.[X], urinary.[X] and matrix.[X] (prosthetic mesh) are now whitelisted object lists with bilingual labels; vascular_comment and global_comment added; UI-only DOM ids are no longer exported.
• operative_report.biopsies.* and operative_report.biopsies_laparo.* — biopsy sites and cytologies are emitted as stable structures; the scalar biopsies_laparo column becomes a structured object.
• operative_report.surgical_procedures_laparo.* and operative_report.planned_treatment_laparo.* — the two laparoscopy scalar columns are replaced by their documented field sets.
• operative_report.hipec.details.* — the HIPEC details sub-object is now a fixed whitelist (pathology, surgery, chemo, temp, duration, flow, volume) instead of a raw passthrough (only temp and duration were declared before).

Unresectability criteria fully rebuilt to the final surgical reference document: 30 criteria across peritoneal disease/organ resections, bulky nodes, distant/extra-peritoneal metastases and occult lesions. Criteria can now carry multi-option enumerations (pancreas head/body/tail, ureter thirds, vessel list, abdominal-wall side, small-bowel segments, duodenum parts), exported per item. The occult-lesions column is now emitted in its own criteria group.

• criteria.[].items.[].options — new per-item field: null when the criterion declares no option set, otherwise the list of selected option keys.
• criteria.[3] (occult_lesions) — the occult-lesions criteria group is now emitted in its own bucket (previously silently folded into non_resecability_reasons); criteria.[].key gains the value occult_lesions.
• Criteria set/grouping changed (data, not schema): the whole unresectability criteria set was rebuilt to the final medical document (22 peritoneal-disease / 5 nodal / 2 metastatic / 1 occult).

Unresectability criteria reworked: right/left laterality is now captured for the criteria that support it (ureter invasion, arterial/venous infiltration, massive diaphragm involvement) and exported as a per-item scalar enum. A "second, third and fourth part of duodenum" criterion is added and "Ureter(s) invasion" moves to the peritoneal-disease column.

• criteria.[].items.[].laterality — new per-item field: null when not applicable, otherwise one of right | left | bilateral.
• Criteria set/grouping changed (data, not schema): new "second, third and fourth part of duodenum" criterion; "Ureter(s) invasion" moved from the extra-peritoneal to the peritoneal-disease group.

PIPAC and HIPEC export now match their documented contract: hipec.performed is emitted (was stored but dropped), and the PIPAC section is a stable, documented structure (was passed through raw) enriched with the computed protocol label.

• operative_report.hipec.performed — now emitted (yes/no); previously documented but never produced.
• operative_report.pipac.* — PIPAC is no longer a raw passthrough. Documented keys: performed, context, chemo_details, protocol, protocol_label_fr, drug, dose, duration, comment. Newly exported: context, chemo_details, drug, duration; protocol_label_fr is now computed (was absent from the raw payload).

Imaging PCI morphology aligned with the "Lexicon of morphological terms on imaging": three MORPHEUS 2 terms (nodule, thickening_plaque, fat_infiltration) whose qualifier/complementary extras now drive auto-scoring. Infiltration is merged into the fat_infiltration term and the dedicated infiltration block is removed (BREAKING).

• pci_details.[X].infiltration.{present,retractile,diffuse_retractile} — REMOVED. Fat infiltration is now reported as the "fat_infiltration" term inside pci_details.[X].nodules.morpheus2 / morpheus_extras / morpheus_details (qualifiers fat_infiltration_q_focal | fat_infiltration_q_diffuse).
• pci_details.[X].nodules.morpheus2 — imaging value set replaced: the 9 legacy imaging terms give way to nodule, thickening_plaque, fat_infiltration. (Surgery terms unchanged.)
• pci_details.[X].nodules.morpheus_extras — new imaging qualifier/complementary values: nodule_q_{micronodule,nodule,mass}, nodule_c_{calcified,mucinous,cystic,scalloping}, thickening_plaque_q_{focal,diffuse}, thickening_plaque_c_{calcified,mucinous}, fat_infiltration_q_{focal,diffuse}, fat_infiltration_c_{calcified,mucinous}.

Residual PCI for incomplete cytoreductions, Aletti Surgical Complexity Score for ovarian cancer, and formal documentation of file metadata.

• scores.pci.residual.{applicable,total,max,regions_vector} — residual PCI after an incomplete cytoreduction (CC-1/2/3).
• scores.aletti_total, scores.aletti_complexity_class, scores.aletti_complexity_label — Aletti SCS (ovarian cancer evaluations only).
• aletti_details[] — per-category Aletti breakdown (ovarian cancer evaluations only).
• meta.generated_at, meta.version, meta.language_codes — file metadata now formally documented in the codebook.

Laparoscopy (PIPAC) workflow fields and patient sex.

• evaluation_meta.patient_sex, evaluation_meta.laparoscopy_chemo_name and related laparoscopy fields.
• operative_report.biopsies_laparo, surgical_procedures_laparo, planned_treatment_laparo.

Schéma reconstruit (cette version est antérieure au schéma machine-lisible ; reconstitué depuis l'historique des changements).

First versioned codebook of the structured surgery/imaging export.

• Initial published structure: evaluation_meta, scores, pci_details, fagotti, criteria and the full operative_report tree.

Téléchargements indisponibles : cette version est antérieure au schéma machine-lisible et ne peut être reconstituée de façon fiable.