The FDA’s Quality Management System Regulation (QMSR) took effect on February 2, 2026, and it changed the record a diagnostics team has to produce. That rule amends 21 CFR Part 820 and incorporates ISO 13485:2016 by reference. It also retires the design control structure most medical device teams built their workflows around.
Teams moving a research use only (RUO) product toward a cleared in vitro diagnostic (IVD) submission now build evidence against a structure that postdates their programs. The research phase is still where the data that carries a submission comes from, and in our experience it’s where teams quietly decide how expensive the transition will be. This guide covers what 21 CFR 809.10 exempts, how the US and EU draw the line, and what carrying the record into a cleared IVD takes.
What Is Research Use Only (RUO)?
Research use only is a narrow FDA exemption that lets a diagnostic product sit outside most IVD obligations while it’s genuinely still in research. The RUO statement comes from 21 CFR 809.10(c)(2)(i), which makes a qualifying shipment exempt from IVD labeling requirements in paragraphs (a) and (b) when three conditions hold at once. A qualifying product must be in the laboratory research phase of development, cannot be represented as an effective IVD, and must carry labeling that prominently bears the statement “For Research Use Only. Not for use in diagnostic procedures.” Miss any one and the exemption falls away.
The labeling detail runs the other way from what most teams expect. Paragraph (c) lifts the requirements in 809.10(a) and (b), which is where net quantity, manufacturer identity, and the lot-or-control-number requirement live. An accurate quantity statement and the manufacturer’s name and place of business still attach to any device in package form, under section 502(b) of the Federal Food, Drug, and Cosmetic (FD&C) Act. Most manufacturers keep lot control as a traceability practice rather than an 809.10 obligation.
How RUO Products Differ From Cleared IVDs
An RUO product and a cleared IVD sit further apart than the labeling difference suggests. The RUO designation covers reagents and instruments along with the software and test systems built around them, so long as the work stops short of diagnosis. The table sets the two side by side across the dimensions that matter.
| Dimension | RUO Product | Cleared IVD |
| Intended use | Laboratory research phase only, no clinical diagnosis or patient management | Clinical diagnosis and patient management within the cleared intended use |
| Labeling | RUO statement, with the 809.10(a) and (b) requirements lifted | Full labeling per 21 CFR 809.10(a) and (b), including intended use, performance, and warnings |
| Premarket review | Not required | Required via 510(k), De Novo, or premarket approval (PMA) |
| Quality management system | Not required under 21 CFR Part 820 | Required, including design and development controls under ISO 13485 Clause 7.3, across the product lifecycle |
| Clinical claims | None permitted | Permitted within the cleared scope |
| Post-market obligations | Outside Medical Device Reporting (MDR), corrections, and removals | MDR, corrections and removals, and surveillance apply |
Where RUO Products Fit in Diagnostic Development
RUO products earn their place where a clinical claim would be premature and the work is still characterizing performance. Early assay development and biomarker discovery both qualify. Two settings bear more directly than the rest on what the transition later costs:
- Laboratory-developed test (LDT) component supply: Reference laboratories use RUO components inside LDTs they validate themselves, and as of August 2026 that work sits under Clinical Laboratory Improvement Amendments (CLIA) oversight, not FDA device review. The laboratory carries responsibility for the finished test, so the RUO label correctly reflects the component maker’s narrower scope.
- Analytical method development: Method development teams pick antibody pairs, characterize interference, and probe matrix effects before analytical validation begins. RUO tools carry the right claim because the specifications are still being written.
That CLIA boundary is newer than it looks. FDA’s May 2024 rule treating laboratories as device manufacturers was vacated in March 2025, and FDA reverted 21 CFR 809.3(a) effective September 2025. Used deliberately, both settings produce data that holds up when the product carries a clinical claim.
Why the RUO Exemption Is Narrower Than the Label Suggests
RUO products do sit outside most regulatory controls, and FDA says so directly, though none of that relief comes from the label. Premarket review, the Part 820 quality management system requirements, and post-market reporting all fall away.
That relief follows from the absence of a diagnostic intended use, not from the carton. What 21 CFR 809.10(c) exempts is a shipment, and only from the labeling requirements in paragraphs (a) and (b) and a part 861 standard. Putting an RUO label on a product exempts it from nothing else.
In the EU, falling outside the In Vitro Diagnostic Regulation (IVDR) does not put a product outside EU law, so the exclusion is not a blanket pass.
Technical support is where the line tends to blur, and FDA has drawn it explicitly. Generic maintenance and software updates for an RUO product stay inside the research frame. Support for performing clinical validation at a clinical laboratory is listed as evidence of a conflicting intended use. That is the evidence FDA builds a case on.
What Triggers FDA Enforcement
Enforcement turns on the commercial record around the label. Agena Bioscience’s Director of Regulatory and Quality told FDA investigators that the firm markets its MassARRAY4 System as research use only and sells it to both research and clinical diagnostic companies. Distribution records and a customer list obtained during the inspection showed shipments to clinical testing laboratories. In March 2024 FDA concluded that the RUO disclaimers on the MassARRAY4 System and the iPLEX HS Colon Panel were inconsistent with that evidence.
DRG Instruments’ website did the work for the investigators a year later. FDA quoted clinical applications on the firm’s website, including “Diagnosis of systemic/local conditions,” “Obstetrics & Gynecology” and “Drug Monitoring.” Customer records showed the Salivary Cortisol ELISA RUO going to multiple companies in the business of performing clinical analysis. In both cases the RUO statement sat where it belonged, and the rest of the commercial record carried the product across the line.
Both letters point at the same exposure, and the cost runs well past relabeling. Consequences can include seizure, injunction, civil money penalties, and pressure to pursue a 510(k) or PMA before further distribution.
How the RUO Regulatory Framework Works in the US and EU
FDA weighs the label against the commercial record and can act when the two disagree. IVDR works from a scope question instead, asking whether a manufacturer specifically intended the product for in vitro diagnostic examination.
How the FDA Evaluates Objective Intent
FDA applies an objective-intent standard, weighing the label against the sales record and the support content. During an inspection investigators pull distribution records, customer lists, and the firm’s website as it stood, then compare that pattern to the claim on the carton. If the evidence contradicts the label, FDA can treat the product as misbranded under section 502 of the FD&C Act and adulterated under section 501.
How EU IVDR 2017/746 Treats RUO Products
IVDR applies to products intended for a medical purpose. Article 1(3)(a) puts products for general laboratory use or research-use-only products outside the Regulation, unless those products, in view of their characteristics, are specifically intended by their manufacturer for in vitro diagnostic examination. Performance studies are a different matter, because Article 1(1) states the Regulation applies to them too, under separate requirements. Article 2(45) draws the practical line, providing that a device intended for research purposes, without any medical objective, is not a device for performance study.
A product that stays inside the scope exclusion does not need CE marking under IVDR. Medical Device Coordination Group (MDCG) guidance puts it plainly. A product intended for research use only cannot be intended by its manufacturer for a medical purpose. The conduct rule sits in the Regulation itself, where Article 7 prohibits labeling or advertising that creates a false impression about diagnosis or suggests uses outside the stated purpose.
How to Transition an RUO Product Into an IVD
A product has to leave RUO status when its intended use shifts into clinical diagnosis, or when the way it sells implies that shift. The move gets cheaper the earlier the design record opens, long before a relabeling push meets reviewers asking for missing records.
The path from RUO to a commercial IVD may include an investigational stage. As development moves from laboratory research into product testing or clinical investigation, IUO labeling or applicable IDE requirements may apply before the product is cleared, authorized, or approved for clinical use.”
Open the Design Record Before Investigational Work
The design and development record opens right after feasibility, before any investigational studies begin, under ISO 13485 Clause 7.3. Starting the Clause 7.3.10 design and development file early captures inputs, outputs, verification, validation, and reviews as they happen, with authors and dates. Back-filling that file close to submission, the record most teams still call the Design History File, is a pattern auditors know. A record reconstructed from memory reads differently from one built as the work happened.
Why the QMSR Timing Decides Your Documentation Load
Building to the QMSR from the start avoids a second round of documentation work later and keeps the program compatible with EU markets. Design and development requirements now sit at 820.10(c), which points to ISO 13485 Clause 7.3 and its subclauses. Teams already certified to ISO 13485:2016 still carry FDA-specific additions such as Unique Device Identification (UDI), among others.
Which Submission Pathway Fits the Device
The submission pathway follows from the device’s classification. Most Class II IVDs clear through 510(k) against a cleared predicate. A novel IVD with no legally marketed predicate uses the De Novo pathway instead.
De Novo asks FDA to classify the device into Class I or Class II, where general controls, or general and special controls, give reasonable assurance of safety and effectiveness. Class III IVDs require PMA under section 515, supported by valid scientific evidence that normally covers analytical and clinical performance. Analytical studies built to recognized Clinical and Laboratory Standards Institute (CLSI) documents give reviewers a familiar design.
Why Traceability Breaks Down During Transition
A quality engineer at an IVD company pulls the verification record for a design input written in the RUO phase. The input is in a spreadsheet and the protocol is in a shared drive. Nobody has reconciled them since the author left. Nobody did anything wrong, and the record still drifted from the product it describes, which now has to be reconstructed under submission pressure.
Research-phase documentation holds up until a regulated submission asks for a single, current, reviewable chain from user need through verification and validation evidence. A requirements traceability matrix links design inputs to verification and validation in one view. Teams managing that chain in disconnected files carry a compounding burden, since every design change forces manual updates.
How Jama Connect Supports RUO-to-IVD Transition
When design inputs, risk items, verification records, and change history live in separate systems, the chain a reviewer expects gets stitched together by hand. Design transfer slows too, because production specs can’t be tied back to the validated design.
Jama Connect® is a web-based requirements management and traceability platform for regulated product development. Its medical device and life sciences framework covers diagnostics explicitly, including LDTs and RUO products, aligned to ISO 13485. When an upstream requirement changes, every downstream artifact that traces to it is flagged as suspect. The owner either updates it or clears the flag and records the assessment. Design review then starts from a record that is already current.
Treating Research Use Only as a Structured Program Phase
The exemption is narrower than the carton suggests, and the record built during research decides whether the transition costs a review cycle or a program. If that record still lives in spreadsheets and lab notebooks, you can start a free trial today and see the alternative on your own data.
Frequently Asked Questions About Research Use Only
Can an RUO product be sold to clinical laboratories?
Selling to clinical labs isn’t automatically a problem. It becomes one when the surrounding conduct points to clinical use, through promotional material, clinical support, or a customer book of clinical analysis companies. The Agena and DRG warning letters turned on exactly that combination of evidence.
When does an RUO product need to transition to an IVD?
Once commercial behavior, marketing copy, or support practice implies clinical use, the product is on the wrong side of the RUO line, updated carton or not. Building the design and development record, risk records, and traceability during the RUO phase costs far less than reconstructing them for the submission.
How does the QMSR affect RUO-to-IVD transition plans?
The QMSR amends 21 CFR Part 820 rather than replacing it, and incorporates ISO 13485:2016 by reference. For a transition plan that means the design and development record has to satisfy ISO 13485 Clause 7.3 rather than the now-Reserved 820.30. A team already certified to ISO 13485:2016 still has FDA-specific requirements layered on top: UDI under Part 830, MDR under Part 803, device tracking under Part 821, and corrections and removals under Part 806.
Can a product be research use only in the US and regulated in the EU?
Yes, though the label is not what settles it in either place. Both regimes read intent from the whole commercial record, so a single global label paired with region-specific promotion can hold in one jurisdiction and fail in the other. Intended-use statements and distributor training have to say the same thing everywhere the product ships.
