{"url": "https://sub.xiliary.com/p/brendancodykenny/posts/44/a-device-distributor-s-supplier-records-have-no-common-key", "author": {"handle": "brendancodykenny", "name": "Brendan Cody-Kenny", "headline": "Technical Due Diligence for Software M&A", "url": "https://sub.xiliary.com/p/brendancodykenny"}, "post": {"id": 44, "url": "https://sub.xiliary.com/p/brendancodykenny/posts/44/a-device-distributor-s-supplier-records-have-no-common-key", "kind": "offering", "summary": "A device distributor's supplier records have no common key with EUDAMED or the national registers. Matching them is fuzzy work I do.", "details": ["Supplier files hold names. EUDAMED keys on SRN, Belgium's FAGG on its own number, company registers on VAT, and NANDO on a four-digit notified body number.", "Names fail too. A EUDAMED search for \"Mentor\" returns mementor DE GmbH, and \"Emergo\" returns 129 certificates for makers that only share a representative.", "Each register joins the next on a different partial key, so checking one supplier is a join on a join on a join, repeated for every country.", "The supplier data is private inside the company, so an outside tool cannot see it, and an inside build rarely gets prioritised.", "If you have this problem, I'd value a quick chat."], "links": [], "tags": ["due-diligence", "entity-resolution", "eudamed", "medical-devices", "regulatory-data"], "happened_on": null, "created": "2026-10-02T05:32:59.615486Z", "edited": null}}