Medical Device QMS: ISO 13485 and FDA-Compliant Quality Management

For manufacturers past clearance. Built for production.

Medical Device QMS Software: A Full Production-Phase Quality System for QMSR and ISO 13485 Compliance

Medical device QMS software is a quality management system built to satisfy the production quality, complaint handling, training, CAPA, supplier control, and post-market surveillance requirements that the Quality Management System Regulation (QMSR) and ISO 13485:2016 impose on medical device manufacturers. It differs from a generic QMS in that its record architecture, workflow enforcement, and audit evidence structure are organized around the specific record types and traceability requirements of device manufacturing: the Device Master Record (DMR), the Device History Record (DHR), the Design History File (DHF), and the complaint handling and MDR evaluation obligations that apply to any commercially distributed device.

Most medical device QMS software is built for the design phase. It optimizes for 510(k) submission readiness, design history file completeness, and the document-heavy work of early-stage product development. That is a well-served market. The market that is less well served is the mid-market manufacturer who cleared FDA review and is now managing a quality system for an active, commercially distributed product.

The quality system needs of a manufacturer in active production differ materially. Device History Records must be maintained for every manufactured unit. Field complaints require investigation and MDR evaluation. Production nonconformances require CAPA with verified closure. Training records for production and quality staff must be linked to current procedure versions. The Device Master Record must be controlled, versioned, and accessible as the authoritative production specification. eLeaP’s medical device QMS software is built for this environment. This page covers the QMSR regulatory framework, Device Master Record and Device History Record management, complaint handling and MDR evaluation, supplier controls under ISO 13485 Section 7.4, CAPA for production-phase quality systems, training under ISO 13485 Section 6.2, and post-market surveillance obligations.

Design Phase vs. Production Phase: Why the QMS Requirements Are Different

A device company in the design phase needs a QMS that manages design controls, risk management under ISO 14971, and the design history file. QMS platforms purpose-built for the design phase optimize for 510(k) preparation and FDA design control requirements, and for that development-phase buyer they serve a specific need. But a manufacturer who has passed clearance and is shipping product to hospitals, distributors, or direct-to-patient channels has a structurally different set of quality system obligations.

Design is largely frozen. The quality system is now predominantly operational: production records, nonconformance management, incoming inspection, supplier audits, complaint intake, MDR evaluation, and training for the production floor. The DHF is a maintained archive, not an active workspace. The DHR is a growing ledger of production evidence that must be complete and accurate for every unit shipped. Design-phase QMS platforms are not optimized for this environment — their strength is pre-market; their limitation is the ongoing operational quality system that carries compliance obligations for the life of the product.

eLeaP targets the production-phase manufacturer. The platform covers the full quality system suite — document control, CAPA, supplier quality, nonconformance, training, and complaint management — in a single configurable instance. It is optimized for the ongoing quality operations of a manufacturer with cleared products, production staff, and regulatory surveillance obligations.

The QMSR: What the Quality Management System Regulation Means for Your QMS Software

The Quality Management System Regulation (QMSR), effective February 2, 2026, replaced 21 CFR Part 820 in its prior form as the FDA quality system regulation for medical device manufacturers. The QMSR is the most significant structural change to the medical device quality regulation in decades. Its core mechanism is incorporation by reference: the QMSR adopts ISO 13485:2016 as the foundational quality system standard for medical device manufacturers regulated by FDA.

The practical consequence is that a medical device quality system built on ISO 13485 is now, in substance, a QMSR-compliant quality system. FDA’s supplemental requirements in the QMSR address areas where the agency’s expectations extend beyond the ISO 13485 baseline — complaint handling, MDR evaluation, and certain records and traceability requirements — but the underlying quality system architecture is ISO 13485. Device manufacturers who had already aligned their quality systems to ISO 13485 for international market access are in the strongest position for QMSR compliance.

eLeaP’s medical device QMS software is structured around ISO 13485 requirements across all functional modules — document control, CAPA, supplier management, production controls, training, and complaint handling. Customers using eLeaP for ISO 13485 certification have the structural foundation for QMSR compliance already in place. The transition documentation package from eLeaP maps the QMSR requirements to the ISO 13485 sections addressed by each platform module, supporting the gap assessment that manufacturers completing their QMSR transition need to document.

For manufacturers who operated under the prior 21 CFR Part 820 without ISO 13485 alignment, the QMSR transition requires a more substantive quality system review. eLeaP supports this transition with configurable workflow templates mapped to QMSR requirements and a structured implementation approach that prioritizes the areas of greatest gap for manufacturers coming from the prior 820 framework.

Device Master Record and Device History Record: Two Distinct Requirements, One Connected System

The Device Master Record and the Device History Record are the two foundational record types in medical device production quality. They are conceptually distinct — the DMR is the specification, the DHR is the evidence — but they must be connected: the DHR for every unit produced must demonstrate that the unit was manufactured in conformance with the DMR in effect at the time of production. When an FDA investigator examines a DHR, they are verifying that the production record references the correct DMR revision and that every step performed matches the authorized specifications.

Device Master Record Management

The DMR under the QMSR and ISO 13485 must include or reference the device specifications, production process specifications, quality assurance procedures and specifications, packaging and labeling specifications, and installation and servicing procedures. eLeaP manages the DMR as a controlled document set within the quality management system. Each document type that constitutes the DMR — manufacturing specifications, work instructions, acceptance criteria, test procedures — is version-controlled, routed through the configured approval workflow on revision, and accessible from the device record in the system.

When a DMR document is revised, the change control workflow governs the revision from initiation through impact assessment, approval, and release. Documents that affect validated processes or established production methods trigger the appropriate revalidation or process verification activities as part of the change closure workflow. The change record links to the revised DMR document and to any associated CAPA, deviation, or complaint that originated the change — providing the full traceability chain that an auditor or investigator expects to find.

Device History Record Management

The DHR for each manufactured unit must demonstrate that the device was manufactured in accordance with the DMR. Under ISO 13485:2016, batch record and production control requirements are governed by Clause 7.5.1 (control of production and service provision), while the Medical Device File — the master specification set equivalent to the DMR — is governed by Clause 4.2.3. The QMSR and ISO 13485 require that the DHR include the dates of manufacture, the quantity manufactured and released, the acceptance records indicating the device was manufactured in accordance with the DMR, the primary identification label, and any unique device identifier or other identification used. For implantable devices, the DHR must also include the identity and traceability information required for that device class. Unique Device Identifier (UDI) values — including both the Device Identifier (DI) and the Production Identifier (PI) components — are captured within the production record fields of the DHR, supporting lot-level and unit-level traceability requirements for post-market complaint investigations and field safety corrective actions.

eLeaP’s production record structure creates DHR records at the unit or batch level, depending on the manufacturer’s production model. The DHR links to the DMR version in effect at the time of production, the equipment qualification records for equipment used in production, the acceptance inspection records for incoming materials used in the unit, and the in-process and final acceptance test records. Nonconformances detected during production associate directly with the DHR for the affected unit, along with the disposition decision and any CAPA initiated.

Training records for the production personnel who performed each DHR step are accessible from the DHR record within the same platform. An FDA investigator reviewing a DHR can verify that the operators who performed each step were trained on the current work instruction version at the time the step was performed. This traceability — from the DHR step to the operator to the training record to the document version — is the standard that QMSR and ISO 13485 Section 6.2 together require, and it is available as a native capability in eLeaP rather than as a manual reconciliation exercise across separate systems.

Complaint Handling: MDR Evaluation and the QMSR Requirement

The QMSR complaint handling requirements — incorporating ISO 13485 Section 8.2.2 and FDA’s supplemental complaint file requirements — mandate that each manufacturer maintain complaint files and establish and maintain procedures for receiving, reviewing, and evaluating complaints by a formally designated unit. Every complaint must be evaluated to determine whether it requires investigation and, if investigation is required, whether the investigation reveals information that requires submission of a Medical Device Report under 21 CFR Part 803.

The complaint handling obligation is one of the most inspection-sensitive areas of the medical device quality system. FDA investigators review complaint files for evidence that complaints were received and logged promptly, that every complaint was evaluated for MDR reportability, that investigations were conducted for complaints meeting the investigation criteria, and that MDRs were filed within the required timeframes — 30 days from becoming aware of a reportable death, serious injury, or a device malfunction that would be likely to cause or contribute to death or serious injury if it were to recur; and five days for events that require remedial action to prevent an unreasonable risk of substantial harm to the public health.

eLeaP’s complaint management workflow captures complaints at intake — from healthcare providers, distributors, patients, or sales representatives — and routes each complaint through a structured evaluation workflow. The initial evaluation determines whether the complaint meets the criteria for investigation under the manufacturer’s complaint handling procedure. If investigation is required, the investigation record captures the device identification, the lot or unit number, the nature of the complaint, and the investigation findings.

The MDR evaluation step is a required stage in the investigation workflow. The evaluator documents the MDR decision criteria determination — whether the device malfunctioned, caused or contributed to a death or serious injury, or could do so if the malfunction recurred — with the rationale. If an MDR is required, the complaint record tracks the MDR filing documentation, submission status, and submission date against the applicable reporting window. If no MDR is required, the rationale is documented in the complaint record and available for regulatory review.

Complaint trending is a native reporting function. When multiple complaints reference the same device family, the same component, or the same failure mode, the trend surfaces in the complaint management dashboard. Complaint trends that indicate a potential systematic product issue generate notifications for quality management review and, where indicated, initiate the CAPA process. The link between the complaint trend and the resulting CAPA is maintained in both records — the complaint records reference the CAPA, and the CAPA record references the complaints that originated it.

Supplier Quality Management: ISO 13485 Section 7.4 in Production

Incoming inspection failures — components that fail acceptance testing, materials that do not meet specifications — connect directly to the DHR for any unit produced from that lot and generate supplier corrective action request (SCAR) obligations. The supplier quality record must show that the incoming inspection result was documented, the SCAR was issued and tracked to closure, and the supplier’s response was evaluated before the supplier remains on the approved supplier list. When a supplier’s pattern of nonconformances crosses the threshold defined in the manufacturer’s supplier qualification criteria, re-qualification or disqualification is required.

eLeaP’s supplier quality module maintains supplier qualification records including initial evaluation, qualification status, approved supplier list membership, audit history, and SCAR history. Supplier performance scorecards aggregate incoming inspection reject rates, SCAR closure rates, and audit finding trends. Supplier re-evaluation at defined intervals is scheduled within the system and generates notifications when due. Incoming inspection records link to purchase orders and supplier records, and SCARs link to the incoming inspection nonconformances that triggered them — maintaining the traceability chain from incoming inspection finding through corrective action closure.

CAPA for Medical Device Manufacturers: Production Nonconformances and the QMSR Requirement

The QMSR CAPA requirement, aligned with ISO 13485 Sections 8.5.2 and 8.5.3, requires that manufacturers identify the causes of actual and potential nonconformities, evaluate the need for action to prevent recurrence, determine and implement actions needed, record the results of actions taken, and review the effectiveness of corrective and preventive actions taken. For production-phase medical device manufacturers, the CAPA input sources differ from a startup’s design-phase CAPA inputs: production nonconformances, incoming inspection rejections, field complaints, supplier SCARs, internal audit findings, and post-market surveillance data all feed the CAPA system.

eLeaP’s CAPA workflow for medical device manufacturers is configured to the production context. Nonconformances detected in production associate directly with the DHR for the affected unit. When a nonconformance pattern indicates a systemic issue — the same failure mode appearing across multiple DHRs for the same device family — the CAPA is initiated from within the nonconformance trending view, with all contributing events linked to the CAPA record. The root cause investigation has access to the production records, the equipment qualification status, and the training records for personnel involved in the affected production steps without manual data assembly.

CAPA effectiveness verification for production-phase issues requires a monitoring period during which effectiveness criteria are assessed against actual production data. eLeaP’s effectiveness verification workflow defines the monitoring period, the specific metrics being tracked, and the threshold that constitutes successful verification. The CAPA record is not available for closure until the monitoring period is complete and the effectiveness data is documented. Recurrence during the monitoring period automatically re-opens the effectiveness verification stage and notifies quality management.

Training for Medical Device Production Staff: ISO 13485 Section 6.2 and the QMSR

ISO 13485 Section 6.2 requires that personnel performing work affecting product quality be competent on the basis of appropriate education, training, skills, and experience, and that records of training and experience be maintained. The QMSR adopts this requirement by reference. For production-phase manufacturers, every operator performing a step in the manufacturing process must be demonstrably trained on the current version of the work instruction governing that step, and training records must be traceable to the specific document version.

eLeaP’s integrated QMS and LMS deliver this traceability natively. When a work instruction in the DMR is revised, the system identifies every production role assigned to that document and creates retraining assignments automatically. The training completion record carries the document version number. The DHR for any unit produced after the revision effective date references an operator training record that reflects the current work instruction version, not the prior one. The gap between document revision and confirmed retraining — the gap that generates training-related 483 observations — is closed structurally rather than procedurally.

For manufacturers implementing new production lines, new products, or new procedures, eLeaP’s role-based training matrix assigns all required training to new personnel or personnel moving into new roles without manual enrollment. The system automatically cross-references a user’s existing training records against their new role requirements, generating a targeted list of outstanding training assignments needed to satisfy the role’s training profile. Quality managers can verify training compliance against active DHR role assignments before sign-off, providing the documentary evidence that prevents training-related 483 observations.

Post-Market Surveillance and Feedback: ISO 13485 Section 8.2.1 and EU MDR Obligations

ISO 13485 Section 8.2.1 requires that the organization gather and monitor information relating to whether the organization has met customer requirements, and use complaint data and post-market surveillance data as feedback inputs to the quality system — including as inputs to management review, CAPA, and product improvement decisions. For manufacturers selling into EU markets under EU MDR (2017/745) or EU IVDR (2017/746), post-market surveillance obligations are substantially more prescriptive: manufacturers must maintain a post-market surveillance plan, generate periodic safety update reports (PSURs) or post-market surveillance reports on defined schedules, and conduct post-market clinical follow-up where required.

eLeaP supports post-market surveillance through the complaint management module, which aggregates complaint data, failure mode trends, and feedback data for analysis. Complaint trend reports are available as inputs to the post-market surveillance plan, and eLeaP streamlines post-market surveillance by aggregating and making exportable the internal quality system inputs — complaint trends, nonconformances, and CAPA metrics — that feed into broader PSUR and PMSR clinical summaries. The clinical evaluation narrative and external data sources required for a complete PSUR remain the manufacturer’s responsibility. Post-market surveillance data feeds into the management review input data set and, where complaint trends indicate systematic product issues, initiates the CAPA process with permanent cross-reference traceability — the originating complaint trend and the resulting CAPA record are linked in both directions so that auditors can navigate between them without leaving the quality system.

Evaluating Medical Device QMS Software for Production-Phase Manufacturers

The market includes platforms optimized for pre-market development and platforms marketed as full QMS suites without production-phase depth. When evaluating medical device QMS software for a manufacturer in active production, the evaluation should test workflow specificity rather than feature presence.

Question 1: Does the Platform Maintain DHRs Linked to the DMR Version in Effect at Production?

Does the platform maintain DHRs that link production steps to the DMR version in effect at the time of production — or does it manage documents that describe what DHRs should contain? A document management system can store DHR templates. A production-phase medical device QMS creates DHR records that carry the DMR version reference at the record level, link to the acceptance inspection records for materials used, and link to the equipment qualification records for equipment used in that production run. The distinction between a document that describes a DHR and a system record that is a DHR is the audit evidence difference.

Question 2: Does the Complaint Workflow Include a Structured MDR Evaluation Stage?

Does the complaint handling workflow include a structured MDR evaluation step with documentation of the determination and the rationale — or does it provide a generic complaint intake form? MDR evaluation is not a checkbox. It is a documented determination that must include the device malfunction or injury assessment against the reportability criteria of 21 CFR Part 803, with the rationale documented and the submission status tracked against the applicable reporting window. A complaint system without a structured MDR evaluation stage forces the evaluator to document the determination outside the complaint record, creating a traceability gap.

Question 3: Does a DMR Document Revision Automatically Trigger Retraining?

Does a DMR document revision automatically trigger retraining for affected production roles — and does the DHR for subsequently produced units reference operator training records that match the current work instruction version? The training gap between a procedure revision and confirmed workforce retraining is the most common source of training-related 483 observations in production-phase medical device inspections. A QMS+LMS integration that automatically creates version-stamped training assignments on document revision, and links DHR production steps to the operator’s training record for that document version, closes that gap structurally.

Question 4: Does the CAPA Effectiveness Workflow Gate Closure on a Completed Monitoring Period?

Does the CAPA effectiveness verification workflow prevent closure until the monitoring period is complete and effectiveness data is documented — or does it allow closure based on corrective action assignment alone? ISO 13485 Section 8.5.2 requires that the effectiveness of corrective action taken be reviewed. A CAPA system that allows closure when corrective actions are assigned and implemented, without requiring a defined monitoring period and documented effectiveness evidence, does not satisfy this requirement. The monitoring period enforcement must be a system control, not a procedural expectation.

Question 5: Does the Platform Support the Full Production Quality Suite in a Single System?

Does the platform support the full production quality suite — DMR and DHR management, complaint handling and MDR evaluation, supplier qualification and SCAR management, nonconformance control, CAPA with effectiveness verification, and training management with document version traceability — in a single configurable system? A production-phase manufacturer whose quality system spans multiple platforms for these functions faces manual reconciliation at every audit and inspection. Each cross-system record linkage is a potential traceability gap. A single integrated platform eliminates those gaps at the architecture level.

eLeaP’s answers to all five questions are yes, demonstrable in a scoped walkthrough configured for medical device production. The demonstration covers DHR-to-DMR traceability, complaint intake through MDR evaluation, document revision-to-training assignment workflow, and supplier SCAR management — against a configuration reflecting device manufacturing rather than a generic quality system demonstration. Request a scoped medical device QMS demonstration at eleapsoftware.com.

Frequently Asked Questions: Medical Device QMS Software

What is medical device QMS software?

Medical device QMS software is a quality management system built to satisfy the production quality, complaint handling, CAPA, training, supplier control, and post-market surveillance requirements of the QMSR (effective February 2, 2026) and ISO 13485:2016. It differs from a generic QMS in that its record architecture is organized around the specific record types of device manufacturing — the Device Master Record (DMR), the Device History Record (DHR), the Design History File (DHF) — and its workflows enforce the ISO 13485 and QMSR-specific requirements for each record type, including MDR evaluation in complaint handling, traceability requirements for implantable devices, and training record linkage to specific DMR document versions.

What is the QMSR and how does it relate to ISO 13485?

The Quality Management System Regulation (QMSR), effective February 2, 2026, is FDA’s current quality system regulation for medical device manufacturers, replacing the prior 21 CFR Part 820. The QMSR incorporates ISO 13485:2016 by reference as its foundational quality management framework, meaning that a manufacturer whose quality system satisfies ISO 13485:2016 satisfies the QMSR’s foundational requirements. FDA’s supplemental QMSR requirements — covering complaint handling, MDR evaluation and reporting, and certain traceability obligations — extend beyond the ISO 13485 baseline but do not contradict it. Manufacturers who had maintained ISO 13485-aligned quality systems for international market access are in the strongest structural position for QMSR compliance.

What is the difference between the Device Master Record and the Device History Record?

The Device Master Record is the specification: it contains or references the device specifications, production process specifications, quality assurance procedures, packaging and labeling specifications, and installation and servicing procedures that define how the device is manufactured and what it must conform to. The Device History Record is the evidence: it records, for each manufactured unit or batch, the dates of manufacture, the quantity manufactured and released, the acceptance records demonstrating conformance with the DMR, and the unique device identifier or other identification. The DHR for every unit produced must reference the DMR version that was in effect at the time of production, demonstrating that the unit was manufactured against the current authorized specification.

What are the MDR reporting requirements for medical device complaint handling?

21 CFR Part 803 requires that medical device manufacturers submit Medical Device Reports to FDA for device malfunctions, serious injuries, or deaths that involve their devices. The reporting timeframes are: 30 days from becoming aware of a reportable death, serious injury, or a device malfunction that would be likely to cause or contribute to death or serious injury if it were to recur; and five days for events that require remedial action to prevent an unreasonable risk of substantial harm to the public health. Every complaint must be evaluated for MDR reportability, and the determination — whether an MDR is required or not — must be documented with the rationale. MDR submissions must be tracked with their submission date and status against the applicable reporting window.

What does ISO 13485 Section 6.2 require for production staff training?

ISO 13485 Section 6.2 requires that personnel performing work affecting product quality be competent on the basis of appropriate education, training, skills, and experience. The organization must determine the necessary competence, provide training to achieve and maintain it, evaluate the effectiveness of training, and maintain records of education, training, skills, and experience. For production-phase manufacturers, the practical compliance requirement is that every operator performing a manufacturing step is trained on the current version of the work instruction governing that step — not a prior superseded version — and that this currency is demonstrable from training records linked to the specific document version.

What are the ISO 13485 supplier control requirements under Section 7.4?

ISO 13485 Section 7.4 requires that medical device manufacturers establish documented criteria for evaluating and selecting suppliers based on their ability to meet requirements, maintain records of evaluations and resulting actions, and monitor and re-evaluate suppliers at defined intervals. Section 7.4.2 requires that purchasing information describe the product or service with sufficient clarity for verification upon receipt. Section 7.4.3 requires that purchased products be verified against specified requirements before use. For production-phase manufacturers, supplier controls are an ongoing quality system function: incoming inspection results, SCARs, audit findings, and re-evaluation records all constitute the supplier quality record that an FDA investigator or Notified Body auditor will review.

What post-market surveillance obligations apply to medical device manufacturers under QMSR and EU MDR?

Under the QMSR, medical device manufacturers must gather and monitor post-market feedback — including complaint data — as an input to the quality system, management review, and CAPA. Under EU MDR (2017/745) and EU IVDR (2017/746), post-market surveillance obligations are more prescriptive: manufacturers must maintain a post-market surveillance plan, generate periodic safety update reports (PSURs for Class IIa, IIb, and III devices) or post-market surveillance reports (for Class I devices) on defined schedules, and conduct post-market clinical follow-up where required. The complaint management and trend analysis data maintained in the QMS is the primary data source for PMS reporting — the QMS must aggregate and make accessible the complaint, CAPA, and feedback data that post-market surveillance reporting requires.

How does eLeaP’s QMS+LMS integration satisfy the ISO 13485 production training requirement?

ISO 13485 Section 6.2’s training requirement is not satisfied by maintaining training records in a separate LMS that the QMS cannot query. It requires that the quality system demonstrate, for any production operator performing a manufacturing step, that they are trained on the current version of the document governing that step. eLeaP’s integrated QMS and LMS address this through two mechanisms: first, document revisions automatically generate training assignments for all affected production roles, closing the interval between a procedure revision and workforce retraining; and second, DHR production steps link to the operator’s training record within the same platform, so that an FDA investigator can verify training currency for any production step in any DHR without cross-system navigation or manual record assembly.

Medical Device QMS Software: Terminology and Search Synonyms

Medical device QMS software is referenced by several terms across regulatory guidance, Notified Body requirements, and quality management software categories. The following synonyms and related terms describe capabilities covered on this page.

Medical Device Quality Management System / Medical Device QMS

“Medical device quality management system” and “medical device QMS” are direct synonyms for medical device QMS software, describing the platform from the quality management system architecture frame. The functional scope is identical: DMR and DHR management, complaint handling and MDR evaluation, CAPA, training with document version traceability, supplier controls, and post-market surveillance data management — all configured for ISO 13485 and QMSR compliance.

QMSR Software / QMSR Compliance Software

“QMSR software” and “QMSR compliance software” are the US-regulatory-specific terms that have emerged since the QMSR’s February 2, 2026 effective date. Because the QMSR incorporates ISO 13485 by reference, QMSR software is in substance ISO 13485 software with FDA’s supplemental complaint handling, MDR evaluation, and traceability requirements addressed. Buyers searching “QMSR software” are typically US manufacturers evaluating whether their existing quality system fully addresses the QMSR’s supplemental requirements above the ISO 13485 baseline.

ISO 13485 Certified QMS Software / ISO 13485 Compliant QMS

“ISO 13485 certified QMS software” and “ISO 13485 compliant QMS” describe a medical device QMS platform structured around ISO 13485:2016 clause requirements — the same structure that now underlies QMSR compliance. ISO 13485 compliance covers international market access requirements including EU MDR/IVDR Notified Body certification; QMSR compliance covers FDA-regulated US market access. A single ISO 13485-aligned QMS platform satisfies both.

Device History Record Software / DHR Management Software

“Device history record software” and “DHR management software” refer specifically to the production record management capability within medical device QMS software — the system capability that creates DHR records at the unit or batch level, links them to the DMR version in effect at production, and maintains the acceptance inspection, equipment qualification, and operator training record linkages that make each DHR a complete production evidence set.

Medical Device Complaint Management Software / MDR Software

“Medical device complaint management software” and “MDR software” refer to the complaint handling and MDR evaluation capability within medical device QMS software. The defining requirements are: mandatory MDR evaluation as a structured workflow stage, documented determination with rationale, and submission tracking against 30-day and 5-day reporting windows. A complaint system without these structured MDR evaluation capabilities does not satisfy the QMSR complaint handling requirements.

Medical Device CAPA Software / Nonconformance Management Software

“Medical device CAPA software” and “nonconformance management software” refer to the corrective and preventive action capability configured for ISO 13485 Section 8.5.2 and 8.5.3 requirements — root cause linkage, effectiveness verification criteria as required pre-implementation fields, and closure prevention without documented effectiveness data. Medical device CAPA software differs from a general corrective action tool in that its CAPA records connect to DHR nonconformances, complaint records, audit findings, and supplier SCARs as originating quality events within the same system.

About eLeaP QMS

eLeaP is a quality management and learning management platform built by Telania, LLC, founded in 2002. The platform serves medical device manufacturers, pharmaceutical companies, biotech, CDMO/CRO, aerospace, food and beverage, and cannabis organizations requiring a fully integrated, validated QMS and LMS in a single platform. For medical device manufacturers, the core differentiator is native QMS+LMS integration: DMR document revisions automatically trigger training assignments for affected production roles, design-change-driven document revisions are gated on training completion before the change can close, and the DHR links production steps to operator training records within the same platform. eLeaP is designed for mid-market medical device manufacturers (50–500 employees) with cleared or approved products who require full QMSR and ISO 13485 compliance capability without enterprise QMS implementation complexity.

Related resources: