gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] encounters... extend vs new, and how to decide? was:


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] encounters... extend vs new, and how to decide? was: improved soap notes creator screenshot
Date: Sun, 30 Nov 2008 22:35:40 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Nov 24, 2008 at 12:46:48PM -0800, Jim Busser wrote:

> If the to-be-developed waiting list note mechanism would be coupled to 
> the patient record and therefore only (or customarily) able to be viewed 
> as part of activating a patient, then should the RFE for the NEW show 
> have to be (also) supplied in the above dialog?

It should, eventually, yes.

> Supposing, at any real-time visit, it is decided that the patient should 
> come back for one or more visits for specific purposes (let us say, to 
> reassess their blood sugar control in 2 weeks, and they also wish or 
> agree to return some time in the next few months for a pap smear, would 
> we potentially create any encounters ahead of time?

Not encounters but either (externally managed) appointments
with an RFE which should feed back into GNUmed or
recall/managed care plan entries or whatever mechanism is
developed.

> A future 0.5-ish sort-by-encounter -- as just discussed in http:// 
> lists.gnu.org/archive/html/gnumed-devel/2008-11/msg00113.html -- could 
> then list, below the encounters which have already been completed, the 
> encounters that are yet-to-be...
>
> these would list (in future, chronologic 
> order) the encounters for which a future booking (clin_when) has been 
> made, and below those the encounters which have been created-in-advance 
> but are yet to be booked, and in the meantime their clin_when could 
> remain NULL?
As above, not "encounters-to-be" but, yes, those expected
RFEs should suitably inform in that display.

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]