Automate verification of participants

[Davinkjohnson]

@amber-emmes The first use case is getting participants to a "point-in-time" of being just after site verification.

For the created test accounts, ensure that the participant appears to have just been created and verified by a site. (for now it's not critical which site, but in the future we will want to ability to select the site.)

[sonyekere]

#838

[amber-emmes]

Both the front and back end work for this should now be available in dev; give it a spin at your convenience.

[amber-emmes]

Please confirm that this button does not appear in stage and this should be ready for stage -> prod release.

[sonyekere]

Hi @amber-emmes Can we close this issue?

[amber-emmes]

If the button is working to your satisfaction, then yes, we can.

[sonyekere]

Reopening this issue. @brotzmanmj Amber completed the participant verification reset automation in dev environment, this can be checked by the Operations team at any time.

Also as an FYI for the Jan release, automated testing will go out in the next release alongside the lower priority home mouthwash work.

Automated testing of surveys and modules will be a future task, and planning for resources and timeline allocation will be discussed.

[brotzmanmj]

Hi @sonyekere I'll ask the Ops the to check participant verification reset automation in dev.

For this item: "Also as an FYI for the Jan release, automated testing will go out in the next release alongside the lower priority home mouthwash work." If this is not automated testing of surveys and modules, then can you explain what this consists of? Thanks

[brotzmanmj]

Adding to this thread our email conversation so we can easily access where we left off:
From Nov 22: Michelle to Sandra:
I’m checking on this to be clear in what the ops team needs to do. We are asked to check this from the ops perspective to make sure the button is working as we would expect in dev.
I don’t see any requirements for this written out in github but I assume it is doing the following, and this is just off the top of my head so I’m sure not a complete list:

• Verification status – verified, date of verification = either current date or the original verification date?
• All surveys deleted, and survey flags and dates reset not started and null respectively
• All notifications deleted
• All refusal and withdrawal and data destruction reversed and reset to null/default status
• All biospecimens deleted from the Biospecimens table
• All Kit assembly data deleted from the Kit Assembly table
• All biospecimen data deleted from the Participants table and default variables related to biospecimens reset to default/null settings
• All incentive data reset to default/null settings
• They should still be consented and user profile completed, consent form and HIPAA form signed
• Anything else I may have missed.

@Onyekere, Sandra (NIH/NCI) [C] I assume all of the above were testing in dev and the ops staff are not needed to confirm all of that. Is that correct?

With that in mind, can you explain what testing is needed from the ops team to confirm this is working as expected? I’m happy to ask someone to do it if we can state the scope.

And Sandra's response:
Thanks for the detailed response. Since we anticipate revisiting automated testing in January, I’ll work with Amber to create a scope for testing in the January release. I’ll also loop in Rohan, as he could be a great asset in formalizing something that Ops can follow and use for testing.

For this release, Amber’s time is largely occupied with the mouthwash overhaul work, which will also help in building out the scope for testing the biospecimen work with automated testing. When time allows in this release cycle, I’ll schedule some time with DevOps to discuss this further and then provide Ops with more direction.

[sonyekere]

Per our discussion on 1/2/2024, I willl proceed in scheduling a touchpoint. @rohanjay10 and @amber-emmes kindly review Michelle's points above.

[rohanjay10]

Hi all, below are the notes from today's call discussion. Please let me know if anything needs to be adjusted.

Testing document containing the cids for vars being reset with before and after cid values put together by @amber-emmes @rohanjay10: https://nih.app.box.com/file/1741132227704

1/28 call with @brotzmanmj @amber-emmes @robertsamm @mnataraj92 @Davinkjohnson @rohanjay10

Tool goal: Reset pts and pt status to a point when they are freshly verified

• Currently in Dev but could be adjusted to be used in stage

• Reset of survey data, flags, user surveys, biospecimen, cancer occurrences, kit assemblies - External data. Withdrawls, refusals would be reset to default/null

• Pt data would be reset to default flags when a user is created(except for the keys the user preservers such as consent date, address, email)

• Tool would preserve verification status(whether they are verified or not)

• Currently the tool wipes User Profile history

• Previously used to test home MW, and reset PO box and physical address

Vars to incorporate

• User Profile data. Physical address/PO box there currently. Additional UP vars to be added to the list of vars to be reset, including additional UP pt 4 vars(other contact info)
  • @mnataraj92 to use the 'New vars to add in connect' incorporated into SOP, to include variables for User Profile and anything leading up to verification
• Consent
• Tool would need to be updated for new study activities or surveys
• Survey Flags(for Cancer Screening and Connect Experience) that @cunnaneaq mentioned on email would go to default, and will be added by @amber-emmes . This would need to be incorporated into the testing plan

Tool is located in the Dev SMDB pt details page where a pt would edited. Red button to reset the User

• Future set up where user is displayed the values the user has, and the values that would be reset

• Tool currently is for users who have access to the User Profile in SMDB dev in pt details page.

Sites

• Look into if sites need to have access to the reset tool, and if so explain the tool functionalities to the sites(as majority of sites do this manually, HP currently has a way to automate pt reset)
• Certain pages on SMDB such as pt withdrawal page, or certain details on pt details are not editable by sites
• NORC could also use this for testing/incentives

Testing

• Would be used for future testing for resetting test pts

• @brotzmanmj @robertsamm @mnataraj92 to use the tool to see if its working as expected and let @amber-emmes know if any vars that need to be reset, aren't getting reset

• @cunnaneaq to look into testing of the tool as initial testing was done by her

• @robertsamm and @mnataraj92 to connect with @cunnaneaq and Erin on vars to check and get feedback on the tool, and then get it into stage.
  Test Scenarios to cover a broad variety scenarios/surveys, for Active/Passive recruit cases

• Including Biospecimens, clinical collection, Home MW collections and see if they populate as expected with several notifications. Include several refusal vars to be reset and checked. New Cancer Screening Survey and Connect Experience survey flags above would also be incorporated into the testing plan

• @mnataraj92 @robertsamm to start testing of scenario and update on the Github issue
  Note: Dev Test pts in the ROI PA plan would not be used so those pts can continue to be used for existing testing

Tool development is not time sensitive.