# Diagnostic 00155 : ePRO controls should be configured correctly This diagnostic applies the following rules to check that ePRO controls have been configured correctly. ## Calendar - The Field should have View and/or Entry restrictions (at Field or Form level) ## NRS V2 and NRS 5 Labels - Minimum Value should be 0 - Maximum Value should be 10 - Increment should be 1 ## Form Availability and Form Availability with Date Labels - The Field Data Format should be "$100" - The Form should be a Log Form - Start Date Folder OID should be a Folder OID in the draft - Start Date Form OID should be an active Form OID in the draft - Start Date Field OID should be an active Field OID in the Start Date Form - End Date Folder OID should be a Folder OID in the draft - End Date Form OID should be an active Form OID in the draft - End Date Field OID should be an active Field OID in the End Date Form ## Body Map Joint - If Attributes enabled is "true": - Attribute 1 should have a maximum length of 20 - Attribute 2 should have a maximum length of 20 - Attribute 3 should have a maximum length of 20 ## Barcode Scanner - The Field Data Format must be text, starting with "$" ## Scheduled Form Notification - Notification Message should have a maximum length of 150 - Notification Message should not contain HTML tags - Reference Form OID should be an active Form in the draft - Delivery - % of Elapsed Open/Close Window should be an integer between 1 and 100 ## Anytime Form Notification - Notification Message should have a maximum length of 150 - Notification Message should not contain HTML tags - All fields to be completed by the eCOA user must be log Fields. Form Availability, Open/Close Window, NoCloudDisplay or fields containing a Form Settings Patient Cloud control type do not need to be log fields. ## Bristol Scale - The Field should have a Variable OID "2" - The Field should have a Control Type of "text" ## BSS7-TWB and BSS7-TWB-2 - The Field should have a Variable OID "BSS7_TWB" - The Field should have a Data Format of "$10" ## XFB - Conditional - Full folder path should be '#' or a path of valid Folder OIDs and repeat numbers, such as: - /VISIT1[1] - /CYCLE[1]/DA[2] - The Form OID of the form to be evaluated should not be empty - The Form OID of the form to be evaluated should be an active Form OID in the draft - The Field OID of the field to be evaluated should not be empty - The Field OID of the field to be evaluated should be an active Field OID in the Form ## XFB - Action - Full folder path should be '#' or a path of valid Folder OIDs and repeat numbers, such as: - /VISIT1[1] - /CYCLE[1]/DA[2] - Form OID of the target form to be evaluated should not be empty - Form OID of the target form to be evaluated should be an active Form OID in the draft - Comma separated Field OIDs should not be empty - Comma separated Field OIDs should be an active Field OID in the Form, or a list of active Fields OIDs, separated by commas - FieldOIDs specified as logical AND/OR statements to evaluate should not be empty - FieldOIDs specified as logical AND/OR statements to evaluate should contain only one "AND" clause - FieldOIDs specified as logical AND/OR statements to evaluate should contain only one "OR" clause ## Auto Advance - Folder path in which the referenced form exists should be '#' or a path of valid Folder OIDs and repeat numbers, such as: - /VISIT1[1] - /CYCLE[1]/DA[2] - Form OID of the next form in the sequence should not be empty - Form OID of the next form in the sequence should be an active Form OID in the draft ## Photo Capture - The Field Data Format should be "$255" for log fields or "$100" for standard fields - The Maximum number of photos should be an integer value ## Multi-Select Field Option - The Multi-Select Field should not have a VariableOID. - FieldOID of the containing Multi-Select Field should not be empty - FieldOID of the containing Multi-Select Field should an active Field OID in the same Form