Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do you plan to also represent ClinVar RCVs and VCVs in the future? #5

Open
larrybabb opened this issue Jan 9, 2023 · 1 comment
Open

Do you plan to also represent ClinVar RCVs and VCVs in the future? #5

larrybabb opened this issue Jan 9, 2023 · 1 comment
Labels
question Further information is requested

Comments

@larrybabb
Copy link
Collaborator

From Epic on Jan 4, 2023....
Do you plan to also represent ClinVar RCVs and VCVs in the future?
@larrybabb larrybabb added the question Further information is requested label Jan 9, 2023
@larrybabb
Copy link
Collaborator Author

We will be creating the VCV level (Variant Aggregation statement) in a VA statement-based format. For those interested in this please upvote this and provide a little background as to why you would want this. Please keep in mind that VCV variant aggregations are a mix of all SCV types associated with a single variation (not just the Var Path statements).

We do NOT intended to standardize on the RCV form of clinvar statements (unless someone can make a compelling case as to why that would be useful).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@larrybabb