[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Gnumed 1:4
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Gnumed 1:4 |
Date: |
Sun, 14 Apr 2013 18:02:03 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sun, Apr 14, 2013 at 05:58:02PM +0200, Karsten Hilbert wrote:
> Date: Sun, 14 Apr 2013 17:58:02 +0200
> From: Karsten Hilbert <address@hidden>
> To: address@hidden
> Subject: Re: [Gnumed-devel] Gnumed 1:4
> User-Agent: Mutt/1.5.21 (2010-09-15)
>
> On Sun, Apr 14, 2013 at 03:26:44PM +0200, Jerzy Luszawski wrote:
>
> > The waiting list is missing one feature important for me - SCHEDULING
> > the patient to FUTURE DATE.
>
> That is by design. The waiting list is a list intended to
> list patients currently waiting in the waiting room to be
> seen.
>
> The fact that GNUmed cannot (neither does it want to) actual
> correspondence of patient on its waiting list vs those
> physically sitting in the waiting room allows room for
> certain sorts of creative use of said waiting list (which is
> fine).
>
> Adding support *to the waiting list* for patients being
> *scheduled* to *eventually* and *potentially* be on the
> wwaiting list IMHO smells of overstretching the metaphor.
Especially now that inbox messages support a due date which
can be (ab)used for a Poor Man's scheduling of sorts meaning
there's not really a need (IMO) or desire (by me) for a
"non-proper" implemenation.
> I suppose you'd want to extend the gmDemographics.py ->
> cKOrganizerSchedulePnl into something more generic
An "appointments list", that is. Which is another
well-established concept/metaphor.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346