[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] failure of 1.3.3 to show current encounter in Overview
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-bugs] failure of 1.3.3 to show current encounter in Overview? |
Date: |
Fri, 3 May 2013 23:35:12 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, May 03, 2013 at 08:59:51PM +0000, Jim Busser wrote:
> >> … is it the fact that the 2nd encounter is current or that
> >> it contains today's date that prevents the updating in the
> >> overview?
> >
> > The overview shows emr.get_last_but_one_encounter() as
> > "last". This is because emr.get_last_encounter() will ALWAYS
> > be today (or, rather, the current encounter).
> >
> > Suggestions for improving the "last" in "last: 2013 Apr 18"
> > welcome :-)
>
> The main situation that I would like to avoid is where one
> user may not realize that some other user (or an import
> daemon) may have already written new results into the
> record, and/or that they patient might even be physically
> present already in the praxis.
>
> Therefore I am thinking that any current encounter type
> other than the equivalent of review chart, and any encounter
> in which new information has been written / saved, might be
> helpful to cause an update to what is shown in Overview.
My explanation of what happens / is displayed and your
description of what you desire seem orthogonal to me ?
Am I misunderstanding something ?
Apart from bugs (or missing code) the overview refreshes
whenever anything it depends from (displays) changes.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346