Dear Silje, I think we agree.
In my view it is not wise to use pre-coorinated codes that include contextual information. The reason is that the complete why, when, who and how result in too many permutations in order to be tractable. One must make the distinction between how data is expressed in a generic system interface connected to other services such as: database, clinical reasoner, import/export, etc. and between a specific interface that users connect with for data inspection, data entry, statistical data analysis. The former must NOT use pre-coordinated terms; the latter depending on user requirements will use pre-coordinated terms that can be constructed using the raw data in the generic system interface. Gerard Freriks +31 620347088 [email protected] Kattensingel 20 2801 CA Gouda the Netherlands > On 23 Mar 2018, at 10:35, Bakke, Silje Ljosland > <[email protected]> wrote: > > I read Thomas’ reply with great interest, and I generally agree that with a > well thought out information model, the very detailed precoordinated > expressions are redundant. At the same time I understand Mikael’s point of > view too. BUT, what I’m often met with is that because these precoordinated > expressions exist (like for example “lying blood pressure” and “sitting blood > pressure”), we should use them INSTEAD OF using our clever information models > (that we do have) for recording new data. <> > <> > > In my opinion this is wrong because it doesn’t take into account that > healthcare is unpredictable, and this makes recording more difficult for the > clinician. How many different variations would you have to select from? Take > the made up example “sitting systolic blood pressure with a medium cuff on > the left upper arm”; this will be a lot of possible permutations, especially > if you take into account all the different permutations where one or more > variable isn’t relevant. > > So while I don’t think the existence of these precoordinated terms in itself > is a problem, it’s a potential problem that people get a bit overzealous with > them. > > Regards, > Silje >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
