gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] re: rschedule


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] re: rschedule
Date: Sat, 1 Jul 2006 16:30:26 +0200
User-agent: KMail/1.9.3

On Saturday 01 July 2006 03:39, Syan Tan wrote:
> <p>the pros for linking oscar appointments , is that the gui is already
> done, and everything has been debugged.</p><p>the cons are that it adds a
> massive amount of supporting java libraries to run it ; this may not be a
> problem</p><p>with a debian installation, especially if it is possible to
> run tomcat from something like an alternate java runtime;</p><p>but the ,
> say optional, appointments functionality with oscar would require
> installing a java runtime, tomcat,</p><p>mysql , apache libraries, all
> which are testing debian packages anyway. </p><p>To do it, it requires
> associating oscar demographics with gnumed demographics. </p><p>The use of
> the appointment system seems to run something like:</p><p>add appointment
> -&gt; enter name, enter reason,&nbsp; optionally include use case of
> searching demographics,</p><p>and specifically linking demographic identity
> to appointment. </p><p>So an intercept point might be the button search
> demographics, this could bring up a gnumed</p><p>demographic search jsp
> pages (needs to be written), and then the post-processing for this search,
> is to use a gnumed</p><p>demographic id and store it with appointments.
> Perhaps add another field to the appointments table</p><p>specifying from
> which application the demographic id is associated with. </p><p>&nbsp;The
> second intercept is the E (ncounter) hyperlink that follows&nbsp; an
> appointment created from a searched and positively</p><p>identified
> identity.&nbsp;  Here, the appointments table entry's extra application
> field could be looked up, and if it </p><p>is &quot;gnumed&quot; , then the
> action taken in java could be a number of things for interprocess
> communication to a gnumed</p><p>application , say running on the same
> machine, ( e.g. a appointment searching listening socket, or a local
> identity</p><p>list file in say the .gnumed directory regularly polled by
> the gnumed app , or a write to a postgresql identities_to_open table and a
> notify</p><p>or it is polled by gnumed).&nbsp;</p><p>Currently, gnumed has
> no idle state, it always has a patient open or it is not running at
> all.</p><p>You could have a polling when idle timer running in the gnumed
> wx event queue, that checks to see if </p><p>an identity has been
> registered in a identities_to_open table , for the current user, say every
> 2 seconds.</p><p>Alternatively, issue a notify command, but I'm not sure if
> the java sql component for postgresql lets you do it</p><p>but it probably
> does. &nbsp;</p><p>Someone needs to decide if it is desirable to try to
> link the appointments in oscar to gnumed, and</p><p>then what is the
> desired mechanism to notify the gnumed applicaiton, and the desired way
> of</p><p>opening ( e.g. auto filling the search textfield at the top of the
> gnumed application, so that when the</p><p>user is ready, just hits enter ,
> and the search module in gnumed brings up the patient</p><p>specified in
> the appointment. Maybe slightly modify the gnumed search widget so that if
> it is a number, followed</p><p>by the name, it sees if the this is a unique
> patient id, and if it is , just opens the patient</p><p>without bringing up
> the search list).&nbsp;</p><p>&nbsp;</p><BR>
Just to mention it here I suggest in the long run one might take a look at 
chandler (calendar application) entirely written in wxpython it's designed to 
avoid a lot of problems. Does iCal as far as I can see plus it is wxpython.
Should be easy to nterface.

But hey. Oscar is there already so chandler is more like an long term option
-- 
Sebastian Hilbert 
Leipzig / Germany
[www.gnumed.de]  -> PGP welcome, HTML ->/dev/null
Faire Angebote beim Internetshoppen gibt es in meinem Onlineshop
fairdeal.profiseller.de




reply via email to

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