How to model Entity Attribute Value sources


I’m new to Data Vault modelling so apologies if this is a basic question. I am trying to model a source that holds all it’s data in EAV tables and I’m struggling to decide how to model these. Some of the entities relate to each other and, using business logic, build up into a single entity. For example there is a post code entity which relates to a hospital entity. So my question is, should I be creating a hub from the Hospital and then be storing the postcode in the Hospital satellite (applying business logic) or should the postcode be a hub in it’s own right with a link to Hospital (not applying business logic)? If it is the latter then the DV model is going to be huge because almost everything is stored in the EAV tables which would make any queries awful.

Post code is not a business object