Submit a Correction
ASH publishes a public errata workflow. If you find a factual, numerical, regulatory, or clinical inaccuracy on any page \u2014 here's how to flag it.
ASH commits to a public, auditable errata workflow. When a correction is accepted, it is logged on the /corrections page and surfaced in the /api/changelog JSON feed with category correction.
This page tells you what counts as a correction, what doesn't, and how to submit one through the most efficient channel for the issue type.
What counts as a correction
Factual
A claim made on the site that is demonstrably wrong against a primary source. Example: "The FDA cleared leeches in 2003" (actual: K040187, June 21, 2004).
Numerical / PMID
A PMID, DOI, sample size, year, or other number that doesn't resolve to the claimed reference. Example: PMID cited but PubMed metadata is for a different paper. ASH ran 4 PMID Integrity Sprints in May 2026 and welcomes additional spot-checks.
Regulatory
Incorrect statement about FDA / EMA / national-authority status of medicinal leeches or hirudin-class drugs in any jurisdiction. Most consequential category; handled urgently.
Clinical / safety
A risk, contraindication, or protocol detail that could materially mislead a patient or clinician. Example: missing a known absolute contraindication. Handled within 48 hours.
What doesn't count as a correction
- Disagreements about interpretation of evidence (e.g. "you graded this GRADE low; I'd grade it moderate"). Submit as a discussion instead \u2014 these inform future review cycles but don't generate errata entries.
- Style preferences (capitalization, comma placement, phrasing).
- Requests to add content that isn't on the site (instead use a feature request or open issue \u2014 see the contribution channels below).
- Disagreements with ASH's editorial stance on the drug-vs-leech distinction or Tier framing. These are deliberate editorial positions backed by the methodology page.
How to submit
Channel 1 (preferred) \u2014 GitHub Issue
The fastest path. ASH's website source is fully public on GitHub. Open an issue with the correction label.
Use the template below in the issue body. SLA: 7 days to triage, 30 days to resolve or escalate.
Channel 2 \u2014 Pull Request
If you can directly fix the file, send a pull request. ASH editorial team reviews within 14 days. Required: link to the primary source supporting your change.
Browse open PRs →Channel 3 \u2014 Email
For sensitive corrections (e.g. patient identifiers in an image you spotted), please use email. Public GitHub issues are not appropriate for PHI / PII.
corrections@hirudotherapysociety.org →Submission template
Copy and fill in below. Used for all three channels.
### Correction submission **Page URL:** https://www.hirudotherapysociety.org/... **Section / line:** (paragraph heading or quote of the exact sentence) **Category:** factual | numerical-pmid | regulatory | clinical-safety **Current text:** (quote what's currently on the page) **Proposed text:** (what it should say) **Primary source / evidence:** - URL or full citation (DOI / PMID / official document number) - For PMID corrections: PubMed link - For regulatory: official authority document URL **Why this matters:** (1-3 sentences — brief) **Submitter:** (name & affiliation, if comfortable; anonymous OK) **Conflicts of interest:** (relevant industry / consulting / clinical practice ties)
Service-level commitments
| Category | Triage | Resolution target |
|---|---|---|
| Clinical / safety | 24 hours | 48 hours |
| Regulatory | 48 hours | 7 days |
| Factual | 7 days | 30 days |
| Numerical / PMID | 7 days | 30 days |
All triaged corrections are acknowledged publicly on /corrections. Resolved corrections also appear in /api/changelog?category=correction.
Editorial accountability
ASH is a California 501(c)(3) nonprofit (EIN 92-2997844). Editorial decisions are made by the Editorial Board (see /about/board). Reviewers' credentials are visible on every page via the PageMeta component. Conflicts of interest, when present, are disclosed alongside the relevant page.