Medical Device Training LMS: FDA Compliance and Product Training Management

QMSR and ISO 13485 Competency Documentation, CAPA Integration, and DHR-Ready Record

Medical Device Training LMS: FDA QMSR and ISO 13485 Compliance

Medical device manufacturers operate under training requirements that are structurally different from pharmaceutical GMP — not less demanding, but differently organized. Where pharmaceutical training obligations are driven primarily by procedure-based SOP training matrices and CAPA retraining workflows, medical device training requirements are embedded throughout the quality management system regulation itself: in design controls, production and process controls, corrective and preventive action, complaint handling, and management responsibility. Training is not a standalone compliance function in a medical device quality system. It is a thread woven through every major element of the QMS. Request a demo to see how eLeaP manages medical device training compliance — from design control qualification through CAPA closure — in a quality system built for current QMSR and ISO 13485 requirements.

The regulatory framework governing medical device training is now the Quality Management System Regulation (QMSR), which replaced 21 CFR Part 820 as of February 2026. The QMSR aligns US device quality requirements with ISO 13485:2016, and its training requirements are more specific and more demanding than those of the legacy Quality System Regulation. Manufacturers who were operating under legacy QSR structures without ISO 13485 alignment and who have not updated their training programs to reflect QMSR requirements are now out of compliance.

For training program design and training management infrastructure, the QMSR raises the bar in three specific ways: it requires formal competency determination for all quality-affecting functions, it requires documented effectiveness evaluation of training actions, and it requires maintenance of records spanning education, training, skills, and experience — not just training completion logs. Understanding what these requirements mean in practice, and where training obligations arise across the device quality system, is the starting point for evaluating whether a training management system is genuinely fit for the current regulatory environment.

Resources: FDA Quality Management System Regulation — QMSR Resources

The Regulatory Framework: QMSR and ISO 13485

The QMSR and Its Training Requirements

The QMSR, effective February 2026, governs quality management systems for medical device manufacturers selling into the US market. By adopting ISO 13485:2016 as its foundation, the QMSR replaced the prescriptive requirements of the legacy QSR with a risk-based, process-oriented quality management framework. For training specifically, the QMSR’s alignment with ISO 13485 Clause 6.2 introduces requirements that are materially more detailed than those in the superseded §820.25.

The QMSR requires that device manufacturers:

The effectiveness evaluation requirement is the most operationally significant addition relative to the legacy QSR. Under the QMSR, it is not sufficient to deliver training and document completion. The organization must evaluate whether training produced the competency it was designed to produce — and document that evaluation. This requirement connects device training management directly to assessment infrastructure, performance observation, and post-training quality event monitoring.

The awareness requirement is equally specific. Personnel must understand not just the procedures governing their work but the device defects that can result from improper performance of their specific functions, and the consequences of noncompliance with quality procedures. Training content must be designed with explicit reference to function-specific failure modes and device defect risks — not generic quality awareness messaging.

ISO 13485 Clause 6.2 in Detail

ISO 13485 Clause 6.2 (Human Resources) is the international standard reference from which the QMSR’s training requirements derive. For device manufacturers seeking or maintaining ISO 13485 certification — required for CE marking under EU MDR 2017/745 and IVDR 2017/746 — Clause 6.2 establishes the audit criteria against which training programs are evaluated.

Clause 6.2.1 — General. Personnel performing work affecting product quality shall be competent on the basis of appropriate education, training, skills, and experience. The word “competent” is load-bearing: it means demonstrably capable of performing the function correctly, not simply trained on the relevant procedure.

Clause 6.2.2 — Competence, awareness, and training. The organization shall determine necessary competence, provide training to achieve and maintain it, evaluate effectiveness, ensure awareness of quality relevance, and maintain records. The record-keeping requirement spans the full competency basis — education credentials, training history, skills assessments, and experience documentation — for each quality-affecting function.

Notified body auditors conducting ISO 13485 surveillance audits and MDR/IVDR technical documentation reviews examine Clause 6.2 compliance systematically. Organizations whose training records consist of completion logs without competency determination documentation, effectiveness evidence, or education and experience records will generate Clause 6.2 nonconformities.

Training Requirements Across the Device Quality System

Medical device training obligations are not confined to a single section of the quality system. They arise wherever regulated activities are performed by personnel whose competency must be demonstrated. Understanding where these obligations arise identifies where training records connect to other quality system records — and where the QMS+LMS integration delivers the most compliance value.

Design Control Training

The QMSR’s design control requirements govern development activities through which device designs are created, reviewed, verified, validated, and transferred to production. Personnel performing design control activities — design engineers, human factors specialists, clinical evaluators, regulatory affairs professionals — must be trained on the design control procedure and qualified to perform their specific roles within the design process.

Design control training documentation carries particular weight because design history file (DHF) records are reviewed during FDA inspections and product liability proceedings. A design review record signed by an engineer without a current training record for the design control procedure is a record of uncertain validity — a point FDA investigators and litigators both note.

Training requirements for design control extend beyond the design control SOP itself. Personnel conducting design verification and validation must be trained on the specific methods they employ — statistical sampling, test method validation, human factors study protocols. For software-intensive devices, personnel working under IEC 62304 must be trained on the software development lifecycle procedures governing those activities.

Design control training must remain current through the entire development lifecycle. A product requiring three years from concept to submission generates ongoing training obligations across that period: initial training, retraining when design control procedures are revised, and qualification updates when personnel change roles within the development team. Version-specific training records covering the full development timeline must be available for DHF review.

Production and Process Controls Training

Production and process controls govern the manufacturing processes by which device designs are translated into manufactured products. Production training requirements in device manufacturing follow the same logic as GMP training in pharmaceutical manufacturing: operators must be trained on the current versions of the procedures governing their manufacturing operations, equipment qualifications must be documented, and retraining must be triggered when procedures change.

The device history record (DHR) must document the procedures used in manufacturing each production unit or lot. Training records demonstrating that personnel who manufactured specific device units were trained on the current procedures at the time of manufacture are supporting documentation for the DHR. When a device becomes the subject of a complaint investigation or field safety corrective action, the DHR — including training records — is reviewed to assess whether manufacturing personnel were qualified for their functions at the time of manufacture.

Equipment qualification. Device manufacturing equipment requires process validation under the QMSR’s process controls requirements. Personnel operating validated manufacturing equipment must be trained on equipment operating procedures and qualified to use the equipment. Equipment qualification records in device manufacturing are per-operator and per-equipment — each operator’s qualification for each specific piece of equipment must be documented independently.

Sterile device manufacturing. Manufacturers of sterile medical devices operate under additional training requirements for sterile processing, cleanroom behavior, gowning, environmental monitoring, and sterilization operations. Operators in sterile manufacturing must demonstrate and maintain the behavioral discipline that contamination control requires. Periodic requalification — including observed performance assessment — is standard practice for cleanroom operators, and the training records must reflect each requalification event with its assessment basis.

Software-incorporated devices. Medical devices incorporating software — which now encompasses the majority of active medical devices — require that development and testing personnel are trained on software development lifecycle procedures under IEC 62304 and on device-specific development standards. Software training records in the device quality system context are part of the technical file and DHF, with the same version-control and audit trail requirements as manufacturing training records.

CAPA-Triggered Training in Medical Device Quality Systems

CAPA is the quality system function most reliably generating training requirements in device manufacturing. The QMSR’s CAPA requirements — aligned with ISO 13485 Clause 8.5.2 — require that corrective actions be implemented and verified for effectiveness. When a CAPA investigation identifies training as a root cause or contributing factor, the corrective action must include documented retraining with effectiveness verification before the CAPA can be closed.

The effectiveness verification requirement under ISO 13485 Clause 8.5.2 is explicit: the organization must verify that corrective actions do not adversely affect applicable regulatory requirements and that the actions taken are effective. For training-related corrective actions, this means demonstrating not just that training was completed but that the quality problem has not recurred during the effectiveness monitoring period.

For device manufacturers under a consent decree or responding to a Warning Letter — situations where CAPA program credibility is under direct FDA scrutiny — the automated closure dependency between CAPA records and training completion records is not an operational convenience. It is a compliance control that prevents the most common CAPA audit finding: CAPAs closed without verifiable evidence that corrective training was implemented and effective.

CAPA Training LMS — Connecting Corrective Actions to Retraining Workflows

eLeaP’s native QMS+LMS integration addresses the CAPA-to-training workflow directly. When a CAPA record in eLeaP’s QMS identifies retraining as a corrective action, training assignments are generated automatically in the LMS for the specified job functions and procedure versions. The CAPA record reflects live training completion status. The CAPA cannot be submitted for closure until training completion is confirmed and effectiveness verification documentation is attached. The audit trail connecting the quality event, the corrective action, the training assignment, and the completion record is maintained within a single system — producing the closed-loop documentation that FDA investigators and notified body auditors require.

Complaint Handling Training

The QMSR’s complaint handling requirements govern the evaluation, investigation, and reporting of device-related complaints, including Medical Device Reporting (MDR) obligations under 21 CFR Part 803. Personnel performing complaint investigations and MDR reportability determinations must be specifically trained and qualified for those functions.

The qualification basis for complaint investigation personnel is particularly important because MDR reporting decisions have direct regulatory consequences. Late or missing MDR submissions generate warning letters and civil money penalties. A reportability determination made by personnel without documented training on the relevant regulatory criteria is a decision of uncertain reliability — and FDA examiners in both premarket review and post-market surveillance contexts will note the absence of qualification documentation.

Complaint handling training must be refreshed when procedures are revised — a regular occurrence as MDR regulations are updated, international vigilance reporting requirements change, or complaint handling procedures are revised following CAPA investigations. Personnel who evaluate complaints must be trained on the current version of the complaint handling procedure before performing evaluations, with version-specific completion records maintained in the same way as manufacturing SOP training records.

Competency Determination: The QMSR Requirement Most Programs Underinvest In

The QMSR’s competency determination requirement — specifying the education, training, skills, and experience required for each quality-affecting function — is the element of Clause 6.2 that most device training programs have historically underinvested in, because it requires more than procedure training design.

Competency determination means producing documented competency frameworks for each quality-affecting function: what education level is required, what prior experience is relevant, what skills must be demonstrated, and what training is needed to develop competencies not established through prior background. The training program is then designed to develop and maintain those competencies — not simply to deliver procedural content.

The competency determination feeds directly into the effectiveness evaluation requirement. If the organization has not defined what competency means for a specific function, it cannot evaluate whether training produced that competency. The competency framework is the measurement standard against which training effectiveness is assessed.

eLeaP’s competency management tools support competency determination documentation within the training record structure. Job function competency requirements can be defined in the system, training items linked to specific competency dimensions, and assessment results recorded against defined competency criteria. The training record for a device manufacturer demonstrates not just what training was completed but what competency the training was designed to develop and what evidence was produced that the competency was achieved.

Effectiveness Evaluation in Practice

Effective training evaluation under the QMSR requires more than post-training testing. A complete effectiveness evaluation program includes:

Post-training assessment. A written test or practical demonstration immediately following training provides evidence that content was absorbed. Assessment pass/fail criteria must be defined in advance and documented in the training record.

On-the-job performance observation. For critical manufacturing and quality functions, documented supervisor observation of post-training job performance provides stronger effectiveness evidence than testing alone. The observation record must capture who observed, when, what was assessed, and the evaluator’s conclusion.

Quality event correlation. For CAPA-related retraining specifically, the QMSR’s effectiveness verification requirement connects training completion to quality event monitoring. If a deviation type recurs after retraining was delivered as a corrective action, the training was not effective and the CAPA requires reassessment. Effectiveness monitoring must be documented during the verification period — typically thirty to ninety days — with a formal effectiveness conclusion recorded in the CAPA record.

Periodic training needs reassessment. ISO 13485 Clause 6.2 requires ongoing management of personnel competency, not just initial training delivery. When device designs change, manufacturing processes are modified, or regulatory requirements are updated, the competency requirements for affected functions must be reassessed and the training program updated accordingly.

Device History Record and Training Documentation

The device history record required under the QMSR must demonstrate that each device unit or lot was manufactured in accordance with the device master record. Training records are the evidentiary foundation for the personnel qualification component of that demonstration.

When an investigator examines a DHR — during an inspection, an adverse event investigation, or a product liability proceeding — they need to confirm that every operator who performed a quality-affecting manufacturing step on the specific lot was trained on the current version of the governing procedure at the time of manufacture. This is a date-specific, operator-specific, version-specific query. The training management system must be able to answer it with a point-in-time compliance reconstruction, not just a current status report.

This point-in-time query capability requires that training records preserve historical training status immutably: every completion record archived with its version reference and timestamp, retrievable in exactly the state it existed on the manufacturing date regardless of subsequent training events or procedure revisions. A training record that was modified after completion — without an audit trail entry documenting the modification — cannot be relied upon as DHR supporting documentation.

eLeaP’s training record architecture preserves complete historical training status. Every completion record is archived with its version reference and completion timestamp, and point-in-time compliance queries reconstruct each operator’s training status as it existed on any specified date. Audit trail integrity confirms that no record has been modified since completion without attribution. For DHR-linked queries, the answer is retrievable in seconds.

21 CFR Part 11 LMS — Requirements, Features, and Validation

Notified Body Audits and Clause 6.2 Compliance

Device manufacturers seeking or maintaining ISO 13485 certification — required for CE marking under EU MDR and IVDR — are subject to notified body audits examining Clause 6.2 compliance. Notified body auditors assess training programs against four consistent criteria:

Competency frameworks. Does the organization have documented competency requirements for each quality-affecting function? Are these requirements specific to the device type and the function’s actual impact on product quality, or are they generic job description language?

Training matrix completeness and currency. Does the training matrix reflect all quality-affecting functions? Has it been updated when new procedures were added, when job functions changed, or when the QMSR transition required quality system revisions?

Effectiveness evaluation evidence. Does the organization have documented evidence — assessment results, performance observations, quality metric monitoring — that training produced the intended competency? Is effectiveness evaluation applied systematically or only selectively?

Calibration between documented requirements and actual records. Do training records reflect the requirements specified in the competency framework and training matrix? Or is there drift between what the training SOP specifies and what the records actually show?

The calibration question is where most Clause 6.2 audit findings originate. When the training program specifies annual requalification for critical manufacturing functions but records show operators fifteen months past their last completion, the gap is a direct nonconformity. eLeaP’s real-time compliance dashboard closes this gap continuously: the training matrix defines requirements, the LMS enforces them, and the compliance dashboard reflects actual training status against defined requirements in real time — not just at audit preparation time.

Medical Device Training LMS: Frequently Asked Questions

What does the QMSR require for training documentation, and how does it differ from the legacy QSR?

The QMSR, effective February 2026, replaced 21 CFR Part 820 and aligns US device quality requirements with ISO 13485:2016. For training specifically, the QMSR introduces three requirements that go beyond the legacy QSR’s §820.25: formal competency determination specifying the education, skills, and experience required for each quality-affecting function; documented effectiveness evaluation confirming that training produced the intended competency; and maintenance of records spanning education, training, skills, and experience — not just training completion logs. Manufacturers who were operating under legacy QSR without ISO 13485 alignment and who have not updated their training programs to reflect these requirements are now operating out of compliance.

How does ISO 13485 Clause 6.2 apply to medical device training records?

ISO 13485 Clause 6.2 requires that device manufacturers determine necessary competencies for quality-affecting functions, provide training to achieve and maintain those competencies, evaluate training effectiveness, ensure personnel awareness of their quality contributions, and maintain records of education, training, skills, and experience. These requirements apply to all functions affecting product quality — manufacturing operators, quality engineers, design control personnel, complaint investigators, regulatory affairs professionals, and anyone else whose work directly influences device quality or regulatory compliance. The QMSR adopts Clause 6.2 as its training requirements framework, making these obligations enforceable by FDA as well as by notified bodies conducting ISO 13485 certification audits.

How should device manufacturers handle training records for personnel involved in design control activities?

Design control personnel must be trained on the design control procedure and on the specific methodologies they employ in verification and validation activities. Training records for design control personnel are part of the DHF and are reviewed during regulatory submissions and inspections. Version-specific training records covering the full development timeline must be maintained — when the design control procedure is revised, retraining must be documented against the new version before personnel continue design control activities. For software-intensive devices, personnel working under IEC 62304 must have training records covering the software development lifecycle procedures governing their activities, with those records available as part of the software technical file.

What training records are required for personnel performing complaint investigations and MDR evaluations?

Personnel performing complaint investigations and MDR reportability determinations must be trained on the complaint handling procedure, the MDR reporting criteria under 21 CFR Part 803, and any internal decision frameworks the organization uses for reportability assessments. Training records should document not just procedure completion but demonstrated understanding of regulatory criteria — typically through a formal assessment. When complaint handling procedures are revised, all complaint investigation personnel must be retrained on the revised procedure before performing evaluations, with version-specific completion records maintained. The qualification basis for MDR evaluation personnel is particularly scrutinized because reportability decisions have direct regulatory consequences.

How does the QMS+LMS integration apply to medical device CAPA programs under the QMSR?

Under the QMSR’s CAPA requirements, corrective actions must be implemented and verified for effectiveness. When a CAPA identifies training as a root cause, the corrective action requires documented retraining with effectiveness verification before closure. In eLeaP’s integrated system, CAPA records in the QMS generate training assignments in the LMS automatically when retraining is designated as a corrective action — linked to the specified job functions, current procedure version, and CAPA record number. The CAPA cannot be submitted for closure until training completion and effectiveness verification documentation are confirmed. For manufacturers under FDA scrutiny where CAPA program credibility is directly at issue, this system-enforced closure dependency is a compliance control, not an administrative convenience.

What validation documentation does a device manufacturer need for their LMS under the QMSR?

The QMSR requires that computer software used as part of the quality management system be validated. An LMS managing training records that are QMS records falls within this scope. Required validation documentation includes a User Requirements Specification, a risk assessment, IQ/OQ/PQ qualification protocols and reports, a Validation Summary Report, and an ongoing change control process for software updates. All validation documentation must be retained as quality records for the operational lifetime of the system. eLeaP provides a validation documentation package — protocol templates, functional specifications, SDLC documentation, and change notification processes — to support device manufacturer validation activities under the QMSR framework.

How should training records be structured to support device history record requirements?

DHR-supporting training records must be retrievable by lot and manufacturing date: for any device unit or lot, the records must confirm that all operators performing quality-affecting manufacturing steps were trained on the current procedure versions at the time of manufacture. This requires version-specific completion data with timestamps, immutable archiving for point-in-time compliance reconstruction, and linkability to production records identifying which operators performed which steps. eLeaP’s historical compliance reporting supports DHR-linked queries: point-in-time training status is reconstructable for any operator on any date, with version references and audit trail integrity preserved for the full retention period.

The Medical Device Training Infrastructure That Holds Up to QMSR and Notified Body Scrutiny

Device manufacturers managing training records in spreadsheets, unvalidated LMS platforms, or systems without competency documentation and effectiveness evaluation infrastructure are producing quality records that do not meet current QMSR requirements. The consequence is not just an audit finding — it is a quality system deficiency that calls into question the integrity of every device manufactured by personnel whose competency cannot be demonstrated to the standard the regulation now requires.

eLeaP’s medical device training LMS provides the infrastructure that QMSR and ISO 13485 Clause 6.2 compliance actually demands: competency-based training matrices with effectiveness evaluation workflows, CAPA-to-training automation through native QMS integration, version-specific DHR-linked completion records, validated system architecture with full audit trail documentation, and notified body-ready compliance reporting.

Request a demo to see how eLeaP manages medical device training compliance — from design control qualification through CAPA closure — in a quality system built for current QMSR and ISO 13485 requirements.