Check the Provenance of Online Health Information

Before adding a statement to a health information page, find out where it came from and whether that source supports the way the statement will appear. A familiar publisher name can help you locate a document, but the editorial decision depends on the document itself: its author, date, scope, and the specific passage behind the summary.

A provenance record lets another editor retrace that decision. It should identify the source version and show how the proposed wording relates to it. If the original cannot be located or its scope is unclear, keep the statement out of the publication queue until a reviewer can resolve the gap.

Start with the claim you want to publish

Copy the proposed sentence into an editorial worksheet. Under it, record the page and section where it would appear. A single paragraph can combine several assertions, each of which may need its own source. Split a compound sentence into separate checks so a citation for one part does not appear to support the whole paragraph.

Next, follow the citation or link. If an article describes another organization’s report, locate that report and the relevant section. Keep the referring article in your notes as a discovery source, then compare its summary with the underlying document. Check the document title and issuing organization on the source itself. A link in a search result or a page title alone may not identify the version that the author used.

The NIH Office of Dietary Supplements recommends considering who runs and funds a site, the sources behind its information, and the date of review or update. Those questions are a starting point for an editorial assessment. They do not replace checking the passage that supports a particular sentence.

Build a record another editor can follow

Use one row for each proposed statement. Include enough detail for a reviewer to find the same passage and understand why it was selected:

  • Proposed wording. Include the full sentence and its destination on your page.
  • Source identity. Record the author or organization, title, publisher, and direct URL or stable identifier when available.
  • Version and dates. Record the publication date, any stated revision date, and the date your team accessed the source. Label each date by its meaning.
  • Supporting passage. Note the section, page number, table, or other locator. Save a short quotation in the internal worksheet if your editorial process permits it.
  • Scope and limitations. Record the population, setting, period, and conditions stated by the source when they matter to the sentence.
  • Decision and owner. Mark the item ready for review, awaiting clarification, or excluded. Name the person responsible for the next action.

If a source changes at the same address, a URL by itself may not tell a reviewer which wording was examined. Record the version and keep an approved copy or a reference to an accessible version under the team’s document-handling rules. Do not invent a revision date when one is absent. Record that the date was not found and ask the reviewer whether the source is suitable for the intended use.

Compare scope with the proposed summary

Read the relevant section around the cited passage, including qualifications that change its meaning. Note whom the document addresses and what it actually describes. Then read the proposed sentence on its own. Would a reader understand the same population, setting, and degree of certainty?

An editor may need to narrow a sentence, attribute it to the source, or add context beside it. If the source does not support the proposed wording, return the item to the author. Keep the decision in the worksheet so the same unsupported wording is not reintroduced during a later revision.

Avoid using the presence of a reference as the final check. A reference can lead to a general landing page, an older edition, or a document that discusses a different question. Record the mismatch and locate a better source before approving the statement.

Work through a fictional source mismatch

Imagine an editor is preparing a page about how an organization publishes health information. A draft says, “The organization reviews every page each month.” A linked organizational overview says that pages are reviewed regularly, but it gives no monthly schedule.

The editor opens the source, records its title and access date, and saves the section describing the review process. The editor marks “every month” as unsupported and asks the source owner for a current policy. If the owner cannot provide a checkable schedule, the revised draft can describe the published statement as a regular review process, with attribution and the same limits as the source.

The useful result is a traceable decision: the team knows which wording was removed, why it was removed, and which source supported the remaining description. The review record also gives the next editor a clear reason to check for an updated policy before making the claim more specific.

Keep provenance current

Assign each published page to an owner who can decide when its sources need another check. A source update, a broken link, or a reader’s correction can trigger an earlier review. Record what changed and whether it affects the page. If a link is broken, first identify whether the original publisher has moved the same document. Confirm that a replacement has the same scope before substituting it.

A review date should describe a review that actually happened. Record the result even when no text change is needed, including which sources were checked and who made the decision. This gives the next reviewer a useful starting point.

Frequently asked questions

Is a government or university domain enough to approve a claim? It helps identify a publisher, but the editor still needs to find the relevant document and confirm that its scope supports the sentence.

What if a source has no visible date? Record that no date was found. Ask the responsible reviewer to assess the source and seek a dated version when the date matters to the claim.

Can an article cite a source it has not read? The editor should obtain and review the relevant source before using it to support the page. If it cannot be accessed, document the limitation and choose wording supported by material the team has checked.

What if a source is updated after publication? Compare the new version with the passage used in the page. Record whether the update affects the summary, assign any required revision, and preserve a reference to the version previously reviewed.