The direct answer: the CER establishes the clinical conclusion; PMS continuously collects postmarket information; PMCF proactively addresses clinical questions and evidence gaps; the PSUR periodically integrates the resulting safety and performance information; and the SSCP communicates the validated public-facing summary. A change in one document must therefore trigger an assessment of the others.

Alignment does not mean copying identical paragraphs from one document to another. Each document has a distinct regulatory purpose. Alignment means that shared facts, evidence, risks, conclusions, and commitments remain controlled across the technical documentation while each report explains them at the level appropriate to its audience and reporting period.

One connected evidence system

Each document produces inputs for the next decision.

The relationships are iterative rather than linear. PMS, PMCF, PSUR, and SSCP information moves into and out of the CER, while changed conclusions can also trigger updates to risk management and labeling. Each update requires an impact assessment across the connected evidence system.

DocumentPrimary roleCritical alignment output
CEREvaluates whether clinical evidence supports safety, performance, clinical benefit, and an acceptable benefit-risk profile.Evidence gaps, residual uncertainties, PMCF needs, and the current clinical conclusion.
PMSDefines and operates the system for collecting and evaluating postmarket information throughout the device lifecycle.Complaints, vigilance, trends, literature, user feedback, CAPA signals, and other postmarket findings.
PMCFProactively answers clinical questions that remain after market access and confirms continued safety and performance.New clinical data, resolved or persistent gaps, emerging risks, and implications for the clinical evaluation.
PSURPeriodically integrates exposure, complaints, vigilance, trends, CAPA, literature, and PMCF results.An updated evaluation of safety, performance, benefit-risk, and required actions for the reporting period.
SSCPCommunicates validated safety, performance, clinical evidence, alternatives, and residual risks to its intended public audience.A controlled public summary that must remain consistent with the current technical documentation.

Where alignment fails

Contradictions often begin with ordinary updates.

01

A new risk appears only in the PSUR

A reporting-period signal is discussed in the PSUR, but the CER still states that no new clinical risks were identified and the SSCP retains an outdated residual-risk description.

02

PMCF does not answer the CER’s evidence gap

The CER identifies uncertainty in long-term performance, while the PMCF plan collects short-term satisfaction data without endpoints or follow-up capable of resolving that uncertainty.

03

Claims drift across controlled documents

The intended purpose, target population, device variants, clinical benefit, or state-of-the-art comparator changes in one document without being reconciled across the remaining evidence system.

04

Data cut-off dates create competing conclusions

Complaint, vigilance, literature, and PMCF datasets cover different periods, but the documents do not explain the difference. Reviewers cannot determine which conclusion reflects the current evidence.

A practical control method

Manage shared evidence as controlled data, not repeated prose.

Before drafting or updating a document, establish a cross-document alignment matrix. The matrix should identify the authoritative source, current approved statement, affected documents, reporting cut-off date, owner, and action required for every shared element.

  1. 01

    Device identity and scope

    Device name, Basic UDI-DI, models, variants, accessories, risk class, and applicable configurations.

  2. 02

    Intended purpose and claims

    Indications, contraindications, target populations, intended users, clinical benefits, and performance claims.

  3. 03

    Evidence base

    Device-specific data, equivalent or similar device data, literature cut-off dates, state of the art, and evidence limitations.

  4. 04

    Safety and risk

    Known and emerging risks, undesirable side effects, complaint and vigilance patterns, residual risks, and benefit-risk conclusions.

  5. 05

    Postmarket commitments

    PMS objectives, PMCF questions, methods, timelines, acceptance criteria, report dates, and follow-up actions.

  6. 06

    Controlled conclusions

    Whether safety and performance remain supported, what changed, why it changed, and which documents require revision.

At the end of every CER, PMS, PMCF, or PSUR cycle, conduct an impact assessment rather than assuming that approval of one report closes the activity. The assessment should record which conclusions changed, which remained unchanged, and which linked documents require an immediate or scheduled update.

Cross-document consistency is not a final proofreading step. It is a lifecycle control that begins when the evidence question, data sources, document owners, and update cadence are defined.

What notified body readiness looks like

A reviewer should be able to follow the same evidence story across every document.

A coherent file makes it possible to trace a clinical uncertainty from the CER to a proportionate PMCF objective, from the PMCF result to the PSUR evaluation, and from the updated conclusion to the risk documentation and SSCP. The terminology may be adapted for each audience, but the underlying facts and regulatory rationale should not change.

For manufacturers managing multiple products or recurring update cycles, the most reliable approach is to coordinate the documents as a program. Shared evidence tables, controlled definitions, synchronized cut-off dates, and documented impact assessments reduce rework and make reviewer questions easier to answer.

Primary regulatory references

Sources for the alignment framework.

This article provides general information and does not replace device-specific regulatory assessment or legal advice.