Information date: 4 September 2026 — FDA defines a combination product as a product composed of two or more regulated components, including drug-device combinations, and assigns oversight according to the product’s primary mode of action. Knowing that statement is not enough for an operating, research or compliance decision. The team must first establish who and what it applies to, how the effect reaches the real process, and which evidence would justify action.
Verified facts and scope
FDA defines a combination product as a product composed of two or more regulated components, including drug-device combinations, and assigns oversight according to the product’s primary mode of action.
A peptide active ingredient may reach users as a vial, prefilled syringe, pen, pump, tablet or other presentation. Route, formulation, container closure, instructions, device interface and intended user can change the evidence needed even when the molecular sequence is unchanged.
How the effect reaches operations
The formulation controls stability and exposure, while the device controls dose delivery and user interaction. Manufacturing variation or interface error can therefore alter the administered dose without changing the nominal strength on the label.
Reviewing only peptide purity may miss extractables, delivery accuracy or human-factor failures. Reviewing only the device may miss aggregation, adsorption and degradation over the product’s shelf life and use conditions.
For “Peptide Applications Need a Product-Mode Map: Molecule, Formulation and Device Cannot Be Reviewed Separately”, official rules or published findings, direct evidence from the relevant product or process, and assumptions that remain untested should be recorded separately. A broad source defines the external boundary; it does not replace batch records, protocols, contracts, labels or direct observations.
Decision
Build one product-mode map before selecting tests: identify each constituent, its function, every contact material, the user steps and the primary therapeutic action. A component without an evidence owner is a development hold.
Implementation checklist
- Draw the complete path from drug substance through formulation, container, device and administration.
- For each interface, list the failure that could change identity, strength, quality, dose or user understanding.
- Test one representative use scenario with the intended presentation and predefined acceptance criteria.
- Assign one decision owner, one implementation owner and a dated review point for “Peptide Applications Need a Product-Mode Map: Molecule, Formulation and Device Cannot Be Reviewed Separately”.
- For “Peptide Applications Need a Product-Mode Map: Molecule, Formulation and Device Cannot Be Reviewed Separately”, archive the source page, access date, applicable population or entity, and internal evidence both supporting and opposing the current decision.
- When a rule, formulation, supplier, protocol or observed result changes, reopen only the affected question in “Peptide Applications Need a Product-Mode Map: Molecule, Formulation and Device Cannot Be Reviewed Separately”.
Evidence and review
For “Peptide Applications Need a Product-Mode Map: Molecule, Formulation and Device Cannot Be Reviewed Separately”, start with one real case rather than an abstract checklist. Record the input version, responsible owner, start time, observed result and stop condition. If the team cannot complete “Draw the complete path from drug substance through formulation, container, device and administration.” with current evidence, it should not expand the process to more products, patients, suppliers or markets. The first review should focus only on facts capable of changing the decision.
The second control follows “For each interface, list the failure that could change identity, strength, quality, dose or user understanding.”. Keep the source date, applicable population or entity, deadline, cost effect and owner in the same evidence file. A wording preference does not justify a new version. A repeated discrepancy, an unsupported health claim or a regulatory mismatch does: correct that point and hold release until the evidence is available.
After “Test one representative use scenario with the intended presentation and predefined acceptance criteria.”, compare the intended outcome with what actually happened. Apply the same success criteria to each later expansion. If only one number, date or responsibility changes, update that field and the affected conclusion instead of recreating evidence that remains valid. This keeps the decision traceable without turning review into an open-ended rewrite cycle.
Counter-scenario and ownership
The review must also test the opposite of the expected outcome. If “The formulation controls stability and exposure, while the device controls dose delivery and user interaction. Manufacturing variation or interface error can therefore alter the administered dose without changing the nominal strength on the label.”, the record should already identify who detects it, who can pause the process, and who communicates with affected people or authorities. Direct, current evidence about the studied product, population or transaction takes priority when it conflicts with a broad market statement. Keep both the approval reason and the rejection reason. Later evidence should reopen only the affected question, not trigger an unsupported rewrite of findings that still hold.
Limits of the conclusion
Regulatory classification and evidence requirements are product-specific. This framework does not establish safety, effectiveness, approval status or a particular FDA centre assignment.
