Contact ODE is not a pathway

Type a product code into a portfolio setup form and, most of the time, the pathway comes back as one of three plain words: 510(k), PMA, or 510(k) Exempt. Sometimes it doesn’t. Sometimes the field FDA publishes for exactly this purpose returns two words that aren’t a pathway at all: Contact ODE. That isn’t a bug in whatever tool is reading it. It is FDA’s own documented answer, and it means what it says — call the Office of Device Evaluation, because the database itself doesn’t know yet.

Three real values, and a fourth that refuses to be one

FDA’s device classification database carries a field, submission_type_id, that names the regulatory pathway a product code is limited to. openFDA’s own field reference documents four values, and only three of them are pathways: 1 for 510(k), 2 for PMA, 4 for 510(k) Exempt. The fourth, 3, is defined in FDA’s own reference as Contact ODE— the agency’s wording for a product code whose submission-type limitations, if any, are not clearly defined. It is not a placeholder somebody forgot to fill in. It is the documented, correct answer for a specific set of codes, and the honest reading of it is the same as the reading of any other empty field in this data: FDA is telling you what it doesn’t know, structurally, in the same record that tells you what it does.

A value with no listing at all

The live data holds one more wrinkle the field reference doesn’t mention. Alongside the documented 1, 2, 3, and 4, some records carry a submission_type_id value, and a device_classletter, that map to neither a class nor a pathway the reference enumerates — the signature of a Humanitarian Device Exemption. An HDE is its own pathway, under 21 CFR Part 814, Subpart H, built for a device treating or diagnosing a condition that affects fewer than 8,000people in the United States a year — small enough that a conventional effectiveness trial is rarely practical, which is why an approved HDE is not required to demonstrate the same reasonable-assurance-of-effectiveness standard the other three pathways share, while still having to show its safety. That is a real, well-defined regulatory category. It is just not one the classification database’s own field reference enumerates alongside the other three, which leaves a lookup built strictly to that reference to decide, on its own, what to do with a value nobody described.

An undocumented value in a government dataset is not automatically an error. Sometimes it is a category that exists in the world before it exists on the page describing the data.

What a lookup does when the database won’t answer

FDA Radar’s own product-code lookup — the one that turns a single product code into the eleven fields an onboarding form asks for — reads this exact field, and it is built to do one thing when the value isn’t one of the three mapped pathways: say so, in FDA’s own wording, rather than pick one. A code whose submission_type_idis 3 surfaces as “FDA lists this code as ‘Contact ODE’ — the pathway is undetermined,” not as a guess dressed up as PMA or 510(k). A value the field reference doesn’t define at all surfaces as a note asking for manual confirmation, the same treatment an unmapped device-class letter gets. None of that is judgment about what the pathway should be — it is a refusal to invent one, the same discipline this product applies to every field FDA itself declined to fill in.

The practice

Hit “Contact ODE” on a product code that matters to your portfolio and the productive move is not to keep asking the tool. It is to read FDA’s classification record for that code directly — the definition text, the regulation number if one exists, the review panel it sits under — and, if the device in question might be humanitarian-use, to check FDA’s HDE listings separately, since that pathway lives outside the three the classification field was built to describe. This is regulatory intelligence and method, never regulatory advice: which pathway actually governs a specific device, and what that means for a specific submission, is a determination for a regulatory professional reading the file, not a field in a lookup table. What the lookup can honestly do is stop at the edge of what FDA itself has published, and say exactly where that edge is.