Address Hierarchy should support the i18n of address hierarchy entries.
The use case would be to assume that all entry names in the address hierarchy are in fact i18n messages (translated by the ad-hoc properties files.)
All public methods of AddressHierarchyService should then return translated entry names to the end user so that the downstream UI experience is never affected. We cannot assume that any UI layer is taking care of translating address fields when leveraging the Address Hierarchy module.
Finally an Hibernate interceptor should intercept the patient saving and updating processes to "reverse translate" the addresses fields prior to saving them to the database.