Corrections policy
Corrections and vendor response policy
A publication that cannot be corrected cannot be trusted. This page explains exactly how to move a claim, and what will not move it.
Short answer
How do you correct errors on this site?
Send the page URL, the exact sentence, and a primary source that contradicts it. Factual errors are corrected within five working days and the page's last-reviewed date is updated. Scores change when the evidence changes — new documentation, published pricing, a new certification or a self-serve developer path — and not because a vendor objects to the conclusion.
Cite as: Corrections policy, Compare Healthcare API, last reviewed 2026-09-01.
How to submit a correction
1Identify the exact claim
Quote the sentence and give the page URL. Claims are corrected at sentence level, not page level.
2Supply a primary source
Link the vendor's own documentation, pricing page, trust centre or contract language that contradicts the claim. Marketing assertions without documentation do not move a score.
3State the requested change
Say what the sentence should read instead. Requests to delete an unflattering but accurate statement are declined and, if repeated, noted publicly.
4Send it
Email the correction to the address on this page with the URL in the subject line.
5Expect a decision, not a negotiation
Factual errors are corrected within five working days. Scores change only when the underlying evidence changes, and a change is stamped with a new review date.
What we correct, and what we do not
We correct: wrong facts, out-of-date facts, misattributed quotes, broken source links, mis-stated pricing models, mis-stated certification status, and any case where we recorded something as undisclosed that is in fact published.
We do not remove: accurate limitations, accurate statements that a vendor does not publish something, our weighting choices, or conclusions a vendor dislikes. Those are arguments, not errors — and the weighting is published precisely so the argument can be had in the open.
We escalate: if a vendor supplies a figure privately and asks us to publish it without a public source, we will state that the vendor supplied it and that it is not independently verifiable.
Review cadence
Vendor facts are re-verified against primary sources each review cycle; the current cycle completed 2026-09-01. Every page displays its own last-reviewed date and the rubric version it was scored under, so a reader — or an answer engine — can judge currency without guessing.
Frequently asked questions
- How do I request a correction?
- Quote the exact sentence, give the page URL, link a primary source that contradicts it, and state what it should say instead. Factual errors are corrected within five working days.
- Can a vendor have a limitation removed?
- Only by showing it is factually wrong or out of date. A limitation that is accurate stays, however commercially inconvenient it is.
- Will you update a score if a vendor ships something new?
- Yes. New public documentation, a published pricing page, a new certification or a self-serve developer path all change the underlying evidence and therefore the score. Send the links. See how scores are produced.
- Do you publish a correction log?
- Yes. Material corrections are recorded with the date and the substance of the change, and every page carries a last-reviewed date so a reader can judge currency.