gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] unhandled exceptions EMR_MedicalHx_, GNUmed_IFAP, Of


From: James Busser
Subject: Re: [Gnumed-devel] unhandled exceptions EMR_MedicalHx_, GNUmed_IFAP, Office_Appts
Date: Sun, 13 Jan 2008 15:39:32 -0800

On 13-Jan-08, at 1:06 PM, Karsten Hilbert wrote:
On Sun, Jan 13, 2008 at 12:43:27PM -0800, James Busser wrote:
Except even on my local database, when I added past history items with the
EMR tree selected, it did not refresh after a minute. When I clicked
Progress notes the item was immediately there, and when I clicked back on EMR tree it was there. But it appears something extra is required (at least on mac) to refresh the screen. Does that make sense and does it appear
correct, and not on Windows or Linux?
Oh that, OK, sorry. That is still true and being worked on
(even on Windows/Linux).

Then I do not understand what was possible in your "fun" post about database change awareness (recopied below) ... how is this change awareness manifest? If the user must somehow signal the backend that the user wishes their information refreshed, does it make GNUmed currently no different than any other EMR?


On 7-Jan-08, at 7:12 AM, Karsten Hilbert wrote in Re: [Gnumed-devel] fun w/ 0.2.8

Now that several people have got 0.2.8 running a fun
experiment is demonstrating the database change awareness of
the client:

Two people activate the same patient from the public
database.

One of them edits demographics data, say, the name,
DOB, or allergies.

The other observes how those values change on *his* client
in real time responding to edits done by someone else
possible across continents.






reply via email to

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