Japan 'My Number' national ID system data mix-ups
Japan's national identification and public-services system was found to have repeatedly linked personal data, including bank accounts and health insurance details, to the wrong individuals, forcing the government to pause parts of the rollout and conduct a nationwide review.
The damage was public. The root cause was preventable.
Japan's national identification and public-services system was found to have repeatedly linked personal data, including bank accounts and health insurance details, to the wrong individuals, forcing the government to pause parts of the rollout and conduct a nationwide review.
What the software actually got wrong
Errors during data registration and system linkage let different people's personal records become cross-matched under someone else's ID number, a data-integrity failure in how the system's registration process validated and linked incoming records.
Errors during data registration and system linkage let different...
Errors during data registration and system linkage let different people's personal records become cross-matched under someone else's ID number, a data-integrity failure in how the system's registration process validated and linked incoming records.
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.