[Top][All Lists]

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

Re: BC billing data source was Re: [Gnumed-devel] slave mode scripts

From: Sebastian Hilbert
Subject: Re: BC billing data source was Re: [Gnumed-devel] slave mode scripts
Date: Sat, 31 Jul 2010 08:31:20 +0200
User-agent: KMail/1.13.3 (Linux/2.6.33-6-desktop; KDE/4.4.5; i686; ; )

Am Samstag 31 Juli 2010, 01:40:42 schrieb Jim Busser:
> On 2010-07-13, at 11:36 AM, Karsten Hilbert wrote:
> > Reading pycommon/ might help, too.
> Some original ideas boiled down... specification for the external data file
> at bottom
> Much of what I need could be achieved by just extending the "external
> patient sources" which GNUmed already knows and can already read. If all I
> want is to be able to invoke a patient in GNUmed from the outside this
> makes a lot of sense. It could be debugged from within the client - just
> hit F2 and select the patient from among the choices. I think this will
> need a new XDT file to be created to "map" to the specification below, and
> for this XDT to be reference in the local user config file?
> The ONLY remaining part would then be to get the already-existing
> ??? to tell the client to *now* look for a new external
> patient.
> This is less a need for the clinician unless the patient had not before
> been created in GNUmed *and* the doctor is logged onto the billing
> software. It is more a need for the front desk who (in a small office)
> does both billing and appointments.
> Would such "GNUmed being told to look"  still depend on a running slave
> instance to be "controlled"?

Yes. A script could invoke a "switch to patient" in a running slave instance 
or you could manually pull up a master instance and find the patient through 
e.g. hitting F2.

Pulling up the patient and switching to a plugin in a slave instance is 
already there. What is it you then want to do inside GNUmed ?
Or do you just want the automation to avoid manual searches in GNUmed ?

In the script(s) you can define which plugins to pull up in a running slave. 
For all other purposes you can have a master instance running in parallel.

Can you describe the workflow of use/interaction between the billing software 
and GNUmed ? We might suggest more comprehensive approaches regarding the 
slave/master issue.

I can give you an example. In Germany many commercial packages have the option 
to kickstart external applications through some menu item. When they do they 
export the current patient and call the external application (with user 
defined command line arguments).

We have used that to tell a German EMR to start GNUmed (actually talk to the 
slave) and switch to the document archive plugin. GNUmed (the slave instance) 
will read the exported patient file , open it in GNUmed (or create a new 


reply via email to

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