Medical devices, IVDs, cosmetics and compliance technology.Explore SMEDTEC OS
← Back to Insights
Eu Mdr ComplianceQuality Management SystemsPost Market Surveillance

Post-Market Systems Under Pressure: EDC, eQMS and Scale

Sherif Elkhadem
20 November 2026
7 min read
Server rack with green status lights in a data centre, representing clinical data infrastructure supporting post-market surveillance and quality systems.

Three articles published by Greenlight Guru in quick succession focus on electronic data capture systems, 21 CFR Part 11 compliance, and eQMS selection for post-market teams. Read together, they reveal a structural truth: the regulatory infrastructure that gets a device to market is rarely the infrastructure that can sustain it there. For manufacturers navigating EU MDR's continuous PMCF obligations or FDA's expanding quality system inspection scope, the technical architecture supporting post-market surveillance, clinical follow-up and complaint handling is now the bottleneck.

This matters because under EU MDR Annex XIV Part B, post-market clinical follow-up is not a fixed-duration study. It runs for the entire commercial life of the device, with data feeding back into clinical evaluation updates on a regular cycle. That changes the selection criteria for every system in the data chain. An EDC platform chosen for a twelve-month trial may buckle under a decade of continuous collection. An eQMS that handled clearance documentation may collapse when complaint volumes scale across markets. And the assumption that software compliance is the vendor's problem rather than the manufacturer's has already ended several inspections badly.

PMCF Demands Infrastructure Built for Years, Not Months

Greenlight Guru's breakdown of EDC systems for PMCF under EU MDR starts with a premise most trial sponsors overlook: the system will be in production use for years. That shifts the evaluation from feature lists to operational endurance. Can the platform handle protocol amendments without orphaning historical data? Does the vendor's support model assume a single study with a fixed end date, or continuous operation with rolling updates? Will the audit trail survive a regulatory inspection five years after the device launched, when the original validation team has moved on?

The article identifies five EDC platforms and evaluates them against PMCF-specific criteria: integration with clinical evaluation reporting, support for long-term data retention, traceability across protocol versions, and regulatory audit readiness. The common failure mode is not technical capability at launch, but operational brittleness under sustained use. A system that works well for a 200-subject pivotal trial may require manual workarounds when managing 2,000 subjects across three protocol amendments and six sites over eight years. Those workarounds become compliance gaps the moment an inspector asks to see the validation records.

For manufacturers building regulatory operations infrastructure, the lesson is blunt: PMCF systems are post-market infrastructure, not clinical trial tools repurposed. Selection criteria must account for lifecycle cost, vendor stability, and integration with post-market surveillance workflows, not just features and pricing at the point of purchase. The cheapest system that meets today's requirements is expensive if it fails during an inspection in year four.

21 CFR Part 11 Compliance Sits with the Manufacturer, Not the Software

The second article tackles a persistent misconception: that 21 CFR Part 11 compliance is a property of the software rather than the organisation using it. When an EDC vendor claims their platform is Part 11 compliant, they mean the system provides features that can support compliance, such as audit trails, electronic signatures, and access controls. They do not mean the manufacturer is automatically compliant by virtue of purchasing a licence.

FDA's guidance on electronic systems, records and signatures in clinical investigations makes this explicit. The sponsor or investigator is responsible for ensuring that electronic records meet Part 11 requirements, which include validation of the system, documented procedures for its use, and controls that prevent unauthorised access or data alteration. The software enables those controls, but the manufacturer must implement, document and maintain them. During an inspection, FDA will ask to see validation protocols, training records, and evidence that procedures are followed. A vendor brochure is not evidence.

Table
21 CFR Part 11 Compliance: Vendor Capability vs. Manufacturer Responsibility
AspectVendor ProvidesManufacturer Must Demonstrate
Audit TrailSystem logs all data changes, timestamps and user IDsValidation that logs are tamper-proof, procedures for review, evidence of periodic audit
Electronic SignaturesMechanism for authenticated user signature eventsValidation linking signature to identity, training records, signature manifestation on output
Access ControlRole-based permissions and password policiesDefined roles, documented access reviews, records of user provisioning and deactivation
Data IntegrityDatabase constraints and backup routinesValidation of data flow, disaster recovery testing, documented retention and disposal procedures
System ValidationInstallation qualification documentationFull IQ/OQ/PQ, risk assessment, change control, revalidation after updates
Part 11 compliance is a shared responsibility. Vendors supply technical controls; manufacturers validate, document and sustain them under inspection.

This distinction matters because inspection findings increasingly target system validation and procedural gaps rather than software defects. A manufacturer using a well-known EDC platform can still receive a 483 observation if validation documentation is incomplete, if users bypass electronic signatures with manual workarounds, or if audit logs are not reviewed. The system's technical capability is irrelevant if the quality management system does not control how it is used. For teams running AI as a Service implementations built around regulated processes, the principle extends further: validation and ongoing oversight remain the manufacturer's burden, regardless of the sophistication of the tool.

Scaling Post-Market Operations Breaks Clearance-Era Systems

The third article addresses eQMS replacement, specifically the scenario where a manufacturer already has a quality system in production but needs to migrate to a platform that can support scaled post-market operations. The challenge is not feature comparison. It is executing the migration without breaking traceability, losing complaint data, or introducing gaps that become inspection findings.

Greenlight Guru outlines seven criteria for evaluating an eQMS when replacing an existing one: data migration integrity, support for live complaints and CAPAs during transition, integration with post-market surveillance workflows, traceability across the old and new systems, audit readiness throughout the migration, multi-market regulatory support, and vendor longevity. The hardest part is not choosing the new platform, but proving to an inspector that nothing was lost or altered during the move.

The article's framing assumes the reader is already past the startup phase. The device is on market, complaints are arriving, post-market surveillance data is accumulating, and the original eQMS is showing cracks under load. This is the reality for manufacturers who cleared a device with a lean team and minimal tooling, then discovered that EU MDR's post-market clinical follow-up obligations, FDA's QMSR inspection scope, and MHRA's vigilance reporting timelines demand infrastructure the initial system cannot provide. Replacing an eQMS under those conditions is a live-system migration with regulatory and operational risk on both sides.

Process

eQMS Replacement Decision Sequence for Post-Market Teams

  1. Trigger Assessment
    Document the operational or compliance gap: complaint backlog, traceability breaks, inspection findings, or inability to support new markets or regulatory obligations.
  2. Data Inventory
    Map all records in the current system: complaints, CAPAs, design history, post-market surveillance, vigilance reports, audit trails. Identify dependencies and cross-references.
  3. Migration Risk Analysis
    Assess data loss risk, traceability breaks, downtime impact, procedural gaps during transition, and inspection timing. Document mitigations for each.
  4. Platform Evaluation
    Evaluate candidate eQMS platforms against post-market criteria: migration tooling, live complaint handling, multi-market support, audit trail continuity, vendor stability.
  5. Parallel Operation Plan
    Design a phased migration with the old system remaining operational until the new one is validated and all historical records are traceable. Define cutover criteria.
  6. Validation and Cutover
    Execute IQ/OQ/PQ on the new system, migrate data in controlled batches, validate traceability, train users, then decommission the old system with documented retention of archived records.
eQMS replacement is a regulated activity. Each step must be documented, risk-managed and auditable.

What This Means for Your Team

These three articles converge on a single operational reality: post-market infrastructure is now the regulatory chokepoint for devices under EU MDR and FDA QMSR. The systems that capture clinical data, manage complaints, track CAPAs, and feed post-market surveillance are no longer back-office tools. They are part of the technical documentation under MDR Annex II, subject to inspection under FDA's QMSR, and central to the vigilance and clinical evaluation obligations that run for the life of the device. Choosing them badly, validating them incompletely, or replacing them carelessly creates compliance risk that compounds over time.

For regulatory and quality teams, the immediate task is to audit the systems already in use. Can the current EDC platform sustain PMCF for another five years? Is the eQMS validated to 21 CFR Part 11 standards, with documented procedures and audit trail reviews? If a complaint volume spike or a regulatory inspection happened next month, would the system hold up under scrutiny? If the answer to any of these questions is uncertain, the gap needs documenting and the mitigation plan needs funding.

For manufacturers planning to scale into new markets or extend product lines, the question is not whether to invest in post-market infrastructure, but when and how. Delaying the decision until an inspection finding forces it is expensive. Building it in parallel with product development, as part of the regulatory strategy from the start, is cheaper and faster. The systems that support post-market obligations are not optional extras. They are foundational regulatory architecture, and treating them as anything less is a risk no inspection-ready manufacturer can afford.

Key Takeaways

  • PMCF under EU MDR runs for the life of the device, so EDC systems must be evaluated for operational endurance over years, not months. Vendor stability, long-term support and integration with clinical evaluation workflows matter as much as feature lists.
  • 21 CFR Part 11 compliance is the manufacturer's responsibility, not the software vendor's. Audit trails, electronic signatures and access controls must be validated, documented and maintained under procedural control. A compliant system does not make a compliant organisation.
  • Replacing an eQMS while a device is on market is a live-system migration with traceability and audit risk. Data integrity, complaint continuity and inspection readiness must be maintained throughout the transition, with full validation before cutover.
  • Post-market infrastructure is now the regulatory bottleneck. The systems supporting PMCF, complaint handling, vigilance reporting and post-market surveillance are part of the technical documentation and subject to inspection. Choosing them badly creates compliance debt that scales with time.

Post-market obligations are no longer a trailing concern once clearance is secured. Under current regulatory expectations, they are the longest and most scrutinised phase of a device's lifecycle. The infrastructure supporting them must be built to last, validated to withstand inspection, and operated under continuous procedural control. For manufacturers still treating EDC, eQMS and Part 11 compliance as procurement decisions rather than regulatory architecture, these three articles offer a corrective. The systems that capture and manage post-market data are not tools. They are the foundation on which every clinical evaluation update, vigilance report and inspection response will stand.

Frequently asked questions

What makes an EDC system suitable for PMCF under EU MDR?

A PMCF-ready EDC system must support continuous data collection for the entire life of the device on market, integrate with clinical evaluation reporting cycles, maintain audit trails meeting 21 CFR Part 11 standards, and handle protocol amendments without breaking traceability. The system will be used for years, not months, so vendor stability and long-term support matter as much as features at launch.

Who is responsible for 21 CFR Part 11 compliance in an EDC system?

The organisation using the system is responsible for Part 11 compliance, not the software vendor. While vendors can provide features that enable compliance, such as audit trails, electronic signatures and access controls, the manufacturer must validate the system, write procedures for its use, and demonstrate during inspection that those procedures are followed. Software alone does not satisfy the regulation.

When should a medical device manufacturer replace its eQMS?

Consider replacing an eQMS when the platform cannot support scaled post-market operations without breaking traceability, when complaint volumes outpace the system's workflow capacity, when regulatory changes require documentation structures the current system cannot model, or when third-party integrations multiply to the point where data integrity risk exceeds operational benefit. The replacement happens while the existing system remains live and subject to inspection.

What are the core requirements for an eQMS supporting a device already on market?

An eQMS for post-market use must maintain full traceability during migration from the previous system, handle live complaints and CAPAs without workflow interruption, support multiple regulatory regimes if the device is sold across borders, integrate with post-market surveillance and vigilance reporting, and provide audit trails that satisfy both FDA QMSR and EU MDR Annex II technical documentation requirements. Uptime and vendor longevity are as critical as feature completeness.

Sources cited in this digest

Related Articles

Quality Management

FDA safety alerts and Microsoft outage test continuity

FDA posts early alerts for two device removals as MHRA navigates a Microsoft outage. For manufacturers, these events reveal where safety architecture meets operational resilience.

16 November 2026
Fda Medical Device Approvals

Tandem's Mobi Recall and Abbott's Lead Approval Signal New Risk Thresholds

Tandem's insulin pump recall hits 230 adverse events as Abbott wins dual approval for cardiac pacing. For device manufacturers, these parallel moves reveal where post-market surveillance expectations and approval pathways are diverging.

13 November 2026
Quality Management

MHRA Patient Engagement, Philips Settlement and 1nhaler Funding

MHRA formalises patient involvement architecture as Philips pays €288m to settle CPAP recall claims. For device manufacturers, these moves clarify where post-market accountability now sits.

6 November 2026

Need Regulatory Guidance?

Get expert help with your medical device regulatory strategy. From EU MDR compliance to FDA submissions, we're here to help.

Get Started →More Articles