Company Core Data Sheet: The Label Every Other Label Comes From

A CCDS is the document a marketing authorization holder maintains internally stating its own position on a product: the core safety information, indications, dosing, contraindications, warnings and pharmacology.

No regulator approves it and it is not normally submitted. Its purpose is to give every local label the company files one agreed source to derive from.

Label drift across markets

A product approved in thirty countries has thirty labels. The EU has an SmPC, the United States has prescribing information, and every other market has its own format and its own review.

Without a master, those thirty labels drift. A warning added in one market because a national authority asked for it does not reach the other twenty-nine. Two years later the same product carries materially different safety information depending on where you buy it, and nobody planned that.

The CCDS is the control against drift. Local labels are permitted to differ, but each difference should be deliberate and justified, usually by a local regulatory requirement, rather than accidental.

Contents

• Indications the company considers supported.
• Dosing and administration.
• Contraindications, warnings and precautions.
• Adverse reactions, the core safety profile.
• Pharmacology and other non-safety content.

The safety sections carry most of the regulatory weight, which is why the document is usually owned jointly by global labeling and pharmacovigilance.

The change cycle

1. A trigger arrives. A signal from pharmacovigilance, a regulator's request, a study result, a class effect.
2. The CCDS is revised and approved internally, with an effective date.
3. Local impact is assessed: which markets need a variation, at what reporting category, on what timeline.
4. Local labels are updated, each through its own national procedure.
5. Implementation is tracked until every market has landed.

Step 5 is where it goes wrong. A CCDS updated centrally with no tracking of which markets have implemented gives you a document that is correct and a portfolio that is not. Regulators ask about implementation status, and "the CCDS was updated" is not an answer to it.

Divergence and implementation status

Where does each local label differ from the CCDS, and why? Every divergence should map to a local requirement or an approved local variation.

Which markets are behind on the current CCDS version? Including the ones where the variation was submitted and is still under review.

Both are slow to answer in practice, because the answer is spread across thirty documents in as many formats and languages.