Alpha Testing - User Profile

[brotzmanmj]

Requirements for User Profile are ready for DevOps: https://nih.app.box.com/file/501193852134

Data dictionary has been updated to include User Profile variables: https://nih.app.box.com/file/497660089154

Data dictionary: Cells highlighted in yellow are changes made by Nicole. Please implement when feasible.

[brotzmanmj]

Adding link to the visio representation of the user profile: https://nih.app.box.com/file/510870927526 The word document above ("Requirements for User Profile") contains the same information in a different format: https://nih.app.box.com/file/501193852134 If any differences between the two, refer to the word "Requirements" document.

[brotzmanmj]

Allen Malone (KP) request 9/6/19 to add MRN to the User Profile for KP participants for use in identity verification. Michelle, Nicole, Alaina updating documentation on Box.

[meganstead]

Hackathon feedback from KPCO:  Recommend the account profile captures alternative method of communicating with recruit in case there are issues with the primary communication method.  In other words, if the recruit creates an account with email, then request a cell phone number and visa versa.

Notes from @brotzmanmj : Agreed- We can resolve by sharing the user profile requirements with the site when ready. However, the email provided in the user profile for contacting the participant does not need to be the same as the email they use for account log in. These are two separate things.

@ashreves - please update the user profile requirements documentation to indicate that the email address in the user profile will be populated with the email they used to create account; we will populate from the account creation but they will be allowed to edit it. Same with phone number. Please comment when documentation is updated.

[meganstead]

Hackathon feedback from KPCO: No radio buttons should be set by default. If the recruit skips the question, the answer will be incorrect.

@ashreves - please update eligibility screener requirements documentation and comment here when complete. Please also add this feedback from @brotzmanmj - user needs to be able to ‘clear’ a response.

@bhaumik55231 once requirements are update please make the appropriate configuration updates.

[meganstead]

A question regarding the ideal structure of addresses for mailing purposes arose during our internal Tuesday am meeting. I’ve compiled information from several NORC resources below. 1) Typically, the following fields are required a. First Name b. Last Name c. Address d. Addr2 (if needed) e. Apt f. City g. State h. ZIP 2) The exact format of the file (excel, CSV, text, SAS, etc.) and variable attributes (numeric, text, length) should be decided upon based on requirements from the mailing vendor (excel is quite common) 3) Usually, whether programmatic or manual, some data review is recommended prior to sharing the addresses with the mail vendor 4) At NORC, our team uses a program called Bulk Mailer to clean the addresses. Bulk Mailer has algorithms to determine “matches” when missing or incorrect data is present.

A quick example, internally for NORC, may follow the following steps: 1) Address information is pulled from our case management system into an excel file 2) Based on mailing needs, addresses are flagged or separated (e.g. certain respondents get one type of kit and others get another type of kit we would separate those address lists into separate tabs or spreadsheets) 3) Addresses are run through initial cleanup steps 4) Addresses are run through Bulk Mailer 5) Mailings use the address results from Bulk Mailer

[FrogGirl1123]

Added @FrogGirl1123 and @ruggz13 since the user profile is now being generated in the Quest app.

[bhaumik55231]

Closing this issue as the User Profile is finalized and developed.