eduKateSG · Why Science?
Follow medical-device advice from development to patient access
Use current FDA TAP resources through eligibility, dated enrolment, all-office expansion, TAP advisors, non-FDA engagement, patient, provider and payer input, programme limits and later marketing decisions.
A medical device can clear a scientific and regulatory hurdle yet still struggle to reach patients because design, workflow, evidence, payment and adoption do not line up. FDA’s Total Product Life Cycle Advisory Program, or TAP, explores those connections earlier.
TAP is a pilot, so scope and counts move. FDA reported 159 enrolled devices on 7 October 2026 and says the programme expanded across all Offices of Health Technologies from 1 July 2026 for eligible Breakthrough-designated and STeP devices.
Did you know? TAP can facilitate early interaction with non-FDA parties such as patients, providers and payers, but it does not make their decisions or replace a manufacturer’s management and advisers.
This guide supports programme and evidence literacy. It does not predict authorization, coverage or adoption.
Chapter index
Chapters 1–9: pilot scope, enrolment and advisory work
- 1. TAP is a CDRH pilot
- 2. The programme looks beyond one review event
- 3. Enrolment follows published criteria
- 4. Programme scope expanded in July 2026
- 5. The enrolment count is dated
- 6. Fiscal-year capacity differs from actual enrolment
- 7. TAP advisors provide a navigation role
- 8. FDA review teams retain regulatory authority
- 9. Non-FDA engagement can be facilitated
Chapters 10–17: stakeholder input, programme limits and authorizations
- 10. TAP does not run outside engagements
- 11. Patient input and regulatory evidence differ
- 12. Provider input can reveal adoption barriers
- 13. Payer input is not a coverage promise
- 14. TAP does not decide acceptable business risk
- 15. Enrolment is not marketing authorization
- 16. Public status needs exact language
- 17. A TAP receipt preserves the whole route
The TAP Pilot becomes understandable when enrolment criteria, TAP advisor work, FDA review and non-FDA engagement stay connected. The Total Product Life Cycle Advisory Program is a pilot created under the MDUFA V commitment to support medical-device development and patient access. This keeps advisory support separate from formal regulatory and payer decisions.
Try this
Evidence question: Which official page, guidance or record supports the point about tap is a cdrh pilot? 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 identifier, date, source and one limit for tap is a cdrh pilot. 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 tap is a cdrh pilot, its identifier or version context, and one limit that must remain visible.
TAP considers the full path from development to patient access for eligible enrolled devices. TAP considers the full path from concept through evidence, regulatory review, adoption and patient access while keeping each decision owner distinct. It also preserves the limits FDA publishes for TAP.
Try this
Evidence question: Which official page, guidance or record supports the point about the programme looks beyond one review event? 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 identifier, date, source and one limit for the programme looks beyond one review event. 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 the programme looks beyond one review event, its identifier or version context, and one limit that must remain visible.
Enrolment is not marketing authorization, reimbursement or a promise of commercial success. Eligible Breakthrough-designated and STeP devices must meet current TAP enrollment criteria and capacity rules. Enrolment dates and programme pages make the route auditable.
Try this
Evidence question: Which official page, guidance or record supports the point about enrolment follows published criteria? 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 identifier, date, source and one limit for enrolment follows published criteria. 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 enrolment follows published criteria, its identifier or version context, and one limit that must remain visible.
Programme scope and totals are dated facts because the pilot continues to expand. FDA states that TAP expanded across all Offices of Health Technologies on 1 July 2026 for eligible devices meeting the criteria. The device must still meet the applicable evidence and marketing standard.
Try this
Evidence question: Which official page, guidance or record supports the point about programme scope expanded in july 2026? 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 identifier, date, source and one limit for programme scope expanded in july 2026. 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 programme scope expanded in july 2026, its identifier or version context, and one limit that must remain visible.
The TAP Pilot becomes understandable when enrolment criteria, TAP advisor work, FDA review and non-FDA engagement stay connected. FDA reported 159 devices enrolled as of 7 October 2026, a snapshot that should not be repeated without its date. This keeps advisory support separate from formal regulatory and payer decisions.
Try this
Evidence question: Which official page, guidance or record supports the point about the enrolment count is dated? 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 identifier, date, source and one limit for the enrolment count is dated. 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 enrolment count is dated, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Work with TAP
6. Fiscal-year capacity differs from actual enrolment
TAP considers the full path from development to patient access for eligible enrolled devices. Published ceilings for FY2026 and FY2027 describe planned capacity, not a promise that each place will be filled or each device will succeed. It also preserves the limits FDA publishes for TAP.
Try this
Evidence question: Which official page, guidance or record supports the point about fiscal-year capacity differs from actual enrolment? 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 identifier, date, source and one limit for fiscal-year capacity differs from actual enrolment. 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 fiscal-year capacity differs from actual enrolment, its identifier or version context, and one limit that must remain visible.
Enrolment is not marketing authorization, reimbursement or a promise of commercial success. A TAP advisor can help identify risks, challenges, questions and potential routes during development. Enrolment dates and programme pages make the route auditable.
Try this
Evidence question: Which official page, guidance or record supports the point about tap advisors provide a navigation role? 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 identifier, date, source and one limit for tap advisors provide a navigation role. 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 tap advisors provide a navigation role, its identifier or version context, and one limit that must remain visible.
Programme scope and totals are dated facts because the pilot continues to expand. Advisory programme interaction does not replace the formal review division or the statutory decision process. The device must still meet the applicable evidence and marketing standard.
Try this
Evidence question: Which official page, guidance or record supports the point about fda review teams retain regulatory authority? 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 identifier, date, source and one limit for fda review teams retain regulatory authority. 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 fda review teams retain regulatory authority, its identifier or version context, and one limit that must remain visible.
The TAP Pilot becomes understandable when enrolment criteria, TAP advisor work, FDA review and non-FDA engagement stay connected. TAP may help innovators identify and interact with patients, providers, payers or other ecosystem participants for relevant input. This keeps advisory support separate from formal regulatory and payer decisions.
Try this
Evidence question: Which official page, guidance or record supports the point about non-fda engagement can be facilitated? 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 identifier, date, source and one limit for non-fda engagement can be facilitated. 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 non-fda engagement can be facilitated, its identifier or version context, and one limit that must remain visible.
TAP considers the full path from development to patient access for eligible enrolled devices. FDA states that TAP does not design, coordinate, convene or operate the innovator’s engagement with non-FDA parties. It also preserves the limits FDA publishes for TAP.
Try this
Evidence question: Which official page, guidance or record supports the point about tap does not run outside engagements? 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 identifier, date, source and one limit for tap does not run outside engagements. 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 tap does not run outside engagements, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Engage the ecosystem
11. Patient input and regulatory evidence differ
Enrolment is not marketing authorization, reimbursement or a promise of commercial success. Patient needs can shape design and endpoints, but they do not replace analytical, bench, clinical or other evidence required for authorization. Enrolment dates and programme pages make the route auditable.
Try this
Evidence question: Which official page, guidance or record supports the point about patient input and regulatory evidence differ? 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 identifier, date, source and one limit for patient input and regulatory evidence differ. 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 patient input and regulatory evidence differ, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Engage the ecosystem
12. Provider input can reveal adoption barriers
Programme scope and totals are dated facts because the pilot continues to expand. Workflow, training, interoperability and usability feedback can identify practical problems without deciding FDA clearance or approval. The device must still meet the applicable evidence and marketing standard.
Try this
Evidence question: Which official page, guidance or record supports the point about provider input can reveal adoption barriers? 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 identifier, date, source and one limit for provider input can reveal adoption barriers. 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 provider input can reveal adoption barriers, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Separate final decisions
13. Payer input is not a coverage promise
The TAP Pilot becomes understandable when enrolment criteria, TAP advisor work, FDA review and non-FDA engagement stay connected. Early discussion can clarify evidence needs for coverage or reimbursement, while actual payer decisions remain separate. This keeps advisory support separate from formal regulatory and payer decisions.
Try this
Evidence question: Which official page, guidance or record supports the point about payer input is not a coverage promise? 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 identifier, date, source and one limit for payer input is not a coverage promise. 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 payer input is not a coverage promise, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Separate final decisions
14. TAP does not decide acceptable business risk
TAP considers the full path from development to patient access for eligible enrolled devices. FDA lists limits including that TAP does not decide which risks are acceptable or which activities should be financed. It also preserves the limits FDA publishes for TAP.
Try this
Evidence question: Which official page, guidance or record supports the point about tap does not decide acceptable business risk? 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 identifier, date, source and one limit for tap does not decide acceptable business risk. 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 tap does not decide acceptable business risk, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Separate final decisions
15. Enrolment is not marketing authorization
Enrolment is not marketing authorization, reimbursement or a promise of commercial success. A TAP device still must meet its applicable PMA, De Novo or 510(k) standard before marketing. Enrolment dates and programme pages make the route auditable.
Try this
Evidence question: Which official page, guidance or record supports the point about enrolment is not marketing authorization? 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 identifier, date, source and one limit for enrolment is not marketing authorization. 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 enrolment is not marketing authorization, its identifier or version context, and one limit that must remain visible.
Programme scope and totals are dated facts because the pilot continues to expand. A statement should distinguish designation, TAP enrolment, submission, authorization, coverage and adoption rather than compress them into “approved.” The device must still meet the applicable evidence and marketing standard.
Try this
Evidence question: Which official page, guidance or record supports the point about public status needs exact language? 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 identifier, date, source and one limit for public status needs exact language. 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 public status needs exact language, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Separate final decisions
17. A TAP receipt preserves the whole route
The TAP Pilot becomes understandable when enrolment criteria, TAP advisor work, FDA review and non-FDA engagement stay connected. Record eligibility, enrolment date, office, development milestone, interactions, external stakeholder input, submission number, decision and access date. This keeps advisory support separate from formal regulatory and payer decisions.
Try this
Evidence question: Which official page, guidance or record supports the point about a tap receipt preserves the whole route? 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 identifier, date, source and one limit for a tap receipt preserves the whole route. 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 a tap receipt preserves the whole route, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A patient-access story is credible when every decision owner remains visible
TAP helps an innovator see the full route early. The science lesson is to keep FDA authorization, payer coverage, provider adoption and patient use as connected but separate evidence objects.
Save the device, designation or STeP status, TAP criteria, request and enrolment dates, Office of Health Technology, TAP milestones, FDA interactions, non-FDA parties, questions asked, evidence changes, marketing submission, decision, coverage evidence and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| TAP enrolment | Entry to the advisory pilot | Which criteria and date? |
| TAP advisor | Helps identify development risks and connections | Which question was addressed? |
| Non-FDA engagement | Offers patient, provider or payer perspective | Who owns the later decision? |
| Marketing authorization | Formal FDA decision under the applicable pathway | Which record proves it? |
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 Total Product Life Cycle Advisory Program — accessed 25 October 2026.
- FDA TAP Overview — accessed 25 October 2026.
- FDA TAP Pilot Enrollment and Expansion — accessed 25 October 2026.
- FDA TAP Non-FDA Engagement — accessed 25 October 2026.
- FDA Total Product Life Cycle for Medical Devices — accessed 25 October 2026.