Audit: QRS - Weeping Forsythia for Health & Longevity
Audit conducted on 15/08/2026 16:01 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 83 |
| Failed | 0 |
| N/A | 10 |
| 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. | 🟢 | Every populated span traces to ER text: protocol cells to ER lines 331/333/335/341, time cells to lines 205/343/386, benefits/risks to the ER tier headings, gates to lines 284-309, monitoring table to lines 416-421, qualitative items to lines 425-429. |
| 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 hedged ER passage is carried into the QRS in a firmer form; at-a-glance keeps “come almost entirely from rodents” and “narrow and episodic” from ER lines 451. |
| 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”). | 🟢 | The ER avoid-list (lines 302-309) is carried into the Contraindications gate at full strength; no caution item is promoted to a contraindication or vice versa. |
| 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 only from the ER avoid-list, Key Interactions only from the ER interaction bullets, and no Benefit-/Risk-Modifying Factor (ER lines 203-215, 271-279) appears anywhere in the QRS. |
| 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. | 🟢 | The QRS carries no PMIDs, no NCT identifiers, no author names and no brand names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | Only generic ER-sourced references remain (“the largest trial”, “the pivotal trial”, “the first-stage human programme”), all present in ER lines 333/335/386. |
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. | 🟢 | Matches the ER’s measured, evidence-weighted register, including its British spelling (“standardised”, “oestrogen”, “diarrhoea”, “paediatric”). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Numbers are given where the ER has them (7 vs 10 days, 6-15 g, 0.35 g capsules) alongside plain-language framing. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Protocol cells describe what was studied (“the schedule used in the pivotal trial”) rather than instructing. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Cadence and protocol text is stated descriptively (“Dosing after food is standard”), with no imperative addressed at a patient. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instance of “recommend”, “advise”, “should” directed at a user anywhere in the populated spans. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | Verified: no second-person pronoun occurs in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms that remain (Child-Pugh class, Oleaceae, P-glycoprotein) are decision-relevant gate content taken verbatim from the ER, and Oleaceae carries its ER gloss “(olive-family)”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tier lines collapse multiple ER sub-headings into a single semicolon-separated line; gate items are noun phrases without rationale. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-file search; the document is written entirely in the third person. |
| 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 biomarker targets (hs-CRP < 0.5 mg/L, ALT 10-26 U/L) rather than conventional laboratory cut-offs signal the optimizer audience. |
| 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. | 🟢 | Presents a simmered decoction, thrice-daily dosing and a repeat laboratory panel without softening for convenience. |
| 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 consumer-simplified “just take a capsule” framing; the three distinct preparation routes are kept side by side. |
| 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. | 🟢 | At-a-glance states the decisive point for an optimizer directly: the realistic place is “narrow and episodic, not a standing longevity routine”. |
| 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 at-a-glance uses “standing longevity routine”. |
| 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Uses “adverse events”, “capsules”, “decoction”, “gastrointestinal adverse reactions”; the phrase “Over-the-counter fever reducers” is the ER’s own label (ER line 288). |
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 fixed strings match the template character for character, including “Risk & Side Effects” (line 574) and the subhead “Time to effect” (line 477). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template variable names are present; the indexed placeholders marker_#* and qualitative_item# are expanded to marker_1..6 and qualitative_item_1..5 as intended. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-variable spans (website=”evidence_review”, website=”audit”, website=”full_review”) are intact and empty/unchanged, as are the stylesheet link and the template’s structural comments. |
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 source ER section mapped by this QRS is empty; every mapped ER section is populated. |
| 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 traditional dose”, “Standardised formula dose”, “Purified single-compound dose”), all eight interaction labels, and all five qualitative labels are the ER’s bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Monitoring markers reuse the ER table’s biomarker names exactly; the ER supplies no bold labels for the time-to-effect cells, so the three descriptive cell labels are the minimum required by the template. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Full-file search returns no emoji; the ER’s 🟩/🟥/🟨 tier markers and the “⚠️ Conflicted” flags were correctly dropped. |
| 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. | 🟢 | Each section is condensed to the template’s budget: two four-line tier lists, eight one-line gate items per gate, six table rows, five qualitative one-liners, and a single-sentence-pair cadence. |
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 comment opens immediately after “<!doctype html>” on line 1 and precedes the template comment on line 16. |
| 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 “—” on line 3, closing “—” on line 13; the preceding title text on line 2 sits outside the block. |
| 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; none of the frontmatter values is repeated in the header, footer 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:03" is quoted, and it must be because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: weeping_forsythia_2026-0825-1426_Opus_ER.md, matching the ER’s own filename field. |
| 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 version badge at the top of QRS.md. |
| 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-0815-1552, in the required format. |
| 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” is a single word with no version or qualifier. |
| 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” is nickname plus version number with no trailing qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 states weeping_forsythia_2026-0825-1426_Opus_QRS.html, which is the file’s actual name on disk. |
| 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. | 🟢 | Re-checked across all ten keys: single space after each colon, no trailing whitespace, no stray 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 &) |
🟢 | Line 22: “Weeping Forsythia for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded. |
| 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: “Weeping Forsythia for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/15/2026”, the correct reformatting of 2026-0815-1552. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter value. |
| 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 carries only the template’s title and subline; the ER’s “Also known as” list was correctly not carried over. |
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 lines 449-451 to what it is, what the evidence supports, where the evidence is weak, and how it should realistically be used. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 54 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Four claims map to four distinct Conclusion passages: two-thousand-year fever remedy (line 449), shorter illness started in the first two days (line 451), rodent-only inflammation/liver/weight/bone data (line 451), narrow and episodic rather than a standing longevity routine (line 451). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “influenza-like illness” and “rodents” are the only semi-technical words and both are in common use. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, sample size or p-value appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | The ER’s risk ratios and confidence intervals are deliberately absent; only the directional “shorter, milder” remains. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Sourced from the “Populations who should avoid Weeping forsythia” list inside that ER section (lines 300-309). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All eight ER avoid-list entries are present, in ER order, with no additions. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Eight discrete <li> elements inside the span (lines 542-549). |
| 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. | 🟢 | Each item is a bare noun phrase; the ER’s connective wording is trimmed (“maintained on ciclosporin or tacrolimus” → “on ciclosporin or tacrolimus”) with no dash-trailing 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). | 🟢 | Retains “particularly the first 12 weeks”, “(olive-family)” plus olive/ash/privet, “Child-Pugh Class B or C”, “below 30 mL/min/1.73 m²”, and “outside paediatric-labelled formulas”. |
| 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. | N/A | The ER’s avoid-list uses no ranking notation inside parentheses. |
| 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 eight such populations, and the section is correspondingly 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. | 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 eight items map to the eight interaction bullets at ER lines 284-298. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | No ER bullet is duplicated across the two gates; the immunosuppressant interaction and the transplant-recipient contraindication are separate ER entries with different scope. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eight discrete <li> elements inside the span (lines 557-564). |
| 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. | 🟢 | Every bullet’s mechanism, mitigation and citation text is stripped; only the drug-class label and its example list remain, with no dash-trailing clauses. |
| 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). | 🟢 | The six ER-supplied drug lists are preserved verbatim; for the two ER bullets whose labels carry no parenthetical, the named agents from the bullet body are retained (“honeysuckle flower, andrographis, elderberry, echinacea, zinc, berberine”; “cold-water immersion, scheduled fever-reducer protocols”), which is what makes those two items interpretable. |
| 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. | N/A | The ER’s interaction bullets use no ranking notation inside parentheses. |
| 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 names eight such interactions, and the section is correspondingly populated rather than empty. |
| 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 | The section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three cells derive from the ER Therapeutic Protocol section (lines 331-341). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The three dosing routes the ER leads with — traditional decoction, standardised thirteen-herb capsule, purified forsythin — are the only bullets that specify an executable dose. |
| 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 and all three sets are used. |
| 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 carry substantive ER-derived content; values give the dose (6-15 g; four 0.35 g capsules three times daily; forsythin 50/100/200 mg three times daily) and subs give preparation, duration and tolerability from the same 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 | 🟢 | Full symptom resolution (ER line 386), fever (lines 386 and 205) and steady state (line 343) are the only time-to-effect quantities the ER reports. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | The two endpoints tied to the High-tier benefit lead, with full symptom resolution (7 vs 10 days) ahead of fever, and the pharmacokinetic steady-state figure last. |
| 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 | The ER supplies three distinct time-to-effect aspects and all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine spans are populated with ER figures: “7 days (median)”, “24 to 48 hours”, “About day 3”, each with a supporting sub-line from the same ER passage. |
| 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 (lines 343 and 386), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All eight benefit sub-headings from ER lines 152-198 are represented in the matching tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present and populated (lines 521-532). |
| 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. | 🟢 | Each tier is a semicolon-separated list of the ER sub-headings alone; the ER’s Magnitude figures (RR 1.22, OR 0.47) and the “⚠️ Conflicted” qualifier are all omitted. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any of the four benefit lines. |
| 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. | N/A | The ER populates all four benefit tiers, so no span needed hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven risk sub-headings from ER lines 222-266 are represented in the matching tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present and populated (lines 576-587). |
| 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. | 🟢 | Each tier lists only the ER sub-heading text; the pooled risk ratios (0.63, 0.70) and the “⚠️ Conflicted” flag on reproductive uncertainty are correctly dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any of the four risk lines. |
| 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 | The ER populates all four risk tiers, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Table rows and cadence both come from the ER Monitoring Protocol & Defining Success section (lines 410-421). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six ER table rows are present with their ranges and rationales verbatim: hs-CRP, ALT, eGFR, complete blood count with differential, fasting glucose, oral temperature. |
| 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. |
🟢 | Carries the ER’s full cadence: baseline before the first dose, repeat at four weeks, then every three to six months, immediate repeat on rash/diarrhoea/fatigue, and no ongoing schedule for episodic use. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Taken from the “Qualitative markers worth tracking” list at ER lines 423-429. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers are present with their bold labels intact: fever curve, cough and throat symptoms, energy and daily function, digestive tolerance, sleep continuity. |
Issues 15/08/2026 16:01
Pass rate 100.00%. No issues found.
Issues 15/08/2026 15:57
- 1.1 — Invalid
&sup9;HTML entity: Line 641, [marker_4_target] writes “1.5-3.0 ×10&sup9;/L” and “< 0.3 ×10&sup9;/L”;&sup9;is not a valid HTML entity (only¹,²and³exist), so the cell renders the literal text “×10&sup9;/L” instead of the ER’s “×10⁹/L”.
Fixes 15/08/2026 15:57
- 1.1 — Invalid
&sup9;HTML entity: In [marker_4_target] (line 641) both occurrences of the non-existent entity&sup9;were replaced with the numeric reference⁹, so the cell now renders “×10⁹/L” as written in the ER.