On Wednesday 25 October 2006 15:40, Greg Twyford wrote:
> > In the meantime, we keep pushing development of a free alternative that
> > runs natively on Linux - my current mini-gnumed and web interface are
> > really only platform independent bolt-ons and extensions to said Medibase
> > backend (nowadays called Promedicus)
>
> Horst,
>
> So the backend is still proprietary, or have I missed something here?

You mean in my practice?

I have a mutated conglomerate of tables, many of them still stemming from the 
old Medibase, some of them extended by extra columns, lots of extra tables
You can still connect to it with the old Medibase GUI frontend, qand that is 
indeed what my associates still do (unlkess tyhey access scanned documents, 
quickly browse through path results, or manage anticoagualted patienst which 
either much faster or only possible with my own self written software)

These tables run on the open sourced Firebird SQL server (fromer Interbase) on 
a Debian Linux machine
The old Medibase GUI client runs within a Win4Lin TS session on the same 
Debain machine
My web frontend is written in PHP and runs on Apache again on the same Debian 
machine

A second web frontend accessible by patients runs on a separate tiny Via Epia 
box (again Apache/PHP), firewalled to only allow a low-privileged connection 
to the Firebird server but no other connection possible/allowed with the 
surgery network

Thus, three proprietary bits you still find in my practice:
a) Win4Lin Terminal Server
b) old Medibase GUI front end
c) Pracsoft 1.x (phasing in and out depending obn the current state of my 
replacement, currently it's "in" again and frustrating my front desk staff no 
end)

As soon as the prescription module for myt own software as well as the billing 
module are finalized, all three proprietary bits will go forever, and good 
riddance. Just can't afford to hold my breath til that happens

Good news are:
1.) appointments and billing systems are clean room designs - no dependency 
nor copied bits form any proprietary software
2.) rest of my own software will be gradually ported to a clean room design

One day, ...

Horst
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

Reply via email to