for HiGHmed, we explore the use of the newly introduced other_details field to represent above mentioned concepts. We aim to concurrently allow the mapping to corresponding FHIR resources. For me this appears to be a natural fit, as the care episodes and encounters have a hierarchical relationship and encounters on hospital level can be nested with clinic encounters (I refer to encounter as defined by FHIR: https://www.hl7.org/fhir/encounter.html). Furthermore, this is a nice way to link versioned objects to encounters and episodes.
So far, so good. However, I find the following challenge(s):
-these concepts are typical admin entries. Folders only allow item_structures, i.e. clusters. I have found several situations where the entry types are making re-use quite difficult. Do you have any ideas for the future, how this can be solved more elegantly? For now, I can simply copy all elments from the admin entry into the cluster.
-As an alternative: might it make sense to add another field to the folders with an optional reference to a composition containing the admin entry? This might be a cleaner solution as we could keep everything inside the admin archetypes, we can use the known mechanisms for querying etc.
-As DIRECTORIES can be archetyped: would it be even better if we could define this extra reference in an archetype/template that defines contraints on the DIRECTORY structure? Only problem is that nobody has this implemented.
Would be great to get some feedback.
Edit: sorry for not making the title of this post more technically abstract. I may change this one after getting a bit more clarity on this topic.