The Lesson: A Classification Order Is a Design Input
When FDA codifies a classification, special controls stop being one company's negotiated conditions and become the published bar for every future submitter. That is the right way to read the Federal Register document published on October 9, 2026 (document number 2026-20726), which classifies the infant pulse rate and oxygen saturation monitor for over-the-counter (OTC) use into class II with special controls.
If you make, or plan to make, a consumer-facing infant monitor that reports pulse rate or oxygen saturation, the special controls in that order belong in your design inputs now, not after your first submission goes sideways.
This article walks through what the order does, how it changes your regulatory path, and how to map the special controls to a quality management system built on ISO 13485:2016. This article does not reproduce the codified text or name the originating de novo request and product code, so treat the Federal Register document as the controlling source and confirm the effective date and exact special-control language there before you act.
What Did FDA Actually Classify?
FDA classified the infant pulse rate and oxygen saturation monitor for over-the-counter use into class II (special controls). The agency's stated rationale is that class II provides a reasonable assurance of safety and effectiveness for the device type, and that general controls alone would not be enough. The special controls are identified in the order and will be part of the codified language for the classification.
A few points are worth anchoring before going further:
- The device type is OTC. The classification addresses monitors intended for use by parents and caregivers without a clinician directing the use. That intended use is what drives most of the special controls, because the user is a lay person interpreting numbers about a baby.
- It sits in the cardiovascular devices panel. The title of the order is "Medical Devices; Cardiovascular Devices; Classification of the Infant Pulse Rate and Oxygen Saturation Monitor for Over-the-Counter Use."
- It is a classification, not a guidance document. The special controls will be codified in the Code of Federal Regulations as part of the classification regulation, so they are regulatory requirements for the device type rather than optional recommendations.
The statutory basis for this type of action is section 513(f)(2) of the Federal Food, Drug, and Cosmetic Act, the de novo pathway for novel low-to-moderate risk devices with no legally marketed predicate. A device that is automatically class III under section 513(f)(1) can be reclassified through de novo into class I or II, and once FDA grants the request and later publishes the classification, the device type becomes available as a predicate.
Why Does the De Novo-to-Classification Step Matter?
Most people focus on the de novo grant and treat the later Federal Register notice as paperwork. That undersells it. Before the order, a competitor had to either file its own de novo request or argue a predicate relationship that FDA might not accept for an OTC infant monitor. After the order, the device type has a codified classification and a defined set of special controls, which is the foundation for a 510(k) under 21 CFR Part 807, Subpart E.
Here is how the path changes:
| Question | Before classification | After classification (class II, special controls) |
|---|---|---|
| Typical premarket route | De novo request, or a 510(k) with a hard-to-defend predicate | 510(k) against the classified device type |
| What defines acceptable performance | Whatever FDA negotiated in an individual decision | Codified special controls, public to all |
| Predicate availability | Limited to the original authorized device and any that followed | The classified device type can be cited as a predicate in a 510(k) |
| Main risk for new entrants | Uncertainty about what FDA will ask for | Failing to demonstrate each special control |
| Where your effort goes | Making the case for the device | Documenting conformance to a known list |
A 510(k) must demonstrate substantial equivalence to a legally marketed predicate under section 513(i) of the FD&C Act. Because special controls will apply to this device type, confirm in the order what evidence FDA expects for each one. The classification makes the target clearer, which is good news, but it also removes the excuse of ambiguity. If you want a refresher on how the premarket notification process connects to your quality system, our page on FDA 510(k) submissions covers the fundamentals.
What Will the Special Controls Likely Cover?
The exact special controls are in the order, and this article does not restate them. The themes below are illustrative only. They reflect what special controls for OTC physiological monitors commonly address, not the order's text, and they may differ from it. Use them to prepare questions for reading the order, not as a list of requirements.
Illustrative themes, not the order's list:
- Clinical or performance data. Evidence that the device measures pulse rate and oxygen saturation accurately in the intended population, which for infants raises sensor fit, motion, skin perfusion, and skin pigmentation questions.
- Non-clinical performance testing. Bench testing of sensor accuracy, alarm or notification behavior, battery and wireless performance, and environmental conditions of home use.
- Software verification and validation. Documentation of the software that processes the signal and presents readings or notifications, including the behavior of any algorithm that decides when to alert a caregiver.
- Electrical, thermal, and mechanical safety. Conformance to recognized consensus standards, typically IEC 60601-1 for basic safety and, for pulse oximeter equipment, ISO 80601-2-61.
- Human factors and usability. Validation that lay users can place the sensor, read the output, and respond correctly, which is where IEC 62366-1 comes in.
- Labeling. Clear statements of intended use, limitations, and what the device is not for, written for a parent rather than a clinician.
That last category deserves attention. An OTC infant monitor creates a specific hazard that has little to do with sensor physics. A parent may treat a reassuring reading as clearance to stop watching their child, or treat a false alarm as a reason to stop trusting the device. Both failure modes are use-related, and both belong in your risk file.
When you read the order, build a simple traceability table with three columns: the special control as written, the design output or test report that satisfies it, and the quality record that proves it was controlled. That is the same discipline you already apply under design controls.
How Does This Fit With the Quality Management System Regulation?
Timing matters here. FDA's Quality Management System Regulation, which amended 21 CFR Part 820 to incorporate ISO 13485:2016 by reference, took effect on February 2, 2026. So a manufacturer entering this device type today is doing so under a Part 820 that is already aligned with ISO 13485. That is helpful, because the special controls and the QMS requirements reinforce each other.
The mapping below is our interpretation of how common themes line up with ISO 13485:2016, not language from the order:
| Special-control theme | Relevant ISO 13485:2016 clause | What an auditor or FDA reviewer will look for |
|---|---|---|
| Performance and clinical evidence | 7.3.6 Design and development verification, 7.3.7 Validation | Protocols approved before testing, with acceptance criteria tied to design inputs |
| Software V&V | 7.3.2 Planning, 7.3.6 Verification, 7.3.7 Validation | Software lifecycle records tied to design verification and validation |
| Safety standards conformance | 7.3.3 Design inputs | Standards identified as inputs, with test reports as outputs |
| Human factors | 7.3.7 Validation, 7.1 Planning of product realization | Use-related risks identified and validated with representative lay users |
| Labeling | 7.3.4 Design outputs, 4.2.4 Control of documents | Labeling treated as a design output, controlled as a document, with change control and review |
| Risk management | 7.1 with ISO 14971:2019 | Hazards, hazardous situations, and risk controls traced to design |
Clause 7.3.3 of ISO 13485:2016 requires design and development inputs to include applicable regulatory requirements. Under Part 820 as amended, labeling and packaging are also addressed directly in the device labeling and packaging controls provision (21 CFR 820.45), so label content and handling should be controlled there as well as through document control. A codified special control is precisely that kind of regulatory requirement. If your design input document does not list it, an auditor has a straightforward finding to write.
If your design history is not yet organized around this, our overview of design controls for medical devices is a good place to start.
What Should Existing Manufacturers Do Right Now?
If you already market an OTC infant pulse oximeter or similar monitor, the classification order may touch you in a different way than it touches a new entrant. Work through these steps in order.
1. Read the order and confirm the dates
Find the effective date in the Federal Register document, and note whether it sets any compliance deadline for devices already on the market. Do not assume. Put the date, the document number (2026-20726), and the publication date (October 9, 2026) in your regulatory tracking file.
2. Confirm your current regulatory status
Pull your marketing authorization, whether that is a de novo grant, a 510(k) clearance, or something else, and check that your device matches the classified device type, including the OTC intended use. A prescription-use infant oximeter used in hospitals is a different device type with different controls. If your product straddles both, be precise about which indication each model carries.
3. Run a gap assessment against each special control
Take the list from the order and mark each item as met with objective evidence, partially met, or not met. Be honest about partial. A test report that covered adult fingertip sensors does not demonstrate infant performance, and a usability study with clinicians does not demonstrate lay-user validation.
4. Update the risk management file
Reconcile your ISO 14971 file with the special controls. Any hazard the order names should appear in your hazard analysis with a traceable control. Our article on integrating ISO 14971 with ISO 13485 explains how to keep the risk file connected to design and production records.
5. Check labeling and marketing claims
OTC labeling must be written for lay users, and claims about what the device does need to match the cleared or authorized intended use. Marketing language that implies the device prevents or predicts a medical event is a classic way to turn a class II device into a regulatory problem. Review your website, app store listing, and packaging against the intended use statement.
6. Plan for post-market obligations
Class II devices remain subject to Medical Device Reporting under 21 CFR Part 803, corrections and removals reporting under 21 CFR Part 806, and establishment registration and listing under 21 CFR Part 807. For an infant oximeter, define complaint categories in advance: false alarms, missed alarms, inaccurate readings, sensor skin irritation or burns, loose or detached sensors, and app notification failures. A missed alarm or inaccurate reading linked to a death or serious injury is a potential MDR trigger under Part 803. For a consumer product, complaint handling is where you will feel the load. Parents will contact you at 3 a.m. about alarms, and each of those contacts is a potential complaint record under Part 820 as it now reads, and under clause 8.2.2 of ISO 13485:2016.
What Should New Entrants Do Differently?
If you are earlier in development, the order is a gift of contrast. You now know what the finish line looks like, which is not something earlier entrants could say. The best use of that is to write the special controls into your design input document on day one and build your verification plan backward from them.
A few practical suggestions:
- Choose the predicate carefully. Substantial equivalence turns on intended use and technological characteristics. For an OTC infant monitor, differences in sensor location, wireless architecture, or algorithmic alerting can raise new questions of safety and effectiveness, so identify them early.
- Budget for infant-specific evidence. Adult performance data will not carry over. Plan for the population your labeling names.
- Treat software as a core deliverable. If the product is a sock, a band, or a clip paired with a phone app, the app is part of the device or its accessory, and its lifecycle records need to be as thorough as the hardware. See our guide to software validation under ISO 13485 and IEC 62304 for how those pieces fit.
- Engage FDA early. A Pre-Submission meeting is the cleanest way to test your plan against the special controls before you commit to a study.
Startups often ask whether they need ISO 13485 certification to file a 510(k). You do not need a certificate to submit, but with the QMSR now in force you do need a quality system that meets the requirements of Part 820, and building it on ISO 13485 is the most direct way to get there. For an infant monitor, make sure that system already covers alarm-related complaint handling and use-related risk files before your first units reach homes.
What Are the Common Mistakes With a New Class II Device Type?
These problems tend to recur whenever FDA publishes a new classification.
The first is treating the special controls as a checklist to be satisfied at the end of development. They are design inputs, and testing done before they are understood often has to be repeated.
The second is relying on standards conformance as a substitute for a rationale. Citing ISO 80601-2-61 or IEC 60601-1 shows you tested against the standard. It does not show that the test addresses the hazards of a baby wearing the device overnight at home.
The third is weak control of the sensor supply chain. A sensor or optical component that changes without change control can shift accuracy in ways your verification no longer covers. Supplier qualification under clause 7.4 of ISO 13485:2016 and change control under clause 7.3.9 are where that gets caught.
The fourth is ignoring the difference between a number and a decision. A parent does not read a saturation percentage the way a clinician does. If your usability validation does not include realistic scenarios, such as a low reading at night with a sleeping baby, you have not validated the use that matters.
What Does a Published Target Change?
One classification is too little to infer a broader FDA direction, so this article does not try to. What the order does provide is a published set of special controls for this device type.
For manufacturers, that predictability is the real opportunity. A known list of special controls is something a quality system can be built around, and it is easier to defend an audit finding when your design inputs already cite the regulation.
Where does your own file stand today? If you cannot trace each special control to a specific test report and a specific controlled document, that is the first place to look.
If you would like a second set of eyes on a gap assessment, you can reach me through Certify Consulting.
Last updated: 2026-10-21
Frequently Asked Questions
What did FDA do with the infant pulse rate and oxygen saturation monitor for OTC use?
FDA classified the device type into class II (special controls) in a Federal Register order published October 9, 2026 (document 2026-20726). The agency determined that class II, with the special controls identified in the order, provides a reasonable assurance of safety and effectiveness.
Do I need a 510(k) for an OTC infant pulse oximeter now?
In general, a class II device type with special controls that is not exempt is brought to market through a 510(k) under 21 CFR Part 807, Subpart E. Check the order and the codified regulation for any exemption language, and confirm your intended use matches the classified device type.
How do the special controls relate to ISO 13485?
Clause 7.3.3 of ISO 13485:2016 requires design inputs to include applicable regulatory requirements, so each codified special control should appear in your design input document. Verification and validation under clauses 7.3.6 and 7.3.7 then produce the evidence that each one is met.
Is the Quality Management System Regulation relevant to this device?
Yes. The QMSR amended 21 CFR Part 820 to incorporate ISO 13485:2016 by reference and took effect on February 2, 2026. Manufacturers of this device type are expected to operate a quality system that meets it.
Where can I find the exact special controls and effective date?
Both are in the Federal Register document at federalregister.gov under document number 2026-20726. Always rely on that text rather than a summary, including this one, when writing your design inputs.
Jared Clark
Principal Consultant, Certify Consulting
Jared Clark is the founder of Certify Consulting, helping organizations achieve and maintain compliance with international standards and regulatory requirements.