Suggest an edit
Every record has a form. Propose a change with a source, say who you are, declare any conflict, and it becomes a GitHub issue a maintainer can turn into a merged edit. Organisations can update their own records the same way.
Three ways in
- The form on any page. Open “Suggest an edit” in the sidebar, choose the field, paste the proposed value and a source URL, add your name and a way to verify you. It opens a prefilled GitHub issue; you submit it with a free GitHub account.
- Edit the record directly. The same box links to the exact line in the repository. GitHub will fork and open a pull request for you. Run
npm testif you can; the build fails on a bad id or a missing source. - Email is not a channel. Everything goes through the public issue tracker so the discussion and the source are visible.
For companies and institutions
You may update your own record: website, headquarters, products and their stage, programmes, links. Facts only; no promotional language, no unsourced superlatives, no removing negative trials or withdrawals (those belong in the record and in the Failure museum). Identity is verified by a message from your official domain or an official account. The merged record names your organisation in its provenance line so readers know who wrote it.
What happens next
- Triage within a week. If a source is missing we ask for one; unsourced changes are not merged.
- The issue is assigned a review track (clinical, scientific, regulatory, patient advocate, organisation self-edit). Tracks are listed in REVIEWERS.md.
- Merged changes appear on the site at the next deploy and in the changelog. Factual corrections are also logged in
CORRECTIONS.md. - Conflicts of interest are displayed next to review badges and in provenance lines.
Licence
Contributions are published under CC BY 4.0 (data) and MIT (code). Submitting the form confirms you agree.