> > - The fact that the current tools do not expose or use these attributes, > > is a design decision made by the people writing the tools. > > Well probably often a "decision" in lack of time/resources or (less > likely) lacking ideas of good/useful ways to present them. A tool > exposing the RM has to deal with both RM and AM in detail and thus > takes more time building than dealing with AM only. > Actually I think it was more to try to keep the task of archetyping simple as it is a task targeted at Domain Experts (Clinicians) without them requiring to know about the RM (well so we thought). Unfortantly, hiding some attributes that are commonly required by the clinician forces them to put it in the archetype so they can see it. We are also finding more and more RM attributes that we want to archetype other than just data structures such as participations.
The challange is to find a visualisation of the archetype that is still simple but can also expand out to include relevant RM attributes. In Ocean's next generation of tools, mainly inspired by the requirements of the Archetype Query Builder where criteria on RM attributes is common, we will have a configurable tree view of templates where individual RM attributes can be turned on or off, right down to the data type attributes if needed. We are also looking at alternate visualisation of archetypes for the next iteration of the Ocean Archetype Editor. Regards ? Heath ? Heath Frankel Product Development Manager Ocean Informatics Ground Floor, 64 Hindmarsh Square Adelaide, SA, 5000 Australia ? ph:?+61 (0)8 8223 3075 mb: +61 (0)412 030 741 email:?heath.frankel at oceaninformatics.com
