I disagree. I like hierarchical structure which goes from country to system to field. And the field name is the same as in the system so that there is less confusion. If there is a usecase to use it as a ref, it could be copied to ref field, but I'm not sure about such a usecase since this id is not a code or a natural key.

EE:EHIS:name is required only when it's different from the name.