[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: GNUmed and FreeDiams
From: |
Jim Busser |
Subject: |
Re: [Gnumed-devel] Re: GNUmed and FreeDiams |
Date: |
Thu, 30 Dec 2010 14:48:28 -0800 |
On 2010-12-30, at 1:06 PM, Karsten Hilbert wrote:
> There is code for neither so far (and not for Germany
> either). What there's code for is to read the German and the
> FreeDiams exchange file and use that to populate
> branded_drug.
How would it work, from the GNUmed user point of view, to use FreeDiams?
1) configuration… with FreeDiams
(a) the executable that is to be called resides on the client machine
(b) one or more FreeDiams dbs will also live on the same machine
(c) the GNUmed client would need to be able to resolve
whether it is running under Linux vs Windows vs Mac
i.e. the OS-dependent executable path (and db) to call
(d) in a mixed OS environment, (c) cannot be supported
by a single, centrally-stored string. Presumably, each
of multiple OS-appropriate codes need to be stored in
GNUmed and the user needs to "select" FreeDiams?
2) actual within-patient use?
- user activates a patient (sets in focus)
- user selects Medication plugin
- user click "Add" button (?)
and without further action gets launched into an instance of FreeDiams?
How would a user signal to pass the list to FreeDiams, to re-prescribe some or
all current medication or just test interactions?
Upon returning from the FreeDiams session…
1) any branded-drug that was prescribed, but does not yet-exist in GNUmed
--> gets added to the table "branded_drug"
2) any drug which the patient was not already listed as currently taken
--> gets added to the current list
3) what if the drug already exists on the current list…
--> will the dosage / regimen (as returned by FreeDiams) over-write the
most recent "current"?
-- Jim