[Top][All Lists]

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

Re: [Gnumed-devel] roadmap

From: Ian Haywood
Subject: Re: [Gnumed-devel] roadmap
Date: Wed, 30 Jul 2003 03:08:36 +1000

On Tue, 29 Jul 2003 08:09:21 +0200 (MEST)
address@hidden wrote:

> > ------------------------
> > drug information browser
> > ------------------------
> > maintainer: RMIT
> > hackers:
> >  - if data is available locally
> >  - PBS via via XML-RPC, initially
> >  - AMIS (German) to follow
> What will be RMITĀ“s commitment ? Will they work mainly on the backend /
> side or will we get a new drug browser GUI ? I planned to improve 
> the
Currently they are working on only, not the drug browser. David and
Alan are keen to do more general gnumed work after this, but it not (yet) 
part of their project.

> GUI of the existent drug browser somewhat and add XML-capability to the
> lower level backend API in the future - just want to know if this still makes
Please do, we will eventually need a drug browser, it is not a core feature 
here in Oz 
as we don't (yet) have any textual data to display. We do have basic drug 
packet sizes type stuff that allows us to prescribe, I am interested in writing 
a middleware to do
this, before starting on the prescription widget itself.

I notice you have written a configurable drug infomration viewer in 
test-area/gmDrug, I would like to extend this
for the prescription widget, but I'm not
sure it can provide the precision that is needed: this needs databases 
to 'look' the same: use the same strings to define units, formulations, amounts 
etc. in the same way,
plus (later) things like interactions checking. My original conception was for 
separate Python 'drivers'
which do this, which can hide more detail of the underlying database and export 
a higher level API. 


PGP public key E750652E at
9BF0 67B7 F84F F7EE 0C42  C063 28FC BC52 E750 652E

Attachment: pgpfqxlM1rfbY.pgp
Description: PGP signature

reply via email to

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