Can a registry be used for neuromodulation PMCF?
It can, where the registry is designed against the specific post-market question and the methodology and regulatory rationale are set out for the device and indication concerned. It is not automatic. A registry may be well suited to questions such as durability, device survival, revision burden, therapy persistence and other long-term outcomes across a defined population. Where the evidence question requires scheduled assessments, trained clinical ratings or imaging that routine-care data do not capture reliably, a routine registry may not be sufficient unless it is specifically designed to collect those assessments prospectively.
How long should a neurostimulation registry follow patients?
The follow-up horizon should be justified against the clinical question, device characteristics, intended use, expected timing of relevant safety and performance events, residual risks and the evidence gap the program is intended to address. For implanted systems, expected device service life may be an important input, particularly when battery longevity, revision, replacement or late device events form part of the evidence question. Retention assumptions and the statistical consequences of attrition should be addressed prospectively.
What should an SCS PMCF program collect?
Depending on the evidence gap: responder status at defined timepoints with the definition justified for the indication, pain and function instruments, therapy continuation and discontinuation, analgesic use as a confounder, lead migration and fracture, revision and explant with the reason recorded, and device deficiencies. Programming history should be structured rather than free text.
What should a DBS PMCF program capture?
Depending on the indication, device and clinical claims: longitudinal clinical rating scales with medication state and assessment timing recorded, programming changes, device-related events, revision and replacement, and battery, recharge or replacement considerations where relevant to the system. Where lead position is part of the question, an imaging review pathway has to be agreed before enrollment rather than reconstructed later.
How should revisions and explants be recorded in a neurostimulation registry?
Against an event taxonomy defined before the first patient is enrolled, so terminology remains consistent across the clinical database, complaint-handling, vigilance and quality-system workflows. Each event needs its date, its reason and its relationship to the device where applicable.
How do you reduce loss to follow-up in long-term implant registries?
By designing for it: realistic retention assumptions, a contact model that does not depend on one coordinator remaining in post, follow-up windows wide enough that a late visit stays analyzable, and completeness monitored as a live metric. Attrition cannot be eliminated over years, so it is measured and accounted for in the analysis.
Can Eclevar support a multicountry neuromodulation registry in Europe?
Yes. Eclevar supports multicountry European neuromodulation programs through central program governance, regional clinical operations and qualified local coverage where appropriate. Data management, biometrics and medical writing are coordinated centrally across the program, and Eclevar leads and coordinates regulatory and ethics start-up according to the country, the authority and the applicable submission pathway. Country-specific coverage is discussed during feasibility.
Can registry data feed the PMCF evaluation report and the clinical evaluation?
Yes, where the registry has been designed against the relevant PMCF and clinical-evaluation questions. The required variables, definitions, follow-up structure, data-quality controls and analytical plan should be established prospectively, so that the resulting dataset can support the PMCF evaluation and the broader clinical evidence strategy where appropriate.
How does post-market clinical data connect to ISO 13485 and CAPA?
Device deficiencies, revision patterns and explant reasons observed in a post-market program are read alongside complaint handling, vigilance and the risk management file. Where the manufacturer's quality system requires it, a signal identified in the data may trigger corrective and preventive action. Designing the event taxonomy so it maps onto the quality system's terminology avoids the same event existing twice, described two different ways.