Skip to main content

RADplus 2023 Monthly Release 2023.00.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
Avatar PM 2023 is Installed
Scenario 1: Validate Upgrading RADplus 2022 to 2023 is successful when 2022.04.00 is loaded
Specific Setup:
  • Latest Monthly Release is installed.
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
Update 2 Summary | Details
Append Document
Scenario 1: Append Documents - Validate user permissions to append documents
Specific Setup:
  • Have a system with a [Root] system code and sub system code defined [TestSub]
  • Sub system code [TestSub] has been assigned a specific program [ProgramA]
  • [TestClient] is admitted in two episodes:
  • [Episode1] to [ProgramA]
  • [Episode2] to [ProgramB]
  • [UserA] has access to both the [Root] system code and sub system code [TestSub]
  • [UserB] has access only to the sub system code [TestSub]
  • [FormA] has been submitted for [TestClient] in [Episode1] and a document has been generated [DocA]
  • [FormB] has been submitted for [TestClient] in [Episode2] and a document has been generated [DocB]
  • Log in as [UserB] into the [TestSub] sub system code
Steps
  1. Open form "Append Documents"
  2. Select the applicable form type in the "Form Type" field
  3. Select [TestClient] in the "Entity" field
  4. Enter the applicable date range in the "From Date" and "To Date" fields
  5. Click the "List of Documents" field
  6. Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
  7. Validate the drop down list does not display [Doc2] filed for [FormB] in [Episode2, ProgramB], as expected
  8. Select the row for [Doc1]
  9. Add any desired comments in the "New Comments to be Appended to Original Document" field
  10. Submit the form
  11. Validate the 'Confirm Document' dialog displays the appended comments
  12. Validate the document contains the appended signature of the logged in user [UserB] at the end of the document.
  13. Click [Accept].
  14. Validate the form files successfully.
  15. Log out as [UserB]
  16. Log in as [UserA] into the sub system code [SubCode]
  17. Repeat step1
  18. Validate the results are the same, as the sub code is restricted to only [ProgramA]
  19. Log out as [UserA]
  20. Log in as [UserA] into the [Root] system code
  21. Repeat step 1
  22. Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
  23. Validate the drop down list also displays [Doc2] filed for [FormB] in [Episode2, ProgramB], as [UserA] has access to both the root and sub system code.
My To Do's Widget - Sign Tab
Scenario 1: 'My To Do's Widget - Validate user permissions to access documents
Specific Setup:
  • Have a system with a root and a sub system code
  • The sub system is code is assigned to only [ProgramA]
  • [UserA] is a staff member that can cosign for other staff members and has access to log into both the root and the sub code
  • [UserB] is a staff member and cannot cosign for other staff members and has access to log both the root and the sub code
  • [TestClient] has been admitted in two episodes:
  • "Episode1" in [ProgramA]
  • "Episode2" in [ProgramB]
  • Two documents have been routed for [TestForm] for [TestClient]
  • [DocA] - was routed to [UserA] for an [Epsiode1]
  • [DocB] - was routed to [UserB] for [Episode2]
  • [UserA] and [UserB] have the "My To Do's" widget on their home view
Steps
  1. Log in to the sub code as [UserA]
  2. Navigate to the "My To Do's" widget
  3. Click the [Sign] tab
  4. Search for [UserA] in the "Staff" search field
  5. Validate [DocA] is found
  6. Search for [UserB] in the Staff field
  7. Validate [DocB] is not found, as [DocB] was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
  8. Log out as [UserA] from sub code
  9. Log in as [UserA] to the root system code
  10. Navigate to the "My To Do's" widget
  11. Click the [Sign] tab
  12. Search for [UserA] in the "Staff" search field
  13. Validate [DocA] is found
  14. Search for [UserB] in the "Staff" search field
  15. Validate [DocB] is found, as [UserA] can co-sign for other staff members is logged into the root system code, which has access to all programs
  16. Log out as [UserA]
  17. Log in as [UserB] into the sub code
  18. Navigate to the "My To Do's" widget
  19. Click the [Sign] tab
  20. Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
  21. Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
  22. Validate [DocB] is not listed in the "Search Documents" list, as that document was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
  23. Log out as [UserB] from sub code
  24. Log in as [UserB] to the root system code
  25. Navigate to the "My To Do's" widget
  26. Click the [Sign] tab
  27. Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
  28. Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
  29. Validate [DocB] is listed in the "Search Documents" list, as the document was routed to [UserB] and is logged into the root system code, which has access to all programs
My To Do's Widget - Sign Tab
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
Scenario 1: 'My To Do's Widget (Sign Tab) - Validate approving documents as as Co-Signer
Specific Setup:
  • [UserA] is a staff member
  • [UserB] is a staff member
  • [UserC] is a staff member that can co-sign To Do's for other staff members
  • Two documents have been routed in form [TestForm], for [TestClient]
  • [DocA] - was routed to [UserA] in [Episode1]
  • [DocB] - was routed to [UserB] in [Episode2]
  • [UserC] has the "My To Do's" widget on their home view
  • Log in as [UserC]
Steps
  1. Navigate to the "My To Do's" widget
  2. Click the [Sign] tab
  3. In the "Staff" search filed, search for [UserA]
  4. Validate the row for [DocA] is the "Search Documents" list, and select the row
  5. Validate the "Document" preview pane displays data as expected for the document
  6. Navigate to the end of the document
  7. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  8. Click [Accept], to move the document to the "Accepted Documents" section
  9. Select the document
  10. Click [Sign All]
  11. Validate the document is removed from the "Sign Tab"
  12. In the "Staff" search filed, search for [UserB]
  13. Validate the row for [DocB] is the "Search Documents" list, and select the row
  14. Validate the "Document" preview pane displays data as expected for the document
  15. Navigate to the end of the document
  16. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  17. Click [Accept], to move the document to the "Accepted Documents" section
  18. Select the document
  19. Click [Sign All]
  20. Validate the document is removed from the "Sign Tab"
  21. Open form "Clinical Document Viewer"
  22. Select [TestClient] in the "Select Client" field
  23. Click [Process]
  24. Click the [Results] tab
  25. Locate the row for the [DocA] signed in step 1b and select the "View" check box
  26. Click the [View] button
  27. Validate the "Document" preview pane displays data as expected for the document
  28. Navigate to the end of the document
  29. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  30. Click [Close All Documents]
  31. Locate the row for the [DocB] signed in step 1b and select the "View" check box
  32. Click the [View] button
  33. Validate the "Document" preview pane displays data as expected for the document
  34. Navigate to the end of the document
  35. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  36. Click [Close All Documents]
  37. Click the [Search] tab
  38. Click [Close]
Document Archiving
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Archiving
Scenario 1: Document Archiving - Form field validations
Specific Setup:
  • A "Form" type [FormtypeA], is defined in form "Document Management Definition" and includes restrictions selected in field "Document Restrictions'
  • [FormA] is set up in form "Document Routing Setup" with [FormtypeA]
  • A document [DocumentA] generated with [FormA] exists for [TestClient], that was created over "180" days ago
  • A "Form" type [FormtypeB], is defined in form "Document Management Definition" and does "not" include any restrictions selected in field "Document Restrictions'
  • [FormB] is set up in form "Document Routing Setup" with [FormtypeB]
  • A document [DocumentB] that was generated with [FormB] exists for [TestClient], that was created over "180" days ago
Steps
  1. Open form "Clinical Document Viewer"
  2. Select [TestClient]
  3. Click [Process]
  4. Validate [DocumentA] generated by [FormA], is displayed as expected date
  5. Validate [DocumentB] generated by [FormB], is displayed as expected date
  6. Close the form
  7. Open form "Document Archiving"
  8. Select "Client" the entity type in the "Entity Type" field
  9. Select "Individual" in the "Include" field
  10. Select [TestClient] in the "Entity" field
  11. Select the applicable episode in the "Episode" field
  12. In the "Archive Documents Older Than" enter the desired date greater than "180" days
  13. Click the "View Form Types Included"
  14. Validate row is displayed for [FormTypeA] for [FormA]
  15. Validate row is displayed for [FormTypeB] for [FormB]
  16. Click [Archive]
  17. At the "Are you sure you want to Archive these Documents" dialog, click [Yes]
  18. Close the form
  19. Open form "Clinical Document Viewer"
  20. Select [TestClient]
  21. Click [Process]
  22. Validate [DocumentA] generated by [FormA] is no longer displayed, as expected
  23. Validate [DocumentB] generated by [FormB] is no longer displayed, as expected
Topics
• Document Routing • NX • My To Do's • Document Management
Update 3 Summary | Details
Modeled Forms - 'Decimal' and 'Integer' fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (PM)
  • Dictionary Update (PM)
  • Modeled Client
Scenario 1: Modeled Form - 'Decimal' and 'Integer' field validations
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Have a modeled form with "Decimal" and "Integer" field types (Form A).
  • "Form A" must be accessible from the Chart View.
Steps
  1. Select "Client A" and access "Form A".
  2. Enter a negative decimal value in the 'Decimal' field (Ex: -1.24).
  3. Validate the value is accepted.
  4. Enter a negative integer value in the 'Integer' field (Ex: -1212).
  5. Validate the value is accepted.
  6. Click [Submit].
  7. Double click on "Client A" in the 'My Clients' widget.
  8. Validate that the 'Chart View' is displayed.
  9. Select "Form A" from the left-hand side.
  10. Validate the record filed in the previous steps is displayed.
  11. Validate the 'Decimal' field contains the value filed in the previous steps (Ex: -1.24).
  12. Validate the 'Integer' field contains the value filed in the previous steps (Ex: -1212).
  13. Close the Chart.
  14. Select "Client A" and access "Form A".
  15. Click [Edit] to edit the previous filed record.
  16. Enter a positive decimal value in the 'Decimal' field (Ex: 2.41).
  17. Validate the value is accepted.
  18. Enter a positive integer value in the 'Integer' field (Ex: 1212).
  19. Validate the value is accepted.
  20. Click [Submit].
  21. Double-click on "Client A" in the 'My Clients' widget.
  22. Validate that the 'Chart View' is displayed.
  23. Select "Form A" from the left-hand side.
  24. Validate the record updated in the previous steps is displayed.
  25. Validate the 'Decimal' field contains the value filed in the previous steps (Ex: 2.41).
  26. Validate the 'Integer' field contains the value filed in the previous steps (Ex: 1212).
  27. Close the Chart.
Topics
• Modeling
Update 7 Summary | Details
'Client Lookup/Header Configuration Manager' - Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CarePOV Management
  • Progress Notes (Group and Individual)
  • CLIENT DASHBOARD
  • Allergies and Hypersensitivities
  • Client Lookup/Header Configuration Manager
  • View Definition
  • NX View Definition
Scenario 1: Bed Board client alert icons display in the client header
Specific Setup:
  • Bed Board POV widget is installed and enabled.
  • Five "Client Alerts" are defined in "CarePOV Management" form with icons.
  • The "Client Information" widget is present on the Home View.
  • A client is enrolled in an inpatient episode and has data filed for the five client alerts to display (Client A).
Steps
  1. Open "CarePOV Management" form.
  2. Select the "Client Alerts" section.
  3. Select "Edit" in the 'Add or Edit Alert' field.
  4. Select an alert in the 'Client Alert' field.
  5. Select "Yes" in the 'Include in Client Header' field.
  6. Click [Save].
  7. Repeat the above steps to add the five defined client alerts to the client header.
  8. Select "Client A" and navigate to the "Client Information" widget.
  9. Validate the five "Client Alert" icons are displayed.
  10. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  11. Validate the five "Client Alert" icons are displayed in the client header.
  12. Close the form.
Scenario 2: Validate form access in the Client Header
Specific Setup:
  • A client must be admitted into an active episode and have 100 allergies on file (Client A).
  • There must be two users:
  • A user that is logged in and has full access to forms (User A).
  • A user that does not have access to the 'Allergies and Hypersensitivities' form (User B).
  • The users' myDay view must be configured to include the Client Information header (View A).
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and navigate to "View A".
  2. Hover over the 'Allergies (100)' link in the 'Client Header'.
  3. Validate a flyover displays fifteen allergies listed and 85 more.
  4. Click the 'Allergies (100)' link.
  5. Validate a menu displays and the user can scroll through all the allergies.
  6. Close the menu.
  7. Click edit icon.
  8. Validate the 'Allergies and Hypersensitivities' form opens.
  9. Validate the edit icon no longer displays in the 'Client Header'.
  10. Discard the form.
  11. Select "Client A" and launch the 'Client Dashboard'.
  12. Validate the 'Client Dashboard' displays as expected.
  13. Hover over the 'Allergies (100)' link in the 'Client Header'.
  14. Validate a flyover displays fifteen allergies listed and 85 more.
  15. Click the 'Allergies (100)' link.
  16. Validate a menu displays and the user can scroll through all the allergies.
  17. Close the menu.
  18. Click edit icon.
  19. Validate the 'Allergies and Hypersensitivities' form opens.
  20. Validate the edit icon no longer displays in the 'Client Header'.
  21. Discard the form.
  22. Log out.
  23. Log in as "User B".
  24. Select "Client A" and navigate to "View A".
  25. Validate the edit icon does not display in the 'Client Header'.
  26. Validate a flyover displays fifteen allergies listed and 85 more.
  27. Click the 'Allergies (100)' link.
  28. Validate a menu displays and the user can scroll through all the allergies.
  29. Close the menu.
  30. Launch the 'Client Dashboard'.
  31. Validate the edit icon does not display in the 'Client Header'.
  32. Hover over the 'Allergies (100)' link in the 'Client Header'.
  33. Validate a flyover displays fifteen allergies listed and 85 more.
  34. Click the 'Allergies (100)' link.
  35. Validate a menu displays and the user can scroll through all the allergies.
  36. Close the menu.
Scenario 3: Condensed Client Header validations
Specific Setup:
  • The logged in user must have access to the 'Client Lookup/Header Configuration Manager' form (User A).
  • The 'Bed Board POV' widget is installed and enabled.
  • Five "Client Alerts" are defined in the 'CarePOV Management' form with icons.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • A client is enrolled in an existing episode and has data filed for the five client alerts to display (Client A).
  • "Client A" must have allergies on file.
  • A program is defined (Program A).
  • A client is admitted in "Program A" (Client B).
  • Please note: This is for Avatar NX systems only.
  • This is for initial configuration. Once the 'Expand/Collapse' toggle has been selected, it will override settings in the 'Client Lookup/Header Configuration Manager' form for the user.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Validate the "Condensed Header" and "Condensed Header Override" fields display.
  3. Navigate to the 'Condensed Header' tab.
  4. Validate "Bed Board Alerts" is selected in the 'Condensed Header Field Position 2' field.
  5. Select any value in the 'Condensed Header Field Position 1' field.
  6. Select "Yes" in the 'Default Views To Condensed Header' field.
  7. Select "Yes" in the 'Default Client Entity Forms to Condensed Header' field.
  8. Validate text displays stating: "Note: This setting will default all views configured to include client information header in view to utilize the condensed header. Individual views may still override this setting via the options 'Default Client Information header to condensed view' in View Definition > View Designer."
  9. Navigate to the 'Condensed Header Override' tab.
  10. Click [Add New Item].
  11. Select "Program A" in the 'Program' field.
  12. Select any value in the 'Condensed Header Field Position 1' field.
  13. Select any value in the 'Condensed Header Field Position 2' field.
  14. Select "No" in the 'Default Client Entity Forms To Condensed Header' field.
  15. Click [Submit].
  16. Log out.
  17. Log in as "User A".
  18. Navigate to the 'All Documents' view.
  19. Select "Client A" from the 'My Clients' list.
  20. Validate the client information header is condensed.
  21. Validate the value selected in the 'Condensed Header Field Position 1' field displays.
  22. Validate the 'Bed Board Alerts' display.
  23. Click [View] and validate a menu displaying all 'Active Alerts'.
  24. Close the menu.
  25. Click [Allergies] and validate a menu displaying allergies.
  26. Close the menu.
  27. Click the 'Expand/Collapse' toggle.
  28. Validate the client information header is full size.
  29. Navigate to the 'myDay' view.
  30. Navigate to the 'All Documents' view.
  31. Validate the client information header is full size.
  32. Launch the 'Client Dashboard'.
  33. Validate the client information header is full size.
  34. Click the 'Expand/Collapse' toggle.
  35. Validate the client information header is condensed.
  36. Click [Close].
  37. Navigate to the 'myDay' view.
  38. Access the 'Progress Notes (Group and Individual)' form.
  39. Validate the client information header is condensed.
  40. Clear the 'Select Client' field.
  41. Enter and select "Client B" in the 'Select Client' field.
  42. Validate the client information header is full size.
  43. Close the form.
  44. Access the 'View Definition' form.
  45. Click [Select View].
  46. Select "Add New View" in the 'Select Views' field.
  47. Click [OK].
  48. Enter any value in the 'View ID' field.
  49. Enter "View A" in the 'View Description' field.
  50. Select "Home View" in the 'View Type' field.
  51. Select "Yes" in the 'Allow User To Customize View' field.
  52. Click [Launch View Designer].
  53. Validate 'Default Client Information header to condensed view' is disabled.
  54. Click [Include Client Information header in view].
  55. Validate 'Default Client Information header to condensed view' is now enabled.
  56. Select the desired widgets and arrange them as desired.
  57. Click [Submit], [Submit], and [No].
  58. Access the 'NX View Definition' form.
  59. Select "User" in the 'User or Role' field.
  60. Enter and select "User A" in the 'Select User' field.
  61. Click [Additional myDay Views].
  62. Select "View A" and click [OK].
  63. Click [File].
  64. Validate an 'Avatar NX View Definition' dialog stating: "Filed" and click [OK].
  65. Close the form.
  66. Validate "View A" displays in the top navigation.
  67. Navigate to "View A".
  68. Validate the client information header is full size.
  69. Select the 'Customize Toggle' button.
  70. Select the 'My Activity' menu.
  71. Select the 'View/Add Widgets' tab.
  72. De-select 'Include Client Information header in view'.
  73. Validate the client information head no longer displays.
  74. Select the 'Customize Toggle' button and close the menu.
Topics
• Progress Notes (Group And Individual) • RADplus Utilities • NX • Allergies and Hypersensitivities • myAvatar NX Only • View Definition
2022 Update 16 Summary | Details
Document Management - Perceptive 2022.01 Release
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Batch Capture and Indexing
  • Clinical Document Viewer
  • Client Document Capture
  • Document Capture
  • Staff Document Capture
  • Entity-Based Document Capture
  • Document Management Definition
  • Family Registration
  • Delete Document
Scenario 1: Perceptive Batch Capture and Indexing - JxBrowser enabled
Specific Setup:
  • Perceptive storage method must be utilized.
Steps
  1. Open the "Batch Capture and Indexing" form.
  2. Click "Capture" to create a new batch.
  3. Choose "Scanner" for the "Source".
  4. Click "Open Batch".
  5. Scan a document
  6. If Batch Verify is utilized, then click "Send To".
  7. If Batch Verify is not utilized, then click "Submit".
  8. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  9. Select the batch that was sent to this queue.
  10. Open the batch and click "Submit".
  11. Close form.
  12. Open the "Batch Capture and Indexing" form.
  13. Click "Capture" to create a new batch.
  14. Choose "File" for the "Source".
  15. Click "Browse" and browse to the location of where the file is stored on the server.
  16. Click "Open".
  17. Click "Open Batch".
  18. If Batch Verify is utilized, then click "Send To".
  19. If Batch Verify is not utilized, then click "Submit".
  20. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  21. Select the batch that was sent to this queue.
  22. Open the batch and click "Submit".
  23. Close form.
  24. Open "Chart Review" form for the client and episode that the documents were just scanned and imported for.
  25. Navigate to the form/category that you want to validate.
  26. Select a document that was scanned in.
  27. Validate that the document displays.
  28. Click the "Print" button.
  29. Print the document.
  30. Validate that the printed document matches what displayed on the viewer.
  31. Select a document that was imported in.
  32. Validate that the document displays.
  33. Click the "Print" button.
  34. Print the document.
  35. Validate that the printed document matches what displayed on the viewer.
  36. Open "Clinical Document Viewer".
  37. Validate you can view and print both the scanned and imported document.
Scenario 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.
Scenario 3: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 4: Staff Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • There must be a practitioner defined (Practitioner A).
  • A document must exist for import.
Steps
  1. Access the 'Staff Document Capture' form.
  2. Enter "Practitioner A" in the 'Staff ID' field.
  3. Click [Launch POS Capture].
  4. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  5. Click [Import].
  6. Validate the 'Document Capture' opens in a new window.
  7. Select any value in the 'Document Type' field.
  8. Enter any value in the 'Document Description' field.
  9. Click [Capture] and [Browse].
  10. Locate the file to be imported and click [Open] and [Done].
  11. Validate the image displays.
  12. Click [Save].
  13. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Staff" in the 'Select Type' field.
  16. Select "Individual" in the 'Select All or Individual Staff' field.
  17. Select "Practitioner A" in the 'Select Staff' field.
  18. Click [Process].
  19. Locate and select the document that was saved in the previous steps.
  20. Validate the image displays.
  21. Click [Close All Documents], [Search] and [Close].
  22. Navigate back to the open 'Staff Document Capture' form.
  23. Click [Launch POS Capture].
  24. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  25. Click [Import].
  26. Validate a second document capture window opens.
  27. Navigate back to the open 'Staff Document Capture' form.
  28. Click [Discard].
  29. Validate the document capture windows close and the form discards.
Scenario 5: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • Select a client, staff, provider, family and performing provider for the tests.
Steps
  1. Open the "Entity-Based Document Capture" form.
  2. Select "Client" in the "Entity Type" dropdown.
  3. Select "Non-episodic" in the "Episode Number" dropdown.
  4. Click "Launch POS Capture" button.
  5. Import in a document saved as a file on the server.
  6. Validate the document renders on screen.
  7. Select a "Document Type".
  8. Optionally, set the "Document Description" to desired text.
  9. Click the "Save" button.
  10. Validate that messages display indicating the document was successfully saved.
  11. Click the "Close" button.
  12. Close the form.
  13. Open the "Clinical Document Viewer".
  14. Select the "Client" Entity.
  15. Select the client from the document capture above.
  16. Validate a row was added for the document that was just saved.
  17. View the document to validate it displays as it was captured.
  18. Print the document to ensure it prints as it was captured.
  19. Open the "Entity-Based Document Capture" form.
  20. Select "Staff" in the "Entity Type" dropdown.
  21. Click "Launch POS Capture" button.
  22. Import in a document saved as a file on the server.
  23. Validate the document renders on screen.
  24. Select a "Document Type".
  25. Optionally, set the "Document Description" to desired text.
  26. Click the "Save" button.
  27. Validate that messages display indicating the document was successfully saved.
  28. Click the "Close" button.
  29. Close the form.
  30. Open the "Clinical Document Viewer".
  31. Set "Select Type" to "Staff".
  32. Select the staff from the document capture above.
  33. Validate a row was added for the document that was just saved.
  34. View the document to validate it displays as it was captured.
  35. Print the document to ensure it prints as it was captured.
  36. Open the "Entity-Based Document Capture" form.
  37. Select "Performing Provider" in the "Entity Type" dropdown.
  38. Click "Launch POS Capture" button.
  39. Import in a document saved as a file on the server.
  40. Validate the document renders on screen.
  41. Select a "Document Type".
  42. Optionally, set the "Document Description" to desired text.
  43. Click the "Save" button.
  44. Validate that messages display indicating the document was successfully saved.
  45. Click the "Close" button.
  46. Close the form.
  47. Open the "Clinical Document Viewer".
  48. Set "Select Type to "Performing Provider".
  49. Select the client from the document capture above.
  50. Validate a row was added for the document that was just saved.
  51. View the document to validate it displays as it was captured.
  52. Print the document to ensure it prints as it was captured.
  53. Open the "Entity-Based Document Capture" form.
  54. Select "Provider" in the "Entity Type" dropdown.
  55. Click "Launch POS Capture" button.
  56. Import in a document saved as a file on the server.
  57. Validate the document renders on screen.
  58. Select a "Document Type".
  59. Optionally, set the "Document Description" to desired text.
  60. Click the "Save" button.
  61. Validate that messages display indicating the document was successfully saved.
  62. Click the "Close" button.
  63. Close the form.
  64. Open the "Clinical Document Viewer".
  65. Set "Select Type" to "Provider".
  66. Select the client from the document capture above.
  67. Validate a row was added for the document that was just saved.
  68. View the document to validate it displays as it was captured.
  69. Print the document to ensure it prints as it was captured.
  70. Open the "Entity-Based Document Capture" form.
  71. Select "Family" in the "Entity Type" dropdown.
  72. Click "Launch POS Capture" button.
  73. Import in a document saved as a file on the server.
  74. Validate the document renders on screen.
  75. Select a "Document Type".
  76. Optionally, set the "Document Description" to desired text.
  77. Click the "Save" button.
  78. Validate that messages display indicating the document was successfully saved.
  79. Click the "Close" button.
  80. Close the form.
  81. Open the "Clinical Document Viewer".
  82. Set "Select Type" to "Family".
  83. Select the client from the document capture above.
  84. Validate a row was added for the document that was just saved.
  85. View the document to validate it displays as it was captured.
  86. Print the document to ensure it prints as it was captured.
  87. Close all forms.
Scenario 6: Chart Review - Document Capture - Scan Nonepisodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify it was non-episodic.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 7: Chart Review - Document Capture - Import Non Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Navigate to the "Chart".
  3. Click "Document Capture".
  4. Import a non-episodic document.
  5. Assign a "Document Type" to the document.
  6. Optionally, add a "Document Description".
  7. Save the document.
  8. Validate messages display that indicate the document was successfully saved.
  9. Select the document type from the list that the document was just saved under.
  10. Select the document that was just saved from the document list.
  11. Validate the document displays and prints as it was rendered upon import.
  12. Close all forms.
Scenario 8: Chart Review - Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Import a document and select an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was imported.
  11. Print the document and validate it prints as it was imported.
  12. Close the forms.
Scenario 9: Chart Review - Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 10: Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 11: Family Entity - Validation
Specific Setup:
  • Perceptive must be installed and configured.
  • Family entity must be configured on the perceptive server.
  • Using the "Document Management Defaults" form:
  • Select "Family" in the "Select Entity Types Allowed" checklist.
  • Using the "Document Management Definition" form
  • Add new document type(s) for the Family entity documents.
  • Using "Family Registration", create a family and add family members.
Steps
  1. Open the "Entity-Based Document Capture" form.
  2. Select "Family" in the "Entity Type" field.
  3. Select the Family created in setup.
  4. Scan a document.
  5. Save the document and validate messages are received saying it was saved successfully and added to Avatar.
  6. Open the "Clinical Document Viewer".
  7. Retrieve the family document that was scanned in.
  8. Validate the document displays as it was captured.
  9. Print the document and validate it prints as it displays.
  10. Open the "Entity-Based Document Capture" form.
  11. Select "Family" in the "Entity Type" field.
  12. Select the Family created in setup.
  13. Import a document.
  14. Save the document and validate messages are received saying it was saved successfully and added to Avatar.
  15. Open the "Clinical Document Viewer".
  16. Retrieve the family document that was imported in.
  17. Validate the document displays as it was captured.
  18. Print the document and validate it prints as it displays.
Scenario 12: Clinical Document Viewer - "Void & Copy" documents
Specific Setup:
  • Perceptive is enabled.
  • In "User Definition", validate user has permissions to void documents.
  • The entity being tested must have imported or scanned documents on file.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select the desired entity in the "Entity Type field".
  3. Select "Individual" in the 'Select All or Individual' entity field.
  4. Select the desired entity (Client ID, Staff ID, Family ID, etc).
  5. Click [Process].
  6. Select a document and view it.
  7. Click [Void] and then [Void & Copy]
  8. Select a target entity to copy the document to.
  9. If the entity is a client, select the desired episode in the 'Select Episode' field.
  10. Click [Void].
  11. Validate the document list now has a Status of "Void" for the original document.
  12. Select the "Search" section.
  13. Select the target entity.
  14. Click [Process].
  15. Validate the copied document is now in the document list for this entity.
  16. View the copied document and validate it displays as expected.
  17. Click [Close All Documents].
  18. Select the "Search" section.
  19. Click [Close].
Scenario 13: Clinical Document Viewer - "Void" documents
Specific Setup:
  • Perceptive is enabled.
  • User has permissions to void documents.
  • A client must have non-routed documents on file in the 'Clinical Document Viewer' (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer'.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Select "Client A" in the 'Select Client' field.
  4. Click [Process].
  5. Select any non-routed document and view it.
  6. Click [Void] and [Void] again.
  7. Select the desired value in the 'Void Reason' field.
  8. Enter the desired value in the 'Void Comments' field.
  9. Click [Void] and [Close All Documents].
  10. Select the "Search" section.
  11. Click [Close].
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void".
  14. Select the document.
  15. Validate the document displays with "Voided" in the 'Console Widget Viewer'.
Scenario 14: Clinical Document Viewer - View and Print
Specific Setup:
  • Select a client who has documents that have been routed, scanned and imported.
Steps
  1. Open the "Clinical Document Viewer" form.
  2. Open a document that was imported from a .bmp file.
  3. Validate you can view and print this document.
  4. Open a document that was imported from a .gif file.
  5. Validate you can view and print this document.
  6. Open any document that was imported from a .jpg file.
  7. Validate you can view and print this document.
  8. Open any document that was imported from a .tif file.
  9. Validate you can view and print this document.
  10. Open any document that was imported from a .txt file.
  11. Validate you can view and print this document.
  12. Open any document that was imported from a .xls file.
  13. Validate you can view and print this document.
  14. Open any document that was imported from a .xml file.
  15. Validate you can view and print this document.
  16. Open any document that was imported from a .doc file.
  17. Validate you can view and print this document.
  18. Open any document that was imported from a .png file.
  19. Validate you can view and print this document.
  20. Open any document that was imported from a .docx file.
  21. Validate you can view and print this document.
  22. Open any document that was imported from a .xslx file.
  23. Validate you can view and print this document.
  24. Open any routed progress note or treatment plan type of document.
  25. Validate you can view and print this document.
  26. Open any documents that were imported from a .pdf file.
  27. Validate you can view and print this document.
  28. Select 4 random documents to view.
  29. Validate that all 4 documents open for display and that all of them display.
  30. Click "Close All Documents".
  31. Select the same 4 random documents to print.
  32. Click "Print All".
  33. Validate all 4 documents preview and print out as if it's one file.
Scenario 15: Clinical Document Viewer - Undocked
Specific Setup:
  • Select a test client who has multiple documents on file.
Steps
  1. Click the "Undocked" icon on the "Clinical Document Viewer" form.
  2. Open a random document.
  3. Validate you can view and print the document.
  4. Select 4 documents to view.
  5. Validate you can display all 4 documents.
  6. Select 4 documents to print.
  7. Validate all 4 documents print as one document.
Topics
• Perceptive • Clinical Document Viewer • NX
2022 Update 73 Summary | Details
Document Capture - Upload Notification To Dos
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Clinical Document Viewer
  • Document Capture
  • User Role Definition
  • User File Import
  • Admission
  • Review To Do Item
Scenario 1: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 2: Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 3: Validate Document Upload Notifications
Specific Setup:
  • Using the "User Role Definition" form:
  • Select a user role.
  • Navigate to the "Document Management" section.
  • Click "Specify Forms" in the "Forms to Send Upload Notifications".
  • Click "Select Forms".
  • Select one of the forms to receive upload notifications.
  • Using the "User Definition" form, assign the user signed on to the user role defined above.
  • Admit or select a test client.
Steps
  1. Open the "Client Document Capture" form.
  2. Import or scan in a document for the test client.
  3. Set the "Document Type" to a form that is set to receive upload notifications for the user.
  4. Save the document.
  5. Navigate to the "myToDo's" widget.
  6. Validate a To Do was generated for the upload notification.
  7. Select the upload notification item.
  8. Set the "Set To Do Item to Reviewed" to "Reviewed".
  9. Click "Submit".
  10. Navigate to the "myToDo's" widget.
  11. Validate the Upload Notification To Do item is removed from the widget.
  12. Open the "Clinical Document Viewer" form.
  13. Locate and display the document that was just saved.
  14. Validate it displays appropriately.
Scenario 4: Validate Delayed Document Upload Notification
Specific Setup:
  • Using the "User Role Definition' form:
  • Select a user role.
  • Navigate to the "Document Management" section.
  • Click "Specify Forms" in the "Forms to Send Upload Notifications".
  • Click "Select Forms".
  • Select one of the forms to receive upload notifications.
  • Using the "User Definition" form, assign the user signed on to the user role defined above.
  • Admit or select a test client.
Steps
  1. Open the "Client Document Capture" form.
  2. Import or scan in a document for the test client.
  3. Set the "Document Type" to a form that is set to receive upload notifications for the user.
  4. Save the document.
  5. Navigate to the "myToDo's" widget.
  6. Validate a To Do was generated for the delayed upload notification.
  7. Select the delayed upload notification item.
  8. Set the "Set To Do Item to Reviewed" to "Reviewed".
  9. Click "Submit".
  10. Navigate to the "myToDo's" widget.
  11. Validate the Delayed Upload Notification To Do item is removed from the widget.
  12. Open the "Clinical Document Viewer" form.
  13. Locate and display the document that was just saved.
  14. Validate it displays appropriately.
Clinical Data Repository (CDR) - Remove DocM and DocR schema tables from the Clinical Data Repository
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Capture
  • Client Document Capture
  • Clinical Document Viewer
Scenario 1: Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 2: Removing DocR and DocM tables from CDR
Steps

Internal Testing Only

Delete/Re-Assign To Do Items - Acknowledgment To Dos no longer displayed
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Admission
  • Delete/Re-Assign To Do Items
Scenario 1: Progress Note (Group and Individual) - Document Routing - Validate "Acknowledgement" To-Do functionality
Specific Setup:
  • A client must be admitted in an existing episode. (Client A)
  • Must have two users defined with associated staff members (User A and User B). Must be logged in as "User A".
  • Document routing must be enabled for the 'Progress Note (Group and Individual)' form in 'Document Routing Setup' with the following fields set.
  • Have the 'Approver Required' field set to "Yes".
  • Have the 'Acknowledgment Allowed' field set to "Yes".
  • Have the 'Allow Notifications When Final' field set to "No".
  • Have the 'Allow Comments During Approval' field set to "No".
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. Select any value in the 'Note Type' field.
  4. Populate any required and desired fields.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note] and [Accept and Route].
  7. Enter the password associated with "User A" and click [Verify].
  8. Enter the practitioner associated to "User A" in the 'Add Approver' field and click [Add].
  9. Verify the 'Add Members to Acknowledge' field is present.
  10. Search for the practitioner associated to "User B" using only one letter in the 'Add Members to Acknowledge' field.
  11. Click [Add] and [Submit].
  12. Close the form.
  13. Navigate to the 'My To Do's' widget.
  14. Validate there is a To-Do for the progress note filed in the previous steps.
  15. Click [Approve Document].
  16. Validate the 'Document Preview' contains the progress note data filed in the previous steps.
  17. Click [Accept].
  18. Enter the password associated with "User A" and click [Verify].
  19. Validate the To-Do is no longer present.
  20. Log out.
  21. Login as "User B" and navigate to the 'My To Do's' widget.
  22. Validate there is a To-Do for the progress note filed in the previous steps.
  23. Click [Acknowledge Document] and [Acknowledge].
  24. Enter the password associated with "User B" and click [Verify].
  25. Validate the To-Do is no longer present.
Scenario 2: Delete/Re-Assign Ackknowledgement To Dos
Specific Setup:
  • Admit or select a test client.
  • Using the "Document Routing Setup" form, enable document routing.
  • Enable acknowledgments by setting the field "Acknowledgement Allowed" to "Yes".
  • Set "Verification Level of Acknowledgment" to "Warn User if Acknowledgement is missing"
  • Set "Days after finalized document to alert" to "Y".
  • File the form.
  • Using "Dictionary Update", print the dictionary for the data element Note Type (10751).
  • Locate a note type that says it requires a signature.
Steps
  1. Open the Progress note form that was used during setup.
  2. Create a progress note.
  3. Set the "Note Type" to one the requires a signature.
  4. Set the "Draft/Final" field to "Final".
  5. Select "Caseload Practitioners" from the "Add Members to Acknowledge".
  6. Set "Add Approver" to a valid practitioner.
  7. Validate the Practitioner chosen in Add Members to Acknowledge" listbox has "Acknowledge" check marked.
  8. Submit the form to route the document.
  9. Navigate to the "myToDo's" widget.
  10. Select the To do that was just generated.
  11. Click the "Accept" button.
  12. Click the "Sign" button.
  13. Close the To Do widget.
  14. Sign off of Avatar.
  15. Log back in as the user that you designated as an approver.
  16. Navigate to the "myToDo's" widget.
  17. Locate the To do generated for this test.
  18. Click "Accept".
  19. Click "Sign".
  20. Log off of Avatar.
  21. Log back on as the user who was designated to receive the acknowledgment To Do.
  22. Navigate to the "myToDo's" widget.
  23. Validate it contains the "Acknowledgment Document To do.
  24. Open the " Delete/Re-Assign To Do Items" form.
  25. Set "Delete/Re-Assign" to "Delete".
  26. Set "Select User" to the user who received the Acknowledgment To Do".
  27. Select a To Do to be deleted.
  28. Add a comment as to why it's being deleted.
  29. Navigate to the "myToDo's" widget and validate the to do was removed.
Background Notification Task - Infinite Loop when an error is encountered
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Clinical Document Viewer
  • Document Capture
  • User Role Definition
  • User File Import
  • Admission
  • Review To Do Item
Scenario 1: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 2: Validate Document Upload Notifications
Specific Setup:
  • Using the "User Role Definition" form:
  • Select a user role.
  • Navigate to the "Document Management" section.
  • Click "Specify Forms" in the "Forms to Send Upload Notifications".
  • Click "Select Forms".
  • Select one of the forms to receive upload notifications.
  • Using the "User Definition" form, assign the user signed on to the user role defined above.
  • Admit or select a test client.
Steps
  1. Open the "Client Document Capture" form.
  2. Import or scan in a document for the test client.
  3. Set the "Document Type" to a form that is set to receive upload notifications for the user.
  4. Save the document.
  5. Navigate to the "myToDo's" widget.
  6. Validate a To Do was generated for the upload notification.
  7. Select the upload notification item.
  8. Set the "Set To Do Item to Reviewed" to "Reviewed".
  9. Click "Submit".
  10. Navigate to the "myToDo's" widget.
  11. Validate the Upload Notification To Do item is removed from the widget.
  12. Open the "Clinical Document Viewer" form.
  13. Locate and display the document that was just saved.
  14. Validate it displays appropriately.
Scenario 3: Validate Delayed Document Upload Notification
Specific Setup:
  • Using the "User Role Definition' form:
  • Select a user role.
  • Navigate to the "Document Management" section.
  • Click "Specify Forms" in the "Forms to Send Upload Notifications".
  • Click "Select Forms".
  • Select one of the forms to receive upload notifications.
  • Using the "User Definition" form, assign the user signed on to the user role defined above.
  • Admit or select a test client.
Steps
  1. Open the "Client Document Capture" form.
  2. Import or scan in a document for the test client.
  3. Set the "Document Type" to a form that is set to receive upload notifications for the user.
  4. Save the document.
  5. Navigate to the "myToDo's" widget.
  6. Validate a To Do was generated for the delayed upload notification.
  7. Select the delayed upload notification item.
  8. Set the "Set To Do Item to Reviewed" to "Reviewed".
  9. Click "Submit".
  10. Navigate to the "myToDo's" widget.
  11. Validate the Delayed Upload Notification To Do item is removed from the widget.
  12. Open the "Clinical Document Viewer" form.
  13. Locate and display the document that was just saved.
  14. Validate it displays appropriately.
Delete/Re-Assign To Do Items - Notification To Dos no longer displayed
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Send To Do Notification
Scenario 1: Delete/Re-Assign Notification To Dos
Specific Setup:
  • Select a client for this test.
Steps
  1. Open the "Send To Do Notification" form.
  2. Select the test client.
  3. Enter text into the "To Do Message" field.
  4. Select the user logged in as in the "Select User" field.
  5. Click "Add User" button.
  6. Validate the user was added to the "Send To" text box.
  7. Click "File To Do" button.
  8. Navigate to the "myToDo's" widget.
  9. Validate the To Do that was just generated is contained in the widget.
CareFabric - SendCareConnectClientDocument action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Transfer Queue Configuration
  • Document Management Definition
  • Clinical Document Viewer
Scenario 1: Disable Transfer Queue - Overwrite existing document
Steps

Internal Testing Only
Topics
• Document Scan/Import • Document Management • Perceptive
2022 Update 96 Summary | Details
RADPlus - Family Entity Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Family Registration
  • Delete Last Movement
  • Table Definition (PM)
  • Family Entity User Modeled Form
  • Delete Family
Scenario 1: Change MR# - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA], note their current PatID# [OrigPatID#]
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved
  • Have a report [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
  2. Validate there is a row displayed for [FamilyA] and [ClientA]
  3. Open "Change MR#" form in Avatar PM.
  4. Select [ClientA] in the "Client ID" field and note their current PatID# [OrigPatID#]
  5. Click [Assign MR#].
  6. Note the new PatID# assigned, [NewPatID#]
  7. Click [Submit].
  8. Validate the form files successfully
  9. At the home view, search for the [OrigPatID#] noted in step 3a
  10. Validate there are no results
  11. Now search for the [NewPatID#] noted in step 3b
  12. Validate the [NewPatID#] is found and the associated client is [ClientA]
  13. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
  14. Validate there is a row displayed for [FamilyA] and with new PatID# [NewPatID#] displayed for [ClientA]
Scenario 2: Client Delete - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA]
  • In form "Family Registration", have a family created [FamilyA] with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table
  • User has launched [ReportA] and has logged into the system
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
  2. Validate there is a row displayed for [FamilyA] and [ClientA]
  3. Open "Client Delete" form.
  4. Select [ClientA] in the "Client ID" field.
  5. Validate an error message is received "Client Must Be Removed From All Families Before Client Can Be Deleted."
  6. Click [OK]
  7. Close the form
  8. Open form "Family Registration"
  9. Select [FamilyA]
  10. Click the "Family Members" section
  11. Select the row for [ClientA]
  12. Click [Delete]
  13. Validate the client is removed as a family member
  14. Submit the form
  15. Open "Client Delete" form.
  16. Select [ClientA] in the "Client ID" field.
  17. Validate an error message is received "All Movements must be deleted before Client can be deleted"
  18. Click [OK]
  19. Close the form
  20. Open form "Delete Last Movement"
  21. Select [ClientA]
  22. Select the admission episode from the "Episode Number" drop down list
  23. Click [Submit]
  24. Click [Yes] to continue
  25. Validate the form submits successfully
  26. Open "Client Delete" form.
  27. Select [ClientA] in the "Client ID" field.
  28. Click [Submit]
  29. Validate the form submits successfully
  30. At the home view, search for [ClientA]
  31. Validate there are no results
  32. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
  33. Validate there is no longer a row displayed for [FamilyA] and [ClientA]
Scenario 3: "Family" Entity User Modeled Form - Create a new form
Specific Setup:
  • In form "Family Registration" have a family created [FamilyA] with one or more clients added as family member's in "Family Members" section of the form.

For this test, [ClientA], [ClientB] and [ClientC] are used

Steps
  1. Open form "Envelope Definition"
  2. Click the [New Avatar Envelope]
  3. Set the "Envelope Description" field to the desired name [EnvelopeA], for the envelope
  4. Select "Family" in the "Entity Database" field
  5. Click the "Yes - Is Envelope Eligible for Export" radio button
  6. Click the "Yes - Always Allow Export" radio button
  7. Click [Submit]
  8. Validate the form files successfully
  9. Open form "Table Definition"
  10. At the "Select Avatar Table" prompt enter the desired table name [TableA]
  11. Click the [New Avatar Table] button
  12. From the "Envelope" dialog drop down list, select [EnvelopeA]
  13. Populate the "Table Name" field with the desired table name [TableA]
  14. Populate the "Table Description" field with the desired description of the table
  15. Select the "Column Definition" section
  16. Click the [Add New Item] button
  17. Select "Family Member(s)" column from the "Type of Column" drop down list
  18. Populate the "Column Name" field
  19. Populate the "Column Description" field
  20. Populate the "Column Label" field
  21. Validate the "Column Definition" grid contains a row with values just populated
  22. Click the [Add New Item] button
  23. Select "Draft/Final (Document Routing)" column from the "Type of Column" drop down list
  24. Populate the "Column Name" field
  25. Populate the "Column Description" field
  26. Populate the "Column Label" field
  27. Validate the "Column Definition" grid contains a row with values just populated
  28. Repeat step 4 for any other desired prompts to be added from the "Type of Column" drop down list
  29. Validate results are as expected
  30. Click [Submit]
  31. Validate the form files successfully
  32. Open form "Form Definition"
  33. At the "Select Avatar Table" prompt enter the desired form name [FormA]
  34. Click the [New Avatar Form] button
  35. From the "Envelope" dialog drop down list, select [EnvelopeA]
  36. Populate the "Table Name" field with the desired table name [TableA]
  37. Populate the "Table Description" field with the desired description of the table
  38. Select a menu location for the form from the "Menu to Place Form Under" field
  39. Populate the "Form Name" field [FormA]
  40. In the "Primary Table" field, select [TableA]
  41. Click the "Pre-display" section
  42. Select one or more pre-display columns from the "Primary Table Pre-display" column prompts
  43. Click the "Section Definition" section
  44. Click [Add New Item] and populate the "Section Description" field
  45. Click the "Object Definition" section
  46. Click [Add New Item]
  47. From the "Table Column" field, select the "Family Member's" column
  48. Validate the "Object Definition" grid reflect the column added
  49. From the "Table Column" field, select the "Draft/Final" column
  50. Validate the "Object Definition" grid reflect the column added
  51. Repeat step b adding any other columns desired from the "Table Column" field
  52. Validate the "Object Definition" grid reflect the columns added
  53. Click [Submit]
  54. Validate the form files successfully
  55. Open [FormA]
  56. At the "Select Family" prompt, select [FamilyA]
  57. Validate the form loads successfully
  58. Verify the "Family Member's" field is present and contains each client added as a family member in the set up, along with a check box next to their name.
  59. Verify the "Draft/Final" field is present on the form.
  60. Verify any other fields added during "Form Definition" are present on the form, as expected.
  61. Select values for any desired fields on the form
  62. Submit the form
  63. Validate the form files successfully.
Scenario 4: "Family" Entity User Modeled Form- Form submission and Doc Routing Validations
Specific Setup:
  • The "Document Management Defaults" form has "Family - User Defined Family" selected in the field "Select Entity Types Allowed"
  • The "Document Management Definition" form has been submitted with a "Form Name" [FName] associated to the "Family" entity in the "Entity Database" field.
  • In form "Family Registration" have a family created [Family] with family members added in "Family Members" section of the form. For the test [ClientA] and [ClientB]
  • Have a user modeled form [Form] created based on the "Family - User Defined Family" entity database
  • [Form] contains fields from [Table] that include a "Family Member(s)" column type, a field using a "Draft/Final" column type and any other desired field types
  • [Form] is enabled for document routing with form name [FName] selected in the "Select Type" field
  • [User] is a staff member who has access to [Form] and [Table]
  • [User] has the "My To do's" widget on their home view
  • Have a report [Report], set to display data in the "SYSTEM.user_modelled_fam_members" table
  • Log in as [User]
Steps
  1. Access [Form]
  2. In the "Select Family" prompt, select [Family]
  3. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB]
  4. Click "All", to select all members
  5. Populate any other desired fields on the form
  6. Select "Draft" in the 'Draft/Final' field.
  7. Click [Submit]
  8. Validate the form files successfully
  9. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
  10. Validate there is a row displayed for [Family] and [ClientA]
  11. Validate there is a row displayed for [Family] and [ClientB]
  12. Access [Form]
  13. In the "Select Family" prompt, select [Family]
  14. In the pre-display screen, click [Edit] to select the row filed in step 1
  15. Validate all fields are populated, as expected
  16. Close the form
  17. Access [Form]
  18. In the "Select Family" prompt, select [Family]
  19. In the pre-display screen, select the row filed in step1
  20. Click [Delete]
  21. Validate the row is removed from the pre-display
  22. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
  23. Validate the row field for [Family] and [ClientA], has been deleted
  24. Validate the row field for [Family] and [ClientB], has been deleted
  25. Access [Form]
  26. In the "Select Family" prompt, select [Family]
  27. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB]
  28. Click "All", to select all members
  29. Populate any other desired fields on the form
  30. Select "Final in the 'Draft/Final' field.
  31. Click [Submit] and then [OK]
  32. Validate the "Confirm Document" screen displays all data submitted, including clients [ClientA] and [ClientB] listed in the "Family Member's field.
  33. Click [Accept and Route]
  34. Enter the password for the user in the 'Password' field and click [OK].
  35. At the "Route Document to" dialog, add [User] as an approver
  36. Click [Submit]
  37. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
  38. Validate there is a row displayed for [Family] and [ClientA]
  39. Validate there is a row displayed for [Family] and [ClientB]
  40. Navigate to the "My To Do's" widget
  41. Click the "New" tab
  42. Validate the To Do for [Form] is present in the list
  43. Validate the "Client" column indicates [Family]
  44. Click [Approve Document]
  45. Validate the document displays all data submitted, including clients [ClientA] and [ClientB] in the "Family Member's" field.
  46. Click [Accept]
  47. Validate the To Do is removed the widget, as expected
  48. In the "My Clients" widget, select any one of the clients selected as a family member in submission of [Form] in step 1. For example [Client]
  49. Double click on the client to open their "Chart"
  50. In the "Documents" section on left side panel, click the form type [Fname], associated with [Form]
  51. Locate the row listed for the document approved for [Form] in step 2
  52. Click the "View" check box and then the [View] button to display the document
  53. Validate the document displays all the data submitted as expected
  54. Close the chart
Scenario 5: Delete Family - Form (Submission and Validations)
Specific Setup:
  • Have an active test client on the system [ClientA]
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
  • File a row for [FamilyA], selecting [ClientA] selected in the "Family Members" field and routing the document to [UserA] to create To do
  • [UserA] has the "My To do's" widget on their home view
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table
  • [UserA] has launched [ReportA] and has logged into the system
Steps
  1. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
  2. Verify a data row is displayed for the row filed in the set up for [FamilyA] that includes [ClientA]
  3. On the home view, validate a To do exists in the "My To do's" widget for the row filed in [FormA] in the set up
  4. Open form "Delete Family"
  5. Select [FamilyA]
  6. Validate an error message is displayed stating "The Family has members on file. You must delete all family members in the Family Registration form prior to deleting the family"
  7. Click [OK]
  8. Open form "Family Registration"
  9. Select [FamilyA]
  10. Click the "Family Members" section
  11. Select each family member row and click delete to remove the row
  12. Submit the form
  13. Open form "Delete Family"
  14. Select [FamilyA]
  15. Click [Submit]
  16. At the "Delete Family" dialog, click [Yes]
  17. Validate the message "Family has been Deleted" displays
  18. Click [OK]
  19. Open form "Delete Family"
  20. Search for [FamilyA]
  21. Validate [FamilyA] is not found
  22. Return to the "My To Do's" widget
  23. Validate a To do is no longer present for [FormA] for [ClientA]
  24. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
  25. Verify there are no rows displayed for [FamilyA]
Topics
• Client Merge • NX • Database Tables
2022 Update 103 Summary | Details
Console Widget Viewer - Perceptive enabled
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • HomeView - Documents Widget
  • HomeView - Console Widget Viewer
Scenario 1: Console Widget Viewer - validate print preview and print output
Specific Setup:
  • User has the 'Primary All Documents Widget' and the 'Console Widget Viewer' on their myDay view.
  • "Client A" has data filed in various forms.
Steps
  1. Select "Client A" and access the 'Primary All Documents Widget'.
  2. Select the 'All Forms' tab.
  3. Select the first desired form, for example 'Diagnosis'.
  4. Click [Print Current].
  5. In the 'Console Widget Viewer', validate the print preview displays as expected without any truncation.
  6. Select several other desired forms.
  7. Click [Print All].
  8. In the 'Console Widget Viewer', validate the print preview displays as expected for all forms, without any truncation.
  9. Click [Print].
  10. Validate the printed forms display as expected, without any truncation.
Scenario 2: Console Widget Viewer - Retrieving and printing documents from Perceptive enabled system
Specific Setup:
  • This update is to be tested in a Perceptive enabled system.
  • Add the "Documents Widget" and the "Console Widget Viewer" to the user's home view using "View Definition".
Steps
  1. Generate a progress note document using one of the progress note forms.
  2. Navigate to the "Documents Widget" on the user's home view.
  3. Locate the progress note created for this test.
  4. Highlight that row in the widget.
  5. Click "View".
  6. Validate the document is retrieved and displays in the "Console Widget Viewer".
  7. Click "Print" to print the document to a printer.
  8. Validate the printed output matches the document displayed in the "Console Widget Viewer".
Topics
• Console Widget • Perceptive
2022 Update 106 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:
  • Final to Draft Override (CWS)
  • Final to Draft Override (PM)
Scenario 1: Final to Draft Override - Form Validations
Specific Setup:
  • A modeled form is defined with the 'Draft/Final' prompt (Form A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Submit].
  5. Access the 'Final to Draft Override' form.
  6. Select "Form A" in the 'Form' field.
  7. Select "Client A" in the 'Entity Lookup' field.
  8. Click [Select Row].
  9. Select the finalized record filed in the previous steps and click [OK].
  10. Validate the 'Row Contents' field contains the values entered in the previous steps.
  11. Enter the desired value in the 'Override Reason' field.
  12. Click [Submit].
  13. Select "Client A" and access "Form A".
  14. Select the record filed in the previous steps and click [Edit].
  15. Validate "Draft" is now selected in the 'Draft/Final' field.
  16. Close the form.
Topics
• Final to Draft Override
2022 Update 110 Summary | Details
Form Definition - Event Logic
Scenario 1: Form Definition - Event Logic setup and validations
Specific Setup:
  • Have a "Modeled" form [ModeledForm], that contains three fields that will be used to set up a "Calculation Type" event in "Form Definition". For this test, the following fields are set up:
  • [FieldA] - a "Dictionary" field
  • [FieldB] - an "Integer" field
  • [FieldC]- a "Decimal" field
Steps
  1. Open "Form Definition" and select the [ModeledForm]
  2. Click the "Section Def" tab and select the section with fields defined in the setup
  3. Click the "Object Def" tab
  4. Select [FieldB]. This will be the field that will trigger the calculation event
  5. Click to the "Event" section and click the [Add Item] button
  6. Set the "Type of Event" field to "Result of Input with Value Checking"
  7. Set the "Compare with for Event" field, select "Specific Value"
  8. Set the "Specific Value" field to a desired value that will be used to trigger the event. For this test "!0" is used
  9. Set the "Relationship to Comparison Value to Trigger Event" select "Equal To"
  10. Set the "Set Value to Specific Table Value on Event" to "Yes"
  11. Set the "Table Value to Have Value Changed on Event" to [FieldC]. (This will be the field populated with the result of the calculation)
  12. Set the "Table Column Value To" to "Calculation Result"
  13. Set the Calculation Type" to "Addition"
  14. Click the "Left Operand" field
  15. Validate [FieldC] is present and select that value
  16. Click "Submit" to file the form
  17. Validate the form files successfully
  18. Re-open "Form Definition"
  19. Click the "Section Def" tab and select the section with fields defined in the setup
  20. Click the "Object Def" tab
  21. Select [FieldB]
  22. Click to the "Event" section
  23. Validate each field value selected in step 1d is populated as expected
  24. Close the form
  25. Open the [ModeledForm]
  26. Navigate to [FieldA] and enter any value. For this test "4" is used
  27. Navigate to [FieldB] enter a value other than "10", which was the trigger value set up
  28. Validate [FieldC] is not populated
  29. Navigate back to [FieldB] and enter "10"
  30. Validate [FieldC] is populated with addition result of [FieldA] plus [FieldB], as expected. In this test, "14" was validated
  31. Submit the form
  32. Return to the [ModledForm]
  33. Select the row just submitted in step 3
  34. Validate all fields are populated as expected
Chart View - Data display
Scenario 1: Chart View - Form data validations
Specific Setup:
  • Have a copy of the "Treatment Plan" form [TPlanCopy] created using form "Create New Treatment Plan"
  • Have a modeled table[MTable] that includes any desired field types and also includes the "Selection Leaf" field that points to [TPlanCopy]. For this example: "Selection Leaf: TPlanCopy" would be listed for selection.
  • Create a "Modeled" form [MForm] that includes all the fields table [MTable]
  • Have a treatment plan filed in treatment plan[TPlanCopy] for a client [TestClient], that includes "Problem", "Goal", "Objective" and an "Intervention" tree view items submitted in the form
  • Have the user with access to the modeled form [MForm]
  • Have the modeled form [MForm] added to the users chart view
Steps
  1. Select client [TestClient]
  2. Open modeled form [MForm]
  3. Click the [Select Treatment Plan Item] button
  4. Validate a "Tab" is opened named with the name of the treatment plan copy created in the set up [TPlanCopy]
  5. Validate the data displayed contains the "Problems", "Goals", "Objective", "Interventions" tree view data submitted in the setup
  6. Validate the data displayed for each tree item is as expected and listed in a readable format
  7. Select the last tree item, "Interventions", this will bring in all connected tree items
  8. Click the [Return] button
  9. In the "Selection Leaf" field text box
  10. Validate the "Problems", "Goals", "Objective", "Interventions" tree view data is displayed as expected, and in a readable format
  11. Submit the form
  12. Validate the form files successfully
  13. Re-open [MForm] for client [TestClient]
  14. Select the row just submitted
  15. Validate all fields are populated, as expected
  16. Close the form
  17. Open "Chart" view for client [TestClient]
  18. Select [MForm] on the left side forms list
  19. Validate the data under the "Select Leaf:" field includes the "Problems", "Goals", "Objective", "Interventions" tree view data as expected
  20. Validate the data is in a readable paragraph format, with each item (Problem, Goal, Objective, etc) starting on a separate line.
  21. Validate data in any other fields are displayed as expected
Envelope Import - Mapped Dictionaries
Scenario 1: Envelope Export/Import - Validate forms that contain "Mapped" dictionary fields
Specific Setup:
  • Have a server with two Avatar instances setup [SystemA] and [SystemB]
  • [SystemA] has several programs set up in form "Program Maintenance" that include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
  • [SystemB] has several programs set up in form "Program Maintenance" but they do not include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
  • [SystemA] contains two modeled "Envelopes"
  • [EnvelopeA] contains [FormA], it includes a dictionary field [FormA_Dict1] which is mapped to the "(10011) Program" dictionary
  • [EnvelopeB] contains [FormB], it contains a dictionary field [FormB_Dict1] that is mapped to the mapped dictionary "[FormADict1]" set up in [FormA]
  • Both envelopes have been exported from [SystemA] and the export files have saved on the server
  • User has logged in [SystemB]
Steps
  1. Open form "Envelope Import"
  2. Click [Select Envelope Import File]
  3. Navigate to the location of [EnvelopeA] and select the file
  4. Select "Create New"
  5. Click "Begin Import Scan"
  6. Validate there are no errors or warnings in the scan results
  7. Click [Begin Import]
  8. Validate the envelope imports successfully
  9. Repeat steps 1 for [EnvelopeB]
  10. Validate the results are as expected
  11. Open [FormA]
  12. Navigate to field [FormADict1]
  13. Validate programs "ProgramA(800)", "ProgramB(900) and "ProgramC(950) are not displayed in the field, as expected
  14. Select any other program
  15. Submit the form
  16. Return to [FormA]
  17. Select the row just submitted
  18. Validate field [FormADict1] contains the expected value
  19. Close the form
  20. Open [FormB]
  21. Navigate to field [FormBDict1]
  22. Validate programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)" are not displayed in the field, as expected
  23. Select any other program
  24. Submit the form
  25. Return [FormB]
  26. Select the row just submitted
  27. Validate field [FormBDict1] contains the expected value
  28. Close the form
Form "Display User"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Display User
  • User Display Report
Scenario 1: "Display User" Form - "User Display" report data validations
Specific Setup:
  • Have a user [UserA] who is not assigned to a user role
  • Have another user [UserB] who is assigned to a user role [RoleA]
  • Have another user [UserC] who is assigned to a user role [RoleB]
  • In form "User List Management", have or create a new user list [Userlisttest] with following users submitted in the form
  • In the "Workflow Users" section, add [UserA]
  • In the "Workflow User Roles" section, add [RoleA] but do not add [RoleB]
  • Logged in user has access to form "Display User"
Steps
  1. Open form "Display User"
  2. In field "Individual or All Users", click the "Individual" radio button
  3. In the "Select User" field, select [UserA]
  4. Click the [Display User(s)] button
  5. Validate the "User Display" report generates successfully and in a timely manner
  6. Validate the "User ID" field is populate with [UserA]
  7. Validate the "User Description" field is populated as expected
  8. Validate the "Associate With User Role" field is set to "No", as expected
  9. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  10. Close the report
  11. In the "Select User" field, select [UserB]
  12. Click the [Display User(s)] button
  13. Validate the "User Display" report generates successfully and in a timely manner
  14. Validate the "User ID" field is populate with [UserB]
  15. Validate the "User Description" field is populated as expected
  16. Validate the "Associate With User Role" field is set to "Yes"
  17. Validate the "User Role" field is populated with [RoleA], as expected
  18. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  19. Close the report
  20. In the "Select User" field, select [UserC]
  21. Click the [Display User(s)] button
  22. Validate the "User Display" report generates successfully and in a timely manner
  23. Validate the "User ID" field is populate with [UserC]
  24. Validate the "User Description" field is populated as expected
  25. Validate the "Associate With User Role" field is set to "Yes"
  26. Validate the "User Role" field is populated with [RoleB], as expected
  27. Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
  28. Close the report
Importing Images in Forms
Scenario 1: Validate Images imported and submitted in a forms
Specific Setup:
  • Have a form that contains a "Primary" and a "Multiple Iteration" section, with each section containing a "Picture" field and any other desired fields.
  • Have "Autosave" is enabled on the form
  • Have three image files(for example ".JPG" images) available for import, [ImageA], [ImageB] and [ImageC]
  • A client [TestClient], is admitted in an active episode
Steps
  1. Open the form
  2. Select [TestClient] and then select the episode
  3. Select the primary section of the form
  4. Navigate to the "Picture" field and import [ImageA]
  5. Populate any other desired fields in the section
  6. Navigate to the multiple-iteration section of the form
  7. Click [Add] to add a row [Row1]
  8. Navigate to the "Picture" field and import [ImageB]
  9. Populate any other desired fields
  10. Click [Add] to add another row [Row2]
  11. Navigate to the "Picture" field and import [ImageC]
  12. Populate any other desired fields
  13. Wait for "Autosave" to automatically trigger or click the [Backup] button
  14. Validate an "Autosave" message is displayed indicating the time of the backup
  15. Close the form
  16. Open the form
  17. Select [TestClient] and then select the episode
  18. Validate a message displays: "You have an unsubmitted backup of this data record. Do you wish to restore from the backup?"
  19. Click [Yes]
  20. Navigate to primary section of the form
  21. Validate the "Picture" field is populated with [ImageA]
  22. Validate all other fields are populates as expected
  23. Navigate to the multiple-iteration section of the form
  24. Select [Row1]
  25. Validate the "Picture" field is populated with [ImageB]
  26. Validate all other fields are populated as expected
  27. Select [Row2]
  28. Validate the "Picture" field is populated with [ImageC]
  29. Validate all other fields are populated as expected
  30. Click [Submit]
  31. Validate the form files successfully
  32. Return to the form
  33. Select [TestClient] and then select the episode
  34. Navigate to primary section of the form
  35. Validate the "Picture" field is populated with [ImageA]
  36. Validate all other fields are populates as expected
  37. Navigate to the multiple-iteration section of the form
  38. Select [Row1]
  39. Validate the "Picture" field is populated with [ImageB]
  40. Validate all other fields are populates as expected
  41. Select [Row2]
  42. Validate the "Picture" field is populated with [ImageC]
  43. Validate all other fields are populates as expected
  44. Close the form
Topics
• Modeling • NX • Chart Review • Forms • Envelope Import • User Definition • User Role Definition • Auto Save
2022 Update 121 Summary | Details
'Client Merge' process
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Documentation Form
  • Admission
Scenario 1: Validate 'Client Merge' for clients with appointments linked via Service Documentation to CWS modeled forms
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A second client is enrolled in an existing episode and has the same name as "Client A" (Client B).
  • A CWS modeled form configured for service documentation must be defined with a 'Draft/Final' field (Service Documentation Form).
  • The 'Attach Selected Appointment To Service Documentation On Draft' registry setting is set to "1" or "2".
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Right click in any available time slot and click [Add Appointment].
  3. Select "Client A" in the 'Client' field.
  4. Populate any other required and desired fields.
  5. Click [Submit].
  6. Validate the appointment for "Client A" is displayed.
  7. Click [Dismiss].
  8. Select "Client A" and access the "Service Documentation Form".
  9. File an existing appointment note for the appointment filed in the previous steps.
  10. Select "Draft" in the 'Draft/Final' field.
  11. Click [Submit].
  12. Access the 'Client Merge' form.
  13. Select "Client A" in the 'Source Client' field.
  14. Select "Client B" in the 'Target Client' field.
  15. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
  16. Select "Yes" in the 'Create New Episode On Merge' field.
  17. Click [File].
  18. Validate a message is displayed stating: Do you wish to continue with the indicated action?
  19. Click [Yes].
  20. Validate a message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
  21. Click [OK] and close the form.
  22. Select "Client B" and access the 'Service Documentation Form'.
  23. Select the new episode created on merge.
  24. Validate the note filed in the previous steps is displayed in the Pre-Display.
  25. Click [Edit].
  26. Validate all previously filed data is displayed.
  27. Close the form.
Topics
• Scheduling Calendar • Client Merge
2022 Update 128 Summary | Details
Dynamic Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Member Enrollment
Scenario 1: Dynamic Form - Validations
Specific Setup:
  • User has access forms, "Basic Troubleshooting", "Treatment Plan" and "Member Enrollment"
Steps
  1. Open form "Basic Troubleshooting"
  2. Click the [Test Dynamic Forms] button
  3. Validate message "Test Successful", is displayed
  4. Click the [OK] button
  5. Set the "Duration (minutes)" field to "1"
  6. Click the [Submit] button
  7. Verify the message window "Submitting... Please Wait", is displayed
  8. Wait "1" Minute
  9. Verify the message window "Submitting... Please Wait" closes and the user is returned to the home screen
  10. Open the "Treatment Plan" form and select the desired client in the "Select Client" search field
  11. Populate the "Plan Date" field
  12. Populate any other desired fields
  13. Set the "Draft/Final" to "Draft"
  14. Click the Launch Plan button
  15. Click the [Add New Problem] button
  16. Click the [Return to Plan] button
  17. Validate the "Plan Saved" message is displayed and click [OK]
  18. Set the "Draft/Final" field to "Final"
  19. Click [Submit]
  20. Validate the message "Cannot finalize plan until the following required fields are completed"
  21. Click the OK button
  22. Populate any missing required fields
  23. Click the [Submit] button
  24. Validate the form files successfully
  25. Open the Member Enrollment - Avatar MSO / Membership Management form
  26. Populate the "Last Name" field with a name that is not on file yet as a member
  27. Populate the "First Name" field
  28. Populate the Sex" field
  29. Click the Search button
  30. Validate the message "Search Results - No Matches found", is displayed
  31. Click [OK] button
  32. Click the New Client button
  33. Click the Auto Assign ID Number - Yes button
  34. Validate the "Name" field is populated as expected
  35. Populate any other desired fields
  36. Submit the form
  37. Validate the form files successfully
Topics
• Forms • Cache
2022 Update 140 Summary | Details
Console Widget Viewer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Last Movement
  • Admission
Scenario 1: "Console" Widgets - View form data in the "Console Widget Viewer"
Specific Setup:
  • Have a client already admitted in four active episodes. [Ep1], [Ep2], [Ep3] and [Ep4]
  • In form "Console Widget Configuration" create a console widget for an episodic based form [WAdmit]. For this test, an "Admission" form widget is used
  • The logged in user has access to form "Delete Last Movement"
  • The logged in user has the console widget [WAdmit] and the "Console Widget Viewer" widget on their home view or on an additional view
Steps
  1. At the home view, select the client
  2. In the "Episode" selection field on the menu bar, select "All Episodes"
  3. Refresh the [WAdmit] widget
  4. Validate rows for all four episodes are displayed
  5. Click the [View] button for each episode row
  6. Validate the "Console Widget Viewer" displays the expected data for each episode
  7. Open form "Delete Last Movement"
  8. Select [Ep2]
  9. Complete and submit the form
  10. Repeat step 2 for [Ep3]
  11. Refresh the [WAdmit] widget
  12. Validate only admission rows for [Ep1] and [Ep4] are present
  13. Click the [View] button for each row
  14. Validate the "Console Widget Viewer" displays the expected data for each episode
  15. Select the client and open the "Admission" form
  16. Populate all the required fields to admit the client to any program to create a new episode [Ep5]
  17. Submit the form
  18. Validate the form files successfully
  19. Repeat step 5, admitting the client to any other program to create another episode [Ep6]
  20. At the home view, select the client
  21. In the "Episode" selection field on the menu bar, select "All Episodes"
  22. Refresh the [WAdmit] widget
  23. Validate rows for [Ep2] and [Ep3] are not present as expected
  24. Validate rows for [Ep1], [Ep4] are present
  25. Validate the two new episode admission for [Ep5] and [Ep6] are also present
  26. Click the [View] button for each episode row in the widget
  27. Validate the "Console Widget Viewer" displays the expected data for each episode
Scenario 2: "All Documents" Widget - View form data in the "Console Widget Viewer"
Specific Setup:
  • Have a client already admitted in four active episodes. [Ep1], [Ep2], [Ep3] and [Ep4]
  • Have an episodic form included in the "All Documents" widget. For this test, the "Admission" form is used
  • The logged in user has the "All Documents" widget and the "Console Widget Viewer" widget on their home view or an additional view
  • The logged in user has access to the "Delete Last Movement" and the "Admission" forms
Steps
  1. At the home view, select the client
  2. In the "Episode" selection field on the menu bar, select "All Episodes"
  3. Navigate to the "All Documents" Widget
  4. Select the "Admission" form from the "Form Description" column form list
  5. Validate rows for all four episodes are displayed
  6. Click the [View] button for each episode row
  7. Validate the "Console Widget Viewer" displays the expected data for each episode
  8. Open form "Delete Last Movement"
  9. Select [Ep2]
  10. Complete and submit the form
  11. Repeat step 2 for [Ep3]
  12. At the home view, select the client
  13. In the "Episode" selection field on the menu bar, select "All Episodes"
  14. Navigate to the "All Documents" Widget
  15. Select the "Admission" form from the "Form Description" column form list
  16. Validate only admission rows for [Ep1] and [Ep4] are present
  17. Click the [View] button for each episode row
  18. Validate the "Console Widget Viewer" displays the expected data for each episode
  19. Select the client and open the "Admission" form
  20. Populate all the required fields to admit the client to any program to create a new episode [Ep5]
  21. Submit the form
  22. Validate the form files successfully
  23. Repeat step 7, admitting the client to any other program to create another episode [Ep6]
  24. At the home view, select the client
  25. In the "Episode" selection field on the menu bar, select "All Episodes"
  26. Navigate to the "All Documents" Widget
  27. Select the "Admission" form from the "Form Description" column form list
  28. Validate rows for [Ep2] and [Ep3] are not present as expected
  29. Validate rows for [Ep1], [Ep4] are present
  30. Validate the two new episode admission for [Ep5] and [Ep6] are present
  31. Click the [View] button for each episode row in the widget
  32. Validate the "Console Widget Viewer" displays the expected data for each episode
Topics
• Console Widget • Console Widget Configuration • NX • All Documents Widget
Update 141 Summary | Details
Product Updates - form compiles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (PM)
Scenario 1: "Product Updates" form - Post installation validations
Steps
  • Internal testing only
Product Update - On hold
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (CWS)
  • Product Updates (PM)
Scenario 1: Product Updates - Validate the "Guardiant" product update check functionality
Steps
  • Internal testing only
Topics
• Forms • Guardiant
2022 Update 142 Summary | Details
Product Updates - form compiles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (PM)
  • Print Error Log (PM)
Scenario 1: 'Product Updates' Form - Installation and post installation validations
Specific Setup:
  • Have a system where a product update [TestUpdate] will be installed that compile a form or forms. For example an update that will require compiling "Modeled" forms.
Steps
  1. Open form "Product Updates"
  2. Click [Select Application]
  3. Select the desired application
  4. Click [Select Update/Customization Pack]
  5. Browse to the location containing the ".GSA" file for [TestUpdate]
  6. Click [OK]
  7. Click [Review Update/Customization Pack Contents]
  8. Validate the results in the "Review Update/Customization Pack Contents" text box are as expected for the update being loaded
  9. Click [Install Update Customization Pack]
  10. Validate message "Update Loaded" is displayed
  11. Click [OK]
  12. Close the form
  13. Open form "Current Server" in application the update was installed in
  14. Navigate to the "Updates" list section
  15. Click the search text editor icon
  16. In the update listing search for the update installed in step 1
  17. Validate the update is found, as expected
  18. Close the form
  19. Open form "Print Error Log"
  20. Select today's date
  21. Run the report
  22. Validate there are no errors
  23. Locate any form that may have been recompiled by the product update. For example a "Modeled" form
  24. Populate the fields on the form
  25. Submit the form
  26. Validate the form files successfully
  27. Return to the form
  28. Select the row just submitted
  29. Validate all fields are populated, as expected
Topics
• Update Install • NX