Audit: QRS - Caffeic Acid Phenethyl Ester for Health & Longevity
Audit conducted on 10/09/2026 03:02 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 87 |
| 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. | 🟢 | Spot-checked every populated span: dosing 226–1500 mg (ER 405), 900 mg clustering (ER 405), split dosing (ER 415), timing (ER 417), 8–24 / 8–12 week windows (ER 460, 490), 3-day URI remission (ER 193), all 10 markers and targets (ER 494–503), all gate items (ER 345–379). |
| 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. | 🟢 | “No protocol exists for the isolated compound” (line 457) and “half-life is unmeasured in humans” (line 471) mirror ER 403 and 413; “local, short-term effect only” mirrors ER 191. |
| 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”). | 🟢 | Tier placement matches the ER exactly (no High/Medium benefits, Medium risk = contact dermatitis); “Pregnancy and lactation” stays in the stop gate, not the caution gate. |
| 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. | 🟢 | Stop items come from the ER “Populations who should avoid” list (ER 369–379); caution items from the ER interaction bullets (ER 345–367). No modifying factors appear in either gate. |
| 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. | 🟢 | No PMIDs, author names, NCT numbers or brand names (EPP-AF, Comvita, Apis Flora) appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind in the sheet. |
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. | 🟢 | Sober, evidence-graded register throughout, matching the ER’s repeated distinction between isolate and whole-extract data. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and windows are given without hedging or alarm; the sheet states what can be tracked and when. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Descriptive constructions (“Common practice given…”, “trials detecting glycemic and lipid change ran…”) rather than instructions. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives; the footer disclaimer is the template’s own. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrences of “recommend”, “advise”, “should take” or equivalents; “Nothing meaningful should be expected before two months” is ER wording (ER 460). |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are glossed or plain (“the enzyme that makes urate”, “averages blood sugar over roughly three months”); the At-A-Glance lede is fully jargon-free. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items are single clauses, benefit and risk tiers are semicolon-separated noun phrases, marker rows are three short cells. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your” in any span. |
| 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. | 🟢 | Optimal-range targets (hs-CRP below 0.5 mg/L, HbA1c 4.9–5.4%) rather than conventional disease cutoffs. |
| 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. | 🟢 | Ten-marker panel, split dosing with meals and weekly skin checks are all presented as ordinary expectations. |
| 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. | 🟢 | No simplified “ask your doctor” framing; assumes access to IL-6, eosinophil count and home blood-pressure averaging. |
| 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. | 🟢 | The lede foregrounds the absence of isolate data and the sourcing problem — the two facts that decide use 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. | 🟢 | “anti-aging” does not occur; the title uses “for Health & Longevity”. |
| 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 and event terms are formal (“oral spray”, “gastrointestinal intolerance”, “allergic contact dermatitis”, “systemic hypersensitivity”); “blood sugar” appears only inside an ER-verbatim explanation of glycated hemoglobin. |
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” | 🟢 | All headings, gate headings, tier labels and column headers match the template byte-for-byte. |
| 3.2 | All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. | 🟢 | Diff of the span-name sets against the template shows only the expected expansions of marker_#* (1–10) and qualitative_item# (1–6); 70 spans present. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Head, style block, website=”evidence_review”/”audit”/”full_review” spans and footer are 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” | N/A | No section of the source ER is empty; the empty High/Medium benefit and High risk tiers are governed by 12.5 and 13.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. | 🟢 | Protocol labels “Standard extract dosing”, “Split rather than single dosing”, “Best time of day” are the ER’s bold labels (ER 405, 415, 417); caution items reuse the ER interaction labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names match the ER biomarker table exactly; benefit and risk items reuse the ER subsection headings. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Zero emoji characters in the file; tiers are rendered with CSS classes and bold labels only. |
| 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. | 🟢 | Every section is heavily condensed against the ER (13 protocol bullets → 3 cells, 8 benefit subsections → 1 line, 10-row biomarker table stripped to three columns); no section carries ER prose across. |
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. | 🟢 | Lines 2–14: the metadata comment immediately follows the doctype and precedes every other element. |
| 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. | 🟢 | Opening “—” at line 3, closing “—” at line 13. |
| 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. | 🟢 | Enclosed in an HTML comment; no metadata value is repeated in the header or body. |
| 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. | 🟢 | Only duration: “00:04” is quoted, correctly, because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: caffeic_acid_phenethyl_ester_2026-0910-0002_Opus_ER.md. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | Line 6: qrs_creation_date: 2026-0910-0248. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Line 7: qrs_creator_ai_nickname: Opus. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” — single word, no version. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Line 8: qrs_creator_ai_fullname: Opus 5. |
| 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” — nickname plus version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the actual filename caffeic_acid_phenethyl_ester_2026-0910-0002_Opus_QRS.html. |
| 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. | 🟢 | All ten keys are single-space separated with no trailing whitespace; git_issue: 5977 and git_user: evipedia-4 are unquoted as required. |
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 &) |
🟢 | Line 22: “Caffeic Acid Phenethyl Ester for Health & Longevity - 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 &) |
🟢 | Line 417 matches the ER canonical_topic with the ampersand encoded. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 09/10/2026, from qrs_creation_date 2026-0910-0248. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: Opus 5. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | The header holds only the title and the template subline; no alternate-names line despite the ER carrying five. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses ER 536–542: mechanism, absence of isolate trials, extract-only human data, allergy harm, origin-dependent content. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 52 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Four claims map to ER 536, 538, 542 and 542 respectively. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “propolis”, “NF-κB” and “polyphenol” are rendered as “bee resin”, “a central inflammatory control system” and are avoided entirely. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No study, author, year or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind in the lede. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All ten items trace to the ER “Populations who should avoid” list (ER 369–379) within that section. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Complete: all nine ER bullets are represented, with the final combined bullet split into “Anyone under 18” and “Active cancer treatment without oncologist sign-off”. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Ten <li> elements inside the stop_items span (lines 572–589). |
| 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. | 🟢 | ER rationale clauses are stripped throughout (“given documented cross-reactivity”, “where no human safety data of any kind exist”, “given wholly uncharacterized human clearance”, “where contaminant clearance is impaired”). |
| 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). | 🟢 | Retained: INR 2.0–3.0 and the three-month instability window, the 14-day pre-procedure window, Child-Pugh Class B or C, CKD stage 4 or 5 with (below 30 mL/min/1.73 m²), age 18. |
| 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. | 🟢 | The ER uses no ranking notation here; the only parenthetical retained is a numeric threshold, carried without bare symbols. |
| 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. |
🟢 | The ER names nine such populations, and the section is correctly populated rather than empty. |
| 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. <!– empty: ER names no population that should avoid the intervention –> | N/A | The section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All eleven items are the ER interaction bullets at ER 345–365. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Eleven of the ER’s twelve interaction bullets are carried; “Cytotoxic chemotherapy and radiotherapy” is correctly omitted because it is an absolute contraindication already in the stop gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eleven <li> elements inside the caution_items span (lines 597–622). |
| 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 is the drug-class label plus its example list; every ER rationale sentence (“caution”, “monitor”, mechanism, INR-recheck advice) is stripped. |
| 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). | 🟢 | All eleven parenthetical drug lists are preserved verbatim from the ER bullets. |
| 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. | 🟢 | The ER parentheses are plain comma-separated drug lists; no ranking symbols appear. |
| 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. |
🟢 | The ER lists twelve interactions, and the section is correctly populated. |
| 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. <!– empty: ER names no interaction that changes how the intervention is used –> | N/A | The section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three cells trace to the ER Therapeutic Protocol bullets at ER 403, 405, 413, 415 and 417. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, dosing frequency and timing are the only three executable aspects in that section; the remaining bullets are competing approaches, pharmacology and modifying factors. |
| 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 | The ER supplies three distinct actionable aspects, so no set is unused. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine spans populated; the ER caveat that no isolate protocol exists is carried into action_1_sub. |
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 | 🟢 | Inflammation, glycemic/lipid and upper respiratory symptoms are the only endpoints for which the ER gives a time course (ER 193, 460, 490). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Inflammation first (largest pooled effect, SMD −1.73, ER 169), then the cardiometabolic markers, then the local upper respiratory effect. |
| 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 | Three distinct aspects exist in the ER, so no set is unused. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine spans populated; values 8–12 weeks, 8–24 weeks and 3 days all appear in 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 | The ER provides time-to-effect information, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All items are ER Expected Benefits subsection headings (ER 165–249). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 544–562. |
| 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. | 🟢 | Semicolon-separated noun phrases only; no magnitudes, confidence intervals or “⚠️ Conflicted” markers carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in either benefit tier. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | The ER has no High or Medium benefits; both spans are emptied and set to style=”display: none” (lines 544–545). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All items are ER Potential Risks & Side Effects subsection headings (ER 277–325). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 634–651. |
| 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. | 🟢 | Patch-test percentages, case-report detail and mechanism sentences from the ER are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any risk tier. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | The ER has no High risk; the span is emptied and set to style=”display: none” (line 634). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER Monitoring Protocol & Defining Success biomarker table (ER 492–503). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All ten ER biomarkers present, with targets carried verbatim, including the eosinophil and uric-acid safety markers. |
| 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. |
🟢 | Line 811 condenses ER 490, including the weekly warfarin clotting check for the first month. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Items are the ER’s “Qualitative markers worth tracking alongside the labs” list (ER 505–512). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present, verbatim. |
Issues 10/09/2026 03:02
Pass rate 100.00%. No issues found.
Issues 10/09/2026 02:55
- 1.3 — Cancer-treatment contraindication narrowed: Contraindication item 10 (QRS line 587) reads “Cytotoxic chemotherapy or radiotherapy without oncologist sign-off”, narrowing the ER’s broader avoid-population “anyone receiving active cancer treatment without oncologist sign-off” (ER line 379).
- 2.15 — Colloquial “dental work”: Contraindication item 5 (QRS line 582) uses the consumer-grade “dental work” in place of the ER’s own “elective surgical or dental procedure involving bleeding risk” (ER line 375).
Fixes 10/09/2026 02:55
- 1.3 — Cancer-treatment contraindication restored: Changed the tenth contraindication from “Cytotoxic chemotherapy or radiotherapy without oncologist sign-off” to “Active cancer treatment without oncologist sign-off”, restoring the ER’s full avoid-population.
- 2.15 — Colloquial “dental work” replaced: Changed the fifth contraindication from “Within 14 days of elective surgery or dental work with bleeding risk” to “Within 14 days of elective surgical or dental procedures with bleeding risk”.