Audit: QRS - Anktiva to Treat Cancer

Audit conducted on 24/09/2026 02:51 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	88
Failed	0
N/A	6
Pass Rate	100.00%

• Total = Passed + Failed + N/A
• Pass Rate = Passed / (Passed + Failed) × 100
• N/A items are excluded from the pass rate calculation

---

1. General Rules

#	Description	Result	Comments
1.1	Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER.	🟢	All QRS statements trace to ER text (Therapeutic Protocol, Expected Benefits, Potential Risks, Key Interactions & Contraindications, Monitoring, Practical Considerations, Conclusion).
1.2	Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing.	🟢	Cautious phrasing carried through: “Splitting is not studied” (action_3_sub), “(theoretical)” on the lymphoma contraindication.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	No strengthening or softening; interaction severities (caution/monitor) and contraindications match ER wording.
1.4	The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc.	🟢	Contraindications come from ER “Populations who should avoid ANKTIVA”; interactions, benefits and risks keep their ER categories and tiers.
1.5	PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact.	🟢	Only brand name is TICE BCG, which the ER uses for the same regimen; no PMIDs, NCT IDs or expert names.
1.6	The QRS does not introduce new attributions.	🟢

2. Focus, Tone & Audience

#	Description	Result	Comments
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢
2.4	The QRS avoids language that implies medical or clinical advice	🟢
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address found.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are glossed in plain language (BCG, cystoscopy, cytology, eGFR, CD4, myocardial infarction).
2.8	Information is presented in a concise and very compact manner	🟢
2.9	It DOES NOT address the reader directly	🟢
2.10	The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review.	🟢
2.11	The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort.	🟢
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	No “anti-aging” wording.
2.15	The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt.	🟢	Route described as instillation by catheter / subcutaneous dosing; no colloquial terms.

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present; repeating marker_#/qualitative_item_# spans expanded as numbered instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	website spans and all non-variable markup identical to the template.

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	🟢	No ER source section is empty; empty High benefit tier is handled per 12.5.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	Action labels and interaction labels use the ER bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators in the QRS.
4.5	The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page.	🟢	Sections are condensed relative to the ER (no mechanistic rationale, magnitudes or citations carried).

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	duration is quoted because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	26.9.23 matches QRS.md version.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	2026-0924-0206
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	Opus 5.5
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢

6. Page Title & Header

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &)	🟢	“Anktiva to Treat Cancer - Quick Reference Sheet”
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/24/2026 from 2026-0924-0206.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence	🟢	Opens with “a prescription-only, laboratory-made immune signaling protein” and its use for early bladder cancer returning after BCG.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.3	[at_a_glance] is no longer than 70 words	🟢	70 words (script count).
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each fact maps to the ER Conclusion; “prescription-only” to the Examine/ConsumerLab sections.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 8 ER “Populations who should avoid ANKTIVA” items present.
8.3	Individual [stop_items] are formatted as <li></li>	🟢
8.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Only short plain-language glosses remain; no trailing dash clauses.
8.5	Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Qualifiers kept: stage T2 or higher, 14 days, >10 mg prednisone, NYHA III–IV, 6 months, eGFR ≤40 mL/min, (theoretical).
8.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	🟢	No ranking notation in the ER bullets; none carried through.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	Section is populated; ER lists populations to avoid.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	Section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All 9 ER interactions present; they are drug classes rather than listed contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Each item reduced to label plus severity (caution/monitor).
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Example drug lists and thresholds (above 10 mg/day, above 3 g/day, above 400 IU) preserved.
9.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	🟢	No ranking notation in the ER bullets; none carried through.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	Section is populated; ER lists interactions.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	Section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Approved bladder regimen, Second induction and maintenance, Single versus split dosing.
10.3	If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	ER provides more than three actionable aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢

11. Time to Effect

#	Description	Result	Comments
11.1	The three sets of [time] items cover the three most important time-to-effect aspects from the ER	🟢	3-month assessment, 6-month late response, 12-month success definition (Practical Considerations, Monitoring Protocol).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	All three relate to complete response, the main benefit, in chronological order.
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	ER provides three time-to-effect aspects.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel	N/A	ER provides time-to-effect information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢
12.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content in benefit items.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	ER has no High benefit; benefits_high span set to display: none.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢
13.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content in risk items.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four risk tiers have items.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 8 ER table biomarkers listed.
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty.	🟢	Cadence matches the ER ongoing-monitoring paragraph.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 5 ER qualitative markers listed.

Issues 24/09/2026 02:51

Pass rate 100.00%. No issues found.

Issues 24/09/2026 02:47

1. 7.2 — Lede omits key execution risk: The at-a-glance (QRS line 433) mentions only “mostly local, short-lived side effects” and omits the Conclusion’s decision-relevant risk that postponing surgery lets some cancers invade deeper (ER line 462).

Fixes 24/09/2026 02:47

1. 7.2 — Added surgery-delay risk to lede: Added “though postponing surgery lets some cancers invade deeper” to the at-a-glance (from ER Conclusion) and tightened wording (“together with” to “with”, “has come back despite that treatment” to “returned despite it”) to stay within 70 words.

Issues 24/09/2026 02:44

1. 7.5 — Clinical-register word in lede: The At-a-Glance (line 433) uses “is instilled into the bladder”, a clinical-register term a non-specialist would not use unprompted; the ER Conclusion (line 458) uses the plain wording “delivered into the bladder”.

Fixes 24/09/2026 02:44

1. 7.5 — Clinical-register word in lede: Replaced “is instilled into the bladder” with the plainer ER Conclusion wording “is delivered into the bladder” in the At-a-Glance.

Issues 24/09/2026 02:41

1. 2.15 — Lay route phrasing in lede: At-A-Glance (QRS line 433) says Anktiva “is delivered into the bladder” instead of the formal “instilled into the bladder”.
2. 4.2 / 4.3 — Interaction label not verbatim: Key Interactions item at QRS line 565 inserts “immune signaling protein drugs:” into the ER bold label “Other cytokine therapies (aldesleukin, interferon alfa):” (ER line 325).
3. 13.4 — Parenthetical kept in risks: risks_high (QRS line 578) retains the parenthetical “(under-the-skin)” in “injection-site reactions with subcutaneous (under-the-skin) injection”.

Fixes 24/09/2026 02:41

1. 2.15 — Formal route phrasing in lede: Changed “is delivered into the bladder” to “is instilled into the bladder” in the At-A-Glance.
2. 4.2 / 4.3 — Restored verbatim interaction label: Removed the inserted “immune signaling protein drugs:” so the label reads “Other cytokine therapies (aldesleukin, interferon alfa):” as in the ER.
3. 13.4 — Stripped risk parenthetical: Replaced “injection-site reactions with subcutaneous (under-the-skin) injection” with “injection-site reactions with subcutaneous dosing”, matching the ER heading.

Issues 24/09/2026 02:39

1. 2.7 — Unexplained specialist terms: “Lynch syndrome” in [benefits_speculative] (line 531) and “cytokine therapies” in [caution_items] (line 565) appear without the plain-language explanation the ER provides (“an inherited cancer-risk condition”, ER line 215; immune signaling proteins, ER line 243).

Fixes 24/09/2026 02:39

1. 2.7 — Glossed specialist terms: Changed “cancer prevention in Lynch syndrome” to “cancer prevention in Lynch syndrome, an inherited cancer-risk condition” and “Other cytokine therapies (aldesleukin, interferon alfa)” to “Other cytokine therapies (immune signaling protein drugs: aldesleukin, interferon alfa)”, using the ER’s own explanations.

Issues 24/09/2026 02:35

1. 8.4 — Trailing rationale in contraindication: The item at QRS line 544 ends with “(BCG requirements)”, an explanatory attribution of why the conditions apply rather than a decision-gate qualifier; 8.4 requires such explanations to be stripped.

Fixes 24/09/2026 02:35

1. 8.4 — Trailing rationale removed: Removed “(BCG requirements)” from the end of the active-infection/fever/blood-in-urine/14-day-resection contraindication, leaving only the decision-gate conditions.

Issues 24/09/2026 02:31

1. 2.15 — Lay route-of-administration phrasing: risks_high (line 578) reads “injection-site reactions with under-the-skin injection” instead of the formal route term “subcutaneous” used in the ER (line 247).
2. 8.5 — Dropped parenthetical qualifier: The contraindication at line 544 omits the ER’s parenthetical “(BCG requirements)” (ER line 331), which scopes the UTI/fever/visible blood/14-day resection exclusions.

Fixes 24/09/2026 02:31

1. 2.15 — Formal route term restored: Changed risks_high “injection-site reactions with under-the-skin injection” to “injection-site reactions with subcutaneous (under-the-skin) injection”.
2. 8.5 — Parenthetical qualifier restored: Appended the ER qualifier “(BCG requirements)” to the contraindication on active urinary tract infection, fever, visible blood in the urine, or within 14 days of bladder resection.

Issues 24/09/2026 02:27

1. 2.7 — Unexplained specialist terms: Benefits Low uses “checkpoint-inhibitor” (line 528) and Risks High uses “subcutaneous dosing” (line 578) without a plain-language rendering on the sheet.

Fixes 24/09/2026 02:27

1. 2.7 — Plain-language term rendering: Changed Benefits Low “restored checkpoint-inhibitor activity” to “restored activity of immune-brake-releasing checkpoint inhibitors” and Risks High “subcutaneous dosing” to “under-the-skin injection”.

Issues 24/09/2026 02:25

1. 2.15 — Lay route-of-administration phrasing: [risks_high] (line 578) reads “injection-site reactions when injected under the skin”, lay phrasing for the subcutaneous route instead of the ER’s formal “Injection-Site Reactions with Subcutaneous Dosing”.

Fixes 24/09/2026 02:25

1. 2.15 — Formal route-of-administration phrasing: In [risks_high], changed “injection-site reactions when injected under the skin” to “injection-site reactions with subcutaneous dosing”, matching the ER heading.

Issues 24/09/2026 02:21

1. 2.7 — Unexplained jargon in Risks: “injection-site reactions with subcutaneous dosing” (risks_high, line 578) and “Disseminated BCG infection” (risks_low, line 584) use specialist terms without plain-language wording, unlike the rest of the sheet.

Fixes 24/09/2026 02:21

1. 2.7 — Plain-language risk wording: Changed “injection-site reactions with subcutaneous dosing” to “injection-site reactions when injected under the skin” (risks_high) and “Disseminated BCG infection” to “BCG infection spreading beyond the bladder” (risks_low).

Issues 24/09/2026 02:18

1. 8.4 — Trailing rationale in contraindication: The stop item at line 544 ends with “(BCG requirements)”, a rationale rather than a time window, severity, threshold or staging qualifier.
2. 13.3 / 13.4 — Parenthetical gloss in risks: risks_medium at line 581 keeps the explanatory parenthetical “(a kidney-function marker)” after “serum creatinine”.

Fixes 24/09/2026 02:18

1. 8.4 — Trailing rationale removed: Removed “(BCG requirements)” from the end of the active-infection/bladder-resection contraindication item.
2. 13.3 / 13.4 — Parenthetical gloss removed: Changed “rise in serum creatinine (a kidney-function marker) and potassium” to “rise in the kidney-function marker creatinine and in potassium” in risks_medium.

Issues 24/09/2026 02:14

1. 2.7 — Unexplained specialist terms: “Cystoscopy, cytology” (time_1_sub line 489, marker_2_name line 617), “leukocyte esterase” (marker_6_target line 664), “NK-cell” (stop_items line 549) and “creatinine” (risks_medium line 581, marker_3 lines 628/634) appear without the plain-language glosses the ER provides.

Fixes 24/09/2026 02:14

1. 2.7 — Specialist terms glossed: Added ER-sourced glosses: cystoscopy (camera examination of the bladder) and cytology (microscope check of urine cells) in time_1_sub, leukocyte esterase (white-cell enzyme) in marker_6_target, NK-cell (natural killer cell) in stop_items, and creatinine (a kidney-function marker) in risks_medium.

Issues 24/09/2026 02:12

1. 2.7 — Unexplained medical jargon terms: “lymphopenia” (line 531), “cystectomy” (line 581), “IL-15–dependent lymphoid cancers” (line 587), “myocardial infarction” (line 547) and “filling defects” (line 675) appear without the plain-language glosses the ER provides.

Fixes 24/09/2026 02:12

1. 2.7 — Replaced unexplained jargon terms: Changed “lymphopenia” to “low lymphocyte counts”, “delaying cystectomy” to “delaying bladder removal”, “IL-15–dependent lymphoid cancers” to “immune-cell cancers that depend on the immune signal IL-15”, and added ER glosses “(heart attack)” after “myocardial infarction” and “(gaps in the contrast outline)” after “filling defects”.

Issues 24/09/2026 02:08

1. 2.7 — Unexplained specialist acronyms: “CIS” (marker_2_target, line 620), “BCG” (action_1_value line 447 and gate items lines 544, 558), “eGFR” (line 548) and “CD4” (line 545) appear without any plain-language explanation anywhere on the sheet.

Fixes 24/09/2026 02:08

1. 2.7 — Specialist acronyms explained: Added plain-language glosses: BCG explained in action_1_sub (“BCG is a weakened tuberculosis-related bacterium”), “biopsies free of CIS” changed to “biopsies free of carcinoma in situ (flat surface cancer)”, “eGFR ≤40 mL/min” changed to “Kidney filtering capacity (eGFR) ≤40 mL/min”, and “low CD4 counts” changed to “low CD4 (helper T cell) counts”.