Se below: Vennlig hilsen Bj?rn N?ss Produktansvarlig DIPS ASA
Mobil?+47 93 43 29 10 -----Original Message----- From: openEHR-technical [mailto:[email protected]] On Behalf Of Diego Bosc? Sent: 13. november 2014 21:23 To: For openEHR technical discussions Cc: openehr-clinical at lists.openehr.org Subject: Re: Postulate: DV_QUANTITY should be modelled with fewest possible units As mentioned on twitter, I agree with that postulate for templates, but not general archetypes :) [Bj?rn N?ss] I partly agree. I agree that the Templates would adapt archetypes to a given use-case and as part of that constraint units. But my concern in bringing this up is the query part. I have been very lucky with archetypes that makes it possible to model and save the maximum dataset for every phenomena we meet. But then - when we are using queries, CDS, process support and reporting over archetyped data we need to reduce complexity where we can. Healthcare is a complex domain. The maximum dataset for simple observations like body temperature, body weight, etc. shows this. This is why I want to introduce this postulate to remember to keep complexity down as often as possible. Of course it is not hard to query over grams and kilos, compare them and do whatever we want. But the real question is why do we need to do that? For general archetypes that will be reused in different use-cases and different modules it is best to define the datastructure in a consistent way. And then leave it up to the user-interface to display the data in a way that fits the current user or user-group. 2014-11-13 21:07 GMT+01:00 Bj?rn N?ss <bna at dips.no>: > I want to try out a postulate regarding modelling of datavalues, and > more specific DV_QUANTITY. > > > > The postulate is: > > > > Postulate 1: A data type of DV_QUANTITY should be modelled with fewest > possible units! > > > > Reason behind this is to make queries and reasoning over the values easy. > This makes it both faster and safer building sustainable software and > systems using these values. > > I also think that converting between i.e. grams and kilos should be > done in the client (user interface / integration engine/ etc.). > > > > What do you think? > > > > > > > > > > Vennlig hilsen > Bj?rn N?ss > Product Owner > DIPS ASA > > Mobil +47 93 43 29 10 > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > ehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
