Audit: QRS - Chinese Hawthorn for Health & Longevity
Audit conducted on 21/08/2026 12:21 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. | 🟢 | Spot-checked every span: protocol doses (ER 372, 374, 380, 384), time-to-effect (ER 429, 164), all 13 monitoring targets (ER 461–473), cadence (ER 455, 457, 473), 9 contraindications (ER 322, 336–348), 9 interactions (ER 314–332), benefit/risk tiers (ER 150–202, 222–294) and the qualitative list (ER 477–485). |
| 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. | 🟢 | ER’s hedges are carried: “though trials disagree” mirrors ER 509; “claims rest on animals and cells” mirrors ER 509; “no reduction in cardiac events, with displacement risk” keeps the ER heading (ER 256). |
| 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”). | 🟢 | Pregnancy/breastfeeding stays an absolute contraindication; camphor stays an absolute contraindication (ER 322) rather than being demoted to 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. | 🟢 | Nothing from ER Benefit-Modifying Factors (ER 207–215) or Risk-Modifying Factors (ER 299–309) is surfaced in the gates or risk card; gates come only from ER Key Interactions & Contraindications. |
| 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 (e.g., “Dr. Willmar Schwabe” from ER 378 is not surfaced). |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attribution appears anywhere 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. | 🟢 | The sheet reproduces the ER’s sceptical, species-aware framing (European relatives vs. Crataegus pinnatifida) without adding enthusiasm. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and explicit decision gates give the reader what is needed to act, while the evidence limits are stated plainly. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Every span is a noun phrase or descriptive statement; no prescriptive verbs. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Doses and thresholds are reported as what trials and pharmacopoeias used, not as instructions. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommend”, “advise”, “should”, or “we suggest” in any populated span. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns and no imperatives in any populated span. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Abbreviations from the ER table are expanded in full (LDL-C, HDL-C, ApoB, HbA1c, ALT, hs-CRP, NT-proBNP); the At-A-Glance uses “heart attacks”, “blood fats”, “mislabeled product”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every gate, benefit, risk, and monitoring entry is a single condensed phrase; no sentence-level prose outside the At-A-Glance and cadence line. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed across all populated spans. |
| 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. | 🟢 | Functional-optimal targets (e.g., triglycerides below 100 mg/dL, ALT below 20/17 U/L) rather than conventional disease cut-offs. |
| 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. | 🟢 | Weekly home blood-pressure and pulse logging, a 13-marker panel, and split dosing with meals all assume a willing, effortful reader. |
| 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. | 🟢 | The monitoring burden and the ApoB/NT-proBNP additions are well beyond general-population expectations. |
| 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 displacement hazard and the species-mismatch problem are given weight proportionate to a self-directed supplement user. |
| 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 “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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | “gastrointestinal complaints”, “myocardial infarction”, “orthostatic hypotension”, “phytobezoar” — clinical register throughout the card body. |
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 verified at lines 446, 490, 536, 631, 661, 858, 567, 597; tier labels at 540/545/551/557 and 634/638/645/651; column headers at 665–667. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Full variable set present: page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), benefits_×4, stop_items, caution_items, risks_×4, marker_1–13 (name/target/why), monitoring_cadence, qualitative_item_1–5. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The non-variable template spans (website="evidence_review", website="full_review", website="audit"), the CSS block, and the footer disclaimer are untouched. |
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 ER section mapped onto the QRS is empty — Benefits, Risks, Interactions/Contraindications, Protocol, and Monitoring are all populated in the ER. |
| 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 cells reuse ER bold labels verbatim: “Standardized extract, European model” (ER 372), “Whole-fruit, Chinese model” (ER 374), “Time of day” (ER 380); monitoring row labels reuse the ER table’s Biomarker column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label is shortened or reworded; the only change is expansion of the ER’s abbreviations in the “Why” column, which is not a label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji in the file; the ER’s tier emojis and “⚠️ Conflicted” markers are correctly dropped in favour of CSS palettes and bold tier labels. |
| 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 entry is condensed to a single phrase and the template’s one-page layout (A4 @page rule, 9–11pt scale, two-column gates) is intact; content volume is the minimum the completeness items (8.2, 9.2, 14.2) permit. |
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, immediately after <!doctype html> on line 1 and before 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 lead-in text on line 2 sits before the opening delimiter. |
| 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 its values are repeated in the body except the creation date and model name, which are required by 6.3 and 6.4. |
| 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, 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: chinese_hawthorn_2026-0821-1033_Opus_ER.md — matches the ER on disk. |
| 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-0821-1157. |
| 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: qrs_filename: chinese_hawthorn_2026-0821-1033_Opus_QRS.html — matches the file 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-verified across all eleven keys; no stray whitespace or unnecessary 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: “Chinese Hawthorn for Health & Longevity - Quick Reference Sheet”, matching ER frontmatter 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: “Chinese Hawthorn for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/21/2026”, the correct reformat of 2026-0821-1157. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter. |
| 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’s fixed subline; the ER’s “Also known as” list (ER 31) is 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 |
🟢 | Lines 434–438 compress ER 509–511 into the four decision-relevant facts: what is proven, in which species, how large, and where the real hazard sits. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | European relatives / exercise tolerance / no fewer events → ER 509; blood pressure and lipids → ER 509; animals and cells → ER 509; harms mild and the displacement and mislabelling hazards → ER 511. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “heart attacks”, “blood fats”, “animals and cells”, “mislabeled product” — no acronyms, no clinical classifications. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, sample size, or p-value. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | Direction only (“falls modestly”, “improve”); no numbers. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items trace to ER 312–348. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven “Populations who should avoid” bullets (ER 336–348) are present, with ER 340 correctly split into two items, plus the camphor absolute contraindication (ER 322). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Nine <li> elements, lines 570–592. |
| 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. | 🟢 | The ER’s trailing rationales are stripped (“where symptom-level evidence cannot substitute for guideline therapy”, “until the cardiac regimen is stable”, “on preclinical uterine-stimulation data”); no dash-trailing clause survives. |
| 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). | 🟢 | “NYHA Class IV”, “second- or third-degree”, “below 50 beats per minute”, “below 100 mmHg”, “within 90 days”, “(raw or dried whole fruit, not standardized extracts)”, “(apple, pear, peach, almond)” all preserved; only the ER’s plain-language glosses are dropped. |
| 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 uses no ranking notation inside parentheses in Key Interactions & Contraindications. |
| 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 avoidance populations, and the section is correspondingly populated. |
| 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 nine items trace to ER 314–332. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Nine of the ER’s ten interaction bullets appear; the camphor bullet (ER 322) is correctly excluded because it sits in the Contraindications gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Nine <li> elements, lines 600–621. |
| 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 a bare noun phrase; the ER’s mechanism sentences and mitigation instructions (“Home pressure and pulse logging for 4 weeks manages it”, “a 7-day washout precedes elective surgery”) are 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). | 🟢 | Named example drugs are carried from the ER bullet bodies: metoprolol/amlodipine/lisinopril/losartan, isosorbide mononitrate/sildenafil, warfarin/apixaban/clopidogrel, pseudoephedrine/phenylephrine, and the supplement and lifestyle lists. |
| 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 uses no ranking notation inside parentheses in Key Interactions & Contraindications. |
| 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 ten interactions, and the section is correspondingly 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. | 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 ER Therapeutic Protocol (ER 370–394). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The two competing dose routes (ER 372, 374 — presented by the ER as alternatives at ER 376) and timing (ER 380) are the three load-bearing implementation decisions. |
| 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 more than three actionable aspects; 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. |
🟢 | Nine spans populated: 900–1,800 mg at 18.75% oligomeric procyanidins (ER 372); 9–12 g dried fruit as decoction, stir-fried slices, or granules (ER 374); with or just after the two largest meals, split two or three times daily (ER 380, 384). |
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 | 🟢 | Heart-failure symptoms, blood lipids, and blood pressure — the only three time-to-effect windows the ER states (ER 429, corroborated at ER 164). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Heart failure is the ER’s only High-tier benefit (ER 150–152); lipids and blood pressure are Medium (ER 158–166), and are ordered as the ER orders them. |
| 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; 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. | 🟢 | “8 weeks or later” and “8 to 16 weeks” come from ER 429; the triglyceride 12-week note from ER 164; the “not before 8 weeks” caveat from ER 429. |
| 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 explicit time-to-effect data at ER 429, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All four tiers map one-to-one onto the ER headings at ER 150–202. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated, lines 538–560. |
| 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-joined list of the ER’s own benefit headings; no Magnitude figures (ER 156, 164, 170, 178, 184) are carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefits span. |
| 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 needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All four tiers map one-to-one onto the ER headings at ER 222–294. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated, lines 633–655. |
| 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 reproduces the ER’s risk headings only; the event counts and hazard ratios at ER 228, 234, 242, 248, 254, 260, 268, 274, 280 are all 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 risks span; the ER’s glosses (“a spinning sensation”, “a hardened mass of plant fiber”) are stripped. |
| 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 needs hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | The table reproduces the ER Monitoring Protocol & Defining Success biomarker table (ER 459–473). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All thirteen ER rows are present in ER order, with targets and rationales carried across; abbreviations are expanded rather than dropped. |
| 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. |
🟢 | Lines 848–852 condense ER 455, 457 and the digoxin note at ER 473: baseline, weekly home readings, full panel at 12 weeks, then every 6 to 12 months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Taken from the ER’s “Qualitative markers worth tracking alongside the labs” list (ER 475–485). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers are present, verbatim and in ER order, at lines 861–888. |
Issues 21/08/2026 12:21
Pass rate 100.00%. No issues found.
Issues 21/08/2026 12:09
- 12.3 / 13.3 — Conflicted qualifier not stripped:
benefits_high(line 540),benefits_medium(line 546), andrisks_medium(line 639) each end with a trailing “— conflicted” qualifier, which the section preambles declare redundant because the tier label already encodes evidence strength.
Fixes 21/08/2026 12:09
- 12.3 / 13.3 — Conflicted qualifier stripped: Removed the trailing “— conflicted” from
benefits_high,benefits_medium, andrisks_medium, leaving the tier label alone to carry the evidence-strength signal.
Issues 21/08/2026 12:07
- 1.3 — At-a-glance drops blood-pressure hedge: [at_a_glance] (line 435) asserts “Blood pressure falls modestly and blood fats improve”, while the ER Conclusion (line 509) qualifies it as “Blood pressure falls modestly, though the trials disagree”; omitting the hedge strengthens the ER claim.
Fixes 21/08/2026 12:07
- 1.3 — At-a-glance blood-pressure hedge restored: [at_a_glance] now reads “Blood pressure falls modestly, though trials disagree, and blood fats improve”, matching the ER Conclusion’s qualification; the closing clause was tightened to “replacing proven treatment” to keep the summary within the 60-word budget (now 59 words).