Skip to main content

RADplus 2023 Monthly Release 2023.03.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 54 Summary | Details
State Form Definition - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: State Form Definition - file "Definition Options" validations
Specific Setup:
  • Have a definition file created [TestDef], in form "State Form Definition" for any table on the system. For this test a definition is created using the "Admission" table, that will select and display "PATID" and "Episode" for each client admission on the system
Steps
  1. Open form "State Form File Generation"
  2. Select definition file [TestDef]
  3. In the "File Generations Options" field,
  4. Click "Compile"
  5. Set prompt 'Generate Flag On Compile' to "Yes"
  6. Click [Process]
  7. Validate "Compile Complete" is displayed
  8. Click "Create File On Server"
  9. Click [Process]
  10. Validate a file is created and view the file
  11. Validate data as expected for each client admitted on the system, as expected
  12. In the "File Generations Options" field,
  13. Click "Compile" again
  14. Validate a message containing no records are found is displayed, since all records were previously flagged and no changes were made to any records since the last compile
  15. Open the 'Admission' form for any client [TestClient]
  16. Select an episode and change any of the data in the form and then submit the form
  17. Return to the "State Form File Generation"
  18. In the "File Generations Options" field,
  19. Click "Compile"
  20. Set prompt 'Generate Flag On Compile' to "Yes"
  21. Click [Process]
  22. Click "Create File On Server"
  23. Click [Process]
  24. Validate a file is created and view the file
  25. Validate data for just [TestClient] is present, as expected
  26. Open the 'State Form Definition' form
  27. Select definition file [TestDef]
  28. Select 'Single Submission Flagging' in the 'Definition Options' field
  29. File the definition
  30. Open the 'Admission' form for any client [TestClient]
  31. Select an episode and change any of the data in the form and then submit the form
  32. Return to the "State Form File Generation"
  33. In the "File Generations Options" field,
  34. Click "Compile"
  35. Set prompt 'Generate Flag On Compile' to "Yes"
  36. Click [Process]
  37. Click "Create File On Server"
  38. Click [Process]
  39. Validate no records are present even though the data was modified, since prompt "Single Submission Flagging" was selected in step 5
State Form Tools - Import/Export
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, selecting the same values
  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. Navigate back to the "Action" field
  30. Select "Export Translations to CSV"
  31. Click the [Select CSV File] button
  32. Validate a file is location and save the file
  33. Navigate to location of the file and open it
  34. Validate all three translations entered in the previous steps, are present in the file as expected
  35. Closet the report
  36. Click the [Select Translations to Delete] button
  37. Validate all three translations are preset
  38. Click the check box for each item
  39. Click [OK] and [Yes] to continue
  40. Click [Submit]
  41. Click [Yes] to return to the form
  42. Repeat step 2, selecting the same values
  43. In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4
  44. Validate the "State Forms Dictionary Code" field is blank, as expected
  45. In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6
  46. Validate the "State Forms Dictionary Code" field is blank, as expected
  47. In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8
  48. Validate the "State Forms Dictionary Code" field is blank, as expected
  49. Navigate back to the "Action" field
  50. Select "Import Translations to CSV"
  51. Click the [Select CSV File] button
  52. Navigate to the location of file exported in step 14
  53. Select the file
  54. Validate a "Confirm" dialog is displayed, stating that 3 translations were processed and to submit the report to finalize the import
  55. Submit the form
  56. Return to the form
  57. Repeat step 2
  58. In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4
  59. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode1]
  60. In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6
  61. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode2]
  62. In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8
  63. Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode3]
State Form Query Logging- form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form File Generation
  • State Form Query Logging
Scenario 1: 'State Form Query Logging' form - Functionality and validations
Specific Setup:
  • Have a system with two state form file definitions created in form "State Form Definition" [SFileA] and [SFileB]
  • [SFileA] is a definition that contains one record [Rec]
  • [SFileB] is a definition that contains two records [Rec] and [Rec2]
  • Have a report to display data in the "RADplus_sf_audit_query" table, sorted by the "ID" field and displaying the fields "ID", "Query" and "Rec"
Steps
  1. Open form "State Form File Generation"
  2. Select definition [SFileA] in the "State Form" field. (Make a note of the file "ID" number located next to the state form file name)
  3. Select "Compile" in the "File Generation Options" field
  4. Populate the "File Description" field
  5. Click [Process]
  6. At the "Compile Complete" dialog, click [OK]
  7. Open form "State Form Query Logging"
  8. Select definition [SFileA] in the "State Form" field
  9. Validate the "Record" filed is automatically populated with the record name [Rec]. (Make a note of the record name)
  10. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  11. Click the [Refesh] button
  12. Validate the query field refreshes as expected with with the expected SQL query based on the table and selection criteria being executed in the record,
  13. Close the form
  14. Run the report created to query table "RADplus_sf_audit_query" table
  15. In the "ID" column, locate the row that contains a value starting with the definition "ID" for [SFileA], noted in step 1a
  16. Validate the "Record" field value matches the value noted in step 2a
  17. Validate the "Query" field value matches the value noted in step 2a
  18. Close the report
  19. Open form "State Form File Generation"
  20. Select definition [SFileB] in the "State Form" field. (Make a note of the file "ID" number, located next to the state form file name)
  21. Select "Compile" in the "File Generation Options" field
  22. Populate the "File Description" field
  23. Click [Process]
  24. At the "Compile Complete" dialog, click [OK]
  25. Open form "State Form Query Logging"
  26. Select definition [SFileB] in the "State Form" field
  27. Click the "Record" field
  28. Validate there are two records for selection, as expected. [Rec] and [Rec2]
  29. Select [Rec]
  30. Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
  31. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  32. Click the [Refesh] button
  33. Validate the query field refreshes as expected with with the expected SQL query based on the table and selection criteria being executed in the record,
  34. Navigate back to the "Record" field
  35. Select [Rec2]
  36. Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
  37. Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
  38. Click the [Refesh] button
  39. Validate the query field refreshes as expected with with the expected SQL query based on the table and selection criteria being executed in the record
  40. Run the report created to query table "RADplus_sf_audit_query" table
  41. In the "ID" column, locate the row(s) that contains a value starting with the definition "ID" for [SFileB], noted in step 4a
  42. Validate a row is found for record name [Rec]
  43. Validate the "Query" field value for record [Rec] matches the value noted in step 5a
  44. Validate a row is also found for record name [Rec]
  45. Validate the "Query" field value for record [Rec2] matches the value noted in step 5a
  46. Close the report
Topics
• State Forms • State Form Tools • NX
Update 76 Summary | Details
Client/Staff widget - Staff Credentials
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Practitioner Category
  • Practitioner Enrollment
Scenario 1: Practitioner - Practitioner Credentials - Search Results
Specific Setup:

Dictionary Update: Staff File - (214) Practitioner Credential - has desired values.

Identify two practitioners to add credentials to.

Steps
  1. Open 'Practitioner Category'
  2. Enter the first staff member in 'Select Staff'.
  3. Select the desired search result.
  4. Select the desired 'Enrollment History'.
  5. Select the desired 'Category/Taxonomy'.
  6. Click [Practitioner Credentials].
  7. Select the desired value in 'Select Credentials'. Note the value.
  8. Click [OK].
  9. Click [Add Practitioner Categories].
  10. Click [OK].
  11. Submit the form.
  12. Search for the practitioner and verify that the dictionary code displays after the name and before the ID number.
  13. Open 'Practitioner Enrollment'.
  14. Enter the second staff member in 'Select Staff'.
  15. Select the desired search result.
  16. Select the 'Categories/Taxonomy' section.
  17. Select the desired 'Category/Taxonomy'.
  18. Click [Practitioner Credentials].
  19. Select the desired value in 'Select Credentials'. Note the value.
  20. Click [OK].
  21. Click [Add Practitioner Categories].
  22. Click [OK].
  23. Submit the form.
  24. Search for the practitioner and verify that the dictionary code displays after the name and before the ID number.
Topics
• Database Management • NX
Update 79 Summary | Details
Block Client - report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Block Client Chart
Scenario 1: Block Client Chart (Form) - "Blocked Clients" Report
Specific Setup:
  • In form "Block Client Chart"
  • Have a client [TestClientA] already added in the "Blocked Clients" section
  • Have another client [TestClientB] who needs to be added to the list
  • Have access to form "Block Client Chart"
Steps
  1. Open form "Block Client Chart"
  2. Click the "Blocked Clients" section
  3. In the "Block Clients" grid
  4. Validate a row is present for [TestClientA], as expected
  5. Click the [Add New Item] button
  6. In the "Select Client" field, search and select [TestClientB]
  7. Populate the required and desired fields in the section
  8. Click [Submit]
  9. Validate the form files successfully
  10. Re-open form "Block Client Chart"
  11. Click the "Blocked Clients" section
  12. In the "Block Clients" grid
  13. Validate a row is present for [TestClientA], as expected
  14. Validate a row is present for [TestClientB], as expected
  15. Click back to the main section of the form
  16. In the "Clients to Display" field, select "All" clients
  17. Click the [List Blocked Clients] button to generate the report
  18. Validate the "Block Clients" report contains
  19. Information submitted for [TestClientA] and [TestClientB], as expected
Topics
• 835 Health Care Claim Payment/Advice • 835 • 837 Institutional • Block Client Chart
Update 81 Summary | Details
Quick Link - Reports
Scenario 1: Validate quick links for launching reports
Specific Setup:
  • Have a modeled form [TestForm] in application PM, that is not "Client" based. For example a form that is "Staff" entity based
  • Using form "Report Definition" in "CWS", have a report definition defined [TestReport] with a "PATID" defined as a parameter that will be passed to the report defined in the form
  • In "Form Designer" edit [TestForm] and add [TestReport] as a "Quick Link"
  • In "Form Designer" edit the "Admission" form add also add [TestReport] as a "Quick Link"
Steps
  1. Open [TestForm]:
  2. Select the entity required to launch into the form. For this example, user is prompted with "Select Staff".
  3. Navigate to the quick link [TestReport] defined on the form in the setup.
  4. Click on the quick link to launch the report definition.
  5. Populate the "Select Client" search prompt with any client [TestClient].
  6. Validate the form opens successfully and [TestClient] is populated in the "Client" search field.
  7. Populate any other desired fields on the form.
  8. Click [Process].
  9. Validate the report launches and data is displayed as expected.
  10. Close the report.
  11. Close [TestForm]:
  12. Open the "Admission" for an existing client [TestClient].
  13. Navigate to the quick link [TestReport] defined in the setup.
  14. Click on the link to launch the report definition.
  15. Validate the form opens successfully and [TestClient] is populated in the "Client" search field.
  16. Populate any other desired fields on the form.
  17. Click [Process].
  18. Validate the report launches and data is displayed as expected.
  19. Close the report.
  20. Submit or close the "Admission" form.
  21. Open the "Admission" for a "New" client:
  22. Navigate to the quick link [TestReport] defined in the setup/
  23. Click on the link to launch the report definition/
  24. Validate an error is displayed indicating that the form cannot be opened for a client that has not been admitted yet.
  25. Click [OK]/
  26. Close the "Admission" form.
Modeled forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form with Multiple Iteration Sections
Scenario 1: Validate filing Modeled forms that contain "Multiple Iteration" sections
Specific Setup:
  • Have a modeled form [TestForm] that contains one "Primary" section and two "Multiple Iteration" sections on the form
  • Have two client [TestClientA] and [TestClientB]
  • For [TestClientA], data has already submitted in [TestForm] that includes "5000" or more rows filed in the multiple iteration section grids
  • For [TestClientB], no data has been submitted in [TestForm]
Steps
  1. Open [TestForm] and select [TestClientB]:
  2. At the primary section:
  3. Populate the desired fields on the section.
  4. Click to the first multiple iteration section:
  5. Click to 'Add' a new row.
  6. Populate the desired fields on the section.
  7. Click to the second multiple iteration section:
  8. Click to 'Add' a new row.
  9. Populate the desired fields on the section.
  10. Submit the form.
  11. Validate the form files successfully.
  12. Return to [TestForm] and select [TestClientB]:
  13. Select the row submitted in step 1..
  14. Validate each section displays data as expected
  15. Open [TestForm] select [TestClientA]:
  16. Select the row of data already submitted, as stated in the setup:
  17. At the primary section
  18. Validate data is displayed as expected.
  19. Click to the first multiple iteration section:
  20. Validate the rows of data already submitted are displayed.
  21. Click to 'Add' a new row:
  22. Populate the desired fields on the section.
  23. Click to the second multiple iteration section:
  24. Validate the rows of data already submitted are displayed.
  25. Click to 'Add' a new row:
  26. Populate the desired fields on the section.
  27. Submit the form.
  28. Validate the form files successfully.
  29. Return to [TestForm] and select [TestClientA]
  30. Select the row submitted in step 3
  31. Validate each section displays data as expected, including the new rows added in the multiple iteration sections.
Topics
• Forms • Forms Designer • Modeling
Update 82 Summary | Details
Guardiant - metrics
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Avatar Clinical - Dashboards - Grafana
Scenario 1: Guardiant Metric "Analytics" Data - Validations
Specific Setup:
  • Have a system installed and configured with "Avatar eMAR" and "Avatar Order Entry" and is enabled to send "Metric" data to "Guardiant"
  • Have "Order Entry" order(s) posted in the system. Note the number of orders [TestOrders] and the date the orders were entered [TestOrderDate]
  • Have "Administrative Events" performed for one or more orders on a specific date. Note the number of events [TestEvent] and the date enter [TestEventDate]
  • Have "Services" posted in the system on a specific date. Note the number of services [TestServices] and the date entered [TestServicesDate]
  • Have access to log into "Guardiant"
Steps
  1. Log into "Guardiant"
  2. At the "Client Search", select the desired client account number
  3. In the right-hand corner, click "Analytics"
  4. Click the "Clinical" tab
  5. Navigate down to the "# of Orders" graph
  6. Hover over date in graph of when order(s) was added [TestOrderDate]
  7. Validate the number of orders [TestOrders] equals the number of expected orders for that day
  8. Navigate to "# of eMAR Administrations" graph
  9. Hover over date [TestEventDate] in graph, the date when the administration event(s) were added
  10. Validate the number equals the expected number of events for that day [TestEvent]
  11. Navigate to "Services by Week" graph
  12. Hover over date [TestServicestDate] in graph of when the services were added
  13. Validate the number equals the expected number of services [TestServices] for that day.
Topics
• Guardiant
Update 85 Summary | Details
User SQL table permissions
Scenario 1: Validate a user's SQL "ODBC" Table permissions
Specific Setup:
  • Have two users exist on the system that have the same "User ID" that differ only by where the period within their user ID is placed. These users are 'not' assigned to a user role.
  • For this test: "U.serA" and "User.A"
  • "U.serA" has access to the "SYSTEM.patient_current_demographics" table but does 'not' have access to the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" table.
  • "User.A" also has access to "SYSTEM.patient_current_demographics" table and 'does' have access to the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables.
  • Two other users exist on the system that have the same "User ID", that differ only by where the period within their user ID is placed. These users 'are' assigned to a user role.
  • For this test: "R.user" and Ruse.r"
  • "R.user" has access to the "SYSTEM.patient_current_demographics" table but 'does not' have access to the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" table.
  • "Ruse.r" also has access to "SYSTEM.patient_current_demographics" table and 'does' have access to the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables.
  • Each user has a "User Data Sources" name configured using MS-Windows "ODBC Data Source Administrator" application, to connect to the testing data base.
  • Have access to "Crystal Reports" or other database program to make an ODBC connection and view SQL Table permissions for the users defined in this set up.
Steps
  1. Open the database program, for this example "Crystal Reports" is used.
  2. Click "File" on the menu and then "New" to create a new report.
  3. At the "Data" dialog, click "Create New Connection".
  4. Double-click "ODBC".
  5. From the "Data Source Selection" dialog, locate the data source name created for user ID "U.serA" and double-click to select it.
  6. Populate the "User ID" field and "Password" with the credentials for "U.serA".
  7. Click "Finish".
  8. At the table tree list:
  9. Click the "SYSTEM" schema folder and then click "Tables".
  10. Validate the "SYSTEM.patient_current_demographics' table is present in the list.
  11. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables are "not" present, as expected.
  12. Click 'Cancel".
  13. Click "File" on the menu and then "New" to create a new report.
  14. At the "Data" dialog, click "Create New Connection".
  15. Double-click "ODBC".
  16. From the "Data Source Selection" dialog, locate the data source name created for user ID "User.A".
  17. Populate the "User ID" field and "Password" with the credentials for "User.A".
  18. Click "Finish".
  19. At the table tree list:
  20. Click the "SYSTEM" schema folder and then click "Tables".
  21. Validate the "SYSTEM.patient_current_demographics' table is present in the list.
  22. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables "are" present, as expected.
  23. Open the database program, for this example "Crystal Reports" is used.
  24. Click "File" on the menu and then "New" to create a new report.
  25. At the "Data" dialog, click "Create New Connection".
  26. Double-click "ODBC".
  27. From the "Data Source Selection" dialog, locate the data source name created for user ID "R.user" and double-click to select it.
  28. Populate the "User ID" field and "Password" with the credentials for "R.user".
  29. Click "Finish".
  30. At the table tree list:
  31. Click the "SYSTEM" schema folder and then click "Tables".
  32. Validate the "SYSTEM.patient_current_demographics' table is present in the list.
  33. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables are "not" present, as expected.
  34. Click 'Cancel".
  35. Click "File" on the menu and then "New" to create a new report.
  36. At the "Data" dialog, click "Create New Connection".
  37. Double-click "ODBC".
  38. From the "Data Source Selection" dialog, locate the data source name created for user ID "Ruse.r".
  39. Populate the "User ID" field and "Password" with the credentials for "Ruse.r".
  40. Click "Finish".
  41. At the table tree list:
  42. Click the "SYSTEM" schema folder and then click "Tables".
  43. Validate the "SYSTEM.patient_current_demographics" table is present in the list.
  44. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appt_data" tables "are" present, as expected.
Team Definition - Web Service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team Definition
Scenario 1: "Team Definition" Web Service - Add/Remove Client from Team
Specific Setup:
  • Have a team [TestTeam] defined in form "Team Definition".
  • Have a client [TestClient] that's admitted in an episode [TestEpisode], that needs to be added to that team.
  • Have the "WEBSVC.TeamDefinition" set up and configured to connect to the testing database in program "SoapUI" or other web service program.
Steps
  1. Open "SoapUI".
  2. Navigate to the "WEBSVC.TeamDefinition" web service.
  3. Click "AddClientToTeam" item and double click on "Request1" to open a new request.
  4. Populate the following required fields with the values needed to execute the web service on the testing system.
  5. With "Client ID" set to [TestClient], "EpisodeNumber" set to [TestEpisode] and "TeamID" set to the team ID number for [TestTeam].
  6. SystemCode
  7. UserName
  8. Password
  9. ClientID
  10. EpisodeNumber
  11. TeamID
  12. Click to process the request.
  13. Validate the request results indicate "Client has been successfully added to the team".
  14. In Avatar:
  15. Navigate to the "Team Definition" form.
  16. Select [TestTeam] for edit.
  17. Navigate to the "Individual Client Assignment" section.
  18. Validate a row is present for [TestClient] in the "Individual Client Assignment" grid, as expected.
  19. Validate the "Client ID" field is populated with [TestClient].
  20. Validate the "Episode(s)" field is populate with [TestEpisode].
  21. Close the form.
  22. Return to "SoapUI".
  23. Navigate to the "WEBSVC.TeamDefinition" web service.
  24. Click "RemoveClientFromTeam" item and double click on "Request1" to open a new request.
  25. Populate the following required fields with the values needed to execute the web service on the testing system.
  26. With "Client ID" set to [TestClient], "EpisodeNumber" set to [TestEpisode] and "TeamID" set to the team ID number for [TestTeam].
  27. SystemCode
  28. UserName
  29. Password
  30. ClientID
  31. EpisodeNumber
  32. TeamID
  33. Click to process the request.
  34. Validate the request results indicate "Client has been successfully removed from the team".
  35. In Avatar:
  36. Navigate to the "Team Definition" form.
  37. Select [TestTeam] for edit.
  38. Navigate to the "Individual Client Assignment" section.
  39. Validate the row for [TestClient] has been removed from the "Individual Client Assignment" grid, as expected.
  40. Close the form.
Topics
• SQL Data Access • Team Definition
Update 86 Summary | Details
Document Management Form Re-Mapping
Scenario 1: Document Management Form Re-Mapping (Re-Map Synced Facilities)
Steps
  1. Internal Testing Only
Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • Print Error Log (PM)
Scenario 1: Document Routing - (Route) a document
Specific Setup:
  • Have any form [TestForm] enabled for document routing, for this example a Modeled form will be used
  • [TestUser] is a staff member with access to [TestFom] and has the "My To Do's" widget on their home view
  • Log in as [TestUser]
Steps
  1. Access [TestForm] for any client [TestClient]
  2. Populate the desired fields on the form
  3. Select "Final" in the 'Draft/Final' field.
  4. A message displays indicating "Selecting Final prevents future edits".
  5. Click [OK] and [Submit].
  6. Verify the document preview displays the data as expected
  7. Click [Accept].
  8. Enter the password for the user in the 'Password' field
  9. Validate the form submits successfully to create the document [TestDoc]
  10. Access the 'Clinical Document Viewer' form.
  11. Enter [TestClient] in the 'Select Client' field.
  12. Locate [TestDoc] in the document results list
  13. Click [View] to display the document
  14. Verify the document preview displays the data as expected
  15. Close the form.
  16. Open form "Print Error Log"
  17. Enter today's date in the date fields
  18. Click [Submit]
  19. Validate there are messages relating to document created in step 1
Scenario 2: Document Routing - (Accept & Route) a document
Specific Setup:
  • Have any form [TestForm] enabled for document routing, for this example a Modeled form will be used
  • [TestUser] is a staff member with access to [TestFom] and has the "My To Do's" widget on their home view
  • Log in as [TestUser]
Steps
  1. Access [TestForm] for any client [TestClient]
  2. Populate the desired fields on the form
  3. Select "Final" in the 'Draft/Final' field.
  4. A message displays indicating "Selecting Final prevents future edits".
  5. Click [OK] and [Submit].
  6. Verify the document preview displays the data as expected
  7. Click [Accept and Route].
  8. Enter the password for the user in the 'Password' field
  9. Click [OK].
  10. In the "Route Document To" screen, select [TestUser] in the "Add Approver" search field and click [Add]
  11. Click [Submit] to route the document [TestDoc]
  12. Navigate to the 'My To Do's' widget.
  13. Locate the To Do for document just routed [TestDoc]
  14. Click [Approve Document]
  15. Verify the document preview displays the data as expected
  16. Click [Accept].
  17. Enter the password for the user in the 'Password' field.
  18. Click [OK].
  19. Validate the "To Do" has been removed from the "My To Do's" widget
  20. Access the 'Clinical Document Viewer' form.
  21. Enter [TestClient] in the 'Select Client' field.
  22. Locate [TestDoc] in the document results list
  23. Click [View] to display the document
  24. Verify the document preview displays the data as expected
  25. Close the form.
  26. Open form "Print Error Log"
  27. Enter today's date in the date fields
  28. Click [Submit]
  29. Validate there are messages relating to document created in step 1
Document Routing - Default From Last Filing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Review To Do Item
Scenario 1: Doc Routing -Default Notification User from Last Filing (Send to 'Non-Staff' enabled)
Specific Setup:
  • Have a form [TestForm] set up in form "Document Routing Setup" with following prompts set:
  • 'Enable Document Routing' se to 'Yes'.
  • 'Allow Notifications When Final' set to 'Yes'.
  • 'Notification List Defaults' set to 'Default From List Filing'
  • Have "Registry setting" 'Allow sending notifications to non-staff users' set to "Y".
  • [UserA] has access to [TestForm] and form 'Registry Settings'
  • [UserB] is a Staff member and has the "My To Do's" widget on their home view
  • [UserC] is not a Staff member and has the "My To Do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access [TestForm] and select any client [TestClient]
  2. Populate all desired fields on the form.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Accept and Route/Notify]
  5. Enter the user's password in the 'Password' field.
  6. Click [OK].
  7. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
  8. Search for [UserB]
  9. Validate the user is found
  10. Click [Add] to have [UserB] receive a To do notification
  11. Search for [UserC]
  12. Validate that [UserC] is found as expected based on the setup
  13. Click [Add] to have [UserC] receive a To do notification
  14. Click [Submit]
  15. Validate the form files successfully
  16. Repeat step 1 a thru e
  17. On the "Route To Document" screen, navigate to bottom where the approvers and notifiers are listed
  18. Validate the [UserB] has been automatically defaulted as a notifier and the "Notify" check box is populated
  19. Validate the [UserC] has been automatically defaulted as a notifier and the "Notify" check box is populated
  20. Click [Submit]
  21. Validate the form files successfully
  22. Log in as [UserB]
  23. Navigate to the "My To Do's" widget
  24. Click to refresh the widget
  25. Click the "New" tab
  26. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  27. Click to open each To Do
  28. Validate the "To Do Information" box contains the expected data
  29. Click the "Reviewed" check box
  30. Click [Submit]
  31. Validate submission is successful and each To Do has been removed form the To Do's list
  32. Log out as [UserB]
  33. Log in as [UserC]
  34. Navigate to the "My To Do's" widget
  35. Click to refresh the widget
  36. Click the "New" tab
  37. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  38. Click to open each To Do
  39. Validate the "To Do Information" box contains the expected data
  40. Click the "Reviewed" check box
  41. Click [Submit]
  42. Validate submission is successful and each To Do has been removed form the To Do's list
Scenario 2: Doc Routing -Default Notification User from Last Filing (Send to 'Non-Staff' user disabled)
Specific Setup:
  • Have a form [TestForm] set up in form "Document Routing Setup" with following prompts set:
  • 'Enable Document Routing' se to 'Yes'.
  • 'Allow Notifications When Final' set to 'Yes'.
  • 'Notification List Defaults' set to 'Default From List Filing'
  • Have "Registry setting", "Allow sending notifications to non-staff users" set to "N".
  • [UserA] has access to [TestForm] and form "Registry Settings"
  • [UserB] is a Staff member and has the "My To Do's" widget on their home view
  • [UserC] is not a Staff member and has the "My To Do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access [TestForm] and select any client [TestClient]
  2. Populate all desired fields on the form.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Accept and Route/Notify]
  5. Enter the user's password in the 'Password' field.
  6. Click [OK].
  7. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
  8. Search for [UserB]
  9. Validate the user is found
  10. Click [Add] to have [UserB] receive a To do notification
  11. Search for [UserC]
  12. Validate that [UserC] is 'not' found as expected based on the setup
  13. Repeat step 1 a thru e
  14. On the "Route To Document" screen, navigate to bottom where the approvers and notifiers are listed
  15. Validate the [UserB] has been automatically defaulted as a notifier and the "Notify" check box is populated
  16. Click [Submit]
  17. Validate the form files successfully
  18. Log out as [UserA]
  19. Log in as [UserB]
  20. Navigate to the "My To Do's" widget
  21. Click to refresh the widget
  22. Click the "New" tab
  23. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  24. Click to open each To Do
  25. Validate the "To Do Information" box contains the expected data
  26. Click the "Reviewed" check box
  27. Click [Submit]
  28. Validate submission is successful and each To Do has been removed form the To Do's list
Topics
• Document Routing • NX
Update 92 Summary | Details
Telehealth - Daylight Savings Time setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Registration - Assign ID
  • Site Registration
  • User Definition
  • Staff Members Hours And Exceptions
  • Registry Settings (PM)
  • Member Specific Information
  • Ambulatory Progress Notes
  • Clinical Document Viewer
Scenario 1: 'Update Client Data' - Verification of form filing
Specific Setup:
  • If custom Form Designer changes are present in 'Update Client Data' form, please use 'Form Designer' to revert to 'Netsmart Produced Changes'.
  • A client is enrolled in an existing episode (Client A).
  • The 'Enable Address Validation' registry setting must be enabled.
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter an invalid address in the 'Client's Address - Street' field and press the 'Tab' key.
  3. Validate an 'Address Validation' dialog stating: "The address was invalid for the following reason: Address Not Found. Discard changes?"
  4. Click [No].
  5. Enter an invalid address in the 'Client's Address - Street' field and press the 'Tab' key.
  6. Validate an 'Address Validation' dialog stating: "The address was invalid for the following reason: Address Not Found. Discard changes?"
  7. Click [Yes].
  8. Validate a dialog stating: "Cancelled." and click [OK].
  9. Validate the 'Client's Address - Street' field is cleared.
  10. Enter a valid address and populate any desired fields.
  11. Enter a 'Place of Birth' value that contains 40 characters.
  12. Select a preferred site in the "Preferred Site" field.
  13. Select a time zone in the "Time Zone for Appointment Reminders".
  14. Click [Submit].
  15. Re-enter the form for the client and validate that the data submitted successfully.
Scenario 2: Time Zone Globals - PM
Steps

Internal Testing Only

Scenario 3: Time Zone Globals - CWS
Steps

Internal Testing Only

Scenario 4: Time Zone Globals - MSO
Steps

Internal Testing Only

Scenario 5: 'Member Specific Information' form - Verification of form filing
Specific Setup:
  • Avatar MSO Registry Setting 'Require Member Enrollment' must be disabled
Steps
  1. Open the 'Member Specific Information' form.
  2. Select value in 'Add/Edit/Delete Funding Source Information' field.
  3. Enter/select values for 'Funding Source', 'Benefit Plan' and 'Effective Date' fields.
  4. Enter/select values for any other desired fields.
  5. Click 'Update Funding Source Information' button to save Funding Source Information entry.
  6. Click the 'Submit' button.
  7. Open the 'Member Specific Information' form.
  8. Select same client ID for record view/edit.
  9. In 'Member Specific Information' form, confirm that values previously filed are present in all fields. (This can also be confirmed directly via Avatar MSO SQL table 'SYSTEM.member_specific_info')
Scenario 6: Ambulatory Progress Notes - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Ambulatory Progress Notes" form.
Steps
  1. Open the "Ambulatory Progress Notes" 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 "Ambulatory Progress Notes" 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 "Ambulatory Progress Notes" 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 "Ambulatory Progress Notes" 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 7b-8c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Topics
• Update Client Data • Dictionary • Member Specific Information • Document Routing • Progress Notes
Update 95 Summary | Details
Routing Admin Dashboard - Query data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Admin Dashboard
Scenario 1: Routing Admin Dashboard - View Queries
Specific Setup:
  • User has the "Rule Based Routing" widget and the "My To Do's" widget on their home view
  • In the "Routing Queue Definition" form, have a queue [TestQueue] defined
  • Have a modeled form [TestForm] that is enabled for document routing
  • In the "Routing Configuration Definition form"
  • Select the "Product" that modeled form [TestForm] was created in
  • Select [TestForm] in the "Form" field
  • Select "Yes" in the "Active" field
  • Submit the form
  • Have two clients [ClientA] and [ClientB]
  • Open [TestForm] and submit and route a row for [ClientA]
  • Open [TestForm] and submit and route a row for [ClientB]
  • In the "My To Do's" widget, locate the to do's sent for [TestForm] in the previous step and approve them
  • In the "Rule Based Routing" widget
  • Locate the row for the document submitted for [ClientA]
  • Click [Launch Workflow List]
  • Fill out the form and click [Send Query]
  • Populate the "Enter Reason" text field and click [Save]
  • In the "Query Definition" grid, add two new query rows [Row1] and [Row2], populating the desired columns in each row and then save the form
  • Locate the row for the document submitted for [ClientB]
  • Click [Launch Workflow List]
  • Fill out the form and click [Send Query]
  • Populate the "Enter Reason" text field and click [Save]
  • In the "Query Definition" grid, add just one query row [Row1] and save the form
Steps
  1. Open the 'Routing Admin Dashboard' form.
  2. Select [ClientA] from the 'Queue' field.
  3. Click [Search].
  4. Select the row from the 'Results' grid.
  5. Click [View Summary].
  6. Select the row in the "Document Summary" screen
  7. Click [View Queries].
  8. In the "Query Definition", queries grid
  9. Validate there are two query rows present, [Row1] and [Row2] for [ClientA] in the grid, as expected
  10. Click [Close] to the "Query Definition" screen
  11. Click [Close] again in the "Document Summary" screen
  12. Returning to the open 'Routing Admin Dashboard' form.
  13. Select [ClientB] from the 'Queue' field.
  14. Click [Search].
  15. Select the row from the 'Results' grid.
  16. Click [View Summary].
  17. Select the row in the "Document Summary" screen
  18. Click [View Queries].
  19. In the "Query Definition", queries grid
  20. Validate there is just one row [Row1] present for [ClientB] in the grid, as expected
Topics
• Rule Based Routing
Update 96 Summary | Details
Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
  • Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
  • Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
  • Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
  • Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
  • In form "Import Reports"
  • Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
  • [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
  • Have three modeled forms available for testing
  • [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
  • [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
  • [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
  • [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
  1. In application "Crystal Reports"
  2. Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
  3. Click to process the report
  4. Validate the report display all data as expected
  5. Close the report
  6. Repeat step 1a again to regenerate the report
  7. Validate results are as expected
  8. Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
  9. Click to process the report
  10. Validate the report display all data as expected
  11. Close the report
  12. Repeat step 1c again to regenerate the report
  13. Validate results are as expected
  14. Log in Avatar
  15. Search for and open [ReportC], the report imported to run from a menu
  16. Validate when selected form the menu, the report launches successfully
  17. Validate the report display all data as expected
  18. Close the report
  19. Repeat step 2a again to regenerate the report
  20. Validate results are as expected
  21. Close the report
  22. Search for and open [ReportD], the "Report Definition" report
  23. Populate any prompts on the form
  24. Click to process the report
  25. Validate the report display all data as expected
  26. Close the report
  27. Repeat step 2b again to regenerate the report
  28. Validate results are as expected
  29. Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
  30. Populate the form
  31. Submit the form as "Final"
  32. Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
  33. Approve/ route and submit the document
  34. Validate submission is successful
  35. Repeat step 2c again
  36. Validate results are as expected
  37. Search for and open [FormB], the form configured with a post filing report
  38. Populate the fields on the form
  39. Submit the form
  40. Validate the form files successfully
  41. Validate the post filing report [ReportF] is launched
  42. Validate the data is displayed as expected
  43. Repeat step 2e again to regenerate the report
  44. Validate results are as expected
  45. Search for and open [FormC], the form configured with the command button report
  46. Populate the fields on the form
  47. Navigate to the "Command Button" field
  48. Click the field to launch the report
  49. Validate [ReportG] is launched
  50. Validate data is displayed as expected
  51. Submit the form
  52. Validate the form submits successfully
  53. Validate the command button report [ReportF] is launched
  54. Validate the data is displayed as expected
  55. Submit the form
  56. Validate the form files successfully
  57. Repeat step 2g again to regenerate the report
  58. Validate results are as expected
Scenario 2: Validate data results from reports generated using an ODBC login connection
Specific Setup:
  • Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
  • Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
  • Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
  • Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
  • In form "Import Reports"
  • Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
  • [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
  • Have three modeled forms available for testing
  • [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
  • [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
  • [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
  • [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
  1. In application "Crystal Reports"
  2. Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
  3. Click to process the report
  4. Validate the report display all data as expected
  5. Close the report
  6. Repeat step 1a again to regenerate the report
  7. Validate results are as expected
  8. Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
  9. Click to process the report
  10. Validate the report display all data as expected
  11. Close the report
  12. Repeat step 1c again to regenerate the report
  13. Validate results are as expected
  14. Log in Avatar
  15. Search for and open [ReportC], the report imported to run from a menu
  16. Validate when selected form the menu, the report launches successfully
  17. Validate the report display all data as expected
  18. Close the report
  19. Repeat step 2a again to regenerate the report
  20. Validate results are as expected
  21. Close the report
  22. Search for and open [ReportD], the "Report Definition" report
  23. Populate any prompts on the form
  24. Click to process the report
  25. Validate the report display all data as expected
  26. Close the report
  27. Repeat step 2b again to regenerate the report
  28. Validate results are as expected
  29. Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
  30. Populate the form
  31. Submit the form as "Final"
  32. Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
  33. Approve/ route and submit the document
  34. Validate submission is successful
  35. Repeat step 2c again
  36. Validate results are as expected
  37. Search for and open [FormB], the form configured with a post filing report
  38. Populate the fields on the form
  39. Submit the form
  40. Validate the form files successfully
  41. Validate the post filing report [ReportF] is launched
  42. Validate the data is displayed as expected
  43. Repeat step 2e again to regenerate the report
  44. Validate results are as expected
  45. Search for and open [FormC], the form configured with the command button report
  46. Populate the fields on the form
  47. Navigate to the "Command Button" field
  48. Click the field to launch the report
  49. Validate [ReportG] is launched
  50. Validate data is displayed as expected
  51. Submit the form
  52. Validate the form submits successfully
  53. Validate the command button report [ReportF] is launched
  54. Validate the data is displayed as expected
  55. Submit the form
  56. Validate the form files successfully
  57. Repeat step 2g again to regenerate the report
  58. Validate results are as expected
Topics
• Query/Reporting • SQL Data Access • Import Reports
Update 96.1 Summary | Details
Sessions Widget
Scenario 1: "Avatar Sessions" Widget - validate data results
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 a 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 and note the current date and time
  4. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA].
  5. If this is 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 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]
  22. Open [ReportA]
  23. Click to generate the report. Note the date and time
  24. Validate the report launches successfully
  25. As [UserA]
  26. Click the 'Refresh' button on the "Avatar Sessions" widget
  27. Validate a row for both [UserA] and [UserB] are listed in the widget
  28. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserA]
  29. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserB]
  30. Validate a new row is present in the widget for [UserC]
  31. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserC].
  32. Note the number of connections in the "# of Connections" column
  33. As [UserC], close [ReportA]
  34. As [UserA]
  35. Click the 'Refresh' button on the "Avatar Sessions" widget
  36. Validate the row for [UserC] is no longer present in the widget, as expected
  37. Validate the rows for [UserA] and [UserB] are still present
  38. As [UserB]
  39. Log out of Avatar
  40. As [UserA]
  41. Click the 'Refresh' button on the "Avatar Sessions" widget
  42. Validate the row for [UserB] is no longer present in the widget, as expected
  43. Validate the row for [UserA] is present, as expected
Data reports/queries
Scenario 1: Validate data results from reports generated using an ODBC login connection
Specific Setup:
  • Create a new user in form "User Definition" [TestUserA] and assign the user permissions to a table, for example table "SYSTEM. patient_current_demographics" is used
  • Have a "Crystal Report" [ReportA] created to display data in that table using and ODBC connection configured for [TestUserA]
  • Have a second user [TestUserB] who that already has access to that same table as [TestUserA]
  • Have a "Crystal Report" [ReportB] created to display data in that table using and ODBC connection configured for [TestUserB]
  • In form "Import Reports"
  • Using the "Import Report as Form" option, have a report [ReportC] imported configured to run from a menu
  • [TestUserC] has access to "Report Definition" form type report [ReportD] for testing. For example, product form "Admits By Program, Zip Code, Ethnicity" can be used
  • Have three modeled forms available for testing
  • [FormA] is enabled for document routing set in form "Document Routing Setup", to use a crystal report [ReportE] as a template to display the document image. (Note: The "Import Report for Document Routing" option in form "Import Reports", can be used to import the report into the system for use)
  • [FormB] configured with a "Post Filing" report [ReportF] that will run at form submission
  • [FormC] configured with a "Command Button" on the form that will run a report [ReportG]
  • [TestUserC] has access to all forms stated in the setup and has the "Crystal Report" application on their desktop
Steps
  1. In application "Crystal Reports"
  2. Open [ReportA], that has the "ODBC" connection configured for [TestUserA]
  3. Click to process the report
  4. Validate the report display all data as expected
  5. Close the report
  6. Repeat step 1a again to regenerate the report
  7. Validate results are as expected
  8. Open [ReportB], that has the "ODBC" connection configured for [TestUserB]
  9. Click to process the report
  10. Validate the report display all data as expected
  11. Close the report
  12. Repeat step 1c again to regenerate the report
  13. Validate results are as expected
  14. Log in Avatar
  15. Search for and open [ReportC], the report imported to run from a menu
  16. Validate when selected form the menu, the report launches successfully
  17. Validate the report display all data as expected
  18. Close the report
  19. Repeat step 2a again to regenerate the report
  20. Validate results are as expected
  21. Close the report
  22. Search for and open [ReportD], the "Report Definition" report
  23. Populate any prompts on the form
  24. Click to process the report
  25. Validate the report display all data as expected
  26. Close the report
  27. Repeat step 2b again to regenerate the report
  28. Validate results are as expected
  29. Search for and open [FormA], the document routing enabled modeled form set to use a "Crystal Report" [ReportE] as template to display the document image
  30. Populate the form
  31. Submit the form as "Final"
  32. Validate the document image is displayed using the format of [ReportE] and data is displayed, as expected
  33. Approve/ route and submit the document
  34. Validate submission is successful
  35. Repeat step 2c again
  36. Validate results are as expected
  37. Search for and open [FormB], the form configured with a post filing report
  38. Populate the fields on the form
  39. Submit the form
  40. Validate the form files successfully
  41. Validate the post filing report [ReportF] is launched
  42. Validate the data is displayed as expected
  43. Repeat step 2e again to regenerate the report
  44. Validate results are as expected
  45. Search for and open [FormC], the form configured with the command button report
  46. Populate the fields on the form
  47. Navigate to the "Command Button" field
  48. Click the field to launch the report
  49. Validate [ReportG] is launched
  50. Validate data is displayed as expected
  51. Submit the form
  52. Validate the form submits successfully
  53. Validate the command button report [ReportF] is launched
  54. Validate the data is displayed as expected
  55. Submit the form
  56. Validate the form files successfully
  57. Repeat step 2g again to regenerate the report
  58. Validate results are as expected
Topics
• Widgets • Forms Designer • Query/Reporting • SQL Data Access • Import Reports
Update 102 Summary | Details
Team Definition - 'Individual Client Assignment' section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team Definition
  • Registry Settings (PM)
  • Progress Notes (Group and Individual)
Scenario 1: Team Definition - 'Individual Client Assignment' section
Specific Setup:
  • Two clients are enrolled in existing episodes (Client A & Client B).
Steps
  1. Access the 'Team Definition' form.
  2. Enter the desired value in the 'Team ID' field.
  3. Enter the desired value in the 'Team Description' field.
  4. Select "Yes" in the 'Active' field.
  5. Select the "Individual Client Assignment" section.
  6. Click [Add New Item].
  7. Select "Client A" in the Client ID' field.
  8. Populate any other desired fields.
  9. Click [Add New Item].
  10. Select "Client B" in the 'Client ID' field.
  11. Populate any other desired fields.
  12. Select the "Team Definition" section.
  13. Click [File] and close the form.
  14. Access the 'Team Definition' form.
  15. Click [Select Team].
  16. Select the team filed in the previous steps and click [OK].
  17. Validate focus does not shift to the "Individual Client Assignment" section automatically.
  18. Select the "Individual Client Assignment" section.
  19. Validate "Client A" and "Client B" are displayed in the 'Individual Client Assignment' grid.
  20. Close the form.
Topics
• Team Definition
Update 106 Summary | Details
Append Document - Approval Comments omitted from workflow
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • Clinical Document Viewer
  • Add Non-User Signature (PM)
  • Progress Notes (Group and Individual) 6
  • ModeledForm
Scenario 1: Progress Notes (Group and Individual) - Validate Approval Comment
Specific Setup:
  • Define additional Avatar users to be as document approvers for the purposed of document routing.
Steps
  1. Open "Document Routing Setup" form.
  2. Select the "Progress Notes (Group and Individual)" form.
  3. Set "Enable Document routing" field to "Yes".
  4. Set "Allow Comments During Approval" to "Yes".
  5. Click "Submit" to file the data.
  6. Open the "Progress Notes (Group and Individual)" form.
  7. File the form in draft mode.
  8. Retrieve the drafted form.
  9. Finalize the form by setting the "Draft/Final" field to "Final".
  10. Submit the form.
  11. Click "Accept".
  12. Provide the password.
  13. When prompted, provide the "Approval Comments".
  14. Open the "Clinical Document Viewer" form.
  15. Locate and view the document that was just filed.
  16. Validate that the document includes the authors Approval Comments in the signature area of the document.
  17. Open the "System Management Portal".
  18. Using SQL, execute the following query: SELECT * from DocR.comments
  19. Validate that a row has been added to the table.
  20. Open the "Progress Notes (Group and Individual)" form. File the form in draft mode.
  21. Retrieve the drafted form.
  22. Finalize the form by setting the "Draft/Final" field to "Final".
  23. Submit the form.
  24. Click "Accept and Route".
  25. Provide the password.
  26. Indicate who the approver(s) are.
  27. To Do's are sent to the approver(s).
  28. Log into Avatar using the User ID of an additional approver.
  29. Select the To Do the "My To Do" widget.
  30. Click "Accept" to approve the form.
  31. Enter the "Approval Comments".
  32. Log into Avatar using the User ID of an additional approver.
  33. Select the To Do the "My To Do" widget.
  34. Click "Accept" to approve the form.
  35. Enter the "Approval Comments" for this approver.
  36. Open the "Clinical Document Viewer" form.
  37. Locate and view the document that was just filed.
  38. Validate that the document includes the approver(s) Approval Comments in the signature area of the document.
  39. Open the "System Management Portal".
  40. Using SQL, execute the following query: SELECT * from DocR.comments
  41. Validate that a row has been added for each "Approval Comment" entered.
Scenario 2: Add Non-User Signature - Form Validation
Specific Setup:
  • Using the "Document Routing Setup" form
  • Enabled document routing for any progress note form.
  • Create a user modeled form in the PM namespace.
  • This form must contain a "Draft/Final" field.
  • Using "Document Routing Setup"
  • Enable document routing for the user modeled form.
  • Click "Yes" in the "Allow Approval Comments" field.
  • Refresh the menus.
  • Select or admit client to be used as test client into any valid program.
Steps
  1. Open the progress note form from the Setup section.
  2. Fill out and finalize a progress note.
  3. Click "Accept" and provide the password.
  4. Open the "Add Non-User Signature" form.
  5. Select the progress note that was filed in the previous step.
  6. Add text to the "Comments" field.
  7. Submit to file.
  8. Open the "Clinical Document Viewer" form.
  9. Bring up the document the non-user signature was added to.
  10. Validate the document displays as it was recorded along with the non-user signature line.
  11. Open the user modeled form.
  12. Fill out all required/desired fields.
  13. Click "Final" in the "Draft/Final" field.
  14. Click "Submit" button.
  15. Click "Sign" button'.
  16. Provider the user's password.
  17. Fill in the "Approval Comments" field.
  18. Open the "Clinical Document Viewer" form.
  19. Validate the document that was just saved displays as it was recorded.
  20. Open the "Add Non-User Signature" form.
  21. Select the document that was just saved.
  22. Display the document to validate the signature line and approval comments are listed.
  23. Enter the text in the "Comments" field.
  24. Click "Accept".
  25. Provide the user's password.
  26. Open the "Clinical Document Viewer" form.
  27. Validate the document that was just saved displays as it was recorded.
Scenario 3: Append Documents
Specific Setup:
  • Create a user modeled form in the PM namespace.
  • This form must contain a "Draft/Final" field.
  • Using "Document Routing Setup"
  • Enable document routing for the user modeled form.
  • Click "Yes" in the "Allow Approval Comments" field.
  • Refresh the menus.
  • Select or admit client to be used as test client into any valid program.
Steps
  1. Open the user modeled form.
  2. Fill out all required/desired fields.
  3. Click "Final" in the "Draft/Final" field.
  4. Click "Submit" button.
  5. Click "Sign" button'.
  6. Provider the user's password.
  7. Fill in the "Approval Comments" field.
  8. Open the "Clinical Document Viewer" form.
  9. Validate the document that was just saved displays as it was recorded.
  10. Open the "Append Document" form.
  11. Select the document that was just saved.
  12. Display the document to validate the signature line and approval comments are listed.
  13. Enter the text to be appended to the document.
  14. Click "Sign".
  15. Provide the user's password.
  16. Open the "Clinical Document Viewer" form.
  17. Validate the document that was just saved displays as it was recorded.
Document Management Defaults - Perceptive synchronization streamlined.
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
  • Document Capture Window
  • Clinical Document Viewer
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: Document Management Defaults - Perceptive Synchronization Options field
Steps

Internal Testing Only

Scenario 3: Document Management Definition - Perceptive Syncing Form Definitions in Multiple Server environment
Specific Setup:
  • To be tested in a multiple server environment that has multiple root system codes.
  • Using the "Document Management Definition" form:
  • Identify a form that exists in all system codes.
Steps
  1. Using the "Document Management Definition" form:
  2. Edit the existing form identified as existing in all root system codes.
  3. File the form.
  4. Open the "Client Document Capture" form.
  5. Scan or import a document.
  6. Select the form edited in "Document Management Definition".
  7. Scan or import the document.
  8. Using "Clinical Document Viewer", select the test client.
  9. Validate the document that was just filed for the form that exists in all root system codes displays as it was previously filed.
Clinical Document Viewer - Printing Perceptive documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Batch Capture and Indexing
  • Chart Review
  • Clinical Document Viewer
Scenario 1: Perceptive scan, import, print,view - JxBrowser enabled
Specific Setup:
  • Perceptive storage method must be utilized.
Steps
  1. Open the "Batch Capture and Indexing" form.
  2. Click "Capture".
  3. Select "Scanner" as the "Source".
  4. Scan in a document.
  5. Validate that the document capture opens in a window within Avatar and not as an Internet Explorer window.
  6. Close the batch by selecting "Send to" and sent it to the Batch Validate queue.
  7. Open the Avatar Batch Validate queue.
  8. Open the batch that was just scanned in.
  9. Click "Submit" to save the document to Avatar.
  10. Open the "Batch Capture and Indexing" form.
  11. Click "Capture".
  12. Select "File" as the "Source".
  13. Browse to the location of the file to be imported.
  14. Import the file.
  15. Validate that the document capture opens in a window within Avatar and not as an Internet Explorer window.
  16. Close the batch by selecting "Send to" and sent it to the Batch Validate queue.
  17. Open the Avatar Batch Validate queue.
  18. Open the batch that was just scanned in.
  19. Click "Submit" to save the document to Avatar.
  20. Close the form.
  21. Open the "Chart Review" form.
  22. Select the test client.
  23. Navigate to the category/section that the documents were scanned/imported into.
  24. View the scanned document.
  25. Click "Print".
  26. Validate that the print window opens in Avatar and not in Internet Explorer.
  27. Print the document.
  28. View the imported document.
  29. Click "Print".
  30. Validate that the print window opens in Avatar and not in Internet Explorer
  31. Print the document.
  32. Select the "Document Capture" link in the "Chart Review" form.
  33. Select "Capture".
  34. Select "Scanner" as the "Source".
  35. Scan in a document.
  36. Validate that the capture window opens in Avatar and not in Internet Explorer.
  37. Save the document to Avatar.
  38. Select the "Document Capture" link in the "Chart Review" form.
  39. Select "Capture".
  40. Select "Filer" as the "Source".
  41. Browse to the location on server of the file to be imported.
  42. Import a document.
  43. Validate that the capture window opens in Avatar and not in Internet Explorer.
  44. Save the document to Avatar.
  45. Navigate to the section that the items scanned/imported in with "Chart Review" are stored.
  46. Open the scanned document.
  47. Click "Print".
  48. Validate that the document displays in an Avatar popup and not an Internet Explorer popup.
  49. Print the document.
  50. Open the imported document.
  51. Click "Print".
  52. Validate that the document displays in an Avatar popup and not an Internet Explorer popup.
  53. Print the document.
  54. Open "Batch Capture and Indexing".
  55. Scan in a large multi page document.
  56. Open "Clinical Document Viewer".
  57. Open the large document.
  58. Validate that the document displays in an Avatar popup and not an Internet Explorer popup.
  59. Click "Print".
  60. Validate that the document displays in an Avatar popup and not an Internet Explorer popup.
  61. Print the document.
Scenario 2: Perceptive Individual Scanning/Importing/Viewing/Printing through Chart Review
Specific Setup:
  • Perceptive storage method must be utilized.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client and episode.
  3. Open the "Document Capture" form within Chart.
  4. Scan a document.
  5. Assign the document to a particular "Document Type".
  6. Save the document.
  7. Import a document.
  8. Assign the document to a particular "Document Type".
  9. Save the document.
  10. Navigate to the section designated by the "Document Type" the document was saved under.
  11. Navigate to the "Episode" tab.
  12. Open the document(s).
  13. Validate the document(s) can be viewed and display as scanned.
  14. Validate the document(s) can be printed and display as scanned.
  15. Close the document.
  16. Open the "Clinical Document Viewer".
  17. Select the desired client and episode.
  18. Locate the document(s) that were just scanned in or imported.
  19. Validate the document(s) can be viewed and display as scanned.
  20. Validate the document(s) can be printed and display as scanned.
  21. Close the form.
Topics
• Progress Notes (Group And Individual) • Envelope Import • Add Non-User Signature • Document Management • NX • Perceptive • Document Scan/Import
Update 108 Summary | Details
Support for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Vitals Entry
  • CareFabric Monitor
  • Discharge
  • Diagnosis
  • GAIN Agency Configuration
  • Scheduling Calendar
Scenario 1: 'Admission' form - Validate the 'ProgramAdmissionCreated' payload
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter any new value in the 'Last Name' and 'First Name' fields.
  4. Select any value in the 'Sex' field.
  5. Click [Search].
  6. Validate a "Search Results" message is displayed stating: No matches found.
  7. Click [New Client].
  8. Validate a "Client" message displays indicating "Auto Assign Next ID Number?"
  9. Click [Yes].
  10. Enter a date prior to daylight savings time in the 'Preadmit/Admission Date' field (Ex. 03/10/2023).
  11. Enter "10:00 AM" in the 'Preadmit/Admission Time' field.
  12. Select the desired program in the 'Program' field.
  13. Enter any value in the 'Type Of Admission' field.
  14. Enter the desired practitioner in the 'Admitting Practitioner' field.
  15. Click [Submit].
  16. Access the 'CareFabric Monitor' form.
  17. Enter the current date in the 'From Date' field.
  18. Enter the current date in the 'Through Date' field.
  19. Enter the client admitted in the previous steps in the 'Client ID' field.
  20. Click [View Activity Log].
  21. Validate the 'CareFabric Monitor Report' is displayed.
  22. Select the 'ProgramAdmissionCreated' activity type.
  23. Click [Click to View Record].
  24. Validate all filed information is populated.
  25. Validate the 'admissionDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' populated in the previous steps with the correct time zone offset prior to daylight savings time (Ex: 2023-03-01T10:00:00.000-05:00).
  26. Close the report and the form.
  27. Access the 'Admission' form.
  28. Verify the 'Select Client' dialog is displayed.
  29. Enter any new value in the 'Last Name' and 'First Name' fields.
  30. Select any value in the 'Sex' field.
  31. Click [Search].
  32. Validate a "Search Results" message is displayed stating: No matches found.
  33. Click [New Client].
  34. Validate a "Client" message displays indicating "Auto Assign Next ID Number?"
  35. Click [Yes].
  36. Enter a date during daylight savings time in the 'Preadmit/Admission Date' field (Ex. 05/01/2023).
  37. Enter "10:00 AM" in the 'Preadmit/Admission Time' field.
  38. Select the desired program in the 'Program' field.
  39. Enter any value in the 'Type Of Admission' field.
  40. Enter the desired practitioner in the 'Admitting Practitioner' field.
  41. Click [Submit].
  42. Access the 'CareFabric Monitor' form.
  43. Enter the current date in the 'From Date' field.
  44. Enter the current date in the 'Through Date' field.
  45. Enter the second client admitted in the previous steps in the 'Client ID' field.
  46. Click [View Activity Log].
  47. Validate the 'CareFabric Monitor Report' is displayed.
  48. Select the 'ProgramAdmissionCreated' activity type.
  49. Click [Click to View Record].
  50. Validate all filed information is populated.
  51. Validate the 'admissionDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' populated in the previous steps with the correct time zone offset during daylight savings time (Ex: 2023-05-01T10:00:00.000-04:00).
  52. Close the report and the form.
Scenario 2: 'Discharge' form - Validate the 'ProgramDischargeCreated' payload
Specific Setup:
  • Two clients must be enrolled in existing episodes (Client A & Client B).
Steps
  1. Select "Client A" and access the 'Discharge' form.
  2. Enter a date prior to daylight savings time in the 'Date Of Discharge' field (Ex. 03/10/2023).
  3. Enter "10:00 AM" in the 'Discharge Time' field.
  4. Select any value in the 'Type Of Discharge' field.
  5. Enter the desired practitioner in the 'Discharge Practitioner' field.
  6. Select the desired value in the 'Discharge Client Living Arrangement' field.
  7. Enter the desired value in the 'Hospital Discharge Instructions' field.
  8. Click [Submit].
  9. Access the 'CareFabric Monitor' form.
  10. Enter the current date in the 'From Date' field.
  11. Enter the current date in the 'Through Date' field.
  12. Enter "Client A" in the 'Client ID' field.
  13. Click [View Activity Log].
  14. Select "ProgramDischargeCreated" in the 'Activity Type' field.
  15. Click [Click to View Record].
  16. Validate all filed information is populated.
  17. Validate the 'dischargeDate' field contains the 'Date Of Discharge' and 'Discharge Time' populated in the previous steps with the correct time zone offset prior to daylight savings time (Ex: 2023-03-01T10:00:00.000-05:00).
  18. Close the report and the form.
  19. Select "Client B" and access the 'Discharge' form.
  20. Enter a date during daylight savings time in the 'Date Of Discharge' field (Ex. 05/01/2023).
  21. Enter "10:00 AM" in the 'Discharge Time' field.
  22. Select any value in the 'Type Of Discharge' field.
  23. Enter the desired practitioner in the 'Discharge Practitioner' field.
  24. Select the desired value in the 'Discharge Client Living Arrangement' field.
  25. Enter the desired value in the 'Hospital Discharge Instructions' field.
  26. Click [Submit].
  27. Access the 'CareFabric Monitor' form.
  28. Enter the current date in the 'From Date' field.
  29. Enter the current date in the 'Through Date' field.
  30. Enter "Client B" in the 'Client ID' field.
  31. Click [View Activity Log].
  32. Select "ProgramDischargeCreated" in the 'Activity Type' field.
  33. Click [Click to View Record].
  34. Validate all filed information is populated.
  35. Validate the 'dischargeDate' field contains the 'Date Of Discharge' and 'Discharge Time' populated in the previous steps with the correct time zone offset during daylight savings time (Ex: 2023-05-01T10:00:00.000-04:00).
  36. Close the report and the form.
Scenario 3: Diagnosis - Validate the 'DiagnosisCreated' and 'DiagnosisUpdated' SDK events
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select the desired value in the 'Type Of Diagnosis' field.
  3. Enter the desired date in the 'Date Of Diagnosis' field.
  4. Enter the desired time the 'Time Of Diagnosis' field.
  5. Click [New Row].
  6. Select the desired value in the 'Diagnosis Search' field.
  7. Select "Active" in the 'Status' field.
  8. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  9. Click [Submit].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Select "DiagnosisCreated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisCreated' record.
  16. Click [Click To View Record].
  17. Validate the 'startDate' field contains the 'Date Of Diagnosis' and 'Time Of Diagnosis' populated in the previous steps.
  18. Validate the 'statusCode' - 'code' field contains "1".
  19. Validate the 'statusCode' - 'displayName' field contains "Active".
  20. Validate all other previously filed data displays as expected.
  21. Close the report and the form.
Scenario 4: Create an appointment and validate the 'AppointmentCreated' SDK event is raised
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Multiple practitioners are defined with hours for scheduling (Practitioner A, Practitioner B and Practitioner C).
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Right click in the 'Appointment Grid' and click [Add Appointment].
  3. Set the 'Service Code' field to the desired service code.
  4. Set the 'Client' field to "Client A".
  5. Select the desired value in the 'Episode Number' field.
  6. Set the 'Practitioner' field to "Practitioner A".
  7. Select the desired location in the 'Location' field.
  8. Set the 'First Co-Practitioner' field to "Practitioner B".
  9. Set the 'Second Co-Practitioner' field to "Practitioner C".
  10. Fill out all required fields.
  11. Click [Submit].
  12. Validate successful submission.
  13. Validate the scheduled appointment is added to the 'Scheduling Calendar' form.
  14. Access the 'CareFabric Monitor' form.
  15. Enter the current date in the 'From Date' field.
  16. Enter the current date in the 'Through Date' field.
  17. Enter "Client A" in the 'Client ID' field.
  18. Click [View Activity Log].
  19. Select "AppointmentCreated" in the 'Activity Type' field.
  20. Click [Click to View Record].
  21. Validate the 'appointmentID' - 'humanReadableValue' - 'id' field contains the scheduled appointment ID.
  22. Validate the 'scheduledProviderIDs' - 'humanReadableValue' - 'id' field contains the name and ID for the co-practitioners.
  23. Validate the 'scheduledProviderIDs' - 'humanReadableValue' - 'id' field contains the name and ID for "Practitioner A".
  24. Validate the 'scheduledProviderIDs' - 'humanReadableValue' - 'id' field contains the name and ID for "Practitioner B".
  25. Validate the 'scheduledProviderIDs' - 'humanReadableValue' - 'id' field contains the name and ID for "Practitioner C".
  26. Close the report and the form.
Topics
• Admission • CareFabric Monitor • Discharge • Forms
Update 116 Summary | Details
Rule Based Routing - Perceptive documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Routing Role Definition
  • Routing Queue Definition
  • Routing Status Definition
  • Routing Role Assignment
  • Routing Assignment Definition
  • Routing Configuration Definition
  • Routing Views Definition
  • Routing Action Definition
  • Ambulatory Progress Notes
  • Rule Based Routing
  • Routing Worklist Item
Scenario 1: Validate 'Rule Based Routing' document routing functionality
Specific Setup:
  • Multiple users must be created with access to all forms: USER A, USER B, USER C, and USER D.
  • A user modeled form must be imported that has 'Service Documentation' fields or a progress note form must be used.
  • Document routing must be enabled for this form.
  • The 'Rule Based Routing' widget must be added to the myDay view.
  • Must create four roles in the 'Routing Role Definition' form.
  • Must assign users with each of the roles created in the 'Routing Role Assignment' form.
  • Must create queues and assign a form to them in the 'Routing Queue Definition' form (Queue 1, Queue 2, and Queue 3).
  • Must create statuses associated with each queue in the 'Routing Status Definition' form.
  • Must configure each queue in the 'Routing Assignment Definition' form.
  • Must select a form in the 'Routing Configuration Definition' form (For example Ambulatory Progress Notes).
  • Must configure header fields and worklist widget details for each queue in the 'Routing Views Definition' form.
  • Must have specific actions configured to route documents to subsequent queues in the 'Routing Action Definition' form.
  • Must be signed in as User A.
Steps
  1. Select any desired client (Client A) and access the 'Ambulatory Progress Notes' form.
  2. Select any value in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Populate all required and desired fields.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit] and [Sign and Route/Notify].
  7. Input password associated with "User A" and click [Verify].
  8. Select the practitioner associated with "User A" in the 'Approver' field.
  9. Click [Add] and [Submit].
  10. Navigate to the 'My To-Do's' widget.
  11. Validate the document filed is in the 'Documents to Sign' column.
  12. Click [Review].
  13. Validate the document opens.
  14. Click [Accept] and [Sign].
  15. Enter the password associated with "User A" and click [Verify].
  16. Logout.
  17. Login with "User B".
  18. Navigate to the 'Rule Based Routing' widget.
  19. Select "Queue 1" in the queue field.
  20. Select the entry associated with "Client A".
  21. Click [Launch Worklist Item].
  22. Fill out the desired and required fields.
  23. Click [Save for Later].
  24. Validate the entry is now "In Process" in the 'Status' field.
  25. Select the item again and click [Launch Worklist Item].
  26. Click [Submit].
  27. Refresh the 'Rule Based Routing' widget.
  28. Validate the entry is no longer present.
  29. Logout.
  30. Login with "User C".
  31. Navigate to the 'Rule Based Routing' widget.
  32. Select "Queue 2" in the queue field.
  33. Select the entry associated with "Client A".
  34. Click [Launch Worklist Item].
  35. Fill out the desired and required fields.
  36. Click [Submit].
  37. Refresh the 'Rule Based Routing' widget.
  38. Validate the entry is no longer present.
  39. Logout.
  40. Login with "User D".
  41. Navigate to the 'Rule Based Routing' widget.
  42. Select "Queue 3" in the queue field.
  43. Select the entry associated with "Client A".
  44. Click [Launch Worklist Item].
  45. Fill out the desired and required fields.
  46. Click [Submit].
  47. Refresh the 'Rule Based Routing' widget.
  48. Validate the entry is now "Completed" in the 'Status' field.
  49. Logout.
Topics
• Document Routing • Rule Based Routing
 

RADplus_2023_Monthly_Release_2023.03.01_Details.csv