Skip to main content

RADplus 2022 Monthly Release 2022.01.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 11 Summary | Details
Product Updates - Version upgrades
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Current Server Information (PM)
  • Product Updates (PM)
  • Globals
  • View Global Data
Scenario 1: "Product Updates" form - Post installation validations
Specific Setup:
  • Have a system with one or more child namespace. For example "CWS", "MSO" and "CFMS"
  • The system is ready to upgrade to following years module update for "RADPlus". For this test, RADplus "2021" will be upgraded to "2022"
Steps
  1. Open the "Product Updates" form.
  2. Select the "PM" namespace from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location of the "RADplus" update file and select the file
  5. Click [Install Update/Customization Pack].
  6. Click [OK] when the install has completed
  7. Click [Close Form]
  8. Open the "Current Server Information" form in the "PM" namespace
  9. Validate the "RADplus Updates" results text box includes two entries
  10. Update #001 - RADplus 2022 Loaded ...
  11. Update #Pre_installation - RADplus 2022 Loaded ....
  12. Close the form
  13. Open the "Current Server Information" form for a child namespace, for example "CWS"
  14. Validate the "RADplus Updates" results text box includes the entry
  15. Update #001 - RADplus 2022 Loaded ...
  16. Close the form
  17. Open the "Current Server Information" form for any other child namespaces
  18. Validate the "RADplus Updates" results text box includes the entry
  19. Update #001 - RADplus 2022 Loaded...
  20. Close the form
Topics
• Cache • Update Install • NX
Update 15 Summary | Details
State Form File - Output
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Task Scheduler
  • System Task Scheduler
  • State Form File Generation
Scenario 1: Validate a state form file generated via the "State Form Task Scheduler" "
Specific Setup:
  • Have a state form definition file created in form "State Form Definition" that with the "Record Delimiter" field set to "Carriage Return + Line Feed" [DefinitionA]
Steps
  1. Open form "State Form Task Scheduler"
  2. Select "Single Definition" in the "Type" field
  3. Select the [DefinitionA] from the "Select Batch or Definition" drop down list
  4. Set the "File Description" field to a desired file name
  5. Select "Static" in the "Change From Date"
  6. Set the "Static Date" field to today's date
  7. Select "Static" in the "Change Through Date"
  8. Set the "Static Date" field to today's date
  9. Select "Yes" in the "Create File" field
  10. Click [Submit]
  11. At the dialog, "Filed. In order for compiles to be run, the new task must be scheduled using the 'System Task Scheduler' form", click [OK]
  12. Open the "System Task Scheduler" form
  13. In the "Schedule(s)" field, select the task created in step for [DefinitionA] in step 1
  14. Select a desired recurrence type pattern from the "Recurrence Pattern" field. For example "Daily"
  15. Populate a desired value in the "Task Occurrence Sequence".
  16. Populate the "Start By" field with today's date
  17. Populate the "Start Time" field with a time later than the current time
  18. Click [Schedule Task]
  19. Close the form
  20. Wait till the "Start Time" set in step 2 has passed
  21. Open the "State Form File Generation" form.
  22. Select [DefinitionA] in the "State Form" field
  23. Select "Dump File" in the "File Generation Options" field
  24. In the "Select File" field, select the compiled file for [DefinitionA], generated by the automated task set up in step 2
  25. Click [Process]
  26. Validate there is a carriage return and a line feed after each record displayed in the output, as expected displayed, has a carriage return and a line feed after it on the report
State Form Definition - XML Header Tags
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: 'XML type "State Form Definition" file validations
Specific Setup:
  • Have a definition created [DefintionA] in form "State Forms Definition" with a "File Type" set to "XML".
Steps
  1. Open form "State Form Definition"
  2. Set field "New or Existing" to "Existing"
  3. Select [DefinitionA] in the "Select State Form" field
  4. Navigate to the "Definitions" Options" field at the bottom of the section
  5. Deselect "Remove XML Declaration", if it is currently selected
  6. Click [File Form]
  7. Validate filing completes successfully
  8. Close the form
  9. Open form "State Form File Generation"
  10. Select the [DefinitionA] in field "State Form"
  11. In the "File Generation Options" field, select "Compile"
  12. Click [Process]
  13. Validate the process completes successfully
  14. In the "File Generation Options" field, select "Dump File"
  15. Click [Process]
  16. Validate the output of the state form report includes the "XML declaration" header tag in the first line of the output. For example: "<?XML version="1.0" encoding="UTF-8"?>"
  17. Close the report and close the form
  18. Open form "State Form Definition"
  19. Set field "New or Existing" to "Existing"
  20. Select [DefinitionA] in the "Select State Form" field
  21. Navigate to the "Definitions" Options" field at the bottom of the section
  22. Select the "Remove XML Declaration" check box
  23. Click [File Form]
  24. Validate filing completes successfully
  25. Close the form
  26. Open form "State Form File Generation"
  27. Select the [DefinitionA] in field "State Form"
  28. In the "File Generation Options" field, select "Compile"
  29. Click [Process]
  30. Validate the process completes successfully
  31. In the "File Generation Options" field, select "Dump File"
  32. Click [Process]
  33. Validate the output of the state form report no longer includes the "XML declaration" header tag in the output of the report.
  34. Close the report and close the form
Topics
• State Form Task Scheduler • NX • State Form Tools
Update 20 Summary | Details
RADplus modeling - Future Dates
Scenario 1: Future Dates - Table Definition
Specific Setup:
  • An envelope must be created or imported with the 3 fields:
  1. A date field "TestingTheAllow" set to allow future dates ("No").
  2. A date field "TestingTheError" set to an error dialog when future dates are selected ("Error").
  3. A date field "TestingTheWarning" set to a warning("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the newly created form.
  2. Set the 'TestingTheAllow' field to a future date.
  3. Validate the 'TestingTheAllow' field is set to a future date.
  4. Set the 'TestingTheWarning' field to a future date.
  5. Validate the 'Warning' Dialog is displayed and click [Cancel].
  6. Set the 'TestingTheWarning' field to the current date.
  7. Validate the 'TestingTheWarning' field is set to the current date.
  8. Set the 'TestingTheError' field to a future date.
  9. Validate the 'Error' Dialog is displayed and click [OK].
  10. Set the 'TestingTheError' field to the current date.
  11. Validate the 'TestingTheError' field is set to the current date.
Site Specific Section Modeling - Future Dates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Disclosure Management
Scenario 1: New Service note in 'Progress Notes (Group and Individual)'
Specific Setup:
  • Using 'Site Specific Section Modeling', 3 fields must be created:
  1. A date field "TestingTheAllow" set to allow future dates ("No").
  2. A date field "TestingTheError" set to an error dialog when future dates are selected ("Error").
  3. A date field "TestingTheWarning" set to a warning ("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select desired episodes from the 'Request Episode(s)' field.
  3. Select 'New Service'.
  4. Select "Psychologist" from the 'Note Type' field.
  5. Set 'Notes Field' field to "test".
  6. Search for and select a valid practitioner in the 'Practitioner' field.
  7. Set the 'Date Of Service' field to a future date.
  8. Validate the 'Warning' Dialog is displayed and click [Cancel].
  9. Set the 'Date Of Service' field to a date in the past.
  10. Validate the 'Date Of Service' field is set to a date in the past.
  11. Search for and select any desired code in the 'Service Charge Code'.
  12. Select "Draft" from the 'Draft/Final' field.
  13. Set the 'Date' field to the current date.
  14. Set the 'TestingTheWarning' field to a future date.
  15. Validate the 'Warning' Dialog is displayed and click [Cancel].
  16. Set the 'TestingTheWarning' field to a future date.
  17. Validate the 'Warning' Dialog is displayed and click [OK].
  18. Validate the 'TestingTheWarning' field contains a future date.
  19. Set the 'TestingTheWarning' field to the current date.
  20. Validate the 'TestingTheWarning' field is set to the current date.
  21. Set the 'TestingTheError' field to a date future date.
  22. Validate the 'Error' Dialog is displayed and click [OK].
  23. Set the 'TestingTheError' field to the current date.
  24. Validate the 'TestingTheError' field is set to the current date.
  25. Set the 'TestingTheAllow' field to a future date.
  26. Validate the 'TestingTheAllow' field is set to a future date.
  27. Click [File Note].
  28. Access the clients chart and confirm a new progress form was filed.
Scenario 2: Disclosure Management - Future Dates
Specific Setup:
  • Using 'Site Specific Section Modeling' the following fields must be set accordingly:
  1. "Request Date" set to a 'warning' ("Warning").
  2. "'Request For Information Start Date" set to an error dialog when future dates are selected ("Error").
  3. "'Request For Information End Date" set to an error dialog when future dates are selected ("Error").
  4. "Authorization Start Date" set to a warning ("Warning").
  5. "Authorization End Date" set to a warning ("Warning").
  6. "Disclosure Date" set to a warning ("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Disclosure Management' form.
  2. Set the 'Request Date' field to a future date.
  3. Validate the 'Warning' Dialog is displayed and click [Cancel].
  4. Set the 'Request Date' field to the current date.
  5. Validate the 'Request Date' field is set to the current date.
  6. Set the 'Request For Information Start Date' field to a future date.
  7. Validate the 'Error' Dialog is displayed and click [OK].
  8. Set the 'Request For Information Start Date' field to a date in the past.
  9. Validate the 'Request For Information Start Date' field is set a date in the past.
  10. Set the 'Request For Information End Date' field to a future date.
  11. Validate the 'Error' Dialog is displayed and click [OK].
  12. Set the 'Request For Information End Date' field to the current date.
  13. Validate the 'Request For Information End Date' field is set to the current date.
  14. Select desired episodes from the 'Request Episode(s)' field.
  15. Select desired items from the 'Requested Chart Items' field.
  16. File and save an Organization.
  17. Select 'Authorization'.
  18. Set the 'Authorization Start Date' field to a future date.
  19. Validate the 'Warning' Dialog is displayed and click [Cancel].
  20. Set the 'Authorization Start Date' field to a date in the past.
  21. Validate the 'Authorization Start Date' field is set a date in the past.
  22. Set the 'Authorization End Date' field to a future date.
  23. Validate the 'Warning' Dialog is displayed and click [Cancel].
  24. Set the 'Authorization End Date' field to the current date.
  25. Validate the 'Authorization End Date' field is set to the current date.
  26. Select desired episodes from the 'Authorization Episode(s)' field.
  27. Select "Yes" and click [Update Chart Items Authorized for Disclosure].
  28. Click [Save].
  29. Select 'Disclosure'.
  30. Set the 'Disclosure Date' field to a future date.
  31. Validate the 'Warning' Dialog is displayed and click [Cancel].
  32. Set the 'Disclosure Date' field to the current date.
  33. Set the 'Disclosure Time' to the current time.
  34. Select desired charts from the 'Chart Disclosure Information'.
  35. Select 'Electronic' and click [Process].
  36. Select "Client A" and access the 'Disclosure Management' form.
  37. Validate a new disclosure was filed.
Topics
• Envelope Definition • Progress Notes • Disclosure
Update 25 Summary | Details
Support is added for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CarePOV Management
  • CareFabric Monitor
  • Registry Settings (PM)
  • Treatment Plan
  • Diagnosis
  • Staff Members Hours And Exceptions
  • Problem List
Scenario 1: CarePOV Management - 'Electronic Visit Verification' - 'Celltrak' integration
Specific Setup:
  • myAvatar must be configured for Electronic Visit Verification.
  • myAvatar must be configured to integrate with Celltrak and vice versa.
  • A New Product using EVV must be created in the 'CareFabric Integration Management' form and a 'User to send To-Dos' must be filed. In the 'Code Mappings' section of this form a "Note Type" mapping type must be created for EVV.
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the 'Electronic Visit Verification' section.
  3. Select "Celltrak" in the 'EVV Vendor' field.
  4. Select the desired user in the 'EVV Admin User ID' field. Please note: this will determine the user that will be notified if EVV communication is lost due to technical issues. The user will be notified via To-Do in the 'My To Do's' widget.
  5. Enter the desired value in the 'Vendor Account Number' field.
  6. Select the desired progress note form in the 'Progress Note Form' field.
  7. Select "Yes" in the 'Save Progress Notes' field.
  8. Select the desired site in the 'Site' field.
  9. Enter the desired value in the 'Medicaid Provider ID' field.
  10. Validate the 'Required Sections' field is displayed and contains: "SendTelephonyPatient - PrimaryDiagnosis", "SendTelephonyPatient - PayerProgram", and "SendTelephonyPatient - PayerID". Please note: when selected, these sections will be required in order to trigger the 'SendTelephonyPatient' EVV action.
  11. Select the desired value(s) in the 'Required Sections' field.
  12. Validate the 'Provider Address To Be Sent' field is displayed and contains: "Home" and "Office". Validate "Office" is the default value. Please note: the 'Addresses' section of the 'SendTelephonyResource' EVV action payload will be determined based on this selection.
  13. Select the desired value in the 'Provider Address To Be Sent' field.
  14. Validate the 'Payor Program ID' grid contains three columns: "Guarantor", "Payer ID", and "Payer Program".
  15. Click [New Row].
  16. Validate the 'Guarantor' field of the 'Payor Program ID' grid contains all guarantors regardless of financial class.
  17. Select the desired value in the 'Guarantor' field of the 'Payor Program ID' table.
  18. Enter the desired value in the 'Payer ID' field of the 'Payor Program ID' table.
  19. Enter the desired value in the 'Payer Program' field of the 'Payor Program ID' table.
  20. Validate the 'Progress Notes Form Mapping' grid is displayed and contains three columns: "Service Code", "Program", and "Progress Notes Form". Please note: This grid allows the ability to determine the progress note forms that will be used when saving notes.
  21. Click [New Row].
  22. Select the desired value in the 'Service Code' field.
  23. Select the desired value in the 'Program' field.
  24. Select the desired value in the 'Progress Notes Form' field.
  25. [Submit].
Scenario 2: Progress Notes (Group and Individual) - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • The 'Progress Notes' widget is on the HomeView for the logged in user.
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings]
  4. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  5. Click [OK].
  6. Validate the 'Registry Setting Details' field contains "Enter "Y" to add 'Treatment Plan' grid field to the form. Enter "YD" to add the grid field and enable the functionality to default the previously selected treatment plan to the new row. Enter "N" to remove the field from the form."
  7. Enter "Y" in the 'Registry Setting Value' field.
  8. Click [Submit].
  9. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  10. Click [OK].
  11. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  12. Click [No].
  13. Access the 'Progress Notes (Group and Individual)' form.
  14. Verify the 'Treatment Plan' grid is displayed.
  15. Enter "Client A" in the 'Select Client' field.
  16. Select the desired episode in the 'Select Episode' field.
  17. Select "Independent Note" in the 'Progress Note For' field.
  18. Select any value in the 'Note Type' field.
  19. Click [New Row] in the 'Treatment Plan' grid.
  20. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  21. Click [View] in the 'Select T.P. Item Note Addresses' field.
  22. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  23. Select the desired treatment plan item in the 'Treatment Plan' window.
  24. Click [Return].
  25. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  26. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  27. Enter the desired value in the 'Notes Field' field.
  28. Select "Draft" in the 'Draft/Final' field.
  29. Click [File Note].
  30. Validate a "Progress Notes" message is displayed stating: Note Filed.
  31. Click [OK].
  32. Validate the 'Treatment Plan' grid no longer contains the previously filed row.
  33. Select the note filed in the previous steps in the 'Select Draft Note To Edit' field.
  34. Validate the 'Treatment Plan' grid contains the row filed in the previous steps.
  35. Click [New Row] in the 'Treatment Plan' grid.
  36. Validate the 'Select T.P. Version' field does not contain a value.
  37. Select the second row in the 'Treatment Plan' grid.
  38. Click [Delete Row].
  39. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows?
  40. Click [Yes].
  41. Select "Final" in the 'Draft/Final' field.
  42. Click [File Note].
  43. Validate a "Progress Notes" message is displayed stating: Note Filed.
  44. Click [OK] and close the form.
  45. Access the 'Registry Settings' form.
  46. Enter "Enable Treatment Plan Grid" in the 'Limit Registry Settings to the Following Search Criteria' field.
  47. Click [View Registry Settings]
  48. Select "Enable Treatment Plan Grid" for 'Progress Notes (Group and Individual)' from the 'Registry Setting' list.
  49. Click [OK].
  50. Enter "YD" in the 'Registry Setting Value' field.
  51. Click [Submit].
  52. Validate a "Registry Editor Filing" message is displayed stating: Successful filing.
  53. Click [OK].
  54. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  55. Click [No].
  56. Access the 'Progress Notes (Group and Individual)' form.
  57. Verify the 'Treatment Plan' grid is displayed.
  58. Enter "Client A" in the 'Select Client' field.
  59. Select the desired episode in the 'Select Episode' field.
  60. Select "Independent Note" in the 'Progress Note For' field.
  61. Select any value in the 'Note Type' field.
  62. Click [New Row] in the 'Treatment Plan' grid.
  63. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  64. Click [View] in the 'Select T.P. Item Note Addresses' field.
  65. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  66. Select the desired treatment plan item in the 'Treatment Plan' window.
  67. Click [Return].
  68. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  69. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  70. Click [New Row] in the 'Treatment Plan' grid.
  71. Validate the 'Select T.P. Version' field defaults in with the value selected in the first row.
  72. Click [View] in the 'Select T.P. Item Note Addresses' field.
  73. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  74. Select the desired treatment plan item in the 'Treatment Plan' window.
  75. Click [Return].
  76. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  77. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  78. Enter the desired value in the 'Notes Field' field.
  79. Select "Final" in the 'Draft/Final' field.
  80. Click [File Note].
  81. Validate a "Progress Notes" message is displayed stating: Note Filed.
  82. Click [OK] and close the form.
  83. Select "Client A" and navigate to the 'Progress Notes' widget.
  84. Validate the progress notes filed in the previous steps are displayed.
  85. Validate the rows filed in the 'Treatment Plan' grid are displayed.
Scenario 3: Diagnosis - Diagnosis Entry
Specific Setup:
  • Client must be enrolled in an active episode and have a diagnosis on file (Client A).
Steps
  1. Select "Client A" and access the ‘Diagnosis’ form.
  2. Select the diagnosis row to edit.
  3. Click [Edit].
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Populate all required and desired fields.
  7. Click [Submit] and [No].
  8. Select "Client A" and access the 'Diagnosis' form.
  9. Select the diagnosis row edited in the previous steps.
  10. Click [Edit].
  11. Validate the newly entered row is displayed as expected.
  12. Close the form.
Scenario 4: 'Staff Members Hours and Exceptions' - Verification of 'Staff Member Hours' Information Entry/Filing
Specific Setup:
  • A staff member must be defined in 'Practitioner Enrollment' (Staff Member A).
Steps
  1. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  2. Click [Staff Member Hours].
  3. Validate the 'Staff Member Hours' grid is displayed.
  4. Click [New Row].
  5. Enter the desired date in the 'Effective Date' field.
  6. Select the desired day in the 'Day' field.
  7. Select the desired site in the 'Site' field.
  8. Enter the desired times in the 'Start Time' and 'End Time' fields.
  9. Populate any other desired values.
  10. Click [Save], [Yes], and [Submit].
  11. Access the 'Staff Members Hours and Exceptions' form for "Staff Member A".
  12. Click [Staff Member Hours].
  13. Validate the 'Staff Member Hours' grid is displayed.
  14. Validate the hours entered in the previous steps are displayed as expected.
  15. Close the form.
Scenario 5: Problem List - Add / Edit / Void a problem
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Must have an "Active" and "Void" dictionary value defined for the 'Status (16214)' dictionary. The 'Active Status' extended dictionary data element defined for these values.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Select the desired problem in the 'Problem' field.
  4. Select "Active" in the 'Status' field.
  5. Populate all other desired fields.
  6. Click [Save], [Yes], and [Submit].
  7. Select "Client A" and access the 'Problem List' form.
  8. Click [View/Enter Problems].
  9. Validate the problem filed in the previous steps is displayed.
  10. Select "Void" in the 'Status' field.
  11. Click [Save], [Yes], and [Submit].
  12. Select "Client A" and access the 'Problem List' form.
  13. Click [View/Enter Problems].
  14. Validate the problem is no longer displayed since it has been voided.
  15. Close the form.
Topics
• Progress Notes • Diagnosis • Practitioner • Problem List
Update 26 Summary | Details
State Form Tools - State Form Button Mapping
Scenario 1: Modeled Form - Validate the use of "State Form Button" mapping functionality
Specific Setup:
  • Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as a "Name" type field [Patient Name] and "Date" type field [Date of Birth], on the form
  • Have a state form definition file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
  • In form "State Form Button Mapping", have the following prompts populated with the form submitted
  • [PopButtonA] selected in the "Button Field"
  • [StateFormDefA] selected in the "State Form Definition" field
  • "Patient Name" selected in the "Parameter Field 1" field
  • "Date of Birth" selected in the "Parameter Field 2" field
  • Have "Netsmart" configure the [PopulateA] button on [FormA] using "Programmer Override" logic in order execute the [StateFormDefA] file so that it populates [FieldA] and [FieldB] on modeled form, when a user clicks the [PopulateA] button
Steps
  1. Open [FormA]
  2. Select the desired client [ClientA]
  3. Click the [PopulateA] button, set up on the form
  4. Validate the [Patient Name] field contains the expected name for [ClientA]
  5. Validate the [Date of Birth] field contains the date of birth for [ClientA]
  6. Click [Submit]
  7. Validate the form files successfully
  8. Return to [FormA]
  9. Select [ClientA]
  10. Validate the [Patient Name] field contains the expected name for [ClientA]
  11. Validate the [Date of Birth] field contains the date of birth for [ClientA]
State Form Definition Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: 'State Form Definition' form - "Define Record Data Elements" grid validations
Specific Setup:
  • Have a state form definition file created in form "State Form Definition", [DefinitionA]. For this example, a definition that selects the "PATID" and "Patient Name" for all clients on the system from the SYSTEM.patient_current_demographics table is used
  • Have two test clients:
  • [ClientA] with a PATID of "1"
  • [ClientB] with a "PATID" of "2" and also has a "Date of Birth" filed in their client record
Steps
  1. Open form "State Form Definition"
  2. Select [DefinitionA]
  3. Navigate to the "Record Definition" tab
  4. Select the existing record in the "Select Record" field
  5. Click the "Define Record Data Elements" to open the data elements grid
  6. In the grid, select the row containing "PATID",
  7. Navigate to the "Force Error Condition" column
  8. Enter "p.PATID = 1" in the input field
  9. Validate the value is accepted
  10. Navigate to 'Default Error Message' column
  11. Enter a default text message that includes the clients name in the message but formatted to use the "NAME1" format variable, to just display only the clients last name. For example enter, "Client {p.patient_name:NAME1} is not valid"
  12. Validate the value is accepted
  13. Save the grid
  14. File the record and file the form
  15. Open form "State Form File Generation"
  16. Select [DefinitionA]
  17. Select "Compile" in the "File Generation Options" field
  18. Click [Process]
  19. Validate a message is displayed indicating the compile is complete but it contains errors
  20. Click [OK]
  21. Click the [Process] button to run the error report
  22. Validate the warning message is present and contains the last name PATID "1" as expected. For example, "Client SMITH is not valid"
  23. Close the report and close the form
  24. Open form "State Form Definition"
  25. Select [DefinitionA]
  26. Navigate to the "Record Definition" tab
  27. Select the existing record in the "Select Record" field
  28. Click "Define Record Data Elements" to open the data elements grid
  29. In the grid, select the row containing "PATID",
  30. Navigate to the "Force Error Condition" column
  31. Enter "p.PATID = "2" in the input field
  32. Validate the value is accepted
  33. Navigate to 'Default Error Message' column
  34. Enter a default text message to include the display of the clients date of birth using the "D3" date format variable, which will display the date in the "YYYY-MM-DD" format. For example enter, "Client {p.patient_name:NAME1} is not valid. DOB {p.date_of_birth:D3}"
  35. Validate the value is accepted
  36. Save the grid
  37. File the record and file the form
  38. Open form "State Form File Generation"
  39. Select [DefinitionA]
  40. Select "Compile" in the "File Generation Options" field
  41. Click [Process]
  42. Validate a message is displayed indicating the compile is complete but it contains errors
  43. Click [OK]
  44. Click the [Process] button to run the error report
  45. Validate a warning message is displayed containing the last name and the date of birth for PATID "2" as expected, for example: "Client SMITH is not valid. DOB 1996-07-25"
Topics
• NX • State Form Tools
Update 27 Summary | Details
User Role Definition - Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • Document Management Definition
  • User Role File Import
  • User Role File Export
Scenario 1: 'User Role File Import' - Import Validations
Specific Setup:
  • Create a new form type [FormX] in form "Document Management Definition". Note the form type ID number, for this example "27" is used
Steps
  1. Open the 'User Role Definition' form.
  2. In the User Role ID field
  3. Enter a name for a new role [RoleX]
  4. Click to the
  5. Click the "Document Management" Section
  6. Select "No" in the 'Is this user a Document Management Administrator?' field.
  7. Select "Specify Forms" in the 'Forms Allowed To View' field
  8. Select the document created in the set up [FormX]
  9. Click back to the "User Role Definition" section
  10. Populate all the required fields and any other desired fields
  11. Submit the form
  12. Validate the form files successfully
  13. Open form "User Role File Export"
  14. Click "Select Roles to Export"
  15. Select [RoleX]
  16. Click [Begin Export]
  17. Save the export file [ExportX] in a folder
  18. Close the form
  19. Open form "Document Management Definition"
  20. Click [Select Form]
  21. Select [FormX]
  22. Click [Delete]
  23. Click [Yes] to confirm the deletion
  24. Exit the form
  25. Open the 'User Role Definition' form.
  26. Select [RoleX]
  27. Click the "Document Management" Section
  28. Click "Specify Forms" in the 'Forms Allowed To View' field
  29. Validate [FormX] is no longer present in the list
  30. Click [Cancel]
  31. Exit the form
  32. Open form "User Role File Import"
  33. Click [Select Import File]
  34. Navigate to the location of [ExportX] saved in step 2
  35. Select the file
  36. Click [Begin Import]
  37. Validate the following warnings are present in the import scan results
  38. "WARNING: Role [RoleX] contains access to view documents of form type '27' that does not exist. Document form type '27' will be skipped.
  39. WARNING: Role [RoleX] has existing data that will be overwritten.
  40. Open the 'User Role Definition' form.
  41. Select [RoleX]
  42. Click the "Document Management" Section
  43. Click "Specify Forms" in the 'Forms Allowed To View' field
  44. Validate the forms list does not include [FormX], as expected
  45. Select [Clear All]
  46. Submit the form
  47. Validate the form files successfully
Scenario 2: User Role Definition - Validate 'Copy User Roles to Other System Codes' functionality
Specific Setup:
  • Have a system defined with two root system codes. [SYSA] and [SYSB]
  • Both system codes contain the same "Forms" and associated form "ID's" defined in form "Document Management Definition"
  • In [SYSA], create a new form type [FormZ] in form "Document Management Definition". Note the form type ID number, for this example "28" is used
  • In [SYSA], have or create a new user role [RoleZ]
  • Have the 'Registry Settings' form, set the 'Copy User Roles to Other System Codes' registry setting to "Y".
  • Log into root code [SYSA]
Steps
  1. Open the 'User Role Definition' form.
  2. Click [Select User Role]
  3. Select [RoleZ]
  4. In the 'Select Codes To Copy User Role To' field, select [SYSB]
  5. Populate any other required fields in that section
  6. Click the "Document Management" Section
  7. Select "No" in the 'Is this user a Document Management Administrator?' field.
  8. Select "Specify Forms" in the 'Forms Allowed To View' field
  9. Select the document created in the set up, [FormZ]
  10. Submit the form
  11. Validate an error is displayed "The following document form types to view do not exist in all selected system codes within 'System Codes To Copy User Role To' and will be unchecked. Document form type '28' does not exist in system code [SYSB]
  12. Click [OK]
  13. At the "Submission will be aborted" error message, Click [OK]
  14. Log out of root code [SYSA]
  15. Log into root code [SYSB]
  16. Open form "Document Management Definition"
  17. Click [Select Form]
  18. Click [Add New]
  19. Validate the "Form ID" field has been assigned the same form ID number assigned to [FormZ] in the set up, form ID "28"
  20. Populate the "Form Name" field
  21. Populate any other required fields
  22. Submit the form
  23. Log out of root code [SYSB]
  24. Log into root code [SYSA]
  25. Open the 'User Role Definition' form.
  26. Click [Select User Role]
  27. Select user role, [RoleZ]
  28. In the 'Select Codes To Copy User Role To' field, select [SYSB]
  29. Populate any other required fields in that section
  30. Click the "Document Management" Section
  31. Select "No" in the 'Is this user a Document Management Administrator?' field.
  32. Select "Specify Forms" in the 'Forms Allowed To View' field
  33. Select the document created in the set up, [FormZ]
  34. Submit the form
  35. Validate the form files successfully
  36. Return to the form
  37. Select [RoleZ]
  38. Click the "Document Management" Section
  39. Click "Specify Forms" in the 'Forms Allowed To View' field
  40. Click [Select Forms to View]
  41. Validate [FormZ] is selected, as expected
  42. Log out of root code [SYSA]
  43. Log into root code [SYSB]
  44. Open the 'User Role Definition' form.
  45. Click [Select User Role]
  46. Validate the "Select User Role" field contains [RoleZ]
  47. Select [RoleZ]
  48. Click the "Document Management" Section
  49. Select "Specify Forms" in the 'Forms Allowed To View' field
  50. Click [Select Forms to View]
  51. Validate [FormZ] is present and selected in the forms list, as expected
  52. Close the form
Topics
• NX • User Role Definition
Update 41 Summary | Details
'Console Widget Configuration' enhanced to allow 'Preferred Forms' selection to display in the 'Console Widget'.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Configuration (PM)
Scenario 1: Console Widget Configuration - Setup and sort order for Preferred Forms in the Multiple Form Widget
Specific Setup:
  • A client must exist that has previously used at least one form available in the 'Forms to Display' section of the 'Console Widget Configuration' form. (Client A)
Steps
  1. Access the 'Console Widget Configuration' form.
  2. Select the 'Multiple Form Widget' section and click [Select Widget].
  3. Select "Add New Widget" in the 'Select Widgets' dialog and click [OK].
  4. Set the 'Widget ID' field to "Test1" and the 'Title' field to "Test Widget 1".
  5. Select an assortment of Forms and click [File].
  6. Close the 'Console Widget Configuration' form.
  7. Access the 'View Definition' form.
  8. Click [Select View], select the current view for the logged in user, and click [OK].
  9. Click [Launch View Designer].
  10. Search for and select "Test Widget 1" from the 'Filter by widget title or category' field.
  11. Click the [Right Arrow] to add "Test Widget 1" to the 'Assigned Widgets' section.
  12. Drag and drop "Test Widget 1" onto the View.
  13. Click [Submit] to verify the changes made to the View.
  14. Click [Submit] and close the form.
  15. Validate "TEST WIDGET 1" has been added to the View.
  16. Select "Client A" and validate any forms that were previously utilized for the client are displayed in a table.
  17. Click [New Record] and validate the Forms selected in 'Console Widget Configuration' are displayed in an alphabetized list.
  18. Select one of the Forms.
  19. Validate the selected Form is launched and close the Form.
  20. Access the 'Console Widget Configuration' form.
  21. Select the 'Multiple Form Widget' section and click [Select Widget].
  22. Select "Test Widget 1 (TEST1)" in the 'Select Widgets' dialog and click [OK].
  23. Validate the 'Widget ID' field contains "TEST1" and the 'Title' field contains "Test Widget 1".
  24. Validate the 'Forms to Display' section contains the previous selection of Forms.
  25. Validate any Forms selected in the 'Forms to Display' section are displayed under 'Preferred Forms'.
  26. Select several of the forms from the 'Forms to Display' section and click [File].
  27. Close the 'Console Widget Configuration' form.
  28. Click [New Record] on "TEST WIDGET 1".
  29. Validate the Forms selected in the 'Preferred Forms' section of 'Console Widget Configuration' are displayed at the top of the list, bolded, and in alphabetical order.
  30. Validate the other Forms that were not selected are listed after the 'Preferred Forms' and in alphabetical order.
  31. Select one of the 'Preferred Forms'.
  32. Validate the selected Form is launched and close the Form.
  33. Access the 'Console Widget Configuration' form.
  34. Select the 'Multiple Form Widget' section and click [Select Widget].
  35. Select "Test Widget 1 (TEST1)" in the 'Select Widgets' dialog and click [OK].
  36. Validate the 'Preferred Forms' section contains the previous selection of Forms.
  37. Deselect all Forms from the 'Preferred Forms' section and click [File].
  38. Close the 'Console Widget Configuration' form.
  39. Click [New Record] on "TEST WIDGET 1".
  40. Validate the Forms that were deselected from the 'Preferred Forms' section in 'Console Widget Configuration' have been unbolded and deprioritized.
Topics
• Console Widget • Console Widget Configuration • NX
Update 50 Summary | Details
Report Definition - Avatar NX
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition (PM)
Scenario 1: Report Definition (Avatar NX) - Create and launch a report requiring an External ODBC Connection
Specific Setup:
  • An external database server [ServerA] exists, that that contains table data [TableA]. For example, an external "SQL" server
  • Using form "NX External ODBC Data Sources", have an "ODBC Data Source" created [DataSourceA] configured to use an ODBC driver to connect to the external database server [ServerA]
  • Have a Crystal Report [ReportA] created, that connects to the external database [ServerA] using [DataSourceA] in order to display data in [TableA].
Steps
  1. Open form "Report Definition"
  2. Click [New Avatar Report]
  3. Populate the "Report Name" field with a name for the report [ReportDefA]
  4. Click [Select Report]
  5. In the "Windows Explorer" window, navigate to the directory that contains [ReportA]
  6. Click [Save]
  7. Click to the "Report Parameters" section
  8. Click [Add New Item] in the "Report Parameters" grid to add any desired parameters. For example "PATID" and "Episode"
  9. Click the [Additional ODBC Connections] section
  10. Click [Add New Item]
  11. Click the "Connection Type" field
  12. Select "myAvatar NX"
  13. Click the "myAvatar NX Connection" field
  14. Select the [DataSourceA] connection created in the set up
  15. Click [Submit]
  16. Validate the form files successfully
  17. Return to the form
  18. Select [ReportA]
  19. Click each section populated in steps 1 thru 3
  20. Validate all fields are populated as expected
  21. Close the form
  22. Search form [ReportDefA]
  23. Populate any parameters required to run the report
  24. Click [Process]
  25. Validate the report results, are as expected
Topics
• Query/Reporting • NX
Update 64 Summary | Details
Form Designer - Import/Export
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
  • Form Designer (PM)
Scenario 1: Form Designer - Export/Import Layout Changes
Specific Setup:
  • Have a robust form containing several sections and several fields on each section (Form A).
  • Edit any section (Section A) of "Form A" and make any type of form designer change in the section. For this example, a field is moved to different location (Field A).
Steps
  1. Access "Form A".
  2. Navigate to "Section A".
  3. Validate the form designer change made in the setup is present and "Field A" is in a new location.
  4. Access the 'Form Designer' form.
  5. Select "Form A" from the 'Forms' field.
  6. Click [Export Form Designer Copy].
  7. Validate a 'Confirm' dialog stating "Export Complete." and click [OK] (Note: Export files are saved in the "Downloads" folder)
  8. Close the form.
  9. Access the 'Form Designer' form.
  10. Select "Form A" from the 'Forms' field.
  11. Select "Section A" in the "Sections" field.
  12. Click [Show Section].
  13. Revert the form designer change confirmed in step 1b so "Field A" is returned to its original location.
  14. Click [Save], [OK] and [Submit].
  15. Access "Form A".
  16. Navigate to "Section A".
  17. Validate the form designer change made in step 3d is present.
  18. Close the form.
  19. Access the 'Form Designer' form.
  20. Select "Form A" from the 'Forms' field.
  21. Click [Import Form Designer Copy]
  22. Navigate to the location of the export file.
  23. Select the file.
  24. Click [Submit].
  25. Access "Form A".
  26. Navigate to "Section A".
  27. Validate the form designer change made in the setup is present and "Field A" is in a new location.
  28. Close the form.
Scenario 2: Form Designer - Validate the ability to import a form after a section has been deleted in 'Form Definition'
Specific Setup:
  • User must create a new table in the 'Table Definition' form with at least three columns.
  • User must create a new form in the 'Form Definition' form with at least three sections defined in 'Section Definition' that correspond with the table columns created (Form A).
Steps
  1. Access the 'Form Designer' form.
  2. Select "Form A" in the 'Forms' field.
  3. Select the first section in the 'Sections' field.
  4. Click [Show Section].
  5. Enter any value in the 'Subsection' field.
  6. Click [Save], [Yes] and [OK].
  7. Repeat step 1b-1e for the remaining sections.
  8. Click [Submit].
  9. Access the 'Form Definition' form.
  10. Select "Form A" in the 'Select Avatar PM Form' field.
  11. Select the 'Section Definition' field.
  12. Select the first section and click [Delete Selected Item].
  13. Validate a dialog stating: "Are you sure?"
  14. Click [Yes] and [Submit].
  15. Access the 'Form Designer' form.
  16. Select "Form A" in the 'Forms' field.
  17. Click [Export Form Designer Copy].
  18. Validate a 'Confirm' dialog stating "Export Complete." and click [OK].
  19. Click [Import Form Designer Copy].
  20. Validate a 'File Upload' dialog and select the newly exported file.
  21. Click [Open] and [Submit].
  22. Validate there is no error message and the form closes.
  23. Refresh the forms.
  24. Select any client and access "Form A".
  25. Validate the form displays the expected sections.
  26. Close the form.
'All Documents' widget - 'Workflow Status'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • HomeView - Primary All Documents Widget
  • Treatment Plan
  • Clinical Document Viewer
Scenario 1: Validate Console Widgets for 'Ambulatory Progress Notes'
Specific Setup:
  • Using the "Site Specific Section Modeling" form, add a SS Note Single Response Dictionary field to the "Ambulatory Progress Notes" form.
  • A Console Widget must be configured for the 'Ambulatory Progress Notes' form. This can be done in the 'Console Widget Configuration' form. Include the site specific section modeling field in the configuration.
  • The Console Widget for 'Ambulatory Progress Notes' must be on the home view.
  • A client must be enrolled in an outpatient episode and have a New Service and Existing Service filed in the 'Ambulatory Progress Notes' form (Client A) and the SS Note Single Response Dictionary type field must be populated.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' Console Widget.
  2. Validate there are rows for the New Service and Existing Service notes that have been previously filed for "Client A".
  3. Validate the site specific section modeling field value is included in the widget data.
  4. Validate all the service fields are displayed.
Scenario 2: Progress Notes (Group and Individual) display in Chart View
Specific Setup:
  • "Progress Notes (Group and Individual)" form includes "Draft/Final".
  • "Progress Notes (Group and Individual)" form is setup to allow Document Routing with "Allow Notifications when Final" field set to "Y".
Steps
  1. Create a note in the "Progress Notes (Group and Individual)" form for any test client (Client A).
  2. Complete all required fields.
  3. Select "Final" in the "Draft/Final" field.
  4. When the Document Routing screen displays, click [Accept and Route] to send this note to any user for approval and to be finalized.
  5. Remain in the "Progress Notes (Group and Individual)" form.
  6. Create another note for Client A and select "Final" in the "Draft/Final" field.
  7. When the Document Routing screen displays, click [Accept] to Finalize the note without sending to a user.
  8. Exit the "Progress Notes (Group and Individual)" form.
  9. Right click on Client A in the "My Clients" widget.
  10. Click on "Progress Notes" in the "Documents" section
  11. Verify the "Document Status" field for both notes is set to "Final".
Scenario 3: Console Widget - Progress Notes Finalized Status
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Submit Note].
  5. Click [Sign].
  6. Enter the password for the logged in user and click [Verify].
  7. Validate a 'Progress Notes' dialog stating: "Note Filed."
  8. Click [OK].
  9. Close the form.
  10. Navigate to the 'All Documents' view.
  11. Refresh the 'All Documents' widget.
  12. Select the 'All Forms' field.
  13. Validate the Progress Note is displayed and select it.
  14. Validate the 'Console Widget Viewer' displays the note.
Scenario 4: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Scenario 5: Console Widget Viewer - Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for the Treatment Plan in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add any problem.
  7. Click [Return To Plan] and [OK].
  8. Submit the form.
  9. Select "Client A" and navigate to "View A".
  10. Validate the 'Treatment Plan' console widget contains the draft treatment plan filed in the previous steps and select it.
  11. Click [View].
  12. Validate the 'Console Widget Viewer' displays the draft treatment plan details filed in the previous steps.
  13. Click [Open Record].
  14. Validate the draft treatment plan is opened.
  15. Select "Final" in the 'Treatment Plan Status' field.
  16. Submit the note.
  17. Select "Client A" and navigate back to "View A".
  18. Validate the 'Treatment Plan' console widget contains the finalized treatment plan filed in the previous steps and select it.
  19. Click [View].
  20. Validate the 'Console Widget Viewer' displays the finalized treatment plan details filed in the previous steps.
  21. Click [Open Record].
  22. Validate a message is displayed stating "This plan is marked as Final. Changes are not allowed. Do you want to continue?"
  23. Click [No].
Scenario 6: Clinical Document Viewer - "Void" documents
Specific Setup:
  • Perceptive is enabled.
  • User has permissions to void documents.
  • A client must have non-routed documents on file in the 'Clinical Document Viewer' (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Select "Client A" in the 'Select Client' field.
  4. Click [Process].
  5. Select any non-routed document and view it.
  6. Click [Void] and [Void] again.
  7. Select the desired value in the 'Void Reason' field.
  8. Enter the desired value in the 'Void Comments' field.
  9. Click [Void] and [Close All Documents].
  10. Select the "Search" section.
  11. Click [Close].
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void".
  14. Select the document.
  15. Validate the document displays with "Voided" in the 'Console Widget Viewer'.
Scenario 7: Validate modeled forms that do not allow edits cannot be edited in the 'All Documents' widget
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A user must have a modeled form (Form A) configured for the 'All Documents Widget'.
  • "Form A" must have "No Re-Entry" selected in the 'Re-Enter Form?' field and "No" selected for the 'Remove Form Pre Display', 'Allow Deletion of Row From Table', and 'Allow Edit of Table Rows' fields in 'Form Definition'.
  • User must have the 'All Documents' widget and the 'Console Widget Viewer' configured to a view ('All Documents' view).
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access "Form A".
  2. Fill out all required and desired fields.
  3. Click [Submit].
  4. Navigate to the 'All Documents' view.
  5. Select the 'All Forms' field.
  6. Select "Form A" from the 'Form Description' field.
  7. Validate the record displays and select it.
  8. Validate the 'Open' button is disabled in the 'All Documents' widget.
  9. Validate the record opens in the 'Console Widget Viewer' and that the 'Open Record' button is disabled.
Scenario 8: Treatment Plan - 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • 'Treatment Plan' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 9: Treatment Plan Copy- 'Pending Approval' workflow
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The Wiley Libraries must be installed.
  • A staff member must be associated to the logged in user. (Staff Member A)
  • "Staff Member A" must be set up in the 'Notification Users' form.
  • A copy must exist of the 'Treatment Plan' form (Treatment Plan Copy).
  • 'Treatment Plan Copy' and "Staff Member A" must be set up in 'Required User List Management' form.
  • The 'My To Do's' widget must be set up on a user's view.
Steps
  1. Select "Client A" and access the 'Treatment Plan Copy' form.
  2. Select the desired episode if present.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select the desired value for the 'Plan Type' field.
  5. Populate any required and desired fields.
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Click [Launch Plan].
  8. Select the desired problem and drag it into the Treatment Plan.
  9. Populate all desired fields.
  10. Select a desired goal and drag it into the Treatment Plan.
  11. Populate all desired fields.
  12. Select a desired objective and drag it into the Treatment Plan.
  13. Populate all desired fields.
  14. Click [Return to Plan].
  15. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  16. Click [OK].
  17. Select "Pending Approval" in the 'Treatment Plan Status' field.
  18. Select "Staff Member A" in the 'Team Member To Notify' field.
  19. Click [Submit].
  20. Navigate to the 'My To Do's' widget.
  21. Click [Approve To Do Item] for "Client A".
  22. Select "Yes" in the 'Approve To Do Item' field.
  23. Enter the desired value in the 'Comments' field.
  24. Click [Submit].
  25. Click [Review To Do Item] for "Client A".
  26. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  27. Click [Submit].
  28. Validate the item is no longer present for "Client A".
Scenario 10: 'All Documents' widget - Validate 'Treatment Plan' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate any required and desired fields.
  5. Select "Draft" in the 'Treatment Plan Status' field.
  6. Click [Launch Plan].
  7. Add any problem.
  8. Populate all desired fields.
  9. Click [Return To Plan].
  10. Validate a 'Plan Save' dialog stating: "Plan saved successfully."
  11. Click [OK].
  12. Submit the form.
  13. Navigate to the 'All Documents' view.
  14. Refresh the 'All Documents' widget.
  15. Select 'All Forms'.
  16. Select "Treatment Plan" in the 'Form Description' field.
  17. Verify the record is present and displays "Draft" in the 'Workflow Status' field and select it.
  18. Validate the 'Console Widget Viewer' displays the plan in the previous steps.
  19. Click [Open Record].
  20. Validate the 'Treatment Plan' form opens with the draft from the previous steps.
  21. Make and desired changes.
  22. Select "Final" in the 'Treatment Plan Status' field.
  23. Click [Submit]
  24. Validate a 'Confirm Document' dialog containing the treatment plan.
  25. Click [Sign].
  26. Enter the password associated with the logged in user and click [Verify].
  27. Navigate to the 'All Documents' view.
  28. Refresh the 'All Documents' widget.
  29. Select 'All Forms'.
  30. Select "Treatment Plan" in the 'Form Description' field.
  31. Verify the record is present and displays "Final" in the 'Workflow Status' field and select it.
  32. Validate the 'Console Widget Viewer' displays the finalized plan from the previous steps.
Topics
• Form Designer • NX • Progress Notes • Widgets • Clinical Document Viewer • Treatment Plan • myAvatar NX Only
Update 66 Summary | Details
'All Documents' widget - User Access Levels
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Console Widget Viewer
  • Clinical Document Viewer
Scenario 1: All Documents Widget - Validate user access levels
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • There must be three users:
  • A user who has full access to forms and is logged in (User A)
  • A user who has read-only access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User B).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User C).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value in the 'Progress Note For' field.
  3. Populate all required and desired fields.
  4. Select "Final" in the 'Draft/Final' field.
  5. Click [Submit Note].
  6. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  7. Enter the password associated with the logged in user and click [Verify].
  8. Close the form.
  9. Navigate to the 'All Documents' view.
  10. Select 'All Forms'.
  11. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  12. Validate the progress note from the previous steps is present and select it.
  13. Validate the note displays in the 'Console Widget Viewer'.
  14. Validate the 'Open' and 'Open Record' buttons are enabled.
  15. Access the 'Treatment Plan' form.
  16. Enter the desired date in the 'Plan Date' field.
  17. Populate all required and desired fields.
  18. Select "Draft" in the 'Treatment Plan Status' field.
  19. Click [Launch Plan].
  20. Populate all required and desired fields.
  21. Click [Return to Plan] and [OK].
  22. Select "Final" in the 'Treatment Plan Status' field.
  23. Click [Submit].
  24. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign].
  25. Enter the password associated with the logged in user and click [Verify].
  26. Navigate to the 'All Documents' view.
  27. Select 'All Forms'.
  28. Select "Treatment Plan" in the 'Form Description' field.
  29. Validate the treatment plan from the previous steps is present and select it.
  30. Validate the plan displays in the 'Console Widget Viewer'.
  31. Validate the 'Open' and 'Open Record' buttons are enabled.
  32. Log out.
  33. Login as "User B".
  34. Select "Client A" and navigate to the 'All Documents' view.
  35. Select 'All Forms'.
  36. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  37. Validate the progress note from the previous steps is present and select it.
  38. Validate the note displays in the 'Console Widget Viewer'.
  39. Validate the 'Open' and 'Open Record' buttons are disabled.
  40. Select "Treatment Plan" in the 'Form Description' field.
  41. Validate the treatment plan from the previous steps is present and select it.
  42. Validate the plan displays in the 'Console Widget Viewer'.
  43. Validate the 'Open' and 'Open Record' buttons are disabled.
  44. Log out.
  45. Login as "User C".
  46. Select "Client A" and navigate to the 'All Documents' view.
  47. Validate "Progress Notes (Group and Individual)" and "Treatment Plan" and not present in the 'Form Description' field.
Scenario 2: Clinical Document Viewer - Validate user access levels
Specific Setup:
  • A client has finalized documents for 'Progress Notes (Group and Individual)' (Client A).
  • There must be two users:
  • A user who has full access to forms and is logged in (User A).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' form (User B).
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Enter "Client A" in the 'Select Client' field.
  4. Select "All" in the 'Episode' field.
  5. Click [Process].
  6. Select the desired document in the 'Search Results' field.
  7. Click to view the document.
  8. Validate document data is displayed.
  9. Click [Close All Documents].
  10. Navigate back to the "Search" section.
  11. Click [Close].
  12. Log out.
  13. Log in as "User B".
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Individual" in the 'Select All or Individual Client' field.
  16. Enter "Client A" in the 'Select Client' field.
  17. Select "All" in the 'Episode' field.
  18. Click [Process].
  19. Validate the desired document has a lock next to it in the 'Search Results' field.
  20. Validate the user is unable to select and view the document.
  21. Navigate back to the "Search" section.
  22. Click [Close].
'All Documents' widget - The 'Limit Console Widget Viewer To Text Only' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Console Widget Viewer
Scenario 1: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
  • The 'Limit Console Widget Viewer To Text Only' registry setting must be enabled.
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps as text.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps as text.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Scenario 2: 'All Documents' widget - Validate the 'Limit Console Widget Viewer To Text Only' registry setting
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' form.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Limit Console Widget Viewer to Text" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Enter "N" in the Registry Setting Value' field.
  5. Click [Submit].
  6. Validate a 'Registry Editor Filing' dialog and click [OK] and [No].
  7. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  8. Select any value in the 'Progress Note For' field.
  9. Populate all required and desired fields.
  10. Select "Draft" in the 'Draft/Final' field.
  11. Click [Submit Note].
  12. Navigate to the 'All Documents' view.
  13. Select 'All Forms'.
  14. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  15. Select the draft from the previous steps.
  16. Validate the draft note displays as text in the 'Console Widget Viewer'.
  17. Navigate back to the 'Progress Notes (Group and Individual)' form.
  18. Enter "Client A" in the 'Select Client' field.
  19. Select any value in the 'Progress Note For' field.
  20. Populate all required and desired fields.
  21. Select "Final" in the 'Draft/Final' field.
  22. Click [Submit Note].
  23. Validate a 'Confirm Document' dialog containing the data and click [Sign].
  24. Enter the password associated with the logged in user and click [Verify].
  25. Validate a 'Progress Notes' dialog stating: "Note Filed".
  26. Click [OK] and close the form.
  27. Navigate to the 'All Documents' view.
  28. Refresh the 'All Documents' widget.
  29. Select 'All Forms'.
  30. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  31. Select the finalized note from the previous steps.
  32. Validate the 'Console Widget Viewer' displays the TIFF image for the finalized note.
  33. Click [Close All].
  34. Access the 'Registry Settings' form.
  35. Enter "Limit Console Widget Viewer to Text" in the 'Limit Registry Settings to the Following Search Criteria' field.
  36. Click [View Registry Settings].
  37. Enter "Y" in the Registry Setting Value' field.
  38. Click [Submit].
  39. Validate a 'Registry Editor Filing' dialog and click [OK] and [No].
  40. Navigate to the 'All Documents' view.
  41. Refresh the 'All Documents' widget.
  42. Select 'All Forms'.
  43. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  44. Select the draft from the previous steps.
  45. Validate the draft note displays as text in the 'Console Widget Viewer'.
  46. Select the finalized note from the previous steps.
  47. Validate the finalized note displays as text in the 'Console Widget Viewer'.
  48. Click [Close All].
Scenario 3: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps.
  11. Click [Open Record].
  12. Validate the draft note is opened.
  13. Select "Final" in the 'Draft/Final' field.
  14. Submit the note.
  15. Select "Client A" and navigate back to "View A".
  16. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  17. Click [View].
  18. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps.
  19. Click [Open Record].
  20. Validate a message is displayed stating "This note is already set to 'Final'."
  21. Click [OK] and validate the finalized note is not displayed.
Topics
• Treatment Plan • Progress Notes • Widgets • NX • Clinical Document Viewer • Progress Notes (Group And Individual) • Console Widget • myAvatar NX Only