Read the source record

Match the source to the question

For a product-status question, look for the actual product record. For a license question, use the relevant licensing board. For a payment question, ask the payer about the specific benefit. Do not let a document about one of those topics stand in for another.

The Food and Drug Administration (FDA) gives this warning about its National Drug Code Directory, checked September 26, 2026. A code or listing does not itself mean approval.

That code is often shortened to NDC. It identifies a product in a directory. Ask what the code establishes before accepting it as proof of a different claim. Keep the actual approval question open until the approval record is identified.

Read a source’s explanation of what it can and cannot show before drawing a conclusion from it. A claim can be accurate within its scope and misleading when that scope is left out.

Distinguish a concern from a final finding

The FDA warning-letter database, checked September 17, 2026, cautions that later interaction with a recipient may change the status of issues described in a letter.

A warning letter records FDA’s concerns on a date; it is not a final finding. A company with no letter may simply not have been reviewed, so the lack of a letter does not establish that the company’s practices passed an FDA review.

Read a letter for what the agency said about the particular conduct. Do not turn it into an invented verdict on every program with a similar product. Ask whether the page also records a reply or a later change.

Reading an event report

FDA’s reporting-data notice, checked September 17, 2026, says a report does not establish cause and cannot be used to estimate how often an event happens.

An unwanted event reported after a medicine is taken is a signal to examine, not a count of proven injuries caused by that medicine.

Keep the source’s own limits beside any count. This distinction helps when comparing a dramatic headline with the underlying record.

For a personal concern, bring the product information to a health professional who can assess the situation. A source document cannot examine the person reading it.

Keep the date beside the claim

Information about product approval and legal status was checked September 26, 2026. Instructions for checking licenses and using public records were checked September 17, 2026.

Those dates describe the source record used here. They do not announce a fresh review of every public page today. Use the linked record to check whether a time-sensitive answer has changed before relying on it.

For the withdrawn-nomination table, April 22, 2026 is the date FDA prints for the page, not a published withdrawal date for each substance.

A nomination asks for an ingredient to be considered. Ask what action the source actually records. A request, a proposed decision, and an approval are different descriptions. Keep the exact description when sharing the information with someone else.

If the source does not answer the claim, write down what remains unknown. Ask the program for the missing record or a narrower statement. An honest gap is easier to work with than a confident answer built from an unrelated link.