lab_result_num has a sample_id column that is null in nearly all cases. Non-null instances are likely artifacts from usage of the old loader. Ages ago, we determined that it was confusing and undesirable for a lab result to be associated with a particular sample from a given visit, since these are clinical values pertaining to the subject's health at the given timepoint. So the ongoing existence of the sample_id column is just there out of an excessively conservative interest in preserving the data therein.
However, there is a need to attach similar bits of data (let's call them numeric and categorical assay results) to individual samples, for work done at the research bench that results in some kind of result data. The motivating example is the VODA quantitative PCR assay (that produce a number like "copies/million cells" for various HIV genes).
The task: add numeric_assay_result and numeric_assay_protocol tables and employ them to add a panel to the Sample page to display VODA results.
lab_result_num
has asample_id
column that is null in nearly all cases. Non-null instances are likely artifacts from usage of the old loader. Ages ago, we determined that it was confusing and undesirable for a lab result to be associated with a particular sample from a given visit, since these are clinical values pertaining to the subject's health at the given timepoint. So the ongoing existence of thesample_id
column is just there out of an excessively conservative interest in preserving the data therein.However, there is a need to attach similar bits of data (let's call them numeric and categorical assay results) to individual samples, for work done at the research bench that results in some kind of result data. The motivating example is the VODA quantitative PCR assay (that produce a number like "copies/million cells" for various HIV genes).
The task: add
numeric_assay_result
andnumeric_assay_protocol
tables and employ them to add a panel to the Sample page to display VODA results.