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.

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

Ability to add tags sitewide #15

Open
wrightmw opened this issue Aug 29, 2021 · 1 comment
Open

Ability to add tags sitewide #15

wrightmw opened this issue Aug 29, 2021 · 1 comment

Comments

@wrightmw
Copy link
Member

wrightmw commented Aug 29, 2021

Tagging required in both GCI and VCI... parallel implementation.

Tag use cases:

  1. Alerts (e.g. new publication, new ClinVar entry, time for re-evaluation, etc) Auto-tags added by VCI
    • New ClinVar entry
      • Triggered by: new ClinVar entry for the variant that is a different (3-level: B/VUS/P) pathogenicity than the approved and submitted to ClinVar curation by the VCEP.
    • Re-evaluation:
      • Triggered by: 2 years from approval date for Likely Path/VUS interpretations. (Steven to check details)
  2. Bulk-tagging (e.g. VP added, ClinVar reports)
    • Added in bulk by system - triggered by curator action
    • Need two layers: 1: Action and 2: Additional info like ClinVar data, date submitted etc.
    • Need to be able to sort on both layers.
    • High priority but dependent on these features,
  3. Free text options (use case: workflow items)
    • ex: denote all variants that use data from a single paper, reviewed pending approval, awaiting patient data from lab.
    • Pre-populated set of options: Pilot Variant, Conflict Resolution, Re-curation, reasons for why variant was selected for curations.

See for scoping: https://broadinstitute.atlassian.net/browse/CSP-102
See for mockups: https://docs.google.com/presentation/d/1bhhzm8ZlkwNHGc2WI-UlcZC5m-TwDQMa5NSteG3sKwQ/edit#slide=id.g9ffe19a625_0_11

@wrightmw
Copy link
Member Author

From ClinGen/clincoded#2145
Approved VCEPs need to be able to mark an entry as "Under Review". This new status would be manually added by the curator, and should be able to be manually deleted...but otherwise by default it would be removed when a Publishing event occurs.

Note: making an interpretation status "Under Review" may need to trigger a status update message to the ERepo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants