[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Synching
From: |
Jim Busser |
Subject: |
Re: [Gnumed-devel] Synching |
Date: |
Sun, 30 Aug 2009 18:21:36 -0700 |
On 30-Aug-09, at 12:54 PM, Thiemo Kellner wrote:
is there the possibility in GnuMed to defer the changes to data such
that one could use the GnuMed client soft on a laptop or the like
and commit the changes to the database when back from seeing
patients? Or is the recommended way to use a master database on a
kind of server and synch/replicate a local database on a mobile
client?
As replied already, it makes a huge difference whether the master
remains unchanged while a single user takes a copy with them, alters
the copy, and seeks to sync the records back.
Multiple asynchronous records would be a huge challenge. They might
roughly be divided into:
- person already exists in GNUmed
- person does not yet exist in GNUmed
If the person did not yet exist, it might be possible down the road to
"import" these "new persons and their data" in the same as-yet-
unimplemented manner as has been entertained for allowing a record
from one GNUmed syystem to another.
If the person did already exist, it might be better to find a way to
create offline information that would then need to be imported into
the existing patient.
If and when Mirth is figured out to import lab data, maybe it could
similarly import outside data into an existing GNUmed patient record.
In the meantime, I suspect multiple asyncronous changes can only be
handled by the offline people taking with them a copy of the GNUmed
database for *reference* and then create a note at the point of care.
If they wished to facilitate problem-oriented records they might use a
text outliner program and on return to the praxis drag-and-drop text
snippets into a new encounter. Simpler of course would be to put the
entirety of the text into a single unattributed episode.