My goals are less ambitious. The situation is not complicated. In
medical clinical trials, the protocols are often fairly complicated,
and the usual approach is to indicate that group one will receive
drug A and group two will receive drug B, and all other management
will be at the discretion of the physicians caring for each patient.
This does not work when it is impossible to mask what treatment is
actually being received, so our goal is to make the "other
management" be quite protocolized. So instead of saying "Fix the
ventilator to make the patient well" we want to say "Turn the
ventilator settings to x, y, z", given some patient state of
"a,b,c". In this manner, no matter who the physician is, a patient
presenting with "a.b.c" will receive the therapy "Turn the ventilator
settings to x,y,z", regardless of physician, time of night, or
institution.
My goal is to provide an end user bedside tool for the nurse or
physician in the ICU for patients on these protocols. But I want to
allow sophisticated users to open an Eclipse perspective that will
enable them to help write the rules for the protocols, as this
process often takes years.
I think the first step is to simply enable this to happen in a robust
GUI environment; the long term step may be to try to use a tool like
Protege as the front end of this process, as perhaps this will better
help us derive the knowledge needed from researchers and physicians,
etc. I am fortunate because I am an experienced ICU physician with
about 30 years of computer programming experience, enabling me to try
to play this schizophrenic role. However, adding Eclipse, Hibernate,
Spring, Java, and Jess to the learning curve has made this quite
interesting.
Thanks for your comments.
On Jul 17, 2006, at 5:06 PM, Robert Kildare wrote:
Hi
It's nice to read someone who is at my level of JESS use. I think I
have
some answers at times, but leave it to the hardened campaigners in
case I
lead you up the garden path.
I am also involved in trying to get users to edit rules. Getting
users to
learn the process is a major difficulty - even seriously constrained,
simple rule structures with user-friendly infix rather than prefix
syntax
and stored translations, contextual help. I am hoping to have the
software learn from the changes so that the recommendations it makes
capture expertise dynamically. Perhaps in your medical scenario it is
worth considering returning a degree of certainty with the
diagnosis? If
I answered one of your questions, my degree of certainty would be
about 0.3
cheers
Rob
==============Original message text===============
On Mon, 17 Jul 2006 22:18:23 +1000 "mdean77" wrote:
The OTHER reason, which I forgot to mention, to want this code to be
on the Jess side, is that my "dream application" actually will have
two perspectives (it is an RCP Eclipse based application). The
normal clinical user will enter some clinical information, push a
button for a clinical recommendation, receive the recommendation
(with the "Why" and "Really Why" things I mentioned previously),
accept or decline the recommendation, and all these interactions will
be persisted to the database. But the second perspective would
enable a user to edit the *.clp files that are used. Thus, I
anticipate distribution of this application without a complete set of
*.clp files, as some of the users are actually going to be developing
the rule sets.
Thanks.
On Jul 16, 2006, at 6:01 PM, friedman_hill ernest j wrote:
I think mdean77 wrote:
However, I do not see how this relates to I/O Routers. And my next
stretch is into the TextAreaWriters, which don't really exist in
SWT,
but this must be simpler than I am making it.
TextAreaWriter and its new Swing cousin are both very simple classes
that implement Writer by taking the calls to "write()" and turning
them into an "appendText" sort of call on a text component. Writing
something similar for an SWT Text widget would be a very quick
exercise.
But the point of TAW and friends, and of mucking with I/O routers in
general, is that you've already got a command-line program, and you
want to graft it onto a GUI without much work. If you're writing
things from scratch, then I wouldn't bother. Build your strings, talk
to your Text widgets, and just generally write the code the way you'd
write it in Java. In fact, it's perfectly fine to write as much of it
in Java as makes you comfortable, leaving just the rules in Jess.
---------------------------------------------------------
Ernest Friedman-Hill
Advanced Software Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 294-2234
PO Box 969, MS 9012 [EMAIL PROTECTED]
Livermore, CA 94550 http://herzberg.ca.sandia.gov>
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users
[EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify owner-jess-
[EMAIL PROTECTED]
--------------------------------------------------------------------
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users
[EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify owner-jess-
[EMAIL PROTECTED]
--------------------------------------------------------------------
===========End of original message text===========
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users
[EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify owner-jess-
[EMAIL PROTECTED]
--------------------------------------------------------------------
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
