Dear Pariya,
I would vote for the first alternative. If we start to mix up the
information model and the decision support rules too much we will end up
with a quite chaotic system.
Regards,
Mikael
_____
From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Pariya Kashfi
Sent: den 1 juni 2009 10:12
To: For openEHR technical discussions
Subject: Representing knowledge in Archetypes/Templates or external rules
Dear All,
I have encountered a question regarding knowledge representation during
archetype designing.
Let's say a list of some special drugs that patient has used is important
for Evaluation. I have two options here: First, to apply one external rule
during the data entry, and mark the patient as e.g X-affected. Secondly, to
represent this knowledge in Templates/Archetypes I am designing. It can be
in the form of an Item-Tree-Medication-List using internal codes ( to
specify medications that may be selected in the drug list). And to check
this node at runtime or during evaluation of EHR for storage.
It may even be a third option that I have not been considers so far i.d
using internal rules (First Order Logic) within archetypes.
The first option, sounds more general to me, and the benefit is that
whenever I want to update rules, I don't need to change the
arcehtypes/templates. And the second option sounds more natural to me in
that I express the knowledge in archetypes directly, makes it more
understandable for clinicians and can be modeled by themselves.
Which one is more acceptable based on openEHR concepts?Do you see any flaws
in these solutions?Is there any better idea?
Regards
Pariya
MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of Technology
http://www.chalmers.se/cse/EN/people/kashfi-hajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090601/06e0c458/attachment.html>
