Skip to main content

RADplus 2024 Monthly Release 2024.01.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 14 Summary | Details
The 'Limit Wait Time for Dynamic Message Box' Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Billing
  • Treatment Plan
Scenario 1: Basic Troubleshooting - testing dynamic forms
Specific Setup:
  • The user must have access to the 'Basic Troubleshooting' form.
  • The 'Limit Wait Time for Dynamic Message Box' registry setting must be set to "60;2".
Steps
  1. Access the 'Basic Troubleshooting' form.
  2. Validate the form displays as expected.
  3. Click [Test Dynamic Forms].
  4. Validate a 'Dynamic Form Test' message displays stating: "Test Successful".
  5. Wait for 60 seconds and validate the message refreshes and appears again on the form.
  6. Wait for another 60 seconds and validate the message no longer displays after the second appearance.
  7. Click [Discard].
Topics
• Treatment Plan • Quick Billing
Update 18 Summary | Details
Form Definition - Service Documentation forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
  • Table Definition (CWS)
  • Form Definition (CWS)
  • Copy Form to Different System Code (CWS)
Scenario 1: Service Documentation Notes form creation
Specific Setup:
  • Multiple root system codes are defined (System Code A & System Code B).
  • Must be logged in with "System Code A".
  • An envelope must be defined in the 'Envelope Definition' CWS form (Envelope A).
  • A CWS table must be defined (Table A) associated to "Envelope A" with the following table columns:
  • 'Progress Note For' - Single Select Dictionary
  • 'Note Addresses Which Existing Service/Appointment' - Single Select Dictionary
  • 'Service Program' - Single Select Dictionary
  • 'Service Practitioner' - Staff Lookup
  • 'Service Date' - Date
  • This table must have "Yes" selected in the 'Service Documentation Table' field.
  • The above table columns must be mapped to the respective Progress Note prompts in the 'Service Documentation' section of the 'Table Definition' form.
  • A CWS form must be defined (Form A) associated to "Envelope A" and "Table A" that does not yet have the 'Service Documentation' table columns added to the form.
  • The logged in user must have access to "Form A".
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Copy Form to Different System Code' CWS form.
  2. Select "Form A" in the 'Select Form' dialog and click [OK].
  3. Enter "System Code B" in the 'Target System Code' field.
  4. Enter the desired user in the 'Target System Username' field.
  5. Enter the password for the user in the 'Target System Password' field.
  6. Select the desired value in the 'Target System Menu to Place Form Under' field.
  7. Select the desired value in the 'Copy unlocked dictionary values' field.
  8. Populate any other desired fields.
  9. Submit the form.
  10. Access the 'Form Definition' CWS form for "Form A".
  11. Navigate to the "Object Def." section.
  12. Click [Add New Item].
  13. Add the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns.
  14. Populate any required and desired fields.
  15. Submit the form.
  16. Access the 'Form Definition' CWS form for "Form A".
  17. Navigate to the "Object Def." section.
  18. Validate the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns added in the previous steps are displayed.
  19. Click [Add New Item].
  20. Add the 'Service Program', 'Service Date', and 'Service Practitioner' table columns.
  21. Populate any other required and desired fields.
  22. Submit the form.
  23. Select "Client A" and access "Form A".
  24. Validate the form displays as expected with the following fields:
  25. 'Progress Notes For'
  26. 'Note Addresses Which Existing Service/Appointment'
  27. 'Service Program'
  28. 'Service Date'
  29. 'Service Practitioner'
  30. File a new service for the client.
  31. Verify successful submission.
  32. Access Crystal Reports or other SQL Reporting Tool.
  33. Create a report using the 'SYSTEM.billing_tx_history' SQL table.
  34. Validate a row is displayed for "Client A" for the service created via "Form A".
  35. Close the report.
Envelope Import with Form Designer changes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
Scenario 1: Envelope Export/Import - 'Include Form Design Changes' in the file set to "Y"
Specific Setup:
  • Have a modeled form (Form A), contained in (Envelope A), that will be used to make form designer changes.
  • "Form A" must have a primary/secondary table and a multi-iteration table associated.
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" from the 'Forms' field.
  3. Make any type of form designer change in the section [FDchange1]. For example, a field is moved to different location.
  4. Save the changes and exit the form.
  5. Access the 'Envelope Export' form.
  6. Select "Envelope A".
  7. In the "Include Form Design Changes? field, select "Yes".
  8. Click [Begin Export].
  9. Validate export is completed successfully (Export A).
  10. Access the 'Form Designer' form.
  11. Select "Form A" from the 'Forms' field.
  12. Make another form designer change in the section [FDchange2].
  13. Save the changes and exit the form.
  14. Access "Form A".
  15. Validate [FDchange1] and [FDchange2] are both present in the form.
  16. Access the 'Envelope Import' form.
  17. Click [Select Envelope For Import].
  18. Navigate the location "Export A".
  19. Select the file and select "Overwrite Existing".
  20. In the "Include Form Design Changes? field, select "Yes". [Note: "Yes" implies that any form designer changes contained in the import file, 'will' be imported and/or overwrite any existing changes already made on the form].
  21. Click [Begin Import Scan].
  22. Validate there are no errors/warnings found within the import file scan results.
  23. Click [Begin Import].
  24. Validate import is completed successfully.
  25. Access "Form A".
  26. Validate [FDchange1] is present on the form.
  27. Validate [FDchange2] is not present on the form.
  28. Close the form.
Topics
• Service Documentation • Envelope Import • Form Designer • Envelope Export
Update 27 Summary | Details
Observer NX - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Allergies and Hypersensitivities
  • Network Connectivity
Scenario 1: Observer NX - Validate filtering client list
Steps

Internal Testing Only.
Topics
n/a
Update 31 Summary | Details
Search Results - Diagnosis Filtering
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
Scenario 1: Diagnosis - Editing a diagnosis
Specific Setup:
  • Admission:
  • An existing client is identified or a new client is admitted. Note the client id/Name.
  • Diagnosis:
  • A client must have a diagnosis entered.
Steps
  1. Open the 'Diagnosis' form.
  2. Search for desired client in the 'Select Client' field.
  3. Validate results display.
  4. Select desired client from the results.
  5. Validate a Pre-Display is displayed showing existing diagnoses for the client.
  6. Select an existing diagnosis record.
  7. Click [Edit].
  8. Enter an invalid time in the 'Time of Diagnosis' field.
  9. Validate an Error message stating: "Invalid time format. HH:MM AM, HH:MM PM or HHMM military time (Midnight is 0000 hours.)"
  10. Validate the 'Time of Diagnosis' field defaults to the time that was saved prior.
  11. Change the 'Time of Diagnosis' field to the current time.
  12. Enter a different practitioner in the 'Diagnosing Practitioner' field.
  13. Select "Void" in the 'Status' field.
  14. Validate the voided diagnosis is crossed off.
  15. Navigate to the myDay view.
  16. Navigate back to the open 'Diagnosis' form.
  17. Validate the voided diagnosis is crossed off.
  18. Validate the 'Diagnosing Practitioner' contains the value entered in the previous steps.
  19. Click [Submit].
  20. Validate a Pre-Display Confirmation dialog is displayed stating: Do you want to return to Pre-Display?
  21. Click [Yes].
  22. Select desired diagnosis record.
  23. Click [Edit].
  24. Select "No" in the 'Show Active Only' field.
  25. Validate the voided diagnosis displays and is crossed off.
  26. Close the form.
  27. Open the "Registry Settings" form.
  28. Search for the registry setting "Default Limit Results by ICD Category".
  29. Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
  30. Click [Submit] to file the form.
  31. Open the "Diagnosis" form.
  32. Edit a previously added row of the "Diagnosis" table.
  33. Search for any a number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 2: Diagnosis - Diagnosis Entry
Specific Setup:
  • A client must be enrolled in an active episode (Client A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Click [Add].
  3. Select "Admission" in the 'Type of Diagnosis' field.
  4. Press the 'Tab' key on the 'Type of Diagnosis' field.
  5. Validate the focus shifts to the 'Date of Diagnosis' field and the admission date is displayed as expected.
  6. Press the 'Tab' key on the 'Date of Diagnosis' field.
  7. Validate the focus shifts to the 'Time of Diagnosis' field.
  8. Enter any value in the 'Time of Diagnosis' field.
  9. Click [New Row].
  10. Search for and select the desired value in the 'Diagnosis Search' field.
  11. Verify the 'Add To Problem List' field is defaulted to 'Yes'.
  12. Populate all required and desired fields.
  13. Click [Submit] and [No].
  14. Select "Client A" and access the ‘Diagnosis’ form.
  15. Select the previously created diagnosis row to edit.
  16. Click [Edit].
  17. Click [New Row].
  18. Search for and select the desired value in the 'Diagnosis Search' field.
  19. Validate that the 'Diagnosis Search' returns the expected diagnoses.
  20. Populate all required and desired fields.
  21. Click [Submit] and [No].
  22. Select "Client A" and access the 'Diagnosis' form.
  23. Select the diagnosis row edited in the previous steps.
  24. Click [Edit].
  25. Validate that the newly added diagnosis row is displayed.
  26. Close the form.
  27. Open the "Registry Settings" form.
  28. Search for the registry setting "Default Limit Results by ICD Category".
  29. Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
  30. Click [Submit] to file the form.
  31. Select 'Client A' and open the "Diagnosis" form.
  32. Edit a previously added row of the "Diagnosis" table.
  33. Search for any number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 3: Registry Setting - Default Limit Results by ICD Category"
Specific Setup:
  • Note: When setting up the new Registry Setting, 'Default Limit Results by ICD Category', also check the following registry setting: 'Avatar PM->Client Information->Diagnosis->->->Remove References to ICD-9/DSM-IV Codesets'. If it's set to '2' do the following:
  • Open the "Client Charge Input With Diagnosis Entry" form.
  • Attempt to do a search on Diagnosis.
  • Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
  • If 'No Records Found' is in the search results, then update 'Remove References to ICD-9/DSM-IV Codesets' as follows:
  1. Change the value from 2 to 0 and submit the change.
  2. Change the value from 0 back to 2 and submit the change.
  3. Repeat steps the above steps to verify that the results are displayed as expected.
Steps
  1. Open the "Registry Settings" form.
  2. Search for the registry setting "Default Limit Results by ICD Category".
  3. Note: This registry setting is only available in NX.
  4. Note the registry setting is defaulted to blank. This will generate all results.
  5. Open any of the following forms that include a diagnosis search such as "Client Chart Input with Diagnosis", "Diagnosis", "Edit Service Information", "Service Panel Chart Input", "Set Associated Codes", Ambulatory or Inpatient Progress Notes with Diagnosis, etc.
  6. Attempt to do a search on Diagnosis.
  7. Validate the search result returns all values and does not filter any results.
  8. Open the "Registry Settings" form.
  9. Search for the registry setting "Default Limit Results by ICD Category".
  10. Set the registry setting to a valid value other than blank.
  11. Open any of the forms mentioned in step 2.
  12. Attempt to do a search on Diagnosis.
  13. Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
Topics
• Diagnosis
Update 36 Summary | Details
Console Widget Viewer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • All Documents Widget Definition
  • View Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Access the 'Practitioner Enrollment' form.
  13. Select the practitioner linked to the logged in user for view/update.
  14. Validate that all the required/ desired fields are populated correctly.
  15. Click [Categories/Taxonomy] tab.
  16. Select any existing row in 'Category/Taxonomy' field.
  17. Validate all required fields are populated.
  18. Click "Practitioner Credentials" button.
  19. Select "Credential A" from the list.
  20. Click [OK]
  21. Click [Add Practitioner Categories].
  22. Validate the 'Confirm' dialog contains "Saved. Please note: The changes will take effect when you submit the form." message.
  23. Click [OK].
  24. Click [Submit].
  25. Select "Client A" and navigate to the 'All Documents' view.
  26. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  27. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  28. Select the progress note for viewing.
  29. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  30. Click [Print]
  31. Select "Print Current" dropdown value.
  32. Validate the practitioner's credential "Credential A" is displayed on the printable form.
  33. Validate an [Append] button is displayed and click it.
  34. Validate the 'Append Progress Notes' form is displayed.
  35. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  36. Click [Submit].
  37. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  38. Click [Accept].
  39. Enter the password associated with the logged in user and click [Verify].
  40. Click [Close All] in the 'Console Widget Viewer'.
  41. Refresh the 'All Documents' widget.
  42. Select the progress note appended in the previous steps for viewing.
  43. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  44. Click [Close All].
Scenario 2: Progress Notes (Group and Individual) - Add a progress note via the Client Chart
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Please note : this is for myAvatar only.
  • The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
  1. Double click on "Client A" in the 'My Clients' widget.
  2. Verify the 'Chart View' for "Client A" is displayed.
  3. Select 'Progress Notes (Group & Individual)' on the left-hand side.
  4. Validate any previously filed notes are displayed for "Client A".
  5. Click [Add].
  6. Validate the 'Progress Notes (Group and Individual)' form is displayed.
  7. Populate all required and desired fields.
  8. Select "Draft" in the 'Draft/Final' field.
  9. Click [File Note].
  10. Validate a message is displayed stating: Note Filed.
  11. Click [OK].
  12. Validate the 'Chart View' is displayed.
  13. Refresh the chart.
  14. Validate the note filed in the previous steps is displayed.
  15. Close the chart.
Topics
• Progress Notes • All Documents Widget
Update 38 Summary | Details
Form Designer - Exports
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
  • Form Designer (PM)
Scenario 1: Form Designer - Validations in UAT environment
Specific Setup:
  • The 'Close Charges' form has had prior form designer changes made.
  • Must be logged in with a UAT system code.
Steps
  1. Access the 'Form Designer' form.
  2. Select "Close Charges" in the 'Forms' field.
  3. Select "Close Charges" in the 'Sections' field.
  4. Select "Yes" in the 'Revert To Other Form Designer Copy' field.
  5. Validate the 'Export All Sections or Selected Section?' field is disabled.
  6. Select "No" in the 'Revert To Other Form Designer Copy' field.
  7. Validate the 'Export All Sections or Selected Section?' field is disabled.
  8. Close the form.
Topics
• Form Designer
Update 39 Summary | Details
Registry Settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Codes
  • Client Ledger
Scenario 1: Validating the error message Registry Setting -'Unit Calculation with Minimum Duration' in 'Service Documentation' Form
Specific Setup:
  • Registry Settings:
  • Set the value 'Unit Calculation with minimum duration' ="Y".
  • Client:
  • Identify an existing client or create a new client. Note the client’s admission date.
  • Verify existing or add a Financial Eligibility record.
  • Service Code:
  • ‘An existing service code is identified that has a value defined for the 'Minimum Duration for Unit Calculation' field (Service Code 1).
  • Progress Note entry and Service Documentation entry need to be updated to compare service duration entered in Notes against the Service Code’s configuration for “Minimum Duration for Unit Calculation”.
  • A modeled form containing Progress Note fields (Service Documentation) must be imported through 'Envelope Import' and the logged in user must have access to it.


Steps
  1. Open "Service Codes" form.
  2. Click [Edit] in Add New Or Edit Existing.
  3. Enter 'Service Code 1' in 'Service Code'.
  4. Capture the value in 'Minimum Duration for Unit Calculation'.
  5. Click [Submit].
  6. Click [No].
  7. Open "Service Documentation Notes Form".
  8. Enter the 'Client ID' in [Search Client].
  9. Enter any value in [Date of Service].
  10. Enter 'Service Code 1' created in setup in [Service Code].
  11. Enter a value more than 'Minimum duration' field in 'Service Code' form in 'Service Duration'.
  12. Click [Submit].
  13. Open "Client Ledger" form.
  14. Enter the 'Client ID'.
  15. Click [All Episodes] in 'Claim/Episode/All Episodes'.
  16. Click [Simple] in 'Ledger Type'.
  17. Click [Yes] in 'Include Zero Charges'.
  18. Click [Process].
  19. Validate whether the services created in "Service Documentation notes" has been assigned to appropriate guarantor in Client Ledger.
  20. Click [X].
  21. Click [Yes].
  22. Click [Discard].
  23. Repeat Steps 7-22, with a value in 'Service Duration' less than the 'Minimum Duration for Unit Calculation' set in the "Service Codes" form.
  24. Open the "Registry Settings" form and change the value of the ‘Unit Calculation with Minimum Duration‘ setting to ‘YW’.
  25. Validate the warning message displayed: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes.
  26. Click [OK].
  27. Click [Submit].
  28. Open the "Registry Settings" form and change the value of the ‘Unit Calculation with Minimum Duration‘ setting to ‘YE’.
  29. Repeat Steps 7-22, with a value in 'Service Duration' less than the 'Minimum Duration for Unit Calculation' set in the "Service Codes" form.
  30. Validate the error message displayed: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes.
  31. Click [OK].
  32. Click [Submit].
Topics
• Registry Settings
Update 40 Summary | Details
Mobile user count
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • Dynamic Form - User Role Definition - Select User Role
Scenario 1: Validate adding a user in form 'User Definition'
Specific Setup:
  • A form must be defined in 'Document Management Definition' with an apostrophe (Form A).
Steps
  1. Access the 'User Definition' form.
  2. Enter the desired value in the 'User ID' field.
  3. Enter the desired value in the 'User Description' field.
  4. Populate all required and desired fields.
  5. Navigate to 'Document Management' tab.
  6. Select "No" in the 'Is this user a Document Management Administrator' item.
  7. Select "Specify forms" in the 'Forms Allowed to Print' field.
  8. Click [Select Forms to Print].
  9. Select "Form A" in the 'Select Forms' field.
  10. Click [OK].
  11. Click [Select Forms to Print].
  12. Validate "Form A" is still selected.
  13. Click [OK].
  14. Submit the form.
  15. Access the 'User Definition' form.
  16. Select the user created in the previous steps.
  17. Navigate to 'Document Management' tab.
  18. Click [Select Forms to Print].
  19. Validate "Form A" is still selected.
  20. Click [OK] and close the form.
To Do and Delete/Re/Assign - All Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Approver Override
  • Escalate To Do Item
  • Delete/Re-Assign To Do Items
Scenario 1: "Approver Override" form - Validate Document display and functionality
Specific Setup:
  • Have two users who are staff members [StaffA] and [StaffB].
  • Have two forms enabled for document routing [FormA] and [FormB] and both use form type, [TypeA].
  • [ClientA] has two document rows [DocRow1] and [DocRow2] submitted in [FormA] that has been routed to [StaffB] for approval.
  • [ClientB] has two document rows [DocRow1] and [DocRow2] submitted in [FormB] that has been routed to [StaffB] for approval.
  • [StaffA] has the "My To Do's" widget on their home view.
  • Log in as [StaffA].
Steps
  1. Open form "Approver Override":
  2. In the "Form Type" field choose In the "Entity" field, select [TypeA].
  3. In the "Entity" field select [ClientA]:
  4. Populate the "From" and "To", date fields.
  5. Click the "List of Documents" field:
  6. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  7. Select [DocRow1]:
  8. Click [Display Document] to view the document:
  9. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow1], as expected.
  10. Click [Close].
  11. Click the "List of Documents" field:
  12. Select [DocRow2].
  13. Click [Display Document] to view the document:
  14. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow2], as expected.
  15. Click [Close].
  16. In the "Entity" field select [ClientB]:
  17. Populate the "From" and "To", date fields.
  18. Click the "List of Documents" field.
  19. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  20. Select [DocRow1]:
  21. Click [Display Document] to view the document:
  22. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow1], as expected.
  23. Click [Close]
  24. Click the "List of Documents" field
  25. Select [DocRow2]
  26. Click [Display Document] to view the document
  27. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  28. Click [Update Approvers]
  29. In the "Route Document To" screen, uncheck the current selected approver
  30. In the "Add Approver" field, select [StaffA]
  31. Click [Submit]
  32. Navigate to the "My To Do's" widget, and locate the row with the To Do sent in step 1d
  33. Click [Approve Document]
  34. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  35. Click [Accept]
  36. Populate the "Verify Password" prompt
  37. Click [OK]
  38. Validate the "To Do" is removed from the "My To Do's"
Scenario 2: Delete/Re-Assign To Do's - Validations
Specific Setup:
  • [UserA] has sent a notification To Do [NoteTodoA] to [UserB] via form "Send To Do Notification"
  • [UserA] has also sent a notification to do [NoteTodoB] to [UserC] via form "Send To Do Notification"
  • [UserD] does not have any To Do's in their "My To Do's" list
  • [UserE] has two To Do items [TestToDoA] and [TestToDoB] in their "My To Do's" list, not generated via form "Send To Do Notification"
  • Log in as [UserA]
Steps
  1. Navigate to the "My ToDo's" widget and click to refresh the widget
  2. Click the "Sent & Not Received" column in the widget
  3. Validate [NoteTodoA] generated in setup that was sent to [UserB] is present
  4. Validate [NoteTodoB] generated in setup that was sent to [UserC] is present
  5. Select [NoteTodoA] and click the "Escalate" column in the widget
  6. Click the "Escalate To Do Item" link in the column
  7. In the "Escalate To Do Item" form
  8. Search for [UserD], in the "Select User" search field
  9. Click [Add User]
  10. In the "Sent To" field, click the check box for [UserD]
  11. In the "Note" field, enter a desired message for [UserD]
  12. Click [Submit]
  13. At the "To Do Sent" message dialog, click [OK]
  14. Now select the row for the to do [NoteTodoB] click the "Escalate" column
  15. Click the "Escalate To Do Item" link in the column
  16. In the "Escalate To Do Item" form
  17. Search for [UserE], in the "Select User" search field
  18. Click [Add User]
  19. In the "Sent To" field, click the check box for [UserE]
  20. In the "Note" field, enter a message for [UserE].
  21. Click [Submit]
  22. At the "To Do Sent" message dialog, click [OK]
  23. At the Home View, open form "Delete/Re-Assign To Do Items"
  24. Select "Delete" in the "Delete/Re-assign" field
  25. In the "Select User" field, select [UserD]
  26. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed
  27. Click [OK]
  28. Validate there are no to do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step1, [Please Note: Any To Do's generated via "Send Notification To Do" form, are excluded from the "Delete/Re-Assign To Do Items" form]
  29. Click [OK]
  30. Select "Re-Assign" in the "Delete/Re-assign" field
  31. In the "Select User" field, select [UserD] again
  32. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed again
  33. Click [OK]
  34. Validate there are no To Do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step 1.
  35. Click [OK]
  36. Select "Delete" again in the "Delete/Re-assign" field
  37. This time in the "Select User" field, select [UserE]
  38. Validate the notification to do [NoteToDoB], escalated to [UserE] in step1 is not present in the "To Do's" list box, as expected
  39. Validate [TestToDoA] and [TestToDoB] that were not generated from the "Send To Do Notification" form are present in the "To Do's" list box
  40. Select [TestToDoA] in the "To Do's" list box
  41. Enter any desired comment in the "Comment" field
  42. Submit the form and return to the form
  43. Select "Re-Assign" in the "Delete/Re-assign" field
  44. In the "Select User" field, select [UserE]
  45. Validate [TestToDoA] just deleted is not present in the "To Do's" list box.
  46. Validate the notification [NoteToDoB], escalated to [UserE] is also not present in the "To Do's" list box
  47. Validate [TestToDoB] is present in the "To Do's" list box
  48. Select [TestToDoB]
  49. In the "Select Target User" field, select any other user [UserF] to re-assign the to do to
  50. Submit the form
  51. Validate the form submits successfully
  52. Closet the form
  53. Log out as [UserA]
  54. Log in as [UserF]
  55. Navigate to the "My To Do's" list
  56. Validate the to do reassigned to [UserF] is present in their to do's list as expected
  57. Click [Review To Do Item]
  58. Validate the to do information for [TestToDoB], is displayed as expected
  59. Select the "Review" check box
  60. Submit the form
  61. Validate the To Do is removed from the "My To Do's" widget
To Do List - Other Client Id
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - staff auto assign
  • Practitioner Enrollment
  • Admission (Outpatient)
  • Modeled Client
  • app-create-to-do
  • Review To Do Item (PM)
  • Document Routing Setup (PM)
Scenario 1: Modeled Form - Send To Do
Specific Setup:
  • A modeled form is defined (Form A).
  • "Form A" must have the 'Enable To-Do Creation From Form' field set to "Yes" in 'Form Definition'.
  • A client is enrolled in an existing episode (Client A).
  • Two users (User A & User B) are defined with associated practitioners (Practitioner A & Practitioner B).
Steps
  1. Log in as "User A".
  2. Select "Client A" and access "Form A".
  3. Populate all required and desired fields.
  4. Click [Send To Do].
  5. Validate a 'Create To Do' dialog is displayed.
  6. Select "Practitioner A" in the 'Select Staff' field.
  7. Enter the desired value in the 'Note' field.
  8. Click [Save].
  9. Finalize and submit the form.
  10. Log out.
  11. Log in as "User B".
  12. Navigate to the 'My To Do's' widget.
  13. Validate a To Do is displayed from "User A".
  14. Click [Review To Do Item].
  15. Validate the 'Review To Do Item' form is displayed.
  16. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  17. Click [Submit].
  18. Validate the To Do is no longer displayed.
Topics
• User Definition • User Role Definition • Document Management • ToDo's
Update 48 Summary | Details
'My To Do's' widget - Acknowledgement To Do's
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Dynamic Form - document routing
  • Individual Progress Note
Scenario 1: Document Routing Setup - Use Crystal Report Template - Yes
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The user must have the 'My To Do's' widget configured to their myDay view.
  • Must have a crystal report configured for progress notes document routing (Crystal Report A).
  • The 'Ambulatory Progress Notes' form must be configured in 'Document Routing Setup' as follows:
  • "Yes" selected in the 'Enable Document Routing' field
  • "Yes" selected in the 'Use Crystal Report Template' field.
  • "Crystal Report A" selected in the Crystal Report' field.
  • "Yes" selected in the 'Acknowledgement Allowed' field.
  • The logged in user must have an associated practitioner (Practitioner A).
Steps
  1. Select "Client A" and access any the 'Ambulatory Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Enter any value in the 'Notes Field'.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate a "Confirm Document" dialog is displayed with the crystal report template and note details.
  8. Click [Accept and Route].
  9. Enter the logged in user's password in the 'Verify Password' field.
  10. Add "Practitioner A" as an approver and for acknowledgement.
  11. Click [Submit].
  12. Navigate to the 'My To Do's' widget.
  13. Validate an 'Approve Document' To Do is displayed for "Client A".
  14. Approve and sign off on the document.
  15. Validate the 'Approve Document' To Do is no longer displayed.
  16. Validate an 'Acknowledge Document' To Do is displayed.
  17. Click [Acknowledge Document].
  18. Validate the document is displayed as expected.
  19. Click [Acknowledge].
  20. Enter the logged in user's password in the 'Verify Password' field.
  21. Validate the 'Acknowledge Document' To Do is no longer displayed.
'Table Definition' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Caseload Type Definition (CWS)
  • Notification Type Definition
  • Envelope Definition (CWS)
  • Table Definition (CWS)
  • Form Definition (CWS)
  • Dictionary Update (PM)
Scenario 1: Table Definition - Validate tables with caseload fields
Specific Setup:
  • A caseload type (Caseload A) and Notification type (Notification Type A) must be defined.
  • An envelope (Envelope A) must be defined.
Steps
  1. Access the 'Table Definition' form.
  2. Enter the desired value in the 'Select Table' field and click [New Avatar Table].
  3. Select "Envelope A" in the 'Envelope' field and click [OK].
  4. Enter the desired value in the 'Table Name' and 'Table Description' fields.
  5. Populate any other required and desired fields.
  6. Navigate to the "Column Definition" section.
  7. Click [Add New Item].
  8. Add a column for the 'Addition to Caseload' type as defined in "Caseload A".
  9. Populate any other required and desired fields.
  10. Click [Submit]. This will be referred to as "Table A".
  11. Access the 'Form Definition' form.
  12. Enter the desired value in the 'Select Form' field and click [New Avatar Form].
  13. Select "Envelope A" in the 'Envelope' field and click [OK].
  14. Enter the desired value in the 'Form Name' field.
  15. Select "Table A" in the 'Primary Table' field.
  16. Populate all required and desired fields.
  17. Navigate to the "Section Def." section.
  18. Populate all required and desired fields.
  19. Navigate to the "Object Def." section.
  20. Click [Add New Item].
  21. Add the table column(s) added for "Table A" and populate all desired fields.
  22. Click [Submit].
  23. Access the 'Caseload Type Definition' form.
  24. Click [Select Existing Caseload Type].
  25. Select "Caseload A" in the 'Select Existing Caseload Type' dialog and click [OK].
  26. Validate all previously filed values are displayed.
  27. Click [Submit].
  28. Access the 'Table Definition' form.
  29. Select "Table A" in the 'Select Table' field and click [OK].
  30. Navigate to the "Column Definition" section.
  31. Validate the previously defined column(s) are displayed as expected.
  32. Close the form.
Topics
• Document Routing • Progress Notes • Modeling • Envelope Definition • Table • Forms
Update 50 Summary | Details
Envelope Import/Export
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (CWS)
  • Envelope Import (CWS)
Scenario 1: Envelope Export/Import - Validate modeled forms with "Signature" and "Picture" images
Specific Setup:
  • Have a modeled [EnvelopeA], that contains a modeled form [FormA] configured with:
  • Document routing is enabled and a "Crystal Report" [DocRoutReport] is configured to display the document image
  • A "Pre-Filing" command button report [PreFileRpt], is configured on the form, to display data populated in the form prior to submission
  • 'Signature' and 'Picture" fields on the form, along with any other desired field types
  • Have another modeled envelope [EnvelopeB], that contains a modeled form [FormB] configured with
  • Document routing enabled with "No" "Crystal Report" configured. (Note: this will default to the standard "Tif" image used to display the document data)
  • Signature' and 'Picture" field, along with any other desired field types
  • Have access to forms "Envelope Export" and "Envelope Import"
Steps
  1. Open form "Enveloper Export"
  2. Select [EnvelopeA]
  3. Click [Begin Export]
  4. Navigate to location on the server to store the export file
  5. Click 'OK'
  6. Close the form
  7. Open form "Enveloper Export"
  8. Select [EnvelopeB]
  9. Click [Begin Export]
  10. Navigate to location on the server to store the export file
  11. Click 'OK'
  12. Close the form
  13. Open form "Enveloper Import"
  14. Click [Select Envelope Import File]
  15. Navigate to the location of [EnvelopeA]
  16. Select the file
  17. Click "Overwrite Existing"
  18. Click [Begin Import Scan]
  19. Validate "There are no errors/warnings found within the import file.", is displayed
  20. Click [Begin Import]
  21. Validate "Import Complete" is displayed
  22. Click [Select Envelope Import File]
  23. Navigate to the location of [EnvelopeB]
  24. Select the file
  25. Click "Overwrite Existing"
  26. Click [Begin Import Scan]
  27. Validate "There are no errors/warnings found within the import file.", is displayed
  28. Click [Begin Import]
  29. Validate "Import Complete" is displayed
  30. Close the form
  31. Open form [FormA] for any test client
  32. Populate the "Signature" field with a desired signature [SigImage]
  33. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  34. Populated data in all other desired fields on the form [Note the values entered]
  35. Click to launch the "Pre-File" report [PreFileRpt]
  36. Validate on the document image is displayed as expected
  37. Validate the "Signature" field is populated with [SigImage], as expected
  38. Validate the "Picture" field is populated with [PicImage], as expected
  39. Validate all other fields populated in step 1c, are displayed as expected
  40. Close the report
  41. Submit the form as "Final"
  42. At the document routing "Confirm Document" screen
  43. Validate the 'Crystal Report' document image is displayed as expected based on [DocRoutReport]
  44. Validate the "Signature" field is populated with [SigImage], as expected
  45. Validate the "Picture" field is populated with [PicImage], as expected
  46. Validate all other fields populated in step 1c, are displayed as expected
  47. Submit and route the document
  48. Validate submission is successful
  49. Open form [FormB] for any test client
  50. Populate the "Signature" field with a desired signature [SigImage]
  51. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  52. Populated data in all other desired fields on the form [Note the values entered]
  53. Submit the form as "Final"
  54. At the document routing "Confirm Document" screen
  55. Validate the 'Tiff' document image is displayed as expected
  56. Validate the "Signature" field is populated with [SigImage], as expected
  57. Validate the "Picture" field is populated with [PicImage], as expected
  58. Validate all other fields populated in step 1c, are displayed as expected
  59. Submit and route the document
  60. Validate submission is successful
Document Routing and Pre-File Reports - Crystal Reports
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
Scenario 1: Modeled Forms ('Document Routing' Crystal Report) - Validate display picture and signature fields images
Specific Setup:
  • In form 'System Security Defaults', set field "Enable Signature Pad Support" to "Yes"
  • Have two users for testing [TestUserA] and [TestUserB]
  • [TestUserB] has the "My To Do's" widget on their home view
  • Have a Modeled form [TestForm], that contained in the envelope, set with prompt "Include Envelope within CDR" set up in form "Envelope Definition"
  • The modeled table [TestTable] used in [TestForm] are currently configured with:
  • Prompt "Does this table require an associated table for storage of binary data information" is set to "Yes" and field "Binary Storage Table Name" field populated with a desired binary storage table name [TestBinary]
  • Prompt "Create Pre-Filing Report Table" set to "Yes"
  • Field "Pre-Filing Report Schema/Tab" populated with "PRETEMP" and the modeled table name appended. For this example: "PRETEMP.TestTable"
  • Prompt "Pre-Filing Report Binary Storage Schema/Table" populated with "PRETEMP" and the binary storage table name. For this example, "PRETEMP.TestBinary"
  • A "Signature", "Picture" and "Draft/Final" field added in the table, along with any other desired field types
  • Open form "User Definition", select [TestUserA]
  • Navigate to the "Forms and SQL Tables" section and click "Select Tables for Product Access".
  • Expand the "PM" folder and navigate down to the "CWSPRETEMP" folder (This is the 'CDR' folder for the "PRETEMP" folder in CWS)
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Expand the "CWS" folder and navigate down to the "PRETEMP" folder
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Click [OK] and submit the form
  • Have two "Crystal Reports" setup based [TestForm]
  • [TestReportPM] to display the data submitted in 'CDR' tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "PM" main folder "CWSPRETEMP"
  • [TestReportCWS] to display the data submitted in tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "CWS" main folder "PRETEMP"
  • In form "Import Reports", [TestReportPM] and [TestReportCWS] have been imported with prompt "Import Report for Document Routing" selected in field "Select Import Type" field
  • In form "Document Routing Setup" [TestForm] has been enabled for document routing and currently [TestReportPM] has been selected in "Crystal Report" field
  • [TestUserA] has access to form "Document Routing Setup"
  • Log in as [TestUserA]
Steps
  1. Open form [TestForm] for any test client
  2. Populate the "Signature" field with a desired signature [SigImage]
  3. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  4. Populated data in all other desired fields on the form [Note the values entered]
  5. Set the "Draft/Final" field to "Final"
  6. Submit the form
  7. At the document routing "Confirm Document" screen
  8. Validate on the document image is displayed as expected based on [TestReporPM], 'Crystal Report'
  9. Validate the "Signature" field is populated with [SigImage], as expected
  10. Validate the "Picture" field is populated with [PicImage], as expected
  11. Validate all other fields populated in step 1c, are displayed as expected
  12. Submit and route the document to [TestUserB]
  13. Validate submission is successful
  14. Log out as [TestUserA]
  15. Log in as [TestUserB]
  16. Navigate to the "My To Do's" Widget
  17. Validate the To Do sent in step 1 is present in the list
  18. Click on [Approve Document]
  19. Validate on the document image is displayed as expected based on [TestReporPM], 'Crystal Report'
  20. Validate the "Signature" field is populated with [SigImage], as expected
  21. Validate the "Picture" field is populated with [PicImage], as expected
  22. Validate all other fields populated in step 1c, are displayed as expected
  23. Click [Accept]
  24. Validate submission is successful
  25. Log out as [TestUserB]
  26. Log in as [TestUserA]
  27. Open form "Document Routing Setup" and select [TestForm] for edit
  28. Click on the "Crystal Report" field
  29. Select [TestFormCWS]
  30. Submit the form
  31. Validate the form submits successfully
  32. Repeat steps 1 thru 3
  33. Validate on the document image is displayed as expected based on [TestReportCWS] 'Crystal Report'
  34. Validate the "Signature" field is populated with [SigImage], as expected
  35. Validate the "Picture" field is populated with [PicImage], as expected
  36. Validate all other fields populated in step 1c, are displayed as expected
Scenario 2: Modeled Forms ('Pre-File Report" Crystal Report) - Validate display picture and signature fields images
Specific Setup:
  • In form 'System Security Defaults', set field "Enable Signature Pad Support" to "Yes"
  • Have a Modeled form [TestForm], that contained in that envelope that is set with prompt "Include Envelope within CDR" set up in form "Envelope Definition"
  • The modeled table [TestTable] used in [TestForm] is currently configured with:
  • Prompt "Does this table require an associated table for storage of binary data information" is set to "Yes" and field "Binary Storage Table Name" field populated with a desired binary storage table name [TestBinary]
  • Prompt "Create Pre-Filing Report Table" is set to "Yes"
  • Field "Pre-Filing Report Schema/Tab" populated with "PRETEMP" and the modeled table name appended. For this example: "PRETEMP.TestTable"
  • Prompt "Pre-Filing Report Binary Storage Schema/Table" populated with "PRETEMP" and appended with the binary storage table name. For this example, "PRETEMP.TestBinary"
  • A "Signature" and "Picture" field along with anyother desired field types have been added to the table
  • Open form "User Definition", select [TestUserA]
  • Navigate to the "Forms and SQL Tables" section and click "Select Tables for Product Access".
  • Expand the "PM" folder and navigate down to the "CWSPRETEMP" folder (This is the 'CDR' folder for the "PRETEMP" folder in CWS)
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Expand the "CWS" folder and navigate down to the "PRETEMP" folder
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Click [OK] and submit the form
  • Have two "Crystal Reports" setup based [TestForm]
  • [TestReportPM] to display the data submitted in 'CDR' tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "PM" main folder "CWSPRETEMP"
  • [TestReportCWS] to display the data submitted in tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "CWS" main folder "PRETEMP"
  • In form "Import Reports", [TestReportPM] and [TestReportCWS] have been imported with prompt "Import Report for Document Routing" selected in field "Select Import Type" field
  • In "Form Definition", A "Pre-Fileing Report" command button objects have been added for both [TestReportPM] and [TestReportCWS], so that they can be launched prior to submitting the form, to display data currently populated in the form prior to submission
Steps
  1. Open form [TestForm] for any test client
  2. Populate the "Signature" field with a desired signature [SigImage]
  3. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  4. Populated data in all other desired fields on the form [Note the values entered]
  5. Navigate the command button for [TestReportPM]
  6. Double-click to launch the report
  7. Validate the report opens successfully
  8. Validate the "Signature" field is populated with [SigImage], 'Crystal Report'
  9. Validate the "Picture" field is populated with [PicImage], as expected
  10. Validate all other fields populated in step 1c, are displayed as expected
  11. Submit the form
  12. Validate the form submits successful
  13. Navigate the command button for [TestReportCWS]
  14. Double-click to launch the report
  15. Validate the report opens successfully
  16. Validate the "Signature" field is populated with [SigImage], 'Crystal Report'
  17. Validate the "Picture" field is populated with [PicImage], as expected
  18. Validate all other fields populated in step 1c, are displayed as expected
  19. Submit the form
  20. Validate the form submits successfully
  21. Return to [TestForm]
  22. Select the row just submitted for edit
  23. Validate the "Signature" field is populated with [SigImage], as expected
  24. Validate the "Picture" field is populated with [PicImage], as expected
  25. Validate all other fields populated in step 1c, are displayed as expected
Topics
• Envelope Import • Envelope Export • Document Routing
Update 52 Summary | Details
'All Documents' widget - Progress Notes (Group and Individual)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Financial Eligibility
  • All Documents Widget
  • Document Routing Setup (PM)
  • All Documents Widget Definition
  • View Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • "Client A" must have more than one hundred records on file for 'Progress Notes (Group and Individual)'.
  • "Client A" must have one or more 'Ambulatory Progress Notes' records on file.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Ambulatory Progress Notes' form assigned.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  3. Validate all 'Progress Notes (Group and Individual)' records are displayed for the client (more than one hundred).
  4. Validate the 'Workflow Status' column contains either "Draft" or "Final" for each row.
  5. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  6. Validate all 'Ambulatory Progress Notes' records are displayed for the client.
  7. Validate the 'Time' field contains the proper time the note(s) were filed.
'All Documents' widget - Ambulatory Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • All Documents Widget Definition
  • View Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
  • Treatment Plan
  • Financial Eligibility
  • All Documents Widget
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Access the 'Practitioner Enrollment' form.
  13. Select the practitioner linked to the logged in user for view/update.
  14. Validate that all the required/ desired fields are populated correctly.
  15. Click [Categories/Taxonomy] tab.
  16. Select any existing row in 'Category/Taxonomy' field.
  17. Validate all required fields are populated.
  18. Click "Practitioner Credentials" button.
  19. Select "Credential A" from the list.
  20. Click [OK]
  21. Click [Add Practitioner Categories].
  22. Validate the 'Confirm' dialog contains "Saved. Please note: The changes will take effect when you submit the form." message.
  23. Click [OK].
  24. Click [Submit].
  25. Select "Client A" and navigate to the 'All Documents' view.
  26. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  27. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  28. Select the progress note for viewing.
  29. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  30. Click [Print]
  31. Select "Print Current" dropdown value.
  32. Validate the practitioner's credential "Credential A" is displayed on the printable form.
  33. Validate an [Append] button is displayed and click it.
  34. Validate the 'Append Progress Notes' form is displayed.
  35. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  36. Click [Submit].
  37. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  38. Click [Accept].
  39. Enter the password associated with the logged in user and click [Verify].
  40. Click [Close All] in the 'Console Widget Viewer'.
  41. Refresh the 'All Documents' widget.
  42. Select the progress note appended in the previous steps for viewing.
  43. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  44. Click [Close All].
Scenario 2: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • "Client A" must have more than one hundred records on file for 'Progress Notes (Group and Individual)'.
  • "Client A" must have one or more 'Ambulatory Progress Notes' records on file.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Ambulatory Progress Notes' form assigned.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  3. Validate all 'Progress Notes (Group and Individual)' records are displayed for the client (more than one hundred).
  4. Validate the 'Workflow Status' column contains either "Draft" or "Final" for each row.
  5. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  6. Validate all 'Ambulatory Progress Notes' records are displayed for the client.
  7. Validate the 'Time' field contains the proper time the note(s) were filed.
'All Documents' widget - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Financial Eligibility
  • Admission (Outpatient)
  • Update Client Data
  • Pre Admit
Scenario 1: 'All Documents' widget - Validate 'Update Client Data' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Update Client Data' forms.
Steps
  1. Access the 'Admission' form.
  2. Admit a new client. This will be referred to as "Client A".
  3. Populate all required fields and some demographic data.
  4. Submit the form.
  5. Select "Client A" and access the 'Update Client Data' form.
  6. Validate the demographics fields display as filed.
  7. Update the desired demographics fields.
  8. Submit the form.
  9. Select "Client A" and access the 'Admission' form.
  10. Click [Edit] for the existing episode.
  11. Validate the updated demographics fields are displayed as filed.
  12. Update the desired demographics fields.
  13. Submit the form.
  14. Select "Client A" and access the 'Update Client Data' form.
  15. Validate the updated demographics fields are displayed as filed.
  16. Update the desired demographics fields.
  17. Submit the form.
  18. Navigate to the 'All Documents' view.
  19. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  20. Validate four 'Update Client Data' records are displayed for each update done to the client's demographics.
  21. Click to view each record and validate the documents display as expected in the 'Console Widget Viewer'.
  22. Click [Close All].
Topics
• Progress Notes • All Documents Widget • Admission
Update 61 Summary | Details
Append Documents - Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Append Progress Notes
Scenario 1: Append Documents - validate appending to progress notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" must have a progress note on file that has been approved via document routing (Progress Note A).
  • The 'Progress Notes' widget must be accessible on the HomeView.
Steps
  1. Access the 'Append Documents' form.
  2. Select the form type for "Progress Note A" in the 'Form Type' field.
  3. Select "Client A" in the 'Entity' field.
  4. Enter the current date in the 'From Date' and 'End Date' fields.
  5. Select "Progress Note A" in the 'List of Documents' field.
  6. Click [Display Document].
  7. Validate the details for "Progress Note A" are displayed as expected.
  8. Click [Close All Documents and Exit].
  9. Enter the desired value in the 'New Comments to Be Appended in the Original Document' field.
  10. Click [Submit].
  11. Validate the 'Confirm Document' dialog is displayed and the document is displayed with the appended notes.
  12. Click [Accept].
  13. Enter the user's password and click [Verify].
  14. Validate the form files successfully.
  15. Select "Client A" and access the 'Progress Notes' widget.
  16. Validate "Progress Note A" is displayed with the appended comments with a proper date format.
Topics
• Progress Notes (Group And Individual) • Document Routing • Widgets
Update 71 Summary | Details
Assigning or changing an MR#
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Last Movement
  • Dynamic Form - Delete Last Movement
  • Call Intake
  • Change MR#
  • Client Ledger
Scenario 1: Admission - Validate 'Assign Permanent MR #' functionality
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
Steps
  1. Access the 'Call Intake' form.
  2. Enter the desired last name in the 'Last Name' field.
  3. Enter the desired first name in the 'First Name' field.
  4. Select "Male" in the 'Sex' field.
  5. Click [Search].
  6. Validate the 'Search' field states: "No matches found".
  7. Click [New Client].
  8. Select the desired value in the 'Call Or Walk-In' field.
  9. Select the desired value in the 'Caller Type' field.
  10. Enter the desired date in the 'Call Date' field.
  11. Enter the desired time in the 'Call Time' field.
  12. Select the desired program in the 'Program' field.
  13. Select desired value in the 'Disposition' field.
  14. Click [Submit].
  15. Select the new client in the 'Recent Clients' field.
  16. Validate the client ID contains "P" and the client name is the name entered in step 1
  17. Open the "Admission" form
  18. Validate the "Assign MR#?" dialog is displayed
  19. Click [Yes] to assign a permanent MR#
  20. At the next dialog, click [Yes] to assign the next available ID number
  21. At the "Admission" screen
  22. Validate the "Client Name" field is populated with name entered in step 1
  23. Populate the required fields and any other desired fields on the form
  24. Click to submit the form
  25. Validate the form submits successfully
  26. At the home screen, in the "Recent Clients" list
  27. Validate the client has now been assigned a permanent MR#
  28. Click to open their "Chart" or "Client Dashboard"
  29. Validate the header section displays the clients name and their new permanent MR# in parentheses
  30. For example: TEST CLIENT (25)
Scenario 2: Change MR# - Form Validations
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
  • Have two active clients with permanent MR#'s assigned in the system for testing:
  • [ClientA]
  • The client currently has no documents that are pending approval
  • [ClientB]
  • The client currently has two pending documents approval [Doc1] and [Doc2], routed to user [TestUser]
  • [TestUser] has the "My To Do's" widget on their homeview
  • Log in a [TestUser]
Steps
  1. Access the 'Change MR#' form
  2. Select [ClientA] in the 'Client ID' field.
  3. Click [Assign MR#].
  4. Validate a message is displayed stating: Auto Assign Next ID Number?
  5. Click [Yes].
  6. Validate the 'New Client ID#' field contains the new ID for [ClientA]. Make a note of the new ID number
  7. Click [Submit].
  8. Validate the form submits successfully
  9. At the Home screen, search for [ClientA]
  10. Validate [ClientA] is found and their new client ID noted in step 1 is displayed
  11. Click to open "Chart" or "Client Dashboard"
  12. Validate the header section displays the clients name and their new client ID# in parentheses
  13. For example: Test ClientA (28)
  14. Access the 'Change MR#' form
  15. Select [ClientB] in the 'Client ID' field.
  16. Click [Assign MR#].
  17. Validate a message is displayed stating: Auto Assign Next ID Number?
  18. Click [Yes].
  19. Validate the 'New Client ID#' field contains the new ID for [ClientA]. Make a note of the new ID number
  20. Click [Submit].
  21. Validate an error message stating "This client has documents which are currently pending approval. The MR number cannot be changed until these documents are finalized or rejected."
  22. Click [OK]
  23. Close the form
  24. Navigate to the "My To Do's" widget on the home view
  25. Locate the 'To Do's' for [Doc1] and [Doc2] waiting for review
  26. Click each 'To Do', review and either accept or reject the documents
  27. Validate the 'To Do's' are removed from the 'To Do' list
  28. Access the 'Change MR#' form
  29. Select [ClientB] in the 'Client ID' field.
  30. Click [Assign MR#].
  31. Validate a message is displayed stating: Auto Assign Next ID Number?
  32. Click [Yes].
  33. Validate the 'New Client ID#' field contains the new ID for [ClientB]. Make a note of the new ID number
  34. Click [Submit].
  35. At the Home screen, search for [ClientB]
  36. Validate [ClientB] is found and their new client ID noted in step 5 is displayed
  37. Click to open "Chart" or "Client Dashboard"
  38. Validate the header section displays the client's name and their new client ID# in parentheses. For example: Test ClientB (30)


Scenario 3: Assign Permanent MR# - form validations
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
Steps
  1. Access the 'Call Intake' form.
  2. Enter the desired last name in the 'Last Name' field.
  3. Enter the desired first name in the 'First Name' field.
  4. Select "Male" in the 'Sex' field.
  5. Click [Search].
  6. Validate the 'Search' field states: "No matches found".
  7. Click [New Client].
  8. Select the desired value in the 'Call Or Walk-In' field.
  9. Select the desired value in the 'Caller Type' field.
  10. Enter the desired date in the 'Call Date' field.
  11. Enter the desired time in the 'Call Time' field.
  12. Select the desired program in the 'Program' field.
  13. Select desired value in the 'Disposition' field.
  14. Click [Submit].
  15. Select the new client in the 'Recent Clients' field.
  16. Validate the client ID contains "P".
  17. Access the 'Assign Permanent MR' form.
  18. Validate the 'Name' field contains the name entered in the previous steps.
  19. Validate the 'Temporary ID' field contains "P".
  20. Click [Assign Permanent MR #].
  21. Click [Yes].
  22. Validate the 'Assigned ID' field does not contain "P". Make a note of the ID number
  23. Click [Submit].
  24. Select the new client in the 'Recent Clients' field.
  25. Validate the client ID does not contain "P" and the new number noted in step 3 is assigned, as expected
Table Definition - new table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
  • Envelope Definition (CWS)
  • Document Routing Setup (PM)
  • Form Definition (CWS)
Scenario 1: "Table Definition" Form - New table addition validations
Specific Setup:
  1. Have a system with modeled tables existing in both "PM" and "CWS" applications
  2. Using a database query program, connect to the "CWS" namespace and run the following query:
  3. 'Select tablecsmid from SQLUser.RadPlusCSMTable ORDER BY tablecsmid ASC'
  4. This will output all the table ID numbers (tablecsmid) for the tables existing in that namespace in numerical order. Make a note of the output. (Note: "SQL Query" in the cache "System Management Portal" can be used to execute the query, if access is accessible)
  5. Repeat the last step connected to the "PM" namespace. Make a note of the output
  6. Compare the output from the two namespaces in step 1 and 2
  7. Locate table with an ID# that exists in CWS that does not exist in PM
  8. Note the name and number of the table: For example: [CWSTestTableA (19)]
Steps
  1. In "Avatar CWS" open form "Table Definition"
  2. Select the table noted in the setup [CWSTestTableA]
  3. Navigate to the prompt 'Does this table require an associated table for the storage of binary information' field and set it to "Y", if it's not already
  4. In the 'Binary Storage Table Name' field enter a value (i.e. "Cwsbinary_Test"), if there's not a value already.
  5. Make note of the 'Binary Storage Table Name' field value [Cwsbinary_Test]
  6. Make a note of the envelope name in the "Envelope" field [CWSenvelopeA]
  7. Submit the form and exit
  8. In "Avatar CWS" open form "Envelope Definition" and select [CWSenvelopeA]
  9. Make a note of the value in the "SQL Schema" field [SYSTEMA]
  10. Exit the form
  11. Re-open form "Envelope Definition"
  12. Enter a new envelope name [CWSenvelopeB] and click to create the new envelope
  13. Select a value in the "Entity Database" field
  14. In the "SQL Schema" field, enter a different value than the one noted in n step 2a. [SYSTEMB]
  15. Set the 'Include Envelope within CDR' field to "Yes"
  16. Submit the form
  17. In "Avatar CWS" open form "Table Definition"
  18. In the search field, enter the name of the 'Binary Storage Table Name' field name noted in step 1c. For this test [Cwsbinary_Test]
  19. Click [New Avatar CWS Table]
  20. When prompted to select an "Envelope", select the envelope noted in step 2, [CWSenvelopeA]
  21. Click [OK]
  22. Validate the entry is accepted and the user is navigated to the table definition screen to create the new table
  23. Validate the "Table Name" field is populated with [Cwsbinary_Test]
  24. Populate all the required fields and any other desired fields
  25. Submit the form
  26. Validate the table submits successfully
Topics
• Client Management • Admission • Assign MR# • Change MR# • Modeling
2023 Update 110 Summary | Details
Document Management Defaults - Path name for documents
Scenario 1: Document Management Defaults - form validation
Specific Setup:

Internal Testing Only

Steps

Internal Testing Only

Scenario 2: Document Management Defaults - Perceptive enabled
Specific Setup:

Internal Testing Only

Steps

Internal Testing Only
Topics
• Document Management
2023 Update 133 Summary | Details
State Form Definition - file import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
Scenario 1: "State Form Definition" - Export/Import validations
Specific Setup:
  • Have a "State Form Definition" definition created [SFDef] that is an "XML" type definition and contains a sub record
  • In form "State Form Definition" select [SFDef] and note the ID number assigned to it in parens. For example: "SFDef (1)"
  • Navigate to the "Record Definition" section and note the numerical value assigned in the "Record ID" field. For example: "16"
  • Open the "Define Records Data Element" grid and navigate to the "Subrecord" column of the sub record row.
  • Note the value populated in the field, which is the sub records "name" and "code" number references. For example: "Sub1 (16!!17)"
  • Navigate to the "Import/Export" section of the form and export the state form definition for [SFDefExport]
  • Save the file [SFDefExport] in a desired folder location
Steps
  1. Open form "State Form Definition"
  2. Go to the "Import" section
  3. Select "New" in the "Import Type" field
  4. Click [Select File for Import]
  5. Navigate to the location of the [SFDefExport] export file, saved in the setup
  6. Select the file
  7. In the "Import File Scan Results"
  8. Validate the results indicate there are no issues with the import file
  9. Click [Process Import]
  10. Validate message displayed "Import Complete"
  11. Click [OK]
  12. Close the form
  13. Re-Open form "State Form Definition"
  14. Select "Existing" in the "New or Existing" field
  15. Click the "Select State Form" field, to display the definitions for selection in the drop down list
  16. Validate "SFDef (1)" is present in the list
  17. Validate "SFDef (2)" the imported state form file is also present in the list. It will contain the same name as the original file exported, but with a new ID number assigned.
  18. Select "SFDef (2)" for edit
  19. Navigate to the "Record Definition" section and select the "Main" record
  20. Validate the value in the "Record ID" field has been assigned a different value than the one noted for "SFDef (1)", in the set up, as expected
  21. Click the [Define Records Data Element] to enter the data elements grid
  22. Navigate to the "Subrecord" column of the sub record row
  23. Validate the sub records "name" and internal "code" number references are populated in the field with:
  24. The sub record 'name', still the same as original file exported, "Sub1"
  25. The internal "code" number in parens, but assigned a new number as expected. For example, "(2!!5)"
  26. Exit the grid and close the form
Topics
• State Form Tools
 

RADplus_2024_Monthly_Release_2024.01.01_Details.csv