RADplus 2022 Quarterly Release 2022.03 Acceptance Tests

• Have a modeled form, [FormA] that includes:
• "Client Picture" table column is added to the form with setting and "Allow User to Update Client Picture Image" to "Yes"
• "Signature" field object added to the form
• Setting "Form supports automatic backup" set to "Yes" in "Form Definition"
• Have a "Progress Note" form [FormB] for example the "Inpatient Progress Notes" form, that includes:
• Site-specific "Signature" field object added to the form
• "Autosave" enabled on the form
• Have three image files (for example "jpg" pictures) "Image1", "Image2" and "Image3" available for import from the server
• [UserA] has access to both [FormA] and [FormB] and the forms have been added to their "Chart" view

1. Open [FormA]
2. Select a client [ClientA]
3. Navigate to the "Signature" field
4. Click [Get Signature]
5. Populate the "Please Sign" signature box with signature [Sig1]
6. Click [OK]
7. Click [Get Signature] again
8. Populate the "Please Sign" signature box with a different signature [Sig2]
9. Click [OK]
10. Click [Get Signature] again
11. Populate the "Please Sign" signature box with a different signature [Sig3]
12. Click [OK]
13. Navigate to the "Client Picture" field.
14. Click to "Acquire Image"
15. Navigate to the folder on server containing the images stated in the set up
16. Select [Image1]
17. Validate "Image1" is displayed in the "Client Picture" field
18. Repeat step c, this time selecting [Image2]
19. Validate results are as expected
20. Repeat step c, this time selecting [Image3]
21. Validate results are as expected.
22. Populate any other desired fields, making note of the values entered
23. Click the [Backup] form button
24. Click to exit the form
25. Open [FormA]
26. Select a client [ClientA]
27. Validate a message displays: "You have an unsubmitted backup of this data record. Do you wish to restore from the backup?"
28. Click [Yes]
29. Navigate to the "Signature" field
30. Validate the field is populated with the last signature signed[Sig3], as expected
31. Navigate to the "Client Picture" field
32. Validate the field is populated with the imported [Image3], as expected
33. Validate all other fields are populated as expected
34. Submit the form
35. Return to [FormA]
36. Select a client [ClientA]
37. Select the row just submitted
38. Navigate to the "Signature" field
39. Validate the field is populated with the last signature signed[Sig3], as expected
40. Navigate to the "Client Picture" field
41. Validate the field is populated with the imported [Image3], as expected
42. Validate all other fields are populated as expected
43. At the home view, right-click on [ClientA] to go to their "Chart"
44. Select [FormA] in the forms list
45. Validate the row submitted in step 3 is present
46. Locate to the "Signature" field
47. Validate the field is populated with the last signature signed[Sig3], as expected
48. Locate to the "Client Picture" field
49. Validate the field is populated with the imported [Image3], as expected
50. Validate all other fields are populated as expected
51. Repeat steps 1 thru 4 for the [FormB] that contains the signature field
52. Validate results are as expected

• Have a modeled form, [FormA] that includes:
• "Client Picture" table column is added to the form with setting and "Allow User to Update Client Picture Image" to "Yes"
• "Signature" field object added to the form
• Setting "Form supports automatic backup" set to "No" in "Form Definition"
• Have a "Progress Note" form [FormB] for example the "Inpatient Progress Notes" form, that includes:
• Site-specific "Signature" field object added to the form
• "Autosave" is not enabled on the form
• Have three image files (for example "jpg" pictures) "Image1", "Image2" and "Image3" available for import from the server
• [UserA] has access to both [FormA] and [FormB] and the forms have been added to their "Chart" view

1. Open [FormA]
2. Select a client [ClientA]
3. Navigate to the "Signature" field
4. Click [Get Signature]
5. Populate the "Please Sign" signature box with signature [Sig1]
6. Click [OK]
7. Click [Get Signature] again
8. Populate the "Please Sign" signature box with a different signature [Sig2]
9. Click [OK]
10. Click [Get Signature] again
11. Populate the "Please Sign" signature box with a different signature [Sig3]
12. Click [OK]
13. Navigate to the "Client Picture" field.
14. Click to "Acquire Image"
15. Navigate to the folder on server containing the images stated in the set up
16. Select [Image1]
17. Validate "Image1" is displayed in the "Client Picture" field
18. Repeat step c, selecting [Image2]
19. Validate results are as expected
20. Repeat step c, selecting [Image3]
21. Validate results are as expected.
22. Populate any other desired fields, making note of the values entered
23. Submit the form
24. Open [FormA]
25. Select a client [ClientA]
26. Navigate to the "Signature" field
27. Validate the field is populated with the last signature signed[Sig3], as expected
28. Navigate to the "Client Picture" field
29. Validate the field is populated with the imported [Image3], as expected
30. Validate all other fields are populated as expected
31. Exit the form
32. At the home view, right-click on [ClientA] to go to their "Chart"
33. Select [FormA] in the forms list
34. Validate the row submitted in step 2 is present
35. Locate to the "Signature" field
36. Validate the field is populated with the last signature signed[Sig3], as expected
37. Locate to the "Client Picture" field
38. Validate the field is populated with the imported [Image3], as expected
39. Validate all other fields are populated as expected
40. Repeat steps 1 thru 3 for the [FormB] that contains the signature field
41. Validate results are as expected

• Have a state form definition file [DefA], created in form "State Form Definition"
• Have an "FTP Server" set up to receive files
• Have the following "FTP Server" information available in order to populate the "State Form Task Scheduler" form during testing:

1. The "Service Directory" location
2. The "Server Host Name"
3. The "Server Port Number"
4. The "Server Username" field
5. The "Server Password" field
6. The "Public Key File" and the folder location of the file
7. The "Private Key File" and the folder location of the file

1. Open form "State Form Definition"
2. Select [DefA]
3. Populate the "File Path" field with directory that exists on the logged in users server; [LocationA]
4. Submit the form
5. Validate the form files successfully
6. Open the 'State Form Task Scheduler' form
7. Select [DefA]
8. Select "Yes" in the "Create File" field
9. Select "Yes" in "Send File To FTP Server" field
10. In the "FTP Type" field, select "SFTP - Key Pair"
11. Populate the "Server Host Name" field
12. Populate the "Server Port Number" field
13. Populate the "Server Username" field
14. Populate the "Server Password" field
15. Populate the "Service Directory" field, this is folder location [FTPfolderA] on the FTP server where the file will be sent
16. Populate the "Public Key File Location" field
17. Populate the "Private Key File Location" field
18. Click [Test FTP Connection]
19. Validate test is successful
20. Submit the form
21. Validate the form files successfully
22. Open form "System Task Scheduler"
23. Select the task set up for [DefA] in step 2 from the "Schedule(s)" field
24. Populate the "Recurrence Pattern" field with desired value
25. Populate the "Task Occurrence" field with the desired value
26. Populate the "Start By" field with the desired date for the task to start
27. Populate the "Start Time" field with the desired time for the task to start
28. Select "No" in the "Inactive Task" field
29. Click [Schedule Task]
30. Close the form
31. When the scheduled start by date and time for task filed in step 3 has passed:
32. Validate the state form file [DefA] exist in the folder [LocationA] on the logged in users server, set in step1
33. Validate the state form file [DefA] exists in the folder [FTPfolderA] on the "FTP" server, set in step 2

• Have an environment that contains an Avatar "Database" server and also an "ECP" server configured by Netsmart with the database server as its "Remote" database server
• Have a state form definition file created in form "State Form Definition" [DefA]
• In form "State Form Definition", select [DefA] and note the definition ID# [IDNum], in parentheses next to the file name
• Have a report or query that can display data in the "SYSTEM.RADplus_sf_audit_record" table [ReportA]

1. Open form "State Form Definition"
2. Select [DefA]
3. Populate the "File Path" field with directory that exists on the users local server
4. Submit the form
5. Open the 'State Form Task Scheduler' form
6. Select [DefA]
7. Select "Yes" for Create File
8. Populate any other required fields
9. Submit the form
10. Validate the form files successful
11. pen form "System Task Scheduler"
12. Select the task set up for [DefA] in step 2 from the "Schedule(s)" field
13. Populate the "Recurrence Pattern" field with desired value
14. Populate the "Task Occurrence" field with the desired value
15. Populate the "Start By" field with the desired date for the task to start
16. Populate the "Start Time" field with the desired time for the task to start
17. Select "No" in the "Inactive Task" field
18. Click [Schedule Task]
19. Close the form
20. When the scheduled date and time for task filed in step 2 has passed
21. Run [ReportA] to display data in the "SYSTEM.RADplus_sf_audit_record" table
22. Validate a row is present for the state form definition file, [DefA]
23. Validate the "FileID" column is populated with definitions ID number [IDNum], noted in the setup
24. Validate the "Server" field is populated with expected "FTP" server name, indicating that the file compiled on that server as expected

• Have an "XML" type "State Form Definition" file created that contains a main record and multiple sub-records. [Def1]

1. Open form "State Form File Generation"
2. Select the [Def1] definition in field "State Form"
3. In the "File Generation Options" field, select "Compile"
4. Click [Process]
5. Validate the process completes successfully
6. In the "File Generation Options" field, select "Create File on Server"
7. Click [Process]
8. Click the "Compile Complete", [OK] button
9. Click [Process] to create a file on the server
10. In the "Windows Explorer" window, navigate to a folder location and save the file
11. In the "Save In" drop down list of File Explorer, select a directory and populate the "File Name"
12. Click [Save]
13. In "File Explorer", go to the directory where the file was saved
14. Click to open the file
15. Validate the contents are as expected

• Have user [UserA] that has "Double Quotes" populated in the "User Description" field of their "User Definition" form record
• Have user [UserB] that has an "Apostrophe" populated in the "User Description" field of their "User Definition" form record
• Have user [UserC] that has any other special character populated in the "User Description" field of their "User Definition" form record
• Have user [UserD] that has no special characters in their name
• Have a "State Form Definition" file defined [DefinitionA], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "GROUP BY" command with the statement
• Log in as [UserA]

1. Open form "State Form File Generation".
2. Select definition [DefinitionA] in field "State Form".
3. Populate the "File Description" field.
4. In the "File Generation Options" field, select "Compile".
5. Click [Process].
6. Validate the process completes successfully.
7. In the "File Generation Options" field, select "Dump File".
8. Click [Process].
9. Validate the data output of the file is as expected
10. Log out as [UserA]
11. Log in as [UserB]
12. Repeat step 1
13. Validate results are as expected
14. Log out as [UserB]
15. Log in as [UserC]
16. Repeat step 1
17. Validate results are as expected

• Have a client [ClientA], that's currently admitted in two episodes. [Episode1] and [Episode2]
• Have a state form definition file [StateFormDefA] created that extracts the "Episode" number from the "SYSTEM.admission_data" table
• Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as an "Episode" number field on the form
• In form "State Form Button Mapping", have the following prompts populated with the form submitted
• [PopButtonA] selected in the "Button Field"
• [StateFormDefA] selected in the "State Form Definition" field
• "Episode Number" selected in the "Parameter Field 1" field
• "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic so that when the button is clicked, it will run state form definition file [StateformDefA] to populate "Episode" number field on [FormA], with the current selected episode

1. Open [FormA]
2. Select the desired client [ClientA]
3. Select [Episode1]
4. Click the [PopulateA] button, set up on the form
5. Validate the [Episode] field contains the expected selected episode, [Episode1]
6. Click [Submit]
7. Validate the form files successfully
8. Return to [FormA]
9. Select [Episode1]
10. Select [ClientA]
11. Validate the [Episode] field contains the expected selected episode, [Episode1]
12. Close the form
13. pen [FormA]
14. Select the desired client [ClientA]
15. Select [Episode2]
16. Click the [PopulateA] button, set up on the form
17. Validate the [Episode] field contains the expected selected episode, [Episode2]
18. Click [Submit]
19. Validate the form files successfully
20. Return to [FormA]
21. Select [Episode2]
22. Select [ClientA]
23. Validate the [Episode] field contains the expected selected episode, [Episode2]
24. Close the form

• Have a modeled form [FormA], that includes the following field types: "Name" field [NameA] ;"Date" field [DOB] ; "Dictionary" field [FieldA], Dictionary field [FieldB] and "ScriptLink" button [PopulateA]
• [FormA] has event logic set on a field [FieldA] that will set [FieldB] to be required when specific value [Value1], is selected in [FieldA]
• Have a "State Form Definition" file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
• Have the "State Form Button Mapping" form submitted with following values populated:
• [PopulateA] selected in the "Button Field"
• [StateFormDefA] is selected in the "State Form Definition" field
• [FieldA] is selected in the "Parameter Field1" field
• [FieldB] is selected in the "Parameter Field2" field
• "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic to run state form definition file [StateformDefA] to then populate field values on [FormA] and also trigger any expected event logic

1. Open [FormA]
2. Select [ClientA]
3. Click the [PopulateA] button, set up on the form
4. Validate the [Name] field contains the expected name for [ClientA]
5. Validate the [Date] field contains the date of birth for [ClientA]
6. Validate [FieldA] is populated with [ValueA], the trigger value for the event logic
7. Validate [FieldB] is set to be 'Required', as expected
8. Deselect any values selected in the field
9. Submit the form
10. Validate a message indicating [FieldB] is not populated is displayed
11. Select a value in [FieldB]
12. Submit the form
13. Validate the form files successfully
14. Return to [FormA]
15. Select [ClientA]
16. Validate fields all are populated as expected

• Have a modeled form [FormA] that contains a primary table [TableA] and a second table[TableB],
• Have two fields defined in each table, for this example a "Date" field [FieldA] and a "Multi-Select" dictionary field [FieldB], that is set to be initially 'Disabled', exist in each table
• Have a modeled form that contains [TableA] in the first section of the form and [TableB] in the second section
• In each section, set [FieldA] with following event logic:
• 'Type of Event' set to 'Result of Input with Value Checking'
• 'Compare with for Event' set to 'Other Tabled Column'
• 'Table Column for Comparison' set to 'Data_Entry_Date' (Note: this is always the (current date) at the time of new row data entry)
• 'Comparison Value to Trigger Event' set to 'Less Than'
• 'Required' set to [FieldB]

1. Open "Form Definition" and select [FormA]
2. Click the first section of the form
3. Click the "Object Def" tab
4. Select [FieldA]
5. Click to the "Event Definition" section
6. Select the event created in the set up
7. Validate the field and field values selected for the event defined in the set up, are all populated as expected
8. Click the second section of the form
9. Click the "Object Def" tab
10. Select [FieldA]
11. Click to the "Event Definition" section
12. Select the event created in the set up
13. Validate the field and field values selected for event defined in the set up, are all populated as expected
14. Close the form
15. Open [FormA]
16. Click to "Add" a new row
17. Click to the first section of the form
18. Validate [FieldB] is not required, as expected
19. Enter a date in [FieldA] that is greater than or equal to today's date
20. Validate [FieldB] is still not required
21. Enter a date in [FieldA] that is less than today's date
22. Validate [FieldB] is now required, as expected
23. Click to the first section of the form
24. Validate [FieldB] is not required, as expected
25. Enter a date in [FieldA] that is greater than or equal to today's date
26. Validate [FieldB] is still not required
27. Enter a date in [FieldA] that is less than today's date
28. Validate [FieldB] is now required, as expected

• Have a system with prompt "Include Supplemental Information within User Definition" to "Yes" in form "System security defaults"
• In form "User Definition" have an existing user [UserA] who is assigned to a user role [RoleA] and has "Date of Hire" and "Date of Birth" prompts populated on the "Supplemental" section of the form.
• Have a "User File Import" file created [UserFileA] that includes:
• [UserA] set with a different user role [RoleB] to be updated in the "User Role" field
• A new user [UserB], with the "User Role" field populated with any valid user role. For this test [RoleA] is used

1. Open the 'User File Import' form.
2. Click [Select User Import File]
3. Navigate to the location of [UserFileA] and select the file
4. Click [Open].
5. Validate the scan results display messages, "Warning: Row 1 contains an existing User ID which will be edited on import (UserA)" and "Warnings but no errors detected in import file. Import may proceed"
6. Click [Process User Import File]
7. Validate there are no errors
8. Click [OK].
9. Validate the import completes successfully
10. Open form "User Definition"
11. Select [UserA] in the "Select User" field
12. Validate the user is not assigned to user role [RoleB], as expected
13. Click "Supplemental" section of the form
14. Validate "Date of Hire" and "Date of Birth" prompts are populated, as expected
15. Select [UserB] in the "Select User" field
16. Validate the user is assigned to user role [RoleA], as expected

• Have a Modeled [TableA] which is includes:
• Fields added that will be mapped in the "Service Documentation" section of "Table Definition" that required for service documentation functionality. These include: "Data Row for", "Date of Service", "Service Start Time", "Service End Time", "Service Duration", "Location" "Service Program", "Service Charge". "Service Practitioner" and "Draft/Final" fields
• Any other desired added that are "not" mapped for service documentation functionality
• [FormA] contains both the fields that are mapped for "Service Documentation" and also those are not

1. Select [ClientA]
2. Open [FormA]
3. Set the "Documentation For" field to "New Service
4. Set the "Draft/Final" field to "Final"
5. Validate a message is displayed indicating there are required fields on the form that are not populated and the fields are listed
6. Click [OK]
7. Validate the "Draft/Final" field is set back to "Draft"
8. Select a program in the "Service Program" field
9. Select a service code in the "Service Charge Code" field
10. Select a location in the "Service Location" field
11. Select a practitioner in the "Service Practitioner" field
12. Set the "Service Start Time" to the current time
13. Set the "Service End Time" to a time prior to the current time
14. Set the "Service Duration(Minutes) field to "30""
15. Set the "Draft/Final" field to "Final"
16. Validate a message is displayed indicating the required field "Date of Service" is not populated
17. Click [OK]
18. Validate the "Draft/Final" field is set back to "Draft"
19. Populate the "Date of Service" field
20. Set the "Draft/Final" field to "Final"
21. Validate an error is displayed indicating that the service end time must be after the service start time
22. Click [OK]
23. Validate the "Draft/Final" field is set back to "Draft"
24. Set the "Service Start Time" to one hour earlier than the current time
25. Set the "Service End Time" to the current time
26. Set the "Draft/Final" field to final
27. Validate an error is displayed indicating that time between the service start date and end date is "60" minutes but the "Service Duration(Minutes) field to set to "30"
28. Click [OK]
29. Validate the "Draft/Final" field is set back to "Draft"
30. Set the "Service Duration(Minutes)" field to "60"
31. Set the "Draft/Final" field to "Final"
32. At the "Confirm" dialog, click [OK]
33. Click [Submit]
34. Validate the form files successfully
35. Return to [FormA] and select [ClientA]
36. Edit the row just submitted
37. Validate all fields are populated, as expected

• Have a Modeled [TableA] which is includes:
• Fields added that will be mapped in the "Service Documentation" section of "Table Definition" that required for service documentation functionality. These include: "Data Row for", "Date of Service", "Service Start Time", "Service End Time", "Service Duration", "Location" "Service Program", "Service Charge". "Service Practitioner" and "Draft/Final" fields
• Any other desired fields that are "not" mapped for service documentation functionality. For this test a "Date", "Scrolling Text", "Picture" and "Dictionary" fields are used.
• Have one of the fields set to be required, for the test the "Dictionary" field is set to be required.
• [FormA] contains [TableA] but "only" contains the fields that are "not" mapped for service documentation on the form

1. Select [ClientA]
2. Open [FormA]
3. Populate just the "Date" field
4. Set the "Draft/Final" field to "Final"
5. Validate a message indicating "Dictionary" field is required and is not populated
6. Click [OK]
7. Validate the "Draft/Final" field is set back to "Draft"
8. Populate the "Scrolling Text" field
9. Populate the "Client Picture" field
10. Set the "Draft/Final" field to "Final"
11. Validate a message indicating "Dictionary" field is required and is not populated
12. Click [OK]
13. Validate the "Draft/Final" field is set back to "Draft"
14. Populate the "Dictionary" field
15. Set the "Draft/Final" field to "Final"
16. Validate there are no messages
17. Click [Submit]
18. Validate the form files successfully
19. Return to [FormA] and select [ClientA]
20. Edit the row just submitted
21. Validate all fields are populated, as expected

• Have a testing client [ClientA] with two episodes.
• Episode "1" is an open episode
• Episode "2" is a discharged episode
• Have Registry Setting "Add Date of Death and Reason for Death to Discharge" Set this to "Yes"
• In PM "Dictionary Update", select the "Client" database and search for dictionary "970"(Type of Discharge)
• Edit dictionary code "3 (Death)" and click to the extended attribute section
• In the "Extended Dictionary Element" field, select "Discharge Due to Death?" and ensure its set to "Yes"
• In form "Client Lookup/Header Configuration" go to the "Client Header" section:
• Have fields "Location", "Attending Practitioner", "Admitting Practitioner" included as part of the Client Header.

1. Select [ClientA]
2. Open the " Discharge" form and select the discharged Episode "2"
3. Ensure "Date of Death" and "Reason for Death" are present, initially not required and disabled.
4. Change "Type of Discharge" to "Death"
5. Validate "Date of Death" and "Reason for Death" enable.
6. Enter a "Date of Death"
7. Enter a "Reason for Death"
8. Submit the form
9. Select [ClientA]
10. Select episode "1" in the "Episodes" drop down list on the home view
11. Right-click on the client to open "Chart"
12. Validate the calculated "Age" value displayed in the client header, is a factor of the clients "Date of Death" entered in step1 minus the client "Date of Birth"
13. Validate fields "Location", "Program", "Attending Practitioner" are populated as expected in client header, since this is an episodic form
14. Close the "Chart"
15. Select episode "2" in the "Episodes" drop down list on the home view
16. Right-click on the client to open "Chart"
17. Validate the calculated "Age" value displayed in the client header, is a factor of the clients "Date of Death" entered in step1 minus the client "Date of Birth"
18. Validate fields "Location", "Program", "Attending Practitioner" are populated as expected in client header, since this is an episodic form
19. Close the "Chart"
20. For [ClientA] open the non-episodic form
21. Validate the calculated "Age" value displayed in the header, is a factor of the clients "Date of Death" entered in step1 minus the client "Date of Birth".
22. Validate fields "Location", "Program", "Attending Practitioner" are 'not' populated as expected in client header, since this is an episodic form
23. For [ClientA] open the "episodic" form for open episode, episode "1"
24. Validate the calculated "Age" value displayed in the header, is a factor of the clients "Date of Death" entered in step1 minus the client "Date of Birth"
25. Validate fields "Location", "Program", "Attending Practitioner" are populated as expected in client header, since this is an episodic form
26. For [ClientA] open the "episodic" form for discharged episode, episode "2"
27. Validate the calculated "Age" value displayed in the header, is a factor of the clients "Date of Death" entered in step1 minus the client "Date of Birth"
28. Validate fields "Location", "Program", "Attending Practitioner", are populated as expected in client header, since this is an episodic form

• Have a user role defined in form "User Role Definition" with prompt "User Role For Emergency Access Only" set to "Y".
• Have a user who is assigned to the emergency access role [UserA]
• Have a client that can be used to test the user's blocked client access. [ClientA]
• Prompt "Emergency Access" has been enabled in form "Emergency Access"

1. Open form "Block Client Chart"
2. Click the "Blocked Clients" tab
3. Click [Add New Item]
4. In the "Select Client" field select [ClientA]
5. In the "Allow Emergency Access for User/User Role", select "Yes"
6. In the "Block Users" field, select "Yes-Selected"
7. In the "Selected Users" field, select [UserA]
8. Click [Submit]
9. Validate the form files successfully
10. Open the "Block Client Chart" form
11. Click the List Blocked Clients button
12. Validate [ClientA] is present on the report
13. Click the Close Report button
14. At the home view, search and select [ClientA]
15. Validate the Block Client Dialog - Message text contains "[ClientA] chart is blocked."
16. Click 'Cancel'
17. Validate the user is returned to the client search prompt
18. Select [ClientA] again
19. Validate the Block Client Dialog - Message text contains "[ClientA] chart is blocked." is displayed again, as expected
20. In the "Why are you accessing [ClientA]", text box, populate a reason
21. Click [OK]
22. Open any client based form, for example "Update Client Data"
23. Validate the form opens
24. Validate [ClientA] is displayed in the form
25. Close the form

• Have or create a user [UserA] in form "User Definition", that includes a period "." in their "UserID"
• Have or create another user [UserB] in form "User Definition", that does not include a period "." in their "UserID"

1. Open the "Manage Observer Caseload" form
2. Select [UserA] in the "Select User" field
3. Click the "Caseload" radio button
4. Click "Add" in the "Add or Remove Client From Caseload" field
5. Select a client [ClientB], from the "Unit" field or by using the "Client" search field
6. Click the [Upload Caseload] button.
7. Validate the "Current Caseload" field contains [ClientA]
8. Select [UserB] in the "Select User" field
9. Click the "Caseload" radio button
10. Click "Add" in the "Add or Remove Client From Caseload" field
11. Select a client [ClientB], from the "Unit" field or by using the "Client" search field
12. Validate the "Current Caseload" field contains [ClientB]
13. Exit the form
14. Open form "Change UserID"
15. Select [UserA] in the "User" field
16. Populate the "New User ID" field with a new user ID [UserC]
17. Submit the form
18. Validate the form files successfully
19. Return to the form
20. Select [UserB] in the "User" field
21. Populate the "New User ID" field [UserD]
22. Submit the form
23. Validate the form files successfully
24. Open the "Manage Observer Caseload" form
25. Search for [UserA]
26. Validate [UserA] is not found
27. Search for [UserC]
28. Validate [UserC] the users new ID, is found
29. Validate [ClientA] added in step 1 displays in the "Current Caseload" field, as expected
30. Search for [UserB]
31. Validate [UserB] is not found
32. Search for [UserD]
33. Validate [UserD] the users new ID, is found
34. Validate [ClientB] added in step 1 displays in the "Current Caseload" field, as expected

• Have two clients on the system [ClientA] is identified as the "Target" client for the client merge and [ClientB] is identified as the "Source" client for the merge
• [ClientA] is admitted in [Episode1], [ProgramA] on [DateA]
• [ClientB] is admitted in [Episode1], [ProgramA] on a later date [DateB]
• A row [RowA] has been filed in [FormA], for [ClientA] on [DateA]
• A row [RowB] has been filed in [FormA], for [ClientB] on [DateB]
• Have registry setting "Allow Merging of All Client Data Through Single Filing" set to "Yes"
• Have registry setting "Allow Merging Into Existing Episode" set to "No"
• Have access to a database program and table permissions to run an "SQL" query on the "SYSTEM.RADplus_event_log" table

1. Open the 'Client Merge' form.
2. Enter [ClientB] in the 'Source Client' field.
3. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
4. Enter [ClientA] in the 'Target Client' field.
5. Select "No" in the 'Create New Episode On Merge' field.
6. Click [File].
7. Validate a "Client Merge" message is displayed stating: Do you wish to continue with the indicated action?
8. Click [Yes].
9. Validate a "Client Merge" message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
10. Click [OK].
11. Close the form.
12. At the home view, search for [ClientB] in the "Search Clients" field
13. Validate [ClientA] is not found
14. At the home view, search for [ClientA] in the "Search Clients" field
15. Open [FormA]
16. Validate there are now two episodes displayed [EpisodeA] and [EpisodeB]
17. Select [EpisodeB]
18. Validate the merged row [RowB] from [ClientB] on [DateB] is displayed for selection, as expected
19. Select [RowB]
20. Validate data is displayed as expected
21. Close the form
22. Run the following SQL Query for [ClientB]: "SELECT ID, application, entity_database_code, entity_id, EPISODE_NUMBER, event_date,event_time, event_type, system_code, USERID FROM SYSTEM.RADplus_event_log WHERE FACILITY = [applicable Facility number associated to logged in System Code] AND entity_id = [ClientB]"
23. Validate the results first include two entries, "Entry Copied" and "Entry Deleted" for client merge transaction process itself. Then following that, the "Data Copied" and an "Entry Deleted" records for [Row1], which was merged from [ClientB] to [ClientA]
24. For example:

ID......... Application..EntityType..............EntityID.Epis. .EventDate/Time..........Event Type

507937.. Avatar PM. PATIENT... ............602.......1. ........8/12/2022..2:30 PM.....Data Copied

507939.. Avatar PM. PATIENT................602.......1..........8/12/2022..2:31 PM.....Entry Deleted

507942.. Avatar PM. USER_DEFINED....602.......1..........8/12/2022..2:31 PM.....Data Copied

507943.. Avatar PM. USER_DEFINED....602 ......1..........8/12/2022..2:31 PM.....Entry Deleted

• Have two clients on the system [ClientA] is identified as the "Target" client for the client merge and [ClientB] is identified as the "Source" client for the merge
• [ClientA] is admitted in [Episode1], [ProgramA] on [DateA]
• [ClientB] is admitted in [Episode1], [ProgramA] on a later date [DateB]
• A row [RowA] has been filed in [FormA], for [ClientA] on [DateA]
• A row [RowB] has been filed in [FormA], for [ClientB] on [DateB]
• Have registry setting "Allow Merging of All Client Data Through Single Filing" set to "Yes"
• Have registry setting "Allow Merging Into Existing Episode" set to "Yes"
• Have access to a database program and table permissions to run an "SQL" query on the "SYSTEM.RADplus_event_log" table

1. Open the 'Client Merge' form.
2. Enter [ClientB] in the 'Source Client' field.
3. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
4. Enter [ClientA] in the 'Target Client' field.
5. Select "No" in the 'Create New Episode On Merge' field.
6. Click [File].
7. Validate a "Client Merge" message is displayed stating: Do you wish to continue with the indicated action?
8. Click [Yes].
9. Validate a "Client Merge" message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
10. Click [OK].
11. Close the form.
12. At the home view, search for [ClientB] in the "Search Clients" field
13. Validate [ClientA] is not found
14. At the home view, search for [ClientA] in the "Search Clients" field
15. Open [FormA]
16. Select [EpisodeA]
17. Validate the data for row [RowA] field for [ClientA] on [DateA] is displayed for selection
18. Validate the merged row [RowB] from [ClientB] on [DateB] is also displayed for selection, as expected
19. Select [RowB] for edit
20. Validate date is filed as expected
21. Close the form
22. Run the following SQL Query for [ClientB]: "SELECT ID, application, entity_database_code, entity_id, EPISODE_NUMBER, event_date,event_time, event_type, system_code, USERID FROM SYSTEM.RADplus_event_log WHERE FACILITY = [applicable Facility number associated to logged in System Code] AND entity_id = [ClientB]"
23. Validate the results first include two entries, "Entry Copied" and "Entry Deleted" for client merge transaction process itself. Then following that, the "Data Copied" and an "Entry Deleted" records for [Row1], which was merged from [ClientB] to [ClientA]
24. For example:

ID......... Application..EntityType..............EntityID.Epis. .EventDate/Time..........Event Type

507937.. Avatar PM. PATIENT... ............602.......1. ........8/12/2022..2:30 PM.....Data Copied

507939.. Avatar PM. PATIENT................602.......1..........8/12/2022..2:31 PM.....Entry Deleted

507942.. Avatar PM. USER_DEFINED....602.......1..........8/12/2022..2:31 PM.....Data Copied

507943.. Avatar PM. USER_DEFINED....602 ......1..........8/12/2022..2:31 PM.....Entry Deleted

• Have a system with multiple root system codes defined.
• [UserA] has access to the "Form Designer" form
• [UserA] access to the following forms:
• 'Table Definition', 'Form Definition', 'Envelope Definition', 'Report Definition', 'Site Specific Section Modeling' and any other desired forms
• [UserA] is logged any desired root system code

1. Open form "Form Designer"
2. From the "Forms" list, select any desired form
3. Select any section from the "Sections" tab
4. Validate field "Other System Codes to File Form Designer Changes to" contains all other valid root systems codes, displayed as expected
5. Click back to the "Forms" list and validate the following forms are present for selection in the drop down list:
6. 'Table Definition'
7. 'Form Definition'
8. 'Envelope Definition'
9. 'Report Definition'
10. 'Site Specific Section Modeling'
11. Select each form in step c
12. Click [Show Section]
13. Select each section listed for the form for edit:
14. Validate the form layout is displayed as expected
15. Click [Save]
16. Validate the section saved successfully
17. Click [Submit]
18. Validate the "Form Definition" form is saved successfully

• Have a system where the cache server resides in a different time zone than the client's workstation. For example, cache server rides in "Central" time zone, users workstation is in "Eastern" time zone.
• In the 'Registry Settings' form, set registry 'Utilize Local Workstation Time Zone' setting to "Y".
• Open any form [FormA] in "Form Designer" and make any change to the field layout on the form. [FDChange1].
• Note the current layout of the form and the current date and time.
• Submit the form.

1. Open the 'Form Designer' form.
2. Select [FormA] from the 'Forms' field.
3. Select the desired section.
4. Click [Show Section].
5. Validate the changes made [FDChange1] in the setup, are present.
6. Make another change to form field layout. [FDChange2].
7. Note the current layout of the form and the current date and time.
8. Submit the form.
9. Repeat steps 1 thru 4.
10. Validate the changes made [FDChange2] in the setup, are present on the form layout.
11. Click [Cancel] then [Yes] to go back to the main section.
12. In the "Revert To Other Form Designer Copy" select "Yes".
13. Click the "Select Copy to Revert to" drop down list.
14. Locate the row of the last change made [FDChange2].
15. Validate the timestamp for that row is consistent with the data and time noted in step 6.
16. Locate the row of form designer change made in the setup [FDChange1].
17. Validate the timestamp for that row is consistent with the data and time noted in setup.
18. Select that row.
19. Submit the form.
20. On the home view, search for [FormA].
21. Open the form.
22. Validate the form layout of the form is consistent with the layout [FDChange1], reverted to in step 11.

• Have access to the "Form Definition" form in the "PM" namespace and any child namespace
• Have access to the "Form Designer" form in the "PM" namespace and any child namespace
• Have access to any modeled form in each namespace [FormA]
• In each namespace, open "Form Definition" and select [FormA], make a note the following:
• In "Event Definition" section, note the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Hide" and "Unhide" fields

1. Open form "Form Designer"
2. From the "Forms" drop down list, select "Form Definition"
3. Select the "Event Def." section from the "Sections" field
4. Navigate to the "Select Copy to Revert to" field.
5. Select "Netsmart Produced Changes". (Please Note: This selection will revert the section to the latest Netsmart product design layout for the section. Note: In the event the user wants to revert to the previous layout after submission, the user can return and select the previous layout from the "Select Copy to Revert to" field drop down list and restore it back)
6. Click [Submit]
7. Validate the form files successfully
8. Navigate back to the "Form Definition"
9. Select [FormA]
10. Navigate to the "Object Definition" and select a field to edit
11. Click the "Event Def" section on the left side
12. Scroll down and observe the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Lock", "Unlock" and "Fields for Summation" fields
13. Validate the size of the box containing the dictionary values of the fields noted in the set up has increased and more dictionary values are now visible, if applicable. (Note: the increase is approximately twice the original size)
14. Close the form
15. Repeat steps 1 and 2 in any child namespaces
16. Validate results are as expected

• Have a system with “Netsmarts "(NIAM) Netsmart’s Identity and Access Management" functionality” configured.
• In form "User Definition",:
• User [ExternalA] has is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
• User [ExternalA] is assigned to a user role with "SQL" Table access in form "User Definition"
• User [NoExternalA] is assigned is set with prompt 'Use External Login' to 'No' and is assigned to any user role
• Have access to form "Change User ID"
• Have access to program "SoapUI" to execute web services
• Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user

1. Open "SoapUI"
2. Navigate to the "WEBSVC.UserManagement" web service
3. Locate the <UserID> field in the "UpdateUser" request configured in the set up
4. Populate the field with the UserID for [UserA]
5. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
6. Click the "Submit Request" arrow to execute the web service
7. Validate the 'Message' field in the response section states: "User [UserA] was successfully updated"
8. Open form "User Definition"
9. Select [UserA]
10. Locate the field that was updated in step 1
11. Validate the field updated via the web service in step1, contains the new value [NewValueA]
12. Navigate back to the "WEBSVC.UserManagement" web service
13. Locate the <UserID> field in the "UpdateUser" request configured in the set up
14. Populate the field with the UserID for [UserB]
15. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
16. Click the "Submit Request" arrow to execute the web service
17. Validate the 'Message' field in the response section states: "User [UserB] was successfully updated"
18. Open form "User Definition"
19. Select [UserB]
20. Locate the field that was updated in step 3
21. Validate the field updated via the web service in step 3, contains the new value [NewValueA]
22. Navigate back to the "WEBSVC.UserManagement" web service
23. Locate the <UserID> filed in the "UpdateUser" request configured in the set up
24. Populate the field with the UserID for [UserC]
25. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
26. Click the "Submit Request" arrow to execute the web service
27. Validate the 'Message' field in the response section states: "User [UserC] was successfully updated"
28. Open form "User Definition"
29. Select [UserC]
30. Locate the field that was updated in step 5
31. Validate the field updated via the web service in step4, contains the new value [NewValueA]

• Have a view defined in form "View Definition" [TestViewA] with one or more widgets assigned to the view
• Have two existing widgets [WidgetA] and [WidgetB] hat have the same widget name, that are not assigned yet to [TestViewA]. For this test:
• [WidgetA] is the Netsmart product widget "Financial Eligibility (NTST_FINANCIAL ELIG)"
• [WidgetB] is the console widget "Financial Eligibility [PATIENT500]". This widget can be created using the "Console Widget Configuration" form and selecting "Financial Eligibility [PATIENT500]" from the prompt "Form to Create Widget For" and then submitting the form
• [ClientA] has data filed in form "Financial Eligibility"
• Have two users [UserA] and [UserB]
• [UserA] has access to form "View Definition"
• [TestViewA] is assigned to a [UserB] as their home view
• Log in as [UserA]

1. Access the 'View Definition' form.
2. Click [Select View].
3. Select [TestViewA] from the "Select Views" list box
4. Click [OK].
5. Click [Launch View Designer]
6. Validate [WidgetA] is present on the layout as expected
7. In the "Available" widgets list, search for [WidgetA]
8. Validate [WidgetA] is found and select the widget
9. Click the right arrow icon to add it to the "Assigned" widget list
10. Click and drag [WidgetA] to the layout section
11. In the "Available" widgets list, search for [WidgetB]
12. Validate [WidgetB] is found and select the widget
13. Click the right arrow icon to add it to the "Assigned" widget list
14. Click and drag [WidgetB] to the layout section
15. Click [Submit] to return to exit the view designer and return to the main form and click [Submit].
16. Validate that a 'Form Return' message is displayed stating: "Submitting has completed. Do you wish to return to form?"
17. Click [No].
18. Log out as [UserA] and login as [UserB]
19. At the home view, click [Preferences] on the menu bar
20. Select 'Widgets' from the tab selection.
21. Click [Reload Home View].
22. Validate that a 'Confirm Reload' message appears stating: "Are you sure you want to discard current changes and reload layout from server?"
23. Click [Yes].
24. Validate that [WidgetA] and [WidgetB] are no present on the view
25. Click [Apply].
26. At the home view
27. Validate that [WidgetA] and [WidgetB] are now present on the home view
28. Select [ClientA]
29. Validate data is displayed in the widget, as expected

• Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information"
• Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined
• Have access to form "Form Designer"

1. Open form "Form Designer"
2. Select the product form [FormA], from the "Forms" drop down list
3. Select a section from the "Tabs" drop down list
4. Click on [FieldA] in the form layout section.
5. Click the "SQL Info" on the left side panel to display field and table name information
6. Validate "Table Name" for the [TableA] reflects current SQL table name for example "SYSTEM.user_emergency_contact_information"
7. Validate "Field Name" for the [FieldA] reflects current SQL table name, for example "Emergency_contact_name"
8. Close the form
9. Open form "Form Designer"
10. Select the modeled form [FormB] from the "Forms" drop down list
11. Select a section from the "Tabs" drop down list
12. Click on [FieldB] in the form layout section.
13. Click the "SQL Info" on the left side panel to display field and table name information
14. Validate "Table Name" for the [TableB] reflects current SQL table name for example "SYSTEM.modeled_form"
15. Validate "Field Name" for the [FieldB] reflects current SQL table name, for example "Clients_full_name"
16. Close the form

• Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information"
• Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined

1. Open 'Form and Table Documentation'.
2. Set 'Type of Documentation' to 'Form'.
3. Select "Individual" in the "Individual or All Forms" field
4. Select [FormA] from the 'Form to be Documented' field
5. Click [Process]
6. Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected
7. Click the "Page" field and go to the last page of the report
8. Validate all field names and their associated SQL table names are listed, as expected
9. Click [Close]
10. Set 'Type of Documentation' to 'Form'.
11. Locate and select [TableA] in field "Table(s) to be Documented"
12. Click [Process]
13. Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected
14. Click [Close]
15. Repeat step 1 for modeled [FormB] and [TableB]
16. Validate results are as expected

• Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA]
• Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA]

1. Open form "Display User Role"
2. Select "All" in the Individual or All User Roles" field
3. Set field "Include Deactivated User Roles" to "Yes"
4. Click [Process]
5. Validate the "Display User Role" report is displayed
6. Search for the active ole [ActiveRoleA]
7. Validate the role is found
8. Search for the deactivated role [DeactiveRoleA]
9. Validate the role is found, as expected
10. Close the report
11. Select "Individual" in the Individual or All User Roles" field
12. Click the "User Role" field
13. Validate the drop down list contains [ActiveRoleA]
14. Validate the drop down list also contains [DeactiveRoleA], as expected

• Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA]
• Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA]

1. Open form "Display User Role"
2. Select "All" in the Individual or All User Roles" field
3. Set field "Include Deactivated User Roles" to "No"
4. Click [Process]
5. Validate the "Display User Role" report is displayed
6. Search for the "Active" role [ActiveRoleA]
7. Validate the role is found
8. Search for the "Active" role [DeactiveRoleA]
9. Validate the role is not found, as expected
10. Close the report
11. Select "Individual" in the Individual or All User Roles" field
12. Click the "User Role" field
13. Validate the drop down list contains [ActiveRoleA]
14. Validate the drop down list does not contain [DeactiveRoleA], as expected

• Have an "Alert" defined in form "Client Alerts" [AlertA]

1. Open form "Client Triggers"
2. Select [TableA] in the "Table" field
3. Click to the "Table Based Triggers" section
4. Click to "Add New Item"
5. Select [AlertA] in the "Client Alert Type" field
6. Select the desired value from the "Trigger On" field
7. Select a value if desired from the "Offset Trigger Based On The Following Date Field"
8. Populate the "Number of Days Alert Should be Active" field
9. Populate the "Days Before/After Date Field to Offset Trigger" field
10. Click to the "Field Based Triggers" section and
11. Click to "Add New Item"
12. Select [AlertA] in the "Client Alert Type" field
13. Select the desired value in the "Trigger Alert for All Episodes" field
14. Populate the "Number of Days Alert Should be Active" field
15. Click the "Field" prompt
16. Validate all the expected field valued for [TableA] are listed for selection
17. Select a desired value
18. Select the desired value in the "Type of Comparison" field
19. Populate the "Comparison Value" field with the desired value
20. Select a value if desired from the "Offset Trigger Based On The Following Date Field"
21. Populate the "Days Before/After Date Field to Offset Trigger" field
22. Submit the form
23. Return to form "Client Triggers"
24. Select [TableA] in the "Table" field
25. Click to the "Table Based Triggers" section
26. Validate all fields are populated as expected based on the value filed in step 1
27. Click to the "Field Based Triggers" section
28. Validate all fields are populated as expected based on the value filed in step 1

• In form "Widget Definition" have a 'Multiple Row SQL' widget defined [WidgetA] with the 'Enhanced Widget View' field set to "Yes"
• Have [WidgetA] placed on a users home view [UserA]
• Log in as [UserA]

1. Click to "Refresh" [WidgetA]
2. Validate the columns display data as expected and the columns are not sorted
3. Locate a desired column [ColumnA], in the widget
4. Click column header name once
5. Validate the "Up" arrow icon is highlighted and data in the column is sorted in ascending order
6. Click column header a second time
7. Validate the "Down" arrow icon is highlighted and data in the column is sorted in descending order
8. Click column header a third time
9. Validate the "Up" and "Down" arrows are no longer highlighted and data is no longer sorted in the column
10. Holding the "Shift" key, select [ColumnA] and click the column header name once to sort it in ascending order
11. While still holding the 'Shift' key, select another column [ColumnB] and click the column header name twice to sort it in descending order
12. Validate widget data results are sorted by [ColumnA] in ascending order and then by [ColumnB] in descending order, as expected
13. Select any column in the widget, for example [ColumnA] which for this test is "Client ID #"
14. In the search input box below the column name type in search criteria, for example "4"
15. Validate the list is filtered and displays only clients whose client ID contains a "4"
16. Click in the input box and clear the search criteria entered
17. Validate the list is refreshed and displays all results in column again
18. Click the line between [ColumnA] and [ColumnB] and drag the line to the left in order to reduce the size of [ColumnA]
19. Validate the width of the column is reduced, as expected
20. Click the line between [ColumnA] and [ColumnB] drag the line to the right in order to increase the size of [ColumnA]
21. Validate the width of the column is increased as expected
22. Repeat steps 1 thru 4 sorting, filtering and resizing any desired columns
23. Click the "Refresh" button in the widget
24. Validate all sorting, filtering and resizing results remain
25. Log out as the same user and log back in using the same browser session
26. Validate all sorting, filtering and resizing results have remained the same as before the user logged out
27. Log out as the same user and close the browser session
28. Open a new browser session and log back in
29. Validate all sorting, filtering and resizing set prior to logging out, has been removed

• Have a progress note "Console" widget [WidgetA] created in form "Console Widget Configuration" for any form [FormA]. For example, the "Individual Progress Notes" form.
• Include the following fields columns among the those selected to display in the widget, 'Practitioner ', 'Service Charge Code 'Date of Service', 'Service Program' and 'Draft/Final'
• Have [WidgetA] and the "Console Widget Viewer" widget placed on the home view a user [UserA]
• Log in as [UserA]

1. Open [FormA]
2. Select [ClientA]
3. Click to add a new row
4. In the "Progress Note For" field select "New Service"
5. Populate all required fields, including, 'Practitioner ', 'Service Charge Code', 'Date of Service' and 'Service Program'
6. Select "Draft" in the "Draft/Final" field
7. Submit the form
8. Validate the form files successfully
9. Click the [WidgetA] refresh button
10. Validate the "Draft/Final" column contains "Draft", as expected
11. Validate all columns are populated as expected, including the 'Practitioner', 'Service Charge Code', 'Date of Service' and 'Service Program'
12. Re-open [FormA] for [ClientA]
13. In the 'Select Draft Note to Edit" field, select the row filed in Step 1
14. Set the "Draft/Final" field to "Final"
15. Submit the form
16. Validate the form files successfully
17. Click the [WidgetA] refresh button
18. Validate the "Draft/Final" column contains "Final", as expected
19. Validate all columns are populated as expected, including the 'Practitioner', 'Service Charge Code', 'Date of Service' and 'Service Program'
20. Click the [View]
21. In the "Console Widget Viewer" widget,
22. Validate the "Draft/Final" column displays "Final", as expected
23. Validate all other field values are displayed as expected, including the 'Practitioner', 'Service Charge Code', 'Date of Service' and 'Service Program' fields

• Have a system with “Netsmarts "(NIAM) Netsmart’s Identity and Access Management" functionality” configured.
• In form "User Definition",:
• User [ExternalA] has is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
• User [ExternalA] is assigned to a user role with "SQL" Table access in form "User Definition"
• User [NoExternalA] is assigned is set with prompt 'Use External Login' to 'No' and is assigned to any user role
• Have access to form "Change User ID"
• Have access to program "SoapUI" to execute web services
• Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user

1. Open "SoapUI"
2. Navigate to the "WEBSVC.UserManagement" web service
3. Locate the <UserID> field in the "UpdateUser" request configured in the set up
4. Populate the field with the UserID for [UserA]
5. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
6. Click the "Submit Request" arrow to execute the web service
7. Validate the 'Message' field in the response section states: "User [UserA] was successfully updated"
8. Open form "User Definition"
9. Select [UserA]
10. Locate the field that was updated in step 1
11. Validate the field updated via the web service in step1, contains the new value [NewValueA]
12. Navigate back to the "WEBSVC.UserManagement" web service
13. Locate the <UserID> field in the "UpdateUser" request configured in the set up
14. Populate the field with the UserID for [UserB]
15. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
16. Click the "Submit Request" arrow to execute the web service
17. Validate the 'Message' field in the response section states: "User [UserB] was successfully updated"
18. Open form "User Definition"
19. Select [UserB]
20. Locate the field that was updated in step 3
21. Validate the field updated via the web service in step 3, contains the new value [NewValueA]
22. Navigate back to the "WEBSVC.UserManagement" web service
23. Locate the <UserID> filed in the "UpdateUser" request configured in the set up
24. Populate the field with the UserID for [UserC]
25. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
26. Click the "Submit Request" arrow to execute the web service
27. Validate the 'Message' field in the response section states: "User [UserC] was successfully updated"
28. Open form "User Definition"
29. Select [UserC]
30. Locate the field that was updated in step 5
31. Validate the field updated via the web service in step4, contains the new value [NewValueA]

• Have a system configured to use Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality
• In form "User Definition":
• User [UserA] is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
• User [UserA] is assigned to a user role with "SQL" table access
• User [UserB] is set with prompt 'Use External Login' to 'No' and is assigned to any desired user role
• Have access to form "Change User ID"
• Have access to program "SoapUI" to execute web services
• Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user

1. Open "SoapUI"
2. Navigate to the "WEBSVC.UserManagement" web service
3. Locate the "<UserID>" field in the "UpdateUser" request configured in the set up
4. Populate the field with [UserA]
5. Change the current value in the "<User Description>" field to a different value [NewValueA]
6. Change the value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
7. Click the "Submit Request" arrow to execute the web service
8. Validate the message 'User USERA successfully updated', is displayed as expected
9. Open form "User Definition"
10. Select [UserA]
11. Validate the "User Description" field contains the new value [NewValueA], updated via web service
12. Validate the field "Warn if User Attempts Non Caseload Access" is set to [NewValueB], updated via the web service
13. Open form "Change User ID"
14. Select [UserB] in the "User" Field
15. Populate the "New User ID" field with a new ID [UserC]
16. Submit the form
17. Validate the form files successfully
18. Open form "User Definition"
19. Select [UserB]
20. Validate the field "Deactivate User" is checked
21. Validate only the "User Description" field is enabled on the form
22. Navigate back to the "WEBSVC.UserManagement" web service
23. Locate the "<UserID>" field in the "UpdateUser" request configured in the set up
24. Populate the field with [UserB]
25. Change the current value in the "<User Description>" field to a different value [NewValueA]
26. Change the value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
27. Click the "Submit Request" arrow to execute the web service
28. Validate message 'User USERB successfully updated', is displayed
29. Open form "User Definition"
30. Select [UserB]
31. Validate the "User Description" field contains the new value [NewValueA], updated via web service
32. Validate the field "Warn if User Attempts Non Caseload Access" is not set to its original valued, as only the "User Description" field can be updated for deactivated users
33. Navigate back to the "WEBSVC.UserManagement" web service
34. Locate the "<UserID>" filed in the "UpdateUser" request configured in the set up
35. Populate the field with the [UserC]
36. Change the current value in the "<User Description>" field to a different value [NewValueA]
37. Change a value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
38. Click the "Submit Request" arrow to execute the web service
39. Validate message "User USERC successfully updated", is displayed
40. Open form "User Definition"
41. Select [UserC]
42. Validate the "User Description" field contains the new value [NewValueA], updated via web service
43. Validate the field "Warn if User Attempts Non Caseload Access" is set to [NewValueB], updated via the web service

• Have two users who are practitioners, [StaffA] and [StaffB]
• [TeamA] has been created in form "Team Definition" and both [StaffA] and [StaffB] have been assigned to the team
• In form "Compliance Rule Definition" :
• Create a rule that will set a client out of compliance if a diagnosis has not been submitted for the client, within five days after their admission date
• In field "Team To Send Notification To", have [TeamA] selected, which will send a To Do to staff members on the team when a client is out of compliance
• Have a client [ClientA] who already has had a diagnosis filed within five days after of their admission date
• Have a client [ClientB] who has not had a diagnosis filed within five days after of their admission date
• [StaffA] and [StaffB] have both clients on their caseload
• [StaffA] and [StaffB] have the "My Clients" and the "My To Do's" widgets on their home view
• Log in as [StaffA]

1. At the home view
2. Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup
3. Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup
4. Click to refresh the "My To Do's" widget
5. Validate the To Do list for [StaffA] does not contain a To Do compliance notification for [ClientA], as expected
6. Validate the To Do list for [StaffA] does contains a To Do compliance notification for [ClientB]
7. Click [Review To Do Item]
8. Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA] notification has been received.
9. Click the "Reviewed" check box
10. Click [Submit]
11. Validate the submission is successful and the To Do is removed from the To Do's list
12. Log out as [StaffA]
13. Log in as [StaffB]
14. At the home view
15. Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup
16. Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup
17. Click to refresh the "My To Do's" widget
18. Validate the To Do list for [StaffB] does not contain a To Do compliance notification for [ClientA]
19. Validate the To Do list for [StaffB] does contains a To Do compliance notification for [ClientB]
20. Click [Review To Do Item]
21. Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA] notification has been received.
22. Click the "Reviewed" check box
23. Click [Submit]
24. Validate the submission is successful and the To Do is removed from the To Do's list

• Have two users who are practitioners, [StaffA] and [StaffB]
• In form "Practitioner Enrollment", [StaffA] has [CatagoryA] selected in the 'Practitioner Categories for Coverage Filter' field
• In form "Practitioner Enrollment", [StaffB] does not have [CatagoryA] selected in the "Practitioner Categories for Coverage Filter" field
• [TeamA] has been created in form "Team Definition" and both staff members have been assigned to the team
• In form "Compliance Rule Definition" :
• Create a rule that will set a client out of compliance if a diagnosis has not been submitted for the client, within five days after their admission date
• In field "Team To Send Notification To", have [TeamA] selected, which will send a To Do to staff members on the team when a client is out of compliance
• In the field "Notification Provider Categories for Coverage Filter" select [CategoryA]. [Please Note: This field has been renamed from 'Notification Practitioner Category Filter', in order to accurately reflect the contents of the field]
• Have a client [ClientA] who already has had a diagnosis filed within five days of their admission date
• Have a client [ClientB] who has not had a diagnosis filed within five days after of their admission date
• [StaffA] and [StaffB] have both clients on their caseload
• [StaffA] and [StaffB] have the "My Clients" and the "My To Do's" widgets on their home view
• Log in as [StaffA]

1. At the home view
2. Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup
3. Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup
4. Click to refresh the "My To Do's" widget
5. Validate the To Do list for [StaffA] does not contain a To Do notification for [ClientA], as expected
6. Validate the To Do list for [StaffA] does contains a compliance To Do for [ClientB]
7. Click [Review To Do Item]
8. Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA]" notification has been received.
9. Click the "Reviewed" check box
10. Click [Submit]
11. Validate the submission is successful and the To Do is removed from the To Do's list
12. Log out as [StaffA]
13. Log in as [StaffB]
14. At the home view
15. Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup
16. Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup
17. Click to refresh the "My To Do's" widget
18. Validate there is no compliance To Do present for either [ClientA] or [ClientB] as expected, since [StaffB] does not have [CatagoryA] selected in the "Practitioner Categories for Coverage Filter" field of form "Practitioner Enrollment"

• Have a form [FormA] set up in form "Document Routing Setup" with following prompts set:
• 'Enable Document Routing' se to 'Yes'.
• 'Allow Notifications When Final' set to 'Yes'.
• 'Notification List Defaults' set to 'Default From List Filing'
• [UserA] has access to [FormA]
• [UserB] is a Staff member and has the "My To Do's" widget on their home view
• Log in as [UserA]

1. Access [FormA] and select any client [ClientA]
2. Populate all desired fields on the form.
3. Select "Final" in the 'Draft/Final' field.
4. Click [Accept and Route/Notify]
5. Enter the user's password in the 'Password' field.
6. Click [OK].
7. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
8. Search for User. [UserB],
9. Click [Add] to have [UserB] receive a To do notification
10. Validate that [UserB] is added and the "Notify' check box is populated
11. Click [Submit]
12. Validate the form files successfully
13. Repeat step 1 a thru e
14. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
15. Validate the [UserB] is automatically added to the approver list and the "Notify" check box is populated
16. Click [Submit]
17. Validate the form files successfully
18. Log in as [UserB]
19. Navigate to the "My To Do's" widget
20. Click to refresh the widget
21. Click the "New" tab
22. Validate there are two new To Do's in the list for [ClientA], for [FormA]
23. Click to open each To Do
24. Validate the "To Do Information" box contains the expected data
25. Click the "Reviewed" check box
26. Click [Submit]
27. Validate submission is successful and each To Do has been removed form the To Do's list

• Have a form enabled for "Document Routing" [FormA]
• In form "Document Routing Setup", have prompt "Create Document Only" set to "Yes" for [FormA]
• In "Document Routing Setup", have 'Skip Display Of Image' set to "Yes" for [FormA]
• The 'My To Do's' widget is on the user's home screen
• Have a client [ClientA] enrolled in an active episode [EpisodeA]

1. Open [FormA]
2. Select [ClientA]
3. Select [EpisodeA]
4. Complete the desired fields
5. Set the "Draft/Final" prompt to "Final"
6. Click [Submit]
7. Validate no document image or route to document screen(s) are displayed
8. Validate a quick "Confirm Document", "Saving Image Data" screen displays and the form files successfully
9. Navigate to form "Clinical Document Viewer"
10. In the "Search Clients" field, select [ClientA]
11. Select [EpisodeA] in the "Episodes" field
12. Click [Process]
13. In the document "Results" list, validate there is a document row present for [ClientA] for the submission of [FormA] in step 1
14. Double-click the row to view the document
15. Validate the data is displayed as expected

• Have a form enabled for "Document Routing" [FormA]
• In form "Document Routing Setup", have prompt "Create Document Only"' set to "Yes" for [FormA]
• In "Document Routing Setup", have 'Skip Display Of Image' set to "No" for [FormA]
• The 'My To Do's' widget is on the user's home screen
• Have a client [ClientA] enrolled in an active episode [EpisodeA]

1. Open [FormA]
2. Select [ClientA]
3. Select [EpisodeA]
4. Complete the desired fields
5. Set the "Draft/Final" prompt to "Final"
6. Click [Submit]
7. At the "Confirm Document" screen, validate the document is displayed as expected
8. Click [Accept]
9. At the "Verify Password" prompt, populate the "Password" field
10. Click [OK]
11. Validate the user is not presented with the "Route To Document" screen, as expected
12. Validate the form submits successfully
13. Navigate to form "Clinical Document Viewer"
14. In the "Search Clients" field, select [ClientA]
15. Select [EpisodeA] in the "Episodes" field
16. Click [Process]
17. In the document "Results" list, validate there is a document row present for [ClientA] for the submission of [FormA] in step 1
18. Double-click the row to view the document
19. Validate the data is displayed as expected

• Have a progress note form [FormA] enabled for "Document Routing"
• In form "Document Routing Setup":
• Have prompt 'Skip Display Of Image' set to "No" for [FormA]
• Have prompt "Create Document Only" set to "No" for [FormA]
• Have a 'Note Type' requiring a co-signature defined on the system [NotetypeA]
• Have a client [ClientA] enrolled in an active episode [EpisodeA]
• [UserA] has access to [FormA]
• [UserB] is a staff member and has the "My To Do's" widget on their home view
• Log in as [UserA]

1. Open [FormA]
2. Select [ClientA]
3. Select [EpisodeA]
4. Complete the progress note, selecting [NotetypeA], which requires a co-signer
5. Set the "Draft/Final" prompt to "Final"
6. Click [Submit]
7. At the "Route To Document" screen
8. Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer
9. In the 'Add Approver' field, select [UserB]
10. Validate the [Submit] button is now enabled
11. Click [Cancel]
12. Validate user is returned to [FormA] and form is set to "Final"
13. Click [Submit]
14. At the "Route To Document" screen
15. Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer
16. In the 'Add Approver' field, select [UserB]
17. Validate the [Submit] button is now enabled
18. Click [Submit]
19. Validate the form submits successfully
20. Log out as [UserA] and log in as [UserB]
21. Navigate to the 'My To Do's' widget
22. Locate the To Do routed in step 1 for [FormA]
23. Click 'Approve Document'
24. Validate the document is displayed as expected
25. Click [Sign]
26. Enter the user's password
27. Click [OK]
28. Validate the To Do is removed from the 'My To Do's' widget

• Have a progress note form [FormA] enabled for "Document Routing"
• In form "Document Routing Setup":
• Have prompt 'Skip Display Of Image' set to "No" for [FormA]
• Have prompt "Create Document Only" set to "No" for [FormA]
• Have a 'Note Type' requiring a co-signature defined on the system [NotetypeA]
• Have a client [ClientA] enrolled in an active episode [EpisodeA]
• [UserA] has access to [FormA]
• [UserB] is a staff member and has the "My To Do's" widget on their home view
• Log in as [UserA]

1. Open [FormA]
2. Select [ClientA]
3. Select [EpisodeA]
4. Complete the progress note, selecting [NotetypeA], which requires a co-signer
5. Set the "Draft/Final" prompt to "Final"
6. Click [Submit]
7. At the "Confirm Document" screen, validate the document is displayed as expected
8. Click [Accept/Route]
9. At the "Verify Password" prompt, populate the "Password" field
10. Click [OK]
11. At the "Route To Document" screen
12. Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer
13. In the 'Add Approver' field, select [UserB]
14. Validate the [Submit] button is now enabled
15. Click [Cancel]
16. Validate user is returned to "Confirm Document" screen
17. Click [Accept/Route]
18. At the "Verify Password" prompt, populate the "Password" field
19. Click [OK]
20. At the "Route To Document" screen
21. Validate the [Submit] button is not enabled again as expected, since [FormA] requires a co-signer
22. In the 'Add Approver' field, select [UserB]
23. Validate the [Submit] button is now enabled
24. Click [Submit]
25. Validate the form submits successfully
26. Log out as [UserA] and log in as [UserB]
27. Navigate to the 'My To Do's' widget
28. Locate the To Do routed in step 1 for [FormA]
29. Click 'Approve Document'
30. Validate the document is displayed as expected
31. Click [Sign]
32. Enter the user's password
33. Click [OK]
34. Validate the To Do is removed from the 'My To Do's' widget

• In Avatar, file a [RowA] for [ClientA] in form ""Patient Health Questionnaire-A" form" with field "Assessment Date" populated with a date less than or equal to current date [DateA]
• In Avatar, file another [RowB] for [ClientA] in form ""Patient Health Questionnaire-A" form" with field "Assessment Date" populated with any future date [DateB]
• The "Patient Health Questionnaire-9" form is marked for inclusion in form "Mobile Application Build"

1. Log into "Clinician"
2. Click [Synchronize] to sync data with Avatar
3. Validate synchronization is successful
4. Select [ClientA]
5. Open the "Patient Health Questionnaire-9" form
6. Validate the form launches successfully
7. Validate in the pre-display, [RowA] is displayed
8. Select the row and click [Edit]
9. Validate "Assessment Date" is populated as expected with [DateA]
10. Validate all other fields are populated as expected
11. Add or update a value of any field [FieldA] and make a note of the change
12. Submit the form
13. Validate the form files successfully
14. Open the "Patient Health Questionnaire-9" form
15. Validate the form launches successfully
16. Validate in the pre-display, [RowB] is displayed
17. Select the row and click [Edit]
18. Validate "Assessment Date" is populated as expected with [DateB]
19. Validate all other fields are populated as expected
20. Add or update a value of any field [FieldB] and make a note of the change
21. Submit the form
22. Validate the form files successfully
23. Click [Synchronize] to sync data with Avatar
24. Validate synchronization is successful
25. Log into Avatar
26. Select [ClientA]
27. Open the "Patient Health Questionnaire-9" form
28. In the pre-display, select [RowA] for edit
29. Validate [FieldA] updated in step 1b, is populated as expected
30. Close the form
31. Open the "Patient Health Questionnaire-9" form
32. In the pre-display, select [RowB] for edit
33. Validate [FieldB] updated in step 1b, is populated as expected
34. Close the form

• In Avatar, file a [RowA] for [ClientA] in form "Treatment Plan" form with field "Plan Date" populated with a date less than or equal to the current date
• In Avatar, file another [RowB] for [ClientA] in form "Treatment Plan" form with field "Plan Date" populated with any future date
• Have the "Treatment Plan" form marked for inclusion in form "Mobile Application Build"

1. Log into "Clinician"
2. Click [Synchronize] to sync data with Avatar
3. Select [ClientA]
4. Open the "Treatment Plan" form
5. Validate the form launches successfully
6. Validate in the pre-display, [RowA] is displayed
7. Select the row and click [Edit]
8. Validate "Plan Date" is populated as expected with [DateA]
9. Validate all other fields are populated as expected
10. Add or update a value of any field [FieldA] and make a note of the change
11. Submit the form
12. Validate the form files successfully
13. Open the "Treatment Plan" form
14. Validate the form launches successfully
15. Validate in the pre-display, [RowB] is displayed
16. Select the row and click [Edit]
17. Validate "Plan" is populated as expected with [DateB]
18. Validate all other fields are populated as expected
19. Add or update a value of any field [FieldB] and make a note of the change
20. Submit the form
21. Validate the form files successfully
22. Log into Avatar
23. Select [ClientA]
24. Open the "Treatment Plan" form
25. In the pre-display, select [RowA] for edit
26. Validate [FieldA] updated in step 1b, is populated as expected
27. Close the form
28. Open the " "Treatment Plan" form
29. In the pre-display, select [RowB] for edit
30. Validate [FieldB] updated in step 1b, is populated as expected
31. Close the form

• In Avatar, file a [RowA] for [ClientA] in any "Progress Note" form" for a "New Service" with the "Date Of Service" field populated with the current date
• Have the "Progress Note" form marked for inclusion in form "Mobile Application Build"

1. Log into Avatar
2. Select [ClientA]
3. Open the "Progress Note" form
4. Click [Add] to add a new row [RowB]
5. in the "Progress Note For" field, select "New Service"
6. Set the "Date of Service" field to a future date
7. Validate an error is displayed "Future Dates Not Permitted"
8. Click [OK]
9. Enter today's date
10. Validate entry is permitted
11. Enter a date prior to the current date
12. Validate entry is permitted
13. Populate all other required and desired fields
14. Submit the form
15. Validate the form files successfully
16. Log into "Clinician"
17. Click [Synchronize] to sync data with Avatar
18. Select [ClientA]
19. Open the "Progress Note" form
20. Validate the form launches successfully
21. Validate in the pre-display, [RowA] is displayed
22. Select the row and click [Edit]
23. Validate "Plan Date" is populated as expected with [DateA]
24. Validate all other fields are populated as expected
25. Add or update a value in any field [FieldA] and make a note of the change
26. Submit the form
27. Validate the form files successfully
28. Open the "Progress Note" form
29. Validate the form launches successfully
30. Validate in the pre-display, [RowB] is displayed
31. Select the row and click [Edit]
32. Validate "Plan" is populated as expected with [DateB]
33. Validate all other fields are populated as expected
34. Add or update a value in any field [FieldB] and make a note of the change
35. Submit the form
36. Validate the form files successfully
37. In Avatar
38. Select [ClientA]
39. Open the "Progress Note" form
40. In the pre-display, select [RowA] for edit
41. Validate [FieldA] updated in step 1b, is populated as expected
42. Close the form
43. Open the "Progress Note" form
44. In the pre-display, select [RowB] for edit
45. Validate [FieldB] updated in step 1b, is populated as expected
46. Close the form

• Have registry setting "Enable OpenID Connect Support" enabled in the system
• The system has been configured for (NIAM) functionality with the appropriate settings configured in the "OpenID Connect Configuration" section of form "System Security Defaults"
• An "(ODIC) Identity Provider" solution is enabled that will be used in conjunction with Avatar to authenticate a user set up as a "NAIM" user, for example provider "Okta"
• The "(ODIC) Identity Provider" solution has been enabled for "MFA (Multi factor authentication)".
• [UserA] is assigned an external login ID and password to login as "NIAM" user using the "(ODIC) Identity Provider" solution and their login is enabled for "MFA (Multi factor authentication)" in order to send a one time code to the user at the time of login, for authentication
• [UserA] is configured in form "User Definition" with prompt "User External Login" set to "Yes" and field "External Login ID" populated with external login ID assigned by the "(ODIC) Identity Provider". This will be used as "Netsmart ID" during login.

1. Launch the "Clinician" application
2. Click [Login with Enterprise Credentials]
3. Verify the "Netsmart Identity and Access Management" login page is displayed
4. At the "Netsmart ID" field, populate the "Username" field with the user configured for [UserA]
5. Click [Next]
6. At the "Sign In" screen.
7. Populate the "Username" field
8. Populate the "Password" field
9. Click [Sign In]
10. At the "SMS Authentication" screen
11. Click [Send Code]
12. Enter the code received
13. Click [Verify]
14. Select any system code from the "Select System Code" field, if not already defaulted
15. Populate the "Please re-enter password for local (disconnected state) encryption" field
16. Click the [->]
17. If applicable, the message "You haven't synced your device today. Performing a sync can prevent errors from occurring while using Clinician" will display.
18. Click [Sync]
19. Verify synchronization is successful
20. At the home view, select a desired client [ClientA]
21. Open any [FormA]
22. Populate the form
23. Click [Submit]
24. Validate the form filed successfully
25. Click [Synchronize]
26. Verify synchronization is successful
27. Log into "Avatar"
28. Select [ClientA]
29. Open [FormA]
30. Select the row just submitted in Clinician
31. Verify the form is populated as expected

• Have two users who are staff members. [UserA] and [UserB]
• [UserA] has a UserID that includes a period, for example "John.Smith" and a user description [DescriptionA]
• [UserB] has a UserID that does not include a period and a user description [DescriptionB]
• Have a widget [WidgetA] that displays data in the "SYSTEM_RADplus_teams" table, and includes the "team_finalizer_userID" and "team_finalizer_user_desc" columns in its data output
• Have two teams set up in form "Team Definition", [TeamA] and [TeamB]
• Both teams have [UserA] and [UserB] added to the teams as user's
• Have a report [ReportA] to display data in the "SYSTEM_RADplus_teams" table that includes the "team_finalizer_userID" and "team_finalizer_user_desc" columns in its data output
• [UserC] has access to "Team Definition" and has [WidgetA] on their home view
• Log in as [UserC]

1. Open form "Team Definition"
2. Select [TeamA]
3. Click the "Team Finalizer" field
4. Validate both [UserA] and [UserB] are present
5. Select [UserA]
6. Submit the form
7. Validate submission is successful
8. Return to the form
9. Select [TeamA]
10. Validate the "Team Finalizer" field is populated with [UserA] [DecriptionA]
11. Exit the form
12. Select [TeamB]
13. Click the "Team Finalizer" field
14. Validate both [UserA] and [UserB] are present
15. Select [UserB]
16. Submit the form
17. Validate submission is successful
18. Return to the form
19. Select [TeamB]
20. Validate the "Team Finalizer" field is populate with [UserB] [DescriptionB]
21. Exit the form
22. At the home view, click the refresh button in [WidgetA]
23. Locate the row for [TeamA]
24. Validate the UserID for [UserA] is displayed in the "team_finalizer_userID" column, as expected and includes the period in ID
25. Validate [DescriptionA] is displayed in the "team_finalizer_user_desc column", as expected
26. Locate the row for [TeamB]
27. Validate the UserID for [UserB] is displayed in the "team_finalizer_userID" column, as expected
28. Validate [DescriptionB] is displayed in the "team_finalizer_user_desc" column, as expected
29. Launch [ReportA]
30. Click to preview the report
31. Locate the row for [TeamA]
32. Validate the UserID for [UserA] is displayed in the "team_finalizer_userID" column, as expected and includes the period in ID
33. Validate [DescriptionA] is displayed in the "team_finalizer_user_desc column", as expected
34. Locate the row for [TeamB]
35. Validate the UserID for [UserB] is displayed in the "team_finalizer_userID" column, as expected
36. Validate [DescriptionB] is displayed in the "team_finalizer_user_desc" column, as expected

• Have user [UserA] that has "Double Quotes" populated in the "User Description" field of their "User Definition" form record
• Have user [UserB] that has an "Apostrophe" populated in the "User Description" field of their "User Definition" form record
• Have user [UserC] that has any other special character populated in the "User Description" field of their "User Definition" form record
• Have user [UserD] that has no special characters in their name
• Have a "State Form Definition" file defined [DefinitionA], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "GROUP BY" command within the statement
• Have a "State Form Definition" file defined [DefinitionB], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "ORDER BY" command within the statement
• Log in as [UserA]

1. Open form "State Form File Generation".
2. Select definition [DefinitionA] in field "State Form".
3. Populate the "File Description" field.
4. In the "File Generation Options" field, select "Compile".
5. Click [Process].
6. Validate the process completes successfully.
7. In the "File Generation Options" field, select "Dump File".
8. Click [Process].
9. Validate the data output of the file is as expected
10. Close the form
11. Open form "State Form File Generation".
12. Select definition [DefinitionB] in field "State Form".
13. Populate the "File Description" field.
14. In the "File Generation Options" field, select "Compile".
15. Click [Process].
16. Validate the process completes successfully.
17. In the "File Generation Options" field, select "Dump File".
18. Click [Process].
19. Validate the data output of the file is as expected
20. Close the form
21. Log out as [UserA]
22. Log in as [UserB]
23. Repeat step 1
24. Validate results are as expected
25. Repeat step 2
26. Validate results are as expected
27. Log out as [UserB]
28. Log in as [UserC]
29. Repeat step 1
30. Validate results are as expected
31. Repeat step 2
32. Validate results are as expected

• Have a state form definition file [DefA], created in form "State Form Definition"
• Have an "FTP Server" set up to receive files
• Have the following "FTP Server" information available in order to populate the "State Form Task Scheduler" form during testing:

1. The "Service Directory" location
2. The "Server Host Name"
3. The "Server Port Number"
4. The "Server Username" field
5. The "Server Password" field
6. The "Public Key File" and the folder location of the file
7. The "Private Key File" and the folder location of the file

1. Open form "State Form Definition"
2. Select [DefA]
3. Populate the "File Path" field with directory that exists on the logged in users server; [LocationA]
4. Submit the form
5. Validate the form files successfully
6. Open the 'State Form Task Scheduler' form
7. Select [DefA]
8. Select "Yes" in the "Create File" field
9. Select "Yes" in "Send File To FTP Server" field
10. In the "FTP Type" field, select "SFTP - Key Pair"
11. Populate the "Server Host Name" field
12. Populate the "Server Port Number" field
13. Populate the "Server Username" field
14. Populate the "Server Password" field
15. Populate the "Service Directory" field, this is folder location [FTPfolderA] on the FTP server where the file will be sent
16. Populate the "Public Key File Location" field
17. Populate the "Private Key File Location" field
18. Click [Test FTP Connection]
19. Validate test is successful
20. Submit the form
21. Validate the form files successfully
22. Open form "System Task Scheduler"
23. Select the task set up for [DefA] in step 2 from the "Schedule(s)" field
24. Populate the "Recurrence Pattern" field with desired value
25. Populate the "Task Occurrence" field with the desired value
26. Populate the "Start By" field with the desired date for the task to start
27. Populate the "Start Time" field with the desired time for the task to start
28. Select "No" in the "Inactive Task" field
29. Click [Schedule Task]
30. Close the form
31. When the scheduled start by date and time for task filed in step 3 has passed:
32. Validate the state form file [DefA] exist in the folder [LocationA] on the logged in users server, set in step1
33. Validate the state form file [DefA] exists in the folder [FTPfolderA] on the "FTP" server, set in step 2

• Have an environment that contains an Avatar "Database" server and also an "ECP" server configured by Netsmart with the database server as its "Remote" database server
• Have a state form definition file created in form "State Form Definition" [DefA]
• In form "State Form Definition", select [DefA] and note the definition ID# [IDNum], in parentheses next to the file name
• Have a report or query that can display data in the "SYSTEM.RADplus_sf_audit_record" table [ReportA]

1. Open form "State Form Definition"
2. Select [DefA]
3. Populate the "File Path" field with directory that exists on the users local server
4. Submit the form
5. Open the 'State Form Task Scheduler' form
6. Select [DefA]
7. Select "Yes" for Create File
8. Populate any other required fields
9. Submit the form
10. Validate the form files successful
11. Open form "System Task Scheduler"
12. Select the task set up for [DefA] in step 2 from the "Schedule(s)" field
13. Populate the "Recurrence Pattern" field with desired value
14. Populate the "Task Occurrence" field with the desired value
15. Populate the "Start By" field with the desired date for the task to start
16. Populate the "Start Time" field with the desired time for the task to start
17. Select "No" in the "Inactive Task" field
18. Click [Schedule Task]
19. Close the form
20. When the scheduled date and time for task filed in step 2 has passed
21. Run [ReportA] to display data in the "SYSTEM.RADplus_sf_audit_record" table
22. Validate a row is present for the state form definition file, [DefA]
23. Validate the "FileID" column is populated with definitions ID number [IDNum], noted in the setup
24. Validate the "Server" field is populated with expected "FTP" server name, indicating that the file compiled on that server as expected

• Have an "XML" type "State Form Definition" file created that contains a main record and multiple sub-records. [Def1]

1. Open form "State Form File Generation"
2. Select the [Def1] definition in field "State Form"
3. In the "File Generation Options" field, select "Compile"
4. Click [Process]
5. Validate the process completes successfully
6. In the "File Generation Options" field, select "Create File on Server"
7. Click [Process]
8. Click the "Compile Complete", [OK] button
9. Click [Process] to create a file on the server
10. In the "Windows Explorer" window, navigate to a folder location and save the file
11. In the "Save In" drop down list of File Explorer, select a directory and populate the "File Name"
12. Click [Save]
13. In "File Explorer", go to the directory where the file was saved
14. Click to open the file
15. Validate the contents are as expected