Which raises another interesting issue. Do you create cross model relationships Larry? I could see that causing problems. For example, create an EO in common with an FK to an EO in emr. Then change connections! Now the common EO's relationship points off into space, or worse, at some other object.
Maybe that could be mitigated by forming to-one's using a two key join table in the destination entity's DB with a unique index on one key column? Interesting problem in any case.