[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Task management beyond the make-shift waitlist functional
From: |
Busser, Jim |
Subject: |
[Gnumed-devel] Task management beyond the make-shift waitlist functionality |
Date: |
Tue, 6 Dec 2011 19:10:07 +0000 |
(was Re: [Gnumed-devel] GNUMed SOAP vs SOAPless progress notes)
On 2011-12-06, at 9:23 AM, Karsten Hilbert wrote:
> On Fri, Dec 02, 2011 at 01:15:31AM +0000, Jim Busser wrote:
>
>>> The waiting list is intended to hold and communicate
>>> *patients* waiting in the praxis to be seen. That's the
>>> design goal.
>>
>> You did previously write
>>
>> "Along the way - and drawing
>> from first hand use case experience - I noticed that with a
>> few minor generalizations (arbitrary zoning, arbitrarily
>> settable list position etc) this sort of thing can be used
>> for a lot more than just currently waiting patients…
>>
>> Since the waiting list isn't intended as a tool for
>> clinical-plan-handling-only
>>
>> (?? not sure what was meant)
>>
>> it can only be by social
>> contract at your site that the waiting list zone
>> "clinical-todo" is used for such things
>>
>> http://lists.gnu.org/archive/html/gnumed-devel/2009-07/msg00266.html
>>
>> Thus, I cannot discern whether you did (and do still)
>> picture the Waiting list to double as a task manager,
>
> Ah, indeed, I did write that.
>
> Now, while I still do think that the waiting list *can*
> serve as a make-shift, Poor Man's task manager (to more
> liberally allow such kinds of hacks we've carefully crafted
> the waiting list as not to unduly impede them) I still
> maintain that the immediate design goal for the waiting list
> was to fulfill the purpose "allow maintaining a list of
> patients waiting to be seen".
>
> This does not infringe of the usefulness of managing tasks.
On 2011-12-06, at 9:23 AM, Karsten Hilbert wrote:
> I still
> maintain that the immediate design goal for the waiting list
> was to fulfill the purpose "allow maintaining a list of
> patients waiting to be seen".
Ok...
1. I am relieved to infer that (at least until there would be separate and
better management of care-related must-be-dones) there is no plan to cut back
its make-shift task management capacity
2. As-yet-unanswered is the future-oriented question, as to how this may
eventually be preferably and better-implemented. Two options:
(a) the ability to assign a 'Plan' rows to an individual (or to a role) in the
praxis, however better would be…
(b) the ability to clone a
selection-of-text-within-plan
to become a to-do, stored in a table for this purpose. While some soaP rows may
spawn no to-dos (having already been fully taken care of), any one soaP row
*could* OTOH spawn multiple yet-to-be done tasks. It would be helpful if, for
any patient, it can be made apparent
at the patient level, whether exists for them one or more incomplete
tasks
--> maybe even accessible from the inbox?
a view (plug-in?) of tasks per patient, informing about
task
problem context
assigned to role or user
created_when
created_by
modified_when
encounter ?
Billing would better eventually be its own module, but maybe it can fit in
tasks (I believe at least one GNUmedder is using the waitlist for billing) ! :-)
-- Jim
- [Gnumed-devel] Task management beyond the make-shift waitlist functionality,
Busser, Jim <=