[Top][All Lists]

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

Re: [Gnumed-devel] patient search widget revisited

From: richard terry
Subject: Re: [Gnumed-devel] patient search widget revisited
Date: Wed, 26 Mar 2003 09:07:49 +1100

Just had a play with the wigit and seems qood.  The commonest implementation 
of search order in Oz (hate it or like it - I hate it) is surname,firstname 
or part thereof ie hay,ia etc.  I note that is not implemented yet.

In my program I also implement firstname searches by eg: ,susan would bring 
up a list of all the susan surname entries etc

I like the idea of being able to do a mini query in this box such as

male <40 hay,ia etc or variations therof.

BTW I checked out the OSCAR thing, and I must say I was distinctly 
unimpressed. Not sure why anyone would find it impressive. Web interfaces 
always fail to impress me for some reason - in theory there should be no 
difference, but I've never seen one I feel is functional enough to be useful.



On Tuesday 25 March 2003 12:37 pm, you wrote:
> OK, folks, this is needed so I started on it.
> a) various implementations existed already notably by Ian and
>    Horst upon which I drew code, inspiration, test samples and
>    use cases
> b) it is based on my earlier experiments published here
> c) it does NOT use the phrase wheel
> Please test it !
> Go to test_area/khilbert/patient_search. The relevant widget
> is in gmPatientSelector. Notes:
> - It does run standalone but, yes, even then does it need a
>   database to run against as it uses the GnuMed infrastructure
>   both codewise and database-wise.
> - Ian currently gets the honor of being the default patient
>   courtesy of his holding patient ID 1.
> - You need to create two links there named "business" (pointing
>   to client/business/) and "modules" (pointing to
>   client/python-common/).
> - Docs are within the file.
> - It does not handle selection from a list of matching
>   patients yet.
> - It handles most (simple) search fragments that I throw
>   at it.
> - It provides infrastructure for plugging in country-specific
>   query generators based on the system locale.
> - Upon losing focus it discards typed search fragments and
>   reverts to the currently active patient. A search fragment
>   history is desirable.
> - It prints queries to the console.
> - Level 1 queries are executed first. If no results come up,
>   level 2 queries are sent off. If still no results, level 3
>   queries are tried. This last step should be subject to user
>   intervention (or threaded).
> Please play and complain ! Or fix.
> Karsten

reply via email to

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