eduKateSG · Why Science?
Trace an approved drug from application number to action documents
Use Drugs@FDA to read application types, product records, original and supplemental actions, approval letters, labels and multidisciplinary reviews.
Medicines reach the public through a regulatory record built from applications, studies, manufacturing information, labeling and agency decisions. Drugs@FDA helps readers find information about most FDA-approved brand-name, generic and over-the-counter human drug products.
A single search result can contain several layers: an application, one or more product entries, an approval history, labels, letters and review documents. The application number connects those layers, while action and document labels explain their different roles.
Did you know? FDA defines approval history as a chronological list of agency actions for a drug product under an application. It can include an original approval as well as later changes in labeling, route, strength or patient population.
This guide teaches regulatory information literacy. It does not recommend a medicine, dose or substitution. Those decisions need the current approved information and a qualified healthcare professional.
Chapter index
Chapters 1–9: applications, products and action dates
- 1. The application number anchors the record
- 2. Products sit within applications
- 3. Approval history is chronological
- 4. Original approvals and supplements differ
- 5. Action dates need document context
- 6. Approval letters state the agency action
- 7. Labels describe approved use and risk information
- 8. Review documents explain FDA assessment
- 9. Chemistry and manufacturing are one evidence layer
Chapters 10–17: labels, reviews, approval status and limits
- 10. Clinical reviews evaluate submitted evidence
- 11. Statistical reviews inspect analysis
- 12. Generic approvals follow ANDA pathways
- 13. Tentative approval is not final approval
- 14. Marketing status can change
- 15. Drug names require ingredient checking
- 16. Current labeling sources serve different purposes
- 17. Approval-record literacy supports health careers
CHAPTER 1 OF 17 · Identify the application
1. The application number anchors the record
Drug approval evidence becomes clearer when application identity, action date, label and review documents stay connected. Drugs@FDA organises records around FDA applications such as NDAs, ANDAs and some BLAs. The application number is safer than a trade name for tracking actions. This lets learners trace an authorised claim to the relevant regulatory record.
Try this
Evidence question: Which application type and number are shown? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the application before comparing products. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the application number anchors the record, its identifier or version context, and one limit that must remain visible.
Drugs@FDA follows regulatory actions for approved human drug products through structured records. One application can contain product entries that differ by strength, dosage form or route. Product numbers distinguish these entries. It also keeps an original approval separate from later supplements and label changes.
Try this
Evidence question: Which exact product is being described? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Keep strength, form, route and product number together. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for products sit within applications, its identifier or version context, and one limit that must remain visible.
An approval history is a timeline of FDA actions, not a history of every scientific publication about the medicine. FDA defines approval history as the chronological list of agency actions involving a drug product under an application number. Application and product numbers prevent similar names from being merged.
Try this
Evidence question: Which action changed the product or label? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Build a date-action-document table. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for approval history is chronological, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Identify the application
4. Original approvals and supplements differ
The current scientific question determines whether the user needs an approval letter, label, review or later safety source. An original application establishes the initial approval, while supplements can address manufacturing, labeling, indications, dosing or other changes. Medical decisions still require qualified professional guidance.
Try this
Evidence question: Is this action original or supplemental? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use the action type shown rather than calling every date a new approval. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for original approvals and supplements differ, its identifier or version context, and one limit that must remain visible.
Drug approval evidence becomes clearer when application identity, action date, label and review documents stay connected. A displayed action date identifies an FDA regulatory action. It should not be substituted for a study date, publication date or market launch. This lets learners trace an authorised claim to the relevant regulatory record.
Try this
Evidence question: Which lifecycle event does this date name? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Copy the exact action label beside the date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for action dates need document context, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Read the action history
6. Approval letters state the agency action
Drugs@FDA follows regulatory actions for approved human drug products through structured records. Approval letters document the action and conditions at that time. Later supplements or communications can modify the regulatory picture. It also keeps an original approval separate from later supplements and label changes.
Try this
Evidence question: Which application and supplement does the letter address? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Read the header and action language before summarising. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for approval letters state the agency action, its identifier or version context, and one limit that must remain visible.
CHAPTER 7 OF 17 · Read the action history
7. Labels describe approved use and risk information
An approval history is a timeline of FDA actions, not a history of every scientific publication about the medicine. Drugs@FDA can provide labeling associated with approved products and actions. Label sections should be read as a whole and with their revision date. Application and product numbers prevent similar names from being merged.
Try this
Evidence question: Which label revision supports the statement? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the label date and section heading. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for labels describe approved use and risk information, its identifier or version context, and one limit that must remain visible.
The current scientific question determines whether the user needs an approval letter, label, review or later safety source. Public review materials can include discipline-specific analyses and decision summaries for many products, especially newer approvals. Availability varies by product and era. Medical decisions still require qualified professional guidance.
Try this
Evidence question: Which review discipline answers the question? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Cite the exact review file and page. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for review documents explain fda assessment, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Choose the evidence document
9. Chemistry and manufacturing are one evidence layer
Drug approval evidence becomes clearer when application identity, action date, label and review documents stay connected. Quality reviews consider identity, strength, purity, manufacturing and controls. They do not replace clinical efficacy or safety review. This lets learners trace an authorised claim to the relevant regulatory record.
Try this
Evidence question: Which evidence layer supports the conclusion? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Separate product-quality and clinical statements. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for chemistry and manufacturing are one evidence layer, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Choose the evidence document
10. Clinical reviews evaluate submitted evidence
Drugs@FDA follows regulatory actions for approved human drug products through structured records. Clinical review documents discuss trials, endpoints, safety and benefit-risk considerations within the application. They must be read with the approved indication and decision date. It also keeps an original approval separate from later supplements and label changes.
Try this
Evidence question: Which population and endpoint were evaluated? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Match the review to the label indication. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for clinical reviews evaluate submitted evidence, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Choose the evidence document
11. Statistical reviews inspect analysis
An approval history is a timeline of FDA actions, not a history of every scientific publication about the medicine. Statistical review documents can explain populations, models, missing data and sensitivity analyses used in evaluating submitted studies. Application and product numbers prevent similar names from being merged.
Try this
Evidence question: Which analysis set supports the result? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record endpoint, model and uncertainty. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for statistical reviews inspect analysis, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Choose the evidence document
12. Generic approvals follow ANDA pathways
The current scientific question determines whether the user needs an approval letter, label, review or later safety source. ANDA records support approved generic drug products by referencing the required regulatory basis. An ANDA approval is distinct from an NDA approval history. Medical decisions still require qualified professional guidance.
Try this
Evidence question: Which listed drug and application pathway apply? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Keep NDA and ANDA identifiers separate. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for generic approvals follow anda pathways, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Preserve the regulatory boundary
13. Tentative approval is not final approval
Drug approval evidence becomes clearer when application identity, action date, label and review documents stay connected. A tentative approval means the application meets relevant approval requirements but cannot yet receive final approval, often because of patent or exclusivity barriers. This lets learners trace an authorised claim to the relevant regulatory record.
Try this
Evidence question: Does the record say tentative or final? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Preserve the status wording exactly. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for tentative approval is not final approval, its identifier or version context, and one limit that must remain visible.
Drugs@FDA follows regulatory actions for approved human drug products through structured records. Products may appear with prescription, over-the-counter, discontinued or other marketing information. Discontinued does not by itself state the reason. It also keeps an original approval separate from later supplements and label changes.
Try this
Evidence question: What exact marketing status is displayed? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use FDA sources before inferring safety withdrawal. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for marketing status can change, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Preserve the regulatory boundary
15. Drug names require ingredient checking
An approval history is a timeline of FDA actions, not a history of every scientific publication about the medicine. Trade names can change and similar names can confuse searches. Active ingredient, dosage form, route and application number establish identity. Application and product numbers prevent similar names from being merged.
Try this
Evidence question: Which ingredient and formulation are involved? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Verify identity before linking a label or review. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for drug names require ingredient checking, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Preserve the regulatory boundary
16. Current labeling sources serve different purposes
The current scientific question determines whether the user needs an approval letter, label, review or later safety source. FDA explains that company-submitted current labeling in DailyMed or FDALabel may differ from the latest FDA-approved labeling in Drugs@FDA. Medical decisions still require qualified professional guidance.
Try this
Evidence question: Which source purpose matches the question? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Name the database and label date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for current labeling sources serve different purposes, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Preserve the regulatory boundary
17. Approval-record literacy supports health careers
Drug approval evidence becomes clearer when application identity, action date, label and review documents stay connected. Regulatory scientists, pharmacists, clinicians, librarians and researchers trace applications, actions, labels and reviews for different questions. This lets learners trace an authorised claim to the relevant regulatory record.
Try this
Evidence question: Which document is primary for the claim? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Create an application-action-evidence receipt. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for approval-record literacy supports health careers, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A regulatory decision becomes traceable when the application, action and evidence document stay together
Drugs@FDA lets a learner move from a product name to the exact application and public documents behind an FDA action. The chronology matters because approved information changes over time.
Save the application type and number, product number, ingredient, strength, dosage form, route, action type, action date, letter, label revision, review file and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Application | Regulatory submission identity | Is it NDA, ANDA or BLA? |
| Product entry | Specific strength, form and route | Which product number applies? |
| Approval action | Dated FDA decision or change | Original, supplemental, tentative or final? |
| Review document | Agency assessment of submitted evidence | Which discipline and decision date? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA Drug Approvals and Databases — accessed 25 October 2026.
- Drugs@FDA — accessed 25 October 2026.
- Drugs@FDA glossary — accessed 25 October 2026.
- FDA approved-drug information resources — accessed 25 October 2026.
- FDA drug development and approval process — accessed 25 October 2026.