What Does a Class II Medical Device Manufacturer Need From an eQMS?
Key takeaways:
- Class II devices require 510(k) premarket notification and are subject to the full scope of FDA 21 CFR Part 820 QMSR requirements, making a validated, purpose-built eQMS essential from the design phase onward.
- ISO 13485:2016 is the international quality system standard required by most Class II manufacturers seeking global market access or working with contract manufacturers and distribution partners.
- Post-market surveillance, complaint handling, and CAPA are particularly critical for Class II manufacturers because adverse event reporting obligations begin at the point of clearance.
- Design controls are mandatory for Class II devices under FDA 21 CFR Part 820 and must be implemented in a system that supports traceability from user needs through verification and validation.
- Grand Avenue Software supports the full Class II compliance lifecycle in a single, cloud-based, modular platform with transparent pricing starting at $3,000.
What Is a Class II Medical Device and What Does That Mean for Quality Compliance?
Class II medical devices are those that present moderate risk and require more regulatory controls than Class I devices, but do not need the full premarket approval process required for Class III devices. The FDA clears most Class II devices through the 510(k) premarket notification process, which requires demonstrating substantial equivalence to a legally marketed predicate device.
The compliance obligations for a Class II manufacturer are more extensive than many early-stage companies anticipate. Receiving 510(k) clearance is not the end of regulatory oversight. It is the beginning of a permanent post-market compliance relationship with the FDA.
| Compliance Obligation | What It Requires | When It Applies |
| FDA 510(k) clearance | Demonstration of substantial equivalence to a cleared predicate device, supported by design and testing documentation | Before commercial distribution in the US |
| FDA 21 CFR Part 820 QMSR | Full quality management system covering design, production, distribution, and post-market activities | From the beginning of design and development through the full product lifecycle |
| ISO 13485:2016 | International quality management system standard required for most global market access pathways and contract manufacturer relationships | Required for EU CE mark, many distributor agreements, and contract manufacturer quality agreements |
| FDA 21 CFR Part 11 | Electronic records and signatures in regulated activities must meet authentication, audit trail, and record integrity requirements | Any time electronic approvals, signatures, or records are used in regulated activities |
| MDR / Post-market surveillance | Mandatory adverse event reporting for device malfunctions, serious injuries, and deaths, plus ongoing post-market surveillance activities | Immediately after commercial distribution begins, ongoing |
| EU MDR 2017/745 | European Medical Device Regulation requirements for CE mark, including post-market clinical follow-up and periodic safety update reports | For any Class II equivalent device entering EU markets |
Why Do Class II Manufacturers Need Design Controls in Their eQMS?
Design controls are mandatory for Class II medical devices under FDA 21 CFR Part 820 QMSR. They require manufacturers to establish and maintain procedures for controlling the design of the device to ensure that specified design requirements are met. This is not a documentation exercise. It is a structured process that links user needs to design inputs, design outputs, verification activities, validation activities, and design transfer.
The design control process has direct implications for the 510(k) submission. FDA reviewers expect to see evidence of a structured design process, and the design history file produced by that process becomes the primary technical documentation supporting the submission. A design history file assembled retroactively or maintained in a fragmented system is significantly more difficult to defend in a 510(k) review or FDA inspection than one produced through a controlled, traceable design control process.
An eQMS design control module must support four specific capabilities to satisfy Class II requirements:
- Traceability from user needs through design outputs. Every design requirement must be traceable to verification evidence and ultimately to user needs. An eQMS that manages these relationships in a single system eliminates the traceability gaps that commonly arise when design documentation is spread across separate tools.
- Design review documentation. FDA 21 CFR Part 820 requires formal design reviews at major development phases, with participation of representatives of functions concerned with the design stage being reviewed. These reviews must be documented with controlled records.
- Design change control. Any change to the device design after initial design freeze must go through a controlled change process that evaluates the impact on the original design requirements, verification activities, and regulatory status.
- Design history file maintenance. The design history file must be maintained as a controlled, retrievable record for the life of the device. An eQMS that manages the DHF within the same system as document control ensures version history, approval records, and change documentation are always current and accessible.
Grand Avenue’s Design Control module supports traceability from user needs through design transfer, with controlled review workflows and a design history file structure aligned with FDA 21 CFR Part 820 QMSR requirements.
What Post-Market Compliance Obligations Does a Class II Manufacturer Face?
Post-market compliance for a Class II medical device manufacturer is more demanding than many companies anticipate when they are focused on achieving 510(k) clearance. The post-market phase requires ongoing active surveillance, not passive monitoring.
The four core post-market compliance obligations for a Class II manufacturer under FDA and EU MDR are:
- Medical Device Reporting (MDR). Manufacturers must report to FDA any device malfunction that would be likely to cause or contribute to a serious injury or death if it recurs, all serious injuries and deaths, and certain other adverse events. MDR reports have strict 30-day and 5-day submission timelines depending on the event type. An eQMS complaint-handling module that supports the MDR workflow is essential for consistently meeting these obligations.
- Complaint handling. FDA 21 CFR Part 820 QMSR requires a formal complaint handling process that captures every complaint, evaluates it for MDR reportability, investigates the root cause, and documents the outcome. Complaints cannot be handled informally or tracked in general customer service tools that do not produce the required audit trail.
- CAPA management. Corrective and preventive actions triggered by complaints, nonconformances, internal audit findings, or trend analysis must be managed through a documented, closed-loop process with root cause analysis, defined corrective actions, and verification of effectiveness. FDA inspectors consistently cite CAPA deficiencies as one of the most common observations in Class II device manufacturer inspections.
- Post-market surveillance under EU MDR. For Class II equivalent devices sold in European markets, EU MDR 2017/745 requires a formal post-market surveillance plan, periodic safety update reports for Class IIa devices, and post-market clinical follow-up documentation. These requirements demand a quality system that captures and organizes post-market evidence in a structured, retrievable format.
Grand Avenue’s Complaint Handling module supports structured complaint intake, MDR reportability evaluation, investigation workflow, and closure documentation. Grand Avenue’s CAPA module provides the closed-loop corrective action process that both FDA and ISO 13485 require.
How Does ISO 13485 Certification Affect Class II Manufacturers?
ISO 13485:2016 is the international quality management system standard for medical device manufacturers, and it is effectively a prerequisite for Class II manufacturers seeking market access outside the United States. The EU CE mark pathway under EU MDR 2017/745 requires ISO 13485 certification as part of the conformity assessment process for most device categories. Many contract manufacturers, distributors, and OEM partners require ISO 13485 certification from their suppliers before entering into quality agreements.
For a Class II manufacturer, ISO 13485 certification and FDA 21 CFR Part 820 compliance are complementary rather than duplicative. The two standards share significant structural overlap, as both require controlled document management, management review, corrective and preventive action, complaint handling, internal auditing, and supplier management. An eQMS that supports both standards within a single system allows a manufacturer to satisfy both sets of requirements through one set of quality processes rather than maintaining parallel systems.
| Quality Process | FDA 21 CFR Part 820 QMSR | ISO 13485:2016 |
| Document control | Required: controlled procedures with approval and change history | Required, clause 4.2.4 |
| Training records | Required: personnel competence and training documentation | Required, clause 6.2 |
| Design controls | Required: full design control process for Class II devices | Required, clause 7.3 |
| CAPA | Required: closed-loop corrective and preventive action | Required, clauses 8.5.2 and 8.5.3 |
| Complaint handling | Required: formal complaint process with MDR evaluation | Required, clause 8.2.2 |
| Internal audits | Required: planned internal quality audits | Required, clause 8.2.4 |
| Supplier management | Required: supplier evaluation and control | Required, clause 7.4 |
| Management review | Required: management review of quality system effectiveness | Required, clause 5.6 |
An eQMS that addresses every row in this table within a single platform gives a Class II manufacturer one quality infrastructure that satisfies both regulatory regimes without duplication. Grand Avenue Software supports all of these requirements through its modular suite, allowing manufacturers to implement the modules relevant to their current compliance stage and add more as their obligations expand.
Which Grand Avenue Modules Are Most Critical for Class II Manufacturers?
Class II medical device manufacturers have a broader set of quality system requirements than early-stage startups, and the modules they need reflect the full scope of their post-market compliance obligations. The following modules address the specific demands of the Class II compliance lifecycle:
| Module | Class II Compliance Contribution | Regulatory Requirement |
| Document Control | Controlled SOPs, work instructions, and design history files with full version history and approval audit trails | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 4.2.4, 21 CFR Part 11 |
| Design Control | Traceability from user needs through design outputs, design review documentation, and design history file maintenance | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 7.3 |
| CAPA | Closed-loop corrective and preventive action with root cause analysis, actions, and effectiveness verification | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clauses 8.5.2 and 8.5.3 |
| Complaint Handling | Structured complaint intake, MDR reportability evaluation, investigation workflow, and post-market surveillance documentation | FDA 21 CFR Part 820 QMSR, EU MDR 2017/745, ISO 13485:2016 clause 8.2.2 |
| Training Management | Automated training completion tracking for all personnel performing regulated activities, with records exportable for inspection | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 6.2 |
| Supplier Management | Approved supplier list maintenance, supplier evaluation records, and corrective action tracking for supplier quality issues | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 7.4 |
| Audit Management | Internal audit planning, execution, finding documentation, and closure tracking that demonstrates ongoing quality system oversight | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 8.2.4 |
| Risk Management | ISO 14971 risk management process supporting hazard identification, risk estimation, and risk control documentation | ISO 14971:2019, ISO 13485:2016 clause 7.1, EU MDR 2017/745 |
| Nonconforming Materials | Identification, segregation, and disposition of nonconforming products with documented review and approval | FDA 21 CFR Part 820 QMSR, ISO 13485:2016 clause 8.3 |
| Authentication Management | 21 CFR Part 11 compliant electronic signatures with user authentication and audit trail integrity for all regulated records | FDA 21 CFR Part 11 |
What Does This Look Like in Practice? Class II Manufacturers Using Grand Avenue Software
The compliance requirements described above are reflected in the documented experiences of medical device manufacturers using Grand Avenue Software across a range of device categories and regulatory environments.
Checkpoint Surgical, which manufactures Class II intraoperative peripheral nerve stimulator technology, replaced a legacy on-premise QMS and paper-based training process with Grand Avenue Software. The company previously had a full-time employee dedicated to document control and training management for a distributed field team. After implementation, those processes became fully electronic and audit-ready, with the cost savings more than covering the system investment. The full story is available in the Checkpoint Surgical case study.
Innovia Medical, a global surgical device manufacturer across five specialties including ENT, ophthalmology, and sterile processing — with Class II device categories including Sterile Processing and Aesthetic & Reconstructive — deployed Grand Avenue Software in a phased rollout beginning with Document Control and Training Management and expanding to eight modules. The modular approach allowed each site to demonstrate compliance results before scaling to additional quality processes. The full story is available in the Innovia Medical case study.
Intricon, a contract manufacturer serving Class II and other medical device OEMs, replaced paper-based NCMR and CAPA workflows with Grand Avenue Software. The implementation focused on out-of-the-box functionality with minimal customization, delivering greater task visibility, improved DCR workflows, and a more manageable approved supplier list. The full story is available in the Intricon case study.
Frequently Asked Questions About eQMS for Class II Medical Device Manufacturers
Do Class II devices require design controls?
Yes. FDA 21 CFR Part 820 QMSR requires design controls for Class II medical devices. Design controls must cover design planning, design inputs, design outputs, design review, design verification, design validation, design transfer, design changes, and the design history file. These requirements apply from the beginning of design and development and are directly relevant to the 510(k) submission, which relies on design history file documentation as technical evidence.
What is the difference between complaint handling and MDR reporting for a Class II manufacturer?
Complaint handling is the internal process of capturing, investigating, and resolving reports of product performance issues from customers, distributors, or clinical users. MDR reporting is the external obligation to report specific types of adverse events to FDA within defined timelines. Every MDR-reportable event should originate from the complaint handling process, but not every complaint requires an MDR report. An eQMS complaint handling module that includes MDR reportability evaluation as a structured workflow step ensures that reportable events are identified consistently and reported on time.
How does a Class II manufacturer prepare for an FDA inspection after 510(k) clearance?
A Class II manufacturer should treat 510(k) clearance as the beginning of ongoing FDA oversight, not the end of regulatory work. Post-clearance, the manufacturer becomes subject to FDA Quality System inspections, which evaluate whether the quality system described in the 510(k) submission is actually in place and functioning. The inspection will cover document control, training records, complaint handling, CAPA, and manufacturing controls. A manufacturer whose quality processes are operating in a validated eQMS that produces complete audit trails is in a materially stronger position than one relying on paper-based or generic digital tools.
Is ISO 13485 certification required for US Class II manufacturers?
ISO 13485:2016 certification is not required by FDA for US Class II device manufacturers. However, it is effectively required for manufacturers seeking to sell in European markets under EU MDR 2017/745, and it is commonly required by contract manufacturers, OEM partners, and distributors who require evidence of a compliant quality system before entering quality agreements. Many Class II manufacturers pursue ISO 13485 certification because the standard’s requirements closely align with FDA 21 CFR Part 820 QMSR, and a single quality system can satisfy both simultaneously.
What does an eQMS need to support ISO 14971 risk management for a Class II device?
ISO 14971:2019 is the international standard for risk management of medical devices and is referenced by both ISO 13485:2016 and EU MDR 2017/745. An eQMS risk management module should support hazard identification, risk estimation, risk evaluation, risk control measure documentation, and residual risk assessment. Grand Avenue’s Risk Management module is designed to support ISO 14971 risk management within the same quality infrastructure as document control, CAPA, and complaint handling.
Can a Class II manufacturer manage both FDA and EU MDR compliance in a single eQMS?
Yes. Grand Avenue Software supports FDA 21 CFR Part 820 QMSR, ISO 13485:2016, EU MDR 2017/745, and FDA 21 CFR Part 11 within a single platform. Class II manufacturers targeting both US and European markets can build one compliant quality infrastructure that satisfies the requirements of both regulatory regimes simultaneously, eliminating the need for parallel systems or duplicate documentation processes.
What does Grand Avenue Software cost for a Class II medical device manufacturer?
Grand Avenue Software uses a modular pricing structure starting at $3,000, allowing Class II manufacturers to pay for the modules they need at each stage of their compliance lifecycle. Full pricing details are available on the Pricing page. The modular structure means a manufacturer can start with Document Control and Training Management and expand to Design Control, CAPA, Complaint Handling, and other modules as their compliance obligations grow.
How Grand Avenue Software Supports Class II Medical Device Manufacturers
Grand Avenue Software has supported medical device companies across a range of device classifications and regulatory environments for over 20 years. The platform covers the full Class II compliance lifecycle, from design controls and 510(k) readiness through post-market surveillance and ISO 13485 certification, in a single, cloud-based, modular system with transparent pricing and best-in-class implementation support.
This article is intended for general informational purposes only and does not constitute legal, regulatory, or compliance advice. Medical device companies should consult qualified regulatory affairs professionals and legal counsel when developing and implementing their quality management systems. Device classification and applicable regulatory requirements should be verified with qualified regulatory affairs professionals based on your specific product, intended use, and target markets.