[Top][All Lists]

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

Re: [Gnumed-devel] plugin design question

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] plugin design question
Date: Fri, 1 May 2009 16:09:05 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Apr 30, 2009 at 08:13:41PM +0200, Hilbert, Sebastian wrote:

> I was asking myself. Where do I implement rule checking ? Let's say I would 
> like to let the user select the pacing mode DDDR and store 
> <rateresponse>active</rateresponse> because R is part of the mode. 

That's not rules checking per se. It's just some simple
logic that's happening when the user presses [Save].

> I would implement this in the GUI ? 
> Or in some sort of special intermediateware so a webclient input field could 
> be evaluated as well ?
It would be part of the middleware.

> If we later decide to store values in the database instead of xml part of 
> this 
> will have to be implemented at database level , right ?

> I could then do stuff like warn the user when the battery gets low, a 
> unipolar 
> pacemaker lead is set to bipolar or prompt for shorter follow up intervals 
> when an elevated pacing threshold ist detcted and stuff like that.

That is something entirely different. What you want to do
*here* really are checks to be run at, say, either patient
activation or plugin raise. Those checks can be hardcoded
(not a good idea) or put into a rules system.

Such rules are implementation independant. They should
ideally live in something like EGADSS and interfaced to

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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