Storing codes of two external terminologies

I don’t know the specific case that @Pau_Corral is facing, but if we look at the specifications, the terminology_id attribute is of type TERMINOLOGY_ID, that at the end is just a String value. But that string has a specific formatting that includes the version of the terminology:

So, at least in theory, for every new version of a terminology, we will have a new terminology id. Probably it’s not the intended functionality, but that’s what I can interpret from the spec.

PD. I love when we dig into such small details :sweat_smile: