Re: [Gnumed-devel] Vaccination Functionality Document

[Elizabeth Dodd]

On Wed, 27 Aug 2003 05:44 pm, Hilmar Berger wrote:
> > > Anything is possible Liz, and we can do this. Can you please also put
> >
> > this in
> >
> > > your 'to remind us' task should we forget. There is a field in my
> >
> > vaccine
> >
> > > table which marks vaccines as 'live', so gnuMed should have it as well.
> >
> > Yep, it does :-)   Also plan on enabling patients to be marked
> > "closed due to live vaccination" - we just need a view over
>
>                                                                      
> ^^^^^^ Do we really want to store every rule-dependend bit of information
> on the backend ?
> I always thought that there will some sort of module that checks the data
> on the fly and creates warnings, hints etc. This would allow for more
> flexibility - you don't have to change the backend every time some rule
> changes. And
> changing backend tables in a stable version should be a rare event if data
> integrity should be maintained. IMHO the backend tables should hold
> clinical data but not the way we want to handle them. That might go in
> functions/triggers/whatsoever but should not actually be stored.
>
> Hilmar

I agree, Hilmar, it doesn't belong in the backend. It is an interesting rule 
and probably observed world wide. Also "area" did mean "patient" when 
challenged.
Liz
> --------------------------------------------------
> 1. GMX TopMail - Platz 1 und Testsieger!
> 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
> 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8.
> e-Post

-- 
After an instrument has been assembled, extra components will be found
on the bench.