[Top][All Lists]

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

Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 55, Issue 11

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 55, Issue 11
Date: Wed, 20 Jun 2007 23:02:42 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

On Wed, Jun 20, 2007 at 09:25:06AM +0200, Philipp Walderdorff wrote:
> User-Agent: KMail/1.9.3
> Subject: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 55, Issue 11
> Am Dienstag, 19. Juni 2007 18:00 schrieb address@hidden:
> > > I'd rather would say: GnuMed would be licensed in Austria after having
> > > been adapted, possible through the knowledge of the code of my program.
> >
> > That is another possibility but it will take more time and
> > require getting a new license. It will involve putting the
> > Austrian billing into a module and interfacing that anyway.
> After recent discussion I would think the best would be:
> 1. hold and refresh my lisence for my program in Austria
> 2. Adapt sucessively Gnumed with the knowledge of my source for austrian 
> needs 
> in a modular way, so that other countries can profit.
> 3. Make a new license for GnumedAustria.

This seems like a very good plan.

> For Point 1: To manage this, I would have to interface my programm with the 
> eCard-System. Until now the eCard is managed via Broser and the patient-data 
> are copied and pasted into my program on a second window. In future the 
> interactions between praxis-program and eCard-System will be more intensive 
> because of eReception, the digital paperless prescription, which will be a 
> point of the re-licensening.
> In order to manage this I am asking, if GnuMed has managed this or similar 
> stuff. If this is true, I would like to solve these things with a 
> Python-Program, which is interfaced with may program.

For interfacing the card reader and reading the card (KVK
and also eCard) we use libchipcard (

Martin is a German doctor in Hamburg :-)   I am sure he'll
be able to help you with this part.


GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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