Closed dnil closed 2 years ago
Suggested discussion points:
Suggestion: Phenotype-based priorization of variants
Suggestion: Phenotype-based priorization of variants
Thanks! We have as you know opted to leave the phenotype out of the rank. We can discuss this again: just a brief summary of the current constraints. Prioritization/ranking is still at the pipeline stage. This means the attending clinician would have to fix the detailed phenotype up front around when ordering the case. As it is, only a panel set is (including OMIM) is typically picked before loading. The phenotype then can decide the gene list, as in either just looking at a single panel, picking genes with HPO terms and/or using phenomizer. The thinking goes that variants that are high after that phenotype-selection, would still mostly be high on a phenotype-rank. It is not trivial do devise a scoring scheme that weights phenotype matching to detailed leaf terms, broad trunk phenotype categories vs genes with more or less evidence for phenotype and contrast those quantitatively against the molecular effect of the variant. Some attempts do exist, e.g. exomiser. Do you have a particular system in mind that you like?
Software releases since previous user meeting:
password
in LDAP login formserver.blueprints.alignviewers.unindexed_remote_static
endpointserver.blueprints.alignviewers.remote_static
endpointattachment_filename
parameter renamed to download_name
when Flask 2.2 will be releasedno intervals found
warning in load_region testTP53 Database
, modified also link since IARC has been moved to the US NCI: https://tp53.isb-cgc.org/
safe_str_cmp
import from werkzeug.security
by freezing Werkzeug lib to v2.0 until Flask_login v.0.6 with bugfix is releasedlepture/authlib
Time: Jun 15, 2022 09:00 AM Stockholm Zoom link: https://ki-se.zoom.us/j/64021668001?pwd=NXZzTjBNaUZsd0pybHBTVEtLYW5Mdz09
Recent changes
Discussion points
Content prioritisation
Major release pending
Pipeline updates