The purpose of this DB is to centrally store the xml data returned by the panel inspection while maintaining the structure as much as possible. For example, when searching for past cases by narrowing down to a specific gene, it depends on the motive such as wanting to avoid the situation of reviewing the PDF.
It is developed for the purpose of swallowing xml data collectively, and it is not assumed that users will register other variables of interest together and analyze related things on the DB. It is recommended to create another table or collect data separately for the research.
This DB is designed to swallow the new xml under the above parent folder every time. This is due to the circumstances of our environment.
If you want to link with the patient ID etc., please write the name of the child folder containing the case xml as 20200105_patientidxxyyzz. This database is designed to swallow before and after cutting with an underscore according to the report information.
If you have the above id, you may be able to merge it with a suitable research table later.
The structure of F1CDx and NOP xml itself is not explained here. I created a slide separately, so please check it. Clinicians will find out by comparing the report with xml.
The notes are as follows.
i. No drug information about the mutation is attached.
ii. The format is completely different for F1 and NOP.
iii. TMB has a decimal point.
iv. It does not hold a LOH score.
Regarding research use, I think that you can use it freely at your own risk, but if you use R or Python, I think that it is smart to obtain data with an odbc connection for various analyzes.