Audit: QRS - Gymnema sylvestre for Health & Longevity
Audit conducted on 16/08/2026 18:56 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. | 🟢 | Protocol cells, time-to-effect values, benefit/risk tiers, gate items, monitoring rows and qualitative items all trace to ER Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications and Monitoring Protocol & Defining Success. |
| 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. | 🟢 | marker_9_why carries the ER’s “No established target response exists for gymnema, since pooled trials show no body-size effect” verbatim; [at_a_glance] keeps “rest on small, uneven studies” and “unproven”. |
| 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 and breastfeeding” stays in the Contraindications gate, not the Key Interactions gate; type 1 diabetes keeps the “unless supervised by the prescribing endocrinologist” qualifier. |
| 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. | 🟢 | No item from ER Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or the Risks card; all six caution items map to ER Key Interactions & Contraindications bullets. |
| 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, citations, expert names, NCT identifiers or brand names at all. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are present. |
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, non-promotional register matching the ER; the split framing “a reliable taste effect, an unproven blood-sugar benefit” mirrors the ER Conclusion. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Numeric targets in Monitoring and concrete dosing in Protocol sit alongside plain-language framing in At-A-Glance. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated descriptively (“Lozenges are taken at the moment of craving rather than on a schedule”), not as instruction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative clinical directives in any variable region; the only clinician reference is the fixed template footer disclaimer. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommend”, “advise”, “should” or “must” in any populated span. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns (“you”, “your”) anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained (Child-Pugh Class B or C, alanine aminotransferase, HOMA-IR) are load-bearing decision-gate and biomarker facts carried from the ER. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Benefit and risk tiers collapse to a single semicolon-separated line each; gate items are stripped to the key fact. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan for second-person forms; none found. |
| 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 functional ranges (fasting glucose 70–85 mg/dL, HOMA-IR < 1.0) rather than conventional clinical cut-offs, plus CGM metrics, address the optimizing reader. |
| 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. | 🟢 | Split dosing 15–30 min before the two largest meals, capped lozenge use, and a dense lab schedule assume high willingness to execute. |
| 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. | 🟢 | Continuous glucose monitoring, HOMA-IR and repeat liver-enzyme panels are 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. | 🟢 | At-A-Glance separates the reliable sensory effect from the unproven metabolic one, which is the decision-relevant distinction for an already-optimised reader. |
| 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Cards use formal terms (“Gastrointestinal discomfort”, “Hypoglycemia”); the plain-language wording in At-A-Glance is required by item 7.4 and is carried verbatim from the ER Conclusion. |
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 (lines 445, 491, 540, 569, 590, 625, 653, 657–659, 804). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names are present; the additional spans are the expected row expansions of marker_#_* (9 rows) and qualitative_item_# (6 items). |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A normalised structural diff against the template returns no differences other than the repeated Monitoring rows and Qualitative list items; <span website="..."> markers 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 source ER section that feeds the QRS is empty. |
| 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. | 🟢 | “Standard metabolic dose”, “Craving protocol (competing approach)” and “Best time of day” match the ER Therapeutic Protocol bold labels; interaction labels match the ER Key Interactions & Contraindications bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Benefit and risk items reuse the ER subsection headings verbatim (sentence-cased); monitoring row labels reuse the ER Biomarker column verbatim. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Full-text scan of the emoji code ranges returns no matches; the ER’s 🟩/🟥/🟨 and ⚠️ markers 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. | 🟢 | Every discretionary region is condensed to the key fact; the remaining volume (9 monitoring rows, 6 qualitative items, 8 contraindications) is mandated verbatim by items 14.2, 15.2 and 8.2. |
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 only preceding content is <!doctype html> on line 1. |
| 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; the preceding “QRS — Metadata (invisible, parsed by audit tooling)” text 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; no metadata value is repeated in the header, footer or any card. |
| 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: gymnema_sylvestre_2026-0825-1645_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-0816-1841. |
| 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” = nickname plus version, no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: gymnema_sylvestre_2026-0825-1645_Opus_QRS.html, matching 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 nine 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: “Gymnema sylvestre 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: “Gymnema sylvestre for Health & Longevity”, matching ER frontmatter canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/16/2026”, the correct reformatting of 2026-0816-1841. |
| 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 title and the fixed template subline; the ER’s “Also known as:” list is correctly omitted. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | All four sentences condense the ER Conclusion (lines 490–494), closing on the decision framing. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 58 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Taste blockade and chocolate/sweet-drink reduction, the small uneven metabolic evidence base, and the stomach-upset/hypoglycemia harms each map to separate ER Conclusion passages. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “blood fats”, “stomach upset”, “blood sugar falling too low”, “older diabetes tablets” in place of lipids, gastrointestinal discomfort, hypoglycemia and sulfonylureas; no acronyms. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, author, year or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | The ER’s −21.3%, 42%, SMD and confidence-interval figures are all absent. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All eight items come from the “Populations who should avoid Gymnema sylvestre” list at ER lines 323–332. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All eight ER populations are present, including “Within 14 days of scheduled surgery”, which the ER also flags as an absolute contraindication at line 321. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Eight <li> elements inside the stop_items span (lines 572–585). |
| 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 clause on pregnancy (“— no human safety data, and reported uterine-stimulant activity”) is stripped; no dash-led clause survives in any item. |
| 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). | 🟢 | “Child-Pugh Class B or C”, “above three times the upper limit of normal”, “in the past 12 months”, “under 18 years” and “Within 14 days” are all retained. |
| 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 contraindication 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 correctly 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 six items map to the ER interaction bullets at lines 309–319. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Six of the ER’s seven interaction bullets are carried; “Surgery and anaesthesia” is correctly excluded because it appears in the Contraindications gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Six <li> elements inside the caution_items span (lines 593–615). |
| 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. | 🟢 | Severity / Consequence / Mitigation clauses and the ER’s parenthetical mechanism glosses (“drugs that make the kidneys excrete sugar”, “injected drugs that slow digestion”) are all 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). | 🟢 | Every named agent is retained: glipizide/glyburide/glimepiride/repaglinide/nateglinide; metformin/empagliflozin/dapagliflozin/semaglutide/tirzepatide; the seven glucose-lowering supplements; the four hepatotoxic botanicals. |
| 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 seven 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. | 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 ER Therapeutic Protocol bullets at lines 358, 364, 368 and 372. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard metabolic dose, the competing craving protocol, and timing — the three decisions that determine format, dose and administration. |
| 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 well over three actionable aspects and all three sets are populated. |
| 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 ER-derived content; no placeholder text remains anywhere in the file. |
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 | 🟢 | Taste blockade, blood sugar and blood lipids — exactly the three horizons given in ER Practical Considerations line 415. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Taste blockade (High tier) first, then blood sugar and blood lipids, following the ER’s own ordering within the Medium tier. |
| 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 aspects and all three sets are populated. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | “Immediate” / “4–12 weeks” / “~12 weeks” with subs traced to ER lines 166 and 415. |
| 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, 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 items reuse the ER Expected Benefits subsection headings (lines 162–213). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated (lines 542–562), each tier matching the ER’s own tiering. |
| 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 single semicolon-separated line of bare benefit names; the ER’s Magnitude paragraphs and “⚠️ Conflicted” qualifiers are dropped. |
| 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 spans. |
| 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 | All four benefit tiers have items in the ER, so none needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven risk items reuse the ER Potential Risks & Side Effects subsection headings (lines 242–287). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated (lines 627–647), each tier matching the ER’s own tiering. |
| 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 is a single semicolon-separated line; the ER’s Magnitude paragraphs, case-report details and “⚠️ Conflicted” markers are 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 spans. |
| 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 in the ER, so none 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 (lines 447–457), mapping Biomarker / Optimal Functional Range / Why Measure It? onto Marker / Target / Why. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER rows are present: fasting glucose, HbA1c, fasting insulin, HOMA-IR, triglycerides, LDL cholesterol, ALT and AST, CGM metrics, body weight and waist circumference. |
| 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 794–798 carry the ER’s baseline / 8–12 week / 6 month / 6–12 month schedule plus the daily-then-twice-weekly rule for insulin or sulfonylurea users (ER line 445). |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | The six items reproduce the ER’s “Qualitative markers worth tracking alongside the labs” list (lines 461–466). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present and carried verbatim. |
Issues 16/08/2026 18:56
Pass rate 100.00%. No issues found.
Issues 16/08/2026 18:48
- 1.3 — Hypoglycemia scope broadened: [at_a_glance] (QRS line 436) says blood sugar falls too low “alongside diabetes drugs”, whereas the ER Conclusion scopes this to “insulin or older diabetes tablets” and ER line 311 states metformin, SGLT2 inhibitors and GLP-1 agonists carry “low hypoglycemia risk unless combined with insulin”.
Fixes 16/08/2026 18:48
- 1.3 — Hypoglycemia scope restored: Changed [at_a_glance] from “alongside diabetes drugs” to “alongside insulin or older diabetes tablets”, matching the ER Conclusion’s scoping. The section remains within the 60-word limit at 58 words.