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: James Busser
Subject: Re: [Gnumed-devel] encounters... extend vs new, and how to decide? was: improved soap notes creator screenshot
Date: Mon, 24 Nov 2008 12:46:48 -0800

On 24-Nov-08, at 2:29 AM, Karsten Hilbert wrote:

Why ? Clinician 2 will see the RFE/AOE, duration, and type
of encounter right in the dialog asking whether or not to
continue ? It's always been that way. It looks a bit like this:

------------------------------------------

This chart has been accessed only recently !

RFE: needs insulin refill
AOE: authorized Drugs'n'Goods, 11 Levenshtein Street

by phone (21.11.2008 8:45 - 8:57)

Do you want to continue that encounter or do
you want to start a new one ?

[Continue]                [New]

-----------------------------------------

OK, I had not yet adequately seen/experienced the above but the above certainly makes things nicely clear.

Additionally, the clinician really *should* be able to know
of the (patient-expressed) RFE for the NEW show via a
waiting list note mechanism.

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?

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? Perhaps

- in Praxis ... RFE = r/a blood sugar control
- in Praxis ... RFE = pap smear

The above rows could have infinite expiration. I am less sure about how to handle their "future dating"... it may be acceptable for them to keep their original time stamp of creation to communicate at what point the need for the encounter was recognized or agreed-to even though the encounter will not actually happen until later when the clin_when an in praxis appointment is scheduled, and later completed.

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?




reply via email to

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