Quick Answer
FDA's QMSR governs medical device quality system requirements, while eSTAR is FDA's electronic submission template and resource for device submissions. They are different programs, but eSTAR-ready submissions depend on controlled quality records such as design, risk, verification, validation, labeling, software, sterilization, biocompatibility, and manufacturing evidence.
Key Takeaways
- QMSR is a quality system regulation. eSTAR is a submission preparation resource.
- eSTAR does not replace the need for controlled device quality records.
- Device teams should connect design controls, risk management, testing, validation, and labeling evidence to submission sections early.
- The best workflow is not "export QMS into eSTAR." It is "map approved evidence to the regulatory questions eSTAR helps organize."
- Medical device QMS records become more valuable when they are connected to regulatory submission readiness.
- Device companies often treat quality work and FDA submission work as separate phases. That breaks down quickly. A 510(k), De Novo, or PMA submission depends on records created during quality and product development.
- QMSR and eSTAR are not the same thing. QMSR defines quality system expectations for device manufacturers subject to Part 820. eSTAR helps structure electronic device submissions. The bridge between them is controlled evidence.
- The bridge matters more after the QMSR effective date because device teams need to understand both quality-system execution and submission evidence. FDA's QMSR page states that the amended Part 820 became effective on February 2, 2026 and incorporates ISO 13485:2016 by reference. FDA's eSTAR page separately describes the electronic template and resource used for medical device submissions. A team can use eSTAR correctly and still have weak evidence if its design, risk, verification, validation, labeling, software, or manufacturing records are incomplete.
What QMSR Covers
FDA's QMSR became effective on February 2, 2026 and incorporates ISO 13485:2016 by reference, with additional FDA requirements in Part 820.
For device teams, QMSR affects the quality system used to control processes and records such as:
- Design and development
- Risk management linkage
- Documented procedures and records
- Purchasing and supplier controls
- Production and process controls
- Corrective and preventive action
- Complaint handling
- Control of nonconforming product
- Record controls
The regulation is not a submission template. It is the quality system foundation behind the records a submission may rely on.
For submission readiness, QMSR should push teams to ask whether their quality records are complete, controlled, retrievable, and connected to the device story. The submission writer should not have to reconstruct the design history from disconnected folders. The regulatory lead should not have to guess whether a test report is final, whether a risk control was verified, or whether a labeling change was approved.
What eSTAR Covers
eSTAR is FDA's electronic Submission Template And Resource for medical device submissions. It guides submitters through structured content for applicable device submission types.
Depending on the submission type and current template, eSTAR may organize information related to:
- Administrative details
- Device description
- Indications for use
- Predicate or comparator information, where applicable
- Risk and performance information
- Software documentation, where applicable
- Biocompatibility, sterilization, shelf life, electrical safety, EMC, and other testing, where applicable
- Labeling
- Summary and statement content
Teams should always use the current FDA eSTAR page and template for their submission type.
FDA has also updated eSTAR over time, including alignment with QMSR for relevant templates in 2026. That means teams should not rely on a stale local copy of a template or a prior submission package. Submission preparation should start with the current FDA source and then map each required answer back to controlled evidence.
Why Quality Records Drive Device Submissions
The submission is only as good as the evidence behind it.
| Quality Record | Submission Relevance |
|---|---|
| Design inputs and outputs | Device description, intended use, requirements traceability |
| Risk management file | Hazard analysis, mitigation, verification evidence |
| Verification and validation reports | Performance testing and design validation support |
| Software documentation | Software level of concern, architecture, testing, cybersecurity evidence where applicable |
| Biocompatibility assessment | Patient-contacting material safety support |
| Sterilization validation | Sterile device evidence |
| Shelf-life and packaging validation | Aging, package integrity, and storage support |
| Labeling controls | Instructions, warnings, claims, indications, and consistency |
| Complaint and CAPA records | Postmarket, corrective, or lifecycle context when relevant |
eSTAR can structure the answer. QMS records provide the defensible support.
The Evidence Map Device Teams Need
Before drafting, teams should build an evidence map that connects eSTAR sections to source records.
| eSTAR Area | Typical Source Evidence |
|---|---|
| Device description | Design outputs, drawings, BOM, specifications, configuration records |
| Indications and intended use | Labeling controls, user needs, clinical or performance rationale |
| Risk and performance | Risk management file, verification and validation reports, design review records |
| Software | Software requirements, architecture, hazard analysis, verification, validation, cybersecurity evidence |
| Sterilization and shelf life | Sterilization validation, packaging validation, aging studies, environmental controls |
| Biocompatibility | Biological evaluation plan, test reports, material characterization |
| Labeling | Approved labels, IFU, warnings, claims review, translation controls where relevant |
| Manufacturing | Process validation, supplier qualification, production controls, inspection records |
| Substantial equivalence | Predicate comparison, performance summaries, design comparison, labeling comparison |
The map should identify the record owner, approval status, revision, and any open gap. This keeps eSTAR writing from becoming a last-minute document hunt.
QMSR Does Not Mean "Submit the QMS"
A common misunderstanding is that because QMSR governs the quality system, the submission should contain broad QMS evidence. That is usually not the right frame.
The submission should contain the information required or appropriate for the specific submission type. Quality records support that information. Some records may be directly attached, some may be summarized, and some may remain available for inspection or internal traceability.
The key is to avoid two extremes:
- Under-documenting the submission because "the QMS has it somewhere."
- Overloading the submission with raw quality records that do not answer the review question.
The strongest approach is controlled, section-specific evidence.
Device Change Readiness
For device lifecycle work, QMSR-to-eSTAR readiness is not limited to original submissions. Design and labeling changes can require a documented decision about whether a new 510(k), Special 510(k), PMA supplement, or other regulatory action is needed.
FDA's device change guidance focuses on whether a change could significantly affect safety or effectiveness or introduce a major change in intended use for 510(k)-cleared devices. Software changes have their own specific guidance. That means the QMS change record should contain enough context for regulatory to assess the change:
- What changed in the device, software, labeling, material, manufacturing process, or risk control?
- Which marketed or pending device configurations are affected?
- Does the change affect intended use, indications, safety, effectiveness, performance, risk, or cybersecurity?
- What verification, validation, or risk evidence supports the conclusion?
- Is a new submission needed, and if not, where is the rationale documented?
This change decision should be traceable to the quality evidence. If a later eSTAR submission uses the changed evidence, the submission team should be able to see the change-control history behind it.
Submission Readiness Workflow
Use this workflow before eSTAR drafting begins:
- Define the submission type and current FDA template.
- Map each eSTAR section to required source evidence.
- Confirm each evidence record is approved and version controlled.
- Resolve open design, risk, test, validation, and labeling gaps.
- Run regulatory review against claims, indications, and performance evidence.
- Keep traceability from eSTAR responses back to source quality records.
This avoids late-stage scrambling when the regulatory writer discovers that evidence is still draft, inconsistent, or not linked.
Common Gaps That Delay eSTAR Work
Design Evidence Is Not Version Aligned
The device description, drawings, labeling, risk file, and verification reports must describe the same device configuration. If the design output revision does not match the test report or labeling, the submission team has a credibility problem.
Risk Controls Are Not Traceable
Risk management cannot sit apart from verification and validation. If a risk control is claimed, the evidence map should show where that control was implemented and verified.
Software Evidence Is Treated Too Late
Software documentation can be one of the most time-consuming parts of device submission preparation. Requirements, architecture, testing, anomalies, cybersecurity, and release evidence should be controlled before eSTAR writing begins.
Labeling Claims Are Ahead of Evidence
Marketing or clinical claims must be supported by the intended use, indications, performance evidence, and risk controls. Labeling review should happen alongside evidence mapping, not after submission assembly.
Manufacturing Evidence Is Too Generic
For devices where manufacturing process, sterilization, packaging, shelf life, or supplier controls matter to safety and effectiveness, the submission package needs evidence specific enough to support the device and configuration.
How Assyro Fits
Assyro helps device teams organize submission evidence and connect it to quality context. Teams can map controlled quality records to eSTAR sections, surface missing approvals, preserve traceability from submission answers back to source records, and make regulatory impact assessment visible during device change control.
QMSR compliance still depends on the manufacturer's quality system, procedures, implementation, training, and validation context. Assyro helps teams make the evidence easier to find, review, and reuse for FDA device submissions.
The practical benefit is less manual reconstruction when submission teams need approved device quality evidence.
Related Reading
- eSTAR submission software guide
- 510(k) submission guide
- De Novo submission guide
- PMA submission guide
- Medical device QMS software guide
No. QMSR and eSTAR are separate. QMSR governs quality system requirements. eSTAR is an FDA submission template resource.
References
This guide is for device submission readiness planning and is not legal or regulatory advice.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.
See Assyro in action
Catch eCTD and eSTAR errors before your FDA review cycle.
Book a 20-minute demo this week. We'll validate a sample of your submission live and show you exactly where Assyro catches what your current QC misses.