A reprocessed device answers to a new manufacturer

A hospital that reprocesses a single-use forceps for a second use usually treats the practice as an infection-control decision: validate the cleaning cycle, document it, move on. The FD&C Act treats it as something bigger. The moment a device gets reprocessed for reuse, the reprocessor doesn't inherit a slice of the original manufacturer's compliance file — it becomes the manufacturer the Act is talking about, for that specific device, from that point forward. This blog has already traced how far 21 CFR 807.20's registration duty reaches, and reprocessing is one of the activities the section names outright — not a borderline case argued into scope, but a listed one.

MDUFMA answered a question nobody had forced FDA to settle before

Before the Medical Device User Fee and Modernization Act of 2002, reprocessing sat in a genuine gap: a reprocessed single-use device didn't cleanly trigger a new manufacturer's obligations, because the reprocessor wasn't obviously either an original equipment manufacturer or a party the existing rules had ever named. MDUFMA, signed October 26, 2002, closed that gap by extension rather than by writing a parallel rulebook — a third-party or hospital reprocessor of a single-use device became subject to the same requirements that already applied to an original device manufacturer, and 21 CFR 807.20 now names reprocessing explicitly among the activities that trigger registration, alongside listing and, where the specific device warrants it, premarket submission.

Critical, semicritical, noncritical sets the validation floor

Registration and listing apply the same way regardless of the device; what changes device to device is how much validation evidence a reprocessor owes before that unit goes back into use. FDA sorts reprocessed single-use devices by the nature of the contact they make with a patient: a critical device contacts normally sterile tissue or body spaces and needs sterilization validation, no substitute accepted; a semicritical device contacts intact mucous membranes and can be validated to disinfection or sterilization; a noncritical device only touches intact skin and carries the lightest validation floor of the three. It's the same contact-based logic a biological evaluation plan already runs against a new device under ISO 10993-1, applied here to decide how rigorously a used one has to be proven clean before its second life starts. A reprocessing validation record that doesn't state which of the three categories the device sits in hasn't shown enough to know which floor it was actually validated against.

MDUFMA forced FDA to re-open the premarket question by device type

Some critical and semicritical reprocessed device types had been exempt from premarket notification before 2002, the same way a device's classification exemption can still fail on its own limiting terms. MDUFMA required FDA to review that exempt list specifically for reprocessed critical and semicritical devices and decide which of them actually needed a 510(k) after all — and where FDA kept the requirement, it layered a validation-data element on top of the ordinary elements 21 CFR 807.87 already lists: the submission has to include validation data on cleaning, sterilization, and functional performance, not just the standard substantial-equivalence comparison. A reprocessor that files the ordinary 807.87 elements and treats a device's pre-2002 exemption as still standing has skipped the exact review MDUFMA forced FDA to run.

The label is where the substitution becomes visible downstream

Section 502(v) of the FD&C Act requires a reprocessed single-use device's label to carry a specific statement: “Reprocessed device for single use. Reprocessed by [the reprocessor].” Leaving it off doesn't just create a documentation gap — it misbrands the device under the same section that requires it. That label is also the one place in the distribution chain where the substitution this whole framework runs on becomes visible to a clinician who will never read 807.20: the name on the device is the reprocessor's, not the original manufacturer's, because for regulatory purposes it's the reprocessor's device now. FDA revised its own MedWatch Form 3500A to add a field asking directly whether a reported device was a reprocessed single-use device — a small addition that only makes sense once the reprocessor, not the original manufacturer, is who a complaint or an adverse event actually has to trace back to.

Where this meets the file

A reprocessing program's tracker needs the device's critical, semicritical, or noncritical category, its validation record against that category's floor, its 502(v) label text, and its own MDR reporting line — kept as the reprocessor's own regulated article, not a footnote inside the original manufacturer's device history. This blog has already covered how a medical device report runs its own two clocks once a reportable event exists, and a reprocessing tracker owes that reporting under the reprocessor's own name, not the original manufacturer's. A reprocessing-validation worksheet built around the three contact categories and the 502(v) label requirement is previewed in the launch catalog. If your program tracks a reprocessed device differently, the shelf takes that correction directly.