[Top][All Lists]

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

Fwd: [Gnumed-devel] I need some help

From: Peter Damoc
Subject: Fwd: [Gnumed-devel] I need some help
Date: Thu, 6 Jul 2006 12:09:29 +0300

---------- Forwarded message ----------
From: Peter Damoc <address@hidden>
Date: Jul 6, 2006 10:30 AM
Subject: Re: [Gnumed-devel] I need some help
To: Richard Terry <address@hidden>

I think I've posted on this list before :) I've been looking with hope at GNUMed for some time.
Also you might have seen my name on wxPython list.

I'm not a doctor, I'm a biomedical engineer. I work for the top plastic surgeon here in Romania and my database program revolves completely around his practice. We have a mini clinic here that has also an ENT doctor and a OBGYN and I would like to include those practices too... right now the OBGYN photo database is a second hand citizen (not managed by the software).

My experience is rather limited compared to a full blown programmer.
I've worked for about 6 months after college as a programmer (mostly Java and some PHP). The rest of my programming experience comes from playing with the python/wxpython combo while here at the clinic (almost 3 years now).
I've written a software to manage the plastic surgery photo database (out of laziness of course) and also I'm the developer of CAIS (Computer Assisted Implant Selection) a software for the assistance of the surgeon in the implant selection process for the Breast Augmentation intervention.

My intention is to develop a software that could potentially be used in small clinics like our own but I dream about making it flexible enough so that maybe it could be adapted to small hospitals.
Right now the first things must come first and so... the plastic surgery section has to be cared for first.
- photo database management
- some patient data (simple stuff)
- additional data for each intervention, for example some rhinoplasty simulation (with patient consent via a fingerprint reader)  or a face surgery consult photo with annotated areas for target rejuvenation zones, or even the implant selection/ preoperative markings that are now done separately in CAIS.
- follow-up support (complications and maybe some kind of patient satisfaction assessment)
- the database must support multiple working posts without interconnection requirements, like for example when dr. Stan goes to Bucharest (our clinic is in Bacau) for consults and post-op visits, he should be able to alter the database and when he returns home some mechanism must be in place to assure that the database on his notebook exports the data into the main database and the modifications we might have done here in the meantime get imported in his notebook.

I was planning to create this software as open source because it is way to big to be created by myself alone. It would not be GPL as I need to be able to link to non-open source code (CAIS code is covered by a license from an Allergan/Inamed contract) and maybe dr. Stan would like to keep the rest of the plastic surgery "little helpers" close source also BUT these are small potatoes and completely irrelevant for a GP.

So... back to my original request :) any ideas on how should I approach this?


On 7/6/06, Richard Terry < address@hidden> wrote:

I seem to recognize your name from somewhere.

Anyway, what is your practice and where are you.

If you fill me in I may be able to throw some idea's your way. Please include
your job/programming experience/languages etc in your reply

Dr Richard Terry
(General Practitioner)
Whitebridge NSW

On Wednesday 05 July 2006 18:12, you wrote:
> Hello,
> I know this is way offtopic but maybe there is some kind soul on this list
> with a little more experience in designing databases.
> I'm trying to implement a patient management software for our practice,
> something kinda like GNUMed but much simpler, only some patient data and
> photos.
> The main stumbling block is how to keep the database coherent.
> I want to provide input access from multiple location in our clinic AND I
> need to find a way for this database to be mobile and by mobile I mean
> several notebooks that should somehow keep a copy of the central database
> and allow the doctor to work in another location, without connection to
> central server and with full access to all data up to the point where the
> last "update" was made. When the doctors return to the main clinic there
> should be some kind of mechanism to resync with the main database that
> might have been modified in the meantime.
> How should I approach this?
> Any kind of idea is welcomed.
> Thank you in advance.
> Peter

Peter Damoc
Lead developer for
Inamed CAIS Planning System

reply via email to

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