Skip to main content

RADplus 2022 Monthly Release 2022.03.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 67 Summary | Details
State Form Field Translation - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Field Translation
Scenario 1: State Form Field Translation Form - field entry and validation
Specific Setup:
  • Have a state form file created in form "State Form Definition" [FileA]
Steps
  1. Open form "State Form Field Translation"
  2. Select the state form [FileA] from the "State Form" field drop-down list.
  3. In the "Record" field, select a record.
  4. In the "Table" field, select the desired table.
  5. In the "Table Property" field, select the desired table property.
  6. In the "Action field", select "Single Translation"
  7. In the "Dictionary Code" field, enter a dictionary code [Code1]
  8. In the "State Forms Dictionary Code" field, enter a desired state form dictionary code [StateCode1]
  9. Click [Submit] to record the changes.
  10. Click [Yes] to return to the form
  11. In the "Dictionary Code" field, enter another dictionary code [Code2]
  12. In the "State Forms Dictionary Code" field, enter another desired state form dictionary code [StateCode2]
  13. Click [Submit] to record the changes.
  14. Click [Yes] to return to the form
  15. In the "Dictionary Code" field, enter another dictionary code [Code3]
  16. In the "State Forms Dictionary Code" field, enter another desired state form dictionary code [StateCode3]
  17. Click [Submit] to record the changes.
  18. Click [No] not to return to the form
  19. Open form "State Form Field Translation"
  20. Click the [Print Translations] button
  21. Validate the "File Name Override Field Translations" report contains the three codes filed in the previous steps
  22. Repeat step 2
  23. In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4
  24. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode1]
  25. In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6
  26. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode2]
  27. In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8
  28. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode3]
  29. Click the [Select Translations to Delete] button
  30. Validate all three translations are preset
  31. Click the check box for each item
  32. Click [OK] and [Yes] to continue
  33. Click [Submit]
  34. Click [Yes] to return to the form
  35. Repeat step 2
  36. In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4
  37. Validate the "State Forms Dictionary Code" field is blank, as expected
  38. In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6
  39. Validate the "State Forms Dictionary Code" field is blank, as expected
  40. In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8
  41. Validate the "State Forms Dictionary Code" field is blank, as expected
Application Namespace Validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
Scenario 1: Application Namespace Connection Validation
Specific Setup:
  • Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces
Steps
  1. Open form "Applications Namespace Connection Validations"
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  3. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection errors.
  4. Click [Process]
  5. Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s):
Topics
• State Form Tools • NX
Update 69 Summary | Details
CarePOVClinician - modeled forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Mobile Application Build
Scenario 1: Clinician<>Avatar: Validate synchronization of Modeled Form data
Specific Setup:
  • Have a modeled form in Avatar [FormA]
  • Have an active client [ClientA]
  • Have "CarePOV.Clinician" application installed and configured to connect to Avatar
  • Have a user who is staff member configured as mobile user in form "User Definition" [UserA]
  • [UserA] has launched and logged into Clinician
  • Log into Avatar as [UserA]
Steps
  1. In Avatar, open the "Mobile Application Build" form
  2. Select [FormA] in the "Select RADplus Forms" field
  3. Click [Submit]
  4. Validate submission is successful
  5. Log into Clinician
  6. Click [Synchronize]
  7. Verify synchronization is successful
  8. Verify [FormA] displays in the "All Forms" field
  9. Select [ClientA]
  10. Open [FormA]
  11. Populate the desired fields
  12. Click [Submit]
  13. Click [Synchronize]
  14. Validate synchronization is successful
  15. Log into Avatar
  16. Select [ClientA]
  17. Open [FormA]
  18. Edit the row filed in Clinician [RowA], in step 2
  19. Validate fields on the modeled form are populated as expected
  20. Select a field [FieldA] and change the value in the field [NewValue]
  21. Submit the form
  22. In Clinician
  23. Click [Synchronize]
  24. Verify synchronization is successful
  25. Select [ClientA]
  26. Open [FormA]
  27. Edit [RowA] filed in Avatar, in step 3
  28. Validate the field value [NewValue] is present in [FieldA], as expected
  29. Close the form
Scenario 2: Clinican<>Avatar - Validate synchronization of client demographics data
Specific Setup:
  • Have an active client on the system [ClientA]
  • [UserA] has access to form "Update Client Data"
Steps
  1. Log into Clinician
  2. Select [ClientA]
  3. Open form "Update Client Data"
  4. Make a change to any field [FieldA], for example the "Address" field
  5. Submit the form
  6. Click [Synchronize]
  7. Verify synchronization is successful
  8. Log into Avatar
  9. Select [ClientA]
  10. Open form "Update Client Data"
  11. Validate the change made to the [FieldA] in step 1, is present on the form
  12. Make a change to another field [FieldB]
  13. Submit the form
  14. In Clinician
  15. Click [Synchronize]
  16. Verify synchronization is successful
  17. Select [ClientA]
  18. Open form "Update Client Data"
  19. Validate the change made to [FieldB] in step 2 is present as expected
  20. Close the form
Topics
• 835 • 835 Health Care Claim Payment/Advice • 837 Institutional • 837 Professional • Add New Appointment • Administration Location • Admission • Modeling
Update 86 Summary | Details
Cache - process cleanup
Scenario 1: Verify cleanup of cache internal background processes
Steps
  1. Internal Testing Only
Topics
• Cache
Update 90 Summary | Details
Client Name Display
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Chart
Scenario 1: Validate client name display in the "My Clients" widget and "Chart" view header
Specific Setup:
  • Have a client with just first and last name defined. [ClientA]
  • Have a client with first name, last name and middle name defined. [ClientB]
  • Have a client with first name, middle name, last name and a suffix defined. [ClientC]
  • Have a client with a prefix, first name, middle name, last name and a suffix defined. [ClientD]
  • Have the "My Clients" widget on a user's [UserA] home view
  • Have a client based form available for testing. For example "Update Client Data" [FormA]
  • Have [FormA] added to the users home view
  • Log in as [UserA]
Steps
  1. In the "Search Clients" field of the "My Clients" widget, search for and select [ClientA]
  2. Validate the selected clients first and last name are displayed in both the "My Clients" and "Recent Clients" lists, as expected
  3. Right-click on the clients name and click to display the clients chart
  4. Validate the name in the client chart header displays clients first and last name, as expected
  5. Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their last name(in uppercase)
  6. Click back to the Home View
  7. Search and open [FormA]
  8. Validate the name in the client header displays clients first and last name, as expected
  9. Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their last name(in uppercase)
  10. Close or submit [FormA]
  11. Validate the name in the client header displays clients first and last name, as expected
  12. Validate the "Tab" above the client header, displays the client first name followed by the first initial of their last name(in uppercase)
  13. In the "Search Clients" field of the "My Clients" widget, search for and select [ClientB]
  14. Validate the selected clients first, middle and last name are displayed in both the "My Clients" and "Recent Clients" lists, as expected
  15. Right-click on the clients name and click to display the clients chart
  16. Validate the name in the client chart header displays clients first, middle and last name, as expected
  17. Validate the "Tab" above the client header, displays the client first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase)
  18. Click back to the Home View
  19. Search and open [FormA]
  20. Validate the name in the client header displays clients first, middle and last name, as expected
  21. Validate the "Tab" above the client header, displays the client first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase)
  22. Close or submit [FormA]
  23. Validate the name in the client header displays clients first, middle and last name, as expected
  24. Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase)
  25. In the "Search Clients" field of the "My Clients" widget, search for and select [ClientC]
  26. Validate the selected clients first, middle, last name and suffix(in uppercase letters) are displayed in both the "My Clients" and "Recent Clients" lists, as expected
  27. Right-click on the clients name and click to display the clients chart
  28. Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters)
  29. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
  30. Click back to the Home View
  31. Search and open [FormA]
  32. Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters)
  33. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
  34. Close or submit [FormA]
  35. Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters)
  36. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
  37. In the "Search Clients" field of the "My Clients" widget, search for and select [ClientD]
  38. Validate the selected clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters) are displayed in both the "My Clients" and "Recent Clients" lists, as expected
  39. Right-click on the clients name and click to display the clients chart
  40. Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters)
  41. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
  42. Click back to the Home View
  43. Search and open [FormA]
  44. Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters)
  45. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
  46. Close or submit [FormA]
  47. Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters)
  48. Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)
Topics
• Client Search
Update 94 Summary | Details
Root System Code - creation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Document Management Definition
  • Form Bundler (PM)
  • User Role Definition
  • Data Trail Configuration
  • Launch RxConnect
Scenario 1: New "Root" System Code - Data Validations after root system code creation
Specific Setup:
  • Have a system with a root system code defined [RootA]
  • [RootA] has Avatar "PM", "CWS", "MSO" and "CFMS" installed
  • In addition, [RootA] is configured with the following:
  • "Avatar Identity Manager" is installed
  • The 'Enable Avatar Identity Manager' registry setting is not set to 'Y
  • "RXConnect" installed and configured
  • [UserA] has permissions in form "User Definition" to "RxConnect" to login to the application
  • "Avatar Order Entry" is installed
  • In form 'Ask on Order Entry Definition' form, two questions are defined [TestA] and [TestB]
  • Have a report or query to display data in the "OrderEntry.index_order_code" table [OrderRptA]
  • "Avatar Data Trail" is installed
  • Open form "Data Trail Configuration" and run the report by "Option"
  1. Expand the group tree for each namespace on left side panel and make a note of the forms listed under each namespace
  • In form "Document Management Definition" a form name is defined [FormA] with a "Form Type" [FTypeA] that has two categories [CatA] and [CatB], selected in the "Categories" field
  • In each namespace ("PM", "CWS", "MSO" and "CFMS") a form bundle [BundleA] has been created in form "Form Bundler", that contains two forms, [BformA] and [BformB].
  • In each namespace a modeled form [FormA] has been created using form "Form Definition"
  • In each namespace a report definition [ReportA] has been created using form "Report Definition"
  • A user role [RoleA] has been created in form "User Role Definition"
  • Netsmart has created a new root system code, using [RootA] to copy data from. For this example [RootB] with Facility [5] assigned is used
  • [UserA] has been assigned full form and table access in [RootA] and [RootB]
  • Log in to [RootB] as [UserA]
Steps
  1. Open form "Registry Settings"
  2. Search for setting 'Enable Avatar Identity Manager'
  3. Validate the setting is found, as the module is installed
  4. Validate the setting is set to "N", as the module has not been enabled and configured yet in the new root system code
  5. Close the form
  6. Open form "'Ask on Order Entry Definition'"
  7. Click the "Edit" radio button
  8. In the "AOE to Edit" search field, enter [TestA]
  9. Validate the question is found, and results are as expected
  10. In the "AOE to Edit" search field, enter [TestB]
  11. Validate the question is found, and results are as expected
  12. Run the "OrderEntry.index_order_code" table report [OrderRptA]
  13. Validate a row is present with the "Order Code" column populated with [TestA] and the "Facility" column contains "7" the new facility number for [RootB]
  14. Validate a row is present with the "Order Code" column populated with [TestB] and the "Facility" column contains "7" the new facility number for [RootB]
  15. Close the report
  16. Close the form
  17. Open form "Document Management Definition"
  18. Click [Select Form]
  19. Select [FormA]
  20. Select [FTypeA] in the "Form Type" field
  21. Click [Select Categories]
  22. Validate categories [CatA] and [CatB] are displayed
  23. Close the form
  24. Open form "Form Bundler" in "PM"
  25. Click [Edit Existing]
  26. Validate [BundleA] is present in the list and click [OK] to select the bundle
  27. Click [Included Forms]
  28. Validate [BformA] and [BformB] are listed, as expected
  29. Close the form
  30. Open form "Form Bundler" in each of the child namespaces
  31. Repeat steps 4 a and b
  32. Validate results are as expected
  33. Close the form
  34. From the "Search Forms" field on the home view, search for the "Report Definition" form [ReportA] in "PM"
  35. Select the form
  36. Validates the form opens successfully
  37. Close the form
  38. Repeat step 6 opening [ReportA] in each of the child namespaces
  39. Validate results are as expected
  40. From the "Search Forms" field on the home view, search for the "Modeled" form [FormA] in "PM"
  41. Select the form
  42. Validate the form opens successfully
  43. Close the form
  44. Repeat step 8, searching for the modeled [FormA] in each of the child namespaces
  45. Validate results are as expected
  46. Open form "User Role Definition"
  47. Click [Select User Role]
  48. Validate [RoleA] is present in the results
  49. Click to open the role
  50. Validate data is populated as expected
  51. Close the form
  52. Open form "Data Trail Configuration"
  53. Select "Option" in the "Sort Report By" field
  54. Click [Run Report]
  55. Expand the group tree for each namespace on left side panel
  56. Compare the forms listed under each namespace with ones noted in the set up
  57. Validate the forms listed are the same in both root system codes
  58. At the home screen, search for form "Launch RXConnect"
  59. Click [Launch RXConnect]
  60. Validate the "RXConnect" application is launched in separate window
  61. Validate the user is automatically logged in
  62. Click logout
  63. At the login screen, enter the Avatar user name and password
  64. Click login
  65. Validate the user is logged in successfully
  66. Click [Logout]
  67. In Avatar, close the form
Root System Code - Facility numbers
Scenario 1: New "Root" System Code creation
Steps
  1. Internal Testing Only
Topics
• Forms • NX
Update 98 Summary | Details
ECP Server - Reports
Scenario 1: Validate report data results when run from an "ECP" server
Specific Setup:
  • Have an Avatar system that also has an "ECP" server configured (by Netsmart) to connect to the Avatar server via the "ECP" server, so that reports can be generated from the "ECP" server
  • Have access to two forms run from within Avatar, that launch a report
  • A "PM" form [FormA], for example the "PM" report, "Client Ledger"
  • A child namespace form [FormB], for example "CWS" form "Problem List"
  • Have two reports that can be run from outside the Avatar application, for example via "Crystal Reports"
  • A "PM" table based report [ReportA], for example the "SYSTEM.patient_demographic_history" table
  • A child namespace based table [ReportB] for example "CWS" table, "SYSTEM.cw_patient_notes"
  • [UserA] has permissions to run the forms and reports outlined in the setup
  • Log in as [UserA]
Steps
  1. Navigate to [FormA]
  2. Populate all desired fields
  3. Click to launch the report
  4. Validate the data results in the report, are as expected
  5. Close the report
  6. Wait one minute or more
  7. Repeat step b
  8. Validate the data results in the report, are as expected
  9. Navigate to [FormB]
  10. Populate all desired fields
  11. Click to launch the report
  12. Validate the data results in the report, are as expected
  13. Close the report
  14. Wait one minute or more
  15. Repeat step b
  16. Validate the data results in the report, are as expected
  17. Launch [ReportA]
  18. Click "Preview"
  19. Validate the data results in the report, are as expected
  20. Wait one minute or more
  21. Repeat step a
  22. Validate the data results in the report, are as expected
  23. Close the report
  24. Launch [ReportB]
  25. Click "Preview"
  26. Validate the data results in the report, are as expected
  27. Wait one minute or more
  28. Repeat step a
  29. Validate the data results in the report, are as expected
  30. Close the report
RADplus - processing
Scenario 1: Validate cache internal processing "User.RadPlusProcessStorage" table
Steps
  1. Internal Testing Only
Topics
• Cache • NX
Update 101 Summary | Details
DocR.document_history table
Scenario 1: Validate data in 'DocR.document' table
Specific Setup:
  • [UserA] is a staff member and also has permissions to co-sign to do's for other staff members
  • [UserB] is a staff member and has the 'My To Do's' widget on the Home View.
  • A client [ClientA] is enrolled in an open episode
  • Document routing is enabled for a form [FormA]. For example, a progress note or modeled form
  • Have a report [ReportA] to display data in the "DocR.document_history" table
  • Log in as [UserB]
Steps
  1. Access [FormA]
  2. Select [ClientA] in the 'Select Client' field.
  3. Select [Episode1] where the client is enrolled in [ProgramA]
  4. Populate all required fields any desired fields in the form
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note].
  7. Validate that the 'Confirm Document' dialog is displayed with expected data
  8. Click [Accept and Route].
  9. Validate the 'Route Document To' dialog is displayed.
  10. Select the [UserA] as the 'Approver'.
  11. Click [Submit].
  12. Validate submission is successful
  13. Navigate to the 'My To Do's' widget.
  14. Select the "Sign" tab.
  15. Validate the 'Search Documents' field contains a row for the To do document routed in step 1
  16. Log out as [UserB]
  17. Log in as [UserA]
  18. Navigate to the 'My To Do's' widget.
  19. Select the "Sign" tab.
  20. Search for [UserA] in the "Staff" field
  21. Validate the To do document routed to [UserA] in step 1 is listed in the "Search Document" list box
  22. Select the To Do row
  23. Click [Accept].
  24. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section
  25. Select the row in the "Accepted Documents" section
  26. Validate the document preview, contains the expected data
  27. Click [Sign All]
  28. Enter the password for [UserA] in the 'Verify Password' dialog and click [OK].
  29. Validate the 'Accepted Documents' field no longer contains the To do. (Note the approval submission date and time).
  30. Launch [ReportA]
  31. In the "Action Date" and "Action Time" columns, locate the row based on the approval submission date and time noted in step 5
  32. Validate the "User_Task" column indicates "Approver" and the "UserID" column indicates the user ID or [UserA], the co-signer
My To Do's Widget - Sign Tab
Scenario 1: 'My To Do's' widget - Validate approving documents from the "Sign" Tab
Specific Setup:
  • Have a system with a root system code [RootA] and sub system code defined [SubA]
  • [SubA] is set up to be restricted to only [ProgramA]
  • [UserA] is a staff member and also has permissions to co-sign to do's for other staff members
  • A client [ClientA] is enrolled in [ProgramA] in [Episode1] and [ProgramB] in [Episode2]
  • Document routing is enabled for a form[FormA]. For example a progress note or modeled form
  • [UserA] has access to log into [SubA] but does not have access to [RootA]
  • [UserB] has access to [SubA] and [RootA]
  • Both users have the 'My To Do's' widget on the Home View.
  • Log in as [UserB]
Steps
  1. Access [FormA]
  2. Select [ClientA] in the 'Select Client' field.
  3. Select [Episode1] where the client is enrolled in [ProgramA]
  4. Populate all required fields any desired fields in the form
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note].
  7. Validate that the 'Confirm Document' dialog is displayed with expected data
  8. Click [Accept and Route].
  9. Validate the 'Route Document To' dialog is displayed.
  10. Select the [UserB] as the 'Approver'.
  11. Click [Submit].
  12. Validate submission is successful
  13. Return to [FormA]
  14. Select [ClientA] in the 'Select Client' field.
  15. Select [Episode2] where the client is enrolled in [ProgramB]
  16. Repeat steps1c thru e
  17. Validate routing and submission is successful
  18. Navigate to the 'My To Do's' widget.
  19. Select the "Sign" tab.
  20. Validate the 'Search Documents' list box contains the row for the To Do routed for [Episode1] / [ProgramA] and a row for the To Do document routed for [Episode2] / [ProgramB]
  21. Log out as [UserB]
  22. Log in as [UserA] to sub code [SubA]
  23. Navigate to the 'My To Do's' widget.
  24. Select the "Sign" tab.
  25. Search for [UserA] in the "Search Documents" field
  26. Validate the To Do document routed for [Episode1] / [ProgramA] in step 1
  27. Validate the To Do document routed for [Episode2] / [ProgramB] in step 2 is not present, as sub code [SubA] is restricted to only episodes admitted in [ProgramA]
  28. Select the To Do row
  29. Click [Accept].
  30. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section
  31. Select the row in the "Accepted Documents" section
  32. Validate the document preview, contains the expected data
  33. Click [Sign All]
  34. Enter the password for [UserA] in the 'Verify Password' dialog and click [OK].
  35. Validate the 'Accepted Documents' field no longer contains the To Do row for [Episode1] / [ProgramA]
  36. Log out as [UserB] and login as [UserA]
  37. Access the 'Clinical Document Viewer' form.
  38. Select "Client" in the 'Select All or Individual Client' field.
  39. Select [ClientA] in the 'Select Client' field.
  40. Click [Process].
  41. Validate the document row for the To Do approved in step 4 is present
  42. Double click on the row
  43. Validate the document preview, contains the expected data
  44. Close the form.
Guardiant - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
Scenario 1: Guardiant form - Field validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Have a user with access to the "Guardiant" form
Steps
  1. Open form "Guardiant"
  2. Click the "Guardiant Configuration" section
  3. Click [Test Connectivity]
  4. Validate message "Connectivity Test Successful" is displayed
  5. Click [OK]
  6. Click [Test Daily Collection]
  7. Click [Yes] to the warning message
  8. Validate message "Test Succeeded" is displayed
  9. Click [Test Metrics Collection]
  10. Click [Yes] to the warning message
  11. Validate message "Test Succeeded" is displayed
  12. Click "Export Configuration"
  13. In "File Explorer", select a directory to save file
  14. Click [Save]
  15. Go to the directory where the file was saved
  16. Open the "GuardiantConfiguration.txt" file
  17. Validate data is present in the file
Topics
• My To Do's • NX • Guardiant
Update 113 Summary | Details
Client Search - results
Scenario 1: Validate client search results using "Alternate" lookups
Specific Setup:
  • Have the "My Clients Widget" on the home view
  • Have a client [ClientA], that has their "Date of Birth", "Social Security Number" populated in their client record along with an "Alias" name. For this test, [ClientA] is "Mary Jones" and she has an alias of "Jane Doe"
  • Have the "Client Lookup/Header Configuration Manager" form, have "Alias" configured as an "Alternate" search
  • Have any form [FormA], that includes a client search field within the form [FormA]. For example "Progress Notes Group and Individual"
  • Have access to any client based form [FormB], for example "Update Client Data"
Steps
  1. Open [FormA], the form that includes a search client field
  2. In the "Select Client" search field, search for [ClientA] using their "Date of Birth"
  3. Validate [ClientA] is found in the search results
  4. In the search field, search for [ClientA] using their "Social Security Number"
  5. Validate [ClientA] is found in the search results
  6. In the search field, search for [ClientA] using their name
  7. Validate [ClientA] is found in the search results
  8. In the search field, enter the first name of their "Alias" name. For this example, "Jane" is entered
  9. Validate [ClientA] is found in the search results
  10. Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]", as expected. (For this example, MARY JONES (0000003) [Alias: Jane Doe] is displayed)
  11. Navigate to the "Search Clients" field of the "My Clients" widget
  12. In the search field, search for [ClientA] using their "Date of Birth"
  13. Validate [ClientA] is found in the search results
  14. In the search field, search for [ClientA] using their "Social Security Number"
  15. Validate [ClientA] is found in the search results
  16. In the search field, search for [ClientA] using their name
  17. Validate [ClientA] is found in the search results
  18. In the search field, enter the first name of their "Alias" name. For this test, "Jane" is entered based on the setup steps
  19. Validate [ClientA] is found in the search results
  20. Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]"
  21. For this test, MARY JONES (0000003) [Alias: Jane Doe] would be displayed
  22. Click the "Advanced" button next to the "Search Clients" search field
  23. In the "Last Name" field, enter any letter
  24. In the "Sex" field, select a value
  25. In the "Alias" field, enter the "Alias" for [ClientA]
  26. Open [FormB], the client based form
  27. In the "Select Client" search field, search for [ClientA] using their "Date of Birth"
  28. Validate [ClientA] is found in the search results
  29. In the search field, search for [ClientA] using their "Social Security Number"
  30. Validate [ClientA] is found in the search results
  31. In the search field, search for [ClientA] using their name
  32. Validate [ClientA] is found in the search results
  33. In the search field, enter the first name of their "Alias" name. For this test, "Jane" is entered based on the setup
  34. Validate [ClientA] is found in the search results
  35. Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]"
  36. For this test, MARY JONES (0000003) [Alias: Jane Doe] would be displayed
Topics
• Client Search • NX
Update 114 Summary | Details
Form Designer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Form Designer (CWS)
  • Modeled form with Default Dictionary Values
Scenario 1: Form Designer - Submit and validate form designer changes
Specific Setup:
  • Have access to a form [FormA] in the PM namespace, for example the "Admission" form
  • Have access to a form [FormB] in the child namespace, for example a "CWS" modeled form
  • Have access to the "Form Designer" form in "PM" and in the child namespace
Steps
  1. Access the 'Form Designer' form in the "PM" namespace.
  2. Select [FormA] from the 'Forms' field.
  3. Select the desired section [SectionA] from the 'Sections' field.
  4. Click [Show Section].
  5. Select any field [FieldA] and move/re-size it as desired.
  6. Click [Cancel] and [Yes].
  7. Click [Show Section].
  8. Validate nothing has changed.
  9. Select any field [FieldA] and move/re-size it as desired.
  10. Click [Save], [OK], and [Submit].
  11. Access [FormA]
  12. Navigate to [SectionA]
  13. Validate [FieldA] is displayed in the location set in step 1
  14. Validate the size of [FieldA] is as expected based on the change make in step 1
  15. Click [Discard].
  16. Access the 'Form Designer' form in the child namespace
  17. Select [FormB] from the 'Forms' field.
  18. Select the desired section [SectionA] from the 'Sections' field.
  19. Click [Show Section].
  20. Select any field [FieldA] and move/re-size it as desired.
  21. Click [Cancel] and [Yes].
  22. Click [Show Section].
  23. Validate nothing has changed.
  24. Select any field [FieldA] and move/re-size it as desired.
  25. Click [Save], [OK], and [Submit].
  26. Access [FormB]
  27. Navigate to [SectionA]
  28. Validate [FieldA] is displayed in the location set in step 1
  29. Validate the size of [FieldA] is as expected based on the change make in step 1
  30. Click [Discard].
Topics
• Forms Designer • NX
Update 132 Summary | Details
Routing Admin Dashboard - GSI Size Limit Exceeded
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Admin Dashboard
  • Ambulatory Progress Notes
Scenario 1: Routing Admin Dashboard - Search results validations
Specific Setup:
  • The system is set up for "Rule Based Routing"
  • The system has over a "1000" documents filed in a single rule based routing queue.[QueueA]
Steps
  1. Open a progress note form that is configured to work with Rule Based Routing.
  2. Create and finalize a progress note.
  3. Open the 'Routing Admin Dashboard' form.
  4. Select [QueueA] in the 'Queue' field and leave all other search criteria fields unpopulated.
  5. Click [Search].
  6. Validate up to "1000" rows of data are displayed in the grid. (The system maximum number of rows that can be displayed in the grid).
  7. In the "Queue Search Criteria" section, use any of the search fields to narrow down the results, for example the "Select Programs" field.
  8. Click [Search].
  9. Validate the results are displayed as expected based on the search criteria.
Scenario 2: Routing Admin Dashboard - Re-Assign
Specific Setup:
  • The system is set up for Rule based routing.
Steps
  1. Open a progress note form that is configured to work with Rule Based Routing.
  2. Create and finalize a progress note.
  3. Open the "Routing Admin Dashboard" form.
  4. Select a "Queue".
  5. Click "Search" button.
  6. Click the "Select" column on any row in the Results table.
  7. Click "Re-Assign" button.
  8. Select the desired row in the table.
  9. Click the "Direct Assignment" radio button in the "Assignment Type" field.
  10. Select the "New Queue" to be assigned to from the drop down.
  11. Set the "New Status" for the document to be assigned to.
  12. Set the "New User" the document is to be assigned to.
  13. Click "File" button.
  14. Validate the reassigned row is removed from the results table.
  15. Set the "Queue" to the queue the document was reassigned to.
  16. Click "Search" button.
  17. Validate the row that was reassigned is now showing up in the results table with changed data in the status and user columns.
  18. Click the "Exit Form" button.
Scenario 3: Routing Admin Dashboard - Guidelines Definition
Specific Setup:
  • The system is set up for "Rule Based Routing"
Steps
  1. Using the progress note form configured for Rule Based Routing, create and finalize a progress note.
  2. Open the "Routing Admin Dashboard" form.
  3. Enter any desired filters and click [Search].
  4. Select a row in the "Results" table.
  5. Click [Guidelines Definition].
  6. Add a row of data.
  7. Click [File].
  8. Click [Guidelines Definition].
  9. Validate form redisplays as it was entered.
  10. Click [Cancel].
  11. Click [Exit Form].
Topics
• NX • Rule Based Routing