V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryTFDA (Taiwan)
Compliance · The complete guide

TFDA Taiwan: Taiwan Food and Drug Administration

In short

An orientation to Taiwan’s Food and Drug Administration, its English-site resources and practical preparation for product-specific enquiries.

4,092 words · ~19 min read
Regulatory affairs professional in Taipei reviewing a TFDA application on a tablet
On this page
  1. 01What TFDA Taiwan means and where to begin
  2. 02Taiwan product topics: a resource map, not a classification decision
  3. 03Agency, law, guidance and online resources: distinguish the terms
  4. 04Build a product brief before choosing the next enquiry
  5. 05A preparation lifecycle from product description to human review
  6. 06Link products, questions, documents and decisions
  7. 07Three worked cases: unclear use, outdated files and variant identity
  8. 08Design internal handoffs and recover incomplete transfers
  9. 09Potential readiness errors and proportionate controls
  10. 10Finish with a scoped internal review decision
On this page · 10 sections
  1. 1What TFDA Taiwan means and where to begin
  2. 2Taiwan product topics: a resource map, not a classification decision
  3. 3Agency, law, guidance and online resources: distinguish the terms
  4. 4Build a product brief before choosing the next enquiry
  5. 5A preparation lifecycle from product description to human review
  6. 6Link products, questions, documents and decisions
  7. 7Three worked cases: unclear use, outdated files and variant identity
  8. 8Design internal handoffs and recover incomplete transfers
  9. 9Potential readiness errors and proportionate controls
  10. 10Finish with a scoped internal review decision
AI · Explain it for MY operation

How does TFDA (Taiwan) apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What TFDA Taiwan means and where to begin

TFDA Taiwan means the Taiwan Food and Drug Administration. This article uses TFDA, Taiwan FDA and Taiwan Food and Drug Administration as naming variants for the same agency. Start with the TFDA English home when orienting a Taiwan product enquiry, rather than treating the agency’s name as an answer to a product-specific question.

The English home page provides navigation for Food, Drugs, Controlled Drugs, Medical Devices and Cosmetics. Use those labels to locate relevant material. For internal preparation, keep the topic you searched separate from any conclusion about product classification, application route or approval status.

For administrative hierarchy and institutional responsibilities, consult the current Organization and Functions information through the About FDA directory. That directory also lists Mission and Future Perspectives and Contact. Choose the institutional information for questions about the agency itself; use product-topic navigation to begin questions about a particular product.

For a multi-market project, keep the Taiwan enquiry distinct from parallel work on China’s NMPA or FDA Philippines. Record the market and the question explicitly so that a similarly named authority or an overseas product description does not become an unstated assumption in the Taiwan review.

This article covers official English-site orientation and proposed internal preparation. It is not a product-specific statement of binding legal requirements or a TFDA submission checklist. The preparation suggestions are internal working methods, not regulator instructions; their purpose is to frame the next question clearly for human review.

02Taiwan product topics: a resource map, not a classification decision

The TFDA product directory includes five product-topic labels: Food, Drugs, Controlled Drugs, Medical Devices and Cosmetics. Use these as starting points for an enquiry, not as a classification decision. The table below proposes internal questions and preparation records; it is not a TFDA submission checklist.

jurisdictionofficial product-topic labelinitial question to resolveproposed preparation record
TaiwanFoodWhat is intended to be consumed, how is it presented, and why explore Food?Product identifier, composition description, intended consumption and presentation copy.
TaiwanDrugsWhat intended use or presentation prompted a Drugs enquiry for this product?Product identifier, intended-use statement, presentation copy and reason for the enquiry.
TaiwanControlled DrugsWhich identified substance or product prompted this topic, and what question remains unresolved?Product and substance identifiers, intended use and the basis for consulting this topic.
TaiwanMedical DevicesWhat does the identified product do, for whom, and why consider Medical Devices?Model or variant identifier, function description, intended user and presentation copy.
TaiwanCosmeticsHow is the product intended to be used and presented, and why explore Cosmetics?Product identifier, intended-use description, presentation copy and topic-selection rationale.

Keep this product navigation distinct from the Law & Regulations directory. That directory repeats the five labels and adds Inspections, Compliance & Accreditation and Others. Record which directory an enquiry follows: a product-topic heading and a legal-resource heading serve different navigation purposes. Neither heading should be entered as the provision supporting an internal legal conclusion.

For preparation purposes, treat “supplement,” “IVD” and “chemical product” as descriptions that open questions, not answers assigning a Taiwan legal category. Ask what exact product, composition, function, intended consumption or use, and presentation the enquiry concerns. Record the proposed topic separately from the unresolved scope question. A related discussion of the sterile/aseptic supplement format boundary can help frame a format question, but should not substitute for a Taiwan-specific assessment.

Include a jurisdiction field explicitly set to Taiwan, alongside the product identifier and proposed topic. Keep records for another market—such as an enquiry concerning NMPA in China—separate, even when they concern the same commercial product. Cross-reference shared descriptions where useful, while leaving each market’s scope question and conclusion in its own record.

03Agency, law, guidance and online resources: distinguish the terms

The TFDA home page groups links under Guidance, Law & Regulations navigation. Treat that heading as a route to documents, not as a requirement in itself. Before assigning an internal task, distinguish the organisation, the document’s authority and the purpose of the resource.

term or resourcewhat the reader is looking atuseful next questionboundary
Agency nameTFDA / Taiwan FDA identifies the organisation.Which agency resource addresses this question?Naming an agency does not identify an applicable provision.
Product-topic directoryNavigation organised by topics such as Food, Drugs and Medical Devices.Which topic should I explore?A directory heading is not a product classification decision.
Binding law or regulationThe legal text to examine for applicable obligations.What provision covers this product and activity?Establish scope from the text, not the navigation category.
Official guidanceA regulator document to read for its stated purpose and scope.What does this document explain or recommend?Do not relabel guidance as binding law.
Internal preparation practiceA company’s chosen approach to organising an enquiry.What needs clarification before the enquiry?An internal convention is not a TFDA submission requirement.
Software supportA tool considered for a defined internal task.What function is actually documented?Do not infer capabilities or decision authority from a tool’s name.

The TFDA home page also displays the resource labels “GXP Inspection & Lab Accreditation”, “Online Platform for Application” and “Verification of Digital Pharmaceutical GMP/GDP Certificate”. These labels identify destinations; they should not be read as procedural instructions or platform specifications.

For internal planning, keep applicant preparation, document review, certificate verification and product-specific regulatory decisions as separate task categories. Do not use completion of one as shorthand for another. Related concepts such as change control and GAMP 5 belong in their own context, rather than being treated as TFDA resource definitions. Regulatory and quality decisions remain with authorised people.

04Build a product brief before choosing the next enquiry

Use a short product brief to make the next Taiwan-related question specific. This is a suggested internal preparation record, not a TFDA submission checklist or a statement of required documents. Its purpose is to describe the product under discussion and expose uncertainties before someone chooses the next enquiry.

Proposed fieldWhat to record internally
Product identityInternal identifier, product name and the particular variant being discussed.
Intended use and presentationProposed purpose, user, form, pack and relevant wording describing use.
Composition or specificationsRelevant ingredients, materials or performance characteristics, with units and document references where useful.
Manufacturer identityManufacturer name and the site associated with this product, if known.
Taiwan market contextProposed audience, supply arrangement and whether the product or presentation is already marketed there; mark unknowns explicitly.
Intended activityInitial enquiry, clarification of a specific issue, or preparation for a defined application where applicable. Do not presume an application pathway.
Product-topic candidateFor each topic being considered, record the reason it may be relevant and the exact unresolved question.
Information statusKeep separate fields for product facts, working assumptions and questions requiring clarification.

In the facts field, identify the internal document supporting each material detail. In the assumptions field, state what the team is temporarily treating as true. In the clarification field, write what would resolve the uncertainty. Do not silently turn a proposed use or an unconfirmed manufacturer name into an established fact. Consistent production context tagging can help distinguish the variant being discussed from similarly named products.

Narrow the question before sending it

For a hypothetical brief, assume Product P-17 is a powdered drink mix in single-use sachets and the intended activity is an initial enquiry. Replace “What does TFDA require?” with “For P-17 in this sachet presentation and with the intended-use wording attached, which product-topic resources should we consult for our initial Taiwan enquiry?” Record why the team is considering the food topic without treating that choice as a classification decision.

Keep the brief proportionate: omit irrelevant fields, but retain relevant unknowns as questions. A reviewer should be able to identify the named product, presentation and intended activity without mistaking the template for an official dossier specification.

05A preparation lifecycle from product description to human review

Use this illustrative internal lifecycle to move the product brief towards a reviewable next action. It is not a TFDA processing sequence or submission checklist. Assign a named person to each owner role below and set organisation-defined review dates; these are internal targets, not official processing times or statutory deadlines.

  1. Product owner → regulatory lead: hand over a bounded product description identifying the version, intended use and unresolved descriptive gaps. Output: the description that subsequent work will address.
  2. Regulatory lead → question owner: select an official resource relevant to that description and record its title, URL and access date. Output: a resource reference, with a short explanation of its relevance rather than an assumed classification.
  3. Question owner → document coordinator: formulate the unresolved question narrowly enough to investigate. State which product fact or interpretation remains uncertain. Output: a question tied to the product description and resource reference.
  4. Document coordinator → technical reviewer: index the records needed to examine that question, identifying document versions and responsible owners. Output: an indexed record with missing or conflicting information visibly flagged.
  5. Technical reviewer → product owner: return discrepancies for clarification. Output: a documented request identifying the conflicting information, the person responsible for answering and the next internal review date. Route substantive description changes through the organisation’s change control process.
  6. Authorised internal reviewer → action owner: review the clarified record and document the next action, its scope and rationale. If the question remains unresolved, return it to the product owner and repeat resource selection where the revised description changes the enquiry.
  7. Record custodian → future reviewer: retain the reviewed versions, responses and decision history together. Output: a retrievable history supporting later audit trail review.

The workflow records and supports the authorised person’s action; it does not make that decision.

Applicant Preparation and Human Review
  1. 1
    Describe ProductRecord intended use, presentation and Taiwan market context.
  2. 2
    Locate resourcesChoose relevant English-site topics for the enquiry.
  3. 3
    Frame QuestionsList unresolved points without assuming a regulatory answer.
  4. 4
    Index DocumentsLink current records to product identifiers and questions.
  5. 5
    Resolve mismatchesAssign corrections to named internal owners.
  6. 6
    Review internallyAn authorised person decides the next action.
  7. 7
    Preserve historyRetain the decision and earlier review state.
Suggested internal sequence, not a TFDA processing pathway or official application timetable.

06Link products, questions, documents and decisions

For internal preparation, use five linked entities rather than a folder of loosely named files. The following is an illustrative company record model, not an official TFDA schema or submission requirement. Its purpose is to show which material supports which question and who reached each conclusion.

EntitySuggested fields and role
ProductStable product ID, name, variant and description. Acts as the parent record for the questions being investigated.
Official resourceResource ID, official URL, page label, relevant heading or location, and access date. Where a specific provision supports the review, retain its actual identifier.
Routing questionQuestion ID, product ID, precise unresolved question, owner, and links to relevant official resources and company documents.
Document referenceDocument ID, version, storage location and internal review status. Identifies company material without treating its filename as its identity.
Review decisionDecision ID, linked question ID, reviewer, decision scope, date, conclusion and the resource or document versions considered.

Keep official resources and company documents distinct: the former identify external material consulted; the latter identify the company's own product information or analysis. A resource access date records when a page was consulted, not its effective date. For company files, document control should keep document identity separate from version and storage location, so moving or renaming a file does not break the relationship.

For example, assume one illustrative product, P-001, has three questions: Q-01 about intended use, Q-02 about variant identity and Q-03 about the next enquiry. It also has two document references: D-01 version 2, a product description, and D-02 version 1, a label draft. Both documents can support Q-01; D-01 can also support Q-02. Each question can accumulate separate dated review decisions. This is a one-to-many relationship from product to questions and from product to document references—not a separate product record for every file.

Avoid an unexplained “approved” status. Record a bounded conclusion such as “product description accepted internally for preparing the intended-use enquiry.” If that description changes, link the revision through change control and identify which question-specific decisions need reconsideration.

Proposed applicant preparation record model

Product

Proposed identity and use record.

  • product_id
  • market
  • intended_use
  • presentation
  • revision

Official Resource

Official page and location to consult.

  • resource_id
  • official_url
  • page_label
  • location_label
  • accessed_on

Routing Question

A bounded point for clarification.

  • question_id
  • product_id
  • question_text
  • owner
  • status

Document reference

An internally indexed document version.

  • document_id
  • product_id
  • version
  • controlled_uri
  • review_status

Review decision

A human decision with recorded scope.

  • decision_id
  • question_id
  • reviewer
  • decision_scope
  • decided_on
Illustrative internal entities and fields, not an official TFDA submission schema or software specification.

07Three worked cases: unclear use, outdated files and variant identity

These hypothetical cases apply the product–question–document–decision structure to internal preparation. Each leaves a defined question with a human reviewer; none determines a legal classification or regulatory outcome.

Case one: oral consumption or topical use?

Assumptions: A product brief describes oral consumption. An associated label describes topical cosmetic use. Both are linked to the same product record, and neither has yet been confirmed as the correct description.

Observed inconsistency: The descriptions conflict about how the product is used. Choosing whichever description appears more convenient would conceal the unresolved issue rather than resolve it.

Internal action: Assign the product brief owner responsibility for coordinating correction. Ask that owner to confirm intended use with the label owner, identify the affected versions and retain the conflicting descriptions in the question record. Record who authorises each correction rather than silently overwriting either file.

Human review question: Once intended use is confirmed, which TFDA product-specific enquiry should be pursued, and what uncertainty still needs clarification? Leave routing unresolved until the reviewer has a consistent product description.

Case two: nine current references out of twelve

Assumptions: An organisation’s own preparation plan contains 12 document references. Nine point to current versions; three point to superseded versions. The units are document references. The denominator is the organisation’s assumed plan, not a TFDA document requirement.

Observed inconsistency: Current references equal 9 ÷ 12 × 100 = 75%. This is an inventory measure, not a readiness or acceptance score. It says nothing about whether the documents answer the product questions.

Internal action: Assign three reference replacements to the document owners. Record each old-to-new version relationship, using the traceability approach illustrated by a recipe supersession log, and flag any linked decision affected by changed content.

Human review question: Do the replacement versions still support the recorded conclusions, or must those conclusions be reconsidered?

Case three: shared name, different model identifiers

Assumptions: Two device variants share a commercial name but have different model identifiers. One supporting record names only the first variant.

Observed inconsistency: The shared name does not establish that the record covers both models. The second variant’s connection to that record remains unsubstantiated.

Internal action: Link the record to the named model’s product record. Assign the product record owner a coverage question against the second model; do not copy the supporting link across as confirmed coverage. Carry both identifiers into the review handover.

Human review question: What documented basis, if any, supports applying this record to the second model? The reviewer records the conclusion against that specific variant.

08Design internal handoffs and recover incomplete transfers

For internal preparation, use an illustrative handoff from the product master to the controlled-document index and question log. The product master supplies product identity; the index identifies document versions; the log connects unresolved questions to those records. Transfer manually or through an organisation-defined integration, with a named sender and receiving reviewer. This is a proposed working method, not a TFDA submission process.

Define what moves

Create a transfer record containing product_id, document_id, version, question_id, transfer_id and reconciliation_status. Add sender, recipient, transfer time and payload type. A reference transfer supplies an identifier or location, not the document itself: the receiver checks access to the specified version. A copy transfer supplies document content: the receiver checks that the copy matches the indexed identity and version. These distinctions support an internal chain of custody.

Recover an interrupted handoff

  1. Retain the last complete receiving state. Keep partially received entries separate rather than replacing the working index.
  2. Compare the expected transfer list with received entries. Identify missing records, inaccessible references and missing copies explicitly.
  3. Send only the missing or corrected entries, linking the retry to the original transfer_id. Reconcile the receiving index against the expected identities, versions and question links.
  4. Record who resolved the exception, what changed and when the receiving reviewer accepted reconciliation. Include that history in the internal audit trail review workflow.

For duplicate handling, compare stable document_id and version, preserving product_id and question_id associations. A repeated filename alone neither creates a new record nor proves duplication. If matching identities contain conflicting content, flag the conflict for human resolution. Keep reconciliation_status limited to transfer completeness; it does not represent a regulatory decision.

09Potential readiness errors and proportionate controls

The table below describes potential internal preparation errors—not reported TFDA inspection findings or ranked causes of rejection. These are proposed working controls for a company preparing a product enquiry, not legal requirements, regulator guidance or a TFDA submission checklist. Each control addresses a specific gap without treating administrative completion as an answer to a regulatory question.

potential errorhow it becomes visiblesuggested controlowner
Unresolved question with no ownerAn open question appears in meeting notes but nobody is assigned to pursue it.Assign one accountable owner and record the next action.Preparation lead
Inconsistent measurement unitsTwo documents describe the same quantity using units that have not been reconciled.Reconcile units and measurement basis; retain the original values and conversion calculation.Technical reviewer
Ambiguous manufacturer or site identityThe brief names a company but does not clearly identify the intended manufacturing location.Confirm the company name and site address against company-controlled records.Manufacturing contact
Decision overwritten without contextThe current conclusion differs from an earlier review, with no reason recorded.Retain the previous decision, replacement decision, author, date and reason for change.Decision owner
Issue closed without a recorded answerThe status says closed, but the answer and its basis are absent.Record the answer and closure rationale; otherwise return the issue to open.Issue owner

A unit class library offers a useful organising concept for the unit check. Apply contemporaneous recording when documenting a changed decision, rather than reconstructing its reasoning later.

Example: assume the brief contains a mistyped manufacturer address, while the company-controlled site record identifies the intended location unambiguously. Correcting the brief and recording the basis resolves that company-information question. If the separate question is which TFDA product topic should guide an enquiry about the described use, the address correction does not resolve it. Keep that question open with its assigned owner while seeking external clarification.

10Finish with a scoped internal review decision

Use a short review meeting or documented sign-off to close preparation. This is a proposed internal practice, not a TFDA submission checklist. Name one decision owner—for example, the person your organisation authorises to approve the next enquiry—and include contributors needed to resolve the specific question.

Decide a bounded question

  • State the question being decided and identify the product revision covered; avoid a broad conclusion such as “Taiwan ready.”
  • Define the next activity, its owner and intended recipient—for example, sending a specified product-use question to an identified contact.
  • Identify any unresolved dependency and explain whether it blocks that activity. Where useful, link it to the internal quality risk register.

Choose an organisation-defined outcome

  1. Proceed to the defined next enquiry: record why the preparation supports that limited action.
  2. Return for a specified correction: identify what must change and who will check the correction.
  3. Hold for clarification: state the unanswered question and who will seek the answer.

For any conditional outcome, record the condition, responsible owner and revisit point, such as before the enquiry is sent. If a later product change invalidates the decision’s scope, connect reconsideration to change control rather than silently carrying the sign-off forward.

Close by recording the decision owner’s name and rationale. Mark only the internal preparation task complete; do not label that completion regulatory acceptance. Keep any subsequent approval or release decision separate and with the relevant authorised people.

Frequently asked questions

Q.How can a team handle differences between an English product term and the terminology used in TFDA’s bilingual navigation?+

Use the TFDA English site’s Bilingual Glossary as a terminology starting point. As an internal practice, keep the team’s original term, the corresponding navigation label and the product description together rather than silently replacing one term with another. Link that comparison to the relevant instructions for use, where applicable. Put the terminology mapping under document control, with an owner and revision date, so later reviewers can understand why that navigation route was selected.

Q.Where does the TFDA English site signpost information about food or medicine for personal use?+

The TFDA English homepage includes a navigation entry labelled “Food, Medicine Application for Personal use.” It also lists “Online Platform for Application.” For an internal enquiry record, note the personal-use entry separately from general product navigation and describe the proposed situation in ordinary language. A useful question is: “Which information should I consult for this food or medicine intended for personal use?” This keeps the enquiry focused without presuming an application outcome.

Q.How can an initial consultation question be phrased without assuming its regulatory answer?+

Use a neutral description followed by a routing question: “Our product contains [ingredients], has [physical form], is intended for [use], and would be presented with [wording]. Which TFDA information or consultation route should we follow, and what further details would help you direct the enquiry?” This is a suggested internal practice, not a prescribed TFDA format. Draw technical facts from the tech transfer record and keep unresolved assumptions in a quality risk register.

Q.Which consultation contact details are published on TFDA’s English site?+

The TFDA English site’s contact footer publishes a Consultation Service Hotline at (02) 2787-8200, with service hours of weekdays, 8:00 AM–6:00 PM. It separately lists the general telephone number 886-2-2787-8000 and the address No.109, Ln. 130, Sec. 1, Academia Rd., Nangang Dist., Taipei City 115, Taiwan (R.O.C.). As an internal practice, identify which number was used and record the enquiry date, question and response for follow-up.

Q.How should a Taiwan preparation record treat a classification used for the same product in another market?+

As an internal recordkeeping practice, place the overseas classification in a separate field identifying the jurisdiction, product version and basis for that entry. Keep the Taiwan routing question distinct instead of copying the overseas category into it. For example, maintain separate references for work involving Health Canada or NMPA China. This preserves useful background while making clear which classification belongs to which market and which Taiwan questions still need an answer.

Q.What can a dated TFDA workshop announcement contribute to an internal training plan?+

The TFDA English homepage lists a news item dated 2026-08-26 titled “Taiwan FDA hosts 2026 APEC Medical Devices & Good Registration Management Regulatory Science Center of Excellence Workshop.” As a training-planning practice, use the title and announcement date to identify a potentially relevant topic, not to infer attendance, competence or new obligations. A training record can capture any resulting learning activity; management review can consider whether the topic addresses an identified team knowledge gap.

Q.When should a change to intended use or presentation trigger another internal routing review?+

As an internal screening practice, reopen the routing review when a proposed change alters the description on which the previous route was based. Examples include different intended users, a new stated purpose or revised presentation wording. Use change control to compare the old and proposed descriptions and assign a reviewer. Where the team maintains design controls, connect the review to the relevant design change. This is an internal trigger, not a stated TFDA notification rule.

Q.How can a small team maintain the proposed record structure without specialist software?+

For the proposed internal preparation record, use a shared spreadsheet and a controlled folder. Suggested fields are product identifier, version, terminology mapping, intended use, navigation route, reference URL, access date, open question, owner and response. A short SOP can define who edits and reviews entries. Maintain a dated change log as a simple audit trail, and preserve earlier versions. These are organisational suggestions, not a statement that this setup satisfies any particular electronic-record requirement.

Primary sources

  • TFDA English home
  • TFDA about
Talk to us about TFDA (Taiwan)

Want to see how TFDA (Taiwan) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalMedical Devices
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → 21 CFR Part 11
  • → EU Annex 11
  • → 21 CFR 211
  • → 21 CFR 820
  • → GAMP 5
  • → CSV
  • → CSA
  • → IQ / OQ / PQ

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC