Which Medical Device Product Codes Travel Together?

Every FDA 510(k) submission is filed under a three-letter product code — a shorthand the agency uses to classify the device. There are over 6,000 of them. But devices sometimes need to use multiple product codes, and submitters often discover that the right code depends on which review division they want, what predicate they’re citing, and how narrowly or broadly they want to describe their device’s indications.

One underexplored question: which product codes tend to appear together, either because devices bridge multiple functional categories, or because submitters bundle related indications in the same submission?

How to read this diagram

Each arc on the outer ring represents a product code. The chords connecting them indicate co-occurrence: two codes are connected when they appear together in the same submission or share a meaningful cluster of overlapping submissions.

Wider chords mean stronger co-occurrence. Hover over any arc or chord to see the specific codes and their relationship counts.

Use the specialty dropdown to focus on a single device category — orthopedic, cardiovascular, gastrointestinal, ophthalmic, and others each have their own topology.

Why Product Code Co-occurrence Matters

A product code signals more than classification. It signals regulatory history, applicable special controls, predicate availability, and often, reviewer expectations. When a submission carries two or more product codes, the applicant is implicitly telling FDA: this device sits at the intersection of multiple classifications.

Sometimes that’s unavoidable — a combination device, a multi-function diagnostic, a software-enabled implant. But sometimes it’s a deliberate strategy, chosen because the predicate landscape for a single code is thin, or because the applicant is trying to establish a broader intended use than any single code supports.

What the patterns reveal

A few things stand out across specialties:

Dense clusters signal broad platform devices. In cardiovascular and orthopedic, a handful of codes serve as hubs — appearing alongside many others. These tend to correspond to general-purpose implants or diagnostic platforms that regulators classify differently depending on the specific indication.

Sparse connections are a signal too. Some codes appear with almost no co-occurrence. That isolation might mean the category is tightly scoped, or that submitters working in that area have settled on a consensus classification strategy and rarely need to combine codes.

Specialty boundaries are porous. Several codes appear in clusters that straddle two specialties — notably at the intersection of general surgery and gastroenterology, and between radiology and cardiovascular. These boundary codes are often the ones where predicate strategy is most ambiguous.

What the Submission-Level View Reveals

For regulatory affairs professionals, the more actionable question isn’t which codes co-occur most often across the database — it’s whether your device, or a device similar to yours, follows the same pattern as its predicate.

Consider two cleared 510(k)s in the same specialty, one of which is the other’s predicate. If the subject device references two product codes and the predicate only referenced one, that difference is a data point. Either the applicant successfully expanded scope through the 510(k) process, or the additional code reflects a design feature the predicate didn’t have. Either way, it tells you something about what FDA accepted.

The reverse case is equally informative. A submission that narrows product code scope relative to its predicate may have done so strategically — to reduce the regulatory surface area and increase the likelihood of clearance.

Emerging Questions Worth Investigating

The 6,000 multi-code submissions raise some questions we’re actively exploring in our data:

Do multi-code submissions take longer to clear? If referencing multiple product codes correlates with longer review timelines, that’s a real trade-off for applicants weighing scope against speed-to-market.

Which applicants use multi-code strategies most consistently? Some large device companies file multi-code submissions repeatedly across their portfolio. Whether that reflects a deliberate regulatory strategy or the nature of their products is worth examining.

Are certain code pairings becoming more common over time? A pairing that first appears in 2019 and becomes frequent by 2023 may reflect a new guidance, a cleared combination product that opened a pathway, or a shift in how FDA is interpreting a device type. That trend is invisible in the structured clearance data alone — you need the document layer to see it.

How often do subjects and their predicates share the same code profile? When they don’t, and the subject still cleared, that’s a predicate strategy case study worth knowing about.

Why this matters for regulatory planning

If you’re preparing a 510(k) submission, understanding co-occurrence helps in two ways:

1. Predicate search: Co-occurring codes expand your predicate universe. If your device sits between two categories, submissions that were classified under both codes are likely to contain relevant predicate language and testing protocols.

2. Reviewer routing: Product code selection influences which branch of the device center reviews your submission. Co-occurrence data gives you a sense of which combinations have been accepted before — reducing the risk of a code dispute late in the process.

Access the Data

The chord diagram above is built on live BeneDoc data. If you want to run your own queries — comparing a specific submission against its predicate, or filtering trends by specialty and year — sign up to get access to our platform.

We’re currently working with a small group of regulatory affairs professionals and consultants to refine our search and comparison tools. If you work with 510(k) submissions regularly, we’d like to hear what you’re trying to find.