[Top][All Lists]

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

Re: [Gnumed-devel] drugref2 in Oscar

From: Jim Busser
Subject: Re: [Gnumed-devel] drugref2 in Oscar
Date: Wed, 17 Feb 2010 17:38:12 -0800

On 2010-02-16, at 12:23 AM, Karsten Hilbert wrote:

> On Mon, Feb 15, 2010 at 10:55:36AM -0800, Jim Busser wrote:
>> Is it useful to be able to answer the following questions and,
> It is probably not useful to pursue that goal given their
> track record of not working with your previous inquiries.
> I don't think they are interested in working with outside
> people.

But Jay has very helpfully helped to shed light on what has been changed, and 
where the code resides, for anyone who may be interested, which I was.

I have summarized it:

The original drugref involved a postgres database, python XML-RPC API, and php 

Oscar McMaster EMR reworked drugref into (what they refer to) as drugref2:
   * Oscar never did use the PHP interface, as this was meant for maintaining a 
monolithic database
   * originally imported Canaidian DPD data into the original drugref schema, 
but found this slow
   * subsequently let Canadian DPD data imports persist (as imported) in 
additional tables and added (a python?) DPD plugin to supply needed server-side 
data to the API (versioned in the oscar cvs hosted on sourceforge, but hosted 
for the most part on savannah at the above link?)
   * added tables to speed searching
   * imported later-acquired Holbrook interactions data
   * ported to mysql
   * in 2009
      * made a java version of the API (as an alternative to the pythonic API)
      * implemented the database layer in JPA (Java Persistence API), which has 
made it easier to support both Postgresql and Mysql
      * you can run the java drugref webapp on-top of an existing postgresql 
drugref database and it works
   * more at
      * and miscellaneous notes below for those who would use drugref2

reply via email to

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