[Top][All Lists]

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

[Gnumed-devel] remote control GNUmed

From: Sebastian Hilbert
Subject: [Gnumed-devel] remote control GNUmed
Date: Sun, 27 Nov 2005 23:46:18 +0100
User-agent: KMail/1.9

Hi all,

Jim mentioned it and we took the liberty of giving you the opportunity to see 
GNUmed being driven by an external program.

It is really easy. Set up a local database gnumed_v2 by using in 
bootstrap (latest CVS ). This has consistently worked for me during the last 
few months so I don't expect any problems.

change into the client directory and run
It will start a GNUmed in slave mode.

This instance of GNUmed can be controlled by 3rd party programs like python 

In the same directory there is an example script named Run it 
and watch the GNUmed gui being magically remote controlled.

It opens a patient and switches to the document viewer plugin.

Example session:
address@hidden:~/sources/gnumed/gnumed/client> python
=> setting up connection to GnuMed client on localhost:9999
=> showing macro processor version
cMacroPrimitives $Revision: 1.21 $
=> attaching to macro processor (should fail, missing cookie)
[0, 'attach to personality [None] rejected']
=> attaching to macro processor (should fail, wrong cookie)
[0, 'attach to personality [wrong cookie] rejected']
=> executing action in client (should fail since not attached)
=> attaching to macro processor (should work)
1 0.727081896298
=> trying to raise GnuMed client to top of desktop
cMacroPrimitives.raise_gnumed() not implemented
=> listing loaded plugins (should fail)
=> listing loaded plugins
['gmNotebookedProgressNoteInputPlugin', 'gmScanIdxMedDocsPlugin', 
'gmConfigRegistry', 'gmShowMedDocs', 'gmEMRBrowserPlugin', 'gmManual', 
'gmEMRJournalPlugin', 'gmNotebookedPatientEditionPlugin']
=> raising a plugin that doesn't need an active patient
=> trying to raise a plugin that needs an active patient
=> knew it, need to lock into a patient first ...
1 0.0209650316248
=> trying to raise plugin again
=> switching to document display plugin
=> cleaning up: unlocking patient
[0, 'patient unlock request rejected, wrong cookie provided']
=> unlocking again, correctly
[1, '']
=> detaching from macro processor (should fail)
=> oh well, but now for real

What good is this ? GNUmed 0.2 (librarian) will connect to the commercial 
software we are forced to use side by side with GNUmed.

This software is capable of calling external programs. GNUmed will be running 
in the backgroud all the time. Once you call a ditigal document ( GNUmed 
Archive aka librarian ) from this commercial software it will raise GNUmed, 
select the corresponding patient and display the digital document like a fax, 
referral letter , you name it. No user interaction whatsoever. It will feel 
like a part of the 3rd party software. 

What you see here is our concept of GNUmed. GNUmed will run side by side with 
traditional software. Users will make the transition automatically as more 
features will move from the commercial software into GNUmed. 

Like it or not. GNUmed (my understanding of it ) is not here to replace any 
commercial software here and now.

Wanna know why GNUmed perfoms way better than any package I have seen in 
commercial software ? Because files are stored and accessed through GNUmed. 
Simple rule. If you have access to GNUmed you have access to the digital 
documents. Anywhere. Anytime. Try to do this if you store the documents on a 
SAMBA share :-)
Sebastian Hilbert 
Leipzig / Germany
[]  -> PGP welcome, HTML ->/dev/null
ICQ: 86 07 67 86   -> No files, no URL's
VoIP: callto://address@hidden
My OS: Suse Linux. Geek by Nature, Linux by Choice

Description: application/python

reply via email to

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