What Is a Concerned Member State (CMS) in EU Regulatory Affairs?

A Concerned Member State (CMS) is a Member State participating in a mutual-recognition procedure (MRP) or decentralised procedure (DCP) in which another Member State acts as the Reference Member State (RMS). The RMS leads the assessment; each CMS participates in that assessment and retains responsibility for the national regulatory decision that follows the coordinated procedure.

Purpose and Regulatory Context

The CMS concept exists because MRP and DCP are neither purely national nor centrally authorised procedures. They coordinate several national competent authorities around one assessment while preserving national marketing authorisations.

This architecture should be distinguished from the centralised procedure. A centrally authorised medicinal product receives a Union marketing authorisation following the applicable EMA committee procedure and European Commission decision. In MRP or DCP, by contrast, one national competent authority acts as RMS and the other participating authorities act as CMSs. Agreement is reached through the coordinated procedure, after which the participating Member States adopt the corresponding national decisions.

The CMS is therefore not simply a geographic market and is not a passive recipient of the RMS assessment. It is a participating national competent authority with a defined scientific and regulatory role.

Legal Framework

Article 28 of Directive 2001/83/EC

Article 28 of Directive 2001/83/EC establishes the basic architecture. An applicant seeking authorisation in more than one Member State submits an application based on an identical dossier and requests one Member State to act as RMS. The other participating Member States are the Member States concerned by the application.

Where the medicinal product is already authorised, Article 28(2) provides the basis for mutual recognition. Where it has not yet received an authorisation at the time of application, Article 28(3) provides the coordinated assessment mechanism used for DCP. Article 28(5) links the conclusion of the procedure to national decisions that conform to the agreed assessment report, summary of product characteristics (SmPC), labelling and package leaflet.

The important legal distinction is therefore:

• the RMS leads and prepares or updates the assessment;
• the CMS reviews and participates;
• the participating Member States retain national decision-making responsibility within the agreed outcome.

MRP and DCP are not interchangeable

In an MRP, a national marketing authorisation already exists and the applicant seeks recognition in additional Member States. The existing authorisation and RMS assessment form the starting point.

In a DCP, the product has not yet received the relevant national marketing authorisations when the coordinated procedure begins. The RMS prepares the draft assessment and product-information documents while the CMSs participate in their review.

The CMS role is present in both procedures, but the procedural starting point differs.

The Relationship Between RMS and CMS

The RMS and CMS should be understood as complementary roles rather than as a hierarchy in which the CMS loses scientific independence.

A CMS can therefore question the RMS assessment. The purpose of coordination is to resolve scientific and regulatory issues through a common procedure, not to remove CMS scrutiny.

What a CMS Reviews

Depending on the application and procedural stage, CMS review may encompass quality, non-clinical and clinical evidence, benefit-risk, product information, and relevant risk-management material. The CMS asks whether the RMS conclusions are adequately supported and whether unresolved issues affect approvability under the proposed conditions of use.

For pharmacovigilance professionals, the most important point is that safety is not reviewed in isolation. A safety concern is interpreted in relation to the indication, target population, clinical benefit, alternatives, proposed warnings, contraindications and risk-minimisation measures. The CMS contributes to that integrated regulatory assessment.

Product Information as a Regulatory Outcome

The SmPC, labelling and package leaflet are part of the coordinated outcome described in Article 28. This matters for pharmacovigilance because approved product information affects how subsequent safety information is interpreted and managed.

A CMS may contribute to discussion of warnings, contraindications, adverse reactions, monitoring language and other safety-related wording during the procedure. Once harmonised wording is agreed and national decisions are adopted, subsequent local implementation should remain aligned with the applicable regulatory outcome.

When a CMS Disagrees

A CMS disagreement becomes legally significant when the conditions in Article 29 of Directive 2001/83/EC are met. If a Member State cannot approve the assessment report, SmPC, labelling or package leaflet because of a potential serious risk to public health, it must provide a detailed explanation of its position. The disagreement then enters the coordination mechanism provided by the legislation.

This threshold should not be diluted. A scientific question, preference for different wording or residual uncertainty is not automatically a potential serious risk to public health. Experienced regulatory teams distinguish ordinary points for resolution during assessment from an objection meeting the Article 29 threshold.

CMDh and unresolved disagreement

The Coordination Group for Mutual Recognition and Decentralised Procedures – Human (CMDh) coordinates questions concerning marketing authorisations for human medicines in two or more Member States. Where qualifying disagreement persists, CMDh provides the next coordination level under the applicable legal procedure.

The CMS and CMDh are therefore different concepts. A CMS is a national authority participating in a specific product procedure; CMDh is the coordination group through which Member States address relevant cross-Member-State regulatory questions and unresolved issues.

Post-Authorisation Role

The RMS/CMS relationship does not end when the initial procedure closes. Nationally authorised products may subsequently undergo variations, renewals, worksharing procedures, safety-related changes or other lifecycle actions in which coordinated handling remains relevant.

The exact role of a CMS depends on the procedure. It should not be reduced to the statement that “the RMS manages the product forever.” The medicinal product remains subject to national authorisations and to the applicable EU post-authorisation framework.

Variations

For MRP/DCP products, post-authorisation variations are processed under the applicable EU variations framework and current CMDh procedural guidance. The RMS commonly performs a coordinating role, while CMSs participate according to the type and scope of procedure.

A PV-originated change may therefore pass through several linked steps:

1. new safety evidence is evaluated;
2. the regulatory action required is determined;
3. a variation or other procedure is submitted where applicable;
4. RMS/CMS assessment is completed;
5. agreed product information is implemented nationally;
6. downstream systems, including safety and product-master data, are updated.

The CMS matters because the regulatory outcome must be correctly reflected in the national authorisation for its territory.

Pharmacovigilance Interfaces

The CMS is a regulatory-authority role, not an element of the MAH pharmacovigilance organisation. Nevertheless, the role intersects with PV repeatedly.

Relevant interfaces can include:

• assessment of new or changing safety information in an application;
• review of risk-management proposals;
• safety-related variations;
• implementation of harmonised product information;
• additional risk-minimisation measures where nationally implemented elements are involved;
• regulatory responses to signals, referrals or other Union procedures that affect nationally authorised products.

The operational lesson for an MAH is that a single European scientific conclusion can create multiple implementation obligations across the RMS/CMS product family. Regulatory affairs, pharmacovigilance, labelling and local affiliates therefore need a common product map and a common understanding of which national authorisations are affected.

CMS, National Requirements and Harmonisation

A coordinated procedure does not eliminate every national administrative difference. Requirements concerning national implementation, language, submission mechanics and other locally administered matters may still differ within the limits of the applicable EU framework.

This creates a useful distinction:

• scientific/product-information outcome: intended to remain coordinated;
• national implementation: executed by the relevant national competent authority and MAH organisation.

An organisation should not interpret this distinction as permission to create divergent safety positions without regulatory basis. Where the coordinated procedure has established common wording or conditions, local execution should preserve that agreed substance unless a lawful subsequent procedure changes it.

Practical Implementation for an MAH

A robust operating model begins with accurate procedure and product-family data. For each MRP/DCP family, the organisation should be able to identify the RMS, all CMSs, national authorisation numbers, current product information, active procedures and responsible internal functions.

A useful control record links:

regulatory procedure → affected products/countries → agreed outcome → national implementation → downstream PV and product-data updates.

The record need not take a particular regulatory form; this is recommended operational practice. Its value is traceability. When a safety change is later inspected or reconciled, the organisation can show how the common decision reached every affected national authorisation.

Special Situations

Addition or withdrawal of Member States

Product families can change over time. National authorisations may be withdrawn, transferred or otherwise change status. The current regulatory configuration should therefore be verified rather than assumed from the original DCP/MRP map.

Different national marketing status

A marketing authorisation can exist even where the product is not actively marketed. Commercial status and regulatory-authorisation status are distinct concepts. CMS responsibilities arise from the regulatory procedure and national authorisation, not simply from whether units are being sold.

Safety issues requiring a Union procedure

Some safety issues move beyond the ordinary RMS/CMS framework and become subject to a referral or other Union-level procedure. In that situation the legal basis of the Union procedure determines the assessment and decision pathway. The fact that a product was originally authorised through MRP/DCP does not mean every later safety issue is resolved solely between its RMS and CMSs.

Quality and Governance

CMS-related work is vulnerable to failures at interfaces rather than to misunderstanding the acronym itself. A company can understand that a CMS is a participating Member State and still fail to implement an agreed change across all affected authorisations.

Useful governance controls therefore focus on completeness and traceability:

• maintain a current RMS/CMS product-family map;
• identify which regulatory procedure created or changed the obligation;
• retain the agreed assessment outcome and product-information version;
• track national implementation to completion;
• reconcile regulatory, labelling and pharmacovigilance records after material safety changes;
• escalate unresolved country-level divergence to the appropriate regulatory function rather than resolving it informally.

These controls are recommended operational practice. Their exact design is organisation-specific.

Potential Failure Modes

The following are illustrative failure modes, not reported inspection findings.

Treating the CMS as passive

If internal teams assume the RMS is the only authority that matters, they may miss CMS comments, national implementation steps or country-specific procedural communications.

Confusing coordinated approval with a single Union authorisation

MRP/DCP results in coordinated national authorisations. Treating the outcome as though the European Commission had issued one central authorisation can lead to incorrect records and implementation assumptions.

Losing the product family after authorisation

Transfers, withdrawals and portfolio reorganisations can make the original RMS/CMS map stale. If the map is not maintained, subsequent safety actions may omit an affected authorisation.

Treating every CMS question as a potential serious risk to public health

This obscures the specific Article 29 threshold. Ordinary assessment comments should not be described using a legal escalation concept unless the threshold is actually engaged.

Failure to propagate a safety change

A scientifically correct safety variation may still fail operationally if agreed wording is not implemented in all applicable national product-information records and downstream systems.

Inspection Perspective

An inspector evaluating the MAH's handling of MRP/DCP products is more likely to be interested in evidence of control than in a theoretical definition of CMS. Illustrative questions include:

• Can the organisation identify the current RMS and CMSs for a selected product family?
• How does it determine which national authorisations are affected by a safety-related procedure?
• How are CMS or RMS regulatory outcomes translated into local product-information changes?
• How are discrepancies between the coordinated outcome and national records identified?
• Can the organisation trace a recent safety change from assessment through national implementation and PV-system update?

These are illustrative inspection questions, not statements of mandatory inspection practice.

Practical Example

Consider a DCP involving one RMS and four CMSs. During post-authorisation surveillance, evidence supports adding a new warning. The MAH completes the applicable variation procedure and common wording is agreed.

A weak process closes the task when the RMS procedure ends.

A stronger process recognises that the regulatory outcome still needs to be represented correctly across the affected national authorisations. It tracks implementation in the RMS and four CMS territories, verifies the resulting approved product information, updates internal safety and regulatory records, and reconciles any additional risk-minimisation or communication activities affected by the new warning.

The example illustrates the central principle: coordination creates a common outcome, but controlled national implementation completes the lifecycle change.

Key Takeaways

A Concerned Member State is a participating national competent authority in an MRP or DCP in which another Member State acts as RMS. The CMS reviews the coordinated assessment, can raise scientific and regulatory concerns, participates in agreement on product information and retains responsibility for the resulting national authorisation.

Article 29 provides a formal route when a Member State cannot approve the proposed outcome because of a potential serious risk to public health. That threshold is specific and should not be equated with routine scientific disagreement.

For pharmacovigilance, the practical importance of the CMS lies in the lifecycle interface: safety conclusions and regulatory changes must be implemented coherently across the relevant national product family.

References

1. European Parliament and Council. Directive 2001/83/EC on the Community code relating to medicinal products for human use, consolidated text, particularly Articles 28–29. EUR-Lex.
2. Heads of Medicines Agencies, CMDh. Decentralised Procedure (DCP) procedural guidance, including current Member States' SOP and DCP guidance.
3. Heads of Medicines Agencies, CMDh. Mutual Recognition Procedure and post-authorisation procedural guidance.
4. Heads of Medicines Agencies, CMDh. Variation Procedure guidance and Best Practice Guides, current versions.
5. European Medicines Agency. Coordination Group for Mutual Recognition and Decentralised Procedures – Human (CMDh).

Regulatory Note

This article distinguishes the legally binding framework in Directive 2001/83/EC from CMDh/HMA procedural guidance and from recommended internal operating controls. Exact procedural requirements and current templates should be checked against the legislation and the current HMA/CMDh guidance applicable to the product and procedure. The article is educational and does not replace regulatory or legal advice.