We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similar to issue 40, https://api.cpicpgx.org/v1/rpc/recommendation_lookup?diplotypelookup={"TPMT": {"*16": 1, "*1": 1}}&drugname=in.(azathioprine,mercaptopurine,thioguanine)&order=drugname yields an empty Json response '[]'. So was with the key for *1/*1.
According to https://cpicpgx.org/guidelines/guideline-for-thiopurines-and-tpmt/, TPMT does have a TPMT diplotype-phenotype table. Both *1/*1 and *1/*16 have diplotype and phenotype mapping defined in the spreadsheet.
The text was updated successfully, but these errors were encountered:
I was wondering if there is any update on this. https://api.cpicpgx.org/v1/rpc/recommendation_lookup?diplotypelookup={"TPMT": {"*1": 1, "*3C": 1}} returns an empty Json as well.
Sorry, something went wrong.
I also noticed https://api.cpicpgx.org/v1/rpc/recommendation_lookup?diplotypelookup={"NUDT15": {"*1": 1, "*3": 1}} returns an empty Json. Similarly, NUDT15 diplotype-phenotype table is in the guidelines of NUDT15.
No branches or pull requests
Similar to issue 40, https://api.cpicpgx.org/v1/rpc/recommendation_lookup?diplotypelookup={"TPMT": {"*16": 1, "*1": 1}}&drugname=in.(azathioprine,mercaptopurine,thioguanine)&order=drugname yields an empty Json response '[]'. So was with the key for *1/*1.
According to https://cpicpgx.org/guidelines/guideline-for-thiopurines-and-tpmt/, TPMT does have a TPMT diplotype-phenotype table. Both *1/*1 and *1/*16 have diplotype and phenotype mapping defined in the spreadsheet.
The text was updated successfully, but these errors were encountered: