We have access to a tool which sends a request to the variation services at the NIH. Effectively it hits the APIs using a genomic HGVS, generates an SPDI call and uses the call to perform accurate searches of dbSNP and ClinVar. See the SPDI paper.
The tool failed on testing with variant so needs some additional testing. Otherwise it was robust.
NC_000006.11:g.102503229C>T
Implementation
Because the tool hits an external API, it will need to be integrated within a try: Except statement.
There are two possible implementations.
If the tool runs quickly once integrated and pre-initialised, the links can be generated on the fly and added to validate_results
Otherwise, a link will need to be created in validate_results which creates and returns a new internal page displaying the links.
My preference is option 1
To me it makes sense to add the new tooling as a service which is where the other links are generated prior to display.
We have access to a tool which sends a request to the variation services at the NIH. Effectively it hits the APIs using a genomic HGVS, generates an SPDI call and uses the call to perform accurate searches of dbSNP and ClinVar. See the SPDI paper.
The tool failed on testing with variant so needs some additional testing. Otherwise it was robust.
NC_000006.11:g.102503229C>T
Implementation
Because the tool hits an external API, it will need to be integrated within a try: Except statement.
There are two possible implementations.
If the tool runs quickly once integrated and pre-initialised, the links can be generated on the fly and added to validate_results
Otherwise, a link will need to be created in validate_results which creates and returns a new internal page displaying the links.
My preference is option 1
To me it makes sense to add the new tooling as a service which is where the other links are generated prior to display.