CCDS change management that finds every local label a change touches, and puts each market on its clock from day one
Every core data sheet change finds each local label it touches and puts every market on a clock from day one.
See one case, screen by screen ↓The labeling committee approves a new Company Core Data Sheet, and the clock starts: a safety-critical change has to be submitted in every market within the company’s 30 days. First someone has to work out what actually changed between the two versions, which of those changes are safety-critical, and where each one lands in 26 local labels across 16 markets — the USPI, the SmPC and package leaflet, the bula, the IPP, the JPI, the Product Monograph — each with its own section numbers and template.
Then the local text has to be written in each language without losing what is already approved: the wording a health authority asked for, the format a template requires, the sentence the translation memory already holds. An affiliate shortens a sentence to fit a leaflet and a monitoring instruction quietly disappears. By the time the impact assessment is done, a third of the clock can be gone, and nobody has a single view of which market is late.
Estimated split for one safety-critical CCDS change across 16 markets, by hand and with the solution.
Six agents compare, classify, map, draft, schedule and check every change; the labeling lead decides each local deviation.
Veltrimab CCDS 15.0 adds a warning for drug-induced liver injury after signal SIG-2026-031. It has to reach 16 markets by Nov 1. Here is day 5 of its clock, screen by screen, in the working solution.
Maya opens the cascade map: Veltrimab 15.0, safety-critical, day 5 of 30 to submit in 16 markets. 15 of 16 markets are on track, the deadline is 25 days away, and five things wait for her — a deviation to decide in Brazil, a diverging edit in Mexico, Talmirex CCDS 23.0 approved this morning, and Turkey and South Africa late on Corventa 9.0.
“Meaning Checker · Re-checked 9 affiliate edits since yesterday — 8 keep the CCDS meaning, 1 does not (Mexico).”
The comparer aligned 14.2 and 15.0 section by section and found five changes, layout edits ignored. §4.4 gets a new warning for drug-induced liver injury, with liver enzymes and bilirubin measured before treatment and periodically thereafter — safety-critical. §4.8 adds liver injury as uncommon and moves urticaria to common; §4.6 adds pregnancy registry data; §4.2 and §5.2 are editorial. Omar Haddad, the safety physician, confirmed the safety-critical class.
Why it changed: 27 cases of drug-induced liver injury, 3 with acute liver failure; PRAC asked for §4.4 and §4.8 to change within 60 days.
The impact matrix shows each change against each market: Update where the text must change, Aligned where the local label already says it, Deviation where a registered local wording covers the passage, Diverging where an edit changes the meaning. Across 16 markets and 26 local labels: 68 sections to update, 5 already aligned, 5 deviations or edits to check.
The mapper never marks a passage aligned without a cited local sentence, and registered deviations always go to a person.
Sixteen country tasks open with the procedure from the registration data and an owner in each market: a CBE-0 supplement for the US, already submitted on Oct 6; an SNDS-C for Canada; a Type II variation for the EU, due Nov 25; a notificação de alteração de texto de bula for Brazil. Turkish, Japanese, Chinese and Korean are with the translation vendor, back Oct 9 to 14.
The Brazil draft of the bula profissional, section 5 Advertências e precauções, is built sentence by sentence: approved translations used as they are, a 94 % close match adjusted, and the patient wording for the bula paciente. Brazil has a registered deviation, DEV-BR-004: ANVISA asked in 2024 for liver tests before treatment and every 3 months. The drafter kept that sentence and asks Maya.
“Keep the ANVISA wording — liver tests before treatment and every 3 months — stricter than the CCDS, so the core safety information is still met.”
Maya keeps the deviation, and the register re-confirms it. She approves the Brazil draft — bula profissional and bula paciente — with her password; the signature, its meaning (“Approved by the global labeling lead”) and the time are stored with the record. Rafael Souza, the affiliate regulatory manager in Brazil, has it for affiliate review.
In Mexico, Ana Torres shortened the IPP draft “for space in the IPP reducida” and removed “y periódicamente después”. The Meaning Checker back-translated the edit and flagged it: patients would be tested only once before treatment — weaker than CCDS 15.0 — and no registered deviation covers it.
Three choices: send back with the CCDS sentence, escalate to the Americas head, or accept with a justification and Safety sign-off.
Maya sends the edit back to Ana Torres. The CCDS sentence is restored in the draft, the Meaning Checker re-checks the next edit, and the decision is on the activity record of the change.
Talmirex CCDS 23.0 was approved by the labeling committee this morning after signal SIG-2026-038: a new warning for Stevens-Johnson syndrome and toxic epidermal necrolysis. Maya uploads it and the six agents run: 3 changes, 26 local labels, 44 sections to update, 1 already aligned and 2 deviations to check — Brazil’s ANVISA patient-alert sentence among them. 16 country tasks open, submit by Nov 6.
Over 12 months: 1,184 local label revisions across 30 products and 16 markets, a median of 31 days from CCDS approval to local submission against a 30-day target, and 89 % submitted on time. Where the days go now: impact assessment 2.6 days, translation 9.4, health-authority review 21.
“Impact assessment and drafting take hours, not weeks, once the agents do them; translation and health-authority review remain the long steps.”
The same CCDS change, seen by the five people who move it from the core data sheet to each market — what their week looked like, and what it looks like now.
Six agents compare, classify, map, draft, schedule and check every change; the labeling lead decides each local deviation.
Aligns two CCDS versions section by section and lists every change as a labeling concept with old and new text.
Classifies each change as safety-critical, safety or editorial, gives the reason with the signal, PSUR or committee minutes, and sets the clock that follows from it.
Uses the registration data and the CCDS-to-local section map to find every local label and section a change lands in, and compares meaning, not words, with what the local text already says.
Drafts the local wording sentence by sentence in each market’s language and template — approved translation memory first, then the local template wording, then new translation marked for a linguist.
Opens a country task per market with the procedure, the submission date and the affiliate owner; every morning compares progress with the clock and escalates late markets to the regional head.
Back-translates each affiliate edit, compares its meaning with the CCDS and checks the deviation register before flagging divergence.
Decides each deviation. The agents propose; a named person decides.
The assistant answers from the CCDS versions, every local label, the deviation register and the country tasks — and can escalate a market or add a rule.
Which markets are at risk on the Veltrimab safety deadline?
All 16 markets must submit by Nov 1 (EU Type II by Nov 25). Mexico: the edit dropped the monitoring sentence — send back or escalate. Brazil: waits for your deviation decision. Turkey is with the vendor, back Oct 9; Japan, Korea and China back Oct 13–14. None is late yet.
What changed between CCDS 14.2 and 15.0?
Five changes: a new §4.4 warning for drug-induced liver injury, with liver tests before and during treatment (safety-critical); §4.8 liver injury added as uncommon and urticaria now common; §4.6 a pregnancy registry of 318 pregnancies with no increase in major birth defects; and editorial changes to §4.2 (infusion over at least 30 minutes) and §5.2 (half-life 19 days).
Why is Brazil keeping “every 3 months”?
Because ANVISA asked for it in 2024 (deviation DEV-BR-004). CCDS 15.0 says “periodically”; the stricter local wording still meets the core safety information, so the drafter kept it and asked you.
Add a rule: never overwrite a health-authority deviation
Done. Every deviation in the “Health-authority mandated” category is now locked — like Brazil’s every-3-months liver tests and Turkey’s pregnancy category. Only a new health-authority letter can retire one. The rule is on in Settings and recorded in the audit trail.
13 screens from the working solution, on its sample data. Pick one to see it large.
The clocks, the translation threshold, the approvers and the escalations are settings, not a project.
| Setting | Default | Choose from |
|---|---|---|
| Safety-critical changes — submit within | 30 days | 15 · 30 · 45 days |
| Safety-critical changes — implement within | 90 days | 60 · 90 · 120 days |
| Other safety changes — submit within | 90 days | 60 · 90 · 180 days |
| Use translation memory at or above | 85 % | 75 · 85 · 95 % |
| Keep registered deviations and ask me | On | On · Off |
| Global drafts and deviations decided by | Dr. Maya Chen | Dr. Maya Chen · Lena Ortiz · Dana Okafor |
| Safety-critical wording signed off by | Omar Haddad | Omar Haddad · Dr. Maya Chen |
| Escalate a late market after | 3 days | 1 · 3 · 5 days |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample labeling data · “target” = the design goal, measured in the live solution · “estimated” = our estimate of where the days go, before deployment · “typical” = published labeling benchmarks (30 products × 15 markets × 4 updates ≈ 1,800 revisions a year; change and impact assessment by hand takes days 1–10) and typical company clocks (safety-critical changes submitted within 30 days). People and products named on this page are fictional, from the working solution.
When the Company Core Data Sheet changes, every local label that follows it — USPI, SmPC, bula, IPP, JPI and the rest — has to be assessed, updated, translated, reviewed by the affiliate, submitted and implemented. The CCDS Change Cascade Manager runs that cascade: it finds every label and section a change touches, drafts the local text and tracks each market to approval and implementation.
The Label Impact Mapper uses the registration data and a map from CCDS sections to each local template to find the documents and sections affected. It compares meaning, not words, and marks each passage Update, Already aligned, Not in this label or Deviation — never aligned without a cited local sentence.
No. The drafter never overwrites a registered deviation. It keeps the local wording, shows the CCDS text and the health-authority letter or register entry beside it, and the global labeling lead decides whether to keep it or align to the CCDS.
It reuses approved translations first — exact matches as they are, close matches adjusted and marked — then local template wording, then new translation marked for a linguist. Languages below your threshold (85 % in the working solution) go to the translation vendor automatically.
Yes. The Meaning Checker back-translates every affiliate edit and compares it with the CCDS. Removed or weakened safety information is always flagged, and you can send it back, escalate it to the regional head or accept it with a justification and Safety sign-off.
Yes. The submission and implementation clocks for safety-critical and other safety changes, whether editorial changes wait for the next update, who approves, and when a late market is escalated are all settings.
Yes. The agents propose; people decide. Safety (PV) confirms every safety-critical classification, the global labeling lead decides every deviation and signs each draft before it goes to the affiliate, and each affiliate regulatory manager approves the local text.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your CCDS versions, local labels, translation memory, registration data and deviation register — and it goes live once every quality gate has passed. We will walk you through it on one of your own past CCDS changes first.
Every agency change reaches the right team within hours, translated and cited.
1-min filmSubmission SummariesModule 2 summaries drafted in weeks, every statement cited to its source page.
1-min filmAgency ResponsesEvery agency question gets a cited first draft within hours, consistent with every past answer.
1-min filmWe’ll run the CCDS Change Cascade Manager on one of your own past CCDS versions and its local labels.