Portfolio maintenance
Educational work by a pre-medical student — not medical advice. Not a clinical protocol, prescription, or patient handout, and not for patient care. See DISCLAIMER.
Recorded 29 October 2026. This is a maintenance process, not a claim that future reviews have already occurred.
Before revising a clinical statement
- Identify the exact file, statement, population and source. Check whether the source is a guideline recommendation, consensus statement, general clinical knowledge, context-dependent practice or a synthetic application.
- Verify bibliographic identity, public source availability and the relevant passage. A DOI alone does not prove peer review, accuracy or applicability. Record the scope actually checked.
- Preserve recommendation strength and population limits. Do not turn illustrative patient values into universal treatment targets or software checks into clinical validation.
- Record the correction and update affected links and file manifests. Preserve historical exports as dated snapshots unless they are explicitly regenerated.
- For specialist review, record reviewer permission, qualifications, date, exact scope and unresolved findings. Do not claim review or endorsement without evidence.
When to recheck
Recheck affected sources when a guideline is updated, a citation is corrected or retracted, a public link fails, software behavior changes, or a reviewer identifies an unsupported claim. Before reusing a case in a new context, reassess its population and assumptions. No automated clinical surveillance is represented here.
Suggesting a correction
Use the repository’s evidence-correction issue form with a file/section, the disputed statement, a public source and a concise explanation. Do not submit patient information, charts, confidential material or private institutional documents. Feedback is a request for review, not independent sign-off.
Publication boundaries
The public library contains six clinical educational projects and an additional MCAT study app. Two working repositories remain private for separate substantive review. No clinical shadowing notes or observations are used. Historical Git commits and external publications have separate version histories; a website update does not silently correct them.