-
Notifications
You must be signed in to change notification settings - Fork 28
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
add/edit evidence help text needs some updating #1585
Comments
It also needs to mention Functional. Predisposing needs to be removed from the first sentence. Oncogenic and Predisposing need a sentence explaining that only NA applies. |
Proposed new text for a few places: Beside Below Below Beside |
Consensus update from our group discussion (Obi, Malachi, Jason, Lana, Arpad, KK) this morning: Beside The impact of the variant for predictive, prognostic, diagnostic, or functional evidence types. For predisposing and oncogenic evidence, impact is only applied at the assertion level and N/A should be selected here. Below Below Beside |
These edits have now been pushed to staging. |
We should consider modifying the text beside Currently, it only refers to predictive, diagnostic and prognostic evidence.
|
If CIViC is supported by American funding sources, should curators be expected to familiarize themselves with U.S. definitions of PHI? My understanding is that the specific concept of PHI is a HIPPA product, which makes it somewhat U.S. specific, too. If a curator is working from a country where there's no regulation of PHI, and they submit a patients full name, we would still report it, although the curator's jurisdiction would not have an issue with it. Tangentially related: Do we want oncogenic before functional in the select Type menu, or does it not really matter? |
How about
|
|
Clinical Significance should mention the new Oncogenic evidence type
There was also some discussion in the meeting about clarifying N/A options for field combinations where that will be the only option provided.
The text was updated successfully, but these errors were encountered: