On Sun, Dec 25, 2005 at 08:37:56AM +0800, Syan Tan wrote: > can vaccination last batch number be stored in a separate table which has a > foreign key to vaccine ? > > The reason for this is that if a widget displays a vaccine generically, and > there are several batches in the fridge, and perhaps > several brands of the same generic vaccine (which can be traced by their batch > number), the last batch number might > be better as a drop down list which can be added to , and definitely exhausted > batch numbers removed after selection.
Let's see. There's two situations: We have two different brands of vaccine for one and the same indication (hence, generically the same vaccine). That case is already covered. We have two different boxes belonging to two different lots of the very same vaccine brand in the fridge and we opened *both* boxes. That way we'd have two different lot #s for the very same thing. For one thing GNUmed does support entering *any* lot #. OTOH, it might be good practice to keep on using up one of the boxes first, then the other, perhaps based on expiry. The last_batch_no is not intended to track inventory in stock. Its only purpose is to enable offering a reasonable default batch number when a new vaccination is entered. Do you still see the need for changing the schema ? I'd need more explanation as I can't entirely appreciate the use case yet. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
