Re: [Gnumed-devel] roadmap and what a 0.1 release will "look like"

[Jim Busser]

On Mar 27, 2004, at 12:43 AM, Karsten Hilbert wrote:

> It is certainly possible to write a controlling plugin for the
> wxPython client but that doesn't necessarily make sense: Path
> results will end up in some directory on the server to be
> picked up by the importers. The wxPython client will usually
> run on the client machines ...

With respect to the universe of GNUMed functions, have we use for terms 
like:
- "user-initiated" for a process that can (or may only ever be) 
user-initiated i.e. might not otherwise be "triggered" nor run on a 
schedule
- "user-accessible" (triggerable) for a process that a user may access 
(trigger), though the process might also be automated, and
- "user-controlled" for a process that runs SOLELY when triggered at 
the user's request, where the user may or may not exert some choice, 
perhaps e.g. ASCII export ?

I was thinking that some standalone clients, such as fetching lab 
results, even though they run as background processes, might usefully 
also be  "user-accessible" (triggerable).

Example: patient asks for their lab result taken yesterday, which is 
not yet in GNUMed --- the lab could have generated the result after the 
last cron job. Now, if the user could know that the last job only just 
ran 20 minutes ago, there is little value re-running it, but if it was 
last done a few hours ago (especially if there were a service 
interruption and cron will not run again for a while) it may well be 
worth fetching that result immediately to guide patient care. The user 
could ask that the job be re-run, ideally within the lab viewing 
interface, than to have to contact their practice data administrator or 
even for the user themselves to operate the lab-fetching client whose 
default user interface could require an expert user.