gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Gnumed on Windows: the pain of pyPgSQL


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Gnumed on Windows: the pain of pyPgSQL
Date: Mon, 12 Sep 2005 17:29:52 +0200
User-agent: Mutt/1.5.9i

On Mon, Sep 12, 2005 at 07:42:41AM +1000, Ian Haywood wrote:

> > What should happen if the user had selected a health issue
> > from the problem list but which already has an open episode
> > of age < 90 days ? I think we then need to ask the user for
> > guidance, no ?
> IMHO I would like it silently added to the open episode.
Sounds OK to me. What about the *name* of the episode ? The
user may wonder how to find his notes ...

The scenario is like this. The problem list contains two
items. One is the active health issue, one is the open
episode for that health issue. User selects health issue
thereby indicating he would like to start *another* episode
under that issue - and not continuing the open episode
that's also on display. Would that make sense ? Would that
be a reasonable assumption ? It would mean we should close
the open episode no matter how recent ... This, of course,
requires that the user *can see* in the problem list that
there is an open episode for a given health issue - which as
of today isn't quite true.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346




reply via email to

[Prev in Thread] Current Thread [Next in Thread]