[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] GNUmed release
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] GNUmed release |
Date: |
Wed, 24 Jan 2007 00:11:47 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Tue, Dec 19, 2006 at 09:15:41PM +1100, syan tan wrote:
> Can I suggest someway of knowing where in the chronology of notes
> a particular point the episode view is, e.g. like a button , jump
> to selected episode, which scrolls the chronology view to the current
> episode view ?
I am not sure I understand your suggestion, Syan. Could you
expand a bit on that ?
> Anyone have any opinion about whether import/merge-on-demand is better
> than mass import ?
I think both have their merit depending on what is needed.
One thing is certain, though: merge-on-demand is technically
(quite a bit) more, well, demanding.
I would favour an approach where the user can say "import
data of patient X now". The legacy data of that patient is
exported from the legacy system, imported into GNUmed and
removed from the legacy system.
> Mass import can take quite a long time, maybe it
> would be faster to recode in C or C++;
Using SQL-level COPY should suffice.
> import on demand means more
> space, because the old database has to exist alongside the new database,
> and there may be a need for merging / update if the people keep using
> an old application "just in case"
That's the "more demanding" part I was referring to above.
> Any opinions which features are worth pursuing ?
I'd think the ex-/import on demand is useful.
I'd think even if we did re-export of data for the legacy
app we might have problems getting that data back into the
legacy app.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- Re: [Gnumed-devel] GNUmed release,
Karsten Hilbert <=