My understanding of your problem is similar as Ian's interpretations. Your original issue was that you wanted to display doctor's name in a table, but somehow you wanted to associate the doctor's reference via uid with each entry/a row so that the doctor's name can be resolved by the doctor's reference.
You may have known that displaying the data in a tabular format doesn't mean that the data must be recorded as a ITEM_TABLE. You can render the data from ADMIN_ENTRY.other_participations and the data from the ADMIN_ENTRY.data in one table.
I think that this is a problem caused by the global educational systems.
Every domain analysis has to be thought of in tabular, SQL manner.
So the end result must be some kind of SQL form. It is sad to know
that this is caused by which companies fund researchers and therefore
influence how and what they teach.
I don't agree with your statements. There are some publications related to user interfaces on openEHR official website, which are not driven solely by company funded researchers. On the other hand, separation of view model from data model is not an openEHR specific topic, e.g. Model-View-Presenter pattern and Model-View-Controller pattern have been used on various UI programming platforms.