Cancer Screening History Skip Logic Issue or Saving Issue

[KELSEYDOWLING7]

1. Skip logic for CPAP1 and CPAP2 is that CPAP=1. Connect ID 1757693819 did not select CPAP=1 but does have a response to CPAP1 and CPAP2
2. Skip logic for ENDOBIOP3 is that ENDOBIOP2 must equal 1,2,4, or 77. Connect ID 9581051759 chose 0 for ENDOBIOP2 but does have a response to ENDOBIOP3.

We were hoping Quest 2.0 would eliminate any saving issues. Is there something missing in the logic displayed here https://nih.app.box.com/file/1673745039838?s=e7xhpn3l8pm8y7bwx1ywncba6pybz53i that needs to be updated in the metrics/QC?

[joshid-ims]

1. You mean the logic has SrvScr_CERVSCREEN_v1r0 = 1?

2. "Skip logic for ENDOBIOP3 is that ENDOBIOP2 must equal 1,2,4, or 77." also includes ENDOBIOP2 = 3. Is that right?

I tried to reproduce #2 quickly and I could not. We will test one more time though.

[KELSEYDOWLING7]

@joshid-ims Apologies for the typos. Yes to both questions.

I had a feeling these may not show up on your end. I think we're still having data saving issues. Nicole was hopeful this wouldn't happen in Quest 2.0. Today I found similar issues in Module 1 as well (ethnicity answered where race wasn't selected) so I will let her know

[joshid-ims]

@KELSEYDOWLING7, is it a confirmed that it is related to data saving/Quest 2.0 issue and not a markup issue?

[KELSEYDOWLING7]

No, it's not confirmed to be related to Question 2.0. But rather that we were HOPING that IF it's a saving issue, that Quest 2.0 would resolve that issue

[boyd-mj]

@KELSEYDOWLING7 I asked Ricky to look back at our dev backend testing of this survey for the release that should currently be in production (prior to the executive order changes) and this is what he said:

In dev, I looked at all the records that had CPAP = 0 and none of them have responses for CPAP1 and CPAP2. Same for ENDOBIOP2 = 0, ENDOBIOP3 is all blank for these. So the scenarios did hit these conditions, and they behaved as expected.

So maybe Quest 2.0 has addressed it?

[KELSEYDOWLING7]

@boyd-mj The version currently in production (prior to the executive order changes) did still have these issues present in prod. I made sure to only check participants that completed CSH after the Quest 2.0 release.

I can check again for only participants completing the survey after the executive order changes, if the logic was changed for these variables