close! very close. it's actually spelt "agnieszka"
if the antibiotic GROUP never changes, why don't you just store the group that you used. Why do you have to store all the indivdiual antibiotics? - i can understand you may need to do this, if the panel make up changes over time.
the panel of antibiotics doesn't change, no, but the effect of each antibiotic on each bacterium does. so, the result for ampicillin in one bug will be different to the other bug. but every bug i test will have a result for ampicillin when i use that particular panel.
so, not "tested against all the antibiotics in panel NMIC/ID-101" but
"test against ampicillin resulted in MIC of >8 ug/mL, against tetracyclin (>=16 ug/mL), gentamicin (>8 ug/mL), levofloxacin (<1), nalidixic acid (=2) etc..."
until all the antibiotics & results for that panel are listed.... for each bug tested. (and obviously normalised, arranged to be efficient in an access table etc)
i am not wishing to store only what test was performed, but the RESULT of that test. each antibiotic in each panel is tested against each sample INDIVIDUALLY, not as a whole (i.e., the 20 antibitotics i mentioned that are in the panel are physically separated, they are not all applied at once to each sample - so there are 20 different results for each bug/panel combo, not just one), but what happens is that the sample is individually added to each well of the panel (containing a different antibiotic in each well) and the results are collected.
i know! i'll find a picture.... [bit of net surfing/googling] ....here is a picture of what a panel looks like:
http://www.bd.com/ds/technicalCenter/brochures/br_222786.pdf
cover page of that pdf you'll see these cartridge thingys ("panel") with lots of round bits just sticking out ("wells").
each row of that panel has a different antibiotic, and each column changes the concentration of that antibiotic. you then decant a suspension of your bug into the panel and it distributes the bug to all of the wells via the force of gravity/capillary action.
this panel then goes into a big machine overnight (one machine has a carousel in it which can take uhm, up to about 100 panels, i think).
during that time, the bug either grows, if it's resistant to that particular antibiotic at that particular concentration, or is inhibited by that antibiotic all together, and does not grow at all.
one panel takes only one sample. it is also not reusable. so if i want to test 10 bugs, i have to set up 10 panels (where each panel has identical antibiotics and concentrations of those antibiotics).
the machine gives an output at which concentration the antibiotic inhibited the growth of the bug. so, isolate 14023e07 may have the result "<1 ug/mL" for ampicillin, while isolate 02045e01 may have ">8 ug/mL" for ampicillin.
this machine does not do long-term storage of results, but they can be printed and stored that way.
we have thousands of bugs, not all will be run through this test, but for the ones that are, i don't want to have to remember which antibiotics to add to my results table. while i may have a table with which antibiotics are on each panel, it would be easier if i could programmatically make the correct antibiotics jump into a subform for result entry (so, make ampicllin etc appear in the subform, with me then entering things like >8 or <1 in the result for that antibiotic).
also, it would be infinitely useful to then be able to query our data set to find all those bugs which are, say, resistant to ampicillin (this is determined by interpreting the raw data of ">8 ug/mL", which is detail in CLSI standards - though this is not the right forum to start talking about that!)
but yes, we also will have the benefit of having stored which bug have been tested. with so many bugs, it's important to see which ones have NOT yet been done either
hope that made things clearer, and not more muddy! sorry, i kind of waffled on a bit, but i love my job and just get excited to talk about it
I think detailed stuff like this is never simple in terms of data structure - its similar in concept to a questionaire i think.
tell me about it! i've been maintaining this inherited database for just over a year now. it's been a massive challenge but also very satisfying when i do things right

my supervisor LOVED the efficiency created by this mysterious thing i called "normalisation", for example. and due to this fact alone, i have been heralded the access expert in our lab - go figure!!
