Skip to main content

RADplus 2022 Monthly Release 2022.02.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
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 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 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:
  • User Definition
  • 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 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 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
  • Clinical Document Viewer
  • 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
  • Clinical Document Viewer
  • 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
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