Open main menu

Farmakorakels Wiki β

Changes

Pharmacolyzer

365 bytes added, 12:50, 28 August 2018
Example of how access to the Pharmacolyzer through a REST API could look like
We have coined the verb ''to pharmacolyze'' for the action of the Pharmacolyzer
===Sensitive Getting access to pharmacolyzis of sensitive data===Patient VCFs are sensitive data, and the storage of VCF data and [[Pharmacotyper|pharmacotyping]] data has to be stored are preformed on secure servers. It may also be sensible to run the pharmacolyzer in a facility for sensitive data, and only export the final ''pharmacolysis''. Access to the final PGx analysis could be given through a REST API, and we describe one approach in the section below.
===Examples of use Example of how access to the Pharmacolyzer through a REST APIcould look like===We have downloaded a VCF with samples from the [http://grch37.ensembl.org/Homo_sapiens/Tools/DataSlicer?db=core 1000 genomes project]. Four samples from the VCF was then [[Pharmacotyper|pharmacotyped]] and stored in a JSON file called ''merged_patient.json''which is now accessible to the Pharmacolyzer at pgx.no. Pharmacolysis can be performed for the following drugs and patient samples:
{| class="wikitable"
|-
For pretty printing, the following can be used:
<pre>curl https://www.pgx.no/api/pharmacolyzer -d "patient_name=merged_patient&drugs=azathioprine&samples=NA19461" | python -m json.tool </pre>
Note that this is quite slow (20-30 seconds, especially the first query, when the OWL reasoner process is being set up, later queries may become as little as 4-5 seconds, which is still a bit slow for such a simple program)