Re: [Gnumed-devel] Poor Man's Vaccination Plan

[Karsten Hilbert]

On Wed, Jun 02, 2010 at 08:35:29AM -0700, Jim Busser wrote:

> What about recording a *history* of having been vaccinated (when you don't 
> know what product was used in some other praxis)??

You mean, like, in the sense of a Soap item ?

Sure, accounts of dubious credibility of vaccinations having
taken place should still be recorded manually as Soap items.

However, whenever the provider so thinks it should be
documented in a computable form, however (for later checking
of compliance with vaccination schedules).

Nonetheless, this is an excellent (if perhaps unintended)
hint towards the fact that, technically, vaccination rows
surely are soap rows in the database and we can allow for
some recording of certainty by enabling the user to choose
between "given here or taken from trustworthy records" and
"narrated but I trust it for computation anyway" by means of
the .soap_cat column in clin.vaccination :-)

This would translate into clin.vaccination.soap_cat being
either A or P ...

If it's just the product that's not known -- that's what the
indications selection is for !  You see a vaccination record
for TdaP but no mention of the product so you tick off the
relevant indications and save off the vaccination record
anyway. GNUmed will create 4 vaccination records each linked
to one fake, internally-maintained, single-indication
vaccine. Later on this can be made arbitrarily smart by
checking the indications list for known combinations
(whereof TdaP surely would be one of the first) and
maintaining fake combi-indication vaccines for that. I'll
probably hardcode a few of those for 0.8 even (think HepA +
HepB).

It'll be possible later on to merge previously separate
vaccination records.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346