Skip to main content

RADplus 2024 Quarterly Release 2024.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
2024 Update installation
Scenario 1: Validate Upgrading RADplus 2023 to 2024 is successful when 2023.04.00 is loaded
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
Update 2 Summary | Details
Client list is not displaying in Vitals iOS application
Scenario 1: Validate 'Vitals' app caseload
Steps
  1. Admit client to inpatient program. Do not add Admitting or Attending Practitioner as yourself.
  2. Navigate to Vitals app and Confirm Client is not on your caseload.
  3. Navigate to 'Attending Practitioner' form and make yourself the attending practitioner.
  4. Confirm the client is displayed in Vitals App.
  5. Using 'Attending Practitioner' Form, remove yourself as attending practitioner.
  6. Confirm patient is not displayed in Vitals app.
  7. Navigate to 'Admission' and edit the admission.
  8. Confirm the attending practitioner is showing the practitioner that you just changed.
  9. You are not able to change the attending but you can change the admitting. Change the admitting practitioner to yourself.
  10. Confirm the patient now displays in the Vitals app.
  11. Go back to 'Admission' and edit the admission.
  12. Change the 'Admitting practitioner' to the other practitioner and submit.
  13. Confirm patient is not displayed in Vitals app.
  14. Log out and log back in and confirm the patient is not displayed in your caseload in Vitals.
  15. Transfer patient from other provider to yourself via 'Transfer practitioner' caseload.
  16. Select 'Attending practitioner' caseload first.
  17. Confirm patient displays in Vitals app.
  18. Transfer patient from yourself to the other provider via 'Transfer practitioner' caseload.
  19. Select 'Attending practitioner' caseload.
  20. Confirm patient is not displayed in Vitals app.
  21. Transfer patient from other provider to yourself via 'Transfer practitioner' caseload.
  22. Select 'Admitting practitioner' caseload.
  23. Confirm patient displays in Vitals app.
  24. Transfer patient from yourself to the other provider via 'Transfer practitioner' caseload.
  25. Select 'Admitting practitioner' caseload.
  26. Confirm patient is not displayed in Vitals app.
  27. Add patient to your caseload via 'Nursing caseload' assignment.
  28. Confirm patient displays in Vitals app.
  29. Deselect patient in 'Nursing caseload' assignment.
  30. Confirm patient is not displayed in Vitals app.
  31. Add patient to caseload using 'Manage nursing' caseload.
  32. Confirm patient displays in Vitals app.
  33. Remove patient from caseload using 'Manage nursing' caseload.
  34. Confirm patient is not displayed in Vitals app.
  35. Add patient to 'Manage observer' caseload.
  36. Confirm patient displays in observer app.
  37. Confirm patient displays in vitals app.
  38. Remove patient in 'Manage observer' caseload.
  39. Confirm patient is not displayed in Observer app.
  40. Confirm patient is not displayed in Vitals app.
Topics
• Medication Vital
Update 3 Summary | Details
Internal Utilities
Scenario 1: 'Support Utilities' Form (Internal only) - Validate Export 'Envelope' and Export 'Report' Attributes functionality
Steps
  1. Internal Testing Only
Topics
• Modeling
Update 4 Summary | Details
Form Definition - 'Document Routing' section
Scenario 1: Validate document routing settings in "Form Definition"
Specific Setup:
  • Have a modeled form with a "Draft/Final" or a "Draft/Final/Pending" field (Form A).
Steps
  1. Access the 'Form Definition' form.
  2. Select "Form A".
  3. Navigate to the "Document Routing" section.
  4. Validate the 'Defer Document Generation' field is not displayed.
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Click [Select Type].
  7. Select the desired value and click [OK].
  8. Select the desired value in the 'Approver Required' field.
  9. Click [Submit].
  10. Validate the form files successfully.
  11. Access the 'Form Definition' form.
  12. Select "Form A".
  13. Navigate to the "Document Routing" section.
  14. Validate all previously populated fields are displayed as expected.
  15. Close the form.
Topics
• Modeling • Document Routing
Update 5 Summary | Details
Document Management Definition - Perceptive document synchronization
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Client Document Capture
  • Document Capture
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field.
  6. Select the desired entity in the "Entity" field.
  7. Populate any other desired fields in the "Form" section.
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list.
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report".
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section.
  19. Click [File].
  20. Validate the form files successfully.
  21. Click [Select Form].
  22. Select the form just submitted in step 5.
  23. Validate all fields populated in steps 1 thru 5, are populated as expected.
  24. Click back to the [Form] section.
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list.
  29. Click [Select Form].
  30. Select the form "Inbox Attachments".
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  33. Click [OK].
  34. Click [Select Form].
  35. Select the form "Results Document".
  36. Click [Delete].
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  38. Click [OK].
  39. Close the form.
Scenario 2: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Topics
• Perceptive
Update 7 Summary | Details
Client Alerts - SQL Table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SQL Query/Reporting Tool
  • Client Alerts
Scenario 1: Validate querying data in the "SYSTEM.RADplus_client_alerts table"
Specific Setup:
  • Have two "Alert Types" configured in form "Alert Types"
  • [TypeA] is configured with prompt "Community Alert" set to "Yes"
  • [TypeB] is configured with prompt "Community Alert" set to "No"
  • Have access to form "Client Alerts" to add alerts for a desired client [TestClient]
  • Have a report or query to display field data in the "SYSTEM.RADplus_client_alerts" table
Steps
  1. At the Home View, select [TestClient]
  2. Open the "Client Alerts" form.
  3. From the "Type of Alert" select alert type [TypeA]
  4. From the Episode field select a desired episode [EpisodeA]
  5. Populate the "Start Date" and "End Date" fields
  6. Submit the form
  7. Validate the form files successfully
  8. Re-open the "Client Alerts" form.
  9. From the "Type of Alert" select alert type [TypeB]
  10. From the Episode field select a desired episode [EpisodeA]
  11. Populate the "Start Date" and "End Date" fields
  12. Submit the form
  13. Validate the form files successfully
  14. Open the report or query defined in the set up for the "SYSTEM.RADplus_client_alerts" table
  15. Click to preview data
  16. Validate there are two rows of data for [TestClient], one for each alert submitted
  17. Validate the data displayed in each row, is consistent with the data populated for each alert in steps 2 and 3
Topics
• Client Alerts • SQL Data Access • Community Alert
Update 8 Summary | Details
IRIS/AWS - Servers
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
  • General / Avatar Licensing Graph
  • SMP IRIS
  • SMP IRIS - Home
  • SMP License Usage
Scenario 1: Guardiant Metric "Analytics" Data - Validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application
Steps
  1. Open form "Guardiant"
  2. Click [Test Daily Collection]
  3. Click [Yes] to the warning message
  4. Validate message "Test Succeeded" is displayed
  5. Click [Test Metrics Collection]
  6. Click [Yes] to the warning message
  7. Validate message "Test Succeeded" is displayed
  8. Log into "Guardiant"
  9. At the "Client Search", select the desired client account number
  10. In the right-hand corner, click "Analytics"
  11. Navigate down to "General/Avatar Licensing" graph
  12. In the right corner of the graph set the date range to the desired range, for example "60" days
  13. Click the 'Refresh' button in the graph
  14. In graph, mouse over the most recent date in the graph
  15. Validate the date and values displayed for the following statistics, are as expected
  16. Number of Named Users
  17. Number of application logins
  18. In graph, mouse over the oldest date in the graph
  19. Validate the date and values displayed for the following statistics, are as expected
  20. Number of Named Users
  21. Number of application logins
IRIS/AWS - Servers
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SMP IRIS
  • SMP IRIS - Home
  • SMP License Usage
  • License Usage
  • SoapUI - ClientDemographics - Request
  • SoapUI - ClientDemographics
Scenario 1: "Avatar Sessions" Widget - Column data validations
Specific Setup:
  • Have user [UserA] logged in who has the "Avatar Sessions" widget on their desktop.
  • Have another user [UserB] who has not logged in yet.
  • Have a third user [UserC] who has an ODBC connection created to connect to the testing system, that is configured using his UserID and password
  • [UserC] has a report created [ReportA], to display data in a table in the testing system, using his ODBC connection
Steps
  1. Log in as [UserA] and note the date and time of login
  2. Navigate to the "Avatar Sessions" widget
  3. Refresh the widget and note the current date and time
  4. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA].
  5. On a Netsmart hosted system
  6. Validate the "Login Date" and "Login Time" are consistent with time a date noted in step 1
  7. Validate the "Last Activity" date and time are consistent with the date and time noted in step 2a
  8. Note the current number of connections stated in the "# of Connections" column
  9. Launch any form
  10. Refresh the "Avatar Sessions" widget
  11. Validate the number of connections in the "# of Connections" column has incremented by 1
  12. Close the form just launched
  13. Validate the number of connections in the "# of Connections" column has decreased by 1
  14. Log in as [UserB] and note the current date and time.
  15. Navigate to the "Avatar Sessions" widget and refresh the widget
  16. Validate a row for both [UserA] and [UserB] are listed in the widget
  17. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA]
  18. Validate the "UserID" column of the widget includes the expected user ID associated with [UserB]
  19. Repeat step 2b for [UserB]
  20. Validate results are as expected
  21. As [UserC], Open [ReportA]
  22. Click to generate the report. Note the date and time
  23. Validate the report launches successfully
  24. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  25. Validate a row for both [UserA] and [UserB] are listed in the widget
  26. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserA]
  27. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserB]
  28. Validate a new row is present in the widget for [UserC]
  29. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserC].
  30. Note the number of connections in the "# of Connections" column
  31. As [UserC], close [ReportA]
  32. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  33. Validate the row for [UserC] is no longer present in the widget, as expected
  34. Validate the rows for [UserA] and [UserB] are still present
  35. As [UserB], Log out of Avatar
  36. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  37. Validate the row for [UserB] is no longer present in the widget, as expected
  38. Validate the row for [UserA] is present, as expected
Topics
• Guardiant • Cache • Widgets • Forms Designer • Query/Reporting
Update 9 Summary | Details
Bells Notes Integration - Progress Note document images
Scenario 1: Bells Notes Integration - Validate self approval of progress notes from Bells
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have 'Document Routing' enabled.
  • Must have a note type in Bells for the 'Progress Notes (Group and Individual)' form (Note Type A).
  • 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' and 'Progress Notes' widgets 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 "Note Type A".
  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. Validate a 'To-Do' is not displayed for the note sent via Bells Notes since "User A" does not require an approver.
  14. Select "Client A" and navigate to the 'Progress Notes' widget.
  15. Validate the progress note filed from Bells Notes is displayed.
  16. Access the 'Clinical Document Viewer' form.
  17. Select "Client" in the 'Select Type' field.
  18. Select "Individual" in the 'Select All or Individual Client' field.
  19. Select "Client A" in the 'Select Client' field.
  20. Select "All" in the 'Episode' field.
  21. Click [Process].
  22. Validate a document is displayed for the progress note filed from Bells Notes.
  23. Select the document and click [View].
  24. Validate the PDF generated from Bells Notes is displayed with the note details.
  25. Click [Close All Documents], [Search], and [Close].
'Envelope Import' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (CWS)
Scenario 1: Envelope Import - Validate importing 'Document Routing' enabled forms
Specific Setup:
  • Have an envelope (Envelope A) with a modeled form (Form A) that is enabled for document routing with the following prompts set in 'Document Routing Setup':
  • 'Skip Password Entry' set to "Yes"
  • 'Acknowledgement Allowed' set to "Yes"
  • Have an envelope (Envelope B) with a modeled form (Form B) that is enabled for document routing with the following prompts set in the 'Document Routing Setup' form:
  • 'Skip Password Entry' set to "No"
  • 'Acknowledgement Allowed' set to "No"
Steps
  1. Access the 'Envelope Export' form.
  2. Select "Envelope A".
  3. Select the desired value in the 'Include Form Designer Changes' field.
  4. Click [Begin Export].
  5. Validate the file is exported to the desired location.
  6. Close the form.
  7. Access the 'Envelope Import form.
  8. Click [Select Envelope Import File].
  9. Select the export file for "Envelope A".
  10. Select "Overwrite Existing".
  11. Select the desired value in the 'Load Un-Locked Dictionary Entries' field.
  12. Select the desired value in the 'Load Locked Dictionary Entries' field.
  13. Select the desired value in the 'Include Form Designer Changes' field.
  14. Click [Begin Import Scan].
  15. Validate the 'Import Scan Results' field does not contain errors.
  16. Click [Begin Import].
  17. Validate a message is displayed stating: Import Complete.
  18. Click [OK] and close the form.
  19. Access the 'Document Routing Setup' form.
  20. Click [Select Form].
  21. Select "Form A" and click [OK].
  22. Validate the 'Skip Password Entry' field is set to "Yes".
  23. Validate the 'Acknowledgement Allowed' field is set to "Yes".
  24. Close the form.
  25. Access the 'Envelope Export' form.
  26. Select "Envelope B".
  27. Select the desired value in the 'Include Form Designer Changes' field.
  28. Click [Begin Export].
  29. Validate the file is exported to the desired location.
  30. Close the form.
  31. Access the 'Envelope Import form.
  32. Click [Select Envelope Import File].
  33. Select the export file for "Envelope B".
  34. Select "Overwrite Existing".
  35. Select the desired value in the 'Load Un-Locked Dictionary Entries' field.
  36. Select the desired value in the 'Load Locked Dictionary Entries' field.
  37. Select the desired value in the 'Include Form Designer Changes' field.
  38. Click [Begin Import Scan].
  39. Validate the 'Import Scan Results' field does not contain errors.
  40. Click [Begin Import].
  41. Validate a message is displayed stating: Import Complete.
  42. Click [OK] and close the form.
  43. Access the 'Document Routing Setup' form.
  44. Click [Select Form].
  45. Select "Form B" and click [OK].
  46. Validate the 'Skip Password Entry' field is set to "No".
  47. Validate the 'Acknowledgement Allowed' field is set to "No".
  48. Close the form.
Scenario 2: Envelope Export/Import - Validations
Specific Setup:
  • Must have an envelope available for export (Envelope A).
Steps
  1. Access the 'Envelope Export' form.
  2. Select "Envelope A".
  3. Select the desired value in the 'Include Form Designer Changes' field.
  4. Click [Begin Export].
  5. Validate the file is exported to the desired location.
  6. Close the form.
  7. Access the 'Envelope Import form.
  8. Click [Select Envelope Import File].
  9. Select the export file for "Envelope A".
  10. Select "Overwrite Existing".
  11. Select the desired value in the 'Load Un-Locked Dictionary Entries' field.
  12. Select the desired value in the 'Load Locked Dictionary Entries' field.
  13. Select the desired value in the 'Include Form Designer Changes' field.
  14. Click [Begin Import Scan].
  15. Validate the 'Import Scan Results' field does not contain errors.
  16. Click [Begin Import].
  17. Validate a message is displayed stating: Import Complete.
  18. Click [OK] and close the form.
  19. Access the 'Envelope Definition' form.
  20. Select "Envelope A".
  21. Validate the envelope details are displayed as expected.
  22. Close the form.
Scenario 3: Envelope Export/Import - Validations
Specific Setup:
  • Must have an envelope available for export (Envelope A).
Steps
  1. Access the 'Envelope Export' form.
  2. Select "Envelope A".
  3. Select the desired value in the 'Include Form Designer Changes' field.
  4. Click [Begin Export].
  5. Validate the file is exported to the desired location.
  6. Close the form.
  7. Access the 'Envelope Import form.
  8. Click [Select Envelope Import File].
  9. Select the export file for "Envelope A".
  10. Select "Overwrite Existing".
  11. Select the desired value in the 'Load Un-Locked Dictionary Entries' field.
  12. Select the desired value in the 'Load Locked Dictionary Entries' field.
  13. Select the desired value in the 'Include Form Designer Changes' field.
  14. Click [Begin Import Scan].
  15. Validate the 'Import Scan Results' field does not contain errors.
  16. Click [Begin Import].
  17. Validate a message is displayed stating: Import Complete.
  18. Click [OK] and close the form.
  19. Access the 'Envelope Definition' form.
  20. Select "Envelope A".
  21. Validate the envelope details are displayed as expected.
  22. Close the form.
Rule Based Routing - 'DocR.rule_based_routing' SQL table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Rule Based Routing
  • Routing Admin Dashboard
Scenario 1: Rule-Based Routing - Validate the 'DocR.rule_based_routing' SQL table
Specific Setup:
  • Rule-Based Routing must be configured.
  • The 'Ambulatory Progress Notes' form must be selected in the 'Routing Configuration Definition' form.
  • A client is enrolled in an existing episode.
  • Two users must be defined (User A & User B).
  • The users must have the 'My To Do's' and 'Rule Based Routing' widgets accessible.
  • Must be logged in as "User A" initially.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  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'.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate a "Confirm Document" dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password associated to "User A" and click [OK].
  10. Select "User B" as an approver and click [Submit].
  11. Log out.
  12. Log in as "User B".
  13. Navigate to the 'My To Do's' widget.
  14. Validate a To Do is displayed for "Client A".
  15. Click [Review].
  16. Validate the document is displayed.
  17. Accept and sign off on the document.
  18. Validate the To Do is no longer displayed.
  19. Navigate to the 'Rule Based Routing' widget.
  20. Select the corresponding value in the 'Queue' field.
  21. Validate an item is displayed for "Client A" as expected.
  22. Access Crystal Reports or other SQL Reporting Tool.
  23. Create a report using the 'DocR.rule_based_routing' SQL table.
  24. Validate a row is displayed with the data filed for "Client A" as expected.
  25. Close the report.
Topics
• Progress Notes • CareFabric • Bells Notes • Document Routing • Envelope Import • Envelope Export • Modeling • NX • Query/Reporting • Rule Based Routing
Update 10 Summary | Details
Rule Based Routing widget - performance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Rule Based Routing widget
  • Rule Based Routing
  • Routing Worklist Item
Scenario 1: 'Rule Based Routing' widget - Submission and form data validations
Specific Setup:
  • Have a system enabled for "Rule Based Routing"
  • Modeled form [TestForm] exists and has various field types on the form.
  • In form 'Routing Role Assignment', a role is defined [TestRole] and [TestUser] has been assigned to the role
  • In form "Routing Queue Definition", [TestForm] has been assigned to a rule based routing queue [TestQueue]. (Note: When a row launched from the via "Launch Worklist Item" in the widget, this is the form that will be populated and submitted).
  • In form "Routing Configuration Definition", a desired form that is enabled for document routing, has been selected in the "Initial Assignment" field
  • Several rows has been submitted in that form and routed to [TestUser], who has approved the document(s)
  • [TestUser] has the "Rule Based Routing" widget on their home view
Steps
  1. Locate the 'Rule Based Routing' widget.
  2. Select the queue [TestQueue] identified in the setup section
  3. Validate data rows are loaded and in a timely manner
  4. Select a row and click "Launch Worklist Item"
  5. Validate the "Routing Worklist Item" screen is loaded and contains [TestForm] and its expected field, for data entry
  6. For each field on the form, enter a value
  7. Click [File button].
  8. Validate when applicable, that an error dialog is displayed indicating fields where an incorrect value was entered.
  9. Populate each field indicated with a valid value
  10. Click the [File Button]
  11. Validate the form submits successfully and in a timely manner
  12. Validate the 'Rule Based Routing' widget refreshes in a timely manner
  13. Validate data rows are loaded, as expected
  14. Open form [TestForm]
  15. Select the row just submitted in the widget
  16. Validate all fields are populated, as expected
Rule Based Routing Widget - filing validation logic
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Rule Based Routing widget
  • Rule Based Routing
  • Routing Worklist Item
  • Order Fulfillment Widget
  • Order Entry Console
  • POC Results Entry
Scenario 1: Order Fulfillment widget - "Require Fulfillment" modeled form field validations
Specific Setup:
  • Have CWS Modeled form [TestForm], that contains various different field types.
  • Have an order code set up in 'Order Code Setup', that has the 'Require Fulfillment' set to "Yes" and [TestForm] selected in the "Fulfillment Form" field
  • The 'Order Fulfillment' widget and "Orders" widget exist on the logged in users home view
Steps
  1. Select a client [TestClient] and navigate the "Order" widget
  2. Search for the order code you defined in the 'New Order' field.
  3. Fill out the required fields and click 'Add to Scratchpad', then 'click Sign'.
  4. Validate a row for the order [TestOrder] is displayed in the widget
  5. Return to your homeview and
  6. Refresh the 'Order Fulfillment' widget.
  7. Validate the widget contains a row for the order entered in step 1
  8. Select the row and click 'Fulfill Order'.
  9. Validate [TestForm] is open
  10. For each field on the form enter a value
  11. Click [File button].
  12. Validate when applicable, that an error dialog is displayed indicating fields where an incorrect value was entered.
  13. Populate each field indicated with a valid value
  14. Click the [File Button]
  15. Validate the form submits successfully
  16. Select client [TestClient]
  17. Open form [TestForm]
  18. Validate the row submitted in the widget in step 2, is present
  19. Select the row
  20. Validate all fields are populated as expected
Scenario 2: POC Results Entry - "Associated Form" modeled form field validations
Specific Setup:
  • Have a non episodic modeled form [TestForm], in application "CWS" that contains a variety of columns types, as well as a multiple iteration section.
  • In Order Code setup have "Lab" type order code created [TestCode]
  • Have a client [TestClient] with an active order [TestOrder] that uses [TestCode]
  • In form 'POC Results Entry Configuration'
  • On the 'Observation Definition' section, add a new definition [TestDef] and fill out the required fields
  • On the 'Test Definition' page, add a new test
  • In the 'Associated Form', select [TestForm]
  • Submit the form
  • Have the eMAR widget to your homeview.
Steps
  1. Select [TestClient]
  2. Navigate to the "Emar" widget
  3. Validate the order displays in the 'Lab Orders' tab
  4. Select the order in the widget and click 'Administer'.
  5. Fill out the required fields and click [OK]
  6. Open the 'POC Results Entry' form.
  7. Select [TestOrder] from the 'Order' dropdown.
  8. Validate the collection data is populated
  9. Validate the [TestForm] displays in another window.
  10. Fill out all the fields on the modeled form, including the multiple iteration row, and submit.the form
  11. Validate when applicable, that an error dialog is displayed indicating fields where an incorrect value was entered.
  12. Populate each field indicated with a valid value
  13. Click the [File Button]
  14. Validate the form submits successfully
  15. Reopen the 'POC Results Entry' form
  16. Select [TestOrder].
  17. Validate the collection is not automatically loaded (as it was already submitted)
  18. Change 'Include Resulted Collections' to 'Yes'.
  19. Validate the collection load with the values submitted in step 1.
  20. Edit some field values
  21. Submit the form
  22. Reopen the 'POC Results Entry' form
  23. Select [TestOrder].
  24. Select the collection again.
  25. Validate the changes you made in step 3 are displayed as expected.
Topics
• Rule Based Routing • Order Fulfillment
Update 11 Summary | Details
OE - External Lab Definition - Order Code Setup - Lab Vendor Name with apostrophe
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • External Lab/Radiology Definition for CareConnect
  • Order Code Setup
  • Order Group Setup
Scenario 1: OE NX - Order Code Setup - External Lab Definition - Lab Vendor Name with apostrophe
Specific Setup:
  • A lab vendor must be configured in the 'External Lab/Radiology Definition for CareConnect' form where the 'Lab Vendor Name' contains an apostrophe. (Lab Vendor A).
  • A lab-type order code must exist that has the 'External Lab Definition' configured with "Lab Vendor A". (Lab Code A).
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Access the 'Order Code Setup' form.
  2. Search for and select a lab-type order code.
  3. Click [External Lab Definition].
  4. Validate the 'External Lab Definition' dialog is displayed.
  5. Select "Lab Vendor A" in the 'Lab Vendor Name' cell.
  6. Populate all other required fields and click [Save] and file the form.
  7. Select "Client A" and access the Order Entry Console.
  8. Search for and select "Lab Code A" in the 'New Order' field.
  9. Populate all required fields.
  10. Validate the 'External Lab Vendor Destination' field contains "Lab Vendor A".
  11. Click [Add to Scratchpad] and [Sign].
  12. Validate the 'Order grid' contains a new order.
Topics
• Order Entry Console • NX
Update 12 Summary | Details
'Clinical Document Viewer' form
Scenario 1: Clinical Document Viewer - View documents for "All" clients
Specific Setup:
  • The logged in user must be configured as a supervisor to a user with a high volume of client's in their caseload.
  • Must have a high volume of documents on file.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "All" in the 'Select All or Individual Client' field.
  3. Click [Process].
  4. Validate the documents are displayed in a timely manner.
  5. Scroll to the desired document from the search results table.
  6. Select the desired document in the 'Search Results' field.
  7. Click to view the document.
  8. Validate document data is displayed as expected.
  9. Click [Close All Documents].
  10. Navigate back to the "Search" section.
  11. Click [Close].
Scenario 2: Clinical Document Viewer - View documents for an individual client
Specific Setup:
  • The logged in user must be configured as a supervisor for a user with a high volume of client's in their caseload.
  • A client must have a high volume of documents on file (Client A).
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. Select "All" in the 'Episode' field.
  5. Click [Process].
  6. Validate the documents are displayed in a timely manner.
  7. Select the desired document in the 'Search Results' field.
  8. Click to view the document.
  9. Validate document data is displayed.
  10. Click [Close All Documents].
  11. Navigate back to the "Search" section.
  12. Click [Close].
Topics
• Clinical Document Viewer
Update 13 Summary | Details
Avatar NX - To Do notifications
Scenario 1: Avatar NX Login - Validate 'Workflow Management' notifications
Specific Setup:
  • Please note: this test is for Avatar NX only.
  • Two views must be defined (View A & View B):
  • "View A" does not have the 'My To Do's' widget assigned.
  • "View B" has the 'My To Do's' widget assigned.
  • The logged in user must have To Do's pending in the 'My To Do's' widget (User A).
  • "User A" must have "View B" as their 'HomeView' in the 'User Definition' form.
Steps
  1. Access the 'NX View Definition' form.
  2. Select "User" in the 'User or Role' field.
  3. Select "User A" in the 'Select User' field.
  4. Select "View A" in the 'myDay' field. This view does not have the 'My To Do's' widget associated.
  5. Click [File].
  6. Log out.
  7. Login to Avatar NX as "User A".
  8. Validate a 'Workflow Management' dialog is displayed stating: There are one or more open items within your Workflow Management To Do List.
  9. Click [OK].
  10. Validate the 'My To Do's' widget is not present on the myDay view.
  11. Access the 'NX View Definition' form.
  12. Select "User" in the 'User or Role' field.
  13. Select "User A" in the 'Select User' field.
  14. Select "View B" in the 'myDay' field. This view has the 'My To Do's' widget associated.
  15. Click [File].
  16. Log out.
  17. Login to Avatar NX as "User A".
  18. Validate no 'Workflow Management' dialog is displayed, since the 'My To Do's' widget is present on the myDay view.
'Template On Demand' widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Widget Import (PM)
Scenario 1: Validate 'Template On Demand' widgets in scrolling free text fields
Specific Setup:
  • Please note: this test is for Avatar NX systems only.
  • The 'Enable Templates On Demand for SQL Widgets' registry setting must be set to "Y".
  • Must have a widget with "Yes" selected in the 'Use for Templates On Demand' field in 'Widget Definition' (Widget A).
  • Two views must be defined (View A & View B).
  • "Widget A" must be assigned to "View A" but is not assigned to "View B".
  • The logged in user (User A) must have the following:
  • "View A" assigned as their myDay view in the 'NX View Definition' form.
  • "View B" assigned as their HomeView in the 'User Definition' form.
  • A client is enrolled in an existing episode (Client A).
  • This client must also have data on file that will populate in "Widget A".
Steps
  1. Log into Avatar NX as "User A".
  2. Validate "Widget A" is present on the myDay view.
  3. Access the 'Progress Notes (Group and Individual)' form.
  4. Select "Client A" in the 'Select Client' field.
  5. Select the desired episode in the 'Select Episode' field.
  6. Select "Independent Note" in the 'Progress Note For' field.
  7. Select the desired value in the 'Note Type' field.
  8. Click on the [Template Icon] in the 'Notes Field'.
  9. Click [Widget Templates] and [Templates].
  10. Validate "Widget A" is available for selection and select it.
  11. Validate the 'Notes Field' populates with the data on file for the client accordingly.
  12. Populate any other required and desired fields.
  13. File the note.
The 'SYSTEM.RADplus_users' and 'SYSTEM.RADplus_user_roles' SQL tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: Query SQL Tables - SYSTEM.RADplus_users and SYSTEM.RADplus_user_roles
Specific Setup:
  • Have an Avatar system that has an "ECP" server configured by Netsmart Representative in order to connect to the Avatar server via the "ECP" server for reporting.
  • Various users and user roles are defined.
Steps
  1. Access Crystal Reports or other SQL Reporting Tool.
  2. Create a report using the 'SYSTEM.RADplus_users' SQL table.
  3. Validate the report displays in a timely manner and contains the users defined in the system.
  4. Close the report.
  5. Create a report using the 'SYSTEM.RADplus_roles' SQL table.
  6. Validate the report displays in a timely manner and contains the user roles defined in the system.
  7. Close the report.
Topics
• NX View Definition • My To Do's • Progress Notes • Widgets • User Role Definition • Query/Reporting
Update 14 Summary | Details
The 'Limit Wait Time for Dynamic Message Box' Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Billing
Scenario 1: Basic Troubleshooting - testing dynamic forms
Specific Setup:
  • The user must have access to the 'Basic Troubleshooting' form.
  • The 'Limit Wait Time for Dynamic Message Box' registry setting must be set to "60;2".
Steps
  1. Access the 'Basic Troubleshooting' form.
  2. Validate the form displays as expected.
  3. Click [Test Dynamic Forms].
  4. Validate a 'Dynamic Form Test' message displays stating: "Test Successful".
  5. Wait for 60 seconds and validate the message refreshes and appears again on the form.
  6. Wait for another 60 seconds and validate the message no longer displays after the second appearance.
  7. Click [Discard].
Topics
• Treatment Plan • Quick Billing
Update 15 Summary | Details
'All Documents' widget - Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Append Progress Notes
  • All Documents Widget Definition
  • CONSOLE WIDGET VIEWER widget
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  14. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  15. Select the progress note for viewing.
  16. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  17. Validate an [Append] button is displayed and click it.
  18. Validate the 'Append Progress Notes' form is displayed.
  19. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  20. Click [Submit].
  21. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  22. Click [Accept].
  23. Enter the password associated with the logged in user and click [Verify].
  24. Click [Close All] in the 'Console Widget Viewer'.
  25. Refresh the 'All Documents' widget.
  26. Select the progress note appended in the previous steps for viewing.
  27. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  28. Click [Close All].
Topics
• All Documents Widget
Update 16 Summary | Details
Document Capture - Allow full text of the Episode field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Document Capture
Scenario 1: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 2: Validate Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be installed and enabled.
Steps
  1. Select a client from "myClients" or from the Client search.
  2. Open the client's dashboard.
  3. Using "Document Capture", scan or import in a document.
  4. Select the desired episode to assign the document to.
  5. Validate the correct Episode displays in the "Document Properties" pane.
  6. Capture and save the document.
  7. View the document using "Clinical Document Viewer" or the Chart to ensure it has the correct episode designation and that it displays.
Scenario 3: Validate Document Capture - Import Non-Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
  • Please note: this is for Avatar NX systems only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Select "Client A" and launch the 'Client Dashboard'.
  2. Click 'Document Capture' icon.
  3. Validate a 'Capture Mode' dialog stating: 'How would you like to capture documents?'
  4. Click [Import].
  5. Select 'Non-episodic' in the 'Episode' field.
  6. Validate the 'Document Capture' opens in a new window.
  7. Select any value in the 'Document Type' field.
  8. Enter any value in the 'Document Description' field.
  9. Click [Capture] and [Browse].
  10. Locate the file to be imported and click [Open] and [Done].
  11. Validate the image displays.
  12. Click [Save].
  13. Validate a message stating: 'Save Was Successful.' and 'Document Added to Avatar!'
  14. Click [Close Document Capture].
  15. Close the 'Client Dashboard'.
  16. Navigate to the 'All Documents' view.
  17. Validate the newly imported non-episodic document is present and select it.
  18. Validate the 'Console Widget Viewer' displays the document as expected.
  19. Click [Close All].
  20. Validate the 'Console Widget Viewer' no longer displays the document.
  21. Click 'Document Capture' icon.
  22. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  23. Click [Import].
  24. Select 'Non-episodic' in the 'Episode' field.
  25. Validate the 'Document Capture' opens in a new window.
  26. Click [Close all open forms].
  27. Validate the 'Document Capture' form is closed as expected.
Scenario 4: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: 'Save Was Successful.' and 'Document Added to Avatar!'
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select 'Individual' in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 5: Chart - Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Topics
• Perceptive
Update 17 Summary | Details
Support for Waiting Room functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Spreadsheet Edit Service Information
  • Appointment Management
  • Client Ledger
  • Walk-in Clinic Registration/Waiting Room
  • Walk-in Clinic/Waiting Room
  • Financial Eligibility
Scenario 1: Waiting Room - Place Client in Context
Specific Setup:
  • Please note: this is for Avatar NX systems only. Avatar Appointment Scheduling 2023 Update 34, RADplus 2024 Update 17 and Avatar NX Release 2024.01.00 are required for full functionality.
  • The 'Enable Clinic Scheduling' registry setting must be set to "Y".
  • The 'Walk-in Clinic Registration/Waiting Room' widget must be accessible on the user's myDay view.
  • A site is defined with time slots for clinic hours in 'Site Registration' (Site A), (Time Slot A).
  • Two clients are enrolled in existing episodes (Client A & Client B).
Steps
  1. Navigate to the 'Walk-in Clinic Registration/Waiting Room' widget.
  2. Select "Site A" in the 'Waiting Room/Site' field.
  3. Select "Client A" in the 'Add Client' field.
  4. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  5. Populate any other desired fields.
  6. Click [Add To Waitlist].
  7. Validate a message is displayed stating: Saved.
  8. Click [OK].
  9. Validate "Client A" is displayed in the Waiting Room.
  10. Click on the name for "Client A".
  11. Validate "Client A" is now in context and selected in the 'My Clients' list.
  12. Access the 'Update Client Data' form.
  13. Validate the form is displayed for "Client A".
  14. Close the form and clear the client.
  15. Select "Client B" in the 'Add Client' field.
  16. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  17. Populate any other desired fields.
  18. Click [Add To Waitlist].
  19. Validate a message is displayed stating: Saved.
  20. Click [OK].
  21. Validate "Client B" is now displayed in the Waiting Room.
  22. Navigate to the Staff View 'Walk-in Clinic/Waiting Room' widget.
  23. Validate "Client A" and "Client B" are displayed.
  24. Click on the name for "Client B".
  25. Validate "Client B" is now in context and selected in the 'My Clients' list.
  26. Access the 'Update Client Data' form.
  27. Validate the form is displayed for "Client B".
  28. Close the form and clear the client.
Scenario 2: Waiting Room - Validate Client Information Flyover
Specific Setup:
  • Please note: this is for Avatar NX systems only. Avatar Appointment Scheduling 2023 Update 34, RADplus 2024 Update 17, Avatar NX Release 2024.01.00, and Avatar NX Release 2024.02.00 are required for full functionality.
  • The 'Enable Clinic Scheduling' registry setting must be set to "Y".
  • The 'Walk-in Clinic Registration/Waiting Room' widget must be accessible on the user's myDay view.
  • A site is defined with time slots for clinic hours in 'Site Registration' (Site A), (Time Slot A).
  • A client is enrolled in an existing episode and has the following on file (Client A):
  • Date Of Birth
  • Primary Diagnosis
  • Primary Guarantor
Steps
  1. Navigate to the 'Walk-in Clinic Registration/Waiting Room' widget.
  2. Select "Site A" in the 'Waiting Room Site' field.
  3. Select the desired value in the 'Time Slot' field.
  4. Select "Client A" in the 'Add Client' field.
  5. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  6. Click [Add to Waitlist] and [OK].
  7. Validate the client is added to the Waitlist.
  8. Hover over "Client A".
  9. Validate a client information flyover is displayed with the following:
  10. Name
  11. Date Of Birth
  12. Age
  13. Primary Diagnosis
  14. Primary Guarantor
  15. Click on "Client A".
  16. Validate the client information flyover is now locked into place.
  17. Click [X] to close the flyover.
  18. Select "Add to Calendar" in the 'Action' field for "Client A".
  19. Click [Yes].
  20. Validate the 'Scheduling Calendar - Appointment Details' form is displayed.
  21. Populate all required and desired fields for the appointment.
  22. Click [Submit].
  23. Validate the 'Walk-in Clinic Registration/Waiting Room' widget is displayed.
  24. Hover over "Client A".
  25. Validate a client information flyover is displayed with the following:
  26. Name
  27. Date Of Birth
  28. Age
  29. Primary Diagnosis
  30. Primary Guarantor
  31. Appointment Details
  32. Click on "Client A".
  33. Validate the client information flyover is now locked into place.
  34. Click [X] to close the flyover.
  35. Navigate to the Staff 'Walk-in Clinic/Waiting Room' widget.
  36. Validate "Client A" is displayed in the Waitlist.
  37. Hover over "Client A".
  38. Validate a client information flyover is displayed with the following:
  39. Name
  40. Date Of Birth
  41. Age
  42. Primary Diagnosis
  43. Primary Guarantor
  44. Appointment Details
  45. Click on "Client A".
  46. Validate the client information flyover is now locked into place.
  47. Click [X] to close the flyover.
Topics
• NX • Waiting Room
Update 18 Summary | Details
Form Definition - Service Documentation forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
  • Table Definition (CWS)
  • Form Definition (CWS)
  • Copy Form to Different System Code (CWS)
Scenario 1: Service Documentation Notes form creation
Specific Setup:
  • Multiple root system codes are defined (System Code A & System Code B).
  • Must be logged in with "System Code A".
  • An envelope must be defined in the 'Envelope Definition' CWS form (Envelope A).
  • A CWS table must be defined (Table A) associated to "Envelope A" with the following table columns:
  • 'Progress Note For' - Single Select Dictionary
  • 'Note Addresses Which Existing Service/Appointment' - Single Select Dictionary
  • 'Service Program' - Single Select Dictionary
  • 'Service Practitioner' - Staff Lookup
  • 'Service Date' - Date
  • This table must have "Yes" selected in the 'Service Documentation Table' field.
  • The above table columns must be mapped to the respective Progress Note prompts in the 'Service Documentation' section of the 'Table Definition' form.
  • A CWS form must be defined (Form A) associated to "Envelope A" and "Table A" that does not yet have the 'Service Documentation' table columns added to the form.
  • The logged in user must have access to "Form A".
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Copy Form to Different System Code' CWS form.
  2. Select "Form A" in the 'Select Form' dialog and click [OK].
  3. Enter "System Code B" in the 'Target System Code' field.
  4. Enter the desired user in the 'Target System Username' field.
  5. Enter the password for the user in the 'Target System Password' field.
  6. Select the desired value in the 'Target System Menu to Place Form Under' field.
  7. Select the desired value in the 'Copy unlocked dictionary values' field.
  8. Populate any other desired fields.
  9. Submit the form.
  10. Access the 'Form Definition' CWS form for "Form A".
  11. Navigate to the "Object Def." section.
  12. Click [Add New Item].
  13. Add the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns.
  14. Populate any required and desired fields.
  15. Submit the form.
  16. Access the 'Form Definition' CWS form for "Form A".
  17. Navigate to the "Object Def." section.
  18. Validate the 'Progress Notes For' and 'Note Addresses Which Existing Service/Appointment' table columns added in the previous steps are displayed.
  19. Click [Add New Item].
  20. Add the 'Service Program', 'Service Date', and 'Service Practitioner' table columns.
  21. Populate any other required and desired fields.
  22. Submit the form.
  23. Select "Client A" and access "Form A".
  24. Validate the form displays as expected with the following fields:
  25. 'Progress Notes For'
  26. 'Note Addresses Which Existing Service/Appointment'
  27. 'Service Program'
  28. 'Service Date'
  29. 'Service Practitioner'
  30. File a new service for the client.
  31. Verify successful submission.
  32. Access Crystal Reports or other SQL Reporting Tool.
  33. Create a report using the 'SYSTEM.billing_tx_history' SQL table.
  34. Validate a row is displayed for "Client A" for the service created via "Form A".
  35. Close the report.
Envelope Import with Form Designer changes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
Scenario 1: Envelope Export/Import - 'Include Form Design Changes' in the file set to "Y"
Specific Setup:
  • Have a modeled form (Form A), contained in (Envelope A), that will be used to make form designer changes.
  • "Form A" must have a primary/secondary table and a multi-iteration table associated.
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" from the 'Forms' field.
  3. Make any type of form designer change in the section [FDchange1]. For example, a field is moved to different location.
  4. Save the changes and exit the form.
  5. Access the 'Envelope Export' form.
  6. Select "Envelope A".
  7. In the "Include Form Design Changes? field, select "Yes".
  8. Click [Begin Export].
  9. Validate export is completed successfully (Export A).
  10. Access the 'Form Designer' form.
  11. Select "Form A" from the 'Forms' field.
  12. Make another form designer change in the section [FDchange2].
  13. Save the changes and exit the form.
  14. Access "Form A".
  15. Validate [FDchange1] and [FDchange2] are both present in the form.
  16. Access the 'Envelope Import' form.
  17. Click [Select Envelope For Import].
  18. Navigate the location "Export A".
  19. Select the file and select "Overwrite Existing".
  20. In the "Include Form Design Changes? field, select "Yes". [Note: "Yes" implies that any form designer changes contained in the import file, 'will' be imported and/or overwrite any existing changes already made on the form].
  21. Click [Begin Import Scan].
  22. Validate there are no errors/warnings found within the import file scan results.
  23. Click [Begin Import].
  24. Validate import is completed successfully.
  25. Access "Form A".
  26. Validate [FDchange1] is present on the form.
  27. Validate [FDchange2] is not present on the form.
  28. Close the form.
Topics
• Service Documentation • Envelope Import • Form Designer • Envelope Export
Update 19 Summary | Details
Delete Document - 'Display Document' button
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Document
  • Append Progress Notes
Scenario 1: Validate the functionality of the form "Delete Document"
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document.
Steps
  1. Open form "Delete Document":
  2. Select "Client" in the "Entity Type" field.
  3. Select "Individual" in the "Include" field.
  4. In the "Entity" field, select the client that has the document.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Click the "Select Form" drop down list.
  10. Select the row pertaining to the clients document.
  11. Click [Delete].
  12. Click [Yes], confirming the deletion.
  13. Open form "Clinical Document Viewer":
  14. Select "Individual" from the "Select All or Individual Client" field,
  15. In the "Select Client" field, select a client that had the document,
  16. Select the episode in the "Episode" field,
  17. Click [Process],
  18. Validate the row with the document that was deleted, is not present.
  19. Open the form originally used to create the deleted document:
  20. Select the row originally used to submit the document,
  21. Validate the row has been reverted to "Draft" status.
Scenario 2: Delete Document - Validate form functionality
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document (Client A).
Steps
  1. Access the 'Delete Document' form.
  2. Select "Client" in the 'Entity Type' field.
  3. Select "Individual" in the 'Include' field.
  4. Select "Client A" in the 'Entity' field.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Select the desired form in the 'Select Form' field.
  10. Validate the 'Display Document' button is displayed.
  11. Click [Display Document].
  12. Validate the document displays as expected.
  13. Click [Close All Documents and Exit].
  14. Click [Delete].
  15. Click [Yes], confirming the deletion.
  16. Access the 'Clinical Document Viewer' form.
  17. Select "Individual" in the 'Select All or Individual Client' field,
  18. Select "Client A" in the 'Select Client' field.
  19. Select the episode in the 'Episode' field.
  20. Click [Process].
  21. Validate the deleted document is not present.
  22. Close the form.
Scenario 3: Delete Document - User with access to confidential notes
Specific Setup:
  • The 'RADplus->System Security->User Definition->->->Enable View Confidential Notes' registry setting is set to "Y".
  • The following must be configured for the 'Progress Notes (Group and Individual)' form:
  • In 'Site Specific Section Modeling' - A single select dictionary with "Confidential Notes Logic" selected in the 'Product Custom Logic Definition' field. This field will be named 'Is this a confidential note?'.
  • Yes/No dictionary values should also be configured for this field which can be done in 'Dictionary Update'.
  • Document routing is enabled in 'Document Routing Setup'.
  • The logged in user has access to confidential notes in 'User Definition' (User A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the Progress Notes (Groups and Individual)' form.
  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 "Yes" in the 'Is this a confidential note?' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password associated to the logged in user and click [Verify].
  11. Access 'Delete Document' form.
  12. Select "Client" in the 'Entity Type' field.
  13. Select "Individual" in the 'Include' field.
  14. Select "Client A" in the 'Entity Search' field.
  15. Select the desired episode in the 'Episode' field.
  16. Click [Form Search].
  17. Select the corresponding form type and click [OK].
  18. Select the record filed in the previous steps in the 'Select Form' field.
  19. Click [Display Document].
  20. Validate the document details are displayed. User can select/view the document since they have access to confidential notes.
  21. Click [Close All Documents] and [Delete].
  22. Validate a message is displayed stating: Are you sure you want to delete this document?
  23. Click [Yes].
  24. Select "Client" in the 'Entity Type' field.
  25. Select "Individual" in the 'Include' field.
  26. Select "Client A" in the 'Entity Search' field.
  27. Select the desired episode in the 'Episode' field.
  28. Click [Form Search].
  29. Select the corresponding form type and click [OK].
  30. Validate the deleted record is no longer displayed.
  31. Close the form.
Scenario 4: Delete Document - User without access to confidential notes
Specific Setup:
  • The 'RADplus->System Security->User Definition->->->Enable View Confidential Notes' registry setting is set to "Y".
  • The following must be configured for the 'Progress Notes (Group and Individual)' form:
  • In 'Site Specific Section Modeling' - A single select dictionary with "Confidential Notes Logic" selected in the 'Product Custom Logic Definition' field. This field will be named 'Is this a confidential note?'.
  • Yes/No dictionary values should also be configured for this field which can be done in 'Dictionary Update'.
  • Document routing is enabled in 'Document Routing Setup'.
  • The logged in user has access to confidential notes in 'User Definition' (User A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the Progress Notes (Groups and Individual)' form.
  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 "Yes" in the 'Is this a confidential note?' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password associated to the logged in user and click [Verify].
  11. Access the 'User Definition' form.
  12. Select "User A" in the 'Select User' field.
  13. Select the "Forms and Tables" section.
  14. Select "No" in the 'Allow User to View Confidential Notes' field.
  15. Submit the form.
  16. Access 'Delete Document' form.
  17. Select "Client" in the 'Entity Type' field.
  18. Select "Individual" in the 'Include' field.
  19. Select "Client A" in the 'Entity Search' field.
  20. Select the desired episode in the 'Episode' field.
  21. Click [Form Search].
  22. Select the corresponding form type and click [OK].
  23. Validate the document is not displayed since the user does not have access to confidential notes.
  24. Close the form.
Topics
• Documentation • Clinical Document Viewer • Delete Document
Update 20 Summary | Details
'Change User Role ID' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • Change User Role ID
Scenario 1: Validate adding a user in form 'User Definition'
Specific Setup:
  • The 'Supplemental' section of the 'User Definition' form is enabled. This can be done in the 'System Security Defaults' form.
Steps
  1. Access the 'User Definition' form.
  2. Enter the desired value in the 'User ID' field.
  3. Enter the desired value in the 'User Description' field.
  4. Populate all required and desired fields.
  5. Select the "Forms and Tables" section.
  6. Select "Telehealth" in the 'Netsmart Mobile App Access' field.
  7. Select the desired value in the 'Netsmart Mobile App User Role' field.
  8. Select the "Supplemental" section.
  9. Enter the desired value in the 'Organization Email Address' field. Note: this field becomes required when "Telehealth" is selected in the 'Netsmart Mobile App User Role' field.
  10. Click [Submit].
  11. Validate a "Netsmart Mobile App Access" message is displayed stating: Submitting the form will register the user for Telehealth appointments. Do you wish to continue?
  12. Click [Yes].
  13. Close the form.
Scenario 2: Change User Role ID
Specific Setup:
  • A user role is defined in 'User Role Definition' (User Role A).
  • This user role must be associated to a template in the 'Product Scrolling Free Text Templates' form.
Steps
  1. Access the 'Change User Role ID' form.
  2. Select "ROLETEST" in the 'User Role' field.
  3. Validate the 'Current User Role ID' field contains "ROLETEST".
  4. Enter "ROLETEST1" in the 'New User Role ID' field.
  5. Click [Submit].
  6. Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
  7. Click [No].
  8. Access the 'Change User Role ID' form.
  9. Select "ROLETEST1" in the 'User Role' field.
  10. Validate the 'Current User Role ID' field contains "ROLETEST1".
  11. Enter "roletest1" in the 'New User Role ID' field.
  12. Click [Submit].
  13. Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
  14. Click [No].
  15. Access the 'Change User Role ID' form.
  16. Select "roletest1" in the 'User Role' field.
  17. Validate the 'Current User Role ID' field contains "roletest1".
  18. Close the form.
Topics
• User Definition • User Role Definition • Change User Role Id
Update 22 Summary | Details
Crystal Report Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (CWS)
  • Ambulatory Progress Note
Scenario 1: Progress Notes (Group and Individual) - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • The 'Progress Notes (Group and Individual)' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Progress Notes (Group and Individual)' form using "Crystal Report 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'.
  6. Click [New Row] in the 'Treatment Plan Grid'.
  7. Select "Treatment Plan" in the 'Select T.P. Version' field.
  8. Click [View].
  9. Select the desired treatment plan item and click [Return].
  10. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  11. Click [Sign] for "Signature A" and enter the desired signature.
  12. Select "Final" in the 'Draft/Final' field.
  13. Click [File Note].
  14. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  15. Leave the form open.
  16. Access Crystal Reports or other SQL Reporting Tool.
  17. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  18. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  19. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  20. Close the report.
  21. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  22. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  23. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  24. Close the report.
  25. Navigate back to the 'Progress Notes (Group and Individual)' form.
  26. Click [Accept].
  27. Enter the password associated to the logged in user.
  28. Close the form.
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  33. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  34. Close the report.
  35. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  36. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  37. Close the report.
Scenario 2: Ambulatory Progress Notes - Validate 'Treatment Plan' Grid and Signature fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Ambulatory Progress Notes' form.
  • The 'Ambulatory Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for 'Ambulatory Progress Notes' (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Ambulatory Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  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'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  19. Close the report.
  20. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  21. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  22. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  23. Close the report.
  24. Navigate back to the 'Ambulatory Progress Notes' form.
  25. Click [Accept].
  26. Enter the password associated to the logged in user.
  27. Close the form.
  28. Select "Client A" and access the 'Progress Notes' widget.
  29. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  30. Access Crystal Reports or other SQL Reporting Tool.
  31. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  32. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  33. Close the report.
  34. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  35. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  36. Close the report.
Scenario 3: Inpatient Progress Notes - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Inpatient Progress Notes' form.
  • The 'Inpatient Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for Inpatient progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Inpatient Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  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'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  19. Close the report.
  20. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  21. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  22. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  23. Close the report.
  24. Navigate back to the ' InpatientProgress Notes ' form.
  25. Click [Accept].
  26. Close the form.
  27. Select "Client A" and access the 'Progress Notes' widget.
  28. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  29. Access Crystal Reports or other SQL Reporting Tool.
  30. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  31. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  32. Close the report.
  33. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  34. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  35. Close the report.
Topics
• Document Routing • Progress Notes • Query/Reporting
Update 23 Summary | Details
Connect/Disconnect Application Namespace
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Connect/Disconnect Application Namespace
  • Application Namespace Connections Validation
Scenario 1: Connect/Disconnect Application Namespace - Disconnect Database/then Reconnect with "CDR" Link 'enabled'
Specific Setup:
  • Have a system with a child namespace, for example "Avatar MSO", that is already connected to the parent namespace, for example "Avatar PM", via the "Connect/Disconnect Application Namespace" form
  • Have a report to display data in the "SYSTEM.radplus_error_log" table
Steps
  1. Open the "Connect/Disconnect Application Namespace" form:
  2. From the "Application" field, select the application noted in the setup
  3. In the "Connect or Disconnect" field, select:
  4. "Connect/Maintain Connection/Repair Connection".
  5. Submit the form (Note submission can take some time):
  6. Validate submission is successful.
  7. Close the form
  8. Run the report based on the "SYSTEM.radplus_error_log"
  9. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  10. Re-open the "Connect/Disconnect Application Namespace" form:
  11. From the "Application" field, select the application noted in the setup
  12. In the "Connect or Disconnect" field, select:
  13. "Connect/Maintain Connection/Repair Connection"
  14. In the "Clinical Data Repository (CDR) Link", select "No"
  15. Submit the form (Note submission can take some time):
  16. Validate submission is successful.
  17. Run the report based on the "SYSTEM.radplus_error_log"
  18. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  19. Open form "Applications Namespace Connection Validations":
  20. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  21. Validate there is a message stating "There are no Application/Namespace errors".
  22. Close the form.
Scenario 2: Connect/Disconnect Application Namespace - Disconnect Database/then Reconnect with "CDR" Link 'disabled'
Specific Setup:
  • Have a system with a child namespace, for example "Avatar MSO, that is already connected to the parent namespace, for example "Avatar PM", via the "Connect/Disconnect Application Namespace" form
  • Have a report to display data in the "SYSTEM.radplus_error_log' table
Steps
  1. Open the "Connect/Disconnect Application Namespace" form:
  2. From the "Application" field, select the application noted in the setup
  3. In the "Connect or Disconnect" field, select:
  4. "Connect/Maintain Connection/Repair Connection".
  5. Submit the form (Note submission can take some time):
  6. Validate submission is successful.
  7. Close the form
  8. Run the report based on the 'SYSTEM.radplus_error_log"
  9. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  10. Re-open the "Connect/Disconnect Application Namespace" form:
  11. From the "Application" field, select the application noted in the setup
  12. In the "Connect or Disconnect" field, select:
  13. "Connect/Maintain Connection/Repair Connection"
  14. In the "Clinical Data Repository (CDR) Link", select "Yes"
  15. Submit the form (Note submission can take some time):
  16. Validate submission is successful.
  17. Run the report based on the "SYSTEM.radplus_error_log"
  18. In the "Option Description" field, validate there are no rows listed for the "Connect/Disconnect Application Namespace" form:
  19. Open form "Applications Namespace Connection Validations":
  20. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  21. Validate there is a message stating "There are no Application/Namespace errors".
  22. Close the form.
"Service Documentation" enabled modeled forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
Scenario 1: Service Documentation - Validate 'Autosave' functionality (Registry setting "Default to Draft" set to "N")
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Open 'Form Definition' for the [TestForm] and set 'Form supports automatic backup' to 'Yes'.
  • Registry setting "RADplus->Modeling->Settings->Default To Draft" is set to "N"
  • An appointment [TestAppt] has been scheduled with a client [TestClient] in form "Appointment Scheduling"
  • An existing service exists for [TestClient]
Steps
  1. Open form [TestForm]
  2. Select [TestClient] in the client search field
  3. In the "Documentation For" selection field
  4. Select "Existing Appointment"
  5. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  6. Do not make a selection in the field
  7. Populate any other required or desired fields
  8. Click the "Backup Form" button to auto save your changes
  9. Validate a message is displayed on the form indicating the time of the backup.
  10. Close the form
  11. Reopen form [TestForm]
  12. Select [TestClient] in the client search field
  13. Validate "Restore/Delete Backup Data" screen is displayed
  14. Validate a row is displayed indicating there is an unsubmitted backup
  15. Click "Yes" to accept the backup
  16. Validate [TestForm] is loaded successfully
  17. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  18. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  19. Submit the form
  20. Validate the form submits successfully
  21. Re- open form [TestForm]
  22. Select [TestClient] in the client search field
  23. Select the row just submitted
  24. Validate the "Draft/Final" field has 'not' defaulted to "Draft" selected, as expected
  25. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  26. Repeat steps 1 thru 3 for [TestClient]
  27. Selecting the clients existing service in the "Documentation For" selection field and clicking the "Backup Form" button to auto save your changes
  28. Validate results are as expected
Scenario 2: Service Documentation - Validate 'Autosave' functionality (Registry setting "Default to Draft" set to "Y")
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Open 'Form Definition' for the [TestForm] and set 'Form supports automatic backup' to 'Yes'.
  • Registry setting "RADplus->Modeling->Settings->Default To Draft" is set to "Y"
  • An appointment [TestAppt] has been scheduled with a client [TestClient] in form "Appointment Scheduling"
  • An existing service exists for [TestClient]
Steps
  1. Open form [TestForm]
  2. Select [TestClient] in the client search field
  3. In the "Documentation For" selection field
  4. Select "Existing Appointment"
  5. Validate the "Draft/Final" field has defaulted with "Draft" selected, as expected
  6. Populate any other required or desired fields
  7. Click the "Backup Form" button to auto save your changes
  8. Validate a message is displayed on the form indicating the time of the backup
  9. Close the form
  10. Reopen form [TestForm]
  11. Select [TestClient] in the client search field
  12. Validate "Restore/Delete Backup Data" screen is displayed
  13. Validate a row is displayed indicating there is an unsubmitted backup
  14. Click "Yes" to accept the backup
  15. Validate [TestForm] is loaded
  16. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  17. Validate in the "Draft/Final" is set to "Draft", as expected
  18. Submit the form
  19. Validate the form submits successfully
  20. Re- open form [TestForm]
  21. Select [TestClient] in the client search field
  22. Select the row just submitted
  23. Validate all fields populated prior to backing up the form in step 1, are populated as expected
  24. Validate in the "Draft/Final" is set to "Draft", as expected
  25. Repeat steps 1 thru 3 for [TestClient]
  26. Selecting the clients existing service in the "Documentation For" selection field and clicking the "Backup Form" button to auto save your changes
  27. Validate results are as expected
ODBC connection requests
Internal Test Only
Topics
• Database Management • Auto Save • Service Documentation
Update 26 Summary | Details
Client Lookup/Header Configuration Manager - Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
Scenario 1: 'Client Lookup/Header Configuration Manager' - Validate Header Information
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has emergency contact information on file.
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Select the "Client Header" section.
  3. Click [Add New Item].
  4. Select "Clinical Pathway" in the 'Field to Include in Client Header' field.
  5. Select "Column 2, Position 4" in the 'Field Order' field.
  6. Click [Add New Item].
  7. Select "Emergency Contact Name" in the 'Field to Include in Client Header' field.
  8. Select "Column 3, Position 4" in the 'Field Order' field.
  9. Click [Add New Item].
  10. Select "Emergency Contact Phone" in the 'Field to Include in Client Header' field.
  11. Select "Column 3, Position 5" in the 'Field Order' field.
  12. Click [Submit].
  13. Select "Client A" and navigate to the 'Client Information' header.
  14. Validate the 'Client Information' header is displayed with any applicable details for "Client A".
  15. Validate the 'Emergency Contact' and 'Phone' fields are displayed in the third column, positions 4 and 5, as expected.
  16. Validate all other fields are displayed in their configured column/positions.
Scenario 2: 'Client Lookup/Header Configuration Manager' - Validate Header Information
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has emergency contact information on file.
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Select the "Client Header" section.
  3. Click [Add New Item].
  4. Select "Clinical Pathway" in the 'Field to Include in Client Header' field.
  5. Select "Column 2, Position 4" in the 'Field Order' field.
  6. Click [Add New Item].
  7. Select "Emergency Contact Name" in the 'Field to Include in Client Header' field.
  8. Select "Column 3, Position 4" in the 'Field Order' field.
  9. Click [Add New Item].
  10. Select "Emergency Contact Phone" in the 'Field to Include in Client Header' field.
  11. Select "Column 3, Position 5" in the 'Field Order' field.
  12. Click [Submit].
  13. Select "Client A" and navigate to the 'Client Information' header.
  14. Validate the 'Client Information' header is displayed with any applicable details for "Client A".
  15. Validate the 'Emergency Contact' and 'Phone' fields are displayed in the third column, positions 4 and 5, as expected.
  16. Validate all other fields are displayed in their configured column/positions.
Client Header - Problems
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Code Definition
Scenario 1: Problem List - validate Problem Classification sub-system code restrictions
Specific Setup:
  • A client is admitted into two episodes (Client A):
  • Episode 1 = Program A
  • Episode 2 = Program B
  • Two sub-system codes are defined in the 'System Code Definition' form:
  • "System Code A" has "Program A" selected in 'Associated Programs'.
  • "System Code B" has "Program B" selected in 'Associated Programs'.
  • Two problem classifications are defined for the '(16250) Problem Classification' CWS dictionary:
  • "Classification A" has both the root system code being used & "System Code A" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • "Classification B" has both the root system code being used & "System Code B" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • The 'Client Information' widget is accessible on the HomeView.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Validate the 'Problem List' grid is displayed.
  4. Click [New Row].
  5. Add a new problem. This will be referred to as "Problem A".
  6. Select "Classification A" in the 'Problem Classification' field.
  7. Select "Primary" in the 'Type' field.
  8. Select "Active" in the 'Status' field.
  9. Click [New Row].
  10. Add a new problem. This will be referred to as "Problem B".
  11. Select "Classification B" in the 'Problem Classification' field.
  12. Select "Primary" in the 'Type' field.
  13. Select "Active" in the 'Status' field.
  14. Click [Save], [Yes] and [Submit].
  15. Log out.
  16. Login using "System Code A".
  17. Select "Client A" and access the 'Problem List' form.
  18. Click [View/Enter Problems].
  19. Validate only "Problem A" is displayed.
  20. Click [Close/Cancel] and close the form.
  21. Select "Client A" and navigate to the 'Client Information' widget.
  22. Validate "Problem A" is displayed in the 'Problem' section.
  23. Log out.
  24. Login using "System Code B".
  25. Select "Client A" and access the 'Problem List' form.
  26. Click [View/Enter Problems].
  27. Validate only "Problem B" is displayed.
  28. Click [Close/Cancel] and close the form.
  29. Select "Client A" and navigate to the 'Client Information' widget.
  30. Validate "Problem B" is displayed in the 'Problem' section.
Topics
• Client Header • NX • Sub-System Code • Problem List
Update 27 Summary | Details
Observer NX - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Network Connectivity
Scenario 1: Observer NX - Validate filtering client list
Steps

Internal Testing Only.
Topics
n/a
Update 28 Summary | Details
Avatar NX - Widget Buttons on Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
  • Individual Progress Note
Scenario 1: 'Client Lookup/Header Configuration Manager' - Validate Header Information
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has emergency contact information on file.
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Select the "Client Header" section.
  3. Click [Add New Item].
  4. Select "Clinical Pathway" in the 'Field to Include in Client Header' field.
  5. Select "Column 2, Position 4" in the 'Field Order' field.
  6. Click [Add New Item].
  7. Select "Emergency Contact Name" in the 'Field to Include in Client Header' field.
  8. Select "Column 3, Position 4" in the 'Field Order' field.
  9. Click [Add New Item].
  10. Select "Emergency Contact Phone" in the 'Field to Include in Client Header' field.
  11. Select "Column 3, Position 5" in the 'Field Order' field.
  12. Click [Submit].
  13. Select "Client A" and navigate to the 'Client Information' header.
  14. Validate the 'Client Information' header is displayed with any applicable details for "Client A".
  15. Validate the 'Emergency Contact' and 'Phone' fields are displayed in the third column, positions 4 and 5, as expected.
  16. Validate all other fields are displayed in their configured column/positions.
Scenario 2: Avatar NX - Validate widget buttons in client header
Specific Setup:
  • The logged in user must have the 'Client Information header' configured to their 'myDay' view.
  • The logged in user must have additional view configured.
  • The 'Default Value for Console View Episodes' registry setting must be set to "0"
  • There must be 5 widgets assigned in the 'Client Lookup/Header Configuration Manager' form.
  • Two program overrides must be configured in the 'Client Lookup/Header Configuration Manager' form:
  • Program A and Program B
  • "Program B" must have a widget assigned.
  • Three clients must be defined:
  • A client must be enrolled in more than one existing episodes (Client A).
  • Episode 1 must be 'Program A' and the other can be any other program that's not an override.
  • A client must be enrolled in 'Program A' (Client B).
  • A client must be enrolled in 'Program B' (Client C).
  • Please note: this is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Validate five widgets buttons display in the client header.
  3. Undock one the widgets.
  4. Validate the undocked widgets displays: "Client A | Episode: All" as well as the appropriate data.
  5. Continue undocking widgets in the client header.
  6. Validate the undocked widgets display the correct client information.
  7. Navigate back to the 'myDay' view.
  8. Validate all the undocked widgets close.
  9. Navigate back to the 'Update Client Data' form.
  10. Click [Discard] and [Yes].
  11. With "Client A" selected, undocked the widgets from the client header.
  12. Validate the undocked widgets display the correct client information.
  13. Select a different episode from the 'Episode Selection' field in the top navigation
  14. Validate the undocked widgets update accordingly.
  15. Select "Client B".
  16. Validate no widget buttons display in the client header since none are configured for "Program A".
  17. Validate the undocked widgets update accordingly.
  18. Close the undocked widgets.
  19. Access the 'Progress Notes (Group and Individual)' form.
  20. Validate no widget buttons display in the client header.
  21. Clear the 'Select Episode' field.
  22. Validate the five configured widget buttons display in the client header.
  23. Select "Client C" from the 'Select Client' field.
  24. Validate the widget button configured for "Program B" displays in the client header.
  25. Undock this widget.
  26. Validate the undocked widget displays the correct client information.
  27. Select the desired value in the 'Progress Note For' field.
  28. Select the desired value in the 'Note Type' field.
  29. Enter the desired value in the 'Notes' field.
  30. Select "Draft" in the 'Draft/Final' field.
  31. Click [File Note] and [No].
  32. Validate the undocked widget closes.
  33. Clear the client.
Scenario 3: 'Client Lookup/Header Configuration Manager' - Adding widgets
Specific Setup:
  • Two program overrides must be configured in the 'Client Lookup/Header Configuration Manager' form:
  • Program A and Program B
  • Three clients must be defined:
  • A client must be enrolled in an existing episode (Client A).
  • A client must be enrolled in Program A (Client B).
  • A client must be enrolled in Program B (Client C).
  • Please note: this is for Avatar NX systems only.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Validate the additional form sections: Client Header Widgets, Client Header Override, and Client Header Override Fields.
  3. Navigate to the "Client Header Widgets" form section.
  4. Select the desired widget from the 'Select Widget Button to Include (Max 5)' field.
  5. Click [Add Widget to Header].
  6. Validate the widget displays in the 'Included Widget Buttons' field.
  7. Repeat steps 1c-1e four more times.
  8. Click [Submit].
  9. Access the 'Client Lookup/Header Configuration Manager' form.
  10. Navigate to the "Client Header Override" form section.
  11. Select "Program A" from the 'Client Header Override' field.
  12. Click [Edit Selected Item].
  13. Select the desired widget from the 'Select Widget Button to Include (Max 5)' field.
  14. Click [Add Widget to Header].
  15. Validate the widget displays in the 'Included Widget Buttons' field.
  16. Navigate to the "Client Header Override Fields" form section.
  17. Validate the previously submitted data for "Program A" displays as expected.
  18. Click [Submit].
  19. Select "Client A".
  20. Validate the widget buttons configured in step 1 display as expected.
  21. Select "Client B".
  22. Validate the widget buttons configured in step 2 displays as expected.
  23. Select "Client C".
  24. Validate no widget buttons display in the client header since none were configured for this program.
  25. Access the 'Client Lookup/Header Configuration Manager' form.
  26. Navigate to the "Client Header Widgets" form section.
  27. Select the desired widget from the 'Select Widget to Remove' field.
  28. Click [Remove Widget].
  29. Validate the 'Included Widget Buttons' field updates and displays accordingly.
  30. Click [Submit].
  31. Select "Client A".
  32. Validate the widget buttons display as expected.
  33. Access the 'Client Lookup/Header Configuration Manager' form.
  34. Navigate to the "Client Header Widgets" form section.
  35. Select the desired widget from the 'Select Widget to Change Display Order' field.
  36. Select the desired value from the 'Display Order' field.
  37. Click [Update Order].
  38. Validate the 'Included Widget Buttons' field updates and displays accordingly.
  39. Click [Submit].
  40. Select "Client A".
  41. Validate the widget buttons display as expected.
The 'Client Lookup/Header Configuration Manager' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
  • Individual Progress Note
Scenario 1: 'Client Lookup/Header Configuration Manager' - Validate Header Information
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has emergency contact information on file.
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Select the "Client Header" section.
  3. Click [Add New Item].
  4. Select "Clinical Pathway" in the 'Field to Include in Client Header' field.
  5. Select "Column 2, Position 4" in the 'Field Order' field.
  6. Click [Add New Item].
  7. Select "Emergency Contact Name" in the 'Field to Include in Client Header' field.
  8. Select "Column 3, Position 4" in the 'Field Order' field.
  9. Click [Add New Item].
  10. Select "Emergency Contact Phone" in the 'Field to Include in Client Header' field.
  11. Select "Column 3, Position 5" in the 'Field Order' field.
  12. Click [Submit].
  13. Select "Client A" and navigate to the 'Client Information' header.
  14. Validate the 'Client Information' header is displayed with any applicable details for "Client A".
  15. Validate the 'Emergency Contact' and 'Phone' fields are displayed in the third column, positions 4 and 5, as expected.
  16. Validate all other fields are displayed in their configured column/positions.
Scenario 2: 'Client Lookup/Header Configuration Manager' - Adding widgets
Specific Setup:
  • Two program overrides must be configured in the 'Client Lookup/Header Configuration Manager' form:
  • Program A and Program B
  • Three clients must be defined:
  • A client must be enrolled in an existing episode (Client A).
  • A client must be enrolled in Program A (Client B).
  • A client must be enrolled in Program B (Client C).
  • Please note: this is for Avatar NX systems only.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Validate the additional form sections: Client Header Widgets, Client Header Override, and Client Header Override Fields.
  3. Navigate to the "Client Header Widgets" form section.
  4. Select the desired widget from the 'Select Widget Button to Include (Max 5)' field.
  5. Click [Add Widget to Header].
  6. Validate the widget displays in the 'Included Widget Buttons' field.
  7. Repeat steps 1c-1e four more times.
  8. Click [Submit].
  9. Access the 'Client Lookup/Header Configuration Manager' form.
  10. Navigate to the "Client Header Override" form section.
  11. Select "Program A" from the 'Client Header Override' field.
  12. Click [Edit Selected Item].
  13. Select the desired widget from the 'Select Widget Button to Include (Max 5)' field.
  14. Click [Add Widget to Header].
  15. Validate the widget displays in the 'Included Widget Buttons' field.
  16. Navigate to the "Client Header Override Fields" form section.
  17. Validate the previously submitted data for "Program A" displays as expected.
  18. Click [Submit].
  19. Select "Client A".
  20. Validate the widget buttons configured in step 1 display as expected.
  21. Select "Client B".
  22. Validate the widget buttons configured in step 2 displays as expected.
  23. Select "Client C".
  24. Validate no widget buttons display in the client header since none were configured for this program.
  25. Access the 'Client Lookup/Header Configuration Manager' form.
  26. Navigate to the "Client Header Widgets" form section.
  27. Select the desired widget from the 'Select Widget to Remove' field.
  28. Click [Remove Widget].
  29. Validate the 'Included Widget Buttons' field updates and displays accordingly.
  30. Click [Submit].
  31. Select "Client A".
  32. Validate the widget buttons display as expected.
  33. Access the 'Client Lookup/Header Configuration Manager' form.
  34. Navigate to the "Client Header Widgets" form section.
  35. Select the desired widget from the 'Select Widget to Change Display Order' field.
  36. Select the desired value from the 'Display Order' field.
  37. Click [Update Order].
  38. Validate the 'Included Widget Buttons' field updates and displays accordingly.
  39. Click [Submit].
  40. Select "Client A".
  41. Validate the widget buttons display as expected.
Topics
• Client Header • Progress Notes (Group And Individual) • Update Client Data • NX
Update 29 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 Management Definition
Scenario 1: Document Routing Setup - Allow Comments During Approval set to "Yes" for modeled form
Specific Setup:
  • A client must be enrolled in an existing episode.
  • A modeled form is defined with the following (Form A):
  • Two scrolling free text fields (Field A & Field B)
  • A 'Draft/Final' field
  • Document routing enabled and "Yes" selected for 'Allow Comments During Approval'
  • Have two users for testing with associated practitioners (User A & User B).
  • Both users have the "My To Do's" widget on their home view.
Steps
  1. Log in as "User A".
  2. Select "Client A" and access "Form A".
  3. Populate all required and desired fields.
  4. Enter long text in "Field A" and "Field B".
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate the 'Confirm Document' dialog is displayed with the form details.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user and click [Verify].
  10. Select "User B" as an approver and click [Submit].
  11. Log out.
  12. Log in as "User B".
  13. Access the 'My To Do' widget.
  14. Locate the 'To Do' that was previously sent from 'Documents to Sign'.
  15. Click [Review] and [Accept].
  16. Enter any value in the 'Approval Comments' field.
  17. Click [Sign].
  18. Enter the logged in user's password in the 'Verify Password' field.
  19. Click [Verify].
  20. Validate the 'To Do' has been removed.
  21. Access the 'Clinical Document Viewer' form.
  22. Select "Client" in the 'Select Type' field.
  23. Select "Individual" in the 'Select All or Individual Client' field.
  24. Select "Client A" in the 'Select Client' field.
  25. Click [Process].
  26. Validate the finalized record for "Form A" is displayed and select it for viewing.
  27. Validate the data filed in the previous steps is displayed as expected, with the 'Approval Comments' appended to the end of the document.
  28. Click [Close All Documents] and close the form.
The 'Event Log Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Event Log Report
Scenario 1: Event Log Report - 'All' Event Types and Categories
Steps
  1. Access the 'Event Log Report' form.
  2. Enter the current date in the 'Start Date' and 'End Date' fields.
  3. Enter the desired value in the 'Start Time' field to include the event in the setup.
  4. Click [End Time - Current Time].
  5. Select "All Event Types" in the 'All Event Types or Selected' field.
  6. Select "All Categories" in the 'All Categories or Selected' field.
  7. Select "Ascending" in the 'Data Sort' field.
  8. Click [View Event Log].
  9. Validate the report opens up in a new window.
  10. Click 'Events Sorted By User ID'.
  11. Validate the report displays as expected and is filtered by User ID.
  12. Validate the 'IP Address' field is populated with the user's IP Address.
  13. Close the report and the form.
Topics
• Modeling • Document Routing • Clinical Document Viewer • To-Do's • My To Do's • Approval Comments • Query/Reporting
Update 31 Summary | Details
Search Results - Diagnosis Filtering
Scenario 1: Diagnosis - Editing a diagnosis
Specific Setup:
  • Admission:
  • An existing client is identified or a new client is admitted. Note the client id/Name.
  • Diagnosis:
  • A client must have a diagnosis entered.
Steps
  1. Open the 'Diagnosis' form.
  2. Search for desired client in the 'Select Client' field.
  3. Validate results display.
  4. Select desired client from the results.
  5. Validate a Pre-Display is displayed showing existing diagnoses for the client.
  6. Select an existing diagnosis record.
  7. Click [Edit].
  8. Enter an invalid time in the 'Time of Diagnosis' field.
  9. Validate an Error message stating: "Invalid time format. HH:MM AM, HH:MM PM or HHMM military time (Midnight is 0000 hours.)"
  10. Validate the 'Time of Diagnosis' field defaults to the time that was saved prior.
  11. Change the 'Time of Diagnosis' field to the current time.
  12. Enter a different practitioner in the 'Diagnosing Practitioner' field.
  13. Select "Void" in the 'Status' field.
  14. Validate the voided diagnosis is crossed off.
  15. Navigate to the myDay view.
  16. Navigate back to the open 'Diagnosis' form.
  17. Validate the voided diagnosis is crossed off.
  18. Validate the 'Diagnosing Practitioner' contains the value entered in the previous steps.
  19. Click [Submit].
  20. Validate a Pre-Display Confirmation dialog is displayed stating: Do you want to return to Pre-Display?
  21. Click [Yes].
  22. Select desired diagnosis record.
  23. Click [Edit].
  24. Select "No" in the 'Show Active Only' field.
  25. Validate the voided diagnosis displays and is crossed off.
  26. Close the form.
  27. Open the "Registry Settings" form.
  28. Search for the registry setting "Default Limit Results by ICD Category".
  29. Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
  30. Click [Submit] to file the form.
  31. Open the "Diagnosis" form.
  32. Edit a previously added row of the "Diagnosis" table.
  33. Search for any a number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 2: Diagnosis - Diagnosis Entry
Specific Setup:
  • A client must be enrolled in an active episode (Client A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Click [Add].
  3. Select "Admission" in the 'Type of Diagnosis' field.
  4. Press the 'Tab' key on the 'Type of Diagnosis' field.
  5. Validate the focus shifts to the 'Date of Diagnosis' field and the admission date is displayed as expected.
  6. Press the 'Tab' key on the 'Date of Diagnosis' field.
  7. Validate the focus shifts to the 'Time of Diagnosis' field.
  8. Enter any value in the 'Time of Diagnosis' field.
  9. Click [New Row].
  10. Search for and select the desired value in the 'Diagnosis Search' field.
  11. Verify the 'Add To Problem List' field is defaulted to 'Yes'.
  12. Populate all required and desired fields.
  13. Click [Submit] and [No].
  14. Select "Client A" and access the ‘Diagnosis’ form.
  15. Select the previously created diagnosis row to edit.
  16. Click [Edit].
  17. Click [New Row].
  18. Search for and select the desired value in the 'Diagnosis Search' field.
  19. Validate that the 'Diagnosis Search' returns the expected diagnoses.
  20. Populate all required and desired fields.
  21. Click [Submit] and [No].
  22. Select "Client A" and access the 'Diagnosis' form.
  23. Select the diagnosis row edited in the previous steps.
  24. Click [Edit].
  25. Validate that the newly added diagnosis row is displayed.
  26. Close the form.
  27. Open the "Registry Settings" form.
  28. Search for the registry setting "Default Limit Results by ICD Category".
  29. Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
  30. Click [Submit] to file the form.
  31. Select 'Client A' and open the "Diagnosis" form.
  32. Edit a previously added row of the "Diagnosis" table.
  33. Search for any number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 3: Registry Setting - Default Limit Results by ICD Category"
Specific Setup:
  • Note: When setting up the new Registry Setting, 'Default Limit Results by ICD Category', also check the following registry setting: 'Avatar PM->Client Information->Diagnosis->->->Remove References to ICD-9/DSM-IV Codesets'. If it's set to '2' do the following:
  • Open the "Client Charge Input With Diagnosis Entry" form.
  • Attempt to do a search on Diagnosis.
  • Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
  • If 'No Records Found' is in the search results, then update 'Remove References to ICD-9/DSM-IV Codesets' as follows:
  1. Change the value from 2 to 0 and submit the change.
  2. Change the value from 0 back to 2 and submit the change.
  3. Repeat steps the above steps to verify that the results are displayed as expected.
Steps
  1. Open the "Registry Settings" form.
  2. Search for the registry setting "Default Limit Results by ICD Category".
  3. Note: This registry setting is only available in NX.
  4. Note the registry setting is defaulted to blank. This will generate all results.
  5. Open any of the following forms that include a diagnosis search such as "Client Chart Input with Diagnosis", "Diagnosis", "Edit Service Information", "Service Panel Chart Input", "Set Associated Codes", Ambulatory or Inpatient Progress Notes with Diagnosis, etc.
  6. Attempt to do a search on Diagnosis.
  7. Validate the search result returns all values and does not filter any results.
  8. Open the "Registry Settings" form.
  9. Search for the registry setting "Default Limit Results by ICD Category".
  10. Set the registry setting to a valid value other than blank.
  11. Open any of the forms mentioned in step 2.
  12. Attempt to do a search on Diagnosis.
  13. Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
Topics
• Diagnosis
Update 33 Summary | Details
Product Updates
Scenario 1: Validate accessabilty to the "Product Updates" form based on system configuration
Steps
  1. Internal Testing Only
Topics
• Update Install
Update 34 Summary | Details
Document Management Dictionary Update
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ProviderConnect File Attach
Scenario 1: 'Provider File Attach' - Verification of Document Conversion (From 'ProviderConnect File Attach' Source)
Steps
  • Internal Testing Only
'Provider File Attach' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Provider File Attach
Scenario 1: 'Provider File Attach' - Form Verification
Specific Setup:
  • Document Management Configuration must be defined for Cache Server or Perceptive (via Avatar PM / RADplus Utilities 'Document Management Defaults' form)
  • Dictionary Codes may optionally be defined for 'Other Tabled Files' Data Element '(70007) Document Type' (via Avatar MSO 'Dictionary Update' form)
  • 'Provider File Attach' Widget may optionally be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
  • Clinical Document Viewer/Document Management/All Documents Widgets may optionally be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
  • One or more .PDF (Adobe Portable Document Format) and/or .TIF (Tagged Image File Format) files for Provider File Attach upload/storage
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar MSO 'Provider File Attach' form (under 'Avatar MSO / Provider Management' menu).
  2. Enter/select 'Member ID' value.
  3. Enter/select 'Provider' value.
  4. In 'File Type' field, ensure the following selections are available:
  5. 'Authorization' (will link File Attachment to a specific Avatar MSO Service Authorization record for selected Provider)
  6. 'Provider' (will link File Attachment to selected Provider)
  7. 'Other' (will link File Attachment to selected Provider)
  8. Select 'File Type' value (and 'Authorization' field value if applicable).
  9. Select 'Document Type' value and/or enter 'Comments' value if desired.
  10. Click 'Upload File' button, and select file for Provider Attachment upload/storage.
  11. On completion of File Attachment upload, ensure 'File Name' field is populated with uploaded file name.
  12. Click 'Store File' field to store File Attachment in Avatar MSO; ensure user is presented with confirmation dialog noting 'File successfully created'.
  13. Click 'OK' button to return to 'Provider File Attach' form.
  14. Select 'File Type' value for previously uploaded/stored File Attachment.
  15. Ensure uploaded/stored File Attachment files are listed/available for selection in the 'Existing Files' field.
  16. Close 'Provider File Attach' form.
  17. Navigate to Home View, Chart View or Client Dashboard View where Avatar MSO 'Provider File Attach' Widget is assigned/present
  18. Ensure that the 'Provider File Attach' Widget displays all uploaded/stored File Attachment files for selected/currently active Member ID/Client (one row in Widget display per File Attachment).
  19. Navigate to Home View, Chart View or Client Dashboard View where one or more myAvatar Clinical Document Viewer/Document Management/All Documents Widgets is/are assigned/present
  20. Ensure that the Clinical Document Viewer/Document Management/All Documents Widget displays all uploaded/stored File Attachment files where expected for selected/currently active Member ID/Client, including 'Form Name' value of 'Provider Document'.
  21. Open Crystal Reports or other SQL reporting tool.
  22. In Avatar PM/Avatar MSO SQL table 'DOCM.document_image', ensure that all uploaded/stored Provider File Attachment files are present in SQL table data (one row per File Attachment); ensure that 'formID' value for Provider File Attachment records is 'PCON' ('Provider Document').
  23. Note - As 'formID' is used for 'Form Name' display in Clinical Document Viewer/Document Management/All Documents Widgets; on installation of RADPlus 2024 Update 34, all existing Provider File Attach related Document Management rows will be updated with 'formID' value 'PCON'
  24. In Avatar MSO SQL table 'SYSTEM.file_attach_object', ensure that all uploaded/stored Provider File Attachment files are present in SQL table data (one row per File Attachment).
  25. In Avatar MSO SQL table 'SYSTEM.file_attach_comments', ensure that all uploaded/stored Provider File Attachment 'Comments' field entries are present in SQL table data (one row per 'Comments' entry).
Topics
• System Maintenance • Document Management
Update 35 Summary | Details
'User Merge' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Merge
Scenario 1: 'User Merge' - merge existing user into a new user
Specific Setup:
  • A CWS form must be attached to the PM menu using the 'Attach Other Application Form To Menu' form (Form A).
  • A user role must be defined (User Role A) with the following:
  • Access to "Form A" in the 'Select Forms' field in the 'Appointment Scheduling' section.
  • A user must be defined and associated to "User Role A" (User A).
Steps
  1. Access the 'User Merge' form.
  2. Select "New" in the 'Merge Into New or Existing User' field.
  3. Enter "MergeUser" in the 'New User ID' field.
  4. Enter "Merge User" in the 'New User Description' field.
  5. Select "User A" in the 'Source User 1' field.
  6. Click [Submit].
  7. Validate a "Form Return" message is displayed stating: User Merge has completed. Do you wish to return to form?
  8. Click [Yes].
  9. Select the "User Merge Process" section.
  10. Select "User" in the 'All or User' field.
  11. Select "MergeUser" in the 'User Part of Merge' field.
  12. Click [Display Progress Log].
  13. Validate the 'User Merge Progress Log' shows 100% complete. This may take a few moments.
  14. Close the form.
  15. Access the 'User Definition' form.
  16. Select "User A" in the 'Select User' field.
  17. Validate a message is displayed stating: User ID "User A" is disabled. Only User Description can be updated.
  18. Click [OK].
  19. Select "MergeUser" in the 'Select User' field.
  20. Validate the 'User ID' field contains "MergeUser".
  21. Validate the 'User Description' field contains "Merge User".
  22. Validate "User Role A" is selected in the 'User Role(s)' field.
  23. Close the form.
Routing Admin Dashboard - Completed Items
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Admin Dashboard
  • Rule Based Routing
  • Routing Worklist Item
Scenario 1: Routing Admin Dashboard - Re-Assign
Specific Setup:
  • The system is set up for Rule-Based Routing.
  • Must have a rule-based routing item that has been completed (Item A).
  • Must have a rule-based routing item that has not been completed (Item B).
Steps
  1. Access the 'Routing Admin Dashboard' form.
  2. Select the desired value in the 'Queue' field and click [Search].
  3. Select "Item A" from the 'Results' list and click [Re-Assign].
  4. Validate a message is displayed stating: Completed documents may not be re-assigned.
  5. Click [OK].
  6. Select "Item B" in the 'Results' list and click [Re-Assign].
  7. Select "Direct Assignment" in the 'Assignment Type' field.
  8. Select the desired value in the 'New Queue' field.
  9. Select the desired value in the 'New Status' field.
  10. Select the desired user in the 'New User' field.
  11. Click [File].
  12. Select the queue the document has been re-assigned to in the 'Queue' field.
  13. Click [Search].
  14. Validate "Item B" is displayed in the 'Results' list with the updated status/user.
  15. Close the form.
Scenario 2: Routing Admin Dashboard - Re-Assign
Specific Setup:
  • The system is set up for Rule-Based Routing.
  • Must have a rule-based routing item that has been completed (Item A).
  • Must have a rule-based routing item that has not been completed (Item B).
Steps
  1. Access the 'Routing Admin Dashboard' form.
  2. Select the desired value in the 'Queue' field and click [Search].
  3. Select "Item A" from the 'Results' list and click [Re-Assign].
  4. Validate a message is displayed stating: Completed documents may not be re-assigned.
  5. Click [OK].
  6. Select "Item B" in the 'Results' list and click [Re-Assign].
  7. Select "Direct Assignment" in the 'Assignment Type' field.
  8. Select the desired value in the 'New Queue' field.
  9. Select the desired value in the 'New Status' field.
  10. Select the desired user in the 'New User' field.
  11. Click [File].
  12. Select the queue the document has been re-assigned to in the 'Queue' field.
  13. Click [Search].
  14. Validate "Item B" is displayed in the 'Results' list with the updated status/user.
  15. Close the form.
Topics
• User Definition • User Merge • Rule Based Routing
Update 36 Summary | Details
Console Widget Viewer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Access the 'Practitioner Enrollment' form.
  13. Select the practitioner linked to the logged in user for view/update.
  14. Validate that all the required/ desired fields are populated correctly.
  15. Click [Categories/Taxonomy] tab.
  16. Select any existing row in 'Category/Taxonomy' field.
  17. Validate all required fields are populated.
  18. Click "Practitioner Credentials" button.
  19. Select "Credential A" from the list.
  20. Click [OK]
  21. Click [Add Practitioner Categories].
  22. Validate the 'Confirm' dialog contains "Saved. Please note: The changes will take effect when you submit the form." message.
  23. Click [OK].
  24. Click [Submit].
  25. Select "Client A" and navigate to the 'All Documents' view.
  26. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  27. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  28. Select the progress note for viewing.
  29. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  30. Click [Print]
  31. Select "Print Current" dropdown value.
  32. Validate the practitioner's credential "Credential A" is displayed on the printable form.
  33. Validate an [Append] button is displayed and click it.
  34. Validate the 'Append Progress Notes' form is displayed.
  35. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  36. Click [Submit].
  37. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  38. Click [Accept].
  39. Enter the password associated with the logged in user and click [Verify].
  40. Click [Close All] in the 'Console Widget Viewer'.
  41. Refresh the 'All Documents' widget.
  42. Select the progress note appended in the previous steps for viewing.
  43. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  44. Click [Close All].
Scenario 2: Progress Notes (Group and Individual) - Add a progress note via the Client Chart
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Please note : this is for myAvatar only.
  • The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
  1. Double click on "Client A" in the 'My Clients' widget.
  2. Verify the 'Chart View' for "Client A" is displayed.
  3. Select 'Progress Notes (Group & Individual)' on the left-hand side.
  4. Validate any previously filed notes are displayed for "Client A".
  5. Click [Add].
  6. Validate the 'Progress Notes (Group and Individual)' form is displayed.
  7. Populate all required and desired fields.
  8. Select "Draft" in the 'Draft/Final' field.
  9. Click [File Note].
  10. Validate a message is displayed stating: Note Filed.
  11. Click [OK].
  12. Validate the 'Chart View' is displayed.
  13. Refresh the chart.
  14. Validate the note filed in the previous steps is displayed.
  15. Close the chart.
Topics
• Progress Notes • All Documents Widget
Update 37 Summary | Details
Avatar NX - 'Online Documentation URL'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Progress Notes
Scenario 1: Validate 'Online Documentation URL' links set up in 'Form Designer'
Specific Setup:
  • Please note: this is for Avatar NX.
  • User must have an 'Online Documentation' link set up in 'Form Designer' for the 'Progress Notes (Group and Individual)' form.
  • User must have an 'Online Documentation' link set up in 'Form Designer' for the 'Diagnosis' form.
  • A modeled form is defined (Form A).
  • User must have an 'Online Documentation' link set up in 'Form Designer' for "Form A".
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Validate the 'Online Documentation' link is present.
  3. Click the 'Online Documentation' link and verify a new browser window opens to the URL set up in the pre-conditions.
  4. Validate when you close the new browser window, the NX screen should still be open, and you can close the form successfully.
  5. Access the 'Diagnosis' form.
  6. Validate the 'Online Documentation' link is present.
  7. Click the 'Online Documentation' link and verify a new browser window opens to the URL set up in the pre-conditions.
  8. Validate when you close the new browser window, the NX screen should still be open, and you can close the form successfully.
  9. Access "Form A".
  10. Validate the 'Online Documentation' link is present.
  11. Click the 'Online Documentation' link and verify a new browser window opens to the URL set up in the pre-conditions.
  12. Validate when you close the new browser window, the NX screen should still be open, and you can close the form successfully.
Topics
• Form Designer • NX
Update 38 Summary | Details
Form Designer - Exports
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
  • Form Designer (PM)
Scenario 1: Form Designer - Validations in UAT environment
Specific Setup:
  • The 'Close Charges' form has had prior form designer changes made.
  • Must be logged in with a UAT system code.
Steps
  1. Access the 'Form Designer' form.
  2. Select "Close Charges" in the 'Forms' field.
  3. Select "Close Charges" in the 'Sections' field.
  4. Select "Yes" in the 'Revert To Other Form Designer Copy' field.
  5. Validate the 'Export All Sections or Selected Section?' field is disabled.
  6. Select "No" in the 'Revert To Other Form Designer Copy' field.
  7. Validate the 'Export All Sections or Selected Section?' field is disabled.
  8. Close the form.
Topics
• Form Designer
Update 39 Summary | Details
Registry Settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Codes
  • Client Ledger
Scenario 1: Validating the error message Registry Setting -'Unit Calculation with Minimum Duration' in 'Service Documentation' Form
Specific Setup:
  • Registry Settings:
  • Set the value 'Unit Calculation with minimum duration' ="Y".
  • Client:
  • Identify an existing client or create a new client. Note the client’s admission date.
  • Verify existing or add a Financial Eligibility record.
  • Service Code:
  • ‘An existing service code is identified that has a value defined for the 'Minimum Duration for Unit Calculation' field (Service Code 1).
  • Progress Note entry and Service Documentation entry need to be updated to compare service duration entered in Notes against the Service Code’s configuration for “Minimum Duration for Unit Calculation”.
  • A modeled form containing Progress Note fields (Service Documentation) must be imported through 'Envelope Import' and the logged in user must have access to it.


Steps
  1. Open "Service Codes" form.
  2. Click [Edit] in Add New Or Edit Existing.
  3. Enter 'Service Code 1' in 'Service Code'.
  4. Capture the value in 'Minimum Duration for Unit Calculation'.
  5. Click [Submit].
  6. Click [No].
  7. Open "Service Documentation Notes Form".
  8. Enter the 'Client ID' in [Search Client].
  9. Enter any value in [Date of Service].
  10. Enter 'Service Code 1' created in setup in [Service Code].
  11. Enter a value more than 'Minimum duration' field in 'Service Code' form in 'Service Duration'.
  12. Click [Submit].
  13. Open "Client Ledger" form.
  14. Enter the 'Client ID'.
  15. Click [All Episodes] in 'Claim/Episode/All Episodes'.
  16. Click [Simple] in 'Ledger Type'.
  17. Click [Yes] in 'Include Zero Charges'.
  18. Click [Process].
  19. Validate whether the services created in "Service Documentation notes" has been assigned to appropriate guarantor in Client Ledger.
  20. Click [X].
  21. Click [Yes].
  22. Click [Discard].
  23. Repeat Steps 7-22, with a value in 'Service Duration' less than the 'Minimum Duration for Unit Calculation' set in the "Service Codes" form.
  24. Open the "Registry Settings" form and change the value of the ‘Unit Calculation with Minimum Duration‘ setting to ‘YW’.
  25. Validate the warning message displayed: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes.
  26. Click [OK].
  27. Click [Submit].
  28. Open the "Registry Settings" form and change the value of the ‘Unit Calculation with Minimum Duration‘ setting to ‘YE’.
  29. Repeat Steps 7-22, with a value in 'Service Duration' less than the 'Minimum Duration for Unit Calculation' set in the "Service Codes" form.
  30. Validate the error message displayed: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes.
  31. Click [OK].
  32. Click [Submit].
Topics
• Registry Settings
Update 40 Summary | Details
Mobile user count
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: Validate adding a user in form 'User Definition'
Specific Setup:
  • A form must be defined in 'Document Management Definition' with an apostrophe (Form A).
Steps
  1. Access the 'User Definition' form.
  2. Enter the desired value in the 'User ID' field.
  3. Enter the desired value in the 'User Description' field.
  4. Populate all required and desired fields.
  5. Navigate to 'Document Management' tab.
  6. Select "No" in the 'Is this user a Document Management Administrator' item.
  7. Select "Specify forms" in the 'Forms Allowed to Print' field.
  8. Click [Select Forms to Print].
  9. Select "Form A" in the 'Select Forms' field.
  10. Click [OK].
  11. Click [Select Forms to Print].
  12. Validate "Form A" is still selected.
  13. Click [OK].
  14. Submit the form.
  15. Access the 'User Definition' form.
  16. Select the user created in the previous steps.
  17. Navigate to 'Document Management' tab.
  18. Click [Select Forms to Print].
  19. Validate "Form A" is still selected.
  20. Click [OK] and close the form.
To Do and Delete/Re/Assign - All Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Approver Override
  • Escalate To Do Item
  • Delete/Re-Assign To Do Items
Scenario 1: "Approver Override" form - Validate Document display and functionality
Specific Setup:
  • Have two users who are staff members [StaffA] and [StaffB].
  • Have two forms enabled for document routing [FormA] and [FormB] and both use form type, [TypeA].
  • [ClientA] has two document rows [DocRow1] and [DocRow2] submitted in [FormA] that has been routed to [StaffB] for approval.
  • [ClientB] has two document rows [DocRow1] and [DocRow2] submitted in [FormB] that has been routed to [StaffB] for approval.
  • [StaffA] has the "My To Do's" widget on their home view.
  • Log in as [StaffA].
Steps
  1. Open form "Approver Override":
  2. In the "Form Type" field choose In the "Entity" field, select [TypeA].
  3. In the "Entity" field select [ClientA]:
  4. Populate the "From" and "To", date fields.
  5. Click the "List of Documents" field:
  6. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  7. Select [DocRow1]:
  8. Click [Display Document] to view the document:
  9. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow1], as expected.
  10. Click [Close].
  11. Click the "List of Documents" field:
  12. Select [DocRow2].
  13. Click [Display Document] to view the document:
  14. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow2], as expected.
  15. Click [Close].
  16. In the "Entity" field select [ClientB]:
  17. Populate the "From" and "To", date fields.
  18. Click the "List of Documents" field.
  19. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  20. Select [DocRow1]:
  21. Click [Display Document] to view the document:
  22. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow1], as expected.
  23. Click [Close]
  24. Click the "List of Documents" field
  25. Select [DocRow2]
  26. Click [Display Document] to view the document
  27. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  28. Click [Update Approvers]
  29. In the "Route Document To" screen, uncheck the current selected approver
  30. In the "Add Approver" field, select [StaffA]
  31. Click [Submit]
  32. Navigate to the "My To Do's" widget, and locate the row with the To Do sent in step 1d
  33. Click [Approve Document]
  34. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  35. Click [Accept]
  36. Populate the "Verify Password" prompt
  37. Click [OK]
  38. Validate the "To Do" is removed from the "My To Do's"
Scenario 2: Delete/Re-Assign To Do's - Validations
Specific Setup:
  • [UserA] has sent a notification To Do [NoteTodoA] to [UserB] via form "Send To Do Notification"
  • [UserA] has also sent a notification to do [NoteTodoB] to [UserC] via form "Send To Do Notification"
  • [UserD] does not have any To Do's in their "My To Do's" list
  • [UserE] has two To Do items [TestToDoA] and [TestToDoB] in their "My To Do's" list, not generated via form "Send To Do Notification"
  • Log in as [UserA]
Steps
  1. Navigate to the "My ToDo's" widget and click to refresh the widget
  2. Click the "Sent & Not Received" column in the widget
  3. Validate [NoteTodoA] generated in setup that was sent to [UserB] is present
  4. Validate [NoteTodoB] generated in setup that was sent to [UserC] is present
  5. Select [NoteTodoA] and click the "Escalate" column in the widget
  6. Click the "Escalate To Do Item" link in the column
  7. In the "Escalate To Do Item" form
  8. Search for [UserD], in the "Select User" search field
  9. Click [Add User]
  10. In the "Sent To" field, click the check box for [UserD]
  11. In the "Note" field, enter a desired message for [UserD]
  12. Click [Submit]
  13. At the "To Do Sent" message dialog, click [OK]
  14. Now select the row for the to do [NoteTodoB] click the "Escalate" column
  15. Click the "Escalate To Do Item" link in the column
  16. In the "Escalate To Do Item" form
  17. Search for [UserE], in the "Select User" search field
  18. Click [Add User]
  19. In the "Sent To" field, click the check box for [UserE]
  20. In the "Note" field, enter a message for [UserE].
  21. Click [Submit]
  22. At the "To Do Sent" message dialog, click [OK]
  23. At the Home View, open form "Delete/Re-Assign To Do Items"
  24. Select "Delete" in the "Delete/Re-assign" field
  25. In the "Select User" field, select [UserD]
  26. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed
  27. Click [OK]
  28. Validate there are no to do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step1, [Please Note: Any To Do's generated via "Send Notification To Do" form, are excluded from the "Delete/Re-Assign To Do Items" form]
  29. Click [OK]
  30. Select "Re-Assign" in the "Delete/Re-assign" field
  31. In the "Select User" field, select [UserD] again
  32. Validate a message stating "All To-Do Items for this user have been reviewed or deleted" is displayed again
  33. Click [OK]
  34. Validate there are no To Do's present in the "To Do's" list box as expected, including the escalated notification [NoteToDoA] sent to [UserD] in step 1.
  35. Click [OK]
  36. Select "Delete" again in the "Delete/Re-assign" field
  37. This time in the "Select User" field, select [UserE]
  38. Validate the notification to do [NoteToDoB], escalated to [UserE] in step1 is not present in the "To Do's" list box, as expected
  39. Validate [TestToDoA] and [TestToDoB] that were not generated from the "Send To Do Notification" form are present in the "To Do's" list box
  40. Select [TestToDoA] in the "To Do's" list box
  41. Enter any desired comment in the "Comment" field
  42. Submit the form and return to the form
  43. Select "Re-Assign" in the "Delete/Re-assign" field
  44. In the "Select User" field, select [UserE]
  45. Validate [TestToDoA] just deleted is not present in the "To Do's" list box.
  46. Validate the notification [NoteToDoB], escalated to [UserE] is also not present in the "To Do's" list box
  47. Validate [TestToDoB] is present in the "To Do's" list box
  48. Select [TestToDoB]
  49. In the "Select Target User" field, select any other user [UserF] to re-assign the to do to
  50. Submit the form
  51. Validate the form submits successfully
  52. Closet the form
  53. Log out as [UserA]
  54. Log in as [UserF]
  55. Navigate to the "My To Do's" list
  56. Validate the to do reassigned to [UserF] is present in their to do's list as expected
  57. Click [Review To Do Item]
  58. Validate the to do information for [TestToDoB], is displayed as expected
  59. Select the "Review" check box
  60. Submit the form
  61. Validate the To Do is removed from the "My To Do's" widget
To Do List - Other Client Id
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - staff auto assign
  • Practitioner Enrollment
  • app-create-to-do
  • Review To Do Item (PM)
Scenario 1: Modeled Form - Send To Do
Specific Setup:
  • A modeled form is defined (Form A).
  • "Form A" must have the 'Enable To-Do Creation From Form' field set to "Yes" in 'Form Definition'.
  • A client is enrolled in an existing episode (Client A).
  • Two users (User A & User B) are defined with associated practitioners (Practitioner A & Practitioner B).
Steps
  1. Log in as "User A".
  2. Select "Client A" and access "Form A".
  3. Populate all required and desired fields.
  4. Click [Send To Do].
  5. Validate a 'Create To Do' dialog is displayed.
  6. Select "Practitioner A" in the 'Select Staff' field.
  7. Enter the desired value in the 'Note' field.
  8. Click [Save].
  9. Finalize and submit the form.
  10. Log out.
  11. Log in as "User B".
  12. Navigate to the 'My To Do's' widget.
  13. Validate a To Do is displayed from "User A".
  14. Click [Review To Do Item].
  15. Validate the 'Review To Do Item' form is displayed.
  16. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  17. Click [Submit].
  18. Validate the To Do is no longer displayed.
Topics
• User Definition • User Role Definition • Document Management • ToDo's
Update 41 Summary | Details
Progress Notes - Error handling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Create New Progress Notes Form
  • Progress Notes (Group and Individual) 6
Scenario 1: Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Progress Notes (Group and Individual)" form.
Steps
  1. Open the "Progress Notes (Group and Individual)" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the "Progress Notes (Group and Individual)" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the "Progress Notes (Group and Individual)" form.
  13. Create and route a note to multiple approvers.
  14. Sign on as the first approver.
  15. Locate the document in the approver's "My To Do's" widget.
  16. Click on "Approve Document".
  17. Click "Accept".
  18. Enter the approver's password.
  19. Log on as another approver.
  20. Locate the document in the approver's "My To Do's" widget.
  21. Click on "Approve Document".
  22. Click "Accept".
  23. Enter the approver's password.
  24. Open the "Clinical Document Viewer" form.
  25. Select the document that was just routed/finalized.
  26. Validate that the document displays and prints.
  27. Open the "Progress Notes (Group and Individual)" form.
  28. Create a progress note and route to several approvers.
  29. Log on as another approver.
  30. Locate the document in the approver's "My To Do's" widget.
  31. Click on "Approve Document".
  32. Click "Accept".
  33. Enter the approver's password.
  34. Repeat steps 11b-12c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Scenario 2: Copy of Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
  • A new copy of the progress note form is created using "Create New Progress Note" form.
  • Document routing is enabled for the copy of the "Progress Notes (Group and Individual)" form.
Steps
  1. Open the copy of the "Progress Notes (Group and Individual)" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the copy of the "Progress Notes (Group and Individual)" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the copy of the "Progress Notes (Group and Individual)" form.
  13. Sign on as the first approver.
  14. Locate the document in the approver's "My To Do's" widget.
  15. Click on "Approve Document".
  16. Click "Accept".
  17. Enter the approver's password.
  18. Log on as another approver.
  19. Locate the document in the approver's "My To Do's" widget.
  20. Click on "Approve Document".
  21. Click "Accept".
  22. Enter the approver's password.
  23. Open the "Clinical Document Viewer" form.
  24. Select the document that was just routed/finalized.
  25. Validate that the document displays and prints.
  26. Open the copy of the "Progress Notes (Group and Individual)" form.
  27. Create a progress note and route to several approvers.
  28. Log on as another approver.
  29. Locate the document in the approver's "My To Do's" widget.
  30. Click on "Approve Document".
  31. Click "Accept".
  32. Enter the approver's password.
  33. Repeat steps 12-13 for each additional approver.
  34. Open "Clinical Document Viewer".
  35. Validate the document that was just filed display and prints.
Document Management Definition - Deleting form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
Scenario 1: Document Management Definition - Add/Delete a document
Steps
  1. Open "Document Management Definition".
  2. Add a new form, populating all required fields.
  3. File the form to submit data.
  4. Open "Document Management Definition".
  5. Validate the new form is added.
  6. Click [Delete].
  7. File the form.
  8. Open "Document Management Definition".
  9. Search for the form that was just deleted, but it's no longer there.
Scenario 2: Document Management Definition - Add/Delete with Multiple Root System Codes
Specific Setup:
  • This must be tested in a system that has multiple root system codes.
Steps
  1. Open "Document Management Definition".
  2. Add a new form, populating all required fields.
  3. File the form to submit data.
  4. Open "Document Management Definition".
  5. Validate the new form is added.
  6. Close the form.
  7. Sign onto a system code that is not the main root system code.
  8. Using the "Progress Notes (Group and Individual)" form.
  9. Create and finalize a progress note for an individual.
  10. Finalize the note and route it to one or more additional approvers.
  11. Log on as the additional approvers and approve the note.
  12. Once the final approver has approved the note, sign off and back onto the main root system code.
  13. Open "Document Management Definition".
  14. Attempt to delete the form that was just added in a previous step.
  15. Validate it won't allow you to delete the form type because there are client forms on file.
Topics
• Progress Notes • Progress Notes (Group And Individual) • Document Management
Update 42 Summary | Details
'User File Import' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User File Import
Scenario 1: User File Import - File Validations
Specific Setup:
  • Have a "User File Import" file created that includes pipe characters in the 'User Description' (File A).
Steps
  1. Access the 'User File Import' form.
  2. Click [Select User Import File].
  3. Select "import1" and click [Open].
  4. Validate the 'Import File Scan Results' field contains: No errors or warnings detected in import file.
  5. Click [Process User Import File].
  6. Validate a message is displayed stating: Import Completed!
  7. Click [OK] and close the form.
  8. Access the 'User Definition' form.
  9. Select the user imported via "File A" in the 'Select User' field.
  10. Validate the 'User Description' field contains exclamation points instead of pipe characters.
  11. Validate all imported data is displayed as expected.
  12. Close the form.
  13. Access Crystal Reports or other SQL Reporting Tool.
  14. Create a report using the SYSTEM.RADplus_users SQL table.
  15. Validate a row is displayed for the user imported via "File A".
  16. Validate the 'user_description' field contains values with exclamation points.
  17. Close the report.
Topics
• User Definition
Update 43 Summary | Details
"System Security Defaults" form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Security Defaults
  • Microsoft Outlook Calendar
Scenario 1: System Security Defaults - 'Outlook 365 Integration Configuration' setting validations
Specific Setup:
  • The "Microsoft Azure" cloud computing platform or similar platform has been setup by the client's system administrators to integrate with "Microsoft 365", to provide the "Microsoft Outlook" application to users
  • "Microsoft Outlook 365" integration certificate values : "Client ID", "Client Secret" and "Tenant ID", have been generated by the client's system administration and provided to the logged in user
  • Logged in user has access to form, "Registry Settings" and form "System Security Defaults"
Steps
  1. Open form "Registry Settings"
  2. Search for registry setting "Enable Outlook 365 Integration"
  3. Entering a value of "Y" in the "Registry Settings Value" field will:
  4. Enable support for "Outlook 365 Integration" in the system
  5. Create a new section in form "System Security Defaults", called "Outlook 365 Integration Configuration", where integration certificate values may be entered and submitted
  6. Entering a value of "N" in the "Registry Settings Value" field will:
  7. Disables support for "Outlook 365 Integration" in the system
  8. Removes section "Outlook 365 Integration Configuration" in form "System Security Defaults"
  9. Set the value in the "Registry Settings Value" field to a value other than "Y" or "N"
  10. Validate the error message "The selected value is not valid in the current system code for the following reason: Valid values are Y or N", is displayed
  11. Set the value in the "Registry Settings Value" field to "Y"
  12. Validate the value is accepted
  13. Submit the form
  14. Validate the form files successfully
  15. Click "Yes" to return to the form
  16. Search for registry setting "Enable Outlook 365 Integration"
  17. Validate the "Registry Setting Value" is set to "Y", as expected
  18. Close the form
  19. Open form "System Security Defaults"
  20. Click section "Outlook 365 Integration Configuration"
  21. Click the "Enter Outlook 365 Integration Configuration" button
  22. Validate the "Outlook 365 Integration Configuration" dialog box is displayed
  23. Navigate to the "Client ID" field
  24. Enter a value greater than "100" characters
  25. Validate a message "The field name is too long, the maximum length is 100 characters"
  26. Click "OK"
  27. Enter a value less than "100" characters
  28. Validate the value is accepted
  29. Navigate to the "Client Secret" field
  30. Enter a value greater than "100" characters
  31. Validate a message "The field name is too long, the maximum length is 100 characters"
  32. Click "OK"
  33. Enter a value less than "100" characters and include a tilde '~' character
  34. Validate the value is accepted
  35. Navigate to the "Tenant ID"
  36. Enter a value greater than "100" characters
  37. Validate a message "The field name is too long, the maximum length is 100 characters"
  38. Click "OK"
  39. Enter a value less than "100" characters
  40. Validate the value is accepted
  41. Click [OK]
  42. Submit the form
  43. Validate submission is successful
  44. Return to the form "System Security Defaults"
  45. Select section "Outlook 365 Integration Configuration"
  46. Click the "Enter Outlook 365 Integration Configuration" button
  47. Validate the value in the "Client ID" field is as expected
  48. Validate the value in the "Client Secret" field is as expected, and includes the tilde '~' character displayed
  49. Validate the value in the "Tenant ID" field is as expected
  50. Click [Cancel]
  51. Click the "Enter Outlook 365 Integration Configuration" button again to return to the dialog
  52. In the "Client ID", Client Secret" and "Tenant ID" field, make a change to the value in each field
  53. Click [Cancel]
  54. Click the "Enter Outlook 365 Integration Configuration" button
  55. Validate the original value submitted are displayed not the value changed in step 3c, as expected
  56. In the "Client ID", Client Secret" and "Tenant ID" field, make a change to value in each field again
  57. Click [OK]
  58. Click [Submit] to file the form
  59. Return to the form "System Security Defaults"
  60. Select section "Outlook 365 Integration Configuration"
  61. Click the "Enter Outlook 365 Integration Configuration" button
  62. Validate the values in the "Client ID", "Client Secret" and "Tenant ID" fields, including any tilde '~' characters, are displayed as expected
  63. Open form "Registry Settings"
  64. Search for registry setting "Enable Outlook 365 Integration"
  65. Enter a value of "N" in the "Registry Settings Value" field
  66. Submit the form
  67. Validate the form files successfully
  68. Return to the form "System Security Defaults"
  69. Validate the section "Outlook 365 Integration Configuration", is not longer present on the form as expected
  70. Open form "Registry Settings"
  71. Search for registry setting "Enable Outlook 365 Integration"
  72. Enter a value of "Y" in the "Registry Settings Value" field
  73. Submit the form
  74. Validate the form files successfully
  75. Return to the form "System Security Defaults"
  76. Validate the section "Outlook 365 Integration Configuration", is now present on the form again, as expected
Topics
• System Security Defaults
Update 44 Summary | Details
Client Search Results
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
  • Client Charge Input
Scenario 1: Validate "Client" search field functionality and results
Specific Setup:
  • The 'Disable Soundex in Smart Search' registry setting must be set to "Y".
  • Must have the 'Client and Staff' widget on the HomeView.
Steps
  1. In the 'Search Clients' field on the HomeView, enter a single letter without clicking the [Search] button.
  2. Validate the 'Results' list contains clients whose last name starts with that letter.
  3. In the 'Search Clients' field on the HomeView, enter a single letter and click [Search].
  4. Validate the 'Select Client' dialog is displayed and the 'Results' list contains clients whose last name starts with that letter.
  5. Repeat steps 1 and 2 entering two or more letters.
  6. Validate the 'Results' list contains clients whose last name begins with those two letters.
  7. In the 'Search Clients' field on the HomeView, enter a last name followed by a comma (Ex. LASTNAME,).
  8. Validate the 'Results' list contains clients with the last name entered.
  9. In the 'Search Clients' field, enter a single number without clicking [Search].
  10. Validate the 'Results' list contains clients whose PATID contain that number.
  11. In the 'Search Clients' field, enter a single number and click [Search].
  12. Validate the 'Select Client' dialog is displayed and the 'Results' list contains clients whose PATID contain that number.
  13. Repeat steps 5 and 6 entering two or more numbers.
  14. Validate the 'Results' list contains clients containing PATIDs with those numbers.
  15. Access any client based form and in the 'Select Client' field, enter a single letter without clicking [Search].
  16. Validate the 'Results' list contains clients whose last name starts with that letter.
  17. Access any client based form and in the 'Select Client' field, enter a single letter and click [Search].
  18. Validate the 'Select Client' dialog is displayed and the 'Results' list contains clients whose last name starts with that letter.
  19. Repeat steps 8 and 9 entering two or more letters.
  20. Validate the 'Results' list contains clients whose last name begins with those two letters.
  21. Access any client based form and in the 'Select Client' field, enter a last name followed by a comma (Ex. LASTNAME,).
  22. Validate the 'Results' list contains clients with the last name entered.
  23. Access any client based form and in the 'Select Client' field, enter a single number without clicking [Search].
  24. Validate the 'Results' list contains clients whose PATID contain that number.
  25. Access any client based form and in the 'Select Client' field, enter a single number and click [Search].
  26. Validate the 'Select Client' dialog is displayed and the 'Results' list contains clients whose PATID contain that number.
  27. Repeat steps 9 and 10 entering two or more numbers.
  28. Validate the 'Results' list contains clients containing PATIDs with those numbers.
Topics
• Client Search
Update 46 Summary | Details
The 'Age Display Format' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Call Intake
  • Pre Admit
  • Family Registration
Scenario 1: Validate the 'Age Display Format' registry setting in the 'Client Header' and 'Client Information' widget
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Registry Settings' Form.
  2. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting Details' field contains: This registry setting accepts the values "1", "2", or "3", to customize the format of age across various forms and widgets, including 'Admission', 'Admission (OutPatient)', 'Family Registration', 'Pre Admit', 'Call Intake', 'Client Header', and the 'Client Information' widget. Selecting "1" enables a simplified age display, presenting only the clients' age in years across all specified forms and widgets. Selecting "2", a more detailed age field is made visible and the display of age only in years is hidden on the 'Admission', 'Admission (OutPatient)', 'Family Registration', 'Pre Admit' and 'Call Intake' forms. For clients older than three years, age is shown in months and years, while for those under three, age is shown in days, months, and years. Selecting "3" allows for clients under 3 years old to display their age in months, and those under 2 years to display their age in months and days. All clients aged 3 and above will display age in years only.
  5. Enter "1" in the 'Registry Setting Value' field.
  6. Submit the form.
  7. Select "Client A" and access the 'Admission' form.
  8. Click [Edit].
  9. Enter the desired value in the 'Date Of Birth' field.
  10. Submit the form.
  11. Select "Client A" and access the 'Client Information' widget.
  12. Validate the 'Age' field contains the client's age in years.
  13. Select "Client A" and access the 'Admission' form.
  14. Click [Edit].
  15. Validate the 'Client Header' displays the client's age in years.
  16. Close the form.
  17. Access the 'Registry Settings' Form.
  18. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  19. Click [View Registry Settings].
  20. Enter "2" in the 'Registry Setting Value' field.
  21. Submit the form.
  22. Select "Client A" and access the 'Client Information' widget.
  23. Validate the 'Age' field displays the client's age in:
  24. Months and years if the client is older than 3 years old.
  25. Months, years, and days if the client is under 3 years old.
  26. Select "Client A" and access the 'Admission' form.
  27. Click [Edit].
  28. Validate the 'Client Header' displays the client's age in:
  29. Months and years if the client is older than 3 years old.
  30. Months, years, and days if the client is under 3 years old.
  31. Close the form.
  32. Access the 'Registry Settings' Form.
  33. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  34. Click [View Registry Settings].
  35. Enter "3" in the 'Registry Setting Value' field.
  36. Submit the form.
  37. Select "Client A" and access the 'Client Information' widget.
  38. Validate the 'Age' field displays the client's age in:
  39. Years if the client is older than 3 years old.
  40. Months if the client is between 2 and 3 years old.
  41. Months and days if the client is under 2 years old.
  42. Select "Client A" and access the 'Admission' form.
  43. Click [Edit].
  44. Validate the 'Client Header' displays the client's age in:
  45. Years if the client is older than 3 years old.
  46. Months if the client is between 2 and 3 years old.
  47. Months and days if the client is under 2 years old.
  48. Close the form.
Topics
• Registry Settings • Widgets • Client Header • NX
Update 48 Summary | Details
'My To Do's' widget - Acknowledgement To Do's
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - document routing
  • Individual Progress Note
Scenario 1: Document Routing Setup - Use Crystal Report Template - Yes
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The user must have the 'My To Do's' widget configured to their myDay view.
  • Must have a crystal report configured for progress notes document routing (Crystal Report A).
  • The 'Ambulatory Progress Notes' form must be configured in 'Document Routing Setup' as follows:
  • "Yes" selected in the 'Enable Document Routing' field
  • "Yes" selected in the 'Use Crystal Report Template' field.
  • "Crystal Report A" selected in the Crystal Report' field.
  • "Yes" selected in the 'Acknowledgement Allowed' field.
  • The logged in user must have an associated practitioner (Practitioner A).
Steps
  1. Select "Client A" and access any the 'Ambulatory Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Enter any value in the 'Notes Field'.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate a "Confirm Document" dialog is displayed with the crystal report template and note details.
  8. Click [Accept and Route].
  9. Enter the logged in user's password in the 'Verify Password' field.
  10. Add "Practitioner A" as an approver and for acknowledgement.
  11. Click [Submit].
  12. Navigate to the 'My To Do's' widget.
  13. Validate an 'Approve Document' To Do is displayed for "Client A".
  14. Approve and sign off on the document.
  15. Validate the 'Approve Document' To Do is no longer displayed.
  16. Validate an 'Acknowledge Document' To Do is displayed.
  17. Click [Acknowledge Document].
  18. Validate the document is displayed as expected.
  19. Click [Acknowledge].
  20. Enter the logged in user's password in the 'Verify Password' field.
  21. Validate the 'Acknowledge Document' To Do is no longer displayed.
'Table Definition' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Caseload Type Definition (CWS)
  • Notification Type Definition
  • Envelope Definition (CWS)
  • Table Definition (CWS)
  • Form Definition (CWS)
Scenario 1: Table Definition - Validate tables with caseload fields
Specific Setup:
  • A caseload type (Caseload A) and Notification type (Notification Type A) must be defined.
  • An envelope (Envelope A) must be defined.
Steps
  1. Access the 'Table Definition' form.
  2. Enter the desired value in the 'Select Table' field and click [New Avatar Table].
  3. Select "Envelope A" in the 'Envelope' field and click [OK].
  4. Enter the desired value in the 'Table Name' and 'Table Description' fields.
  5. Populate any other required and desired fields.
  6. Navigate to the "Column Definition" section.
  7. Click [Add New Item].
  8. Add a column for the 'Addition to Caseload' type as defined in "Caseload A".
  9. Populate any other required and desired fields.
  10. Click [Submit]. This will be referred to as "Table A".
  11. Access the 'Form Definition' form.
  12. Enter the desired value in the 'Select Form' field and click [New Avatar Form].
  13. Select "Envelope A" in the 'Envelope' field and click [OK].
  14. Enter the desired value in the 'Form Name' field.
  15. Select "Table A" in the 'Primary Table' field.
  16. Populate all required and desired fields.
  17. Navigate to the "Section Def." section.
  18. Populate all required and desired fields.
  19. Navigate to the "Object Def." section.
  20. Click [Add New Item].
  21. Add the table column(s) added for "Table A" and populate all desired fields.
  22. Click [Submit].
  23. Access the 'Caseload Type Definition' form.
  24. Click [Select Existing Caseload Type].
  25. Select "Caseload A" in the 'Select Existing Caseload Type' dialog and click [OK].
  26. Validate all previously filed values are displayed.
  27. Click [Submit].
  28. Access the 'Table Definition' form.
  29. Select "Table A" in the 'Select Table' field and click [OK].
  30. Navigate to the "Column Definition" section.
  31. Validate the previously defined column(s) are displayed as expected.
  32. Close the form.
Topics
• Document Routing • Progress Notes • Modeling • Envelope Definition • Table • Forms
Update 50 Summary | Details
Envelope Import/Export
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (CWS)
Scenario 1: Envelope Export/Import - Validate modeled forms with "Signature" and "Picture" images
Specific Setup:
  • Have a modeled [EnvelopeA], that contains a modeled form [FormA] configured with:
  • Document routing is enabled and a "Crystal Report" [DocRoutReport] is configured to display the document image
  • A "Pre-Filing" command button report [PreFileRpt], is configured on the form, to display data populated in the form prior to submission
  • 'Signature' and 'Picture" fields on the form, along with any other desired field types
  • Have another modeled envelope [EnvelopeB], that contains a modeled form [FormB] configured with
  • Document routing enabled with "No" "Crystal Report" configured. (Note: this will default to the standard "Tif" image used to display the document data)
  • Signature' and 'Picture" field, along with any other desired field types
  • Have access to forms "Envelope Export" and "Envelope Import"
Steps
  1. Open form "Enveloper Export"
  2. Select [EnvelopeA]
  3. Click [Begin Export]
  4. Navigate to location on the server to store the export file
  5. Click 'OK'
  6. Close the form
  7. Open form "Enveloper Export"
  8. Select [EnvelopeB]
  9. Click [Begin Export]
  10. Navigate to location on the server to store the export file
  11. Click 'OK'
  12. Close the form
  13. Open form "Enveloper Import"
  14. Click [Select Envelope Import File]
  15. Navigate to the location of [EnvelopeA]
  16. Select the file
  17. Click "Overwrite Existing"
  18. Click [Begin Import Scan]
  19. Validate "There are no errors/warnings found within the import file.", is displayed
  20. Click [Begin Import]
  21. Validate "Import Complete" is displayed
  22. Click [Select Envelope Import File]
  23. Navigate to the location of [EnvelopeB]
  24. Select the file
  25. Click "Overwrite Existing"
  26. Click [Begin Import Scan]
  27. Validate "There are no errors/warnings found within the import file.", is displayed
  28. Click [Begin Import]
  29. Validate "Import Complete" is displayed
  30. Close the form
  31. Open form [FormA] for any test client
  32. Populate the "Signature" field with a desired signature [SigImage]
  33. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  34. Populated data in all other desired fields on the form [Note the values entered]
  35. Click to launch the "Pre-File" report [PreFileRpt]
  36. Validate on the document image is displayed as expected
  37. Validate the "Signature" field is populated with [SigImage], as expected
  38. Validate the "Picture" field is populated with [PicImage], as expected
  39. Validate all other fields populated in step 1c, are displayed as expected
  40. Close the report
  41. Submit the form as "Final"
  42. At the document routing "Confirm Document" screen
  43. Validate the 'Crystal Report' document image is displayed as expected based on [DocRoutReport]
  44. Validate the "Signature" field is populated with [SigImage], as expected
  45. Validate the "Picture" field is populated with [PicImage], as expected
  46. Validate all other fields populated in step 1c, are displayed as expected
  47. Submit and route the document
  48. Validate submission is successful
  49. Open form [FormB] for any test client
  50. Populate the "Signature" field with a desired signature [SigImage]
  51. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  52. Populated data in all other desired fields on the form [Note the values entered]
  53. Submit the form as "Final"
  54. At the document routing "Confirm Document" screen
  55. Validate the 'Tiff' document image is displayed as expected
  56. Validate the "Signature" field is populated with [SigImage], as expected
  57. Validate the "Picture" field is populated with [PicImage], as expected
  58. Validate all other fields populated in step 1c, are displayed as expected
  59. Submit and route the document
  60. Validate submission is successful
Document Routing and Pre-File Reports - Crystal Reports
Scenario 1: Modeled Forms ('Document Routing' Crystal Report) - Validate display picture and signature fields images
Specific Setup:
  • In form 'System Security Defaults', set field "Enable Signature Pad Support" to "Yes"
  • Have two users for testing [TestUserA] and [TestUserB]
  • [TestUserB] has the "My To Do's" widget on their home view
  • Have a Modeled form [TestForm], that contained in the envelope, set with prompt "Include Envelope within CDR" set up in form "Envelope Definition"
  • The modeled table [TestTable] used in [TestForm] are currently configured with:
  • Prompt "Does this table require an associated table for storage of binary data information" is set to "Yes" and field "Binary Storage Table Name" field populated with a desired binary storage table name [TestBinary]
  • Prompt "Create Pre-Filing Report Table" set to "Yes"
  • Field "Pre-Filing Report Schema/Tab" populated with "PRETEMP" and the modeled table name appended. For this example: "PRETEMP.TestTable"
  • Prompt "Pre-Filing Report Binary Storage Schema/Table" populated with "PRETEMP" and the binary storage table name. For this example, "PRETEMP.TestBinary"
  • A "Signature", "Picture" and "Draft/Final" field added in the table, along with any other desired field types
  • Open form "User Definition", select [TestUserA]
  • Navigate to the "Forms and SQL Tables" section and click "Select Tables for Product Access".
  • Expand the "PM" folder and navigate down to the "CWSPRETEMP" folder (This is the 'CDR' folder for the "PRETEMP" folder in CWS)
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Expand the "CWS" folder and navigate down to the "PRETEMP" folder
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Click [OK] and submit the form
  • Have two "Crystal Reports" setup based [TestForm]
  • [TestReportPM] to display the data submitted in 'CDR' tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "PM" main folder "CWSPRETEMP"
  • [TestReportCWS] to display the data submitted in tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "CWS" main folder "PRETEMP"
  • In form "Import Reports", [TestReportPM] and [TestReportCWS] have been imported with prompt "Import Report for Document Routing" selected in field "Select Import Type" field
  • In form "Document Routing Setup" [TestForm] has been enabled for document routing and currently [TestReportPM] has been selected in "Crystal Report" field
  • [TestUserA] has access to form "Document Routing Setup"
  • Log in as [TestUserA]
Steps
  1. Open form [TestForm] for any test client
  2. Populate the "Signature" field with a desired signature [SigImage]
  3. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  4. Populated data in all other desired fields on the form [Note the values entered]
  5. Set the "Draft/Final" field to "Final"
  6. Submit the form
  7. At the document routing "Confirm Document" screen
  8. Validate on the document image is displayed as expected based on [TestReporPM], 'Crystal Report'
  9. Validate the "Signature" field is populated with [SigImage], as expected
  10. Validate the "Picture" field is populated with [PicImage], as expected
  11. Validate all other fields populated in step 1c, are displayed as expected
  12. Submit and route the document to [TestUserB]
  13. Validate submission is successful
  14. Log out as [TestUserA]
  15. Log in as [TestUserB]
  16. Navigate to the "My To Do's" Widget
  17. Validate the To Do sent in step 1 is present in the list
  18. Click on [Approve Document]
  19. Validate on the document image is displayed as expected based on [TestReporPM], 'Crystal Report'
  20. Validate the "Signature" field is populated with [SigImage], as expected
  21. Validate the "Picture" field is populated with [PicImage], as expected
  22. Validate all other fields populated in step 1c, are displayed as expected
  23. Click [Accept]
  24. Validate submission is successful
  25. Log out as [TestUserB]
  26. Log in as [TestUserA]
  27. Open form "Document Routing Setup" and select [TestForm] for edit
  28. Click on the "Crystal Report" field
  29. Select [TestFormCWS]
  30. Submit the form
  31. Validate the form submits successfully
  32. Repeat steps 1 thru 3
  33. Validate on the document image is displayed as expected based on [TestReportCWS] 'Crystal Report'
  34. Validate the "Signature" field is populated with [SigImage], as expected
  35. Validate the "Picture" field is populated with [PicImage], as expected
  36. Validate all other fields populated in step 1c, are displayed as expected
Scenario 2: Modeled Forms ('Pre-File Report" Crystal Report) - Validate display picture and signature fields images
Specific Setup:
  • In form 'System Security Defaults', set field "Enable Signature Pad Support" to "Yes"
  • Have a Modeled form [TestForm], that contained in that envelope that is set with prompt "Include Envelope within CDR" set up in form "Envelope Definition"
  • The modeled table [TestTable] used in [TestForm] is currently configured with:
  • Prompt "Does this table require an associated table for storage of binary data information" is set to "Yes" and field "Binary Storage Table Name" field populated with a desired binary storage table name [TestBinary]
  • Prompt "Create Pre-Filing Report Table" is set to "Yes"
  • Field "Pre-Filing Report Schema/Tab" populated with "PRETEMP" and the modeled table name appended. For this example: "PRETEMP.TestTable"
  • Prompt "Pre-Filing Report Binary Storage Schema/Table" populated with "PRETEMP" and appended with the binary storage table name. For this example, "PRETEMP.TestBinary"
  • A "Signature" and "Picture" field along with anyother desired field types have been added to the table
  • Open form "User Definition", select [TestUserA]
  • Navigate to the "Forms and SQL Tables" section and click "Select Tables for Product Access".
  • Expand the "PM" folder and navigate down to the "CWSPRETEMP" folder (This is the 'CDR' folder for the "PRETEMP" folder in CWS)
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Expand the "CWS" folder and navigate down to the "PRETEMP" folder
  • Click to expand the folder
  • Validate both [TestBinary] and [TestTable] are present
  • Click [OK] and submit the form
  • Have two "Crystal Reports" setup based [TestForm]
  • [TestReportPM] to display the data submitted in 'CDR' tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "PM" main folder "CWSPRETEMP"
  • [TestReportCWS] to display the data submitted in tables "PRETEMP.TestTable" and "PRETEMP.TestBinary" residing under the "CWS" main folder "PRETEMP"
  • In form "Import Reports", [TestReportPM] and [TestReportCWS] have been imported with prompt "Import Report for Document Routing" selected in field "Select Import Type" field
  • In "Form Definition", A "Pre-Fileing Report" command button objects have been added for both [TestReportPM] and [TestReportCWS], so that they can be launched prior to submitting the form, to display data currently populated in the form prior to submission
Steps
  1. Open form [TestForm] for any test client
  2. Populate the "Signature" field with a desired signature [SigImage]
  3. Right-Click on the "Picture" field and import a desired picture image [PicImage]
  4. Populated data in all other desired fields on the form [Note the values entered]
  5. Navigate the command button for [TestReportPM]
  6. Double-click to launch the report
  7. Validate the report opens successfully
  8. Validate the "Signature" field is populated with [SigImage], 'Crystal Report'
  9. Validate the "Picture" field is populated with [PicImage], as expected
  10. Validate all other fields populated in step 1c, are displayed as expected
  11. Submit the form
  12. Validate the form submits successful
  13. Navigate the command button for [TestReportCWS]
  14. Double-click to launch the report
  15. Validate the report opens successfully
  16. Validate the "Signature" field is populated with [SigImage], 'Crystal Report'
  17. Validate the "Picture" field is populated with [PicImage], as expected
  18. Validate all other fields populated in step 1c, are displayed as expected
  19. Submit the form
  20. Validate the form submits successfully
  21. Return to [TestForm]
  22. Select the row just submitted for edit
  23. Validate the "Signature" field is populated with [SigImage], as expected
  24. Validate the "Picture" field is populated with [PicImage], as expected
  25. Validate all other fields populated in step 1c, are displayed as expected
Topics
• Envelope Import • Envelope Export • Document Routing
Update 52 Summary | Details
'All Documents' widget - Progress Notes (Group and Individual)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • All Documents Widget
  • All Documents Widget Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • "Client A" must have more than one hundred records on file for 'Progress Notes (Group and Individual)'.
  • "Client A" must have one or more 'Ambulatory Progress Notes' records on file.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Ambulatory Progress Notes' form assigned.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  3. Validate all 'Progress Notes (Group and Individual)' records are displayed for the client (more than one hundred).
  4. Validate the 'Workflow Status' column contains either "Draft" or "Final" for each row.
  5. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  6. Validate all 'Ambulatory Progress Notes' records are displayed for the client.
  7. Validate the 'Time' field contains the proper time the note(s) were filed.
'All Documents' widget - Ambulatory Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
  • Console Widget Viewer
  • Practitioner Enrollment
  • Financial Eligibility
  • All Documents Widget
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Access the 'Practitioner Enrollment' form.
  13. Select the practitioner linked to the logged in user for view/update.
  14. Validate that all the required/ desired fields are populated correctly.
  15. Click [Categories/Taxonomy] tab.
  16. Select any existing row in 'Category/Taxonomy' field.
  17. Validate all required fields are populated.
  18. Click "Practitioner Credentials" button.
  19. Select "Credential A" from the list.
  20. Click [OK]
  21. Click [Add Practitioner Categories].
  22. Validate the 'Confirm' dialog contains "Saved. Please note: The changes will take effect when you submit the form." message.
  23. Click [OK].
  24. Click [Submit].
  25. Select "Client A" and navigate to the 'All Documents' view.
  26. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  27. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  28. Select the progress note for viewing.
  29. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  30. Click [Print]
  31. Select "Print Current" dropdown value.
  32. Validate the practitioner's credential "Credential A" is displayed on the printable form.
  33. Validate an [Append] button is displayed and click it.
  34. Validate the 'Append Progress Notes' form is displayed.
  35. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  36. Click [Submit].
  37. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  38. Click [Accept].
  39. Enter the password associated with the logged in user and click [Verify].
  40. Click [Close All] in the 'Console Widget Viewer'.
  41. Refresh the 'All Documents' widget.
  42. Select the progress note appended in the previous steps for viewing.
  43. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  44. Click [Close All].
Scenario 2: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client must be enrolled in an existing episode (Client A).
  • "Client A" must have more than one hundred records on file for 'Progress Notes (Group and Individual)'.
  • "Client A" must have one or more 'Ambulatory Progress Notes' records on file.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Ambulatory Progress Notes' form assigned.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  3. Validate all 'Progress Notes (Group and Individual)' records are displayed for the client (more than one hundred).
  4. Validate the 'Workflow Status' column contains either "Draft" or "Final" for each row.
  5. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  6. Validate all 'Ambulatory Progress Notes' records are displayed for the client.
  7. Validate the 'Time' field contains the proper time the note(s) were filed.
'All Documents' widget - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Pre Admit
Scenario 1: 'All Documents' widget - Validate 'Update Client Data' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Update Client Data' forms.
Steps
  1. Access the 'Admission' form.
  2. Admit a new client. This will be referred to as "Client A".
  3. Populate all required fields and some demographic data.
  4. Submit the form.
  5. Select "Client A" and access the 'Update Client Data' form.
  6. Validate the demographics fields display as filed.
  7. Update the desired demographics fields.
  8. Submit the form.
  9. Select "Client A" and access the 'Admission' form.
  10. Click [Edit] for the existing episode.
  11. Validate the updated demographics fields are displayed as filed.
  12. Update the desired demographics fields.
  13. Submit the form.
  14. Select "Client A" and access the 'Update Client Data' form.
  15. Validate the updated demographics fields are displayed as filed.
  16. Update the desired demographics fields.
  17. Submit the form.
  18. Navigate to the 'All Documents' view.
  19. In the 'All Documents' widget, select the 'Multi-Form Tab'.
  20. Validate four 'Update Client Data' records are displayed for each update done to the client's demographics.
  21. Click to view each record and validate the documents display as expected in the 'Console Widget Viewer'.
  22. Click [Close All].
Topics
• Progress Notes • All Documents Widget • Admission
Update 54 Summary | Details
Entity-Based Document Capture - Client ID and Episode
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Staff Document Capture
  • Entity-Based Document Capture
  • Batch Capture and Indexing
  • Client Document Capture
  • Document Capture
Scenario 1: Staff Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • There must be a practitioner defined (Practitioner A).
  • A document must exist for import.
Steps
  1. Access the 'Staff Document Capture' form.
  2. Enter "Practitioner A" in the 'Staff ID' field.
  3. Click [Launch POS Capture].
  4. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  5. Click [Import].
  6. Validate the 'Document Capture' opens in a new window.
  7. Select any value in the 'Document Type' field.
  8. Enter any value in the 'Document Description' field.
  9. Click [Capture] and [Browse].
  10. Locate the file to be imported and click [Open] and [Done].
  11. Validate the image displays.
  12. Click [Save].
  13. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Staff" in the 'Select Type' field.
  16. Select "Individual" in the 'Select All or Individual Staff' field.
  17. Select "Practitioner A" in the 'Select Staff' field.
  18. Click [Process].
  19. Locate and select the document that was saved in the previous steps.
  20. Validate the image displays.
  21. Click [Close All Documents], [Search] and [Close].
  22. Navigate back to the open 'Staff Document Capture' form.
  23. Click [Launch POS Capture].
  24. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?".
  25. Click [Import].
  26. Validate a second document capture window opens.
  27. Navigate back to the open 'Staff Document Capture' form.
  28. Click [Discard].
  29. Validate the document capture windows close and the form discards.
Scenario 2: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • In the "Document Management Defaults" form, select "Program" in the "Select Entity Types to Allow" field.
  • Select a performing provider and a program for the tests.
Steps
  1. Access the 'Entity-Based Document Capture' form.
  2. Select "Performing Provider" in the 'Entity Type' field.
  3. Enter the desired performing provider in the 'Entity' field in the format of "LAST,FIRST".
  4. Validate the 'Results' field displays the performing provider and select it.
  5. Click [Launch POS Capture].
  6. Import in a document saved as a file on the server.
  7. Validate the document renders on screen.
  8. Select the desired value in the 'Document Type' field.
  9. Enter the desired value in the 'Document Description' field.
  10. Click [Save].
  11. Validate that messages display indicating the document was successfully saved.
  12. Close the form.
  13. Access the 'Clinical Document Viewer' form.
  14. Select "Performing Provider" in the 'Entity' field.
  15. Select "Individual" in the 'Select All or Individual Performing Provider' field.
  16. Select the performing provider from the previous steps in the 'Select Performing Provider' field.
  17. Click [Process].
  18. Validate a row was added for the document that was just saved.
  19. View the document to validate it displays as it was captured.
  20. Close the form.
  21. Access the 'Entity-Based Document Capture' form.
  22. Select "Program" in the 'Entity Type' field.
  23. Enter the desired program in the 'Entity' field.
  24. Validate the 'Results' field displays the program and select it.
  25. Click [Launch POS Capture].
  26. Import in a document saved as a file on the server.
  27. Validate the document renders on screen.
  28. Select the desired value in the 'Document Type' field.
  29. Enter the desired value in the 'Document Description' field.
  30. Click [Save].
  31. Validate that messages display indicating the document was successfully saved.
  32. Close the form.
  33. Access the 'Clinical Document Viewer' form.
  34. Select "Program" in the 'Entity' field.
  35. Select "Individual" in the 'Select All or Individual Performing Program' field.
  36. Select the program from the previous steps.
  37. Click [Process].
  38. Validate a row was added for the document that was just saved.
  39. View the document to validate it displays as it was captured.
  40. Close the form.
Scenario 3: Perceptive Batch Capture and Indexing - JxBrowser enabled
Specific Setup:
  • Perceptive storage method must be utilized.
Steps
  1. Open the "Batch Capture and Indexing" form.
  2. Click "Capture" to create a new batch.
  3. Choose "Scanner" for the "Source".
  4. Click "Open Batch".
  5. Scan a document
  6. If Batch Verify is utilized, then click "Send To".
  7. If Batch Verify is not utilized, then click "Submit".
  8. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  9. Select the batch that was sent to this queue.
  10. Open the batch and click "Submit".
  11. Close form.
  12. Open the "Batch Capture and Indexing" form.
  13. Click "Capture" to create a new batch.
  14. Choose "File" for the "Source".
  15. Click "Browse" and browse to the location of where the file is stored on the server.
  16. Click "Open".
  17. Click "Open Batch".
  18. If Batch Verify is utilized, then click "Send To".
  19. If Batch Verify is not utilized, then click "Submit".
  20. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  21. Select the batch that was sent to this queue.
  22. Open the batch and click "Submit".
  23. Close form.
  24. Open "Chart Review" form for the client and episode that the documents were just scanned and imported for.
  25. Navigate to the form/category that you want to validate.
  26. Select a document that was scanned in.
  27. Validate that the document displays.
  28. Click the "Print" button.
  29. Print the document.
  30. Validate that the printed document matches what displayed on the viewer.
  31. Select a document that was imported in.
  32. Validate that the document displays.
  33. Click the "Print" button.
  34. Print the document.
  35. Validate that the printed document matches what displayed on the viewer.
  36. Open "Clinical Document Viewer".
  37. Validate you can view and print both the scanned and imported document.
Scenario 4: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: 'Save Was Successful.' and 'Document Added to Avatar!'
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select 'Individual' in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Topics
• Perceptive • Document Capture
Update 56 Summary | Details
Treatment Plan - PCL Date fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Required User List Management
Scenario 1: Treatment Plan - Validate 'Pending Approval' workflow with PCL date fields
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • Two users must be defined with associated staff members (User A & User B).
  • "User A" and "User B" must be defined as workflow users in the 'Required User List Management' form for the 'Treatment Plan'.
Steps
  1. Log into Avatar NX as "User A".
  2. Select “Client A” and access the ‘Treatment Plan’ form.
  3. Enter the desired date in the 'Plan Date' field.
  4. Enter any value in the 'Plan Name' field.
  5. Select any value in the ‘Plan Type’ field.
  6. Enter the desired date in the 'Plan End Date' field.
  7. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  8. Select "Draft" in the 'Treatment Plan Status' field.
  9. Click [Launch Plan].
  10. Add a problem, goal, objective, and intervention.
  11. Populate all required and desired fields.
  12. Click [Return to Plan] and [OK].
  13. Select "Pending Approval" in the 'Treatment Plan Status' field.
  14. Click [Submit].
  15. Validate that a "Confirm Document" message is displayed.
  16. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are not displayed.
  17. Click [Accept and Route].
  18. Validate a "Verify Password" message is displayed.
  19. Enter the password associated with the logged-in user in the 'Password' field.
  20. Click [Verify].
  21. Select the practitioner associated to "User A" as an approver and the practitioner associated to "User B" as an approver/supervisor.
  22. Click [Submit].
  23. Log out.
  24. Log into Avatar NX as "User B".
  25. Navigate to the 'My To Do's' widget.
  26. Click [Documents to Sign].
  27. Validate the To Do for "Client A" is displayed.
  28. Click [Review].
  29. Validate the 'Document Preview' contains the treatment plan data, without the 'PCL End Date' and 'PCL Finalized Date' fields.
  30. Click [Accept] and [Sign].
  31. Validate a "Verify Password" message is displayed.
  32. Enter the password associated with the logged-in user in the 'Password' field.
  33. Click [Verify].
  34. Validate the To Do for "Client A" is no longer displayed.
  35. Log out.
  36. Log into Avatar NX as "User A".
  37. Navigate to the 'My To Do's' widget.
  38. Click [Documents to Sign].
  39. Validate the To Do for "Client A" is displayed.
  40. Click [Review].
  41. Validate the 'Document Preview' contains the treatment plan data.
  42. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are appended to the end of the document. If there are multiple approvers, these fields will only become visible when the last approver goes to approve the document.
  43. Click [Accept] and [Sign].
  44. Validate a "Verify Password" message is displayed.
  45. Enter the password associated with the logged-in user in the 'Password' field.
  46. Click [Verify].
  47. Validate the To Do for "Client A" is no longer displayed.
Scenario 2: Treatment Plan - Validate 'Final' workflow with PCL Date fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • The logged in user must have an associated practitioner.
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter any value in the 'Plan Name' field.
  4. Select any value in the ‘Plan Type’ field.
  5. Enter the desired date in the 'Plan End Date' field.
  6. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  7. Select "Draft" in the 'Treatment Plan Status' field.
  8. Click [Launch Plan].
  9. Add a problem, goal, objective, and intervention.
  10. Populate all required and desired fields.
  11. Click [Return to Plan] and [OK].
  12. Select "Final" in the 'Treatment Plan Status' field.
  13. Click [Submit].
  14. Validate that a "Confirm Document" message is displayed.
  15. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed in the body of the document.
  16. Click [Accept and Route].
  17. Validate a "Verify Password" message is displayed.
  18. Enter the password associated with the logged-in user in the 'Password' field.
  19. Click [Verify].
  20. Select the practitioner associated to the logged in user as an approver.
  21. Click [Submit].
  22. Navigate to the 'My To Do's' widget.
  23. Click [Documents to Sign].
  24. Validate the To Do for "Client A" is displayed.
  25. Click [Review].
  26. Validate the 'Document Preview' contains the treatment plan data, with the 'PCL End Date' and 'PCL Finalized Date' fields in the body of the document.
  27. Click [Accept] and [Sign].
  28. Validate a "Verify Password" message is displayed.
  29. Enter the password associated with the logged-in user in the 'Password' field.
  30. Click [Verify].
  31. Validate the To Do for "Client A" is no longer displayed.
Topics
• Treatment Plan • Document Routing
Update 57 Summary | Details
The 'Form Deletion' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
  • All Documents Widget
  • Form Deletion (PM)
  • Table Deletion (PM)
  • Envelope Deletion (PM)
Scenario 1: 'All Documents Widget Definition' form
Specific Setup:
  • A modeled form has been deleted in the 'Form Deletion' form (Form A).
Steps
  1. Access the 'All Documents Widget Definition' form.
  2. Select "Add" in the 'Add or Edit Tab' field.
  3. Populate the required fields and click [File].
  4. Edit the tab that was just added.
  5. Validate that the tab displays as it was data entered.
  6. Click [Forms Assigned].
  7. Validate "Form A" is not displayed in the list.
  8. Navigate to the 'Multi-Document Tab' section.
  9. Select "Add" in the 'Add or Edit Tab' field.
  10. Populate the required fields and click [File].
  11. Edit the tab that was just added.
  12. Validate that the tab displays as it was data entered.
  13. Navigate to the 'Multi-Progress Notes Tab' section.
  14. Select "Add" in the 'Add or Edit Tab' field.
  15. Populate the required fields and click [File].
  16. Edit the tab that was just added.
  17. Validate the tab displays as it was data entered.
  18. Navigate to the 'All Documents Widget Definition' section.
  19. Select "Add" in the 'Add or Edit Widget' field.
  20. Validate the [New Row] and [Delete Row] buttons are enabled.
  21. Populate the required fields and click [File].
  22. Edit the widget that was just added.
  23. Validate the widget displays as the data was entered with dark grey text.
  24. Close the form.
'Form and Table Documentation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation
Scenario 1: Form and Table Documentation - "All Forms"
Steps
  1. Access the 'Form and Table Documentation' form.
  2. Select "Form" in the 'Type of Documentation' field.
  3. Select "All Forms" in the "Individual or All Forms" field.
  4. Click [Process]
  5. Validate "Option ID" is displayed on the report for all forms.
  6. Click [Close] and close the form.
Topics
• All Documents Widget Definition • Modeling • Forms
Update 59 Summary | Details
Avatar - RxConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Launch RxConnect
Scenario 1: Avatar "NIAM" user login - Verify "RxConnect" launch and login when "RXConnect" NIAM Login functionality "Disabled"
Specific Setup:
  • Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality configured by Netsmart.
  • RxConnect must be installed and configures to communicate with myAvatar
  • The "RxConnect" application is currently configured 'not' to allow login authentication via "NIAM"
  • An Avatar user has two types of login user ID's setup for logging into Avatar, that were set up in form "User Definition"
  • [UserIdA], a standard Avatar user with a password and assigned with the following setup
  • In "Select Forms for User Access"
  • The user is assigned form "Launch RxConnect" under the "Avatar PM" folder
  • Under the "RxConnect" folder the user is assigned an ' RxConnect' specific "Access" permission, for example "Pharmacist",
  • [UserIdB], a "NIAM" type user, configured with the following setup:
  • Field "User External Login" set to "Yes"
  • Field "External Login ID" is populated with the 'External login ID' assigned by a "(ODIC) Identity Provider". For example, provider "Okta".
  • In "Select Forms for User Access"
  • Assigned form "Launch RxConnect", located under the "Avatar PM" folder
  • Under the "RxConnect" folder, the user is assigned an 'RxConnect' specific "Access" permission. For example "Pharmacist"
Steps
  1. At the "Avatar" login screen, click "Login with Enterprise Credentials"
  2. At the "External Login Provider" screen, populate the "Netsmart ID" field with the "External login ID" assigned to [UserIdB] in the setup.
  3. At the Avatar login screen, select the "System" code to log into, from the "System" code field
  4. Enter the password assigned and validate login to Avatar is successful
  5. Search for and open the "Launch RxConnect" form
  6. Click the [Launch RxConnect] button
  7. Validate the "RxConnect" application is launched and the user is automatically logged in
  8. At the top of the screen under the menu's
  9. Validate the "User" field, indicates [UserIdB]
  10. Validate the "Access" field, indicates the access permission stated in the setup
  11. On the menu, click "Logout"
  12. Validate there is a user login and password prompt displayed now, in order to log back in:.
  13. In the "UserName" field, enter the [UserIdB] (the Avatar user set up for "NIAM" set with "RxConnect" access)
  14. In the "Password" field, enter any value or either leave it blank, as they don't get a standard password, as noted in the setup
  15. Click [Login]
  16. Validate access is denied with message, "UserID does not exist in any facilities or is not active in any facility.", as expected.
  17. In the "UserName" field, enter the [UserIdA] (the standard Avatar user set with "RxConnect" access).
  18. In the "Password" field, enter their assigned password
  19. Click [Login]
  20. Validate the user is logged in successfully, as expected
  21. Exit the application
Scenario 2: Avatar "NIAM" user login - Verify "RxConnect" launch and login when "RXConnect" NIAM Login functionality "Enabled"
Specific Setup:
  • Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality configured by Netsmart.
  • RxConnect must be installed and configures to communicate with myAvatar
  • The "RxConnect" application is currently configured to 'allow' login authentication via "NIAM" login
  • Have a user with an "External Login ID" and password assigned to them by a "(ODIC) Identity Provider", For example, provider "Okta".
  • In form "User Definition", a user ID has been defined for that user [UserId] and has the following configured settings:
  • Field "User External Login" set to "Yes"
  • Field "External Login ID" is populated with their assigned 'External login ID'
  • In "Select Forms for User Access"
  • In the "Avatar PM" folder, the user is assigned form "Launch RxConnect"
  • In the "RxConnect" folder the user is assigned an ' RxConnect' specific "Access" permission, for example "Pharmacist"
Steps
  1. At the "Avatar" login screen, Click "Login with Enterprise Credentials"
  2. At the "External Login Provider" screen, populate the "Netsmart ID" field with the external login ID assigned [UserId] and click [Next]
  3. At the Avatar login screen, select the "System" code to log into, from the "System" code field
  4. Validate login is successful into Avatar
  5. Search for and open the "Launch RxConnect" form
  6. Click the [Launch RxConenct] button
  7. Validate the "RxConnect" application is launched and the user is logged in
  8. At the top of the screen under the menu's
  9. Validate the "User" field, indicates [UserId]
  10. Validate the "Access" field, indicates the access permission stated in the setup
  11. On the menu, click "Logout"
  12. Validate there is just a [Login] button and no user login or password prompts
  13. Click [Login]
  14. Validate the user is automatically logged back in successfully
  15. Log out of the application
Topics
• RxConnect
Update 60 Summary | Details
Product Update installer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Global Data
Scenario 1: "Avatar" Monthly/Quarterly Release Methodology (Internal testing) - Validations
Steps
  1. Internal Testing Only
Topics
• Table • Cache • Update Install
Update 61 Summary | Details
Append Documents - Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Append Progress Notes
Scenario 1: Append Documents - validate appending to progress notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" must have a progress note on file that has been approved via document routing (Progress Note A).
  • The 'Progress Notes' widget must be accessible on the HomeView.
Steps
  1. Access the 'Append Documents' form.
  2. Select the form type for "Progress Note A" in the 'Form Type' field.
  3. Select "Client A" in the 'Entity' field.
  4. Enter the current date in the 'From Date' and 'End Date' fields.
  5. Select "Progress Note A" in the 'List of Documents' field.
  6. Click [Display Document].
  7. Validate the details for "Progress Note A" are displayed as expected.
  8. Click [Close All Documents and Exit].
  9. Enter the desired value in the 'New Comments to Be Appended in the Original Document' field.
  10. Click [Submit].
  11. Validate the 'Confirm Document' dialog is displayed and the document is displayed with the appended notes.
  12. Click [Accept].
  13. Enter the user's password and click [Verify].
  14. Validate the form files successfully.
  15. Select "Client A" and access the 'Progress Notes' widget.
  16. Validate "Progress Note A" is displayed with the appended comments with a proper date format.
Topics
• Progress Notes (Group And Individual) • Document Routing • Widgets
Update 71 Summary | Details
Assigning or changing an MR#
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Last Movement
  • Dynamic Form - Delete Last Movement
  • Call Intake
  • Change MR#
  • Client Ledger
Scenario 1: Admission - Validate 'Assign Permanent MR #' functionality
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
Steps
  1. Access the 'Call Intake' form.
  2. Enter the desired last name in the 'Last Name' field.
  3. Enter the desired first name in the 'First Name' field.
  4. Select "Male" in the 'Sex' field.
  5. Click [Search].
  6. Validate the 'Search' field states: "No matches found".
  7. Click [New Client].
  8. Select the desired value in the 'Call Or Walk-In' field.
  9. Select the desired value in the 'Caller Type' field.
  10. Enter the desired date in the 'Call Date' field.
  11. Enter the desired time in the 'Call Time' field.
  12. Select the desired program in the 'Program' field.
  13. Select desired value in the 'Disposition' field.
  14. Click [Submit].
  15. Select the new client in the 'Recent Clients' field.
  16. Validate the client ID contains "P" and the client name is the name entered in step 1
  17. Open the "Admission" form
  18. Validate the "Assign MR#?" dialog is displayed
  19. Click [Yes] to assign a permanent MR#
  20. At the next dialog, click [Yes] to assign the next available ID number
  21. At the "Admission" screen
  22. Validate the "Client Name" field is populated with name entered in step 1
  23. Populate the required fields and any other desired fields on the form
  24. Click to submit the form
  25. Validate the form submits successfully
  26. At the home screen, in the "Recent Clients" list
  27. Validate the client has now been assigned a permanent MR#
  28. Click to open their "Chart" or "Client Dashboard"
  29. Validate the header section displays the clients name and their new permanent MR# in parentheses
  30. For example: TEST CLIENT (25)
Scenario 2: Change MR# - Form Validations
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
  • Have two active clients with permanent MR#'s assigned in the system for testing:
  • [ClientA]
  • The client currently has no documents that are pending approval
  • [ClientB]
  • The client currently has two pending documents approval [Doc1] and [Doc2], routed to user [TestUser]
  • [TestUser] has the "My To Do's" widget on their homeview
  • Log in a [TestUser]
Steps
  1. Access the 'Change MR#' form
  2. Select [ClientA] in the 'Client ID' field.
  3. Click [Assign MR#].
  4. Validate a message is displayed stating: Auto Assign Next ID Number?
  5. Click [Yes].
  6. Validate the 'New Client ID#' field contains the new ID for [ClientA]. Make a note of the new ID number
  7. Click [Submit].
  8. Validate the form submits successfully
  9. At the Home screen, search for [ClientA]
  10. Validate [ClientA] is found and their new client ID noted in step 1 is displayed
  11. Click to open "Chart" or "Client Dashboard"
  12. Validate the header section displays the clients name and their new client ID# in parentheses
  13. For example: Test ClientA (28)
  14. Access the 'Change MR#' form
  15. Select [ClientB] in the 'Client ID' field.
  16. Click [Assign MR#].
  17. Validate a message is displayed stating: Auto Assign Next ID Number?
  18. Click [Yes].
  19. Validate the 'New Client ID#' field contains the new ID for [ClientA]. Make a note of the new ID number
  20. Click [Submit].
  21. Validate an error message stating "This client has documents which are currently pending approval. The MR number cannot be changed until these documents are finalized or rejected."
  22. Click [OK]
  23. Close the form
  24. Navigate to the "My To Do's" widget on the home view
  25. Locate the 'To Do's' for [Doc1] and [Doc2] waiting for review
  26. Click each 'To Do', review and either accept or reject the documents
  27. Validate the 'To Do's' are removed from the 'To Do' list
  28. Access the 'Change MR#' form
  29. Select [ClientB] in the 'Client ID' field.
  30. Click [Assign MR#].
  31. Validate a message is displayed stating: Auto Assign Next ID Number?
  32. Click [Yes].
  33. Validate the 'New Client ID#' field contains the new ID for [ClientB]. Make a note of the new ID number
  34. Click [Submit].
  35. At the Home screen, search for [ClientB]
  36. Validate [ClientB] is found and their new client ID noted in step 5 is displayed
  37. Click to open "Chart" or "Client Dashboard"
  38. Validate the header section displays the client's name and their new client ID# in parentheses. For example: Test ClientB (30)


Scenario 3: Assign Permanent MR# - form validations
Specific Setup:
  • Have a system with a modeled table that exists on the system with following fields set in form "Table Definition":
  • 'Does this table require an associated table for the storage of binary information' set to "Yes" and with the "Binary Storage Table Name" field populated with a value
  • "Create Pre-Filing Report Table" set to "Yes" and the field "Pre-Filing Report Schema/Table" populated with a binary table name value
Steps
  1. Access the 'Call Intake' form.
  2. Enter the desired last name in the 'Last Name' field.
  3. Enter the desired first name in the 'First Name' field.
  4. Select "Male" in the 'Sex' field.
  5. Click [Search].
  6. Validate the 'Search' field states: "No matches found".
  7. Click [New Client].
  8. Select the desired value in the 'Call Or Walk-In' field.
  9. Select the desired value in the 'Caller Type' field.
  10. Enter the desired date in the 'Call Date' field.
  11. Enter the desired time in the 'Call Time' field.
  12. Select the desired program in the 'Program' field.
  13. Select desired value in the 'Disposition' field.
  14. Click [Submit].
  15. Select the new client in the 'Recent Clients' field.
  16. Validate the client ID contains "P".
  17. Access the 'Assign Permanent MR' form.
  18. Validate the 'Name' field contains the name entered in the previous steps.
  19. Validate the 'Temporary ID' field contains "P".
  20. Click [Assign Permanent MR #].
  21. Click [Yes].
  22. Validate the 'Assigned ID' field does not contain "P". Make a note of the ID number
  23. Click [Submit].
  24. Select the new client in the 'Recent Clients' field.
  25. Validate the client ID does not contain "P" and the new number noted in step 3 is assigned, as expected
Table Definition - new table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
  • Envelope Definition (CWS)
  • Form Definition (CWS)
Scenario 1: "Table Definition" Form - New table addition validations
Specific Setup:
  1. Have a system with modeled tables existing in both "PM" and "CWS" applications
  2. Using a database query program, connect to the "CWS" namespace and run the following query:
  3. 'Select tablecsmid from SQLUser.RadPlusCSMTable ORDER BY tablecsmid ASC'
  4. This will output all the table ID numbers (tablecsmid) for the tables existing in that namespace in numerical order. Make a note of the output. (Note: "SQL Query" in the cache "System Management Portal" can be used to execute the query, if access is accessible)
  5. Repeat the last step connected to the "PM" namespace. Make a note of the output
  6. Compare the output from the two namespaces in step 1 and 2
  7. Locate table with an ID# that exists in CWS that does not exist in PM
  8. Note the name and number of the table: For example: [CWSTestTableA (19)]
Steps
  1. In "Avatar CWS" open form "Table Definition"
  2. Select the table noted in the setup [CWSTestTableA]
  3. Navigate to the prompt 'Does this table require an associated table for the storage of binary information' field and set it to "Y", if it's not already
  4. In the 'Binary Storage Table Name' field enter a value (i.e. "Cwsbinary_Test"), if there's not a value already.
  5. Make note of the 'Binary Storage Table Name' field value [Cwsbinary_Test]
  6. Make a note of the envelope name in the "Envelope" field [CWSenvelopeA]
  7. Submit the form and exit
  8. In "Avatar CWS" open form "Envelope Definition" and select [CWSenvelopeA]
  9. Make a note of the value in the "SQL Schema" field [SYSTEMA]
  10. Exit the form
  11. Re-open form "Envelope Definition"
  12. Enter a new envelope name [CWSenvelopeB] and click to create the new envelope
  13. Select a value in the "Entity Database" field
  14. In the "SQL Schema" field, enter a different value than the one noted in n step 2a. [SYSTEMB]
  15. Set the 'Include Envelope within CDR' field to "Yes"
  16. Submit the form
  17. In "Avatar CWS" open form "Table Definition"
  18. In the search field, enter the name of the 'Binary Storage Table Name' field name noted in step 1c. For this test [Cwsbinary_Test]
  19. Click [New Avatar CWS Table]
  20. When prompted to select an "Envelope", select the envelope noted in step 2, [CWSenvelopeA]
  21. Click [OK]
  22. Validate the entry is accepted and the user is navigated to the table definition screen to create the new table
  23. Validate the "Table Name" field is populated with [Cwsbinary_Test]
  24. Populate all the required fields and any other desired fields
  25. Submit the form
  26. Validate the table submits successfully
Topics
• Client Management • Admission • Assign MR# • Change MR# • Modeling
2023 Update 91 Summary | Details
'Connect/Disconnect Application Namespace'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
  • Connect/Disconnect Application Namespace
Scenario 1: "Connect/Disconnect Application Namespace" form - Validate form submission and application connection error corrections
Specific Setup:
  • Logged in user has access to the "Connect/Disconnect Application Namespace" form
  • Logged in user has access to the "Application Namespace Connections Validation" form
Steps
  1. Open form "Applications Namespace Connection Validations":
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespaces:
  3. If the message "There are one or more application namespace errors", is displayed
  4. Click [Process] to review the details.
  5. Make a note of any application errors stated in the results. For example, an application "Mapping" type error and note which application for example "CWS", "MSO" that the error pertains to.
  6. Exit the form.
  7. Open the "Connect/Disconnect Application Namespace" form:
  8. From the "Application" field, select the application noted in step 1, that the error was reported in:
  9. For an application currently configured with its "(CDR) Clinical Data Repository" enabled
  10. Select "Yes" in the field "Clinical Data Repository (CDR) Link", otherwise select "No".
  11. In the "Connect or Disconnect" field, select:
  12. "Connect/Maintain Connection/Repair Connection".
  13. Submit the form (Note submission can take some time):
  14. Validate submission is successful.
  15. Open form "Applications Namespace Connection Validations":
  16. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  17. Validate there is now a message stating "There are no Application/Namespace errors".
  18. Close the form.
Topics
• Database Management • Cache
2023 Update 104 Summary | Details
Report Definitions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition Export
  • Report Definition Deletion (PM)
  • Report Definition Import (PM)
Scenario 1: 'Report Definition': (MSE) Multi-Server Environment (Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have a "Report Definition" export file, exported from a system outside the current MSE testing systems. [ExternalReport]
  • As the testing user, have separate avatar session open for each system (BLD, UAT, and LIVE), and log in each environment
Steps
  1. In LIVE,
  2. Open form "Report Definition Import"
  3. Select [ExternalReport], the report definition exported from an external system, as noted in the setup
  4. Validate import is not permitted, with a message indicating that the report does not exist in BLD environment
  5. In BLD
  6. Open form "Report Definition Import"
  7. Select [ExternalReport], validate import is permitted
  8. Click to import the report
  9. Validate import is successful
  10. Open form "Report Definition Export"
  11. Select [ExternalReport]
  12. Export the report [ExternalReportExport] and save the file
  13. In LIVE
  14. Open form "Report Definition Import"
  15. Select [ExternalReportExport],
  16. Validate import is now permitted, now that it has been exported from BLD.
  17. Import the report
  18. Validate import is successful
  19. In BLD
  20. Open form "Report Definition" and create a new definition [ReportA] with two or more parameters
  21. Submit the report and validate submission is successful
  22. Open "Report Definition Export"
  23. Export the definition [ReportExportA] and save the file
  24. In one of the other systems, for this test LIVE is used
  25. Open form "Report Definition Import"
  26. Import [ReportExportA] as 'New'
  27. Validate import is successful
  28. In BLD
  29. Open "Report Definition" to edit [ReportA]
  30. Delete one of the existing parameters.
  31. Submit the form
  32. Return to "Report Definition"
  33. Create another new report definition with one or more parameters [ReportB]
  34. Submit the form and validate submission is successful
  35. Open "Report Definition" Export
  36. Select [ReportB] for export
  37. Validate export is successful [ReportExportB]
  38. In LIVE
  39. Open "Report Definition Import"
  40. Import [ReportExportB]
  41. Validate import is successful
  42. In BLD
  43. Open form "Report Definition Deletion"
  44. Select [ReportB]
  45. Validate a warning message indicating that deleting this report definition will also delete from the following Avatar instances via web service calls, LIVE, is displayed. Click [OK]
  46. Click the "Yes" check box to confirm deletion
  47. Click [Submit]
  48. Validate the "Report Definition Deletion Web Service Dialog", is presented and indicates "In addition to the current environment, this report definition has been deleted from the following environments: LIVE"
  49. Click [OK]
  50. Open "Report Definition"
  51. Search for [ReportB]
  52. Validate is not found, as expected. Close the form
  53. In LIVE
  54. Open "Report Definition"
  55. Validate [ReportB] cannot be found, as expected
  56. Close the form
  57. Open "Report Definition" Import
  58. Click [Select Report Import File] and select [ReportExportB]
  59. Validate a critical error preventing import is displayed, as the report definition does not exist in BLD yet since it was deleted in step 8
  60. In BLD
  61. Open "Report Definition Import"
  62. Click [Select Report Import File] and select [ReportExportB]
  63. Validate is import is successful
  64. In LIVE
  65. Open "Report Definition Import"
  66. Click [Select Report Import File] and select [ReportExportB]
  67. Validated is import is successful now, as the report exists in BLD
  68. Close the form
  69. In LIVE
  70. Re-open "Report Definition" Import
  71. Click [Select Report Import File] and select [ReportExportB] again as "New"
  72. Validate is import is blocked, with message "This report already exists within this system. New copies must be created in the BLD environment first, then moved to the other environments"
  73. Open "Report Definition Export""
  74. Select [ReportB] for export
  75. Validate export is blocked with the following message "This form is not accessible in this environment"
  76. Click [OK] and close the form
  77. In BLD, repeat step 12b
  78. Export the file
  79. Validate export from BLD is successful, as expected
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Definition (MSO)
  • Envelope Definition (MSO)
  • Table Definition (MSO)
Scenario 1: 'Modeling ': (MSE) Multi-Server Environment (Modeled Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have an existing envelope [TestEnvelope] containing a form [TestForm], that exists in BLD and also existing in ether UAT or LIVE. For this test UAT is used
  • [TestForm] contains one or more desired fields on the form, but does not yet contain a "Display" type section, a "Label" field or a 'Report" field
  • In BLD, open form "Form Definition" to edit [TestForm]
  • In the existing main section, add a "Label" and a "Report" object
  • Now add a new section, and choose 'Display' as the type of section.
  • Submit the form and validate submission is successful
  • As the testing user, open a separate avatar session for each system (BLD, UAT, and LIVE), and log in
Steps
  1. In BLD
  2. Open form "Envelope Export" and select [TestEnvelope]
  3. Export the envelope and save the export file in a desired location
  4. Validate export is successful
  5. Log into either LIVE or UAT. For this test UAT is used
  6. Open "Envelope Import" and import [TestEnvelope] as an overwrite
  7. Validate the import is successful
  8. In BLD,
  9. Open "Form Definition" and select [TestForm]
  10. Navigate the "Section Definition" section and delete the "Display" section
  11. Navigate to the "Object Definition" section and delete the "Label" and the "Report" fields
  12. Submit the form.
  13. Validate submission is successful
  14. Staying in BLD
  15. Create a new envelope in "Envelope Definition" [NewTestEnvelop]
  16. Create a new table in "Table Definition" [NewTestTable] with any desired field types
  17. Create a new form in "Form Definition" [NewTestForm], that includes the fields from the table
  18. Validate submissions are successful
  19. Open "Envelope Export"
  20. Export [NewTestEnvelope] and save the file
  21. In UAT
  22. Open "Envelope Import" and select [NewTestEnvelope] for import as 'New'
  23. Validate the import is successful
  24. Staying in UAT
  25. Open [NewTestForm] for any client
  26. Populate the fields and submit the form
  27. Validate submission is successful
  28. In BLD,
  29. Open form "Table Deletion"
  30. Select [NewTestTable]
  31. Validate a message " The selected table is used within one or more forms. It must be removed from all forms prior to deletion."
  32. Close the form
  33. Open form 'Table Definition' to edit [NewTestTable]
  34. Navigate to the "Column Definition" section
  35. Select one of the table columns and click "Delete" to remove it from the table
  36. Validate deletion is blocked, with a message "This field is in use in the following environments and cannot be deleted: UAT"
  37. Click [OK] and close the form
  38. Open form "Form Definition"
  39. Select [NewTestForm] for deletion
  40. Validate an error is displayed blocking submission indicating is there is data present in the form in UAT.
  41. Close the form
  42. In UAT
  43. Open form "NewTestForm"
  44. Select the row filed in step 4 in the pre-display
  45. Click [Delete] to remove the row
  46. In BLD
  47. Open form 'Form Deletion' and select [TestForm] for deletion
  48. Validate a message is displayed that contains "Deleting this form will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  49. Click [OK]
  50. At prompt "Are you sure that you want to delete this form", click the "Yes" checkbox
  51. Submit the form
  52. Validate the"Form Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  53. Click [OK]
  54. Validate submission is successful
  55. Open form "Table Deletion" and select [NewTestTable] for deletion
  56. Validate a message is displayed that contains "Deleting this table will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  57. Click [OK]
  58. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  59. Submit the form
  60. Validate the"Table Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this table has been deleted from the following environments: UAT
  61. Click [OK]
  62. Validate submission is successful
  63. Open form Envelope Deletion' and select [NewTestEnvelope] for deletion
  64. Validate a message is displayed that contains "Deleting this envelope will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion??"
  65. Click [OK]
  66. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  67. Submit the form
  68. At prompt "Are you sure that you want to delete this Envelope", click the "Yes" checkbox
  69. Submit the form
  70. Validate the"Envelope Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  71. Validate submission is successful
  72. In UAT
  73. Open "Form Definition" and search for [NewTestForm]
  74. Validate the form is not found, as expected
  75. Open "Table Definition" and search for [NewTestTable]
  76. Validate the table is not found, as expected
  77. Open "Envelope Definition" and search for [NewTestEnvelope]
  78. Validate the envelope is not found, as expected
Modeled form - diagnosis fields
Scenario 1: Modeled Forms - Validate "Diagnosis History (ICD-10)" Table Alias field data
Specific Setup:
  • Have a Modeled form [TestForm], configured in 'Table Definition" to use the "Alias Table", "Diagnosis History (ICD10)"
  • [FieldA] is mapped to alias table column "Diagnoses Search (Row1)"
  • [FieldB] is mapped to alias table column "Diagnoses Search (Row2)"
  • [FieldC] is mapped to alias table column "Diagnoses Search (Row3)"
  • Have a client [TestClient] with up to three diagnosis, submitted in form "Diagnosis"
  • Diagnosis (Row1) in the form, is populated with diagnosis value [Diag1]
  • Diagnosis (Row2) in the form, is populated with diagnosis value [Diag2]
  • Diagnosis (Row3) in the form, is populated with diagnosis value [Diag3]
  • Have access to the "Diagnosis" form
Steps
  1. Open [TestForm]
  2. Select [TestClient]
  3. Navigate to the section of the form where the mapped diagnosis fields reside
  4. Validate [FieldA] is displayed with previous diagnosis [Diag1] submitted in the set up, as expected
  5. Validate [FieldB] is displayed with previous diagnosis [Diag2] submitted in the set up, as expected
  6. Validate [FieldC] is displayed with previous diagnosis [Diag3] submitted in the set up, as expected
  7. Navigate [FieldA]
  8. Search for and select a new diagnosis [NewDiag1]
  9. Navigate [FieldB]
  10. Search for and select a new diagnosis [NewDiag2]
  11. Navigate [FieldC]
  12. Search for and select a new diagnosis [NewDiag2]
  13. Submit the form
  14. Validate the form submits successfully
  15. Select [TestClient]
  16. Open form "Diagnosis"
  17. Navigate to the "Diagnoses" grid
  18. Double click to select Row ID "1"
  19. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag1], submitted in step 1c
  20. Double click to select Row ID "2"
  21. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag2], submitted in step 1d
  22. Double click to select Row ID "3"
  23. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag3], submitted in step 1e
  24. Close the form
Topics
• Report Definition Import • Modeling • Diagnosis
2023 Update 105 Summary | Details
Program/User Defined – Program Maintenance Entities
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Document
  • Entity-Based Document Capture
  • Document Management Definition
  • Program User Defined Program Maintenance
  • Document Capture
Scenario 1: Validate the functionality of the form "Delete Document"
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document.
Steps
  1. Open form "Delete Document":
  2. Select "Client" in the "Entity Type" field.
  3. Select "Individual" in the "Include" field.
  4. In the "Entity" field, select the client that has the document.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Click the "Select Form" drop down list.
  10. Select the row pertaining to the clients document.
  11. Click [Delete].
  12. Click [Yes], confirming the deletion.
  13. Open form "Clinical Document Viewer":
  14. Select "Individual" from the "Select All or Individual Client" field,
  15. In the "Select Client" field, select a client that had the document,
  16. Select the episode in the "Episode" field,
  17. Click [Process],
  18. Validate the row with the document that was deleted, is not present.
  19. Open the form originally used to create the deleted document:
  20. Select the row originally used to submit the document,
  21. Validate the row has been reverted to "Draft" status.
Scenario 2: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • In the "Document Management Defaults" form, select "Program" in the "Select Entity Types to Allow" field.
  • Select a performing provider and a program for the tests.
Steps
  1. Access the 'Entity-Based Document Capture' form.
  2. Select "Performing Provider" in the 'Entity Type' field.
  3. Enter the desired performing provider in the 'Entity' field in the format of "LAST,FIRST".
  4. Validate the 'Results' field displays the performing provider and select it.
  5. Click [Launch POS Capture].
  6. Import in a document saved as a file on the server.
  7. Validate the document renders on screen.
  8. Select the desired value in the 'Document Type' field.
  9. Enter the desired value in the 'Document Description' field.
  10. Click [Save].
  11. Validate that messages display indicating the document was successfully saved.
  12. Close the form.
  13. Access the 'Clinical Document Viewer' form.
  14. Select "Performing Provider" in the 'Entity' field.
  15. Select "Individual" in the 'Select All or Individual Performing Provider' field.
  16. Select the performing provider from the previous steps in the 'Select Performing Provider' field.
  17. Click [Process].
  18. Validate a row was added for the document that was just saved.
  19. View the document to validate it displays as it was captured.
  20. Close the form.
  21. Access the 'Entity-Based Document Capture' form.
  22. Select "Program" in the 'Entity Type' field.
  23. Enter the desired program in the 'Entity' field.
  24. Validate the 'Results' field displays the program and select it.
  25. Click [Launch POS Capture].
  26. Import in a document saved as a file on the server.
  27. Validate the document renders on screen.
  28. Select the desired value in the 'Document Type' field.
  29. Enter the desired value in the 'Document Description' field.
  30. Click [Save].
  31. Validate that messages display indicating the document was successfully saved.
  32. Close the form.
  33. Access the 'Clinical Document Viewer' form.
  34. Select "Program" in the 'Entity' field.
  35. Select "Individual" in the 'Select All or Individual Performing Program' field.
  36. Select the program from the previous steps.
  37. Click [Process].
  38. Validate a row was added for the document that was just saved.
  39. View the document to validate it displays as it was captured.
  40. Close the form.
Scenario 3: Program User Defined Program Maintenance entity - Create Modeled Form
Specific Setup:
  • Create a user modeled form for the "Program User Defined Program Maintenance" entity.
  • Using "Envelope Definition", create a new envelope for the user modeled form.
  • Using "Table Definition", create a table that also includes a "Draft/Final (Document Routing)" field.
  • Using "Form Definition", define the user modeled form.
  • Refresh menus.
  • Using "Document Routing Setup", enable document routing for the user modeled form.
  • Using "Document Management Definition", create a new form for the "Program User Defined Program Maintenance".
Steps
  1. Open the user modeled form created for this test.
  2. Populate the form and mark the "Draft/Final" as "Draft".
  3. Route the document to an approver.
  4. Log in as the approver.
  5. Navigate to the "ToDo" widget.
  6. Approve the document.
  7. Open "Clinical Document Viewer".
  8. Locate the document that was just finalized.
  9. View the document and validate it displays as it was stored.
  10. Print the document and validate it prints as it displays.
Scenario 4: Program Entity - Validation
Specific Setup:
  • Using the "Document Management Defaults" form, select "Program" in the "Select Entity Types Allowed" field.
  • Using the "Document Management Definition" form, add a new form for the "Program" entity.
Steps
  1. Open the "Entity-Based Document Capture" form.
  2. Scan a document and set the "Document Type" to "Program".
  3. Save the document.
  4. Import a document and set the "Document Type" to "Program".
  5. Open the "Clinical Document Viewer" form.
  6. Set "Select Type" to "Program".
  7. Elect "All" or "Individual" programs.
  8. Locate the documents that were just scanned/imported.
  9. Validate the document displays.
  10. Validate the document prints.
Scenario 5: Program User Defined Program Maintenance Entity - Validation
Specific Setup:
  • Using "Document Management Defaults", define "Program - User Defined Program Maintenance" and "Program" entity types.
  • Using "Document Management Definition", define forms for the "Program" entity and "Program User Defined Program Maintenance" entities.
  • Create a user modeled form for the "Program User Defined Program Maintenance" entity.
  • Using "Envelope Definition", create a new envelope for the user modeled form.
  • Using "Table Definition", create a table that also includes a "Draft/Final (Document Routing)" field.
  • Using "Form Definition", define the user modeled form.
  • Refresh menus.
  • Using "Document Routing Setup", enable document routing for the user modeled form.
Steps
  1. Open the user modeled form created for this test.
  2. Populate the form and mark the "Draft/Final" as "Draft".
  3. Route the document to an approver.
  4. Log in as the approver.
  5. Navigate to the "ToDo" widget.
  6. Approve the document.
  7. Open "Clinical Document Viewer".
  8. Locate the document that was just finalized.
  9. View the document and validate it displays as it was stored.
  10. Print the document and validate it prints as it displays.
Scenario 6: Clinical Document Viewer - "Void & Copy" documents
Specific Setup:
  • Perceptive is enabled.
  • In "User Definition", validate user has permissions to void documents.
  • The entity being tested must have imported or scanned documents on file.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select the desired entity in the "Entity Type field".
  3. Select "Individual" in the 'Select All or Individual' entity field.
  4. Select the desired entity (Client ID, Staff ID, Family ID, etc).
  5. Click [Process].
  6. Select a document and view it.
  7. Click [Void] and then [Void & Copy].
  8. Validate 'Form Type' & 'Change Description' displays as expected for the selected document.
  9. Select a target entity to copy the document to.
  10. If the entity is a client, select the desired episode in the 'Select Episode' field.
  11. Click [Void].
  12. Validate the document list now has a Status of "Void" for the original document.
  13. Select the "Search" section.
  14. Select the target entity.
  15. Click [Process].
  16. Validate the copied document is now in the document list for this entity.
  17. View the copied document and validate it displays as expected.
  18. Click [Void] and then [Void & Copy].
  19. Validate 'Form Type' & 'Change Description' displays as expected for the selected document.
  20. Click [Cancel Void].
  21. Click [Close All Documents].
  22. Select the "Search" section.
  23. Click [Close].
Scenario 7: 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'.
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'.
Perceptive - Document Viewing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Capture
  • Client Document Capture
Scenario 1: Validate Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be installed and enabled.
Steps
  1. Select a client from "myClients" or from the Client search.
  2. Open the client's dashboard.
  3. Using "Document Capture", scan or import in a document.
  4. Select the desired episode to assign the document to.
  5. Validate the correct Episode displays in the "Document Properties" pane.
  6. Capture and save the document.
  7. View the document using "Clinical Document Viewer" or the Chart to ensure it has the correct episode designation and that it displays.
Scenario 2: Client Chart - Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Import a document and select an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was imported.
  11. Print the document and validate it prints as it was imported.
  12. Close the forms.
Scenario 3: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 4: Chart Review - Document Capture - Scan Non-episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify it was non-episodic.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 5: Chart Review - Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 6: Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Document Routing - Saving documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Results Importing
  • View Results
Scenario 1: Progress Notes (Group and Individual) - Document Routing with Crystal Report Template
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' form with the following:
  • "Yes" selected in the 'Use Crystal Report Template' field.
  • A crystal report template selected in the 'Crystal Report' field.
  • User must have the 'My To Do's' widget and 'All Documents' widget accessible on their home view.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "New Service" in the 'Progress Note For' field.
  5. Populate all other required and desired fields.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit Note].
  8. Validate the "Confirm Document" dialog is displayed with the crystal report template.
  9. Click [Sign and Route].
  10. Select the practitioner associated to the logged in user in the 'Supervisor' field.
  11. Click [Submit].
  12. Enter the password associated to the logged in user and click [Verify].
  13. Validate a message is displayed stating: Note Filed.
  14. Click [OK] and close the form.
  15. Navigate to the 'My To Do's' widget.
  16. Click [Documents To Sign].
  17. Validate a To-Do is displayed for the progress note filed in the previous steps.
  18. Click [Review].
  19. Validate the 'Document Preview' displays the crystal report template.
  20. Click [Accept] and [Sign].
  21. Enter the password associated to the logged in user and click [Verify].
  22. Validate the To-Do is no longer displayed.
  23. Click [Close].
  24. Select "Client A" and navigate to the 'All Documents'' widget.
  25. Click [Refresh].
  26. Validate the progress note is displayed and select it.
  27. Validate the 'Console Widget Viewer' displays the crystal report template.
  28. Click [Close All].
Scenario 2: Import Lab Result
Specific Setup:
  • A Results file for importing must be obtained/created for use in testing.
  • This results file should have a facility that matches the facility in the MSH segment.
  • This results file should have a client ID in the PID segment that matches up to a client in the system the test is to be performed in.
  • This results file should be in a .txt format.
  • Place this file on the cache server and note the path name where it's stored.
Steps
  1. Using the "Results Importing" form
  2. Import the file designated in setup by setting "File Path For Import" to the file path name.
  3. Open the "View Results" form.
  4. Validate you can view the result that was just imported.
Topics
• Documentation • Perceptive • Document Capture • Document Routing • Program • Clinical Document Viewer • NX • Results
2023 Update 109 Summary | Details
Entity Information Display - 'Approximate Number of Characters to Display' fields
Scenario 1: Entity Information Display
Specific Setup:
  • The user must have access to the 'Entity Information Display' form.
Steps
  1. Access the 'Entity Information Display' form.
  2. Select "Client" from the 'Entity Database' field.
  3. Select "Three" from the 'Number of Additional Columns to Display' field.
  4. Enter the desired value in the 'Entity Name Header Text' field.
  5. Validate the 'Approximate Number of Characters to Display for Entity Name' field does not accept more than two digits.
  6. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Name' field.
  7. Select the desired value form the 'Entity Information Display Column 1' field.
  8. Validate the 'Entity Information Display Column 1 Header Name' field populates and displays as expected.
  9. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 1' field does not accept more than two digits.
  10. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 1' field.
  11. Select the desired value from the 'Entity Information Display Column 2' field.
  12. Validate the 'Entity Information Display Column 2 Header Name' field populates and displays as expected.
  13. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 2' field does not accept more than two digits.
  14. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 2' field.
  15. Select the desired value from the 'Entity Information Display Column 3' field.
  16. Validate the 'Entity Information Display Column 3 Header Name' field populates and displays as expected.
  17. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 3' field does not accept more than two digits.
  18. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 3' field.
  19. Click [Submit].
Topics
• Entity Information Display • NX
2023 Update 110 Summary | Details
Document Management Defaults - Path name for documents
Scenario 1: Document Management Defaults - form validation
Specific Setup:

Internal Testing Only

Steps

Internal Testing Only

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

Internal Testing Only

Steps

Internal Testing Only
Topics
• Document Management
2023 Update 113 Summary | Details
NX - Dynamic Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: Dynamic Form - Validations
Specific Setup:
  • The logged in user [TestUserA], has access to the following forms:
  • "Basic Troubleshooting", "Treatment Plan", "Member Enrollment", "Treatment Plan", plan, User Definition", "User Role Definition" and "View Definition"
  • In form "User Definition"
  • Have another user [TestUserB], that can be used for testing
  • User [TestUserB] is not logged in
  • Log in as [TestUserA]
Steps
  1. Open form "Basic Troubleshooting"
  2. Click the [Test Dynamic Forms] button
  3. Validate message "Test Successful", is displayed
  4. Click the [OK] button
  5. Set the "Duration (minutes)" field to "1"
  6. Click the [Submit] button
  7. Verify the message window "Submitting... Please Wait", is displayed
  8. Wait "1" Minute
  9. Verify the message window "Submitting... Please Wait" displays and closes the form
  10. Validate user is returned to their home screen
  11. Open the "Treatment Plan" form and select the desired client in the "Select Client" search field
  12. Populate the "Plan Date" field
  13. Populate any other desired fields
  14. Set the "Draft/Final" to "Draft"
  15. Click the Launch Plan button
  16. Click the [Add New Problem] button
  17. Click the [Return to Plan] button
  18. Validate the "Plan Saved" message is displayed and click [OK]
  19. Set the "Draft/Final" field to "Final"
  20. Click [Submit]
  21. Validate the message "Cannot finalize plan until the following required fields are completed"
  22. Click the OK button
  23. Populate any missing required fields
  24. Click the [Submit] button
  25. Validate the form files successfully
  26. Open the Member Enrollment - Avatar MSO / Membership Management form
  27. Populate the "Last Name" field with a name that is not on file yet as a member
  28. Populate the "First Name" field
  29. Populate the Sex" field
  30. Click the Search button
  31. Validate the message "Search Results - No Matches found", is displayed
  32. Click [OK] button
  33. Click the New Client button
  34. Click the "Auto Assign ID Number" dialog, "Yes" button
  35. Validate the "Name" field is populated as expected
  36. Populate any other desired fields
  37. Submit the form
  38. Validate the form files successfully
  39. Open form "User Definition"
  40. Select [TestUserB]
  41. Click the "Generate New Password" button
  42. Make a note of the temporary password populated in the "System Generated Password" field
  43. Submit the form
  44. Log out as [TestUserA]
  45. Log in as [TestUserB]
  46. Validate the user is promoted with the dialog, "Your current password is system generated. You must enter a new password".
  47. Click [OK]
  48. At the "New password entry" dialog
  49. Populate the "Enter New Password" field
  50. Populate the "Re-enter New Password" field with same password
  51. Click [OK]
  52. Validate [TestUserB] is logged in successfully
  53. Open form "User Role Definition"
  54. Click [Select User Role]
  55. Validate the "Select User Role" dialog is displayed
  56. Click [Cancel]
  57. Validate user is returned to the form
  58. Click [Select User Role]
  59. Validate the "Select User Role" dialog is displayed
  60. From the "Select one of the following" field
  61. Select a desired user role and click [OK]
  62. Validate the information for the user role selected, is populated as expected
  63. Close the form
  64. At the "Confirm Close" dialog
  65. Click [Yes]
  66. Open form "View Definition"
  67. Click "Select View"
  68. Validate "Select Views" dialog is displayed
  69. Click [Cancel]
  70. Validate user is returned to the form
  71. Click "Select View"
  72. Validate "Select Views" dialog is displayed
  73. Select a view form the "Views" list
  74. Click [OK]
  75. Validate the information for the view selected, is populated as expected
  76. At the "Confirm Close" dialog
  77. Click [Yes]
  78. Validate the user is returned to the homeview
Topics
• Forms • Cache • NX
2023 Update 118 Summary | Details
'Change User ID' form
Scenario 1: "Change User ID" - Validate reverting a UserID to its previous Value
Specific Setup:
  • [ChangedUserB] is a user whose UserID had been changed from [ChangedUserA], via the "Change User ID" form
  • Have a form, for example, a user based product or modeled form [TestForm] that enabled for document routing. For this test product, form "Ambulatory Progress Notes" is used
  • [ChangedUserB] has been routed a "To Do" document for client [TestClient] via form [TestForm] and has approved it, to create the document [TestDoc]
  • [ChangedUserB] has been routed another "To Do" document that is still in their "To Do" list
  • Have a report or query to display data in the "SYSTEM.Doc_documents" table and include the "data_entry_user_id" field [ReportA]
  • Have a report or query to display data in the table used in [TestForm] and include the "data_entry_user_id" field. For this test, the "SYSTEM.cw_patient_notes" table is used [ReportB]
  • A test [TestUser] and [ChangedUserB] have access to forms "Change UserID", "User Definition"
  • Log in as [TestUser]
Steps
  1. Open form "Change UserID"
  2. Select [ChangedUserB] in the "User" field
  3. Validate the "Old User ID" field is populated with [ChangedUserB]
  4. Click the "Previous" radio button in the "New or Previous ID" field
  5. Validate the "Select Previous ID" field is enabled
  6. Click the drop down list
  7. Select the users original ID [ChangedUserA] from the list
  8. Submit the form
  9. Validate the form submits successfully
  10. Open form "User Definition"
  11. In the "Select User" field, search for [ChangedUserB]
  12. Validate a message is displayed "User ID [ChangedUserB] is disabled. Only User Description can be updated"
  13. Click [OK]
  14. Validate the "Deactivate User" field is selected and disabled
  15. In the "Select User" field, search for [ChangedUserA]
  16. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  17. Close the form
  18. Log out as [TestUser]
  19. At the Login screen
  20. Log in as [ChangedUserB]
  21. Validate login is unsuccessful
  22. At the Login screen
  23. Log in as [ChangedUserA] using the password that was assigned to [ChangedUserB]
  24. Validate login is successful
  25. At the Home View, navigate to the "My To Do's" list
  26. Validate the "To Do" for the document routed for [TestForm] is present in their "To Do" list, as expected
  27. Generate the report to display data in the "SYSTEM.Doc_documents" table
  28. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  29. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  30. Validate other data fields are populated as expected
  31. Generate the report to display data tabled associated with [TestForm]
  32. Locate the row containing submitted for [TestClient] in the setup
  33. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  34. Validate other data fields are populated as expected
  35. Open form "User Definition"
  36. In the "Select User" field, search for [ChangedUserA]
  37. Change the password to a new password
  38. Submit the form
  39. Log out as [ChangedUserA]
  40. Log in as [TestUser]
  41. Open form "Change UserID"
  42. Select [ChangedUserA] in the "User" field
  43. Validate the "Old User ID" field is populated with [ChangedUserA]
  44. Click the "Previous" radio button in the "New or Previous ID" field
  45. Validate the "Select Previous ID" field is enabled
  46. Click the drop down list
  47. Select the users original ID [ChangedUserB] from the list
  48. Submit the form
  49. Validate the form submits successfully
  50. Open form "User Definition"
  51. In the "Select User" field, search for [ChangedUserA]
  52. Validate a message is displayed "User ID [ChangedUserA] is disabled. Only User Description can be updated"
  53. Click [OK]
  54. Validate the "Deactivate User" field is selected and disabled
  55. In the "Select User" field, search for [ChangedUserB]
  56. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  57. Close the form
  58. Log out as [TestUser]
  59. At the login screen
  60. Log in as [ChangedUserA]
  61. Validate login is unsuccessful
  62. At the login screen
  63. Log in as [ChangedUserB] using the new password assigned [ChangedUserA] in step 8
  64. Validate login is successful
  65. Generate the report to display data in the "SYSTEM.Doc_documents" table
  66. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  67. Validate the data_entry_user_id" field now indicates [ChangedUserB], as expected
  68. Validate other data fields are populated as expected
  69. Generate the report to display data tabled associated with [TestForm]
  70. Locate the row containing submitted for [TestClient] in the setup
  71. Validate the "data_entry_user_id" field now indicates [ChangedUserB], as expected
  72. Validate other data fields are populated as expected
User Merge File Import
Scenario 1: User Merge File Import' form (Multiple Users) - create new user
Specific Setup:
  • Have four users for testing
  • [TestUser1], [TestUser2], [TestUser3], [TestUser4],
  • Have a "User Import File" file created [TestImport]
  • Have the import file set up to merge the following users to new user:
  • [TestUser1] and [TestUser2] to a new user [Merged1]
  • [TestUser3] and [TestUser4] to a new user [Merged2]
  • Note: (For file format and requirements for a "User Merge" file, see Wiki page: https://wikihelp.ntst.com/EHR/myAvat...ge_File_Import")
  • Have a report or query to display data in the "SYSTEM.RadPlusUserLink" table
Steps
  1. Open form "User File Import"
  2. Click [Select User Import File]
  3. Navigate to the location of the [TestImport] file
  4. Select the file and click [OK]
  5. In the "User Merge File Scan Results" field, validate there are no messages blocking the import
  6. Click [Process User Merge File]
  7. Validate the merge is successful. [Please Note: by default, the new merged user's temporary password will be their user name after the merge is processed]
  8. Log in as [TestUser1]
  9. Validate login is not successful, as expected
  10. Log in as [TestUser2]
  11. Validate login is not successful, as expected
  12. Using their user name as their temporary password, log in as [Merged1]
  13. Validate the user is prompted to change their password
  14. Enter a new password
  15. Validate login is successful
  16. Repeat step 2 and 3 using [TestUser2] and [TestUser3]
  17. Validate the results are same, as expected
  18. Using their user name as their temporary password, log in as [Merged2]
  19. Validate the user is prompted to change their password
  20. Enter a new password
  21. Validate login is successful
  22. Run the report or query to display data in the "SYSTEM.RadPlusUserLink" table
  23. Locate the row for [Merged1]
  24. Validate the value in the "disable_value" field indicate "No" and note the value in their 'system_link_id" field
  25. Locate the row for [Merged2]
  26. Validate the value in the "disable_value" field indicate "No"
  27. Validate the value in their 'system_link_id" is unique, a different value than what was noted for [Merged1] in step 6a
Topics
• Change User ID • User Merge
2023 Update 121 Summary | Details
All Documents Widget Definition- Select/Deselect forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
Scenario 1: 'All Documents Widget Definition' Form- (Forms attached to a menu from another application) - 'Forms Assigned' Validations
Specific Setup:
  • Have two forms in an application that can be used for testing. For this test, "Avatar PM" is used. [PMForm1] and [PMForm2]
  • In another application, (e.g. Avatar CWS), open form "Attach Other Application Form to Menu"
  • In the "Application" field select the 'Avatar PM' application and in the "Form To Attach" choose the form [PMForm1]
  • In the" Menu to Place Form Under" field choose a desired " CWS" menu for the "PM" form
  • Update "Form Description' field with a new desired name, that will appear on the "CWS" menu [PMForm1CWS]
  • Submit the form
  • Repeat the previous step for [PMForm2], assigning the form a different name [PMForm2CWS], in the 'Form Description' field
  • The logged in user has the [AllDocWidget] is their home view
  • The logged in user has access to form "All Document Widget Definition"
Steps
  1. Open the "All Documents Widget Definition" form.
  2. Select the "Multi-Form Tab" section and select "Add" to create a new tab
  3. Populate the "Tab ID" with a desired value and enter a desired name for the tab [CrossNamespaceTab], in the "Tab Name" field
  4. Click the 'Forms Assigned" button.
  5. Validate both forms PM forms that were attached to a CWS menu in the set up, [PMForm1CWS] and [PMForm2CWS], are available for selection
  6. Validate neither of the forms are currently selected
  7. Select [PMForm1CWS] and leave [PMForm2CWS] unselected
  8. Select any other form [TestForm] leaving any others unselected
  9. Click [OK] to save the changes
  10. Click the "Forms Assigned" button
  11. Validated [PMForm1CWS] is selected and [PMForm2cws] is not, as expected
  12. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  13. Now deselect form [PMForm1CWS] and select [PMForm2CWS]
  14. Click [OK] to save the changes
  15. Click the "Forms Assigned" button
  16. Validated [PMForm2CWS] is selected and [PMForm1CWS] is not, as expected
  17. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  18. Click [OK]
  19. Click [File] to create the tab and save the changes made
  20. Validate submission is successful and exit the form
  21. Open the "All Documents Widget Definition" form.
  22. Select the "Multi-Form Tab" section and select "Edit"
  23. Select tab [CrossNamespaceTab] for edit
  24. Click the 'Forms Assigned" button
  25. Validated [PMForm2CWS] is selected and [PMForm1CWS] is not, as expected
  26. Validate [TestForm] is still selected and all other forms are still unselected, as expected
  27. Click [OK]
  28. Exit the form
All Document Widget - forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
Scenario 1: 'All Document Widget"- (Form attached to a menu from another application) - "Tab" Form/Data validations
Specific Setup:
  • Have a form in any application that can be used for testing. For this testing "Avatar CWS" is used. [CWSForm]
  • In another application, (e.g. Avatar PM), open form "Attach Other Application Form to Menu'
  • In the "Application" field select the 'Avatar CWS' application and in the "Form To Attach" choose [CWSForm]
  • In the "Menu to Place Form Under" choose a desired "PM" menu for the "CWS" form
  • Update "Form Description" field as a desired distinguishable name for "CWS" form that will appear on the "PM" menu [CWSFormPM]
  • Submit the form
  • In form "All Documents Widget Definition", have an all document widget defined [AllDocWidget]
  • The logged in user has the [AllDocWidget] as their home view
  • The logged in user has access to form "All Document Widget Definition" and [CWSForm] and [CWSFormPM]
Steps
  1. Open the "All Documents Widget Definition" form.
  2. Select the "Multi-Form Tab" section and select "Edit"
  3. From the "Select Tab" field, select any existing Tab [CrossNamespaceTab]
  4. Click the "Forms Assigned" button
  5. Select [CWSFormPM], the form attached from a "PM" forms list
  6. Do not select [CWSForm] from the "CWS" forms list, the form used to attach to the other application menu
  7. Click [OK]
  8. Click the "Forms Assigned" button
  9. Validate [CWSformPM] is selected and [CWSForm] is not, as expected
  10. Click [OK] to save the changes
  11. Click [File] to save the tab changes
  12. Navigate the home view
  13. Select a desired client [TestClient]
  14. From the "PM" menu open form [CWSFormPM]
  15. Populate the desired fields and submit the form
  16. At the homeview, click to refresh the [AllDocWidget]
  17. Click the [CrossNamespaceTab] tab
  18. Validate a data row is present in the widget for the row submitted in step 2
  19. Validate "Form Description" field for the row is [CWSForm] as expected. [Note: the name from the original form name used to attach to the other application menu, will always display]
  20. Validate all other column data is displayed, as expected
  21. Navigate back to the home view
  22. Select a desired client [TestClient]
  23. This time from the "CWS" menu, open form [CWSForm]
  24. Populate the desired fields and submit the form
  25. Navigate back to the [AllDocWidget] and click to refresh the widget
  26. Click the [CrossNamespaceTab] tab
  27. Validate a data row is present in the widget for the row submitted in step 4
  28. Validate "Form Description" field for the row is [CWSForm] as expected.
  29. Validate all other column data is displayed, as expected
All document Widget - form data rows
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Risk Level Update
Scenario 1: 'All Documents' widget - Form data row validations
Specific Setup:
  • A client is enrolled in an existing episode [TestClient]
  • Have two modeled forms [FormA] and [FormB]
  • [FormA] is based on a table that is "Date" sorted. [Note: this is configured with prompt "Is This Table Date Sorted" set to "Yes" in "Table Definition"]
  • [FormB] is not based on a table that is "Date Sorted"
  • Have any other desired form [FormC],
  • [FormC] has many rows of data submitted for a client[TestClient], for example four hundred rows or more
  • Have the registry setting "Enable Risk Level Functionality" enabled
  • Have access to the "Risk Level Update" for [TestClient].
  • Have an "All Documents Widget" created [AllDocsWidget], in form " All Documents Widget Definition"
  • Have [FormA], [FormB], [FormC] and the "Risk Level Update" from, added for selection in any tab in the widget, For this test, the "All Forms" tab is used
  • The logged in user has access to all forms in the setup above and the "All Documents Widget Definition" form
  • The logged in user has the "All Document Widget" on their home view
Steps
  1. Select a client [TestClient]
  2. Open [FormA] (Modeled Form 'Date Sorted')
  3. Select an episode
  4. Populate the required "Date Sorted" date field with a date other than the current date
  5. Populate any desired fields
  6. Submit the form
  7. Validate the form files successfully
  8. Note the current date and the "Date Sorted" date entered in step 2b
  9. Open [FormB] (Modeled form not 'Date Sorted')
  10. Select an episode
  11. Populate any desired fields
  12. Submit the form
  13. Validate the form files successfully
  14. Note the submission the date and time
  15. Open the "Risk Level Update" form
  16. Add a row the "Risk Level Change" grid
  17. Populate the "Date of Change" field. Make note of the date value.
  18. Populated other fields, as required
  19. Submit the form
  20. Validate the form submits successfully
  21. At the home view, select [TestClient]
  22. Navigate to the "All Documents Widget" and click the "Refresh" button
  23. Click the "All Forms" tab
  24. Select [FormA] from the 'Form Description' field.
  25. Validate the "Form Description" field is populated with the form name for [FormA]
  26. Select the episode from the "Episode" field
  27. Validate the "Date" column field value, is populated with the "Date Sorted" date noted in step 2d
  28. Validate the "Time" column field value is 'not' populated. [This modeled form based on a table that is "Date Sorted". By design, for tables that are date sorted, the "Date" field will be populated with the sort date instead of the "Date Entry Date" and the "Time" field will be left unpopulated]
  29. Validate each of the columns are populated, as expected
  30. Select [FormB] from the 'Form Description' field.
  31. Validate the "Form Description" field is populated with the form name for [FormB]
  32. Select the episode from the "Episode" field
  33. Validate the "Date" column is populated with the date noted in step 3, which is the 'Date Entry Date'
  34. Validate the "Time" field is populated, as expected with time noted in step 3, which is the "Date Entry Time"
  35. Validate each of the columns are populated, as expected
  36. Select the "Risk Level Update" from the 'Form Description' field.
  37. Validate the "Form Description" field is populated with the form name for [FormA]
  38. Select the episode from the "Episode" field
  39. Validate the "Date" column is populated with "Date of Change" date noted in step 4.[Note: This product form is based on a table that is "Date Sorted". By design, for tables that are date sorted, the "Date" field will be populated with the sort date instead of the "Date Entry Date" and the "Time" field will be left unpopulated]
  40. Validate the "Time" field is 'not' populated, as expected. [Note: as the date displayed in "Date" column field is the data sorted date not the date entry date, by design, the "Time" field value will be blank]
  41. Validate other columns are populated, as expected
  42. Select [FormC] from the 'Form Description' field.
  43. Validate in the right-hand corner of the widget, a counter is displayed indicting "50 of xxx rows"
  44. For example, for this test "50 of 450 rows" is displayed
  45. Validate all "50" rows are displayed, as expected
  46. In the center of the widget, at the bottom
  47. Validate there are left arrow and right arrow navigation buttons bracketing the number of pages of data. For example: < 1 2 3 4 5 >
  48. Validate the page "1" navigation link is currently highlighted
  49. Click the right arrow navigation button again
  50. Validate the next 50 rows are displayed along with previous rows, as expected
  51. Validate in the lower right corner, the counter changes to "100 of 450 rows"
  52. Validate the page "2" navigation link is currently highlighted
  53. Click the right arrow navigation button again
  54. Validate the next 50 rows are displayed along with previous rows, as expected
  55. Validate the counter changes to "200 of 450 rows"
  56. Validate the page "3" navigation link is currently highlighted
  57. Click the right arrow navigation button again
  58. Validate the next 50 rows are displayed along with previous rows, as expected
  59. Validate the counter changes to "250 of 450 rows"
  60. Validate the page "4" navigation link is currently highlighted
  61. If applicable, repeat the last step by clicking the right arrow till the last page is displayed
  62. Validate the next 50 rows are always displayed along with previous rows, as expected
  63. Validate the counter changes to "300 of 450", "350 of 450", "400 of 450" etc., as expected
  64. Validate the page number navigation link increments by one for each page, and is highlighted
Topics
• Forms • All Documents Widget Definition • All Documents Widget
2023 Update 123 Summary | Details
Modeled Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form w/ Multi Iteration Section
  • Program Maintenance
Scenario 1: Validate filing Modeled forms that contain "Multiple Iteration" sections with inactive and active programs
Specific Setup:
  • The test system contains multiple system codes.
  • A modeled form has been created that is client related and contains two dictionaries mapped to the 'Program' dictionary, one on the main section and one on a multiple iteration section. Also include a dictionary not mapped to the program dictionary.
  • Test user has access to the modeled form.
  • Use the modeled form to create a record for desired client. Select an active program in the main section of the form, noting the program. In the multiple iteration section, create at least two rows with active programs, noting the programs.
  • Program Maintenance: Set the programs to 'Inactive'.
Steps
  1. Open the modeled form for the client.
  2. Validate that the program in the main section displays as inactive.
  3. Select the multiple integration section and verify that the programs display as inactive.
  4. Close the form.
  5. Open 'Program Maintenance' and make all the programs active again, filing after each program.
  6. Close the form.
  7. Open the modeled form for the client.
  8. Validate that the program in the main section displays as active.
  9. Select the multiple integration section and verify that the programs display as active.
  10. Close the form.
Topics
• Modeling • NX
2023 Update 127 Summary | Details
'Define EHI' - 'EHI Export' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • EHI Export
Scenario 1: EHI Export - Field Validations
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Validate the 'Forms Included in EHI Export' field is displayed. This will contain a list of forms that file to a table that has a 'PATID' field.
  4. Validate the 'Integrated Application Assessments to Include in EHI Export' field is displayed. This will contain a list of all integrated CareFabric assessments (if configured).
  5. Validate a 'Save' button is displayed. This will be used to save the above definitions.
  6. Navigate to the "Export EHI" section.
  7. Validate a message is displayed stating: Warning: This option allows an organization to export all EHI related information in this system. This can be completed for an individual client/patient or the entire database. Additionally, users can choose a date range to only export information entered into the system during a specific time period. Please note, a complete database extract may have performance implications and should not be done during peak business hours. Additionally, users should ensure that the location they choose to export is both secured and with ample space to accommodate the extracts.
  8. Validate the 'Export the Following' field is displayed and contains the following options:
  9. 'Data and Documentation' - this will export a documentation file for all forms/assessments defined in the "Define EHI" section and files for all applicable data on file for the selected client(s).
  10. 'Data Only' - this will export files for all applicable data on file for the selected client(s) based on the forms/assessments defined in the "Define EHI" section.
  11. 'Documentation Only' - this will export a documentation file for all forms/assessments defined in the "Define EHI" section.
  12. Validate the 'Select Client' field is displayed. This gives the user the ability to export EHI for a specific client.
  13. Validate the 'Entered During Start Date' and 'Entered During End Date' fields are displayed. This gives the user the ability to export EHI for a particular date range.
  14. Validate the 'Select Export Location' field is displayed.
  15. Validate the 'Reason For Export' field is displayed.
  16. Validate the 'Process' button is displayed. This will be used to initiate the export.
  17. Close the form.
Scenario 2: EHI Export - Export Data and Documentation
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
  • A client is enrolled in an existing episode and has data filed in multiple forms & integrated application assessments (Client A).
  • Additional clients must be enrolled in existing episodes and have data on file in multiple forms & integrated application assessments.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Data and Documentation" in the 'Export the Following' field.
  10. Enter the desired date in the 'Entered During Start Date' field.
  11. Enter the desired date in the 'Entered During End Date' field.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: You do not have a Client selected. Proceeding with this export will export data for ALL clients that currently exist in the database. This can result in a large amount of data being created on the myAvatar server. Are you sure that you want to proceed with this export?
  16. Click [Yes].
  17. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  18. Click [OK].
  19. Navigate to the directory of the export file.
  20. Validate a 'form_documentation' file is displayed.
  21. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  22. Close the 'form_documentation' file.
  23. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  24. Validate each file contains the appropriate data for the selected date range.
  25. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
  26. Navigate back to the 'EHI Export' form.
  27. Validate "Data and Documentation" is selected in the 'Export the Following' field.
  28. Validate the 'Entered During Start Date' and 'Entered During End Date' fields no longer contain a value.
  29. Select "Client A" in the 'Select Client' field.
  30. Click [Process].
  31. Validate a message is displayed stating: You do not have a date range selected. Proceeding will export all data regardless of the date it was created. This can result in a large amount of data being created on the myAvatar server. Are you sure you want to proceed with this export?
  32. Click [Yes].
  33. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  34. Click [OK] and close the form.
  35. Navigate to the directory of the export file.
  36. Validate a 'form_documentation' file is displayed.
  37. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  38. Close the 'form_documentation' file.
  39. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  40. Validate each file contains the appropriate data for "Client A".
  41. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
Scenario 3: EHI Export - Export Documentation Only
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Documentation Only" in the 'Export the Following' field.
  10. Validate the 'Select Client' field becomes disabled.
  11. Validate the 'Entered During Start Date' and 'Entered During End Date' fields become disabled.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  16. Click [OK] and close the form.
  17. Navigate to the directory of the export file.
  18. Validate a 'form_documentation' file is displayed.
  19. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  20. Close the file.
Scenario 4: EHI Export - Export Data Only
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
  • A client is enrolled in an existing episode and has data filed in multiple forms & integrated application assessments (Client A).
  • Additional clients must be enrolled in existing episodes and have data on file in multiple forms & integrated application assessments.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Data Only" in the 'Export the Following' field.
  10. Enter the desired date in the 'Entered During Start Date' field.
  11. Enter the desired date in the 'Entered During End Date' field.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: You do not have a Client selected. Proceeding with this export will export data for ALL clients that currently exist in the database. This can result in a large amount of data being created on the myAvatar server. Are you sure that you want to proceed with this export?
  16. Click [Yes].
  17. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  18. Click [OK].
  19. Navigate to the directory of the export file.
  20. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  21. Validate each file contains the appropriate data for the selected date range.
  22. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
  23. Navigate back to the 'EHI Export' form.
  24. Validate "Data Only" is selected in the 'Export the Following' field.
  25. Validate the 'Entered During Start Date' and 'Entered During End Date' fields no longer contain a value.
  26. Select "Client A" in the 'Select Client' field.
  27. Click [Process].
  28. Validate a message is displayed stating: You do not have a date range selected. Proceeding will export all data regardless of the date it was created. This can result in a large amount of data being created on the myAvatar server. Are you sure you want to proceed with this export?
  29. Click [Yes].
  30. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  31. Click [OK] and close the form.
  32. Navigate to the directory of the export file.
  33. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  34. Validate each file contains the appropriate data for "Client A".
  35. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
Scenario 5: EHI Export - Define EHI
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK] and close the form.
  8. Access the 'EHI Export' form.
  9. Validate the "Define EHI" section is displayed.
  10. Validate the 'Forms Included in EHI Export' field contains the form(s) saved in the previous steps.
  11. Validate the 'Integrated Application Assessments to Include in EHI Export' field contains the assessment(s) saved in the previous steps.
  12. Close the form.
Topics
• EHI Export
2023 Update 128 Summary | Details
Guardiant- "Avatar Licensing" graph
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
  • View Global Data
  • General / Avatar Licensing Graph
Scenario 1: Guardiant Metric "Analytics" Data - Validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application
Steps
  1. Open form "Guardiant"
  2. Click [Test Daily Collection]
  3. Click [Yes] to the warning message
  4. Validate message "Test Succeeded" is displayed
  5. Click [Test Metrics Collection]
  6. Click [Yes] to the warning message
  7. Validate message "Test Succeeded" is displayed
  8. Log into "Guardiant"
  9. At the "Client Search", select the desired client account number
  10. In the right-hand corner, click "Analytics"
  11. Navigate down to "General/Avatar Licensing" graph
  12. In the right corner of the graph set the date range to the desired range, for example "60" days
  13. Click the 'Refresh' button in the graph
  14. In graph, mouse over the most recent date in the graph
  15. Validate the date and values displayed for the following statistics, are as expected
  16. Number of Named Users
  17. Number of application logins
  18. In graph, mouse over the oldest date in the graph
  19. Validate the date and values displayed for the following statistics, are as expected
  20. Number of Named Users
  21. Number of application logins
Topics
• Guardiant
2023 Update 129 Summary | Details
User Role Definition - forms permissions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: User Role Definition - "Select Forms for User Access" validations
Specific Setup:
  • In form "User Role Definition", have a role [TestRole] created that can be used for testing
  • Logged in user has access to form "User Role Definition"
Steps
  1. Open form "User Role Definition"
  2. Click [Select User Role]
  3. Select [TestRole]
  4. Click [Select Forms for User Access]
  5. In the form's selection tree dialog:
  6. For each folder, navigate to the selection box to the right of the arrow. For example folders, "Avatar PM", "Avatar CWS"
  7. Click in the selection box till the box is empty, to order to remove all permissions to forms in that folder
  8. Click the arrow next to the folder to expand it
  9. Validate the form selection box for each form in the folder is not populated, as expected
  10. Click [OK] to save the changes
  11. Submit the form
  12. Validate a message is presented with a warning message that states "No forms are selected for this role, are you sure you want to continue?"
  13. Click "Yes" to submit the form
  14. At the "Form Return" dialog, click "Yes" to return to the form
  15. Click [Select User Role]
  16. Select [TestRole]
  17. Click [Select Forms for User Access]
  18. In the form's selection tree:
  19. Validate the selection box to the right of the arrow for each folder is not populated, as expected
  20. Click the arrow next to the folder to expand it
  21. Validate the form selection box for each form in the folder is not populated, as expected
  22. Staying in the form's selection tree dialog:
  23. For each folder, navigate to the selection box to the right of the arrow
  24. Click in the box once to select "RW" read/write access
  25. Now, click the arrow next to the folder to expand it
  26. Validate the form selection box for each form in the folder is populated with "RW", as expected
  27. Click [OK] to save the changes
  28. Submit the form
  29. At the "Form Return" dialog, click "Yes" to return to the form
  30. Click [Select User Role]
  31. Select [TestRole]
  32. Click [Select Forms for User Access]
  33. For each folder, navigate to the selection box to the right of the arrow
  34. Validate the selection box is populated with "RW", as expected
  35. Now, click the arrow next to the folder to expand it
  36. Validate the form selection box for each form in the folder is populated with "RW", as expected
  37. Staying in the form's selection tree dialog:
  38. For each folder, navigate to the selection box to the right of the arrow
  39. Click in the box once to select "R" read/write access
  40. Now click the arrow next to the folder to expand it
  41. Validate the form selection box for each form in the folder is populated with "R", as expected
  42. Click [OK] to save the changes
  43. Submit the form
  44. At the "Form Return" dialog, click "Yes" to return to the form
  45. Click [Select User Role]
  46. Select [TestRole]
  47. Click [Select Forms for User Access]
  48. For each folder, navigate to the selection box to the right of the arrow
  49. Validate the selection box is populated with "R", as expected
  50. Now, click the arrow next to the folder to expand it
  51. Validate the form selection box for each form in the folder is populated with "R", as expected
  52. Close the form
  53. Re-open form "User Role Definition"
  54. Click [Select User Role]
  55. Select [TestRole]
  56. Click [Select Forms for User Access]
  57. In the form's selection tree dialog:
  58. Navigate to one of the form selection folders, for this example "Avatar PM" is used, and click the arrow next to folders selection box to expand the folder
  59. Now select a subfolder on that folder and click the arrow next to it to expand that folder
  60. Click the arrow to expand one of the subfolder under that folder
  61. For one of the forms in that subfolder [FormA], click the form selection box till the box is empty
  62. For another form in that subfolder [FormB], click the form selection box till the box is populated with "RW"
  63. For another one of the forms in the folder [FormA], click the form selection box till the box is populated with "R"
  64. Click [OK] to save the changes
  65. Submit the form
  66. At the "Form Return" dialog, click "Yes" to return to the form
  67. Click [Select User Role]
  68. Select [TestRole]
  69. Click [Select Forms for User Access]
  70. In the form's selection tree dialog
  71. Navigate to back to the subfolder selected with specific form permissions in step 2b
  72. Click the arrow next to the folder's selection box to expand the folder to display the forms
  73. Validate the form selection box for [FormA] is empty, as expected
  74. Validate the form selection box for [FormB] is contains "RW", as expected
  75. Validate the form selection box for [FormC] is contains "R", as expected
  76. Close the form
Topics
• User Role Definition • NX
2023 Update 130 Summary | Details
Form Bundles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Simultaneous Bundle
Scenario 1: Simultaneous Form Bundle Validation
Specific Setup:
  • Have two form bundles set a with the type of bundle set to "Simultaneous"
  • [BundleA] contains:
  • The first form [FormA] being the "Admission" form. Then followed by [FormB] and [FormC], which can be any other forms
  • [BundleB] contains:
  • The first form [FormA] being any "Episodic" type form. Then followed by [FormB] a "Non-Episodic" form and then [FormC] which is another "Episodic" form
  • [TestClient] is admitted in one or more active episodes
  • The logged in user has permission to access all forms contained in the bundles
Steps
  1. At the home view, select [TestClient]
  2. Open [BundleA]
  3. Validate the user is presented with [FormA] the "Admission" form and its ready for data entry
  4. Validate no other forms in the bundle have loaded yet in a tab. [Note: this is the expected behavior]
  5. Populate and submit the "Admissions" form
  6. Validate submission is successful
  7. Validate now that [FormB] and [FormC] have each loaded in a separate tab, as expected
  8. Click the tab for [FormB] and then quickly the tab for [FormC]
  9. Validate [FormC] will not load until [FormB] has fully loaded
  10. Click back to the tab for [FormB]
  11. Validate it has loaded and displays as expected
  12. Submit the form
  13. Validate the form submits successfully
  14. Now click the tab for [FormC]
  15. Validate [FormC] has loaded and displays as expected
  16. Submit the form
  17. Validate the form submits successfully
  18. Open [BundleB]
  19. Validate [FormA] the episodic form, is loaded at the episode selection screen
  20. Click the tab for [FormC] the second episodic form, while the form is loading....
  21. Click back to the tab for [FormA]
  22. Validate the user is able to select an episode and click to open the form
  23. Validate [FormA] loads and displays as expected
  24. Populate and submit the form
  25. Validate the form submits successfully
  26. Click back to the tab for [FormC]
  27. Validate [FormC] is loaded at the episode selection screen
  28. Click the tab for [FormB], while the form is loading.......
  29. Click back to the tab for [FormC]
  30. Validate the user is able to select an episode and click to open the form
  31. Validate [FormC] loads and displays as expected
  32. Submit the form
  33. Validate the form submits successfully
Topics
• Forms
2023 Update 133 Summary | Details
State Form Definition - file import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
Scenario 1: "State Form Definition" - Export/Import validations
Specific Setup:
  • Have a "State Form Definition" definition created [SFDef] that is an "XML" type definition and contains a sub record
  • In form "State Form Definition" select [SFDef] and note the ID number assigned to it in parens. For example: "SFDef (1)"
  • Navigate to the "Record Definition" section and note the numerical value assigned in the "Record ID" field. For example: "16"
  • Open the "Define Records Data Element" grid and navigate to the "Subrecord" column of the sub record row.
  • Note the value populated in the field, which is the sub records "name" and "code" number references. For example: "Sub1 (16!!17)"
  • Navigate to the "Import/Export" section of the form and export the state form definition for [SFDefExport]
  • Save the file [SFDefExport] in a desired folder location
Steps
  1. Open form "State Form Definition"
  2. Go to the "Import" section
  3. Select "New" in the "Import Type" field
  4. Click [Select File for Import]
  5. Navigate to the location of the [SFDefExport] export file, saved in the setup
  6. Select the file
  7. In the "Import File Scan Results"
  8. Validate the results indicate there are no issues with the import file
  9. Click [Process Import]
  10. Validate message displayed "Import Complete"
  11. Click [OK]
  12. Close the form
  13. Re-Open form "State Form Definition"
  14. Select "Existing" in the "New or Existing" field
  15. Click the "Select State Form" field, to display the definitions for selection in the drop down list
  16. Validate "SFDef (1)" is present in the list
  17. Validate "SFDef (2)" the imported state form file is also present in the list. It will contain the same name as the original file exported, but with a new ID number assigned.
  18. Select "SFDef (2)" for edit
  19. Navigate to the "Record Definition" section and select the "Main" record
  20. Validate the value in the "Record ID" field has been assigned a different value than the one noted for "SFDef (1)", in the set up, as expected
  21. Click the [Define Records Data Element] to enter the data elements grid
  22. Navigate to the "Subrecord" column of the sub record row
  23. Validate the sub records "name" and internal "code" number references are populated in the field with:
  24. The sub record 'name', still the same as original file exported, "Sub1"
  25. The internal "code" number in parens, but assigned a new number as expected. For example, "(2!!5)"
  26. Exit the grid and close the form
Topics
• State Form Tools
2023 Update 136 Summary | Details
Clinical Document Viewer - Service Date
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
  • Envelope Definition (CWS)
  • Table Definition (CWS)
  • Form Definition (CWS)
  • Modeled Form with Service Documentation Sorted by Order Entry
Scenario 1: Clinical Document Viewer - Viewing user modeled form with service documentation sorted by date
Specific Setup:
  • Create or import a user modeled form with service documentation that must be ordered by date of service.
  • Give the user access to the modeled form using the "User Definition" form.
  • Click "Refresh Forms".
  • Using "Document Routing Setup":
  • Enable document routing for the user modeled form.
Steps
  1. Open the "Scheduling Calendar" form.
  2. Create an appointment.
  3. Open the modeled form from setup that was enabled for document routing.
  4. Create and finalize the note.
  5. Open the "Clinical Document Viewer
  6. Locate the row that contains the form that was finalized.
  7. Validate the "Service Date" columns is populated with the service date on the form.
Scenario 2: Clinical Document Viewer - Viewing user modeled form with service documentation sorted by entry order
Specific Setup:
  • Create or import a user modeled form with service documentation and must be ordered order of entry.
  • Give the user access to the modeled form using the "User Definition" form.
  • Click "Refresh Forms".
  • Using "Document Routing Setup":
  • Enable document routing for the user modeled form.
Steps
  1. Open the "Scheduling Calendar" form.
  2. Create an appointment.
  3. Open the modeled form from setup that was enabled for document routing.
  4. Create and finalize the note.
  5. Open the "Clinical Document Viewer
  6. Locate the row that contains the form that was finalized.
  7. Validate the "Service Date" columns is populated with the entry date of the form
Topics
• Modeling • Service Documentation • Clinical Document Viewer
2023 Update 144 Summary | Details
Client Lookup
Scenario 1: Validate the 'Display Name as Last,First' registry setting
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Display Name As Last, First" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting' field contains "RADplus->Database Management->Client Lookup->->->Display Name As Last, First"
  5. Validate the 'Registry Setting Details' field contains "Selecting 'Y' will display client name as Last Name, First Name when using the Select Client search from the Home Page. Selecting 'N' will display client name as First Name Last Name".
  6. Enter "Y" in the 'Registry Setting Value' field.
  7. Click [Submit] and close the form.
  8. In the 'Client Search', search for "Client A" using a partial last name.
  9. Validate the 'Results' contain "Client A" in the format of "LAST,FIRST (ID#)" without extra commas.
  10. Access the 'Import Client Picture' form.
  11. Search for "Client A" in the 'Client' field using a partial last name.
  12. Validate "Client A" is displayed in the format of "LAST,FIRST (ID#)" without extra commas.
  13. Close the form.
  14. Access the 'Registry Settings' form.
  15. Enter "Display Name As Last, First" in the 'Limit Registry Settings to the Following Search Criteria' field.
  16. Click [View Registry Settings].
  17. Validate the 'Registry Setting' field contains "RADplus->Database Management->Client Lookup->->->Display Name As Last, First"
  18. Validate the 'Registry Setting Details' field contains "Selecting 'Y' will display client name as Last Name, First Name when using the Select Client search from the Home Page. Selecting 'N' will display client name as First Name Last Name".
  19. Enter "N" in the 'Registry Setting Value' field.
  20. Click [Submit] and close the form.
  21. In the 'Client Search', search for "Client A" using a partial last name.
  22. Validate the 'Results' contain "Client A" in the format of "FIRST LAST (ID#)".
  23. Access the 'Import Client Picture' form.
  24. Search for "Client A" in the 'Client' field using a partial last name.
  25. Validate "Client A" is displayed in the format of "FIRST LAST (ID#)"
  26. Close the form.
Topics
• Registry Settings • Client Search
2023 Update 145 Summary | Details
Netsmart - Support Utilities
Internal Test Only
Topics
• RADplus Utilities
 

RADplus_2024_Quarterly_Release_2024.02_Details.csv