Skip to main content

RADplus 2023 Monthly Release 2023.01.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 13 Summary | Details
Avatar NX - Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Alerts (PM)
Scenario 1: Avatar NX - Validate the 'See more...' text color in the Client Header
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Information' header should be included on the users myDay view.
Steps
  1. Select "Client A" and access the 'Client Alerts' form.
  2. Select "Warning (Custom)" in the 'Type Of Alert' field.
  3. Select "All Forms" in the 'Applicable Forms' field.
  4. Enter the desired value in the 'Custom Message' field.
  5. Click [Submit].
  6. Repeat steps 1-5 to create 3 additional client alerts.
  7. Once complete, navigate to the 'Client Header'.
  8. Validate the 'See more...' text is readable and displayed in white color.
  9. Mouse over the 'See more...' text and validate the client alerts created in the previous steps are displayed.
Widget Wizard - Widget Deletion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Widget Wizard (PM)
Scenario 1: Widget Wizard - Validate ability to delete user created widgets that have been imported
Specific Setup:
  • A user created widget must be defined (Widget A).
Steps
  1. Access the 'Widget Import' form.
  2. Click [Select Import File].
  3. Select the "Widget A".
  4. Validate the 'Import Scan Results' field contains: No errors found.
  5. Click [Begin Import].
  6. Validate a message is displayed stating: Import Complete.
  7. Click [OK] and close the form.
  8. Access the 'Widget Wizard' form.
  9. Click [Select Widget].
  10. Select "Widget A" and click [OK].
  11. Validate the data for "Widget A" is populated.
  12. Validate the 'Delete Widget' button is enabled.
  13. Click [Delete Widget].
  14. Validate a message is displayed stating: Delete Widget "Widget A"?
  15. Click [Yes].
  16. Click [Select Widget].
  17. Validate "Widget A" is no longer displayed in the 'Select Widgets' dialog.
  18. Click [Cancel] and close the form.
Topics
• Client Alerts • Widgets
Update 22 Summary | Details
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
  • Form Definition (CWS)
Scenario 1: Modeled Form - Validate results after submitting form and table definition changes
Specific Setup:
  • Have a modeled "Table" [TestTable] included in form [TestForm], that contains the following fields:
  • [FieldA]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Half Screen"
  • [FieldB]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Full Screen"
  • [FieldC]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Full Screen"
  • A "Draft/Final field"
  • A "Workflow Controlling Notification" field. (Note: workflow notification fields are created in form "Notification Type Definition" and then become available as a column in "Table Definition")
  • Any other desired fields
Steps
  1. Open form [TestForm]
  2. Validate [FieldA] is display in "Half Screen" width and is not a required field, as per the setup
  3. Validate [FieldB] and [FieldC] are displayed in "Full Screen" width and are not required fields, as per the setup
  4. Validate all other fields display as expected
  5. Close the form
  6. Open form "Table Definition"
  7. Select table [TestTable]
  8. Select [FieldB]
  9. Set prompt "Always Required" to "Yes"
  10. Submit the form
  11. Open form [TestForm]
  12. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  13. Validate [FieldB] is still displayed in "Full Screen" width and is now displayed as a required field, as expected
  14. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  15. Validate all other fields display as expected
  16. Close the form
  17. Open form "Form Definition"
  18. Select form [TestForm]
  19. Select [FieldB]
  20. Set prompt "Object Width" prompt set to "Half Screen"
  21. Submit the form
  22. Open form [TestForm]
  23. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  24. Validate [FieldB] is now displayed in "Half Screen" width and is still displayed as required, as expected
  25. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  26. Validate all other fields display as expected
  27. Close the form
  28. Open form "Table Definition"
  29. Select table [TestTable]
  30. Click [Add New Item]
  31. Select a "Column" type
  32. Populate the "Column Name" with the new field [FieldD]
  33. Populate any other required fields
  34. Submit the form
  35. Open form "Form Definition"
  36. Select form [TestForm]
  37. Select [FieldB]
  38. Click to the "Object Def" section
  39. Click [Add New Item]
  40. Select [FieldD]
  41. Submit the form
  42. Open form [TestForm]
  43. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  44. Validate [FieldB] is now displayed in "Half Screen" width and is still displayed as required, as expected
  45. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  46. Validate [FieldD] is displayed on the form
  47. Populate the field
  48. Populate all the fields on the form
  49. Submit the form
  50. Validate the form files successfully
Topics
• Modeling
Update 25 Summary | Details
Document Routing - Approver Comments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Treatment Plan
Scenario 1: Document Routing (Progress Notes) - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a "Progress Notes" form [TestForm], for example form "Progress Notes (Group and Individual)", that has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the 'Co Signer for Other Practitioners' prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users are set with the "My To Do's" widget on their home view
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Document Routing - Signature Images
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Document Routing - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a form [TestForm], for example a "Modeled" form or "Treatment Plan" form that has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the "Co Signer for Other Practitioners" prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users have the "My To Do's" widget on their home views
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Topics
• Progress Notes • NX • Modeling
Update 26 Summary | Details
SQL table permissions
Scenario 1: User Definition - Validate a user's SQL "ODBC" Table permissions
Specific Setup:
  1. Two users exist on the system that have the same "User ID", but which differ by where the period within their user ID is placed. For this example: "U.serA" and "User.A"
  2. "U.serA" has access to the "SYSTEM.patient_current_demographics" table
  3. "U.serA" does not have access "SYSTEM.Admission_data" and "SYSTEM.Appoinment_data" table
  4. "User.A" also has access to "SYSTEM.patient_current_demographics" table
  5. "User.A" does have access to the "SYSTEM.Admission_data" and "SYSTEM.Appiontment_data" tables'
  6. Each user has access to 'Crystal Reports" or other database program to make an ODBC connection and view their assigned SQL Table
Steps
  1. Open the database program, for this example "Crystal Reports" is used
  2. Click "File" on the menu and then "New" to create a new report
  3. At the "Data" dialog, click "Create New Connection"
  4. Double-click "ODBC"
  5. From the "Data Source Selection" dialog, locate the data source name created for user ID "U.serA" and double-click to select it
  6. Populate the "User ID" field and "Password" with the credentials for "U.serA"
  7. Click "Finish"
  8. At the table tree list
  9. Click the "SYSTEM" schema folder and then click "Tables"
  10. Validate the "SYSTEM.patient_current_demographics' table is present in the list
  11. Validate the "SYSTEM.Admission_data" and "SYSTEM.Apppintmentt_data" tables are "not" present, as expected
  12. Click 'Cancel"
  13. Click "File" on the menu and then "New" to create a new report
  14. At the "Data" dialog, click "Create New Connection"
  15. Double-click "ODBC"
  16. From the "Data Source Selection" dialog, locate the data source name created for user ID "User.A"
  17. Populate the "User ID" field and "Password" with the credentials for "User.A"
  18. Click "Finish"
  19. At the table tree list
  20. At the table tree list
  21. Click the "SYSTEM" schema folder and then click "Tables"
  22. Validate the "SYSTEM.patient_current_demographics' table is present in the list
  23. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appointment_data" tables "are" present, as expected
Topics
• SQL Data Access
Update 29 Summary | Details
My To Do's Widget - Client name
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView - My To Do's widget
  • Review To Do Item (PM)
  • Update Client Data
Scenario 1: Validate display of the clients name in the "My To Do's" widget
Specific Setup:
  • In form "Dictionary Update", have the "Client Prefix (175)" and the "Client Suffix (174)" dictionary's, populated with dictionary values.
  • Have clients admitted on the system defined that have client names in the following formats::
  • [ClientA] has just a "first and last name" defined.
  • [ClientB] has a "first name, middle name, last name" defined.
  • [ClientC] has a "first name, middle name, last name and a suffix" defined.
  • [ClientD] has a "prefix, first name, middle name, last name" defined.
  • [ClientE] has a "prefix, first name, middle name, last name and a suffix defined.
  • Have a user [TestUser] who is a staff member and has the "My To Do's" widget on their home view
  • For each client in step 2, have a "To Do" item generated and sent to [TestUser]. (For example, this can be done using form "Send To Do Notification" or any form enabled for document routing)
  • Log in as [TestUser]
Steps
  1. Navigate to the "My To Do's" widget
  2. In the "Client" column, locate the To Do generated for [ClientA]
  3. Validate the clients name displays in the format "First Name Last Name" as expected
  4. Click "Review To Do Item" in the "Action" column to launch the "Review To Do Item" form
  5. Validate the "Client Header" displays the name as expected, in the format "First Name Last Name"
  6. Click the "Reviewed" check box
  7. Submit the form
  8. Validate the To Do is removed from the To Do's list
  9. In the "Client" column locate the To Do generated for [ClientB]
  10. Repeat step 1a,
  11. Validate results are as expected, ensuring the clients name displays in the format, "First Name Middle Name Last name"
  12. In the "Client" column locate the To Do generated for [ClientC]
  13. Repeat step 1a
  14. Validate results are as expected, ensuring the clients name displays in the format, "First Name Middle Name Last name Suffix"
  15. In the "Client" column locate the To Do generated for [ClientD]
  16. Repeat step 1a
  17. Validate results are as expected, ensuring the clients name displays in the format, "Prefix First Name Middle Name Last Name"
  18. In the "Client" column locate the To Do generated for [ClientE]
  19. Repeat step 1a
  20. Validate results are as expected, ensuring the clients name displays in the format, "Prefix First Name Middle Name Last name Suffix"
Topics
• NX
Update 30 Summary | Details
All Doc Widget - Time field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • LookupTypes
  • UserModeledFormA
Scenario 1: 'All Documents' widget - Modeled Form data row validations
Specific Setup:
  • A client is enrolled in an existing episode [TestClient]
  • Have two modeled forms [FormA] and [FormB]
  • [FormA] is based on a table that is "Date" sorted. [Note: this is configured with prompt "Is This Table Date Sorted" set to "Yes" in "Table Definition"]
  • [FormB] is not based on a table that is "Date Sorted"
  • Have the "Primary All Documents Widget" on the users home view
  • [FormA] and [FormB] have been added to the "All Forms" tab of the widget using form "All Documents Widget Definition"
  • [FormB] have been added to the "All Forms" tab of the widget using form "All Documents Widget Definition"
  • Please note: The "Primary All Documents Widget" is for Avatar NX systems only.
Steps
  1. Select a client [TestClient]
  2. Open [FormA] (Modeled Form 'Date Sorted')
  3. Select an episode
  4. Populate any desired fields
  5. Submit the form
  6. Validate the form files successfully
  7. Note the data entry date and time
  8. Open [FormB] (Modeled form not 'Date Sorted')
  9. Select an episode
  10. Populate any desired fields
  11. Submit the form
  12. Validate the form files successfully
  13. Note the data entry date and time
  14. At the home view, select [TestClient]
  15. Navigate to the "Primary All Documents Widget" and click the "Refresh" button
  16. Click the "All Forms" tab
  17. Select [FormA] from the 'Form Description' field.
  18. Validate the "Form Description" field is populated with the form name for [FormA]
  19. Select the episode from the "Episode" field
  20. Validate the "Date" column is populated with date noted in step 2
  21. Validate the "Time" field is 'not' populated, as expected
  22. Validate each of the columns are populated, as expected
  23. Select [FormB] from the 'Form Description' field.
  24. Validate the "Form Description" field is populated with the form name for [FormB]
  25. Select the episode from the "Episode" field
  26. Validate the "Date" column is populated with date noted in step 3
  27. Validate the "Time" field is populated, as expected with time noted in step 3
  28. Validate each of the columns are populated, as expected
Topics
• All Documents Widget
Update 31 Summary | Details
Client Purge Setup - Deleting record
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Purge Setup
Scenario 1: Client Purge Setup - Define Exception Rules - Adding / Deleting rules
Specific Setup:
  • User Definition:
  • The 'Client Purge Setup' form is available in the list of forms.
  • The 'Client Purge Setup' form is selected to enable them in the Avatar menu.
Steps
  1. Open the 'Client Purge Setup' form.
  2. Enter the number of years since the last movement or service for a client to be eligible for purge in the field ‘Years After Last Contact to Be Excluded From Purge’.
  3. In the field 'Months After Last Payment/Adjustment To Be Eligible From Purge', enter the number of months since the last payment/adjustment a client should have to be eligible for purge.
  4. In the ‘Default Reason for Exclusion’ field, select a default reason value to be used by the purge form when clients qualified to be purged are manually excluded.
  5. Click [Define Exception Rules].
  6. Verify the grid opens successfully.
  7. Enter one exception rule to be used by the 'Client Purge' form.
  8. Enter the name of the table to be used for the exception criteria in the 'System Table' field.
  9. Enter the name of the field to be used for the exception criteria in the 'Field' field.
  10. Enter one of the operators to be used for the exception criteria in the 'Conditional' field. Note - The ‘BT’(Between) conditional requires a properly formatted value in the ‘Field Value’ column formatted as number, comma, number. When the ‘Exists’ conditional is selected the ’Field Value’ column is not required but it remains a required field for all other conditionals.
  11. Enter desired value in the 'Field Value' field.
  12. Enter desired value in the 'Record Selection' field, select 'Most Recent’ to use the most recent records regardless of the date and time. Select ‘Past (Minutes)’ to use only records from today created in the past minutes as defined in the field ‘Record Selection Range (Minutes)’.
  13. In the field ‘Record Selection Range (Minutes)’, enter the number of minutes to be used when evaluating a Record Selection defined as ‘Past (Minutes)’
  14. Ensure the field ‘Record Selection Date Field’ displays only date properties and will default to the data entry date field if it exists in the table.
  15. Click [Save].
  16. Click [Yes].
  17. Click [Submit].
  18. Open the 'Client Purge Setup' form.
  19. Click [Define Exception Rules].
  20. Verify the exception rule created displays correctly as entered.
  21. Select the rule.
  22. Click [Delete].
  23. Click [Save].
  24. Click [Submit].
  25. Open the 'Client Purge Setup' form.
  26. Click [Define Exception Rules].
  27. Verify the exception rule does not display and deleted permanently.
  28. Close the grid.
  29. Click [Discard].
Topics
• RADplus Utilities
Update 37 Summary | Details
'Create New Treatment Plan' process - Registry Setting creation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Create New Treatment Plan
  • Registry Settings (CWS)
  • Treatment Plan
Scenario 1: Create a new copy of the 'Treatment Plan' form using 'Create New Treatment Plan'
Steps
  1. Access the 'Create New Treatment Plan' form.
  2. Enter the desired value in the 'Treatment Plan Name' field.
  3. Select the desired value in the 'Episode Required' field.
  4. Click [Submit].
  5. Validate a message is displayed stating: Are you sure you want to create a new copy of the Treatment Plan?
  6. Click [Yes].
  7. Validate a message is displayed indicating the Treatment Plan form has been created.
  8. Click [OK] and close the form.
  9. Access the 'Registry Settings' form.
  10. Enter "Level of Care" in the 'Limit Registry Settings to the Following Search Criteria' field.
  11. Click [View Registry Settings].
  12. Validate the 'Enable Level of Care Functionality' registry setting is displayed for all 'Treatment Plan' forms, including the newly created 'Treatment Plan' copy.
  13. Close the form.
Topics
• Registry Settings • Treatment Plan
Update 51 Summary | Details
Modeled Forms - Table Alias
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
Scenario 1: Modeled Forms - "Table Alias" field and data validations
Specific Setup:
  • Have a client [TestClient] who is active in an existing episode
  • Have a modeled form [TestForm] that contains:
  • A field [TestField] that is not mapped to any of the field in the "Vital Signs" alias table. For this example a "Dictionary" type field is used
  • Mapped "Table" aliased fields. For this test [TestForm] has the following fields in its table [TestTable], that are mapped in "Table Definition" to the following fields in the "CWS" table alias, "Vital Signs":
  • Date
  • Time
  • Diastolic Blood Pressure
  • Systolic Blood Pressure
  • Respiration
  • Please Note: For the "CWS" "Vital Signs" table alias used in this test, the "Date" and "Time" alias fields are required to be populated at the time submission in order to file the data submitted in the mapped alias fields, into the "SYSTEM.cw_vital_signs" table.
  • Have a report created to display data in the modeled table [TestTable]
  • Have a report created to display data in the "SYSTEM.cw_vital_signs" table
  • Have a report created to display data in the "SYSTEM.RADplus_error_log" table
Steps
  1. On the home view, select [TestClient]
  2. Open form [TestForm]
  3. Populate the field [TestField]
  4. Populate the table alias mapped "Date" and "Time" fields
  5. Populate the other mapped alias fields noted in the setup.
  6. Submit the form
  7. Validate the form submits successfully
  8. Run the report to display data in the modeled table [TestTable]
  9. Validate data for all fields populated in step 2a and b, are displayed as expected
  10. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  11. Validate rows for all the mapped table alias fields populated in step 2b, are displayed as expected
  12. Run the report to display data in the "SYSTEM.RADplus_error_log"
  13. Validate there are no messages related to the table alias submission displayed, as expected
  14. Open form [TestForm] and add a new row
  15. Populate just the field [TestField], which is not a mapped alias field
  16. Submit the form
  17. Validate the form files successfully
  18. Run the report to display data in the modeled table [TestTable]
  19. Validate data for field [TestField] populated in step 3a is displayed populated as expected
  20. Validate none of the other fields are populated in the report, as expected
  21. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  22. Validate there are no rows populated from the form submission in step 4a, as the required table alias mapped "Date" and "Time" fields were both not populated.
  23. Run the report to display data in the "SYSTEM.RADplus_error_log"
  24. Validate there are no messages related to table alias submission, as both of the required alias mapped fields were not populated, indicating no attempt to file data in the alias table
  25. Open form [TestForm] and add a new row
  26. Populate field [TestField]
  27. Leave either the alias mapped "Date" or mapped "Time" field unpopulated, and populate any of the other alias mapped fields.
  28. Submit the form
  29. Validate the form submits successfully
  30. Run the report to display data in the modeled table [TestTable]
  31. Validate data for all fields populated in step 4a and 4b, are displayed as expected
  32. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  33. Validate there are no rows populated for the submission in step 4c, as one of the two required fields for alias table submission was not populated.
  34. Run the report to display data in the "SYSTEM.RADplus_error_log"
  35. Validate there is a row with a message stating "Table Alias Submission Failed Validation" displayed
Topics
• Diagnosis • NX
2022 Update 124 Summary | Details
Chart View
Scenario 1: "Chart" view - 'Sort/Filter' data row validations
Specific Setup:
  • Have a modeled form [TestForm] that contains an "SQL Multiple Dictionary" field [MultField]
  • [Multfield] contains several dictionary values with various character counts. For this example:
  • [ValueA] has a character count of "32"; [ValueB] has a character count of "64"; [ValueC] has a character count of "128; [ValueD] has a character count of "256"; [ValueE] has a character count of "299"
  • [ClientA], [ClientB] and [ClientC] that have data rows submitted in [TestForm]
  • [ClientA] has two rows submitted
  • [Row1] with [ValueA] selected
  • [Row2] with [ValueB] selected
  • [ClientB] has four rows submitted
  • [Row1] with [ValueA] selected
  • [Row2] with [ValueB] selected
  • [Row3] with [ValueC] selected
  • [Row4] with [ValueC], [ValueD] and [ValueE] selected
  • [ClientC] has one row submitted
  • Row1 with [ValueB], [ValueC] and [ValueE] selected
  • [TestUser] has form [TestForm] added to their "Chart" view forms
Steps
  1. At the home view, select [ClientA] and then right click to open their chart
  2. Select [TestForm] from the chart forms section
  3. Validate the data row preview section, displays all the rows filed for [ClientA] in the setup
  4. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField],
  5. Click the "Sort/Filter" dropdown list
  6. Validate the "Filter" box contains each row submitted for [ClientA] in the setup
  7. Select one or more values from list and click [OK]
  8. Validate just the row(s) selected are displayed in the preview section
  9. Validate the dictionary value(s) submitted in each row, are displayed as expected
  10. Close the clients chart
  11. At the home view, select [ClientB] and then right click to open their chart
  12. Select [TestForm] from the chart forms section
  13. Validate the data row preview section, displays all the rows filed for [ClientB] in the setup
  14. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField]
  15. Click the "Sort/Filter" dropdown list
  16. Validate the "Filter" box contains each row submitted for [ClientB] in the setup
  17. Select one or more values from list and click [OK]
  18. Validate just the row(s) selected are displayed in the preview section
  19. Validate the dictionary value(s) submitted in each row, are displayed as expected
  20. Close the clients chart
  21. At the home view, select [ClientC] and then right click to open their chart
  22. Select [TestForm] from the chart forms section
  23. Validate the data row preview section, displays all the rows filed for [ClientC] in the setup
  24. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField]
  25. Click the "Sort/Filter" dropdown list
  26. Validate the "Filter" box contains each row submitted for [ClientC] in the setup
  27. Select one or more values from list and click [OK]
  28. Validate just the row(s) selected are displayed in the preview section
  29. Validate the dictionary value(s) submitted in each row, are displayed as expected
  30. Close the clients chart
Guarantor Search fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Fast Financial Eligibility
Scenario 1: "Guarantor" lookup - search results validation
Specific Setup:
  • In form "Guarantor/Payors", have or create two guarantors:
  • [GuarA] has a value populated in "Guarantor Name for Alpha Lookup" field that include parenthesis. (Make a note of their "Guarantor" number assigned)
  • [GuarB] does not have a value populated in "Guarantor Name for Alpha Lookup" field that includes parenthesis. (Make a note of their "Guarantor" number assigned)
  • Have access to a form that contains a "Guarantor" lookup field. For this example, form "Fast Financial Eligibility" is used
Steps
  1. Open the form "Fast Financial Eligibility"
  2. Select any client
  3. Navigate to the "Guarantor #1" search field
  4. Enter a search for [GuarA] using their entire "Guarantor Name for Alpha Lookup" value
  5. Validate the expected value is found and displays without truncation
  6. Enter a search for [GuarA] using just the first letter of their "Guarantor Name for Alpha Lookup" value
  7. Validate the expected value is found and displays without truncation
  8. Enter a search for [GuarA] using the first two or more letters of their "Guarantor Name for Alpha Lookup" value
  9. Validate the expected value is found and displays without truncation
  10. Enter a search for [GuarA] using their assigned "Guarantor" number
  11. Validate the expected value is found and displays without truncation
  12. Populate any other desired fields on the form
  13. Submit the form
  14. Validate the form files successfully
  15. Return to the "Fast Financial Eligibility" form
  16. Select the client used in step 1
  17. Select the row submitted in step 1
  18. Validate that all field are populated, as expected
  19. Open the form "Fast Financial Eligibility"
  20. Select any client
  21. Navigate to the "Guarantor #1" search field
  22. Enter a search for [GuarB] using their entire "Guarantor Name for Alpha Lookup" value
  23. Validate the expected value is found and displays without truncation
  24. Enter a search for [GuarB] using just the first letter of their "Guarantor Name for Alpha Lookup" value
  25. Validate the expected value is found and displays without truncation
  26. Enter a search for [GuarB] using the first two or more letters of their "Guarantor Name for Alpha Lookup" value
  27. Validate the expected value is found and displays without truncation
  28. Enter a search for [GuarB] using their assigned "Guarantor" number
  29. Validate the expected value is found and displays without truncation
  30. Submit the form
  31. Validate the form files successfully
  32. Return to the "Fast Financial Eligibility" form
  33. Select the client used in step 3
  34. Select the row submitted in step 3
  35. Validate that all field are populated, as expected
Appointment Scheduling - notifications
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Review To Do Item (PM)
Scenario 1: Scheduling Calendar - Validate appointment status To Do notifications
Specific Setup:
  • In form "Appointment Scheduling Notification Type Definition", have notification status submitted within form for an "Appointment Status". For this example appointment status "Cancelled" is used.
  • In form "Notifications Setup", have a notification created with the following setup:
  • The "Appointment Canceled" selected in the "Notification Type" field.
  • The "Appointment Practitioner" selected in the "Send Notification(s) to field.
  • "To Do" selected in the "Notification Method" field.
  • The 'Notification Text' field, has text populated in the field that contains greater than or less than symbols. For example, text that may include keyword values: "Your <APPOINTMENT_DATE> appointment with <PATIENT_NAMES> scheduled for <CURRENT_DATE> has been cancelled".
  • [TestUser] is a staff member and has the "My To Do's" widget on their home view.
  • For any client, have an appointment [TestAppt] scheduled with [TestUser] in form "Scheduling Calendar".
  • Log in as [TestUser]
Steps
  1. Open form "Scheduling Calendar"
  2. Navigate to [TestAppt] on the scheduling calendar
  3. Right-Click on the appointment and select "Details/Edit"
  4. In the "Scheduling Calendar - Appointment Details" form, click on the "Appointment Status" field and select "Cancelled"
  5. Submit the form
  6. Close the Scheduling Calendar" form
  7. At the home view, navigate to the "My To Do's" widget"
  8. Locate the To Do with "Scheduling Calendar - Appointment Details" populated In the "Form" column
  9. Click [Review To Do Item]
  10. Validate the information displayed in the "To Do Information" field is as expected and consistent with the notification message text entered in form "Notifications Setup", in the set up
  11. Click the "Reviewed" check box
  12. Click [Submit]
  13. Validate the To Do has been removed from the "My To Do's" widget
Topics
• Chart Review • Guarantor • NX • Appointment Management
2022 Update 139 Summary | Details
ScriptLink - launch form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
Scenario 1: Validate a "ScriptLink" script set on a field to launch another form
Specific Setup:
  • Have a "ScriptLink" script that is configured to launch a specific form. For this example, form "Update Client Data" is used
  • In "Form Designer" the script has been imported in any desired form [TestForm] and is set to trigger when a field [TestField] is populated
Steps
  1. Open form [TestForm]
  2. Select a client [TestClient]
  3. Navigate to field [TestField]
  4. Populate the field
  5. Validate the form configured to launch via the "ScriptLink" script, has launched for [TestClient]. For this exampled form "Update Client Data" has launched
  6. Populate the form
  7. Submit the form
  8. Validate the form files successfully
  9. Back on [TestForm], populate the desired fields on form
  10. Submit the form
  11. Validate the form files successfully
  12. Return to form [TestForm]
  13. Select [TestClient]
  14. Select the row just submitted in step 1
  15. Validate field [TestField] is populated as expected
  16. Validate all other fields are populated as expected
  17. Close the form
  18. Open form "Update Client Data"
  19. Select [TestClient]
  20. Validate all fields are populated as expected
Topics
• Scriptlink • Form Designer • NX