You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the awardee who will export these files from the system, there will be a new button next to the actual Download charts as SVG & Download PDF on the reports page, named Download NIH tables or similar. They will have to upload them afterwards in a place that is out of our reach.
There will be three tables (csv format) to be exported:
One with one row per sample, aggregating data from the sample, it's batch etc;
One with one row per sample, containing information about the results obtained by the awardee on their machines;
One with general results of the whole panel's test (sensitivity, specificity, LOD, etc.)
Some data we don't have it within CDx, especially on table 2) (name of the protocol, units of the readout, technology used, etc.) and we will just have to warn the awardee before downloading that some data needs to be manually fulfilled by them.
The batches entity within CDx is missing some data for these tables to be complete, if we're implementing this feature, this columns will need to be added to batches (PANGO_lineage, WHO_label, etc). This missing info differs from the last bullet point since this is data not available for the awardee: the batches info belongs to the University.
They have all the batches information on a spreadsheet: if we add these columns, when we implement the data migration we will have to map these columns for the existing batches taking this spreadsheet as reference for the first time (or alternatively, they will have to go batch by batch defining it for the existent batches, but I mentioned that this one-time migration can be done). For new batches they will define the full information.
The text was updated successfully, but these errors were encountered:
leandroradusky
changed the title
EPIC - NIH-specific tables exporting
[epic] NIH-specific tables exporting
Jan 24, 2023
leandroradusky
changed the title
[epic] NIH-specific tables exporting
EPIC - NIH specific tables exporting
Jan 24, 2023
They have all the batches information on a spreadsheet: if we add these columns, when we implement the data migration we will have to map these columns for the existing batches taking this spreadsheet as reference for the first time (or alternatively, they will have to go batch by batch defining it for the existent batches, but I mentioned that this one-time migration can be done). For new batches they will define the full information.
@leandroradusky did you ask how many batches they have today? If there are just a few, I think I'd suggest for them to manually update them.
Is the awardee who will export these files from the system, there will be a new button next to the actual Download charts as SVG & Download PDF on the reports page, named Download NIH tables or similar. They will have to upload them afterwards in a place that is out of our reach.
There will be three tables (csv format) to be exported:
Some data we don't have it within CDx, especially on table 2) (name of the protocol, units of the readout, technology used, etc.) and we will just have to warn the awardee before downloading that some data needs to be manually fulfilled by them.
The batches entity within CDx is missing some data for these tables to be complete, if we're implementing this feature, this columns will need to be added to batches (PANGO_lineage, WHO_label, etc). This missing info differs from the last bullet point since this is data not available for the awardee: the batches info belongs to the University.
They have all the batches information on a spreadsheet: if we add these columns, when we implement the data migration we will have to map these columns for the existing batches taking this spreadsheet as reference for the first time (or alternatively, they will have to go batch by batch defining it for the existent batches, but I mentioned that this one-time migration can be done). For new batches they will define the full information.
The text was updated successfully, but these errors were encountered: