The regulatory pathway you choose at this stage determines your development cost, your timeline, and which authorities you will be dealing with for the next several years. Centralised, decentralised, mutual recognition, or national procedure: each has different implications for which countries assess your dossier, how long the review takes, and what kind of product information format you will need.

For innovator products, early decisions around orphan designation, PRIME eligibility, and paediatric strategy (PIP or waiver) shape the development programme in ways that are difficult to reverse later. Orphan designation must be applied for before the marketing authorisation application. PRIME designation, if granted, gives access to early and enhanced EMA dialogue. And the Paediatric Committee (PDCO) decision on your PIP or waiver needs to be in hand before you submit your MAA, not still in progress.

For generics, the key early decisions are reference product selection, bioequivalence strategy (including BCS-based biowaiver evaluation where applicable), and the choice of filing route. For herbal medicines, the classification as traditional herbal or well-established use determines the evidence requirements.

At every starting point, defining the Target Product Profile with regulatory input gives your development team a shared reference point and prevents misalignment between what you are building and what the authorities will expect to see.

“Biologic” covers three categories with fundamentally different development requirements: classical biologics and vaccines, biosimilars, and advanced therapy medicinal products (ATMPs, including gene therapies, somatic cell therapies, and tissue-engineered products). The regulatory pathway, the evidence expectations, and the manufacturing complexity all depend on which category your product falls into.

Classical biologics follow the centralised procedure (mandatory for most). Early scientific advice from EMA is highly valuable for nonclinical model selection and potency assay design. For mRNA-based products, confirm whether the indication triggers ATMP classification or falls under the immunological medicinal product framework; the answer affects which committee assesses your application.

Biosimilars require a reference product strategy from day one: which reference product, sourced from which market, with what analytical similarity study design. The EMA’s streamlining of biosimilar requirements has reduced some nonclinical and clinical expectations, but the comparability exercise remains the backbone of the programme.

ATMPs need early engagement with EMA for classification (CAT classification request) and with national authorities on hospital exemption applicability. Manufacturing complexity for ATMPs is uniquely high: autologous vs. allogeneic, scale-out vs. scale-up, and chain-of-identity/chain-of-custody systems all need to be planned before development begins.

Do you know which MDR classification rule applies to your device?

Most manufacturers have a general sense of their device’s risk class, but MDR Annex VIII contains 22 classification rules with interdependencies that regularly produce surprises, particularly for software components, devices incorporating medicinal substances, and novel technologies that didn’t exist when the rules were written. Getting the classification wrong means choosing the wrong conformity assessment route, which means the wrong Notified Body scope, which means rework.

The classification decision triggers everything else: which Notified Body you need (and whether you need one at all), what clinical evidence is expected, and how your quality management system must be structured. Class III and implantable devices face the most rigorous Notified Body scrutiny and the longest review cycles, while most Class I devices can self-declare conformity, but only if they genuinely fall into that class.

At this stage, you should also be defining the intended purpose with regulatory precision. Under MDR, the intended purpose is the legal basis on which your entire regulatory submission rests, and regulators will hold you to exactly what it says. Ambiguity here creates problems at every subsequent stage.

Most IVDs that were self-certified under the old Directive now require a Notified Body under IVDR.

IVDR replaced the old risk-based list system with a four-class structure (A, B, C, D) under Annex VIII. The practical effect is that the majority of IVDs moved up in classification, and many products that previously needed no third-party review now require Notified Body involvement. If you are still working from your IVDD classification, the first step is to reassess under the IVDR framework.

For companion diagnostics, the classification question is just the beginning. A CDx must be co-developed with the corresponding medicinal product, and the regulatory timelines need to be synchronised from the start. The pharma sponsor’s biomarker strategy, the clinical trial protocol, and the sample access arrangements all need to be agreed early, because the CDx performance data is typically generated within the drug’s clinical trial.

You should also check whether Common Specifications have been designated for your product category. Where they exist, Common Specifications are mandatory unless you can demonstrate that your alternative solution meets at least an equivalent level of safety and performance.

Does your software qualify as a medical device?

This is the first question, and everything else depends on the answer. MDCG 2019-11 provides the decision flowchart: if the software is intended to process, analyse, or create medical information and the output is for individual patient management, it is likely a medical device under MDR. If it is a general-purpose tool (data storage, communication, administrative), it may fall outside the device definition entirely.

If the answer is yes, classification follows MDR Rule 11 (or IVDR Annex VIII for diagnostic software), which assigns risk classes based on the severity of the clinical situation the software addresses.

If AI or machine learning is involved, a further layer applies. The EU AI Act creates parallel obligations for high-risk AI systems, including medical device software classified as high-risk. From August 2027, AI Act conformity assessment requirements apply alongside MDR.

For teams considering the DiGA pathway in Germany (or equivalent national digital health reimbursement schemes like PECAN in France or DTAC in the UK), eligibility criteria should be checked at this stage.

The first question regulators will ask, and the one that shapes your entire development programme, is: what is the primary mode of action? A drug-device combination classified as a medicinal product follows the pharmaceutical regulatory pathway with device conformity assessment for the device component. Classified as a medical device, it follows MDR with consultation of a medicines authority on the drug component.

Beyond the primary mode of action, you need to establish which type of combination product you are developing. The EU framework distinguishes between integral drug-device combinations (where the drug and device form a single entity), co-packaged products (separate items supplied together), and devices incorporating an ancillary medicinal substance. Each type follows a different regulatory process.

Connected combined products (CCPs) add a digital layer: a medicine combined with a software component (such as a smart inhaler with a companion app). For CCPs, the software component may qualify as a medical device under MDCG 2019-11, creating a three-way regulatory intersection.

Your quality system needs to satisfy both GMP (for the pharmaceutical component) and the relevant MDR requirements (for the device component) from the start. Retrofitting a dual QMS later is significantly more expensive and disruptive than building it right from the beginning.

Marketing a food supplement that makes a medicinal claim can trigger reclassification and product recall.

Product classification in the EU is a legal determination, not a label you choose. A product’s classification as a medicinal product, medical device, food supplement, cosmetic, or biocidal product depends on its composition, its mechanism of action, its intended purpose, and how it is presented to the market. National authorities can and do challenge classifications, and the consequences include product withdrawal, regulatory action, and the cost of redeveloping to meet the correct framework.

The most common borderline questions arise between: medical device and medicinal product (primary mode of action assessment), medical device and cosmetic (intended purpose and claims), medical device and food supplement (functional claims vs. physiological effects), and medical device and biocidal product (antimicrobial mechanism).

If your product sits near any of these boundaries, a structured classification assessment early in development prevents discovering the problem at submission, or worse, after launch.

Food supplements, functional foods, and cosmetics are regulated under their own EU frameworks, separate from pharmaceutical and medical device legislation. The regulatory requirements, the evidence expectations, and the market access pathways are distinct.

For food supplements, the first questions are ingredient permissibility, maximum levels, claims eligibility, and novel food status. For cosmetics, the early focus is ingredient compliance under Regulation (EC) No 1223/2009, the intended cosmetic function, and any border issues where a product claim could move it into medicinal or device territory.

In both sectors, claims strategy matters early. A scientifically attractive claim is not necessarily a legally usable claim. Getting this wrong at concept stage leads to reformulation, relabelling, or loss of the intended commercial position.

CMC is where most marketing authorisation delays originate.

Process development, formulation optimisation, analytical method development and validation, stability programmes, and manufacturing scale-up all converge during this phase. Module 3 of the CTD is the largest and most technically detailed section, and inconsistencies between the process description, specifications, and stability data are among the most common deficiency questions.

Scientific advice from the EMA or a national authority is particularly valuable during this phase, especially for pivotal study design, comparability strategy, and non-standard approaches to specification-setting.

Quality system readiness matters here too. Deviation and CAPA management, document control, and vendor qualification all need to be operational. If you will need a Manufacturing Authorisation (MIA) or Wholesale Distribution Authorisation (WDA), the application process should start during this phase.

Changing your manufacturing process after Phase II without a comparability protocol will cost you a year.

Biologics CMC is uniquely unforgiving. The product is defined by the process, so any change to the cell culture conditions, purification steps, formulation, or manufacturing site triggers a comparability exercise. If you don’t have a comparability protocol in place before the change, you will need to generate the data retrospectively.

For biosimilars, the comparability exercise between the biosimilar and the reference product is the central development activity. For ATMPs, chain-of-identity/chain-of-custody systems and potency assay development are critical path items.

If your product includes a delivery device (prefilled syringe, autoinjector, infusion system), drug-device integration work begins here. Human factors engineering, MDR Annex I compliance, and extractables/leachables testing run alongside the biologics CMC programme.

This is where your intended purpose is translated into evidence requirements. The risk management file under ISO 14971 becomes the central thread linking design inputs, non-clinical testing, usability engineering, and eventually clinical evidence.

Biocompatibility (ISO 10993 series), electrical safety, EMC, software verification and validation, sterilisation validation, packaging validation, shelf-life testing, and performance bench testing all need to be scoped based on the device’s intended use and design characteristics.

For software devices, the preclinical phase is largely a verification and validation phase: software requirements specification, architecture, cybersecurity threat modelling, verification planning, and usability engineering outputs all need to be generated before the clinical stage.

Analytical validation comes before clinical performance.

Before an IVD enters the clinical performance stage, it must demonstrate analytical validity: limit of detection, analytical sensitivity/specificity, reproducibility, repeatability, interfering substances, and specimen stability.

For companion diagnostics, analytical validation must be completed early enough to support inclusion in the medicinal product’s clinical programme. The CDx analytical validation must be complete before the pivotal drug trial reads out, and the CDx labelling must be drafted in parallel with the drug labelling.

Software development teams accustomed to agile, rapid-iteration workflows often find the regulatory documentation requirements jarring. IEC 62304 and agile development are compatible, but only if you build the documentation framework into your development process from the start.

The software safety classification under IEC 62304 (Class A, B, or C) determines how much lifecycle documentation you need. Getting the classification right avoids either over-documenting or under-documenting.

For AI/ML-based devices, additional considerations apply: training data governance, model validation strategy, bias assessment, and a predetermined change control plan if you intend to update the algorithm post-market without triggering a new conformity assessment each time.

Developing a combination product means running two development programmes in parallel: drug CMC and device design controls. The challenge is keeping them aligned, because decisions in one track affect the other.

Container closure integrity, extractables and leachables, and drug-device compatibility studies sit at the intersection. Shelf-life testing must account for drug-device interaction, not just the drug substance and product in isolation.

Human factors engineering begins here. For combination products, usability studies must cover both the device operation and the drug administration. Formative usability testing follows IEC 62366 and feeds into the risk management file.

Development follows the confirmed classification. The evidence you generate, the quality system you operate, and the documentation format you use must all align with the regulatory framework for your classified product type.

Throughout development, monitor for reclassification triggers. Changes to the formulation, the claims, or the intended use can shift the classification boundary.

Development of food supplements and cosmetics centres on formulation, stability, safety evidence, and claims strategy. For food supplements, ingredient compliance, maximum levels, and any novel food requirements must be resolved during formulation. For cosmetics, the ingredient list must comply with Annexes II through VI of Regulation 1223/2009.

Claims strategy should be developed in parallel with formulation. For food supplements, only authorised health claims may be used. For cosmetics, claims must be truthful, evidenced, and compliant with the Common Criteria. Claims that imply a medicinal or device-like effect risk reclassification.

By this stage, your formulation, manufacturing process, analytical methods, and stability strategy should be converging toward the commercial target. Module 3 content is taking shape, and the question is no longer what the product could be, but whether the data package will support the dossier you intend to file.

This is where strategic writing and technical consistency matter. We often see development programmes generate the right underlying data, but fail to present it coherently in a way that anticipates authority review questions.

Biologics development is highly sensitive to process drift. Scale-up, comparability, potency, impurity profiling, and reference standard strategy all need tight control before the product moves into the pivotal stage.

For ATMPs, manufacturing readiness is especially critical because commercial and clinical manufacturing often remain closely linked. Late process changes can trigger major regulatory consequences.

During design and development, your technical documentation begins to take its final form. Design inputs and outputs, verification planning, validation evidence, usability engineering, and risk controls all need to be traceable and internally consistent.

A common problem is that manufacturers build the product first and try to reconstruct the design history file later. That usually creates gaps that the Notified Body will find quickly. Traceability from user needs to design inputs, risk controls, verification, and validation is non-negotiable.

For IVDs, design and development runs through performance evaluation, which integrates scientific validity, analytical performance, and clinical performance. The performance evaluation plan and report are core IVDR documents.

Companion diagnostics add a dependency: your development programme must stay synchronised with the medicinal product timeline. If the drug indication changes, the CDx intended purpose may need to change with it.

Software teams need a development process that produces both code and audit-ready evidence. Requirements management, architecture control, verification records, cybersecurity documentation, and usability engineering must all be built into the workflow.

For AI-enabled tools, your validation strategy must show not just model performance but also data provenance, bias assessment, and human oversight logic.

At this stage, the integration points between the drug and device become operationally critical. Device design changes can affect delivered dose, extractables and leachables outcomes, human factors findings, and the final regulatory pathway.

Your development programme should be structured so that pharmaceutical and device teams are not working in parallel isolation.

Development evidence must continue to support the classification position. If your intended use evolves, the classification analysis should be revisited before you lock in further technical or clinical work.

This avoids generating evidence for the wrong legal framework.

Development work in food supplements and cosmetics should create a defensible package for formulation, safety, claims, and marketability. Stability data, claims substantiation, and product information need to support the commercial proposition without crossing the regulatory line.

This is especially important when products are positioned close to the medicinal or device boundary.

Clinical trial applications in the EU are submitted through CTIS under the Clinical Trials Regulation. The IMPD forms the core of the submission and must include your quality, nonclinical, and clinical data.

Protocol design, dose-finding strategy, endpoint selection, and statistical analysis planning all need to reflect current regulatory expectations. If you received scientific advice, the protocol should demonstrably address any recommendations.

If you are a non-EU sponsor, you need an EU Legal Representative or an EU-based sponsor to hold the regulatory responsibilities under the CTR. We act as EU Sponsor or Legal Representative for clinical trials.

Pharmacovigilance planning should begin during the clinical phase. Your QPPV needs to be identified and your PV system master file outlined before you submit your marketing application.

Biologics clinical programmes often carry additional layers: immunogenicity, comparability across process changes, and complex endpoint strategies for advanced therapies.

For ATMPs, long-term follow-up planning often begins during the clinical phase, not after approval.

Clinical evidence for medical devices works differently from pharmaceutical clinical trials. There is no centralised submission through CTIS. Each national competent authority and ethics committee has its own procedural requirements.

For Class III and implantable devices, clinical investigations are typically expected under MDR Article 61, unless you can demonstrate equivalence, which MDCG 2020-5 has made increasingly difficult.

Your clinical investigation plan must align with the conformity assessment route agreed with your Notified Body. The clinical evaluation plan should already be in place before the investigation begins, because the investigation generates evidence to feed into it, not the other way around.

Post-market clinical follow-up (PMCF) planning starts now: your PMCF strategy should be designed alongside the pre-market investigation.

A clinical performance study for an IVD measures diagnostic accuracy, not therapeutic effect.

The endpoints are sensitivity, specificity, positive and negative predictive value, and likelihood ratios. IVDR Annex XIII and XIV set the requirements, and competent authority notification is required under Article 58.

For companion diagnostics, the clinical performance evidence is usually generated within the drug’s clinical trial. The CDx needs to be analytically validated before the drug trial starts, and sample collection must be embedded in the trial protocol.

For self-testing IVDs, lay user studies are required to demonstrate that untrained users can perform the test and interpret the results correctly.

For SaMD, clinical evidence means demonstrating clinical benefit, not just technical performance. The evidence route depends on the intended purpose, risk class, and whether you rely on literature, retrospective data, or prospective clinical investigation.

For digital therapeutics and reimbursable digital health apps, payer evidence expectations may go beyond what is needed for CE marking.

The clinical programme must generate evidence for both the drug and the device components. Human factors validation (summative) studies are typically required alongside the clinical efficacy programme.

Safety reporting is dual-tracked. Drug-related adverse events follow pharmaceutical PV rules. Device-related incidents follow MDR device vigilance requirements. Coordinated assessment prevents gaps or contradictions.

Evidence requirements differ fundamentally by classification. Medicinal product: full clinical trial programme. Medical device: clinical investigation or evaluation. Food supplement: substantiation dossier. Cosmetic: safety assessment.

If you are developing a product that could be classified under more than one framework, understanding these differences early allows you to design an evidence strategy that covers the most demanding scenario.

For food supplements and cosmetics, this stage is less about formal clinical trials and more about building a robust substantiation package. Human data, literature support, safety evidence, and claims substantiation all contribute to whether the product can be marketed credibly and compliantly.

For food supplements, any efficacy language must still fit within authorised health claim rules. For cosmetics, support for product claims must meet the Common Criteria and be consistent with the product’s cosmetic purpose.

The MAA is where everything converges. Your CMC data, nonclinical package, clinical evidence, and product information must form a coherent CTD-format dossier.

Your eCTD must comply with current EU validation rules; non-compliant submissions are rejected technically before any scientific review begins. The SmPC, PIL, and labelling must follow QRD template standards.

A QPPV must be in place and named in the application. If you are a non-EU company, your EU legal representative, MAH structure, and QPPV location need to be resolved before you submit. Paediatric obligations apply unless you have a PDCO waiver or deferral.

Most biologics and all ATMPs must use the centralised procedure. Module 3 carries particular weight given the complexity of biologics manufacturing data.

For ATMPs, conditional marketing authorisation accelerates access but creates post-approval commitments including annual renewal obligations.

Environmental risk assessments for GMO-containing ATMPs are required in each member state where the product will be used.

The conformity assessment is a technical review that determines whether your device reaches the market.

For devices requiring Notified Body involvement (Class IIa and above), this means a rigorous review of your complete technical documentation. Deficiencies mean conditions, delays, or rejection.

The clinical evaluation report and the risk management file are typically the first documents reviewed and the most common sources of questions.

Before CE marking, your EU Authorised Representative (for non-EU manufacturers), Person Responsible for Regulatory Compliance (PRRC), and EUDAMED registration infrastructure need to be in place.

For Class B, C, and D IVDs, the conformity assessment requires Notified Body involvement. Class D devices face the additional requirement of an EU Reference Laboratory opinion.

For companion diagnostics, the conformity assessment triggers a mandatory consultation under IVDR Article 48. This consultation runs on its own timeline and its outcome can affect the CDx approval.

In parallel, FDA pathway for CDx often requires a PMA, which is a longer review than most IVD submissions.

The technical documentation for SaMD includes software-specific elements: IEC 62304 lifecycle outputs, cybersecurity documentation, and clinical evaluation report.

For AI/ML-based devices, the submission must additionally address AI Act conformity requirements including data governance, model transparency, human oversight, and accuracy metrics.

For DiGA, the BfArM Fast-Track application runs on a separate timeline from the MDR conformity assessment.

Two parallel submissions, or one integrated dossier? The answer depends on the primary mode of action.

Drug-led: pharmaceutical MAA to the competent authority, with NB opinion on the device component under MDR Article 117. Device-led: NB conformity assessment under MDR, with medicinal authority consultation on the drug component. Co-packaged: drug and device approved independently.

Timeline coordination between the pharmaceutical and device regulatory pathways is critical. NB review cycles and authority assessment timelines do not naturally align.

The submission type follows the classification. A medicinal product requires an MAA. A medical device requires NB conformity assessment. A food supplement requires national notification. A cosmetic requires CPNP notification.

Labelling and claims must align precisely with the classified status. A product with claims that imply a pharmacological effect may be challenged as an unauthorised medicinal product.

Food supplements require national notification in each Member State, and procedures vary significantly from country to country. For novel food ingredients, centralised EU authorisation under Regulation (EU) 2015/2283 must be completed first.

Cosmetics require CPNP notification before being placed on the EU market. The Product Information File and safety assessment must be complete, and the Responsible Person must be established in the EU.

This is also the stage where artwork, claims wording, warnings, and final label text need to be checked carefully against the target markets.

What happens between MA grant and first patient supply depends on whether you are launching an innovator or a generic.

Innovators: national implementation, pricing and reimbursement submissions, labelling finalisation, Art. 57 submission, PV system activation, medical information service, supply chain readiness. Launch sequence matters because of reference pricing.

Generics: the primary barrier is infrastructure. MAH, WDA, QP/RP, artwork, supply chain. Speed to market is the competitive advantage.

regulanet® enables coordinated market entry across 90+ countries.

Launch infrastructure includes everything required for small molecules plus additional requirements: cold chain validation for the commercial supply chain, ATMP hospital distribution logistics, and conditional MA annual renewal obligations.

For biosimilars, market access positioning around interchangeability is evolving country by country.

From 2025, oncology products and ATMPs fall within scope of EU Joint Clinical Assessments under the HTA Regulation.

CE marking is the regulatory finish line, but not the operational one. Several things need to happen before you can ship:

EUDAMED registration becomes mandatory from May 2026. UDI implementation on labelling, packaging, and in EUDAMED. Economic operator obligations for importers and distributors. Post-market surveillance activation: your PMS system must be operational from day one.

For international markets, we coordinate entry through regulanet® across 90+ countries.

The launch checklist follows the same structure as for medical devices: EUDAMED, UDI, authorised representative, PMS activation.

For companion diagnostics, the CDx labelling must be aligned with the corresponding drug labelling at launch. If the drug SmPC changes during approval, the CDx IFU must be updated to match.

For Class D IVDs with lot verification requirements, ongoing EU Reference Laboratory interaction continues post-launch.

Your app store listing does not replace your regulatory obligations.

CE-marked SaMD distributed through app stores must still comply with MDR post-market requirements. The app store review process has no regulatory standing.

EUDAMED registration, UDI, and authorised representative requirements apply to SaMD just as they do to physical devices.

For DiGA, BfArM listing enables reimbursement. Early alignment between your clinical validation plan and the payer’s evidence expectations prevents discovering at launch that your CE marking evidence doesn’t satisfy reimbursement criteria.

Launching a combination product means coordinating across both pharmaceutical and device regulatory streams simultaneously. Labelling must satisfy both frameworks. Supply chain must cover both GMP and device quality requirements.

Vigilance systems must handle both PV case processing and device incident reporting. Pricing and reimbursement may follow different pathways for the drug and device elements.

For borderline products, the primary ongoing risk at launch is claims compliance. National authorities across EU Member States actively monitor marketed products, and a claim that crosses the boundary can trigger enforcement action.

Market surveillance activity varies by Member State, so a claim that passes in one country may be flagged in another.

Once on the market, food supplements and cosmetics face active market surveillance. Labelling compliance, health claims compliance, allergen declarations, and local notification obligations all need to be managed carefully.

For cosmetics, the Responsible Person’s obligations continue after launch, including management of serious undesirable effects and maintenance of the Product Information File.

Claims compliance remains one of the highest risks at launch because wording that looks commercially attractive may not be acceptable in the target market.

Variations are the core activity: manufacturing changes, specification updates, supplier switches, labelling revisions. The revised EU Variations framework reclassifies some previously Type II changes to Type IB.

Pharmacovigilance: PSURs/PBRERs, signal detection, RMP updates, responses to referrals.

Lifecycle opportunities: new indications, line extensions, Rx-to-OTC switches, geographic expansion. Due diligence support is available for products being acquired or divested.

We coordinate global lifecycle maintenance through regulanet® across 90+ countries.

Post-approval life for biologics is shaped by comparability. Every manufacturing change triggers a comparability assessment.

For ATMPs, long-term follow-up obligations can extend for years or decades after treatment. The follow-up protocol and patient tracking systems must be maintained for as long as the obligation applies.

Pharmacovigilance involves higher-complexity safety profiles: immunogenicity data accumulation, donor-recipient risk tracking for ATMPs, and complex DSURs and PSURs.

The post-market phase carries continuous regulatory obligations. PMS reporting, vigilance, clinical evaluation updates, and NB interactions all continue for as long as the device is on the market.

PMS reporting: PMS Report (Class I) or PSUR (Class IIa+). Vigilance: serious incidents within 15 days, trend reporting, FSCAs. CER updates: living document incorporating new data. Design changes: assessed against MDCG significant change criteria.

If you are still transitioning legacy devices from MDD to MDR, the transition deadlines and NB capacity constraints add further planning pressure.

Post-market obligations include PMS planning, Post-Market Performance Follow-up (PMPF), and PSURs for Class C and D devices.

For companion diagnostics, changes to the drug’s SmPC or indication can directly affect the CDx’s intended purpose. This requires ongoing monitoring of the drug’s regulatory status.

If you still have legacy IVDs transitioning from IVDD to IVDR, classification under the new framework and NB capacity need active management.

Is your software update a significant change under MDR?

Every software update must be assessed against MDR significant change criteria. Your change management system must include a documented process for making this determination on every release.

For AI/ML-based devices, algorithm retraining is the central post-market regulatory challenge. Continuous learning algorithms face particular scrutiny.

Cybersecurity monitoring is ongoing. A cybersecurity incident affecting patient safety triggers vigilance reporting under MDR, separate from any GDPR data breach notification.

Lifecycle management is dual-tracked: pharmaceutical variations for the drug component and technical documentation updates for the device component.

A single change can trigger obligations on both sides. A reformulation may require updated extractables and leachables data affecting the device technical documentation. A device design change may affect the delivered dose, triggering a pharmaceutical variation.

A new Notified Body opinion or supplementary assessment may be required when the device component undergoes a significant change.

Classifications can be challenged years after launch. New case law, guideline revisions, or national authority decisions can shift the boundary for products in your category.

If you evolve your claims over time, each change must be assessed for its impact on the classification. We provide ongoing monitoring and proactive engagement with authorities when a classification challenge appears likely.

Post-market obligations for food supplements and cosmetics focus on surveillance, claims governance, dossier maintenance, and response to authority scrutiny. The key challenge is that compliance is not static: product claims, ingredients, and market expectations evolve.

For food supplements, national enforcement trends, health claims interpretation, ingredient restrictions, and novel food developments need to be monitored continuously. For cosmetics, the Responsible Person must maintain the Product Information File, review safety implications of any changes, and handle reportable serious undesirable effects.

A product that launches compliantly can still drift into non-compliance over time if claims expand, formulas change, or local requirements are not tracked closely.