Swissmedic: Swiss Agency for Therapeutic Products

Swissmedic is Switzerland’s national authority for the authorisation and supervision of therapeutic products. Swissmedic’s official overview describes that remit in terms of drugs and medical products. Read this as an explanation of the authority’s role, not as a licence condition or a complete legal test for a particular operation.

For a manufacturer, the useful starting point is to identify the product, activity, establishment and decision under consideration. What product is involved? What will the organisation do, at which site, and what decision needs to be made? This planning approach avoids treating every interaction with Swissmedic as the same approval. Record those answers before choosing a regulatory route or assembling supporting documents.

This glossary uses the following hierarchy to keep authority and operational advice distinct:

• Binding legal text: consult the applicable provisions for the legal question, with their product, activity and jurisdictional scope.
• Official descriptions or guidance: use these to understand the authority’s remit or stated approach; distinguish explanation from a legal obligation.
• Nonbinding operational practice: use planning methods and evidence organisation to structure work, not to create additional statutory duties.
• Proposed software support: consider tools separately from regulatory authority; keep review, approval and release decisions with responsible people.

Apply the same distinction when reading related manufacturing terminology such as cGMP: a useful operational concept is not, by itself, a Swiss legal conclusion.

Scope check: for a product or activity proposed for Switzerland, consult the current Therapeutic Products Act (TPA) to assess the applicable legal scope. Keep that legal assessment separate from official descriptions of Swissmedic’s remit: an agency overview is not a product-specific route decision.

Use the following matrix as a practical scoping tool, not a legal classification or permission to proceed. Give each unresolved question an owner before planning submissions or operational changes.

For borderline presentations, record intended use, composition, claims, users and proposed activities, then assign the classification question to a competent reviewer. Do not classify solely from the commercial category. Use the Swiss food–therapeutic product boundary and sterile or aseptic supplement format boundary as related review topics, not substitutes for that assessment.

For cross-border work, keep a separate record for each market. Frame any recognition question around the exact product, activity and decision involved, then direct it to the current applicable instruments. Record the instrument reviewed, review date, reviewer and conclusion, including unresolved conditions. Avoid carrying a Swiss conclusion into an EU plan without a distinct jurisdiction-specific assessment.

In common regulated-manufacturing usage, these terms organise different questions and evidence. The comparison below is an operational review aid, not a set of statutory definitions or Swiss licence conditions. Product authorisation concerns a product-level decision; establishment-licence review concerns the named holder, locations and activities; inspection review concerns an assessment and its observations; internal quality release concerns a controlled disposition decision.

Keep each document’s scope visible in the review record: subject, issuer, date, activities covered and unresolved questions. Avoid collapsing these into a single approved status. For example, a site document and a batch-release decision answer different questions even when both relate to the same manufacturing operation. Link an unresolved inspection observation to the relevant deviation record, where applicable, rather than treating the existence of a response as evidence of closure.

An internal readiness assessment is the organisation’s documented evaluation of its evidence and open questions, not a regulatory decision. Record its intended purpose, the evidence considered, remaining uncertainties and the next review action. This keeps the conclusion bounded: readiness for an internal review is not interchangeable with the outcome of an authority’s decision.

For medicines intended for Switzerland, the following is an internal planning workflow, not the official Swiss authorisation procedure. It organises review questions and responsibilities without prescribing a filing route or regulatory outcome.

Workflow diagram — the compact sequence reference: Product-and-market scope → review questions → assigned owners → evidence assembly → gap resolution → documented review → ongoing change assessment.

Start with the product, intended market, activities and decision under consideration. Turn uncertainties into specific questions rather than collecting documents indiscriminately. For each question, identify the evidence needed, its owner and the person accountable for the review conclusion.

• Regulatory affairs: assess which current Swiss provisions and official guidance apply, and what regulatory action may follow.
• Quality: assess quality-system implications, unresolved deviations and the adequacy of supporting review records.
• Manufacturing: explain process feasibility, site capabilities and the production evidence supporting proposed activities.
• Supply chain: map physical movements, storage conditions, distribution partners and operational handovers.
• Safety: assess emerging safety information and coordinate the question of reportability with regulatory affairs.

The evidence owner maintains the source record and explains its context; the conclusion owner evaluates whether it answers the question. These responsibilities can sit with different people. Resolve gaps through named actions, then record the conclusion, rationale, remaining uncertainty and human approval. Escalate unresolved resource or accountability issues through management review.

A proposed product change, site change, new distribution arrangement or safety signal can prompt internal reassessment. Link planned changes to change control, but leave the applicable filing route, reportability determination and legal timing to the relevant current-text assessment. These events are planning prompts, not declarations of Swiss filing duties. Keep subsequent evidence, exception and control reviews tied to the affected question rather than restarting the entire lifecycle.

GMP means good manufacturing practice; GDP means good distribution practice. For background, see cGMP and pharmaceutical GDP. The practical task here is to organise evidence around a defined site and activity. The following dossier is a suggested review structure, not a prescribed Swissmedic submission format or a statement of Swiss legal requirements.

Build a site-specific dossier

• Identify the establishment, legal-entity name and physical address. Make it clear which location the review concerns, especially where an organisation operates several sites.
• Describe the activities under review and index the relevant document references. Record each document’s identifier, version and relationship to the activity being assessed.
• Group inspection correspondence with response records and assign follow-up owners. Give each owner a specific unresolved question or evidence task rather than a general instruction to prepare for inspection.

Read inspection evidence in context

Start with the present operational question: does this assessment address the location and activity now being considered? Read the assessed location, activities examined, observations and responses together. Then identify subsequent changes that could affect the record’s relevance. A favourable label alone is not a sufficient basis for that assessment; explain what the underlying evidence supports and what remains unresolved.

Separate action evidence from closure status

For each observation, connect the proposed action, implementation record and effectiveness assessment. These answer different questions: what was intended, what was done, and whether it addressed the problem. A closure status does not explain those steps. Link the CAPA effectiveness check to its supporting records so the reviewer can evaluate the closure rationale rather than infer success from completion alone.

For medical devices in Switzerland, Swissmedic’s medical-device overview states that, unlike medicinal products, devices do not undergo an official authorisation procedure and identifies effective market surveillance as its focus. This is the agency’s description of its remit, not a checklist of binding manufacturer obligations.

The practical evidence-organising question is therefore: which device and parties are involved, what information explains the issue, and how does that information connect to the investigation and resulting actions? The following is a nonbinding review model, not a statement of Swiss market-access or vigilance duties.

• Identify the device: record its name, model or version and available identifiers; distinguish confirmed identity from assumptions.
• Identify the parties: connect the manufacturer, relevant supply-chain contacts and reporter to their actual involvement in the case.
• Connect the evidence: link relevant technical records and distribution information to complaints, investigation material and resulting actions. Preserve the relationship between each observation and the device concerned.

Keep intake separate from regulatory assessment

At intake, preserve what was reported, including the reporter’s description and supporting material, without rewriting it as a confirmed defect or regulatory conclusion. Identify the product, then assess what the available information establishes and what remains uncertain.

Assign unresolved device-classification questions or reportability questions to a regulatory specialist. Keep the specialist’s assessment distinct from the original report and investigation observations. A useful review record names the unresolved question, its owner and the information needed to resolve it; an incomplete intake should remain visibly incomplete rather than becoming an unsupported conclusion.

The following data-model diagram is a proposed internal schema for organising a Swissmedic-related review, not a Swissmedic database specification. Its purpose is to make the basis of an assessment retrievable without treating linked records as interchangeable.

Product + establishment → review ← regulatory references + evidence items; review → internal decision, rationale and unresolved questions.

Give each review a stable identifier, a defined scope and an accountable owner. Link the relevant product and establishment records rather than copying their descriptions into disconnected files. Record why each evidence item matters, which conclusion it supports and which questions remain open.

Proposed interfaces and field ownership

Confirm the actual system of record for each field before connecting systems. Preserve source identifiers, document versions and reconciliation results alongside the review link. Record whether imported values matched their source and who resolved discrepancies. These are data integrity by design choices; MES–QMS integration should preserve those boundaries rather than create competing master records.

Separate evidence from judgement

Keep source evidence, the internal interpretation and any external decision as separate record types. Link an external decision to its issuing body and stated scope, not merely to an internal status label. A source update can create a change-control review task without silently replacing the approved interpretation; retain the earlier assessment and record the new disposition.

Software support here means a proposed workflow design for storage, linking, routing and retrieval. It does not establish compliance or confer regulatory permission. Designated people remain responsible for internal approval and release decisions.

These hypothetical exercises illustrate internal review practice, not Swiss legal requirements or reported events. Each ends with a proposed next action rather than a regulatory outcome.

Medicines case: proposed outsourced packaging

Assumptions: a medicinal product is intended for Switzerland; controlled product and site records already exist; outsourced packaging is proposed at a different site. The unit of analysis is the proposed change record, managed through change control. The review question is whether the proposal identifies the intended establishment and activity clearly enough for an internal readiness decision.

Compare the operational plan with the controlled product record, site record and referenced establishment document. Record the proposed packaging activity, physical location, site name and document version. Here, the operational plan names a site differently from the establishment document. That mismatch leaves identity unresolved; it does not establish whether the proposal is acceptable or unacceptable.

Assign identity reconciliation to the supplier-quality reviewer, supported by the site-record owner: determine whether the names refer to the same establishment and retain the supporting explanation. Separately, assign regulatory affairs to assess the proposed site and activity against the relevant regulatory records and applicable Swiss scope. A corrected name alone does not answer the activity-scope question.

Proposed internal disposition: keep readiness unresolved while those questions remain open. The change owner records both assignments and their dependencies; the quality approver reviews the reconciled identity and scope assessment before recording the internal readiness conclusion. Any associated technology-transfer planning references that assessment. This exercise does not select a filing route.

Device case: complaint with a conflicting product description

Assumptions: a distributor reports a complaint concerning a device intended for Switzerland, and catalogue and lot identifiers are available. The unit of analysis is the complaint record. The distributor’s product description differs from the controlled product name, leaving uncertainty about which device the narrative describes.

Preserve the original complaint and compare its identifiers with controlled product and distribution records. Suppose those records associate the catalogue and lot identifiers with a controlled product, but do not explain the different description. Record that partial match and the remaining uncertainty rather than silently replacing the distributor’s wording.

The complaint owner requests clarification from the distributor and links the comparison records. Technical reviewers assess the reported problem; the designated vigilance or regulatory reviewer assesses reportability with the uncertainty visible. Those reviews can proceed alongside identity clarification. The proposed next action is documented clarification and parallel assessment, supported by the original report and identifier matches—not closure based on a name correction, a reporting deadline or a final regulatory disposition.

In a Swissmedic-related review, treat broken source links, conflicting document versions, duplicate establishment identities, incomplete data imports and external statuses that differ from internal records as evidence exceptions. This proposed information-control approach flags uncertainty; it does not silently convert a discrepancy into an authorisation, licence or surveillance status.

Use an exception-based review queue to make affected decisions visible while recovery proceeds:

1. Preserve the received information, including its origin, receipt date and conflicting values. Keep the original record rather than overwriting it.
2. Identify affected reviews and decisions. Mark where reviewers have relied on the disputed version, identity or status.
3. Assign a named owner and next action, distinguishing record-repair work from questions requiring quality or regulatory judgement.
4. Reconcile against the chosen authoritative source for that question. Check document identity and revision, establishment identifiers and import completeness; investigate status differences rather than accepting the newest entry automatically.
5. Obtain review of the proposed correction. Retain the resolution rationale, supporting references and remaining uncertainty through an appropriate audit trail review workflow.

Keep data reconciliation and substantive assessment as separate status fields. A restored link can close a link-repair task while assessment of the linked document remains pending. Likewise, merging duplicate establishment records does not settle whether the establishment’s activities match the question under review. Close each track on its own reviewed rationale, with an owner for any unresolved technical or regulatory question.

The matrix below illustrates practical record controls, not published Swissmedic inspection findings or additional legal requirements. Use the term comparison above to keep each record tied to the question it can answer.

Test the controls by asking a reviewer who did not assemble the records to reconstruct a decision. Can they identify the source version used, follow the reasoning, locate open questions and name the responsible owner without relying on an oral explanation? Record any missing connection and assign a next action. This exercise tests traceability; it does not establish regulatory acceptance.

Use the exception-recovery method above for failures. Where version history is unclear, an audit trail review workflow can structure the check; recurring unresolved issues can feed management review.

Use this proposed checklist to close an internal Swissmedic-related readiness review. It is a practical handover tool, not a statutory inspection checklist or compliance certification.

Escalate unresolved resource or accountability issues through management review. Keep recurring review event-driven unless an applicable requirement or internal procedure establishes a schedule.

Handover format: review scope; evidence references and versions; recorded decisions and boundaries; unresolved matters; responsible owners and next actions; next reassessment trigger. Have the receiving owner acknowledge the handover, including any remaining blockers, rather than treating checklist completion as a generic compliance declaration.