You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we're submitting the CIViC assertions generated by the MetaKB Transformers, we should be consistent with the values we're using. Since ClinVar already defines an enum, we should follow this.
Proposed solution
Tier I -> Tier I - Strong
Tier II -> Tier II - Potential
Tier III -> Tier III - Unknown
Tier IV - Benign/Likely benign
Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
Yes, I can create a PR for this feature.
The text was updated successfully, but these errors were encountered:
Feature description
@larrybabb suggested that the CIViC transformer should use the ClinVar
clinicalImpactClassificationDescription
enum: https://github.com/ncbi/clinvar/blob/master/submission_api_schema/submission_api_schema.json#L510-L514Use case
Since we're submitting the CIViC assertions generated by the MetaKB Transformers, we should be consistent with the values we're using. Since ClinVar already defines an enum, we should follow this.
Proposed solution
Tier I -> Tier I - Strong
Tier II -> Tier II - Potential
Tier III -> Tier III - Unknown
Tier IV - Benign/Likely benign
Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
Yes, I can create a PR for this feature.
The text was updated successfully, but these errors were encountered: