Japan's device pathway turns on a standard, not class

Three pathways, not three classes

The PMD Act sorts a device into one of four risk classes — general, controlled, and specially controlled, the last split into Class III and Class IV — and routes each class toward one of three regulatory pathways. Todokede, a pre-market notification, covers Class I general devices: the filing goes to the Pharmaceuticals and Medical Devices Agency and takes effect on submission, with no substantive review behind it. Shonin, a pre-market approval, is PMDA's own review and approval, required for every Class IV device without exception. Between those two sits Ninsho, a pre-market certification carried out not by PMDA but by a Registered Certification Body — a private third party MHLW has accredited to certify Class II and, for a defined subset, Class III devices.

The fork is the standard's existence, not the risk tier

What decides whether a given Class II or Class III device actually reaches Ninsho, rather than defaulting to Shonin, is not the class by itself. It's whether MHLW has published a certification standard covering that device's specific generic name. Two devices sharing the same risk class can land on opposite pathways for that reason alone: one has a generic name with a published standard behind it and goes to a Registered Certification Body; the other has no standard on file for its generic name and goes to PMDA for full approval, whatever its risk profile looks like next to the device that does have one. A regulatory file that reads Japan's requirement straight off the device's class has skipped the fact that actually decides which of the two review bodies ever sees the application.

A registered certification body works a narrow instrument, not open judgment

A Registered Certification Body's authority under Ninsho runs only as far as the applicable certification standard's own text — it checks the specific device against the parameters that standard states, the way an EU notified body checks a device against a harmonized standard it's been designated to assess. A claim, an indication, or a design feature that sits outside what the certification standard actually specifies isn't something the certifying body can wave through on its own judgment; it pushes the device back toward Shonin and a PMDA reviewer empowered to evaluate more than a standard's fixed checklist. The certification body's narrower authority is the tradeoff for the faster, non-governmental review Ninsho otherwise offers.

A US or EU classification doesn't transfer the fork

None of this can be inferred from how the same device was classified anywhere else. A device cleared through a 510(k) or classified under MDR doesn't carry a matching answer into Japan, because the fact that decides the pathway there — a published certification standard tied to the device's specific Japanese Medical Device Nomenclature code — has no equivalent question in either the US or EU systems this blog has already covered in detail. A device team that writes “Japan: Class III, approval track” into a regulatory strategy file without first checking MHLW's own certification-standard list for that JMDN code has substituted a class-based guess for the actual determining fact, in either direction: a Class III device with a standard on file can reach the market through Ninsho, and a nominally lower-risk device without one is stuck at Shonin regardless.

Where this meets the file

A Japan regulatory-strategy record needs the device's PMD Act class and its JMDN code as one field, and a separate, explicit field for whether a certification standard exists for that code — citing the standard's own number where one applies — before the file states which of Todokede, Ninsho, or Shonin actually governs. A multi-jurisdiction classification worksheet built around that structure, distinct from the US and EU classification logic this blog has already covered, is previewed in the launch catalog. If your program tracks Japan's pathway differently, the shelf takes that correction directly.