Well, I bow to your superior method -- ha! I did find that demo page as the only other search result, but it's mostly just data model stuff you can get out of the platform. That docs page & YouTube video were very helpful, though. I offered feedback that they add the table name to the docs page.

Anyway, for other folks, it appears basically be to support an approach to tracking third-party industry codes for models, such as ECRI for medical asset models. I still question the utility of it as an independent table as it's referenced by sn_ent_model rather than having an m2m relationship. So I don't believe this scenario is supported:

Model Infusion Pump XYZ has the code 12345 from ECRI and A5678 from the EMDN. Each of these codes gets it's own record, references the source (ECRI or EMDN), and are tied back to the model Infusion Pump XYZ through m2m relationship or one model to many codes by reference field on the classification.

Rather, you can associate multiple models with a code, but you cannot associate multiple codes with a model.