-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
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
GRCh38 coordinates #429
Comments
Yeah, there are various ways we could approach this. We could do the conversion internally. I think what we should aim for is adopt a standard approach to solving this problem. There are many conversions that may be of interest. For example,
The last thing the world needs is another implementation of these conversions. Our present goal is to tie everything possible to a ClinGen Allele Registry ID. This does not support all variant types, but it is a good start. We will keep our eyes on the development of VMC implementations as well. Here is an example variant in CIViC that has been linked to Allele Registry: Here is the Allele Registry page for that variant: JSON-LD response It looks like it solves a lot of the use cases I list above. Since it would be convenient to many users of CIViC we can pull some of this data into CIViC. The build38 coordinates should be at the top of the list for things to pull in. |
Is there any progress on providing GRCh38 coordinates for variants? |
Has any decision or progress been made on the use of GRCh38 coordinates in CIViC? |
Currently coordinates of variants are provided in GCRh37, would it be possible to also return the coordinates in GRCh38?
The text was updated successfully, but these errors were encountered: