The Workbench · Craft
The Rx legend and a restricted device aren't the same
This blog has already covered how a labeling file can hold two related facts under one heading and lose the distinction between them, and the separate question of when a label is doing risk-control work at all. The “Rx only” statement on a device's label raises a version of the same problem. A device can carry that legend because of what it is, with no FDA order behind it, or because FDA has affirmatively restricted it under a different statutory authority — and a file that treats the legend itself as proof of the second thing has mixed up a labeling fact with a regulatory one.
A device earns prescription status on its own facts
21 CFR 801.109 exempts a device from the adequate-directions-for-use requirement in section 502(f)(1) of the FD&C Act when the device isn't safe for use except under the supervision of a licensed practitioner — because of its potential for harm, its method of use, or the collateral measures its use requires. Nothing about that exemption depends on FDA issuing an order first. It runs on the device's own safety characteristics, as the manufacturer assesses and defends them, which makes 801.109 status a claim the labeling file has to justify on its own terms rather than a box FDA checked somewhere upstream.
The exemption also carries a possession condition that's easy to overlook: it applies only while the device is in the hands of someone regularly and lawfully engaged in manufacturing, transporting, storing, or distributing it, or in the hands of the practitioner authorized to direct its use. That's the hinge the whole scheme turns on — the device is exempt from carrying lay-usable directions precisely because, up to the point of dispensing, it's supposed to stay inside a chain of people who don't need them.
What the Rx legend actually has to carry
801.109(b) requires the label to bear either the “Rx only” symbol statement or the fuller caution naming the type of practitioner authorized to order the device, and requires any labeling that furnishes directions for use to carry real content — indications, effects, routes, methods, frequency and duration, and the hazards, contraindications, side effects, and precautions that go with them. Reminder labeling that names only the device, without use information, is carved out of that second requirement. Labeling bearing use information also has to carry a date of issuance or latest revision — a detail easy to lose track of once a device has been on the market for years.
A restricted device is a separate, affirmative act
Section 520(e) of the FD&C Act gives FDA a different tool: the authority to restrict a device's sale, distribution, or use when that's necessary because reasonable assurance of safety and effectiveness can't otherwise be provided. That restriction doesn't arise from the device's own characteristics the way 801.109 does — it has to be established by regulation issued under 520(e) itself, by an order as a condition of PMA approval under section 515(d)(1)(B)(ii), or through a performance standard under section 514. Each of those is FDA choosing to act on a specific device, not a fact the manufacturer determines from its own risk assessment.
Why the difference isn't academic
A restricted device carries obligations 801.109 doesn't reach on its own: the FD&C Act's misbranding provisions treat false or misleading advertising for a restricted device, or sale in violation of the restricting regulation's conditions, as a distinct violation. A device can be a lawful prescription device under 801.109 without ever having been the subject of a 520(e) regulation, PMA condition, or performance standard, and the reverse pairing is common too — a restricted-device order layered onto a device whose own label already carried the Rx legend independently. Reading the legend backward, as if its presence proves an affirmative restriction exists, skips the step of checking whether one actually does.
Where this meets the file
A labeling or regulatory file needs these tracked as two separate facts: whether 801.109's Rx legend applies, justified against the device's own safety profile, and whether a 520(e) restriction has been affirmatively imposed, verified against the specific regulation, PMA order, or performance standard that would have created it — not inferred from the label. A labeling-classification worksheet built around that split is previewed in the launch catalog. If your program tracks the two differently, the shelf takes that correction directly.
The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.