smalllinux wrote: Hi Gaetano,
I think a cooperative redesign of the database structure is a great idea. Sign me up. I just hope it does not stop us from doing some work on our programs. There was a project called littlefish that spent years working on specs for medical software, without producing any usable code, I think. ;-) http://www.littlefish.com.au/lfproject/intro/lfhome.htm Lets make a data stucture that can be modular and extensible and be used for different specialities. Steven G. http://linduent.sourceforge.net/ Gaetano Paolone <[EMAIL PROTECTED]> wrote: >WHY DON'T WE PLAN A NEW DATABASE STRUCTURE that can be able to >manage every medical practice? > >It can have one or two «configure» tables in which you can store >informations like: > >1) Practice. (dentistry, oculists, dermatologist, general pratictioner >and so on) >2) doctor's name/s >3) invoice header >4) practice's address, telephone, fax, ecc. >5) Treatments amount. > >The other tables could be like (we should discuss a lot about it) >odontolinux's ones: > >patient general data >treatment plan >Ledger >Payments/Invoices > >And then we could write different clients. >(PHP, PHP-Gtk, TclTK, Python, etc.) > >So we could call it the (Debian) Medical Practice Management Suite. __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with [EMAIL PROTECTED] http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

