Audit: QRS - Vinpocetine for Health & Longevity

Audit conducted on 13/09/2026 10:17 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 the `Therapeutic Protocol` bullets, time cells to the `Time to effect` bullet in `Practical Considerations`, benefit/risk tiers to the `Expected Benefits` and `Potential Risks & Side Effects` headings, gates to `Key Interactions & Contraindications`, and the nine markers plus cadence to `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.	🟢	No ER hedge is dropped or hardened; the animal-only reproductive finding stays “Animal pregnancy loss” in [at_a_glance] and sits in the Speculative risk tier, matching the ER.
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 eight ER “Populations who should avoid Vinpocetine” bullets are carried as Contraindications, not downgraded to cautions; warfarin stays a contraindication and is correctly removed from the anticoagulant and CYP2C9 interaction example lists.
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 `Benefit-Modifying Factors`, `Risk-Modifying Factors`, `Risk Mitigation Strategies` or `Emerging Research` is surfaced in the gates; the gates draw only on `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, citations, expert names, NCT identifiers or brand names anywhere.
1.6	The QRS does not introduce new attributions.	🟢	No attributions are present beyond the fixed template AI4L link and the source-ER subline.

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 even-handed treatment of the split cognitive evidence and the under-dosing hypothesis.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Technical precision in the gates and monitoring table sits alongside plain-language framing in [at_a_glance] and the qualitative items.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what the evidence and protocols show, not as instructions issued to an individual.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives or advisory verbs; [monitoring_cadence] describes the ER’s monitoring schedule rather than directing the reader.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No instance of “recommend”, “advise”, “should” or “must” in the document’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the rendered content.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained ER glosses where space allowed (“Alanine aminotransferase (a liver enzyme)”, “Montreal Cognitive Assessment (a 30-point cognitive screen)”, “human chorionic gonadotropin (the pregnancy hormone)”); remaining technical terms are the ER’s verbatim bold labels required by 4.2/9.4.
2.8	Information is presented in a concise and very compact manner	🟢	Tier lists are semicolon-joined single-line entries and gate items are stripped to the key fact.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct address 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.	🟢	Content assumes a self-directed user, e.g. the supplement-content risk carried at Medium and the reproductive gating test in the monitoring table.
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.	🟢	Three-times-daily dosing with meals, a nine-marker baseline panel and six qualitative trackers all presume a willing, effortful audience.
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.	🟢	Density of the monitoring panel and the twelve-item interaction gate exceed general-population framing.
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] foregrounds the two facts that matter most to a self-directed user — that ordinary doses may be too low, and that product content is unreliable.
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.	🟢	The string “anti-aging” does not occur; the header uses the ER’s canonical “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 of administration is given formally (“Standard oral regimen”, “intravenous doses”); no “pill”, “taken by mouth”, “shot” or “bad reaction” appears, including in the lede.

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 verified byte-for-byte against the template at lines 445, 489, 533, 565, 585, 609, 638, 642-644 and 804, with the eight tier labels intact at lines 536, 540, 546, 554, 612, 616, 622 and 629.
3.2	All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS.	🟢	The template’s 38 span occurrences map to the QRS’s 67 once `marker_#_*` expands to nine rows (27) and `qualitative_item_#` to six; no template span name is missing.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Template lines 12-409 (head, CSS, override link) are byte-identical to QRS lines 15-412 apart from the `<title>`; the three non-variable `website="evidence_review"`, `website="audit"` and `website="full_review"` spans and the footer disclaimer are unchanged.

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 drawn on by 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 oral regimen”, “Split dosing rather than a single dose” and “Best time of day” are the ER’s bold labels verbatim; all twelve interaction labels likewise (“Anticoagulants”, “P-glycoprotein substrates”, “QT-prolonging medicines”, etc.).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels are lifted from the ER’s own wording inside the `Time to effect` bullet (“Cognitive and functional change”, “perfusion and rheological changes”, “the hearing study”); marker names match the ER biomarker table.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code point occurs anywhere in the file; the ER’s “⚠️ Conflicted” markers on two headings 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.	🟢	Condensation was applied throughout: the ER biomarker table’s fourth “Context/Notes” column is dropped, every interaction’s “caution;”/”Mitigation:” clause is stripped, example drug lists are trimmed to three, and parenthetical glosses are shortened; residual length is driven by the completeness mandates of 9.2, 13.3, 14.2 and 15.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 form one HTML comment immediately after the doctype at line 1, ahead of the template banner comment at 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 `---` at line 3 and 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 and not duplicated in the header, footer or any span.
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.	🟢	All nine values are trimmed and unquoted except `duration: "00:03"`, which contains a colon and therefore requires quoting.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: vinpocetine_2026-0913-0716_Opus_ER.md`, matching the ER’s own `filename` frontmatter value.
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.9.11`, 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-0913-1009`, 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 carrying 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 context-window or other qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: `qrs_filename: vinpocetine_2026-0913-0716_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; only the colon-bearing `duration` is quoted.

#	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: “Vinpocetine for Health & Longevity - Quick Reference Sheet”, matching the ER’s `canonical_topic` with the ampersand entity-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: “Vinpocetine for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421 shows 09/13/2026, the correct MM/DD/YYYY rendering of `qrs_creation_date: 2026-0913-1009`.
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 block (lines 415-428) carries only the title and the template’s fixed subline; the ER’s “Also known as” list is not reproduced.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Four sentences covering mechanism, the strongest signal, the contested cognitive claim with the under-dosing caveat, and the two decisive hazards — the decision-relevant core of the ER `Conclusion`.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to the ER `Conclusion` paragraphs at lines 507 and 509: the vasodilator/anti-inflammatory mechanism, the disability-not-mortality signal, the split memory evidence with ordinary doses possibly too low, and the animal reproductive plus product-content concerns.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “stroke”, “brain blood vessels”, “pregnancy loss” and “product content” are all ordinary usage, and the ER’s clinical classifiers (“acute ischemic”, “embryo-fetal”) are avoided here.
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 relative risks (0.80, 0.67) and confidence intervals are absent; the signal is described qualitatively.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All eight items come from that section’s “Populations who should avoid Vinpocetine” list at ER lines 352-359.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight ER bullets are present, in ER order, with none added or omitted.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight `<li>` elements inside the [stop_items] span; HTML parses balanced.
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.	🟢	Trailing rationale stripped throughout: “Breastfeeding, for which no safety or transfer data exist” → “Breastfeeding”; the demyelinating item drops “, given the myelin-repair signal in cell work”.
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 C”, “<90 days”, “platelet count below 50 × 10⁹/L”, “resting systolic blood pressure below 100 mmHg” and “in a remission phase” all retained; only the ER’s explanatory glosses inside the parentheses were trimmed.
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 bullets contain no ranking notation; the only symbols are absolute thresholds (“<90 days”, “below 50 × 10⁹/L”) that are self-interpreting.
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 does identify such populations and the section is correctly populated rather than left 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 twelve items come from the bulleted interaction list at ER lines 326-348.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All twelve ER interaction bullets are represented; warfarin is correctly withheld from the anticoagulant and CYP2C9 example lists because it is carried as a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Twelve `<li>` elements inside the [caution_items] span; HTML parses balanced.
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 “caution;”/”monitor;” rationale and every “Mitigation:” clause is stripped; each item is reduced to the drug-class label plus its parenthetical examples.
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 item keeps a parenthetical example list; longer lists were trimmed to three representatives (dipyridamole, fexofenadine, hydrochlorothiazide, domperidone, nattokinase, hibiscus dropped) but none was dropped entirely.
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 parentheses contain plain comma-separated drug names only, with no ranking notation.
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 identifies twelve such entries 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 action sets derive from the ER `Therapeutic Protocol` bullets at lines 383, 389 and 393.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, dose splitting and timing are the three self-administrable levers; the remaining ER bullets are either clinician-administered (the infusion protocol), descriptive (half-life, competing approaches) or modifier notes (genetics, sex, age, baseline markers).
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 `Therapeutic Protocol` section lists eleven bullets, so 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 cells carry substantive ER-derived content, e.g. action_1 “5–10 mg three times daily” with “With meals, totalling 15–30 mg/day, as used in the dementia and chronic-ischemia trials”.

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	🟢	The ER’s `Time to effect` bullet names exactly three horizons — perfusion/rheological within a single infusion or the first days, cognitive and functional at 12–16 weeks, and hearing not before six months — and all three are carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	time_1 “Cognitive and functional change” attaches to the High-tier benefit (reduced death or dependency after acute ischemic stroke); time_2 perfusion/rheology and time_3 hearing are both Low-tier, ordered as the ER lists them within that 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 provides three distinct time-to-effect aspects, so 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 cells populated, e.g. time_3 “Hearing” / “6 months” / “The hearing study saw nothing before six months.”
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 does provide 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 twelve benefit entries correspond one-to-one with the ER’s `Expected Benefits` sub-headings at lines 160-228.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 535, 538, 544 and 552.
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 entry is the ER heading alone; no Magnitude figures, evidence descriptions or mechanism text carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any benefit tier; the “⚠️ Conflicted” marker on the chronic-cerebrovascular cognition heading is stripped as required by 4.4 and 12.3.
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.	N/A	All four benefit tiers have items in the ER, 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 ten risk entries correspond one-to-one with the ER sub-headings at lines 254-306.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 611, 614, 620 and 627.
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 entry is the ER heading alone; the incidence figures (headache 7.9%, diplopia 5.2%, the hundredfold content range) are correctly omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any risk tier; the “⚠️ Conflicted” marker on the sleep-disturbance heading is stripped as required by 4.4 and 13.3.
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.	N/A	All four risk tiers have items in the ER, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Every row derives from the biomarker table in the ER `Monitoring Protocol & Defining Success` section at lines 466-476.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All nine ER biomarkers are present in ER order with their targets intact: blood pressure, full blood count with differential, platelet count, alanine aminotransferase, creatinine with eGFR, fibrinogen, hs-CRP, Montreal Cognitive Assessment and hCG.
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.	🟢	Reproduces the ER’s ongoing-monitoring paragraph (line 464) and adds the pregnancy-test timing from the hCG row’s Context/Notes; no placeholder text remains.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	All six items come from the “Qualitative markers worth tracking alongside the laboratory set” list at ER lines 480-485.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All six ER qualitative markers are carried verbatim and in ER order, from word-finding through unexplained bruising.

Issues 13/09/2026 10:17

Pass rate 100.00%. No issues found.