Skip to content

bug: parse VUS-mid to Uncertain Significance#5270

Open
bpblanken wants to merge 1 commit intodevfrom
benb/VUS-mid
Open

bug: parse VUS-mid to Uncertain Significance#5270
bpblanken wants to merge 1 commit intodevfrom
benb/VUS-mid

Conversation

@bpblanken
Copy link
Collaborator

No description provided.

@bpblanken bpblanken changed the title VUS mid bug: parse VUS-mid to Uncertain Significance Feb 5, 2026
).replace(
'Likely pathogenic/Likely pathogenic',
'Likely pathogenic'
).replace(
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Snippet in the XML:

    <Classifications>
      <GermlineClassification DateLastEvaluated="2026-01-22" NumberOfSubmissions="1" NumberOfSubmitters="1" DateCreated="2026-02-01" MostRecentSubmission="2026-02-01">
        <ReviewStatus>no assertion criteria provided</ReviewStatus>
        <Description>VUS-mid</Description>
        <Citation Type="general">
          <ID Source="PubMed">38484052</ID>
        </Citation>

This strategy does not handle the case where there are conflicting pathogenicities and VUS-mid is listed as one of several different classifications. The handling there is actually more restrictive than we have when parsing the top level pathogenicity.

@bpblanken bpblanken marked this pull request as ready for review February 5, 2026 20:58
@bpblanken bpblanken requested a review from hanars February 5, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant