Classified in 2011. Excluded in 2016.

Product code OUG still sits in FDA’s classification database, Class I, 510(k)-exempt, reviewed by the General Hospital panel. Nothing about the entry looks stale. What it actually covers has shrunk twice since the regulation was written, and neither shrinkage changed a word of the database record a portfolio search returns today.

The category FDA built in 2011

FDA finalized the medical device data system rule on February 15, 2011, moving a category that had been regulated as Class III — premarket approval, by default, for lack of any lower classification — down to Class I under 21 CFR 880.6310. The identification language covered any device, hardware or software, intended to transfer, store, convert format, or display medical device data without controlling or altering the function of the device it connected to. FDA’s reasoning at the time was narrow: general controls were enough because the only risk this category of product posed was getting the data handling itself wrong, not altering a therapy or a diagnosis.

The statute that mooted half of it

Congress reached the same category from a different direction five years later. The 21st Century Cures Act, Section 3060(a), added Section 520(o) to the FD&C Act — 21 U.S.C. § 360j(o) — listing categories of software Congress excluded from the statutory definition of “device” outright. Paragraph (o)(1)(D) names software intended to transfer, store, convert formats, or display clinical laboratory test or other device data and results, along with a clinician’s findings about them, unless that software is also intended to interpret or analyze the data. That is not an enforcement choice FDA made and could reverse. It is Congress removing FDA’s jurisdiction over the described software entirely — the same functions 880.6310 had classified as Class I five years earlier, now outside the device definition by operation of statute.

The exclusion has a sharp edge. The moment a function starts interpreting or analyzing that data — an alarm, an out-of-range flag, a trend call — it crosses back over the line, into either the clinical decision support provision at 520(o)(1)(E) or, for a function FDA judges risky enough, back into needing its own 510(k). No classification record announces that crossing. It happens inside a development roadmap, not inside any database this product or any other reads.

The regulation’s own text ran five years behind

FDA did not rewrite 880.6310’s wording to match the 2016 statute until April 19, 2021 — a final rule filed under docket FDA-2018-N-1440 — when it amended the identification paragraph of eight classification regulations, MDDS among them, to drop the software functions the Cures Act had already excluded and describe only the hardware that remained. FDA issued that rule without notice and comment, on the reasoning that it imposed no new requirement; the statute had already done the work. For five years, the regulation’s own words described a broader category than the law still permitted FDA to reach.

A classification regulation can keep naming a category the statute has already carved out from FDA’s reach. The text catches up on FDA’s own schedule, not the statute’s.

What a portfolio search still won’t show

Read 880.6310 today and it identifies a hardware device — nothing else. A product that only transfers, stores, reformats, or displays device data in software has no classification regulation to cite anymore, because it was never a device to begin with under the current statute, not merely exempted from review as one. That distinction matters for a portfolio: an exempt Class I hardware device still owes FDA registration, listing, and a complaint file. Software excluded under 520(o)(1)(D) owes the FD&C Act nothing, and produces no row in any FDA system — not a 510(k), not a classification entry, not a listing — for this product or any other to find.

The practice

Where a specific software function sits today — excluded outright, under clinical-decision-support enforcement discretion, or a device requiring its own submission — is a determination for the firm’s own regulatory judgment against FDA’s current guidance, never something a classification lookup settles on its own. What stays constant is the gap: product code OUG describes 2026’s narrower hardware-only category, not the data-handling software most of a portfolio still calls MDDS by habit, and an excluded function generates nothing in the four sources this product ingests — Federal Register notices, warning letters, device recalls, and 510(k) clearances — because an excluded function never produces an FDA record at all.