Closed zabeen closed 1 year ago
This change can only be regression tested on AN - it needs more thorough testing on WMDA, where the issue was first reported.
Regression test:
ScoringResult.ScoringResultsByLocus
:
ScoreDetailsAtPositionOne
and ScoreDetailsAtPositionTwo
should be non-null.@zabeen It looks ok from my perspective "searchIdentifier": "163fd602-eeba-4413-a32e-b3f03e2baae0"
Once the change has been deployed to WMDA Dev, need to re-run search
8956421b-8305-463b-ac26-eea97db1350a
, and check orientation ofDRB1
scores on donors267964142
and267967416
. Position 2 should be called mismatch.
Passed - both scoring and match prediction grades had the mismatch in the DRB1_2 position
If that looks good, then release to Prod and re-run searches raised by super-users (will need search IDs for this).
Passed - re-ran case 8 from super-user testing, and DRB1 mismatch is in the expected position.
Positional scores are currently orientated to patient typing, but it makes more sense for them to be aligned to donor typing - and that is the expectation from WMDA (current AN search implementation does not care about the orientation; it does not show this data to users, only the overall grade/match count).