Skip to main content

RADplus 2022 Quarterly Release 2022.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 4 Summary | Details
Team Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team Definition
Scenario 1: Team Definition - field and data validations
Specific Setup:
  • Have an existing team created in form "Team Definition" or create a new one [TeamA]
  • In form "User Definition", have existing users on the system and users with user IDs defined as follows:
  • a user defined with a user ID that is in all lowercase characters
  • a user defined with a user ID that begins with a lowercase character and the rest being in mixed case
  • a user defined with a user ID that is in all uppercase characters
  • a user defined with a user ID that begins with an uppercase character and rest being in mixed case
Steps
  1. Open the "Team Definition" form.
  2. Click [Select Team] and select [TeamA]
  3. Click [Select Users]
  4. Click the "A-J" checkbox, to expand the user list
  5. Validate the entire list of names is displayed in the correct alphabetical order, including any of the users defined in the setup
  6. Select any desired users
  7. Click the "K-Q" checkbox, to expand the user list
  8. Validate the entire list of users are displayed in the correct alphabetical order, including any of the users defined in the setup
  9. Select the desired users
  10. Click the "R-Z" section checkbox, to expand the user list
  11. Validate the entire list of users are displayed in the correct alphabetical order, including any of the users defined in the setup
  12. Select any desired users
  13. Click [OK]
  14. Click [File].
  15. Close the form
  16. Open the "Team Definition" form.
  17. Click [Select Team] and select [TeamA]
  18. Click [Select Users]
  19. Validate users selected in step 3 are selected
  20. Click [Cancel]
  21. Validate that the 'Team Information' text field contains the users selected in step 3 along with their user descriptions
Topics
• Forms • NX
Update 11 Summary | Details
Product Updates - Version upgrades
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Current Server Information (PM)
  • Product Updates (PM)
  • Globals
  • View Global Data
Scenario 1: "Product Updates" form - Post installation validations
Specific Setup:
  • Have a system with one or more child namespace. For example "CWS", "MSO" and "CFMS"
  • The system is ready to upgrade to following years module update for "RADPlus". For this test, RADplus "2021" will be upgraded to "2022"
Steps
  1. Open the "Product Updates" form.
  2. Select the "PM" namespace from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location of the "RADplus" update file and select the file
  5. Click [Install Update/Customization Pack].
  6. Click [OK] when the install has completed
  7. Click [Close Form]
  8. Open the "Current Server Information" form in the "PM" namespace
  9. Validate the "RADplus Updates" results text box includes two entries
  10. Update #001 - RADplus 2022 Loaded ...
  11. Update #Pre_installation - RADplus 2022 Loaded ....
  12. Close the form
  13. Open the "Current Server Information" form for a child namespace, for example "CWS"
  14. Validate the "RADplus Updates" results text box includes the entry
  15. Update #001 - RADplus 2022 Loaded ...
  16. Close the form
  17. Open the "Current Server Information" form for any other child namespaces
  18. Validate the "RADplus Updates" results text box includes the entry
  19. Update #001 - RADplus 2022 Loaded...
  20. Close the form
Topics
• Cache • Update Install • NX
Update 14 Summary | Details
Change MR#
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
Scenario 1: "Change MR#" process - validate client and updated document data (appended and not appended)
Specific Setup:
  • Have a client [ClientA] whose client ID # will need to be changed via the form "Change MR#" or the "Change MPI MR#" form [FormA]
  • For [ClientA] have:
  • A document created [Doc1], for example "Document Routing" document
  • A "Treatment Plan" record on file [TPrec1] filed via the "Treatment Plan" form
  • A "Progress Note" record on file [PMrec1] filed with a progress note form. For example, form "Ambulatory Progress Notes"
  • A "Modeled Form" record [MFrec1] filed with any user modeled form
Steps
  1. Open [FormA]
  2. Enter the current ID of [ClientA] in the "Client ID" field
  3. Click [Assign MR#]
  4. Validate the "New Client ID#" field is populated with a new client ID#
  5. Click [Submit]
  6. Validate the form submits successfully and in a timely manner
  7. In the "My Clients" widget, enter the old client ID# for [ClientA] in the "Search Clients" field
  8. Validate "No matches found" is displayed
  9. In the "My Clients" widget, enter the new client ID# for [ClientA] in the "Search Clients" field
  10. Validate the client is found
  11. Validate the name of the client is as expected
  12. Open form "Clinical Document Viewer"
  13. In the "Select Client" field, enter the old client ID# for [ClientA]
  14. Validate "No matches found" is displayed
  15. In the "Select Client" field, enter the new client ID# assigned to [ClientA]
  16. Validate [ClientA] is found, select the client
  17. Click [Process]
  18. Validate the document [Doc1], is present in the list of documents
  19. Click [View]
  20. Validate data is displayed as expected in the document
  21. Open the "Treatment Plan" form
  22. In the "Select Client" field, enter the old client ID# for [ClientA]
  23. Validate "No matches found" is displayed
  24. In the "Select Client" field, enter the new client ID# assigned to [ClientA]
  25. Validate [ClientA] is found, select the client to open the form
  26. Validate the treatment plan row filed in the set up [TPrec1] for [ClientA], is present for selection in the pre-display
  27. Select the row
  28. Validate the data displayed in the treatment plan, is as expected
  29. Open the "Progress Note" form
  30. In the "Select Client" field, enter the old client ID# for [ClientA]
  31. Validate "No matches found" is displayed
  32. In the "Select Client" field, enter the new client ID# assigned to [ClientA]
  33. Validate [ClientA] is found, select the client
  34. Validate the progress note row filed in the set up [PNrec1] for [ClientA], is present for selection in the pre-display
  35. Select the row
  36. Validate the data displayed in the progress note, is as expected
  37. Open the "Modeled" form
  38. In the "Select Client" field, enter the old client ID# for [ClientA]
  39. Validate "No matches found" is displayed
  40. In the "Select Client" field, enter the new client ID# assigned to [ClientA]
  41. Validate [ClientA] is found, select the client to open the form
  42. Validate the modeled form row filed in the set up [MFrec1] for [ClientA], is present for selection in the pre-display
  43. Select the row
  44. Validate the data displayed in the modeled form, is as expected
Topics
• Change MR# • NX
Update 15 Summary | Details
State Form File - Output
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Task Scheduler
  • System Task Scheduler
  • State Form File Generation
Scenario 1: Validate a state form file generated via the "State Form Task Scheduler" "
Specific Setup:
  • Have a state form definition file created in form "State Form Definition" that with the "Record Delimiter" field set to "Carriage Return + Line Feed" [DefinitionA]
Steps
  1. Open form "State Form Task Scheduler"
  2. Select "Single Definition" in the "Type" field
  3. Select the [DefinitionA] from the "Select Batch or Definition" drop down list
  4. Set the "File Description" field to a desired file name
  5. Select "Static" in the "Change From Date"
  6. Set the "Static Date" field to today's date
  7. Select "Static" in the "Change Through Date"
  8. Set the "Static Date" field to today's date
  9. Select "Yes" in the "Create File" field
  10. Click [Submit]
  11. At the dialog, "Filed. In order for compiles to be run, the new task must be scheduled using the 'System Task Scheduler' form", click [OK]
  12. Open the "System Task Scheduler" form
  13. In the "Schedule(s)" field, select the task created in step for [DefinitionA] in step 1
  14. Select a desired recurrence type pattern from the "Recurrence Pattern" field. For example "Daily"
  15. Populate a desired value in the "Task Occurrence Sequence".
  16. Populate the "Start By" field with today's date
  17. Populate the "Start Time" field with a time later than the current time
  18. Click [Schedule Task]
  19. Close the form
  20. Wait till the "Start Time" set in step 2 has passed
  21. Open the "State Form File Generation" form.
  22. Select [DefinitionA] in the "State Form" field
  23. Select "Dump File" in the "File Generation Options" field
  24. In the "Select File" field, select the compiled file for [DefinitionA], generated by the automated task set up in step 2
  25. Click [Process]
  26. Validate there is a carriage return and a line feed after each record displayed in the output, as expected displayed, has a carriage return and a line feed after it on the report
State Form Definition - XML Header Tags
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: 'XML type "State Form Definition" file validations
Specific Setup:
  • Have a definition created [DefintionA] in form "State Forms Definition" with a "File Type" set to "XML".
Steps
  1. Open form "State Form Definition"
  2. Set field "New or Existing" to "Existing"
  3. Select [DefinitionA] in the "Select State Form" field
  4. Navigate to the "Definitions" Options" field at the bottom of the section
  5. Deselect "Remove XML Declaration", if it is currently selected
  6. Click [File Form]
  7. Validate filing completes successfully
  8. Close the form
  9. Open form "State Form File Generation"
  10. Select the [DefinitionA] in field "State Form"
  11. In the "File Generation Options" field, select "Compile"
  12. Click [Process]
  13. Validate the process completes successfully
  14. In the "File Generation Options" field, select "Dump File"
  15. Click [Process]
  16. Validate the output of the state form report includes the "XML declaration" header tag in the first line of the output. For example: "<?XML version="1.0" encoding="UTF-8"?>"
  17. Close the report and close the form
  18. Open form "State Form Definition"
  19. Set field "New or Existing" to "Existing"
  20. Select [DefinitionA] in the "Select State Form" field
  21. Navigate to the "Definitions" Options" field at the bottom of the section
  22. Select the "Remove XML Declaration" check box
  23. Click [File Form]
  24. Validate filing completes successfully
  25. Close the form
  26. Open form "State Form File Generation"
  27. Select the [DefinitionA] in field "State Form"
  28. In the "File Generation Options" field, select "Compile"
  29. Click [Process]
  30. Validate the process completes successfully
  31. In the "File Generation Options" field, select "Dump File"
  32. Click [Process]
  33. Validate the output of the state form report no longer includes the "XML declaration" header tag in the output of the report.
  34. Close the report and close the form
Topics
• State Form Task Scheduler • NX • State Form Tools
Update 20 Summary | Details
RADplus modeling - Future Dates
Scenario 1: Future Dates - Table Definition
Specific Setup:
  • An envelope must be created or imported with the 3 fields:
  1. A date field "TestingTheAllow" set to allow future dates ("No").
  2. A date field "TestingTheError" set to an error dialog when future dates are selected ("Error").
  3. A date field "TestingTheWarning" set to a warning("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the newly created form.
  2. Set the 'TestingTheAllow' field to a future date.
  3. Validate the 'TestingTheAllow' field is set to a future date.
  4. Set the 'TestingTheWarning' field to a future date.
  5. Validate the 'Warning' Dialog is displayed and click [Cancel].
  6. Set the 'TestingTheWarning' field to the current date.
  7. Validate the 'TestingTheWarning' field is set to the current date.
  8. Set the 'TestingTheError' field to a future date.
  9. Validate the 'Error' Dialog is displayed and click [OK].
  10. Set the 'TestingTheError' field to the current date.
  11. Validate the 'TestingTheError' field is set to the current date.
Site Specific Section Modeling - Future Dates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Disclosure Management
Scenario 1: New Service note in 'Progress Notes (Group and Individual)'
Specific Setup:
  • Using 'Site Specific Section Modeling', 3 fields must be created:
  1. A date field "TestingTheAllow" set to allow future dates ("No").
  2. A date field "TestingTheError" set to an error dialog when future dates are selected ("Error").
  3. A date field "TestingTheWarning" set to a warning ("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select desired episodes from the 'Request Episode(s)' field.
  3. Select 'New Service'.
  4. Select "Psychologist" from the 'Note Type' field.
  5. Set 'Notes Field' field to "test".
  6. Search for and select a valid practitioner in the 'Practitioner' field.
  7. Set the 'Date Of Service' field to a future date.
  8. Validate the 'Warning' Dialog is displayed and click [Cancel].
  9. Set the 'Date Of Service' field to a date in the past.
  10. Validate the 'Date Of Service' field is set to a date in the past.
  11. Search for and select any desired code in the 'Service Charge Code'.
  12. Select "Draft" from the 'Draft/Final' field.
  13. Set the 'Date' field to the current date.
  14. Set the 'TestingTheWarning' field to a future date.
  15. Validate the 'Warning' Dialog is displayed and click [Cancel].
  16. Set the 'TestingTheWarning' field to a future date.
  17. Validate the 'Warning' Dialog is displayed and click [OK].
  18. Validate the 'TestingTheWarning' field contains a future date.
  19. Set the 'TestingTheWarning' field to the current date.
  20. Validate the 'TestingTheWarning' field is set to the current date.
  21. Set the 'TestingTheError' field to a date future date.
  22. Validate the 'Error' Dialog is displayed and click [OK].
  23. Set the 'TestingTheError' field to the current date.
  24. Validate the 'TestingTheError' field is set to the current date.
  25. Set the 'TestingTheAllow' field to a future date.
  26. Validate the 'TestingTheAllow' field is set to a future date.
  27. Click [File Note].
  28. Access the clients chart and confirm a new progress form was filed.
Scenario 2: Disclosure Management - Future Dates
Specific Setup:
  • Using 'Site Specific Section Modeling' the following fields must be set accordingly:
  1. "Request Date" set to a 'warning' ("Warning").
  2. "'Request For Information Start Date" set to an error dialog when future dates are selected ("Error").
  3. "'Request For Information End Date" set to an error dialog when future dates are selected ("Error").
  4. "Authorization Start Date" set to a warning ("Warning").
  5. "Authorization End Date" set to a warning ("Warning").
  6. "Disclosure Date" set to a warning ("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Disclosure Management' form.
  2. Set the 'Request Date' field to a future date.
  3. Validate the 'Warning' Dialog is displayed and click [Cancel].
  4. Set the 'Request Date' field to the current date.
  5. Validate the 'Request Date' field is set to the current date.
  6. Set the 'Request For Information Start Date' field to a future date.
  7. Validate the 'Error' Dialog is displayed and click [OK].
  8. Set the 'Request For Information Start Date' field to a date in the past.
  9. Validate the 'Request For Information Start Date' field is set a date in the past.
  10. Set the 'Request For Information End Date' field to a future date.
  11. Validate the 'Error' Dialog is displayed and click [OK].
  12. Set the 'Request For Information End Date' field to the current date.
  13. Validate the 'Request For Information End Date' field is set to the current date.
  14. Select desired episodes from the 'Request Episode(s)' field.
  15. Select desired items from the 'Requested Chart Items' field.
  16. File and save an Organization.
  17. Select 'Authorization'.
  18. Set the 'Authorization Start Date' field to a future date.
  19. Validate the 'Warning' Dialog is displayed and click [Cancel].
  20. Set the 'Authorization Start Date' field to a date in the past.
  21. Validate the 'Authorization Start Date' field is set a date in the past.
  22. Set the 'Authorization End Date' field to a future date.
  23. Validate the 'Warning' Dialog is displayed and click [Cancel].
  24. Set the 'Authorization End Date' field to the current date.
  25. Validate the 'Authorization End Date' field is set to the current date.
  26. Select desired episodes from the 'Authorization Episode(s)' field.
  27. Select "Yes" and click [Update Chart Items Authorized for Disclosure].
  28. Click [Save].
  29. Select 'Disclosure'.
  30. Set the 'Disclosure Date' field to a future date.
  31. Validate the 'Warning' Dialog is displayed and click [Cancel].
  32. Set the 'Disclosure Date' field to the current date.
  33. Set the 'Disclosure Time' to the current time.
  34. Select desired charts from the 'Chart Disclosure Information'.
  35. Select 'Electronic' and click [Process].
  36. Select "Client A" and access the 'Disclosure Management' form.
  37. Validate a new disclosure was filed.
Topics
• Envelope Definition • Progress Notes • Disclosure
Update 22 Summary | Details
ERS Program Statistics Discharges Report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ERS Program Statistics
  • ERS Program Statistics Discharges Report
Scenario 1: ERS Program Statistics Discharges Report - Data validations
Specific Setup:
  • Have a system that includes a client [ClientA], admitted to an "Inpatient" program and the client has now been discharged from the program
  • Have a system that includes a client [ClientB], admitted to an "Outpatient" program and the client has now been discharged from the program
Steps
  1. Open form "ERS Program Statistics"
  2. Set the "Compile Description" field to a desired value [CompileA]
  3. In the "Compile Programs" field, select the desired "Inpatient" programs
  4. Populate the "Period Start Date"
  5. Populate the "Period End Date"
  6. Click [Compile]
  7. Validate the compile completes successfully
  8. Close the form
  9. Open the "ERS Program Statistics Discharge" report
  10. Select [CompileA] from the "Select Program Statistics Compile" field
  11. Click [Process]
  12. Validate the "Program Statistics - Discharge" report is displayed
  13. From the program listing on the left side panel, select the desired inpatient program
  14. On the next page, click a selected inpatient program link on the report
  15. Validate the "Program Statistics - Discharge" sub report is displayed
  16. Validate the "Length" of Stay" (days) value for [ClientA] is equal to the difference in days, between the "Admit Date" and "Discharge Date", as expected
  17. Close the report
  18. Close the "ERS Program Statistics Discharge" report
  19. Open form "ERS Program Statistics"
  20. Set the "Compile Description" field to a desired value [CompileB]
  21. In the "Compile Programs" field, select the desired "Outpatient" programs
  22. Populate the "Period Start Date"
  23. Populate the "Period End Date"
  24. Click [Compile]
  25. Validate the compile completes successfully
  26. Close the form
  27. Open the "ERS Program Statistics Discharge" report
  28. Select [CompileB] from the "Select Program Statistics Compile" field
  29. Click [Process]
  30. Validate the "Program Statistics - Discharge" report is displayed
  31. From the program listing on the left side panel, select the desired "Outpatient" program
  32. On the next page, click the selected outpatient program link on the report
  33. Validate the "Program Statistics - Discharge" sub report is displayed
  34. Validate the "Length" of Stay" (days) value for [ClientB] is equal to the difference in days, between the "Admit Date" and "Discharge Date", as expected
  35. Close the report
  36. Close the "ERS Program Statistics Discharge" report
Topics
• Forms • NX
Update 25 Summary | Details
Support is added for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CarePOV Management
  • CareFabric Monitor
  • Diagnosis
  • Staff Members Hours And Exceptions
  • Problem List
Scenario 1: CarePOV Management - 'Electronic Visit Verification' - 'Celltrak' integration
Specific Setup:
  • myAvatar must be configured for Electronic Visit Verification.
  • myAvatar must be configured to integrate with Celltrak and vice versa.
  • A New Product using EVV must be created in the 'CareFabric Integration Management' form and a 'User to send To-Dos' must be filed. In the 'Code Mappings' section of this form a "Note Type" mapping type must be created for EVV.
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the 'Electronic Visit Verification' section.
  3. Select "Celltrak" in the 'EVV Vendor' field.
  4. Select the desired user in the 'EVV Admin User ID' field. Please note: this will determine the user that will be notified if EVV communication is lost due to technical issues. The user will be notified via To-Do in the 'My To Do's' widget.
  5. Enter the desired value in the 'Vendor Account Number' field.
  6. Select the desired progress note form in the 'Progress Note Form' field.
  7. Select "Yes" in the 'Save Progress Notes' field.
  8. Select the desired site in the 'Site' field.
  9. Enter the desired value in the 'Medicaid Provider ID' field.
  10. Validate the 'Required Sections' field is displayed and contains: "SendTelephonyPatient - PrimaryDiagnosis", "SendTelephonyPatient - PayerProgram", and "SendTelephonyPatient - PayerID". Please note: when selected, these sections will be required in order to trigger the 'SendTelephonyPatient' EVV action.
  11. Select the desired value(s) in the 'Required Sections' field.
  12. Validate the 'Provider Address To Be Sent' field is displayed and contains: "Home" and "Office". Validate "Office" is the default value. Please note: the 'Addresses' section of the 'SendTelephonyResource' EVV action payload will be determined based on this selection.
  13. Select the desired value in the 'Provider Address To Be Sent' field.
  14. Validate the 'Payor Program ID' grid contains three columns: "Guarantor", "Payer ID", and "Payer Program".
  15. Click [New Row].
  16. Validate the 'Guarantor' field of the 'Payor Program ID' grid contains all guarantors regardless of financial class.
  17. Select the desired value in the 'Guarantor' field of the 'Payor Program ID' table.
  18. Enter the desired value in the 'Payer ID' field of the 'Payor Program ID' table.
  19. Enter the desired value in the 'Payer Program' field of the 'Payor Program ID' table.
  20. Validate the 'Progress Notes Form Mapping' grid is displayed and contains three columns: "Service Code", "Program", and "Progress Notes Form". Please note: This grid allows the ability to determine the progress note forms that will be used when saving notes.
  21. Click [New Row].
  22. Select the desired value in the 'Service Code' field.
  23. Select the desired value in the 'Program' field.
  24. Select the desired value in the 'Progress Notes Form' field.
  25. [Submit].
Scenario 2: Progress Notes (Group and Individual) - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • The 'Progress Notes' widget is on the HomeView for the logged in user.
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings]
  4. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  5. Click [OK].
  6. Validate the 'Registry Setting Details' field contains "Enter "Y" to add 'Treatment Plan' grid field to the form. Enter "YD" to add the grid field and enable the functionality to default the previously selected treatment plan to the new row. Enter "N" to remove the field from the form."
  7. Enter "Y" in the 'Registry Setting Value' field.
  8. Click [Submit].
  9. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  10. Click [OK].
  11. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  12. Click [No].
  13. Access the 'Progress Notes (Group and Individual)' form.
  14. Verify the 'Treatment Plan' grid is displayed.
  15. Enter "Client A" in the 'Select Client' field.
  16. Select the desired episode in the 'Select Episode' field.
  17. Select "Independent Note" in the 'Progress Note For' field.
  18. Select any value in the 'Note Type' field.
  19. Click [New Row] in the 'Treatment Plan' grid.
  20. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  21. Click [View] in the 'Select T.P. Item Note Addresses' field.
  22. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  23. Select the desired treatment plan item in the 'Treatment Plan' window.
  24. Click [Return].
  25. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  26. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  27. Enter the desired value in the 'Notes Field' field.
  28. Select "Draft" in the 'Draft/Final' field.
  29. Click [File Note].
  30. Validate a "Progress Notes" message is displayed stating: Note Filed.
  31. Click [OK].
  32. Validate the 'Treatment Plan' grid no longer contains the previously filed row.
  33. Select the note filed in the previous steps in the 'Select Draft Note To Edit' field.
  34. Validate the 'Treatment Plan' grid contains the row filed in the previous steps.
  35. Click [New Row] in the 'Treatment Plan' grid.
  36. Validate the 'Select T.P. Version' field does not contain a value.
  37. Select the second row in the 'Treatment Plan' grid.
  38. Click [Delete Row].
  39. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows?
  40. Click [Yes].
  41. Select "Final" in the 'Draft/Final' field.
  42. Click [File Note].
  43. Validate a "Progress Notes" message is displayed stating: Note Filed.
  44. Click [OK] and close the form.
  45. Access the 'Registry Settings' form.
  46. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  47. Click [View Registry Settings]
  48. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  49. Click [OK].
  50. Enter "YD" in the 'Registry Setting Value' field.
  51. Click [Submit].
  52. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  53. Click [OK].
  54. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  55. Click [No].
  56. Access the 'Progress Notes (Group and Individual)' form.
  57. Verify the 'Treatment Plan' grid is displayed.
  58. Enter "Client A" in the 'Select Client' field.
  59. Select the desired episode in the 'Select Episode' field.
  60. Select "Independent Note" in the 'Progress Note For' field.
  61. Select any value in the 'Note Type' field.
  62. Click [New Row] in the 'Treatment Plan' grid.
  63. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  64. Click [View] in the 'Select T.P. Item Note Addresses' field.
  65. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  66. Select the desired treatment plan item in the 'Treatment Plan' window.
  67. Click [Return].
  68. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  69. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  70. Click [New Row] in the 'Treatment Plan' grid.
  71. Validate the 'Select T.P. Version' field defaults in with the value selected in the first row.
  72. Click [View] in the 'Select T.P. Item Note Addresses' field.
  73. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  74. Select the desired treatment plan item in the 'Treatment Plan' window.
  75. Click [Return].
  76. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  77. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  78. Enter the desired value in the 'Notes Field' field.
  79. Select "Final" in the 'Draft/Final' field.
  80. Click [File Note].
  81. Validate a "Progress Notes" message is displayed stating: Note Filed.
  82. Click [OK] and close the form.
  83. Select "Client A" and navigate to the 'Progress Notes' widget.
  84. Validate the progress notes filed in the previous steps are displayed.
  85. Validate the rows filed in the 'Treatment Plan' grid are displayed.
Scenario 3: Diagnosis - Diagnosis Entry
Specific Setup:
  • Client must be enrolled in an active episode and have a diagnosis on file (Client A).
Steps
  1. Select "Client A" and access the ‘Diagnosis’ form.
  2. Select the diagnosis row to edit.
  3. Click [Edit].
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Populate all required and desired fields.
  7. Click [Submit] and [No].
  8. Select "Client A" and access the 'Diagnosis' form.
  9. Select the diagnosis row edited in the previous steps.
  10. Click [Edit].
  11. Validate the newly entered row is displayed as expected.
  12. Close the form.
Scenario 4: 'Staff Members Hours and Exceptions' - Verification of 'Staff Member Hours' Information Entry/Filing
Specific Setup:
  • A staff member must be defined in 'Practitioner Enrollment' (Staff Member A).
Steps
  1. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  2. Click [Staff Member Hours].
  3. Validate the 'Staff Member Hours' grid is displayed.
  4. Click [New Row].
  5. Enter the desired date in the 'Effective Date' field.
  6. Select the desired day in the 'Day' field.
  7. Select the desired site in the 'Site' field.
  8. Enter the desired times in the 'Start Time' and 'End Time' fields.
  9. Populate any other desired values.
  10. Click [Save], [Yes], and [Submit].
  11. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  12. Click [Staff Member Hours].
  13. Validate the 'Staff Member Hours' grid is displayed.
  14. Validate the hours entered in the previous steps are displayed as expected.
  15. Close the form.
Scenario 5: Problem List - Add / Edit / Void a problem
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Must have an "Active" and "Void" dictionary value defined for the 'Status (16214)' dictionary. The 'Active Status' extended dictionary data element defined for these values.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Select the desired problem in the 'Problem' field.
  4. Select "Active" in the 'Status' field.
  5. Populate all other desired fields.
  6. Click [Save], [Yes], and [Submit].
  7. Select "Client A" and access the 'Problem List' form.
  8. Click [View/Enter Problems].
  9. Validate the problem filed in the previous steps is displayed.
  10. Select "Void" in the 'Status' field.
  11. Click [Save], [Yes], and [Submit].
  12. Select "Client A" and access the 'Problem List' form.
  13. Click [View/Enter Problems].
  14. Validate the problem is no longer displayed since it has been voided.
  15. Close the form.
Topics
• Progress Notes • Diagnosis • Practitioner • Problem List
Update 26 Summary | Details
State Form Tools - State Form Button Mapping
Scenario 1: Modeled Form - Validate the use of "State Form Button" mapping functionality
Specific Setup:
  • Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as a "Name" type field [Patient Name] and "Date" type field [Date of Birth], on the form
  • Have a state form definition file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
  • In form "State Form Button Mapping", have the following prompts populated with the form submitted
  • [PopButtonA] selected in the "Button Field"
  • [StateFormDefA] selected in the "State Form Definition" field
  • "Patient Name" selected in the "Parameter Field 1" field
  • "Date of Birth" selected in the "Parameter Field 2" field
  • Have "Netsmart" configure the [PopulateA] button on [FormA] using "Programmer Override" logic in order execute the [StateFormDefA] file so that it populates [FieldA] and [FieldB] on modeled form, when a user clicks the [PopulateA] button
Steps
  1. Open [FormA]
  2. Select the desired client [ClientA]
  3. Click the [PopulateA] button, set up on the form
  4. Validate the [Patient Name] field contains the expected name for [ClientA]
  5. Validate the [Date of Birth] field contains the date of birth for [ClientA]
  6. Click [Submit]
  7. Validate the form files successfully
  8. Return to [FormA]
  9. Select [ClientA]
  10. Validate the [Patient Name] field contains the expected name for [ClientA]
  11. Validate the [Date of Birth] field contains the date of birth for [ClientA]
State Form Definition Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: 'State Form Definition' form - "Define Record Data Elements" grid validations
Specific Setup:
  • Have a state form definition file created in form "State Form Definition", [DefinitionA]. For this example, a definition that selects the "PATID" and "Patient Name" for all clients on the system from the SYSTEM.patient_current_demographics table is used
  • Have two test clients:
  • [ClientA] with a PATID of "1"
  • [ClientB] with a "PATID" of "2" and also has a "Date of Birth" filed in their client record
Steps
  1. Open form "State Form Definition"
  2. Select [DefinitionA]
  3. Navigate to the "Record Definition" tab
  4. Select the existing record in the "Select Record" field
  5. Click the "Define Record Data Elements" to open the data elements grid
  6. In the grid, select the row containing "PATID",
  7. Navigate to the "Force Error Condition" column
  8. Enter "p.PATID = 1" in the input field
  9. Validate the value is accepted
  10. Navigate to 'Default Error Message' column
  11. Enter a default text message that includes the clients name in the message but formatted to use the "NAME1" format variable, to just display only the clients last name. For example enter, "Client {p.patient_name:NAME1} is not valid"
  12. Validate the value is accepted
  13. Save the grid
  14. File the record and file the form
  15. Open form "State Form File Generation"
  16. Select [DefinitionA]
  17. Select "Compile" in the "File Generation Options" field
  18. Click [Process]
  19. Validate a message is displayed indicating the compile is complete but it contains errors
  20. Click [OK]
  21. Click the [Process] button to run the error report
  22. Validate the warning message is present and contains the last name PATID "1" as expected. For example, "Client SMITH is not valid"
  23. Close the report and close the form
  24. Open form "State Form Definition"
  25. Select [DefinitionA]
  26. Navigate to the "Record Definition" tab
  27. Select the existing record in the "Select Record" field
  28. Click "Define Record Data Elements" to open the data elements grid
  29. In the grid, select the row containing "PATID",
  30. Navigate to the "Force Error Condition" column
  31. Enter "p.PATID = "2" in the input field
  32. Validate the value is accepted
  33. Navigate to 'Default Error Message' column
  34. Enter a default text message to include the display of the clients date of birth using the "D3" date format variable, which will display the date in the "YYYY-MM-DD" format. For example enter, "Client {p.patient_name:NAME1} is not valid. DOB {p.date_of_birth:D3}"
  35. Validate the value is accepted
  36. Save the grid
  37. File the record and file the form
  38. Open form "State Form File Generation"
  39. Select [DefinitionA]
  40. Select "Compile" in the "File Generation Options" field
  41. Click [Process]
  42. Validate a message is displayed indicating the compile is complete but it contains errors
  43. Click [OK]
  44. Click the [Process] button to run the error report
  45. Validate a warning message is displayed containing the last name and the date of birth for PATID "2" as expected, for example: "Client SMITH is not valid. DOB 1996-07-25"
Topics
• NX • State Form Tools
Update 27 Summary | Details
User Role Definition - Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • Document Management Definition
  • User Role File Import
  • User Role File Export
Scenario 1: 'User Role File Import' - Import Validations
Specific Setup:
  • Create a new form type [FormX] in form "Document Management Definition". Note the form type ID number, for this example "27" is used
Steps
  1. Open the 'User Role Definition' form.
  2. In the User Role ID field
  3. Enter a name for a new role [RoleX]
  4. Click to the
  5. Click the "Document Management" Section
  6. Select "No" in the 'Is this user a Document Management Administrator?' field.
  7. Select "Specify Forms" in the 'Forms Allowed To View' field
  8. Select the document created in the set up [FormX]
  9. Click back to the "User Role Definition" section
  10. Populate all the required fields and any other desired fields
  11. Submit the form
  12. Validate the form files successfully
  13. Open form "User Role File Export"
  14. Click "Select Roles to Export"
  15. Select [RoleX]
  16. Click [Begin Export]
  17. Save the export file [ExportX] in a folder
  18. Close the form
  19. Open form "Document Management Definition"
  20. Click [Select Form]
  21. Select [FormX]
  22. Click [Delete]
  23. Click [Yes] to confirm the deletion
  24. Exit the form
  25. Open the 'User Role Definition' form.
  26. Select [RoleX]
  27. Click the "Document Management" Section
  28. Click "Specify Forms" in the 'Forms Allowed To View' field
  29. Validate [FormX] is no longer present in the list
  30. Click [Cancel]
  31. Exit the form
  32. Open form "User Role File Import"
  33. Click [Select Import File]
  34. Navigate to the location of [ExportX] saved in step 2
  35. Select the file
  36. Click [Begin Import]
  37. Validate the following warnings are present in the import scan results
  38. "WARNING: Role [RoleX] contains access to view documents of form type '27' that does not exist. Document form type '27' will be skipped.
  39. WARNING: Role [RoleX] has existing data that will be overwritten.
  40. Open the 'User Role Definition' form.
  41. Select [RoleX]
  42. Click the "Document Management" Section
  43. Click "Specify Forms" in the 'Forms Allowed To View' field
  44. Validate the forms list does not include [FormX], as expected
  45. Select [Clear All]
  46. Submit the form
  47. Validate the form files successfully
Scenario 2: User Role Definition - Validate 'Copy User Roles to Other System Codes' functionality
Specific Setup:
  • Have a system defined with two root system codes. [SYSA] and [SYSB]
  • Both system codes contain the same "Forms" and associated form "ID's" defined in form "Document Management Definition"
  • In [SYSA], create a new form type [FormZ] in form "Document Management Definition". Note the form type ID number, for this example "28" is used
  • In [SYSA], have or create a new user role [RoleZ]
  • Have the 'Registry Settings' form, set the 'Copy User Roles to Other System Codes' registry setting to "Y".
  • Log into root code [SYSA]
Steps
  1. Open the 'User Role Definition' form.
  2. Click [Select User Role]
  3. Select [RoleZ]
  4. In the 'Select Codes To Copy User Role To' field, select [SYSB]
  5. Populate any other required fields in that section
  6. Click the "Document Management" Section
  7. Select "No" in the 'Is this user a Document Management Administrator?' field.
  8. Select "Specify Forms" in the 'Forms Allowed To View' field
  9. Select the document created in the set up, [FormZ]
  10. Submit the form
  11. Validate an error is displayed "The following document form types to view do not exist in all selected system codes within 'System Codes To Copy User Role To' and will be unchecked. Document form type '28' does not exist in system code [SYSB]
  12. Click [OK]
  13. At the "Submission will be aborted" error message, Click [OK]
  14. Log out of root code [SYSA]
  15. Log into root code [SYSB]
  16. Open form "Document Management Definition"
  17. Click [Select Form]
  18. Click [Add New]
  19. Validate the "Form ID" field has been assigned the same form ID number assigned to [FormZ] in the set up, form ID "28"
  20. Populate the "Form Name" field
  21. Populate any other required fields
  22. Submit the form
  23. Log out of root code [SYSB]
  24. Log into root code [SYSA]
  25. Open the 'User Role Definition' form.
  26. Click [Select User Role]
  27. Select user role, [RoleZ]
  28. In the 'Select Codes To Copy User Role To' field, select [SYSB]
  29. Populate any other required fields in that section
  30. Click the "Document Management" Section
  31. Select "No" in the 'Is this user a Document Management Administrator?' field.
  32. Select "Specify Forms" in the 'Forms Allowed To View' field
  33. Select the document created in the set up, [FormZ]
  34. Submit the form
  35. Validate the form files successfully
  36. Return to the form
  37. Select [RoleZ]
  38. Click the "Document Management" Section
  39. Click "Specify Forms" in the 'Forms Allowed To View' field
  40. Click [Select Forms to View]
  41. Validate [FormZ] is selected, as expected
  42. Log out of root code [SYSA]
  43. Log into root code [SYSB]
  44. Open the 'User Role Definition' form.
  45. Click [Select User Role]
  46. Validate the "Select User Role" field contains [RoleZ]
  47. Select [RoleZ]
  48. Click the "Document Management" Section
  49. Select "Specify Forms" in the 'Forms Allowed To View' field
  50. Click [Select Forms to View]
  51. Validate [FormZ] is present and selected in the forms list, as expected
  52. Close the form
Topics
• NX • User Role Definition
Update 28 Summary | Details
Guardiant
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
  • Dynamic Form - Confirm Dialog
  • Dynamic Form - Warning Dialog
Scenario 1: Guardiant form - Field validations
Steps
  1. Open form "Guardiant"
  2. Click the "Guardiant Configuration" section
  3. Click [Test Connectivity]
  4. Validate message "Connectivity Test Successful" is displayed
  5. Click [OK]
  6. Click [Test Daily Collection]
  7. Click [Yes] to the warning message
  8. Validate message "Test Succeeded" is displayed
  9. Click [Test Metrics Collection]
  10. Click [Yes] to the warning message
  11. Validate message "Test Succeeded" is displayed
  12. Click "Export Configuration"
  13. In "File Explorer", select a directory to save file
  14. Click [Save]
  15. Go to the directory where the file was saved
  16. Open the "GuardiantConfiguration.txt" file
  17. Validate data is present in the file
Product Updates - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (PM)
Scenario 1: Product Updates: Validate import, view, and install update(s)
Steps
  • Internal Testing Only
Topics
• Guardiant • NX • Forms
Update 29 Summary | Details
'Treatment Plan' - approve documents
Scenario 1: 'My To Do's' widget - Approving Documents
Specific Setup:
  • A user is a staff member and has the 'My To Do's' widget on their myDay view (User A)
  • Document routing is enabled for a form (Form A),
  • "User A" is defined with an associated staff member.
  • A client must be enrolled in an existing episode (Client A).
  • Log in as "User A".
Steps
  1. Access [FormA] (for this test the 'Progress Notes (Group and Individual)' form is used)
  2. Select "Client A" in the 'Select Client' 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' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit Note].
  8. Validate that the 'Confirm Document' dialog is displayed with the progress note data, including an electronic signature at the bottom for the current user/staff member as the Author.
  9. Click [Accept and Route].
  10. Validate the 'Route Document To' dialog is displayed.
  11. Select the "User A" as the 'Approver'.
  12. Click [Submit].
  13. Validate a 'Progress Notes' dialog is displayed stating: "Note Filed."
  14. Click [OK].
  15. Navigate to the 'My To Do's' widget.
  16. Validate there is a To-Do's for 'Form A' for "Client A".
  17. Select the row for "Client A" and click the [Approve Document].
  18. Validate the document is displayed with the expected data.
  19. Click [Accept].
  20. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  21. Validate the To-Do is no longer displayed.
  22. Access the 'Clinical Document Viewer' form.
  23. Select "Client" in the 'Select All or Individual Client' field.
  24. Select "Client A" in the 'Select Client' field.
  25. Click [Process].
  26. Validate the document for "Client A" displays in the document list.
  27. Click to view the document.
  28. Validate that the document displays the expected data.
  29. Close the form.
Scenario 2: Treatment Plan - 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • 'Treatment Plan' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 3: Treatment Plan Copy- 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • A copy must exist of the 'Treatment Plan' form (Treatment Plan Copy).
  • 'Treatment Plan Copy' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan Copy' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 4: Treatment Plan - File a Treatment Plan with Document Routing
Specific Setup:
  • Client must be admitted into an active episode with problems recorded in 'Problem List' form (Client A).
  • The 'Treatment Plan' form must have document routing enabled.
  • Must have the 'My To Do's' widget configured on a view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Click [Add].
  3. Enter "T" in the 'Plan Date' field.
  4. Validate the current date is displayed in the 'Plan Date' field.
  5. Click [Plan Date T].
  6. Validate the current date is displayed in the 'Plan Date' field.
  7. Select any value in the 'Plan Type' field.
  8. Select any value from 'Problem List'.
  9. Click [New Row].
  10. Select any value from the 'Role' field in the 'Participation' section.
  11. Select 'Staff ID' and enter "Staff Member A".
  12. Validate that the selected staff member's name displays in the 'Participant Name' field.
  13. Select any value from the 'Plan Author' field.
  14. Select any value from the 'Notification' field,
  15. Add multiple staff members as needed.
  16. Enter any value in the 'Strengths' field.
  17. Enter any value in the 'Weakness' field.
  18. Enter any value in the 'Discharge Planning' field.
  19. Select "Draft" in the 'Draft/Final' field.
  20. Click [Launch Plan].
  21. Select the problem from the 'Tree View'.
  22. Select any value from the Status field.
  23. Click [Add New Goal].
  24. Enter any value (a large amount of data) in the 'Goal' field.
  25. Validate that the data wraps correctly and displays as expected.
  26. Select any value from the Status field.
  27. Click [Add New Objective].
  28. Enter any value (a large amount of data) in the 'Objective' field.
  29. Validate that the data wraps correctly and displays as expected.
  30. Select any value from the Status field.
  31. Click [Add New Intervention].
  32. Enter any value in the 'Intervention' field.
  33. Select any value in the 'Status' field.
  34. Click [Return to Plan].
  35. Select "Final" in the 'Draft/Final' field.
  36. Click [Submit] and [Sign and Route].
  37. Enter the password and press the 'Enter' key.
  38. Select the staff member associated with the logged in user in the 'Route Document To' field and click [Add].
  39. Click [Submit]
  40. Access the 'My To Do's' widget.
  41. Click [My To Do's].
  42. Validate the record for "Client A" and click [Review].
  43. Validate the 'Document Preview' contains the treatment plan from the previous steps.
  44. Click [Accept] and [Sign].
  45. Enter the password and click [Verify].
  46. Validate the record is no longer present.
  47. Close the 'To Do's'.
Topics
• Document Routing • Treatment Plan
Update 31 Summary | Details
Required Field Checking
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form with Draft/Final
  • Dynamic Form - Filing Error
Scenario 1: Form Submission - Required Field Validation
Specific Setup:
  • Have a modeled form with at least two sections and also includes a "Draft/Final" type field on the form [FormA]
  • In each section of the modeled form have some fields that are set to be required and some that are not
  • Have a modeled form with at least two sections and that does not include "Draft/Final" type field on the form [FormB]
  • In each section of the modeled form have some fields that are set to be required and some that are not
  • Have access to any progress note form containing a "Draft/Final" field
  • Have access to any treatment plan form containing a "Draft/Final" field
  • Have a client [ClientA] enrolled in an active episode [EpisodeA]
Steps
  1. Open [FormA]
  2. Select [ClientA] and then [EpisodeA]
  3. Populate desired fields in each section of the form but leave at least one required field blank in each section
  4. Click [Submit]
  5. Validate a message is displayed indicating which required fields are not populated
  6. Click [OK]
  7. Click [Final]
  8. Validate a message is displayed indicating which required fields are not populated
  9. Click [OK]
  10. Validate a message is displayed indicating the "Final" cannot be selected until all the required prompts within the form contain information
  11. Click [OK]
  12. Validate that the sections on the left panel with missing required fields have a red flag next to the section name
  13. Select just one of the sections
  14. Populate the necessary required fields on that section
  15. Click [Final]
  16. Validate a message is displayed indicating which required fields are not populated
  17. Click [OK]
  18. Validate a message is displayed indicating the "Final" cannot be selected until all the required prompts within the form contain information
  19. Click [OK]
  20. Select the other section
  21. Populate the necessary required fields on that section
  22. Click [Final]
  23. Click [Submit]
  24. Validate the form files successfully
  25. Open [FormB]
  26. Select [ClientA] and then [EpisodeA]
  27. Populate desired fields in each section of the form but leave at least one required field blank in each section
  28. Click [Submit]
  29. Validate a message is displayed indicating which required fields are not populated
  30. Click [OK]
  31. Validate that the sections on the left panel with missing required fields have a red flag next to the section name
  32. Select just one of the sections
  33. Populate the necessary required fields on that section
  34. Click [Submit]
  35. Validate a message is displayed indicating which required fields are not populated
  36. Click [OK]
  37. Select the other section
  38. Populate the necessary required fields on that section
  39. Click [Submit]
  40. Validate the form files successfully
  41. Open the progress note form
  42. Select a client in the "Select Client" field
  43. Select an episode in the "Select Episode" field
  44. Select a progress note type from the "Progress Note For" field
  45. Select a note type from the "Note Type" field
  46. Do not populate the required field, "Notes Field"
  47. Set the "Draft/Final" field to "Final"
  48. Click [File Note]
  49. Validate that the error message "The following fields are missing 'Notes Field'", is displayed
  50. Click [OK]
  51. Validate the section listed on the left panel that contains the missing required field, has a red flag next to the section name
  52. Populate the "Notes Field"
  53. Click [File Note]
  54. Validate the form files successfully
  55. Open the treatment plan form
  56. Click the [Submit] button.
  57. Verify an error is received warning about missing required fields.
  58. Click the [T] button in the 'Plan Date' field to input today's date.
  59. Populate the 'Plan Name' field (If applicable)
  60. Select any value from the 'Plan Type' field.
  61. Select "Final" from the 'Draft/Final' field.
  62. Click [Submit].
  63. Validate the form files successfully
Topics
• Forms • NX
Update 33 Summary | Details
NX - Envelope Import
Scenario 1: Validate importing an existing "Envelope" containing form designer changes
Specific Setup:
  • Have an existing modeled form [FormA] on the system, that includes "Form Designer" changes made to the form. Make note of the existing form designer changes
  • Export the "Envelope" [EnvelopeA], that contains [FormA], setting prompt "Include Form Designer Changes" to "Yes"
Steps
  1. Open form "Envelope Import"
  2. Click [Select Envelope For Import]
  3. Navigate the location of [ExportA]
  4. Select the file
  5. In the "Overwrite Existing Envelope or Create New Envelope" field, select "Create New"
  6. Select "Yes" in prompt "Include Form Design Changes"
  7. At the dialog prompt, "Some or all of the imported envelope's attributes are currently being used within a different envelope, unable to retain original attributes. Do you wish to view the details?", click "No"
  8. At the dialog prompt, "Do you want to continue creating the envelope using new attributes?", click "Yes"
  9. Click "Begin Import Scan"
  10. In the "Import Scan Results" field, validate there are warnings stating that import file contains an envelope and a table with names that are already in use, and that the import process will assign new names based upon the existing name.
  11. Click [Begin Import]
  12. Validate import is completed successfully
  13. Open [FormA]
  14. Validate the form designer changes noted in the set up, are displayed as expected
Topics
• Envelope Import • NX
Update 41 Summary | Details
'Console Widget Configuration' enhanced to allow 'Preferred Forms' selection to display in the 'Console Widget'.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Configuration (PM)
Scenario 1: Console Widget Configuration - Setup and sort order for Preferred Forms in the Multiple Form Widget
Specific Setup:
  • A client must exist that has previously used at least one form available in the 'Forms to Display' section of the 'Console Widget Configuration' form. (Client A)
Steps
  1. Access the 'Console Widget Configuration' form.
  2. Select the 'Multiple Form Widget' section and click [Select Widget].
  3. Select "Add New Widget" in the 'Select Widgets' dialog and click [OK].
  4. Set the 'Widget ID' field to "Test1" and the 'Title' field to "Test Widget 1".
  5. Select an assortment of Forms and click [File].
  6. Close the 'Console Widget Configuration' form.
  7. Access the 'View Definition' form.
  8. Click [Select View], select the current view for the logged in user, and click [OK].
  9. Click [Launch View Designer].
  10. Search for and select "Test Widget 1" from the 'Filter by widget title or category' field.
  11. Click the [Right Arrow] to add "Test Widget 1" to the 'Assigned Widgets' section.
  12. Drag and drop "Test Widget 1" onto the View.
  13. Click [Submit] to verify the changes made to the View.
  14. Click [Submit] and close the form.
  15. Validate "TEST WIDGET 1" has been added to the View.
  16. Select "Client A" and validate any forms that were previously utilized for the client are displayed in a table.
  17. Click [New Record] and validate the Forms selected in 'Console Widget Configuration' are displayed in an alphabetized list.
  18. Select one of the Forms.
  19. Validate the selected Form is launched and close the Form.
  20. Access the 'Console Widget Configuration' form.
  21. Select the 'Multiple Form Widget' section and click [Select Widget].
  22. Select "Test Widget 1 (TEST1)" in the 'Select Widgets' dialog and click [OK].
  23. Validate the 'Widget ID' field contains "TEST1" and the 'Title' field contains "Test Widget 1".
  24. Validate the 'Forms to Display' section contains the previous selection of Forms.
  25. Validate any Forms selected in the 'Forms to Display' section are displayed under 'Preferred Forms'.
  26. Select several of the forms from the 'Forms to Display' section and click [File].
  27. Close the 'Console Widget Configuration' form.
  28. Click [New Record] on "TEST WIDGET 1".
  29. Validate the Forms selected in the 'Preferred Forms' section of 'Console Widget Configuration' are displayed at the top of the list, bolded, and in alphabetical order.
  30. Validate the other Forms that were not selected are listed after the 'Preferred Forms' and in alphabetical order.
  31. Select one of the 'Preferred Forms'.
  32. Validate the selected Form is launched and close the Form.
  33. Access the 'Console Widget Configuration' form.
  34. Select the 'Multiple Form Widget' section and click [Select Widget].
  35. Select "Test Widget 1 (TEST1)" in the 'Select Widgets' dialog and click [OK].
  36. Validate the 'Preferred Forms' section contains the previous selection of Forms.
  37. Deselect all Forms from the 'Preferred Forms' section and click [File].
  38. Close the 'Console Widget Configuration' form.
  39. Click [New Record] on "TEST WIDGET 1".
  40. Validate the Forms that were deselected from the 'Preferred Forms' section in 'Console Widget Configuration' have been unbolded and deprioritized.
Topics
• Console Widget • Console Widget Configuration • NX
Update 44 Summary | Details
'DocR.document_history' table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Move Selected Data (CWS)
Scenario 1: Move Selected Data - Table data validations
Specific Setup:
  • Have a client [ClientA], currently active in two episodes [Episode1] and [Episode2]
  • Have a progress note form [FormA], which is enabled for document routing. For example, the "Progress Notes Group & Individual" form
  • Have a row of data [RowA], filed in [FormA] for [ClientA] in [Episode1], with the document routing document routed and approved. (Note the date and time the document was approved)
  • Have a report or query created to display data in the "DocR.document" table [ReportA]
  • Have a report or query created to display data in the "DocR.document_history" table [ReportB]
  • Have [FormA] added to the logged in users "Chart View"
Steps
  1. Run [ReportA], to display data in the "DocR.document" table
  2. Validate [RowA] is present for [ClientA] in [Episode1]
  3. Make a note of the value in "JOIN_TO_UNIQUE_ID" field. For example: "NOTxxxxx.001"
  4. Open form "Move Selected Data"
  5. Select [ClientA] in the "Entity Database" field
  6. Select [FormA] in the "Form" field
  7. Select [ClientA] in the "Old Entity" field
  8. Select [Episode1] in the "Old Episode" field
  9. Click [Select Row to be Moved]
  10. Select [RowA]
  11. Select [ClientA] in the "New Entity" field
  12. Select [Episode2] in the "New Episode" field
  13. Populate the "Reason for Moving Data" field
  14. Click [Submit]
  15. Validate the form files successfully
  16. Run [ReportA], to display data in the "DocR.document" table
  17. Validate [RowA] is present for [ClientA] but the "Episode" field now indicates [Episode2], as expected
  18. Validate the same value exists in the "JOIN_TO_UNIQUE_ID" field but has incremented by 1 after the decimal point. For example "NOTxxxxx.002". Note the value.
  19. Run [ReportB], to display data in the "DocR.document_History" table
  20. Validate [RowA] is present for [ClientA]
  21. Validate the "doc_id" field in the row. contains the same "JOIN_TO_UNIQUE_ID" value noted in step 3. For this example "NOTxxxxx.002". (Note: the value in "doc_id" contains several values separated by pipe (|) symbols)
  22. Select [ClientA]
  23. Right-click on the clients name to open the clients "Chart"
  24. On the left side panel, choose [FormA]
  25. Click the "Episode 1" tab in the main window
  26. Validate [RowA] is not present
  27. Click the "Episode 2" tab in the main window
  28. Validate [RowA] is displayed, as expected for the row moved from episode 1 in step 2
Topics
• Move Selected Data • NX
Update 47 Summary | Details
Ability to use CSMPROG to login to RxConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Launch RxConnect
Scenario 1: Ability to use CSMPROG to login to RxConnect
Steps
  • Internal Testing only
Topics
• RxConnect
Update 49 Summary | Details
(CDR) Clinical Database Repository
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
Scenario 1: (CDR) Clinical Database Repository - Table validations
Specific Setup:
  • Have a system where the child namespace (for example "CWS") is connected to the parent namespace (PM) with "Clinical Data Repository (CDR)" set to "Yes", in form "Connect/Disconnect Application Namespace".
  • Have a "Modeled" table [TableA] that exists in the child namespace, that is contained in an "Envelope" set with prompt "Include Envelope within CDR (Clinical Data Repository)" set to "Yes" in form "Envelope Definition"
  • Have a modeled form that contains [TableA]
  • Have data submitted in [TableA]
  • Have a user [UserA], who will be assigned permissions to the table during testing
  • Have access to an SQL query or reporting program, for example "Crystal Reports"
Steps
  1. Open form "User Definition" and select [UserA]
  2. Navigate to the "Form and SQL Tables" section
  3. Click "Select Tables for Product SQL Access"
  4. Locate the "Avatar PM" section
  5. Search for the CDR schema name of child namespace. For example if the child namespace name is "CWS", the default schema name would be "CWSSYSTEM"
  6. Click on the arrow next to CDR Schema name, to display the list of tables
  7. Validate [TableA] is displayed for selection
  8. Select the table
  9. Click [OK] and submit the form
  10. Open the SQL query or reporting program, for example "Crystal Reports"
  11. Make a connection to the testing database
  12. In the list of "Tables" displayed for selection, locate the "Avatar PM" section
  13. Search for the CDR schema name of child namespace.
  14. Click on the arrow next to CDR Schema name
  15. Click the plus (+) sign next to "Tables", to expand the list of tables
  16. Validate [TableA] is displayed for selection
  17. Select the table and continue on, selecting fields for the report
  18. Click "Print Preview"
  19. Validate data filed in the table is displayed as expected
  20. Open form "Table Definition"
  21. Select [TableA]
  22. Click [Submit] to refile the table
  23. Validate the table files successfully
  24. Repeat steps 1 thru 2
  25. Validate results are as expected
Topics
• SQL Data Access • NX
Update 50 Summary | Details
Report Definition - Avatar NX
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition (PM)
Scenario 1: Report Definition (Avatar NX) - Create and launch a report requiring an External ODBC Connection
Specific Setup:
  • An external database server [ServerA] exists, that that contains table data [TableA]. For example, an external "SQL" server
  • Using form "NX External ODBC Data Sources", have an "ODBC Data Source" created [DataSourceA] configured to use an ODBC driver to connect to the external database server [ServerA]
  • Have a Crystal Report [ReportA] created, that connects to the external database [ServerA] using [DataSourceA] in order to display data in [TableA].
Steps
  1. Open form "Report Definition"
  2. Click [New Avatar Report]
  3. Populate the "Report Name" field with a name for the report [ReportDefA]
  4. Click [Select Report]
  5. In the "Windows Explorer" window, navigate to the directory that contains [ReportA]
  6. Click [Save]
  7. Click to the "Report Parameters" section
  8. Click [Add New Item] in the "Report Parameters" grid to add any desired parameters. For example "PATID" and "Episode"
  9. Click the [Additional ODBC Connections] section
  10. Click [Add New Item]
  11. Click the "Connection Type" field
  12. Select "myAvatar NX"
  13. Click the "myAvatar NX Connection" field
  14. Select the [DataSourceA] connection created in the set up
  15. Click [Submit]
  16. Validate the form files successfully
  17. Return to the form
  18. Select [ReportA]
  19. Click each section populated in steps 1 thru 3
  20. Validate all fields are populated as expected
  21. Close the form
  22. Search form [ReportDefA]
  23. Populate any parameters required to run the report
  24. Click [Process]
  25. Validate the report results, are as expected
Topics
• Query/Reporting • NX
Update 52 Summary | Details
'SYSTEM.RADplus_user_roles' SQL Table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation (PM)
Scenario 1: "SYSTEM.radplus_user_roles" table - field validations
Specific Setup:
  • [UserA] has permissions to access the 'SYSTEM.RADplus_user_roles' table
  • [UserA] has access to the "Form and Table Documentation" form
  • Have a report [ReportA] created in "Crystal Reports" or any other database program, set to display all the fields in the 'SYSTEM.RADplus_user_roles' table
  • Login as [UserA]
Steps
  1. Open 'Form and Table Documentation' in the 'PM' application
  2. Set the 'Type of Documentation' to 'Table'
  3. In the "Table(s) to be Documented" field select the 'SYSTEM.RADplus_user_roles' table
  4. Click [Process].
  5. Verify that the 'Max Length' value for field ' 'r_option_ids' is '16000'.
  6. Close the report and the form,
  7. Open [ReportA]
  8. Click to expand 'SYSTEM.RADplus_user_roles' table in the 'Field Explorer' section, to list all the fields and their associated field lengths shown next to each field
  9. Locate the 'r_option_ids' field
  10. Validate the associated field length value for the field is "16000"'
  11. Click to process the report
  12. Validate data is present in the 'r_option_ids' field, as expected
Topics
• User Role Definition • SQL Data Access • NX
Update 55 Summary | Details
Avatar NX - 'Result ToDos'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Results Entry
Scenario 1: Validate "Results by Caseload" widget for Today
Specific Setup:
  • "Results by Caseload" widget must be on the user's home view.
  • A client must be admitted in an existing episode (Client A).
  • Client A is part of the logged in user's caseload.
Steps
  1. Select "Client A" and access the 'Results Entry' form.
  2. Select "Add" in the 'Add/Edit/Delete Result' field.
  3. Populate the required and desired fields.
  4. Click [File Header].
  5. Validate a dialog is displayed stating "Header information filed" and click [OK].
  6. Select the 'Result Details' item.
  7. Select "Add" in the 'Add/Edit/Delete Result Detail' field.
  8. Click [Select Header].
  9. Validate the header filed in the previous steps is present.
  10. Select the result and click [OK].
  11. Populate all required and desired fields.
  12. Enter today's date in the 'Observation Date' field.
  13. Enter the desired time in the 'Received Time' field.
  14. Click [File Detail Info].
  15. Validate a dialog is displayed stating "Detail information filed" and click [OK].
  16. Close the form.
  17. Navigate to the 'Results By Caseload' widget.
  18. Click the refresh button.
  19. Select "Today" in the 'Range to View' field.
  20. Validate a new row is added for the result.
  21. Select the row and click [View Result].
  22. Validate the 'Review Results' form opens with the entry.
  23. Select the result in the 'Select Results' field and click [Submit].
  24. Refresh the widget.
  25. Validate the row is no longer present in the 'Results by Caseload' widget.
Scenario 2: Sub-system codes - Validate 'Review Result' To-Do's
Specific Setup:
  • This must be tested in an Avatar NX system.
  • There must be a sub-system code set up for system (Code A).
  • There must be a notification set up for 'Results Entry' in the 'Notifications Setup' form.
  • A client must be enrolled in an existing episode (Client A).
  • User must have the 'My To Do's widget configured to a view and be logged in (User A).
Steps
  1. Select "Client A" and access the 'Results Entry' form.
  2. Select "Add" in the 'Add/Edit/Delete Result' field.
  3. Select "User A" in the 'Ordering Practitioner' field.
  4. Populate all required and desired fields.
  5. Click [File Header Info].
  6. Validate a message is displayed stating: Header information filed.
  7. Click [OK].
  8. Click [Result Details].
  9. Select "Add" in the 'Add/Edit/Delete Result Details' field.
  10. Populate all required and desired fields.
  11. Click [File Detail Info].
  12. Validate a message is displayed stating: Detail information filed.
  13. Click [OK].
  14. Click [Exit Option].
  15. Navigate to the 'My To Do's' widget.
  16. Verify there is a result for "Client A".
  17. Click [Results Entry].
  18. Validate the data displays and click [Cancel].
  19. Close the To Do's.
  20. Log out.
  21. Login to "Code A" and navigate to the 'My To Do's' widget.
  22. Verify there is a result for "Client A".
  23. Click [Results Entry].
  24. Validate the data displays and click [Mark Reviewed] and [Save].
  25. Validate the result no longer displays in the 'My To Do's' widget.
  26. Close the To Do's.
Topics
• Widgets • NX • Results
Update 62 Summary | Details
Support for other products and modules
Scenario 1: Approve a document from the "Sign" tab of the 'My To Do's' widget
Specific Setup:
  • User must have the 'My To Do's' widget on the HomeView.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
  • A user is defined with an associated staff member (User A, Staff Member A).
  • Must be logged in as "User A".
  • A client is enrolled in an existing episode (Client A). "Staff Member A" is the admitting practitioner for "Client A".
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' 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' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate that the 'Confirm Document' dialog is displayed with the progress note data, including an electronic signature at the bottom for the current user/staff member as the Author.
  9. Click [Accept and Route].
  10. Validate the 'Route Document To' dialog is displayed.
  11. Select the 'Admitting Practitioner' and validate "Staff Member A" displays as the 'Approver'.
  12. Click [Submit].
  13. Validate a "Progress Notes" dialog is displayed stating: Note Filed.
  14. Click [OK].
  15. Navigate to the 'My To Do's' widget.
  16. Validate there is a To-Do for the progress note filed in the previous steps.
  17. Select the "Sign" tab.
  18. Validate the 'Search Documents' field contains the progress note document for "Client A".
  19. Validate the 'Document' field contains the progress note data, including an electronic signature at the bottom for "Staff Member A" as both the Author and Admitting Practitioner.
  20. Click [Accept].
  21. Validate the 'Search Documents' field no longer contains the progress note document for "Client A".
  22. Validate the 'Accepted Documents' field contains the accepted progress note document for "Client A".
  23. Click [Sign All].
  24. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  25. Validate the 'Accepted Documents' field no longer contains the progress note document for "Client A".
  26. Access the 'Clinical Document Viewer' form.
  27. Select "Client" in the 'Select All or Individual Client' field.
  28. Select "Client A" in the 'Select Client' field.
  29. Click [Process].
  30. Validate the progress note document appears in the document list and double click on it to view.
  31. Validate that the document displays with the progress note data and an electronic signature for the Author & Admitting Practitioner.
  32. Close the form.
Scenario 2: To Do approval for Progress Note form with Document Routing
Specific Setup:
  • A client must be admitted to an active episode (Client A).
  • Have a progress note form enabled for document routing
  • UserA is staff member and has the "My To do's" widget on their 'myDay' view
Steps
  1. Select Client A and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value from the 'Select Episode' field.
  3. Select any value from the 'Progress Note For' field.
  4. Select any value from the 'Note Type' field.
  5. Complete the remaining required fields.
  6. Select 'Final' from the 'Draft/Final' field.
  7. Click [Submit Note].
  8. Click [Sign and Route]
  9. Set the 'Password' field to the password of the logged in user.
  10. Click [Verify].
  11. Set the 'Supervisor' field to any value (for testing add the practitioner associated to the current logged in user) to route to yourself.
  12. Click [Add] and [Submit].
  13. Access the 'My To Do's' widget.
  14. In the 'Documents to Sign' section, select the newly created 'To Do' for Client A.
  15. Click [Review].
  16. Validate that the 'Sign' button remains disabled until the 'Document Preview' displays the document.
  17. Once enabled, click [Accept] and [Sign].
  18. Set the 'Password' field to the password of the logged in user.
  19. Click [Verify].
  20. Validate that the 'To Do' is removed from the 'My To Do's' list ('Documents to Sign') section.
Scenario 3: Bells Notes Integration - Accept a note via the "Sign" section of the 'My To Do's' widget
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • A progress notes form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. (Form A)
  • "Form A" must have document routing enabled.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select the desired note type.
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Click [Sign Note].
  8. Validate the Sign Note' dialog is displayed.
  9. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  10. Validate a message is displayed stating: Note Signed Successfully.
  11. Log into myAvatar as "User A".
  12. Navigate to the "My To Do's" widget.
  13. Select the "Sign" section.
  14. Validate the 'Search Documents' field contains the progress note document sent via Bells Notes for "Client A".
  15. Validate the 'Document' field contains the progress note data.
  16. Click [Accept].
  17. Validate the 'Search Documents' field no longer contains the progress note document for "Client A".
  18. Validate the 'Accepted Documents' field contains the accepted progress note document for "Client A".
  19. Click [Sign All].
  20. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  21. Validate the 'Accepted Documents' field no longer contains the progress note document for "Client A".
Scenario 4: Bells Notes Integration - Accept a note via the "All" section of the 'My To Do's' widget
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • A progress notes form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. (Form A)
  • "Form A" must have document routing enabled.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select the desired note type.
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Click [Sign Note].
  8. Validate the Sign Note' dialog is displayed.
  9. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  10. Validate a message is displayed stating: Note Signed Successfully.
  11. Log into myAvatar as "User A".
  12. Navigate to the "My To Do's" widget.
  13. Select the "All" section.
  14. Validate a To-Do is displayed for the progress note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed.
  17. Click [Accept].
  18. Enter the password for "User A" in the 'Verify Password' field and click [OK].
  19. Validate the To-Do is no longer displayed.
Scenario 5: Treatment Plan - File a Treatment Plan with Document Routing
Specific Setup:
  • Client must be admitted into an active episode with problems recorded in 'Problem List' form (Client A).
  • The 'Treatment Plan' form must have document routing enabled.
  • Must have the 'My To Do's' widget configured on a view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Click [Add].
  3. Enter "T" in the 'Plan Date' field.
  4. Validate the current date is displayed in the 'Plan Date' field.
  5. Click [Plan Date T].
  6. Validate the current date is displayed in the 'Plan Date' field.
  7. Select any value in the 'Plan Type' field.
  8. Select any value from 'Problem List'.
  9. Click [New Row].
  10. Select any value from the 'Role' field in the 'Participation' section.
  11. Select 'Staff ID' and enter "Staff Member A".
  12. Validate that the selected staff member's name displays in the 'Participant Name' field.
  13. Select any value from the 'Plan Author' field.
  14. Select any value from the 'Notification' field,
  15. Add multiple staff members as needed.
  16. Enter any value in the 'Strengths' field.
  17. Enter any value in the 'Weakness' field.
  18. Enter any value in the 'Discharge Planning' field.
  19. Select "Draft" in the 'Draft/Final' field.
  20. Click [Launch Plan].
  21. Select the problem from the 'Tree View'.
  22. Select any value from the Status field.
  23. Click [Add New Goal].
  24. Enter any value in the 'Goal' field.
  25. Select any value from the Status field.
  26. Click [Add New Objective].
  27. Enter any value in the 'Objective' field.
  28. Select any value from the Status field.
  29. Click [Add New Intervention].
  30. Enter any value in the 'Intervention' field.
  31. Select any value in the 'Status' field.
  32. Click [Return to Plan].
  33. Select "Final" in the 'Draft/Final' field.
  34. Click [Submit].
  35. Validate the 'Document Routing' screen is displayed and contains all populated treatment plan data in the new TIFF format.
  36. Click [Sign and Route].
  37. Enter the password and press the 'Enter' key.
  38. Select the staff member associated with the logged in user in the 'Route Document To' field and click [Add].
  39. Click [Submit]
  40. Access the 'My To Do's' widget.
  41. Click [My To Do's].
  42. Validate the record for "Client A" and click [Review].
  43. Validate the 'Document Preview' contains the treatment plan data in the new TIFF format.
  44. Click [Accept] and [Sign].
  45. Enter the password and click [Verify].
  46. Validate the record is no longer present.
  47. Close the 'To Do's'.
Topics
• Document Routing • Progress Notes • My To Do's
Update 64 Summary | Details
Form Designer - Import/Export
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 - Export/Import Layout Changes
Specific Setup:
  • Have a robust form containing several sections and several fields on each section (Form A).
  • Edit any section (Section A) of "Form A" and make any type of form designer change in the section. For this example, a field is moved to different location (Field A).
Steps
  1. Access "Form A".
  2. Navigate to "Section A".
  3. Validate the form designer change made in the setup is present and "Field A" is in a new location.
  4. Access the 'Form Designer' form.
  5. Select "Form A" from the 'Forms' field.
  6. Click [Export Form Designer Copy].
  7. Validate a 'Confirm' dialog stating "Export Complete." and click [OK] (Note: Export files are saved in the "Downloads" folder)
  8. Close the form.
  9. Access the 'Form Designer' form.
  10. Select "Form A" from the 'Forms' field.
  11. Select "Section A" in the "Sections" field.
  12. Click [Show Section].
  13. Revert the form designer change confirmed in step 1b so "Field A" is returned to its original location.
  14. Click [Save], [OK] and [Submit].
  15. Access "Form A".
  16. Navigate to "Section A".
  17. Validate the form designer change made in step 3d is present.
  18. Close the form.
  19. Access the 'Form Designer' form.
  20. Select "Form A" from the 'Forms' field.
  21. Click [Import Form Designer Copy]
  22. Navigate to the location of the export file.
  23. Select the file.
  24. Click [Submit].
  25. Access "Form A".
  26. Navigate to "Section A".
  27. Validate the form designer change made in the setup is present and "Field A" is in a new location.
  28. Close the form.
Scenario 2: Form Designer - Validate the ability to import a form after a section has been deleted in 'Form Definition'
Specific Setup:
  • User must create a new table in the 'Table Definition' form with at least three columns.
  • User must create a new form in the 'Form Definition' form with at least three sections defined in 'Section Definition' that correspond with the table columns created (Form A).
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" in the 'Forms' field.
  3. Select the first section in the 'Sections' field.
  4. Click [Show Section].
  5. Enter any value in the 'Subsection' field.
  6. Click [Save], [Yes] and [OK].
  7. Repeat step 1b-1e for the remaining sections.
  8. Click [Submit].
  9. Access the 'Form Definition' form.
  10. Select "Form A" in the 'Select Avatar PM Form' field.
  11. Select the 'Section Definition' field.
  12. Select the first section and click [Delete Selected Item].
  13. Validate a dialog stating: "Are you sure?"
  14. Click [Yes] and [Submit].
  15. Access the 'Form Designer' form.
  16. Select "Form A" in the 'Forms' field.
  17. Click [Export Form Designer Copy].
  18. Validate a 'Confirm' dialog stating "Export Complete." and click [OK].
  19. Click [Import Form Designer Copy].
  20. Validate a 'File Upload' dialog and select the newly exported file.
  21. Click [Open] and [Submit].
  22. Validate there is no error message and the form closes.
  23. Refresh the forms.
  24. Select any client and access "Form A".
  25. Validate the form displays the expected sections.
  26. Close the form.
'All Documents' widget - 'Workflow Status'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
Scenario 1: Validate Console Widgets for 'Ambulatory Progress Notes'
Specific Setup:
  • Using the "Site Specific Section Modeling" form, add a SS Note Single Response Dictionary field to the "Ambulatory Progress Notes" form.
  • A Console Widget must be configured for the 'Ambulatory Progress Notes' form. This can be done in the 'Console Widget Configuration' form. Include the site specific section modeling field in the configuration.
  • The Console Widget for 'Ambulatory Progress Notes' must be on the home view.
  • A client must be enrolled in an outpatient episode and have a New Service and Existing Service filed in the 'Ambulatory Progress Notes' form (Client A) and the SS Note Single Response Dictionary type field must be populated.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' Console Widget.
  2. Validate there are rows for the New Service and Existing Service notes that have been previously filed for "Client A".
  3. Validate the site specific section modeling field value is included in the widget data.
  4. Validate all the service fields are displayed.
Scenario 2: Progress Notes (Group and Individual) display in Chart View
Specific Setup:
  • "Progress Notes (Group and Individual)" form includes "Draft/Final".
  • "Progress Notes (Group and Individual)" form is setup to allow Document Routing with "Allow Notifications when Final" field set to "Y".
Steps
  1. Create a note in the "Progress Notes (Group and Individual)" form for any test client (Client A).
  2. Complete all required fields.
  3. Select "Final" in the "Draft/Final" field.
  4. When the Document Routing screen displays, click [Accept and Route] to send this note to any user for approval and to be finalized.
  5. Remain in the "Progress Notes (Group and Individual)" form.
  6. Create another note for Client A and select "Final" in the "Draft/Final" field.
  7. When the Document Routing screen displays, click [Accept] to Finalize the note without sending to a user.
  8. Exit the "Progress Notes (Group and Individual)" form.
  9. Right click on Client A in the "My Clients" widget.
  10. Click on "Progress Notes" in the "Documents" section
  11. Verify the "Document Status" field for both notes is set to "Final".
Scenario 3: Console Widget - Progress Notes Finalized Status
Specific Setup:
  • 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).
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Submit Note].
  5. Click [Sign].
  6. Enter the password for the logged in user and click [Verify].
  7. Validate a 'Progress Notes' dialog stating: "Note Filed."
  8. Click [OK].
  9. Close the form.
  10. Navigate to the 'All Documents' view.
  11. Refresh the 'All Documents' widget.
  12. Select the 'All Forms' field.
  13. Validate the Progress Note is displayed and select it.
  14. Validate the 'Console Widget Viewer' displays the note.
Scenario 4: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Scenario 5: Console Widget Viewer - Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for the Treatment Plan in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add any problem.
  7. Click [Return To Plan] and [OK].
  8. Submit the form.
  9. Select "Client A" and navigate to "View A".
  10. Validate the 'Treatment Plan' console widget contains the draft treatment plan filed in the previous steps and select it.
  11. Click [View].
  12. Validate the 'Console Widget Viewer' displays the draft treatment plan details filed in the previous steps.
  13. Click [Open Record].
  14. Validate the draft treatment plan is opened.
  15. Select "Final" in the 'Treatment Plan Status' field.
  16. Submit the note.
  17. Select "Client A" and navigate back to "View A".
  18. Validate the 'Treatment Plan' console widget contains the finalized treatment plan filed in the previous steps and select it.
  19. Click [View].
  20. Validate the 'Console Widget Viewer' displays the finalized treatment plan details filed in the previous steps.
  21. Click [Open Record].
  22. Validate a message is displayed stating "This plan is marked as Final. Changes are not allowed. Do you want to continue?"
  23. Click [No].
Scenario 6: Clinical Document Viewer - "Void" documents
Specific Setup:
  • Perceptive is enabled.
  • User has permissions to void documents.
  • A client must have non-routed documents on file in the 'Clinical Document Viewer' (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).
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Select "Client A" in the 'Select Client' field.
  4. Click [Process].
  5. Select any non-routed document and view it.
  6. Click [Void] and [Void] again.
  7. Select the desired value in the 'Void Reason' field.
  8. Enter the desired value in the 'Void Comments' field.
  9. Click [Void] and [Close All Documents].
  10. Select the "Search" section.
  11. Click [Close].
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void".
  14. Select the document.
  15. Validate the document displays with "Voided" in the 'Console Widget Viewer'.
Scenario 7: Validate modeled forms that do not allow edits cannot be edited in the 'All Documents' widget
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A user must have a modeled form (Form A) configured for the 'All Documents Widget'.
  • "Form A" must have "No Re-Entry" selected in the 'Re-Enter Form?' field and "No" selected for the 'Remove Form Pre Display', 'Allow Deletion of Row From Table', and 'Allow Edit of Table Rows' fields in 'Form Definition'.
  • User must have the 'All Documents' widget and the 'Console Widget Viewer' configured to a view ('All Documents' view).
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access "Form A".
  2. Fill out all required and desired fields.
  3. Click [Submit].
  4. Navigate to the 'All Documents' view.
  5. Select the 'All Forms' field.
  6. Select "Form A" from the 'Form Description' field.
  7. Validate the record displays and select it.
  8. Validate the 'Open' button is disabled in the 'All Documents' widget.
  9. Validate the record opens in the 'Console Widget Viewer' and that the 'Open Record' button is disabled.
Scenario 8: Treatment Plan - 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • 'Treatment Plan' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 9: Treatment Plan Copy- 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • A copy must exist of the 'Treatment Plan' form (Treatment Plan Copy).
  • 'Treatment Plan Copy' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan Copy' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 10: 'All Documents' widget - Validate 'Treatment Plan' records
Specific Setup:
  • 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).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate any required and desired fields.
  5. Select "Draft" in the 'Treatment Plan Status' field.
  6. Click [Launch Plan].
  7. Add any problem.
  8. Populate all desired fields.
  9. Click [Return To Plan].
  10. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  11. Click [OK].
  12. Submit the form.
  13. Navigate to the 'All Documents' view.
  14. Refresh the 'All Documents' widget.
  15. Select 'All Forms'.
  16. Select "Treatment Plan" in the 'Form Description' field.
  17. Verify the record is present and displays "Draft" in the 'Workflow Status' field and select it.
  18. Validate the 'Console Widget Viewer' displays the plan in the previous steps.
  19. Click [Open Record].
  20. Validate the 'Treatment Plan' form opens with the draft from the previous steps.
  21. Make and desired changes.
  22. Select "Final" in the 'Treatment Plan Status' field.
  23. Click [Submit]
  24. Validate a 'Confirm Document' dialog containing the treatment plan.
  25. Click [Sign].
  26. Enter the password associated with the logged in user and click [Verify].
  27. Navigate to the 'All Documents' view.
  28. Refresh the 'All Documents' widget.
  29. Select 'All Forms'.
  30. Select "Treatment Plan" in the 'Form Description' field.
  31. Verify the record is present and displays "Final" in the 'Workflow Status' field and select it.
  32. Validate the 'Console Widget Viewer' displays the finalized plan from the previous steps.
Topics
• Form Designer • NX • Progress Notes • Widgets • Clinical Document Viewer • Treatment Plan • myAvatar NX Only
Update 66 Summary | Details
'All Documents' widget - User Access Levels
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: All Documents Widget - Validate user access levels
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • There must be three users:
  • A user who has full access to forms and is logged in (User A)
  • A user who has read-only access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User B).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User C).
  • 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).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value in the 'Progress Note For' field.
  3. Populate all required and desired fields.
  4. Select "Final" in the 'Draft/Final' field.
  5. Click [Submit Note].
  6. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  7. Enter the password associated with the logged in user and click [Verify].
  8. Close the form.
  9. Navigate to the 'All Documents' view.
  10. Select 'All Forms'.
  11. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  12. Validate the progress note from the previous steps is present and select it.
  13. Validate the note displays in the 'Console Widget Viewer'.
  14. Validate the 'Open' and 'Open Record' buttons are enabled.
  15. Access the 'Treatment Plan' form.
  16. Enter the desired date in the 'Plan Date' field.
  17. Populate all required and desired fields.
  18. Select "Draft" in the 'Treatment Plan Status' field.
  19. Click [Launch Plan].
  20. Populate all required and desired fields.
  21. Click [Return to Plan] and [OK].
  22. Select "Final" in the 'Treatment Plan Status' field.
  23. Click [Submit].
  24. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  25. Enter the password associated with the logged in user and click [Verify].
  26. Navigate to the 'All Documents' view.
  27. Select 'All Forms'.
  28. Select "Treatment Plan" in the 'Form Description' field.
  29. Validate the treatment plan from the previous steps is present and select it.
  30. Validate the plan displays in the 'Console Widget Viewer'.
  31. Validate the 'Open' and 'Open Record' buttons are enabled.
  32. Log out.
  33. Login as "User B".
  34. Select "Client A" and navigate to the 'All Documents' view.
  35. Select 'All Forms'.
  36. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  37. Validate the progress note from the previous steps is present and select it.
  38. Validate the note displays in the 'Console Widget Viewer'.
  39. Validate the 'Open' and 'Open Record' buttons are disabled.
  40. Select "Treatment Plan" in the 'Form Description' field.
  41. Validate the treatment plan from the previous steps is present and select it.
  42. Validate the plan displays in the 'Console Widget Viewer'.
  43. Validate the 'Open' and 'Open Record' buttons are disabled.
  44. Log out.
  45. Login as "User C".
  46. Select "Client A" and navigate to the 'All Documents' view.
  47. Validate "Progress Notes (Group and Individual)" and "Treatment Plan" and not present in the 'Form Description' field.
Scenario 2: Clinical Document Viewer - Validate user access levels
Specific Setup:
  • A client has finalized documents for 'Progress Notes (Group and Individual)' (Client A).
  • There must be two users:
  • A user who has full access to forms and is logged in (User A).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' form (User B).
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Enter "Client A" in the 'Select Client' field.
  4. Select "All" in the 'Episode' field.
  5. Click [Process].
  6. Select the desired document in the 'Search Results' field.
  7. Click to view the document.
  8. Validate document data is displayed.
  9. Click [Close All Documents].
  10. Navigate back to the "Search" section.
  11. Click [Close].
  12. Log out.
  13. Log in as "User B".
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Individual" in the 'Select All or Individual Client' field.
  16. Enter "Client A" in the 'Select Client' field.
  17. Select "All" in the 'Episode' field.
  18. Click [Process].
  19. Validate the desired document has a lock next to it in the 'Search Results' field.
  20. Validate the user is unable to select and view the document.
  21. Navigate back to the "Search" section.
  22. Click [Close].
'All Documents' widget - The 'Limit Console Widget Viewer To Text Only' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
  • The 'Limit Console Widget Viewer To Text Only' registry setting must be enabled.
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps as text.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps as text.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Scenario 2: 'All Documents' widget - Validate the 'Limit Console Widget Viewer To Text Only' registry setting
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' form.
  • 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).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Limit Console Widget Viewer to Text" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Enter "N" in the Registry Setting Value' field.
  5. Click [Submit].
  6. Validate a 'Registry Editor Filing' dialog and click [OK] and [No].
  7. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  8. Select any value in the 'Progress Note For' field.
  9. Populate all required and desired fields.
  10. Select "Draft" in the 'Draft/Final' field.
  11. Click [Submit Note].
  12. Navigate to the 'All Documents' view.
  13. Select 'All Forms'.
  14. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  15. Select the draft from the previous steps.
  16. Validate the draft note displays as text in the 'Console Widget Viewer'.
  17. Navigate back to the 'Progress Notes (Group and Individual)' form.
  18. Enter "Client A" in the 'Select Client' field.
  19. Select any value in the 'Progress Note For' field.
  20. Populate all required and desired fields.
  21. Select "Final" in the 'Draft/Final' field.
  22. Click [Submit Note].
  23. Validate a 'Confirm Document' dialog containing the data and click [Sign].
  24. Enter the password associated with the logged in user and click [Verify].
  25. Validate a 'Progress Notes' dialog stating: "Note Filed".
  26. Click [OK] and close the form.
  27. Navigate to the 'All Documents' view.
  28. Refresh the 'All Documents' widget.
  29. Select 'All Forms'.
  30. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  31. Select the finalized note from the previous steps.
  32. Validate the 'Console Widget Viewer' displays the TIFF image for the finalized note.
  33. Click [Close All].
  34. Access the 'Registry Settings' form.
  35. Enter "Limit Console Widget Viewer to Text" in the 'Limit Registry Settings to the Following Search Criteria' field.
  36. Click [View Registry Settings].
  37. Enter "Y" in the Registry Setting Value' field.
  38. Click [Submit].
  39. Validate a 'Registry Editor Filing' dialog and click [OK] and [No].
  40. Navigate to the 'All Documents' view.
  41. Refresh the 'All Documents' widget.
  42. Select 'All Forms'.
  43. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  44. Select the draft from the previous steps.
  45. Validate the draft note displays as text in the 'Console Widget Viewer'.
  46. Select the finalized note from the previous steps.
  47. Validate the finalized note displays as text in the 'Console Widget Viewer'.
  48. Click [Close All].
Scenario 3: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Topics
• Treatment Plan • Progress Notes • Widgets • NX • Clinical Document Viewer • Progress Notes (Group And Individual) • Console Widget • myAvatar NX Only
Update 70 Summary | Details
NX Console Widget Viewer - "Launch Report" button
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
  • Diagnosis
  • All Documents Widget
Scenario 1: 'All Documents' widget - Validate 'Family Health History' records
Specific Setup:
  • 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).
  • This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Family Health History' form.
  2. Validate "Add New" is selected in the 'Select Family Member' field.
  3. Select any value in the 'Relationship' field.
  4. Populate any desired fields.
  5. Select "Yes" in the 'Health Problems To Record' field.
  6. Click [Enter Health History].
  7. Click [New Row].
  8. Enter any value in the 'Problem' field.
  9. Populate any desired field.
  10. Click [Save], [Submit], and [No].
  11. Navigate to the 'All Documents' view.
  12. Select 'All Forms'.
  13. Select "Family Health History" in the 'Form Description' field.
  14. Validate the entry from the previous steps is present.
  15. Validate the 'Time' field displays.
  16. Select the entry and validate it displays in the 'Console Widget Viewer'.
  17. Validate the 'Launch Report' button exists.
  18. Click [Launch Report].
  19. Validate a report displays with the information filed in the previous steps.
  20. Close the report.
Scenario 2: Console Widget Viewer - Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for the Treatment Plan in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add any problem.
  7. Click [Return To Plan] and [OK].
  8. Submit the form.
  9. Select "Client A" and navigate to "View A".
  10. Validate the 'Treatment Plan' console widget contains the draft treatment plan filed in the previous steps and select it.
  11. Click [View].
  12. Validate the 'Console Widget Viewer' displays the draft treatment plan details filed in the previous steps.
  13. Click [Open Record].
  14. Validate the draft treatment plan is opened.
  15. Select "Final" in the 'Treatment Plan Status' field.
  16. Submit the note.
  17. Select "Client A" and navigate back to "View A".
  18. Validate the 'Treatment Plan' console widget contains the finalized treatment plan filed in the previous steps and select it.
  19. Click [View].
  20. Validate the 'Console Widget Viewer' displays the finalized treatment plan details filed in the previous steps.
  21. Click [Open Record].
  22. Validate a message is displayed stating "This plan is marked as Final. Changes are not allowed. Do you want to continue?"
  23. Click [No].
Scenario 3: Console Widget Viewer - Diagnosis
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Diagnosis in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Access the 'Diagnosis' form for "Client A".
  2. Select "Admission" in the 'Type Of Diagnosis' field.
  3. Enter the desired time in the 'Time Of Diagnosis' field.
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  7. Click [Submit].
  8. Select "Client A" and navigate to "View A".
  9. Validate the 'Diagnosis' console widget contains diagnosis filed in the previous steps and select it.
  10. Click [View].
  11. Validate the 'Console Widget Viewer' displays the diagnosis details filed in the previous steps.
  12. Click [Open Record].
  13. Validate the 'Diagnosis' form is opened for the existing diagnosis and contains the filed information.
  14. Close the form.
Scenario 4: All Documents Widget - Validate user access levels
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • There must be three users:
  • A user who has full access to forms and is logged in (User A)
  • A user who has read-only access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User B).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User C).
  • 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).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value in the 'Progress Note For' field.
  3. Populate all required and desired fields.
  4. Select "Final" in the 'Draft/Final' field.
  5. Click [Submit Note].
  6. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  7. Enter the password associated with the logged in user and click [Verify].
  8. Close the form.
  9. Navigate to the 'All Documents' view.
  10. Select 'All Forms'.
  11. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  12. Validate the time and staff credentials display.
  13. Validate the progress note from the previous steps is present and select it.
  14. Validate the note displays in the 'Console Widget Viewer'.
  15. Validate the 'Open' and 'Open Record' buttons are enabled.
  16. Access the 'Treatment Plan' form.
  17. Enter the desired date in the 'Plan Date' field.
  18. Populate all required and desired fields.
  19. Select "Draft" in the 'Treatment Plan Status' field.
  20. Click [Launch Plan].
  21. Populate all required and desired fields.
  22. Click [Return to Plan] and [OK].
  23. Select "Final" in the 'Treatment Plan Status' field.
  24. Click [Submit].
  25. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  26. Enter the password associated with the logged in user and click [Verify].
  27. Navigate to the 'All Documents' view.
  28. Select 'All Forms'.
  29. Select "Treatment Plan" in the 'Form Description' field.
  30. Validate the treatment plan from the previous steps is present and select it.
  31. Validate the plan displays in the 'Console Widget Viewer'.
  32. Validate the 'Open' and 'Open Record' buttons are enabled.
  33. Validate the 'Launch Report' button exists.
  34. Click [Launch Report].
  35. Validate a report displays with the information filed in the previous steps.
  36. Close the report.
  37. Log out.
  38. Login as "User B".
  39. Select "Client A" and navigate to the 'All Documents' view.
  40. Select 'All Forms'.
  41. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  42. Validate the progress note from the previous steps is present and select it.
  43. Validate the note displays in the 'Console Widget Viewer'.
  44. Validate the 'Open' and 'Open Record' buttons are disabled.
  45. Select "Treatment Plan" in the 'Form Description' field.
  46. Validate the treatment plan from the previous steps is present and select it.
  47. Validate the plan displays in the 'Console Widget Viewer'.
  48. Validate the 'Open' and 'Open Record' buttons are disabled.
  49. Validate the 'Launch Report' button exists.
  50. Click [Launch Report].
  51. Validate a report displays with the information filed in the previous steps.
  52. Close the report.
  53. Log out.
  54. Login as "User C".
  55. Select "Client A" and navigate to the 'All Documents' view.
  56. Validate "Progress Notes (Group and Individual)" and "Treatment Plan" and not present in the 'Form Description' field.
Scenario 5: 'All Documents' Widget - Validate filtering when switching between clients
Specific Setup:
  • 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).
  • Two clients are admitted into two active episodes with documents on file in the 'All Documents' Widget.
  • The 'Default Value for Console View Episodes Registry Setting' must be set to "1".
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. Validate the 'Episode Header' field contains "All Episodes".
  3. Select "Treatment Plan" from the side menu.
  4. Validate the 'All Documents' widget only displays treatment plan records.
  5. Select a 'Treatment Plan' record and validate the 'Console Widget Viewer' displays the selected plan.
  6. Validate the 'Launch Report' button exists.
  7. Click [Launch Report].
  8. Validate a report displays.
  9. Close the report.
  10. Select "Episode 2" in the 'Episode Header' field.
  11. Validate the 'Console Widget Viewer' still displays the selected 'Treatment Plan' but the filters are cleared in the 'All Documents' widget.
  12. Continue selecting various filters and validate the expected result displays.
  13. Select "Client B".
  14. Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'.
  15. Access the 'Registry Settings' form.
  16. Enter "Default Value for Console View Episodes" in the 'Limit Registry Settings to the Following Search Criteria' field.
  17. Select "Yes" in the 'Include Hidden Registry Settings' field.
  18. Click [View Registry Settings].
  19. Select the registry setting and click [OK].
  20. Enter "2" in the 'Registry Setting Value' field.
  21. Click [Submit], [OK], and [No].
  22. Select "Client A" and navigate to the 'All Documents' view.
  23. Validate the 'Episode Header' field contains "Episode 2".
  24. Click [Close All].
  25. Select 'Continuity of Care Document' from the side menu.
  26. Validate only Continuity of Care Documents display in the 'All Documents' widget.
  27. Select a record and validate it is displayed in the 'Console Widget Viewer'.
  28. Select "Episode 1" in the 'Episode Header' field.
  29. Validate the 'Console Widget Viewer' still displays the record but the filters are cleared in the 'All Documents' widget.
  30. Continue selecting various filters and validate the expected result displays.
  31. Select "Client B".
  32. Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'.
Scenario 6: 'All Documents' widget - Validate 'Diagnosis' records
Specific Setup:
  • 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).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select "Admission" in the 'Type Of Diagnosis' field.
  3. Enter the desired time in the 'Time Of Diagnosis' field.
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  7. Click [Submit].
  8. Select "Client A" and navigate to the 'All Documents' view.
  9. Validate "Client A" is in blue text.
  10. Validate 'Primary All Documents Widget' text is blue.
  11. Select 'All Forms'.
  12. Select "Diagnosis" in the 'Form Description' field.
  13. Validate the entry from the previous steps is present.
  14. Validate the 'Time' field displays.
  15. Select the entry and validate it displays in the 'Console Widget Viewer'.
  16. Validate the 'Launch Report' button exists.
  17. Click [Launch Report].
  18. Validate a report displays with the information filed in the previous steps.
  19. Close the report.
Scenario 7: 'All Documents' widget - validate report for user defined assessment
Specific Setup:
  • 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).
  • A user defined assessment with a report configured must exist (Form A).
Steps
  1. Select "Client A" and access 'Form A'.
  2. Populate all required and desired fields
  3. Click [Submit].
  4. Navigate to the 'All Documents' view.
  5. Select 'All Forms'.
  6. Select "Form A" in the 'Form Description' field.
  7. Validate the entry from the previous steps is present.
  8. Validate the 'Time' field displays.
  9. Select the entry and validate it displays in the 'Console Widget Viewer'.
  10. Validate the 'Launch Report' button exists.
  11. Click [Launch Report].
  12. Validate a report displays with the information filed in the previous steps.
  13. Close the report.
'All Documents' widget - 'Time' column
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
  • Client Health Maintenance
  • Diagnosis
Scenario 1: 'All Documents' widget - Validate 'Family Health History' records
Specific Setup:
  • 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).
  • This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Family Health History' form.
  2. Validate "Add New" is selected in the 'Select Family Member' field.
  3. Select any value in the 'Relationship' field.
  4. Populate any desired fields.
  5. Select "Yes" in the 'Health Problems To Record' field.
  6. Click [Enter Health History].
  7. Click [New Row].
  8. Enter any value in the 'Problem' field.
  9. Populate any desired field.
  10. Click [Save], [Submit], and [No].
  11. Navigate to the 'All Documents' view.
  12. Select 'All Forms'.
  13. Select "Family Health History" in the 'Form Description' field.
  14. Validate the entry from the previous steps is present.
  15. Validate the 'Time' field displays.
  16. Select the entry and validate it displays in the 'Console Widget Viewer'.
  17. Validate the 'Launch Report' button exists.
  18. Click [Launch Report].
  19. Validate a report displays with the information filed in the previous steps.
  20. Close the report.
Scenario 2: Verification of 'Enable Military Time' Registry Setting in Time Display Fields
Specific Setup:
  • The 'RADplus->General->->->->Enable Military Time' registry setting must be set to "Y".
  • NOTE: This is a Netsmart Staff only registry setting. Please contact your Netsmart representative to have this setting configured.
  • One or more time format data fields must be selected as Client Search display fields (via 'Client Lookup/Header Configuration Manager' form 'Display Fields' section)
Steps
  1. Open Avatar PM 'Admission' (or 'Pre Admit') form (or directly open Client Search from 'My Clients' Widget).
  2. In Client Search form, enter values for client search criteria.
  3. Click 'Search' button.
  4. In search results - Ensure that time data fields included as Client Search display fields are displayed with 24-hour military time (HHMM) format.
  5. Time format display field examples:
  6. 'Time Of Diagnosis (989)'
  7. 'Time Of Transfer (49)'
Scenario 3: 'All Documents' widget - Validate 'Client Health Maintenance' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Must have a view configured with the 'All Documents' widget and 'Console Widget Viewer'.
  • This is for Avatar NX systems only.
Steps
  1. Access the 'Client Health Maintenance' form.
  2. Select "Client A".
  3. Click Immunization [Update] and [New Row]
  4. Double click the 'Refused' field.
  5. Select "Yes" in the 'Refused' field.
  6. Validate the 'Reason' field is required.
  7. Double click the 'Refused' field.
  8. Select "No" in the 'Refused' field.
  9. Validate the 'Reason' field is not required.
  10. Select "Historical Information - From Parent's Recall (04)" in the 'Source of Immunization' field.
  11. Complete all required fields.
  12. Click [Save] and [Submit].
  13. Access the 'All Documents' widget.
  14. Select "Client A".
  15. Select the 'All Forms' tab.
  16. Validate the 'Time' field displays.
  17. Select the 'Client Health Maintenance' entry.
  18. Validate the 'Console Widget Viewer' displays the immunization data filed in the previous steps.
  19. Validate the 'Source of Immunization' displays as expected.
  20. Validate the 'Launch Report' button exists.
  21. Click [Launch Report].
  22. Validate a report displays with the information filed in the previous steps.
  23. Close the report.
Scenario 4: 'All Documents' widget - Validate 'Enable Military Time' registry setting
Specific Setup:
  • 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).
  • A client must be enrolled in an existing episode (Client A).
  • The 'Enable Military Time' registry setting must be enabled. Please note: This must be done by a Netsmart Representative.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. Select 'All Forms'.
  3. Validate the 'Time' field displays in military time.
  4. Select the "Admission" entry.
  5. Validate the 'Console Widget Viewer' displays the "Preadmit/Admission Time" in military time.
Scenario 5: 'All Documents' widget - Validate 'Diagnosis' records
Specific Setup:
  • 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).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select "Admission" in the 'Type Of Diagnosis' field.
  3. Enter the desired time in the 'Time Of Diagnosis' field.
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  7. Click [Submit].
  8. Select "Client A" and navigate to the 'All Documents' view.
  9. Validate "Client A" is in blue text.
  10. Validate 'Primary All Documents Widget' text is blue.
  11. Select 'All Forms'.
  12. Select "Diagnosis" in the 'Form Description' field.
  13. Validate the entry from the previous steps is present.
  14. Validate the 'Time' field displays.
  15. Select the entry and validate it displays in the 'Console Widget Viewer'.
  16. Validate the 'Launch Report' button exists.
  17. Click [Launch Report].
  18. Validate a report displays with the information filed in the previous steps.
  19. Close the report.
Scenario 6: 'All Documents' widget - validate report for user defined assessment
Specific Setup:
  • 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).
  • A user defined assessment with a report configured must exist (Form A).
Steps
  1. Select "Client A" and access 'Form A'.
  2. Populate all required and desired fields
  3. Click [Submit].
  4. Navigate to the 'All Documents' view.
  5. Select 'All Forms'.
  6. Select "Form A" in the 'Form Description' field.
  7. Validate the entry from the previous steps is present.
  8. Validate the 'Time' field displays.
  9. Select the entry and validate it displays in the 'Console Widget Viewer'.
  10. Validate the 'Launch Report' button exists.
  11. Click [Launch Report].
  12. Validate a report displays with the information filed in the previous steps.
  13. Close the report.
Topics
• Widgets • Console Widget • NX • Treatment Plan • Diagnosis • Client Health Maintenance • Registry Settings
Update 71 Summary | Details
OE NX - Order Validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Validation
Scenario 1: OE NX - Order Validation - Field Validation - 'Allow Multiple Client Selection in 'Physician Order Validation' form' = "Y"
Specific Setup:
  • The 'Avatar Order Entry->Facility Defaults->Order Validation->->->Allow multiple Client selection in Order Validation forms' registry setting must be set to "Y".
  • The 'Avatar Order Entry->Facility Defaults->Order Validation->->->Display Refills Allowed and Dispense Quantity in Order Validation forms' registry setting must be set to "Y".
  • The 'Avatar Order Entry->Facility Defaults->Order Validation->->->Enable filters in Order Validation forms' registry setting must be set to "U&P&T".
  • The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Restrict Order Validation to the Responsible Practitioner' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A handful of clients must have orders that require validation that did not go to OrderConnect and has an Order Practitioner associated with the user logged into the application.
  • Avatar RADplus 2022 update 71 is required for some functionality.
Steps
  1. Access the 'Order Validation' form
  2. Validate all clients are selected upon entering the form.
  3. Validate changing the filters at the top of the form change the clients available in the 'Select Clients' list.
  4. Click [View] for any individual row in the 'Select Orders to Validate' grid.
  5. Validate order information for the selected order displays in the 'Details of Selected Orders' field.
  6. Click [Display Details for All Selected Orders].
  7. Validate the 'Details of Selected Orders' field contains information for all selected orders.
  8. Click [Validate Selected Orders] and validate all orders selected have been validated.
Topics
• NX • Order Validation
Update 72 Summary | Details
Document Routing - Approval Comments
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 Setup - Select Form
  • Ambulatory Progress Notes
  • Staff Assessment
  • Dynamic Form Client Treatment Plan
  • Dynamic Form Plan Date
Scenario 1: Approving Ambulatory Progress Notes with Approval Comments
Specific Setup:
  • Define at least one additional Avatar user(s) to be document approvers for Ambulatory Progress Notes for the purpose of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select a Progress Note form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the Progress Note form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added for each "Approval Comment" entered.
  20. Open the Progress Note form.
  21. Finalize the form by setting the "Draft/Final" field to "Final".
  22. Submit the form.
  23. Click "Accept and Route".
  24. Provide the password.
  25. Select the approver(s).
  26. To Do's are sent to the approver(s).
  27. Sign on to Avatar as the first approver.
  28. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  29. Click "Accept" to approve the form.
  30. Enter the "Approval Comments".
  31. If there are additional approvers, log onto Avatar as the additional approver.
  32. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  33. Click "Accept" to approve the form.
  34. Enter the "Approval Comments" for this approver.
  35. Open the "Clinical Document Viewer" form.
  36. Locate and view the document that was just filed.
  37. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  38. Open the "System Management Portal".
  39. Using SQL, execute the following query: SELECT * from DocR.comments
  40. Validate that a row has been added for each "Approval Comment" entered.
  41. Open the Progress Note form.
  42. Finalize the form by setting the "Draft/Final" field to "Final".
  43. Submit the form.
  44. Click "Accept and Route".
  45. Provide the password.
  46. Select the approver(s).
  47. To Do's are sent to the approver(s).
  48. Sign on to Avatar as the first approver.
  49. Select the To Do to Accept the document from the Sign Tab of the "My To Do" widget.
  50. Click "Accept" to approve the form.
  51. Enter the "Approval Comments".
  52. Click "Sign All" to sign the document.
  53. If there are additional approvers, log onto Avatar as the additional approver.
  54. Select the To Do to Accept the document from the SignTab of the "My To Do" widget.
  55. Click "Accept" to approve the form.
  56. Enter the "Approval Comments" for this approver.
  57. Click "Sign All" to sign the document.
  58. Open the "Clinical Document Viewer" form.
  59. Locate and view the document that was just filed.
  60. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  61. Open the "System Management Portal".
  62. Using SQL, execute the following query: SELECT * from DocR.comments
  63. Validate that a row has been added for each "Approval Comment" entered.
Scenario 2: Approving Progress Notes (Group and Individual) - Approval Comments
Specific Setup:
  • Define at least one additional Avatar user(s) to be document approvers for Progress Notes(Group and Individual) for the purpose of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select a Progress Note form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the Progress Note form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added for each "Approval Comment" entered.
  20. Open the Progress Note form. File the form in draft mode.
  21. Retrieve the drafted form.
  22. Finalize the form by setting the "Draft/Final" field to "Final".
  23. Submit the form.
  24. Click "Accept and Route".
  25. Provide the password.
  26. Select the approver(s).
  27. To Do's are sent to the approver(s).
  28. Sign on to Avatar as the first approver.
  29. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  30. Click "Accept" to approve the form.
  31. Enter the "Approval Comments".
  32. If there are additional approvers, log onto Avatar as the additional approver.
  33. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  34. Click "Accept" to approve the form.
  35. Enter the "Approval Comments" for this approver.
  36. Open the "Clinical Document Viewer" form.
  37. Locate and view the document that was just filed.
  38. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  39. Open the "System Management Portal".
  40. Using SQL, execute the following query: SELECT * from DocR.comments
  41. Validate that a row has been added for each "Approval Comment" entered.
  42. Open the Progress Note form.
  43. Finalize the form by setting the "Draft/Final" field to "Final".
  44. Submit the form.
  45. Click "Accept and Route".
  46. Provide the password.
  47. Select the approver(s).
  48. To Do's are sent to the approver(s).
  49. Sign on to Avatar as the first approver.
  50. Select the To Do to Accept the document from the Sign Tab of the "My To Do" widget.
  51. Click "Accept" to approve the form.
  52. Enter the "Approval Comments".
  53. Click "Sign All" to sign the document.
  54. If there are additional approvers, log onto Avatar as the additional approver.
  55. Select the To Do to Accept the document from the SignTab of the "My To Do" widget.
  56. Click "Accept" to approve the form.
  57. Enter the "Approval Comments" for this approver.
  58. Click "Sign All" to sign the document.
  59. Open the "Clinical Document Viewer" form.
  60. Locate and view the document that was just filed.
  61. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  62. Open the "System Management Portal".
  63. Using SQL, execute the following query: SELECT * from DocR.comments
  64. Validate that a row has been added for each "Approval Comment" entered.
Scenario 3: Approving Inpatient Progress Notes - Approval Comments
Specific Setup:
  • Define at least one additional Avatar user(s) to be document approvers for Inpatient Progress Notes for the purpose of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select a Progress Note form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the Progress Note form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added for each "Approval Comment" entered.
  20. Open the Progress Note form. File the form in draft mode.
  21. Retrieve the drafted form.
  22. Finalize the form by setting the "Draft/Final" field to "Final".
  23. Submit the form.
  24. Click "Accept and Route".
  25. Provide the password.
  26. Select the approver(s).
  27. To Do's are sent to the approver(s).
  28. Sign on to Avatar as the first approver.
  29. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  30. Click "Accept" to approve the form.
  31. Enter the "Approval Comments".
  32. If there are additional approvers, log onto Avatar as the additional approver.
  33. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  34. Click "Accept" to approve the form.
  35. Enter the "Approval Comments" for this approver.
  36. Open the "Clinical Document Viewer" form.
  37. Locate and view the document that was just filed.
  38. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  39. Open the "System Management Portal".
  40. Using SQL, execute the following query: SELECT * from DocR.comments
  41. Validate that a row has been added for each "Approval Comment" entered.
  42. Open the Progress Note form.
  43. Finalize the form by setting the "Draft/Final" field to "Final".
  44. Submit the form.
  45. Click "Accept and Route".
  46. Provide the password.
  47. Select the approver(s).
  48. To Do's are sent to the approver(s).
  49. Sign on to Avatar as the first approver.
  50. Select the To Do to Accept the document from the Sign Tab of the "My To Do" widget.
  51. Click "Accept" to approve the form.
  52. Enter the "Approval Comments".
  53. Click "Sign All" to sign the document.
  54. If there are additional approvers, log onto Avatar as the additional approver.
  55. Select the To Do to Accept the document from the SignTab of the "My To Do" widget.
  56. Click "Accept" to approve the form.
  57. Enter the "Approval Comments" for this approver.
  58. Click "Sign All" to sign the document.
  59. Open the "Clinical Document Viewer" form.
  60. Locate and view the document that was just filed.
  61. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  62. Open the "System Management Portal".
  63. Using SQL, execute the following query: SELECT * from DocR.comments
  64. Validate that a row has been added for each "Approval Comment" entered.
Scenario 4: Approving CWS Modeled forms - Approval Comments
Specific Setup:
  • Define at least one additional Avatar user(s) to be document approvers for a modeled form for the purpose of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select a CWS modeled form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the CWS modeled form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added for each "Approval Comment" entered.
  20. Open the CWS modeled form.
  21. File the form in draft mode.
  22. Retrieve the drafted form.
  23. Finalize the form by setting the "Draft/Final" field to "Final".
  24. Submit the form.
  25. Click "Accept and Route".
  26. Provide the password.
  27. Select the approver(s).
  28. To Do's are sent to the approver(s).
  29. Sign on to Avatar as the first approver.
  30. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  31. Click "Accept" to approve the form.
  32. Enter the "Approval Comments".
  33. If there are additional approvers, log onto Avatar as the additional approver.
  34. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  35. Click "Accept" to approve the form.
  36. Enter the "Approval Comments" for this approver.
  37. Open the "Clinical Document Viewer" form.
  38. Locate and view the document that was just filed.
  39. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  40. Open the "System Management Portal".
  41. Using SQL, execute the following query: SELECT * from DocR.comments
  42. Validate that a row has been added for each "Approval Comment" entered.
  43. Open the Progress Note form.
  44. Finalize the form by setting the "Draft/Final" field to "Final".
  45. Submit the form.
  46. Click "Accept and Route".
  47. Provide the password.
  48. Select the approver(s).
  49. To Do's are sent to the approver(s).
  50. Sign on to Avatar as the first approver.
  51. Select the To Do to Accept the document from the Sign Tab of the "My To Do" widget.
  52. Click "Accept" to approve the form.
  53. Enter the "Approval Comments".
  54. Click "Sign All" to sign the document.
  55. If there are additional approvers, log onto Avatar as the additional approver.
  56. Select the To Do to Accept the document from the SignTab of the "My To Do" widget.
  57. Click "Accept" to approve the form.
  58. Enter the "Approval Comments" for this approver.
  59. Click "Sign All" to sign the document.
  60. Open the "Clinical Document Viewer" form.
  61. Locate and view the document that was just filed.
  62. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  63. Open the "System Management Portal".
  64. Using SQL, execute the following query: SELECT * from DocR.comments
  65. Validate that a row has been added for each "Approval Comment" entered.
Scenario 5: Approving Treatment Plan - Approval Comments
Specific Setup:
  • Define at least one additional Avatar user(s) to be document approvers for Treatment Plans for the purpose of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select the "Treatment Plan" form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the "Treatment Plan" form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added for each "Approval Comment" entered.
  20. Open the Progress Note form. File the form in draft mode.
  21. Retrieve the drafted form.
  22. Finalize the form by setting the "Draft/Final" field to "Final".
  23. Submit the form.
  24. Click "Accept and Route".
  25. Provide the password.
  26. Select the approver(s).
  27. To Do's are sent to the approver(s).
  28. Sign on to Avatar as the first approver.
  29. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  30. Click "Accept" to approve the form.
  31. Enter the "Approval Comments".
  32. If there are additional approvers, log onto Avatar as the additional approver.
  33. Select the To Do to Approve Document from the All Tab of the "My To Do" widget.
  34. Click "Accept" to approve the form.
  35. Enter the "Approval Comments" for this approver.
  36. Open the "Clinical Document Viewer" form.
  37. Locate and view the document that was just filed.
  38. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  39. Open the "System Management Portal".
  40. Using SQL, execute the following query: SELECT * from DocR.comments
  41. Validate that a row has been added for each "Approval Comment" entered.
  42. Open the Progress Note form.
  43. Finalize the form by setting the "Draft/Final" field to "Final".
  44. Submit the form.
  45. Click "Accept and Route".
  46. Provide the password.
  47. Select the approver(s).
  48. To Do's are sent to the approver(s).
  49. Sign on to Avatar as the first approver.
  50. Select the To Do to Accept the document from the Sign Tab of the "My To Do" widget.
  51. Click "Accept" to approve the form.
  52. Enter the "Approval Comments".
  53. Click "Sign All" to sign the document.
  54. If there are additional approvers, log onto Avatar as the additional approver.
  55. Select the To Do to Accept the document from the SignTab of the "My To Do" widget.
  56. Click "Accept" to approve the form.
  57. Enter the "Approval Comments" for this approver.
  58. Click "Sign All" to sign the document.
  59. Open the "Clinical Document Viewer" form.
  60. Locate and view the document that was just filed.
  61. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  62. Open the "System Management Portal".
  63. Using SQL, execute the following query: SELECT * from DocR.comments
  64. Validate that a row has been added for each "Approval Comment" entered.
Topics
• Document Routing • Progress Notes
Update 76 Summary | Details
Rule Based Routing - Multiple iteration tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Role Definition
  • Routing Queue Definition
  • Routing Role Assignment
  • Routing Assignment Definition
  • Routing Configuration Definition
  • Routing Views Definition
  • Admission (Outpatient)
  • Financial Eligibility
  • Rule Based Routing
  • Routing Status Definition
  • Routing Worklist Item
Scenario 1: Rule Based Routing - Validating data in the multiple iteration tables of the 'Clinical Document QA' form upon form submission.
Specific Setup:
  • The system is set up for Rule based routing with a queue functionality.
  • The 'Rule Based Routing' widget is placed on HomeView.
  • Any progress note form is set up for the document routing (i.e., Progress Notes (Group and Individual)). Note the form name and product name where it is created for further testing. Please Note: The 'Clinical Document QA' form used in this test as it contains multiple iteration table in the form.
  • Document Routing Setup:
  • Document routing functionality is enabled for the 'Medical Coding Note' form.
  • Routing Role Definition:
  • Must have an active routing role created in the form (i.e., Admin, Document QA). Note the roles.
  • Routing Queue Definition:
  • Must have an active queue set up for the form with the multiple iteration table (i.e., Coding QA). Note the name of the queue for further testing.
  • Routing Assignment Definition:
  • Two routing assignments are created such that one assignment that completes a workflow and one that doesn't. Note the name of the assignments.
  • Routing Configuration Definition:
  • The 'Product' field is set to the product where the progress note form exists (i.e., CWS). Note the value for further testing.
  • The progress note form configured above is selected in the 'Form' field. Note the name of the form for further testing.
  • The queue created is selected in the 'Initial Assignment' field (i.e., Coding QA). Note the name of the queue for further testing.
  • Select 'Yes' in the 'Active' field.
  • Desired value is selected in the 'Initial Service Status' field. Note the value for further validation.
  • Desired value in the 'Coding Complete Service Status' fields. Note the value for further testing.
  • Apply Status without Coding Form Submission = 'No'. Note the value for further testing.
  • Routing Views Definition:
  • Desired columns are defined to display in the 'Rule Based Routing' widget.
  • User Definition:
  • A staff member is associated with the current user. Note the password for the user.
  • Guarantor:
  • An existing guarantor is identified. Note the guarantor’s code/name.
  • Admission:
  • An existing outpatient client is identified with the guarantor assigned to the client. Note the Client ID/name, Admission program, Admission date.
  • Service Code:
  • An existing professional service code is identified. Note the service code.
  • Service Fee/Cross Reference Maintenance Form:
  • The service fee and HCPCS code are defined for the service code identified above.
  • Progress Note Group and Individual:
  • A final note is filed for the client using 'New Service' option. Note the date of the service.
Steps
  1. Locate the 'Rule Based Routing' widget.
  2. Select desired queue from the 'Queue' dropdown list.
  3. Select 'All Statuses' from the 'Status' dropdown.
  4. Click [Refresh].
  5. Verify the document finalized from the 'Progress Notes (Group and Individual)' in the setup is available in this widget.
  6. Select the document recently created through the 'Progress Note Group And Individual' form.
  7. Select the desired document.
  8. Click [Launch Worklist Item].
  9. Verify the 'Clinical Document QA' form launched successfully from the widget.
  10. Enter data for the missing and Incorrect code type in the multi iteration table.
  11. Click [Save For Later].
  12. Verify the system successfully navigates to the home view.
  13. Locate to the 'Rule Based Routing' widget.
  14. Select desired queue from the 'Queue' dropdown list.
  15. Select 'All Statuses' from the 'Status' dropdown.
  16. Click [Refresh].
  17. Select the document recently saved.
  18. Click [Launch Worklist Item].
  19. Verify the 'Clinical Document QA' form launched successfully from the widget.
  20. Verify the multiple iteration table retains data correctly as entered.
  21. Click [Save For Later].
  22. Verify the system successfully navigates to the home view.
Scenario 2: Rule Based Routing - Validating data in the multiple iteration tables of the 'Coding QA' form upon form submission.
Specific Setup:
  • The system is set up for Rule based routing with a queue functionality.
  • The 'Rule Based Routing' widget is placed on HomeView.
  • Document Routing Setup:
  • Any progress note form is set up for the document routing (i.e., Progress Notes (Group and Individual)). Note the form name and product name where it is created for further testing.
  • Please Note: The 'Coding QA' form used in this test as it contains multiple iteration table in the form.
  • Routing Role Definition:
  • Must have an active routing role created in the form (i.e., Admin, Document QA). Note the roles.
  • Routing Queue Definition:
  • Must have an active queue set up for the form with the multiple iteration table (i.e., Clinical Document QA, Coding QA). Note the name of the queue for further testing.
  • Routing Assignment Definition:
  • Two routing assignments are created such that one assignment that completes a workflow and one that doesn't. Note the name of the assignments.
  • Routing Configuration Definition:
  • The 'Product' field is set to the product where the progress note form exists (i.e., CWS). Note the value for further testing.
  • The progress note form configured above is selected in the 'Form' field. Note the name of the form for further testing.
  • The queue created is selected in the 'Initial Assignment' field (i.e., Clinical Document QA). Note the name of the queue for further testing.
  • Select 'Yes' in the 'Active' field.
  • Desired value is selected in the 'Initial Service Status' field. Note the value for further validation.
  • Desired value in the 'Coding Complete Service Status' fields. Note the value for further testing.
  • Apply Status without Coding Form Submission = 'No'. Note the value for further testing.
  • Routing Views Definition:
  • Desired columns are defined to display in the 'Rule Based Routing' widget.
  • User Definition:
  • A staff member is associated with the current user. Note the password for the user.
  • Guarantor:
  • An existing guarantor is identified. Note the guarantor's code/name.
  • Admission:
  • An existing outpatient client is identified with the guarantor assigned to the client. Note the Client ID/name, Admission program, Admission date.
  • Service Code:
  • An existing professional service code is identified. Note the service code.
  • Service Fee/Cross Reference Maintenance Form:
  • The service fee and HCPCS code are defined for the service code identified above.
  • Progress Note Group and Individual:
  • A final note is filed for the client using 'New Service' option. Note the date of the service.
Steps
  1. Locate the 'Rule Based Routing' widget.
  2. Select desired queue from the 'Queue' dropdown list.
  3. Select 'All Statuses' from the 'Status' dropdown.
  4. Click [Refresh].
  5. Verify the document finalized from the 'Progress Notes (Group and Individual)' in the setup is available in this widget.
  6. Select the document recently created through the 'Progress Note Group And Individual' form.
  7. Select the desired document.
  8. Click [Launch Worklist Item].
  9. Verify the 'Coding QA' form launched successfully from the widget.
  10. Enter data for the missing and Incorrect code type in the multi iteration table.
  11. Click [Save For Later].
  12. Verify the system successfully navigates to the home view.
  13. Locate to the 'Rule Based Routing' widget.
  14. Select desired queue from the 'Queue' dropdown list.
  15. Select 'All Statuses' from the 'Status' dropdown.
  16. Click [Refresh].
  17. Select the document recently saved.
  18. Click [Launch Worklist Item].
  19. Verify the 'Coding QA' form launched successfully from the widget.
  20. Verify the multiple iteration table retains the correct information as entered.
  21. Click [Save For Later].
  22. Verify the system successfully navigates to the home view.
Topics
• Rule Based Routing • NX
Update 81 Summary | Details
Submitting a form with a "DSM-5" diagnosis code
Scenario 1: Submit a Modeled form enabled for "Document Routing"- Registry Setting "DSM Classification To Use" set to "2"
Specific Setup:
  • Have a modeled form [FormA] that includes a "Diagnosis" search field on the form
  • [FormA] is enabled for document routing
  • Have "Registry Setting", "DSM Classification To Use" set to "2"
  • [UserA] is staff member and has the "My To do's" widget on their home view
  • Log in as UserA
Steps
  1. Open [FormA]
  2. In the "Diagnosis" search field, search for a diagnosis code that is also associated "DSM-5" code. For example "Alcohol Abuse (F10.10)"
  3. Populate all other desired fields on the form.
  4. Select "Final" in the 'Draft/Final' field.
  5. Verify the document preview displays the data as expected.
  6. Click [Accept and Route].
  7. Enter the user's password in the 'Password' field.
  8. Click [OK].
  9. Select the practitioner associated to the logged in user as the approver
  10. Click [Submit].
  11. Validate the form submits successfully
  12. Navigate to the 'My To Do's' widget.
  13. Click [Approve Document] for the document routed in the previous steps.
  14. Validate the document preview displays the data as expected.
  15. Click [Accept].
  16. Enter the user's password in the 'Password' field.
  17. Click [OK].
  18. Validate the "To Do" accepted successfully and is removed from the 'My To Do's' widget.
  19. Repeat steps 1 and 2 but in step 1a, select a diagnosis code that does not have an associated "DSM-5" code. For example, "Smoke Hypersensitivity (J30.89)
  20. Validate results are as expected
Scenario 2: Submit a Progress Note form enabled for "Document Routing"- Registry Setting "DSM Classification To Use" set to "2"
Specific Setup:
  • Have any progress note enabled for document routing. For example the "Progress Notes (Group & Individual)" form
  • Using "Site Specific Section Modeling" add a "Diagnosis" search field to the form
  • Have "Registry Setting", "DSM Classification To Use" set to "2"
  • [UserA] is staff member and has the "My To do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access the progress note form
  2. In the "Diagnosis" search field, search for a diagnosis code that is also associated "DSM-5" code. For example "Alcohol Abuse (F10.10)"
  3. Populate all other desired fields on the form.
  4. Select "Final" in the 'Draft/Final' field.
  5. Verify the document preview displays the data as expected.
  6. Click [Accept and Route].
  7. Enter the user's password in the 'Password' field.
  8. Click [OK].
  9. Select the practitioner associated to the logged in user as the approver
  10. Click [Submit].
  11. Validate the form submits successfully
  12. Navigate to the 'My To Do's' widget.
  13. Click [Approve Document] for the document routed in the previous steps.
  14. Validate the document preview displays the data as expected.
  15. Click [Accept].
  16. Enter the user's password in the 'Password' field.
  17. Click [OK].
  18. Validate the "To Do" accepted successfully and is removed from the 'My To Do's' widget.
  19. Repeat steps 1 and 2 but in step 1a, select a diagnosis code that does not have an associated "DSM-5" code. For example, "Smoke Hypersensitivity (J30.89)
  20. Validate results are as expected
Topics
• Modeling • NX • Progress Notes
Update 83 Summary | Details
Avatar NX - 'All Documents' Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: Progress Notes (Group and Individual) - Group Default Notes - file a new service group note
Specific Setup:
  • A group is defined with two or more clients (Group 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).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select the "Group Default Notes" section.
  3. Enter the desired date in the 'Date Of Group' field.
  4. Enter the desired practitioner in the 'Practitioner' field.
  5. Select "New Service" in the 'Progress Note For' field.
  6. Enter "Group A" in the 'Group Name or Number' field.
  7. Select the desired value in the 'Note Type' field.
  8. Enter the desired value in the 'Note' field.
  9. Select the desired group service code in the 'Service Charge Code' field.
  10. Select the desired program in the 'Service Program' field.
  11. Click [File Note].
  12. Validate a "Group Default Notes Message" is displayed stating: Progress notes are filed.
  13. Click [OK] and close the form.
  14. Select a client in "Group A" and navigate to the 'All Documents' view.
  15. Refresh the 'All Documents' widget.
  16. Select 'All Forms'.
  17. Validate the group note from the previous steps is present and select it.
  18. Validate the 'Console Widget Viewer' displays the note with the data entered in the previous steps.
  19. Repeat steps 2a-2d for remaining group members.
Scenario 2: 'All Documents' widget - Validate group scratch note is replaced with individual note
Specific Setup:
  • A group is defined with two or more clients (Group 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).
  • Document routing must be enabled for 'Progress Notes (Group and Individual)'.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select the "Group Default Notes" section.
  3. Enter the desired date in the 'Date Of Group' field.
  4. Enter the desired practitioner in the 'Practitioner' field.
  5. Select "New Service" in the 'Progress Note For' field.
  6. Enter "Group A" in the 'Group Name or Number' field.
  7. Select the desired value in the 'Note Type' field.
  8. Enter the desired value in the 'Note' field.
  9. Select the desired group service code in the 'Service Charge Code' field.
  10. Select the desired program in the 'Service Program' field.
  11. Click [File Note].
  12. Validate a 'Group Default Notes Message' is displayed stating: "Progress notes are filed."
  13. Click [OK] and close the form.
  14. Select a client in "Group A" and navigate to the 'All Documents' view.
  15. Refresh the 'All Documents' widget.
  16. Select 'All Forms'.
  17. Validate the group note from the previous steps is present and select it.
  18. Validate the 'Console Widget Viewer' displays the note with the data entered in the previous steps.
  19. Click [Open Record].
  20. Validate the 'Progress Notes (Group and Individual)' form opens with the data populated from the scratch note.
  21. Make any desired edits.
  22. Select "Final" in the 'Draft/Final' field.
  23. Click [Submit Note].
  24. Validate a 'Confirm Document' dialog containing the finalized note.
  25. Click [Sign].
  26. Validate a 'Progress Notes' dialog stating "Note Filed." and click [OK].
  27. Close the form.
  28. Navigate to the 'All Documents' view.
  29. Refresh the 'All Documents' widget.
  30. Select 'All Forms'.
  31. Validate the 'All Documents' widget does not contain the group scratch note.
  32. Validate the finalized note is present and select it.
  33. Validate the 'Console Widget Viewer' displays the finalized note.
  34. Click [Close All].
  35. Repeat steps 2a-3f for remaining group members.
Scenario 3: Progress Notes (Group and Individual) - Group scratch note - Chart View
Specific Setup:
  • A group service code (Service Code A) must be configured as a "Primary" 'Service Code Category' and "Other" 'Service Code Type - through the 'Service Codes' form
  • A Group (Group A) must exist with at least 1 client (Client A)
  • Progress Notes Group and Individual must be in the list of forms in the Chart View
Steps
  1. Open the 'Progress Notes (Group and Individual)' form.
  2. Select "Group Default Notes" from the 'Sections' menu.
  3. Set the 'Date Of Group' field to the current date.
  4. Set the 'Practitioner' field to the practitioner associated to the logged in user.
  5. Set the 'Progress Note For' field to "New Service".
  6. Set the 'Note Type' field to any value.
  7. Select any value from the 'User To Send Scratch Note To-Do Item To' field.
  8. Set the 'Group Name or Number' field to "Group A".
  9. Set the 'Note' field to any text.
  10. Set the 'Service Charge Code' field to "Service Code A".
  11. Set the 'Service Program' field to any program.
  12. Click [File Note].
  13. Click [OK].
  14. Click [Close Form].
  15. Click [Yes].
  16. Set the 'Search Clients' field to "Client A".
  17. Double Click Client A to open the Chart View.
  18. Click the 'Progress Notes (Group and Individual)' form.
  19. Validate the Progress Notes data displays successfully.
Topics
• Progress Notes (Group And Individual) • NX • All Documents Widget
Update 84 Summary | Details
'All Documents' widget - Non-episodic documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Capture
  • Console Widget Viewer
Scenario 1: Chart Review - Document Capture (Prevent Non-episodic Document Capture - Disabled)
Specific Setup:
  • This must be tested in a Perceptive enabled environment.
  • Have "Document Capture" added to a user's chart review forms
  • Have a client with existing active episodes
  • Have a document that can be imported for an existing client on the system. [DocumentA]
  • Have registry setting "Prevent Non-episodic Document Capture" set to "N"
Steps
  1. Select a client
  2. Right-click on the client and click 'Display Chart'
  3. Select the "Document Capture" form from the list of forms on the left side panel
  4. Select "Import" from the "Capture Mode" dialog box
  5. In the "Select Episode" dialog, click the episode number drop down list
  6. Validate "Non-episodic" and the client "Episodic" episodes are displayed as a selection
  7. Select either non-episodic or any episodic number episode from the list
  8. In the "Document Capture" window, click [Capture]
  9. Click [Browse] in the "Select Files" dialog box
  10. From the "Look In" prompt, navigate to the location of [DocumentA]
  11. Select the file
  12. Click [Open]
  13. Click [Done] in the "Select Files" dialog box
  14. Validate the document capture window displays the document contents as expected
  15. Select the document type from the "Document Type" drop down list
  16. Populate the "Document Description" field, if desired
  17. Click [Save]
  18. Click the "Save was successful" [x] button
  19. Click the "Document was added to Avatar" [x] button
  20. Open "Clinical Document Viewer"
  21. Select the client and view the clients current documents
  22. View the document that was imported in previous steps
  23. Validate the document image is as expected
Scenario 2: Chart Review - Document Capture (Prevent Non-episodic Document Capture - Enabled)
Specific Setup:
  • This must be tested in a Perceptive enabled environment.
  • Have "Document Capture" added to a user's chart review forms
  • Have a document that can be imported for an existing client on the system. [DocumentA]
  • Have registry setting "Prevent Non-episodic Document Capture" set to "Y"
Steps
  1. Select a client
  2. Right-click on the client and click 'Display Chart'
  3. Select the "Document Capture" form from the list of forms on the left side panel
  4. Select the "Document Capture" form.
  5. Select "Import" from the "Capture Mode" dialog box
  6. In the "Select Episode" dialog, click the episode number drop down list
  7. Validate "Non-episodic" is not displayed as a selection
  8. Select an episode
  9. In the "Document Capture" window, click [Capture]
  10. Click [Browse] in the "Select Files" dialog box
  11. From the "Look In" prompt, navigate to the location of [DocumentA]
  12. Select the file
  13. Click [Open]
  14. Click [Done] in the "Select Files" dialog box
  15. Validate the document capture window displays the document contents as expected
  16. Select the document type from the "Document Type" drop down list
  17. Populate the "Document Description" field, if desired
  18. Click [Save]
  19. Click the "Save was successful" [x] button
  20. Click the "Document was added to Avatar" [x] button
  21. Open "Clinical Document Viewer"
  22. Select the client and view the clients current documents
  23. View the document that was imported in previous steps
  24. Validate the document image is as expected
Scenario 3: Validate Document Capture - Import Non-Episodic
Specific Setup:
  • Perceptive must be installed and enabled.
  • A user must be defined (User A).
  • A document must exist for import.
Steps
  1. Login as "User A".
  2. Validate the loading spinner is blue.
  3. Select a client from "myClients" or from the Client search.
  4. Open the client's dashboard.
  5. Validate the 'Client Dashboard', 'Client Header' text and 'Document Capture' icon are blue.
  6. Using "Document Capture", scan or import in a document.
  7. Select "Non-episodic" in the "Episode" field.
  8. Validate the correct Episode displays in the "Document Properties" pane.
  9. Capture and save the document.
  10. View the document using "Clinical Document Viewer" or the Chart to ensure it has the Non-episodic (-) designation and that it displays.
Scenario 4: 'All Documents' widget - validate the correct documents display for sub-system code
Specific Setup:
  • Perceptive must be installed and enabled.
  • A user must be defined (User A). "User A" must be currently logged into the root system code.
  • A document must exist for import.
  • 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).
  • A sub-system code must exist that limits episode access (Sub-System Code A).
  • The 'Prevent Non-Episodic Document Capture' registry setting must be blank.
  • A client must be admitted in an inpatient and outpatient episode (Client A).
Steps
  1. Select "Client A" and access the 'Client Dashboard'.
  2. Using 'Document Capture', scan or import in a document.
  3. Select "Non-episodic" in the 'Episode' field.
  4. Capture and save the document.
  5. Navigate to the 'All Documents' view.
  6. Validate the newly imported non-episodic document is present and select it.
  7. Validate the 'Console Widget Viewer' displays the document.
  8. Click [Close All].
  9. Open the client's dashboard.
  10. Using 'Document Capture', scan or import in a document.
  11. Select an outpatient episode in the 'Episode' field.
  12. Validate the correct Episode displays in the 'Document Properties' field.
  13. Capture and save the document.
  14. Navigate to the "All Documents" view.
  15. Select "All Episodes" in the 'Episode' field.
  16. Refresh the 'All Documents' widget.
  17. Validate the newly imported episodic document is present and select it.
  18. Validate the 'Console Widget Viewer' displays the document.
  19. Log out.
  20. Login to "Sub-System Code A" as "User A".
  21. Select "Client A" and navigate to the 'All Documents' view.
  22. Validate the non-episodic document is present and select it.
  23. Validate the 'Console Widget Viewer' displays the document.
  24. Validate the 'Episode' field does not contain an outpatient episode.
  25. Validate the episodic document from the previous steps is not present in the 'All Documents' widget.
Topics
• Clinical Document Viewer • Document Import/Scan • Perceptive • NX
2021 Update 131 Summary | Details
To Do List - Supported in NX
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • To Do List
  • Dynamic Form Display Row Detail
Scenario 1: To Do List - Validate Print on Pop Up Windows
Steps
  1. Open the "To Do List" form.
  2. Click "Load To Dos" button.
  3. Select a To Do.
  4. Click "Display Row".
  5. Validate document displays.
  6. Click "Print".
  7. Validate document prints as it displays.
  8. Return to the main page.
  9. Click "Print To Do List".
  10. Validate the report includes all the documents in the "To Do List" table.
  11. Return to the main page.
  12. Add a comment to one of the rows.
  13. Close form.
Scenario 2: To Do List - Form Validation
Specific Setup:
  • To Dos generated for various clients.
Steps
  1. Open the "To Do List" form.
  2. Click "Load To Dos" button.
  3. Validate the To Do's are loaded into a table.
  4. Select a row in the table.
  5. Click "Display Row" button.
  6. Validate the document displays and is readable.
  7. Click "Print" button.
  8. Validate the document prints as it displays.
  9. Click "Print To Do List" button.
  10. Validate all the To Dos are included in the list.
  11. Close the report.
  12. Click "Submit" to exit the form.
Topics
• My To Do's • NX
2021 Update 136.1 Summary | Details
Querying Modeled form Data
Scenario 1: Validate querying modeled form data using table 'SYSTEM.RADplus_client_modeled_link"
Specific Setup:
  • Have a modeled form [FormA] with rows of data filed in the form. For this test, modeled form "Patient Conditions" is used.
  • In form "Widget Definition", have two "SQL" query widgets defined [WidgetA] and [WidgetB], set to display data filed in the modeled table[TableA], that is associated with [FormA]. In this example "SYSTEM.patient_conditions" is used
  • [WidgetA] will have a standard query to display all data. For example: "SELECT * FROM SYSTEM.user_patient_conditions" WHERE Option_Id='USER16'"
  • [WidgetB] will have a query to display all data but will use the "SYSTEM.RADplus_client_modeled_link" table. For example: "Select * from SYSTEM.RADplus_client_modeled_link as a inner join SYSTEM.user_patient_conditions as b on a.Option_Id=b.Option_Id and a.PATID=b.PATID and a.FACILITY=b.FACILITY"
  • [UserA] has both widgets placed on their home view
  • Have two reports created, [ReportA] and [ReportB]
  • [ReportA] will query [TableA] directly in order to display all field data
  • [ReportB] will query the "SYSTEM.RADplus_client_modeled_link" table with field "Option Description" field equal to [FormA], in order to display all field data in [TableA]
Steps
  1. Log in as [UserA]
  2. Click the [Refresh] button for [WidgetA] on the home view
  3. Validate data is displayed successfully and note data retrieval time for data to populate in the widget
  4. Click the [Refresh] button for [WidgetB] on the home view
  5. Validate data is displayed successfully and note the data retrieval time for data to display in the widget
  6. Validate the time of data retrieval is the same or better than the time noted in step 2a
  7. Open [ReportA]
  8. Click to submit the report
  9. Validate data is displayed successfully and note the data retrieval time taken for data to populate in the report
  10. Open [ReportB]
  11. Click to submit the report
  12. Validate data retrieval time is the same or better than the time noted in step 4a
Topics
• SQL Data Access • NX