PMS framework and data map
Objectives, responsibilities, data sources, frequencies, quality checks, installed-base denominators and interfaces with risk, clinical, security and CAPA systems.
Post-Market Surveillance
We help SaMD manufacturers design and document proportionate complaint, signal, vigilance, trend and lifecycle-review processes. The scope is advisory and documentation-focused unless operational responsibilities are expressly agreed.
Selected clients
Healthcare teams we have supported


















Scope and deliverables
Manufacturers retain legal reporting and decision responsibility. We can support assessment frameworks and records, but do not imply 24/7 surveillance, authorized-representative status or submission of reports unless specifically contracted and legally appropriate.
Objectives, responsibilities, data sources, frequencies, quality checks, installed-base denominators and interfaces with risk, clinical, security and CAPA systems.
Intake fields, duplicate handling, severity and causality prompts, investigation logic, reportability escalation and controlled decision records.
Expected-event baselines, thresholds, stratification, data limitations, review cadence and escalation criteria proportionate to available volume.
Decision aids and documentation inputs for FDA MDR, EU vigilance and trend reporting, field actions and applicable Indian materiovigilance obligations.
EU PMS report or PSUR structures, benefit-risk updates, sales and population estimates, CAPA summaries and PMCF interfaces where applicable.
Link signals to risk files, cybersecurity monitoring, clinical evaluation, anomaly assessment, CAPA and regulatory change evaluation.
Ways to work together
Create or remediate the process architecture, procedures, templates, roles and evidence flow.
Structure and draft manufacturer-reviewed PMS, PSUR or lifecycle summaries from supplied and validated source data.
Help organize facts, risk and reportability analysis for a defined issue; legal deadlines and submissions remain clearly assigned.
How it works
Identify products, markets, classes, reporting rules, roles and available data.
Define intake, triage, signal, investigation, reporting and escalation workflows.
Create records, train assigned owners and test handoffs using realistic scenarios.
Assess outputs, reconcile trends and update risk, clinical, CAPA and product controls.
Regulations, standards and guidance considered
Frequently asked questions
PMS is the systematic lifecycle process for collecting and evaluating experience from marketed devices. Vigilance is the subset of regulatory reporting and action for specified serious incidents, field safety corrective actions and related events. Exact terms and thresholds vary by jurisdiction.
No. Class I manufacturers prepare a PMS report and update it when necessary. Class IIa, IIb and III manufacturers prepare a PSUR, with update and availability or submission obligations that differ by class and device situation.
Not yet by default. The vigilance/PMS module has its own functionality notice and transition date. Until mandatory use applies, manufacturers follow the relevant national reporting processes and current Commission guidance.
Automation can flag records and support consistency, but reportability depends on facts, definitions, causality, outcomes and jurisdiction-specific rules. Qualified review and documented decisions remain necessary.
Not unless a specific lawful operational scope, coverage model and responsibilities are agreed. Our standard capability is system design, assessment support and documentation; the manufacturer retains deadline tracking, authority accounts and legal accountability.
No. PMS improves detection and response but cannot eliminate product risk or guarantee that field action will never be needed. Conservative escalation and timely corrective action are part of an effective system.
Start with the product you have