Pre-production brief
| Field | Definition |
|---|---|
| Role | Founder, product lead, or first RA/QA owner preparing a combination-product review. |
| Scenario | The product may combine device, drug, or biologic functions and the team is trying to brief a consultant before committing to a filing story. |
| Concrete problem | The team does not know whether PMOA is clear, whether an RFD or Pre-RFD should be discussed, or how to separate device, drug, biologic, GMP, and EU questions. |
| Useful output | A source-backed PMOA/RFD preparation packet with assumptions, source limits, open questions, and reviewer owners. |
| TrueMedDevice role | Organize official-source evidence and review questions. Do not determine PMOA, lead center, pathway, GMP, user-fee status, or EU route. |
Start with PMOA, not a preferred pathway
FDA's combination-product framework starts with the product and its modes of action. If the team starts by saying 'we want a 510(k)' or 'we want to avoid an NDA,' it can hide the question that actually needs review: which mode of action is primary and what evidence supports that position.
A founder-ready packet should show the device function, drug or biologic function, intended use, mechanism evidence, proposed PMOA rationale, and the facts still missing. That packet gives qualified reviewers something to evaluate instead of forcing them to reverse-engineer the product story from scattered notes.
RFD and Pre-RFD are review questions, not slogans
FDA's RFD materials explain the formal designation path and the information FDA recommends in an RFD package. FDA's current final Pre-RFD guidance describes a separate informal, non-binding feedback process that can be relevant before deciding whether to submit a formal RFD.
This article should not tell every founder to file an RFD. The safer workflow is to prepare the RFD-quality facts and ask qualified RA/QA, counsel, or FDA-facing advisors whether an RFD, Pre-RFD, or another interaction is appropriate for the product's uncertainty.
| Packet element | Why it belongs |
|---|---|
| Product description | RFD and Pre-RFD review depends on what the product is, how it is used, and what each constituent part does. |
| Constituent-part status | The team must separate device, drug, and biologic functions before asking FDA to classify the product identity. |
| PMOA rationale | The proposed lead-center story should be tied to evidence, not preference. |
| Open facts | A reviewer needs to see what is unknown before deciding whether FDA interaction is needed. |
Do not make the separate-application question absolute
FDA guidance supports the idea that one marketing application is often used when a combination product can be reviewed under one lead center. But that is not the same as saying a separate NDA, ANDA, BLA, PMA, De Novo, or 510(k) can never be required.
The review packet should state the assumption being tested: one application, more than one application, or a lead-center consultation model. Then it should show the source basis and the facts that could change the answer.
Keep user-fee programs separate
MDUFA is the medical-device user-fee program. PDUFA is the prescription-drug user-fee program. A combination-product packet should not use one fee table as shorthand for the other.
The useful founder output is a dated fee-reference table that links to the current FDA pages and says what the fee page can and cannot decide. A fee amount does not decide PMOA, application type, or review center.
EU Article 117 is a separate issue list
EU MDR Article 117 concerns medicinal products with an integral device constituent and changes how the device part's General Safety and Performance Requirements may need to be documented in the medicines application context.
That is not the same decision tree as FDA PMOA and lead-center assignment. If Europe is in scope, the Article 117 section should be a separate question list for EU regulatory counsel or notified-body/medicines review planning, not a shortcut translation of the FDA path.
What TrueMedDevice can prepare
TrueMedDevice can prepare a source-backed combination-product briefing pack: product-function map, PMOA assumption table, RFD/Pre-RFD question set, application-pathway caveat table, fee-source references, GMP source ledger, and EU Article 117 issue list.
Source ledger
What it can tell you
The regulatory framework for product jurisdiction, PMOA-related designation questions, and Request for Designation procedures.
What it cannot decide
The PMOA or lead-center answer for a specific product without product facts and qualified review.
What it can tell you
How FDA describes the RFD process, Office of Combination Products submission context, and links to product-classification guidance.
What it cannot decide
Whether your product should submit an RFD, Pre-RFD, or another interaction first.
What it can tell you
FDA's current final Pre-RFD guidance, including the informal, non-binding feedback purpose and the information FDA says sponsors should provide.
What it cannot decide
Whether Pre-RFD feedback is sufficient for a specific product or whether a formal RFD or other FDA interaction is needed.
What it can tell you
The types of information FDA recommends for an RFD package.
What it cannot decide
Whether the package is complete or which center FDA will designate.
What it can tell you
High-level FDA thinking on combination-product premarket pathway coordination and when one or more applications may be involved.
What it cannot decide
The final application strategy for a specific product.
What it can tell you
How FDA organizes current good manufacturing practice requirements for combination products.
What it cannot decide
The final quality-system design, compliance state, or inspection readiness of a manufacturer.
What it can tell you
Current medical-device user-fee tables for device submission types.
What it cannot decide
Whether a device submission is the right path or whether a small-business fee applies.
What it can tell you
Current PDUFA fee categories for drug application planning context.
What it cannot decide
Whether a drug application is required for a specific combination product.
What it can tell you
The EU MDR legal text, including Article 117 changes for medicinal products with an integral device constituent.
What it cannot decide
Whether a specific EU product falls under Article 117 or another medicinal-product/device route.
Frequently asked questions
Does this article tell me whether my product is a combination product?
No. It organizes the evidence and questions that qualified reviewers need when a product may include device, drug, or biologic functions.
Should every uncertain product file an RFD?
Not automatically. The practical step is to prepare RFD-quality facts and discuss whether an RFD, Pre-RFD, or another interaction is appropriate with qualified reviewers.
Can I assume a device-led product never needs a separate drug application?
No. FDA guidance should be applied to the specific product facts. The packet should frame one-application assumptions and separate-application risks as questions for qualified review.
Need a combination-product review packet before the consultant call?
TrueMedDevice can organize PMOA assumptions, RFD questions, source links, fee references, and open reviewer issues into one source-backed packet.