Skip to main content

RADplus 2024 Monthly Release 2024.01.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 29 Summary | Details
Document Routing - Approval Comments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Registry Settings (PM)
  • Clinical Document Viewer
  • Ambulatory Progress Notes
Scenario 1: Document Routing Setup - Allow Comments During Approval set to "Yes" for modeled form
Specific Setup:
  • A client must be enrolled in an existing episode.
  • A modeled form is defined with the following (Form A):
  • Two scrolling free text fields (Field A & Field B)
  • A 'Draft/Final' field
  • Document routing enabled and "Yes" selected for 'Allow Comments During Approval'
  • Have two users for testing with associated practitioners (User A & User B).
  • Both users have the "My To Do's" widget on their home view.
Steps
  1. Log in as "User A".
  2. Select "Client A" and access "Form A".
  3. Populate all required and desired fields.
  4. Enter long text in "Field A" and "Field B".
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate the 'Confirm Document' dialog is displayed with the form details.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user and click [Verify].
  10. Select "User B" as an approver and click [Submit].
  11. Log out.
  12. Log in as "User B".
  13. Access the 'My To Do' widget.
  14. Locate the 'To Do' that was previously sent from 'Documents to Sign'.
  15. Click [Review] and [Accept].
  16. Enter any value in the 'Approval Comments' field.
  17. Click [Sign].
  18. Enter the logged in user's password in the 'Verify Password' field.
  19. Click [Verify].
  20. Validate the 'To Do' has been removed.
  21. Access the 'Clinical Document Viewer' form.
  22. Select "Client" in the 'Select Type' field.
  23. Select "Individual" in the 'Select All or Individual Client' field.
  24. Select "Client A" in the 'Select Client' field.
  25. Click [Process].
  26. Validate the finalized record for "Form A" is displayed and select it for viewing.
  27. Validate the data filed in the previous steps is displayed as expected, with the 'Approval Comments' appended to the end of the document.
  28. Click [Close All Documents] and close the form.
The 'Event Log Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Event Log Report
  • Crystal Report Viewer
Scenario 1: Event Log Report - 'All' Event Types and Categories
Steps
  1. Access the 'Event Log Report' form.
  2. Enter the current date in the 'Start Date' and 'End Date' fields.
  3. Enter the desired value in the 'Start Time' field to include the event in the setup.
  4. Click [End Time - Current Time].
  5. Select "All Event Types" in the 'All Event Types or Selected' field.
  6. Select "All Categories" in the 'All Categories or Selected' field.
  7. Select "Ascending" in the 'Data Sort' field.
  8. Click [View Event Log].
  9. Validate the report opens up in a new window.
  10. Click 'Events Sorted By User ID'.
  11. Validate the report displays as expected and is filtered by User ID.
  12. Validate the 'IP Address' field is populated with the user's IP Address.
  13. Close the report and the form.
Topics
• Modeling • Document Routing • Clinical Document Viewer • To-Do's • My To Do's • Approval Comments • Query/Reporting
Update 33 Summary | Details
Product Updates
Scenario 1: Validate accessabilty to the "Product Updates" form based on system configuration
Steps
  1. Internal Testing Only
Topics
• Update Install
Update 34 Summary | Details
Document Management Dictionary Update
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ProviderConnect File Attach
Scenario 1: 'Provider File Attach' - Verification of Document Conversion (From 'ProviderConnect File Attach' Source)
Steps
  • Internal Testing Only
'Provider File Attach' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Provider File Attach
Scenario 1: 'Provider File Attach' - Form Verification
Specific Setup:
  • Document Management Configuration must be defined for Cache Server or Perceptive (via Avatar PM / RADplus Utilities 'Document Management Defaults' form)
  • Dictionary Codes may optionally be defined for 'Other Tabled Files' Data Element '(70007) Document Type' (via Avatar MSO 'Dictionary Update' form)
  • 'Provider File Attach' Widget may optionally be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
  • Clinical Document Viewer/Document Management/All Documents Widgets may optionally be assigned to Chart View Definition/Home View Definition/Client Dashboard View assigned to user (via 'View Definition' form / 'NX View Definition' form)
  • One or more .PDF (Adobe Portable Document Format) and/or .TIF (Tagged Image File Format) files for Provider File Attach upload/storage
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar MSO 'Provider File Attach' form (under 'Avatar MSO / Provider Management' menu).
  2. Enter/select 'Member ID' value.
  3. Enter/select 'Provider' value.
  4. In 'File Type' field, ensure the following selections are available:
  5. 'Authorization' (will link File Attachment to a specific Avatar MSO Service Authorization record for selected Provider)
  6. 'Provider' (will link File Attachment to selected Provider)
  7. 'Other' (will link File Attachment to selected Provider)
  8. Select 'File Type' value (and 'Authorization' field value if applicable).
  9. Select 'Document Type' value and/or enter 'Comments' value if desired.
  10. Click 'Upload File' button, and select file for Provider Attachment upload/storage.
  11. On completion of File Attachment upload, ensure 'File Name' field is populated with uploaded file name.
  12. Click 'Store File' field to store File Attachment in Avatar MSO; ensure user is presented with confirmation dialog noting 'File successfully created'.
  13. Click 'OK' button to return to 'Provider File Attach' form.
  14. Select 'File Type' value for previously uploaded/stored File Attachment.
  15. Ensure uploaded/stored File Attachment files are listed/available for selection in the 'Existing Files' field.
  16. Close 'Provider File Attach' form.
  17. Navigate to Home View, Chart View or Client Dashboard View where Avatar MSO 'Provider File Attach' Widget is assigned/present
  18. Ensure that the 'Provider File Attach' Widget displays all uploaded/stored File Attachment files for selected/currently active Member ID/Client (one row in Widget display per File Attachment).
  19. Navigate to Home View, Chart View or Client Dashboard View where one or more myAvatar Clinical Document Viewer/Document Management/All Documents Widgets is/are assigned/present
  20. Ensure that the Clinical Document Viewer/Document Management/All Documents Widget displays all uploaded/stored File Attachment files where expected for selected/currently active Member ID/Client, including 'Form Name' value of 'Provider Document'.
  21. Open Crystal Reports or other SQL reporting tool.
  22. In Avatar PM/Avatar MSO SQL table 'DOCM.document_image', ensure that all uploaded/stored Provider File Attachment files are present in SQL table data (one row per File Attachment); ensure that 'formID' value for Provider File Attachment records is 'PCON' ('Provider Document').
  23. Note - As 'formID' is used for 'Form Name' display in Clinical Document Viewer/Document Management/All Documents Widgets; on installation of RADPlus 2024 Update 34, all existing Provider File Attach related Document Management rows will be updated with 'formID' value 'PCON'
  24. In Avatar MSO SQL table 'SYSTEM.file_attach_object', ensure that all uploaded/stored Provider File Attachment files are present in SQL table data (one row per File Attachment).
  25. In Avatar MSO SQL table 'SYSTEM.file_attach_comments', ensure that all uploaded/stored Provider File Attachment 'Comments' field entries are present in SQL table data (one row per 'Comments' entry).
Topics
• System Maintenance • Document Management
Update 41 Summary | Details
Progress Notes - Error handling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Clinical Document Viewer
  • Create New Progress Notes Form
  • Progress Notes (Group and Individual) 6
Scenario 1: Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Progress Notes (Group and Individual)" form.
Steps
  1. Open the "Progress Notes (Group and Individual)" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the "Progress Notes (Group and Individual)" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the "Progress Notes (Group and Individual)" form.
  13. Create and route a note to multiple approvers.
  14. Sign on as the first approver.
  15. Locate the document in the approver's "My To Do's" widget.
  16. Click on "Approve Document".
  17. Click "Accept".
  18. Enter the approver's password.
  19. Log on as another approver.
  20. Locate the document in the approver's "My To Do's" widget.
  21. Click on "Approve Document".
  22. Click "Accept".
  23. Enter the approver's password.
  24. Open the "Clinical Document Viewer" form.
  25. Select the document that was just routed/finalized.
  26. Validate that the document displays and prints.
  27. Open the "Progress Notes (Group and Individual)" form.
  28. Create a progress note and route to several approvers.
  29. Log on as another approver.
  30. Locate the document in the approver's "My To Do's" widget.
  31. Click on "Approve Document".
  32. Click "Accept".
  33. Enter the approver's password.
  34. Repeat steps 11b-12c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Scenario 2: Copy of Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
  • A new copy of the progress note form is created using "Create New Progress Note" form.
  • Document routing is enabled for the copy of the "Progress Notes (Group and Individual)" form.
Steps
  1. Open the copy of the "Progress Notes (Group and Individual)" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the copy of the "Progress Notes (Group and Individual)" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the copy of the "Progress Notes (Group and Individual)" form.
  13. Sign on as the first approver.
  14. Locate the document in the approver's "My To Do's" widget.
  15. Click on "Approve Document".
  16. Click "Accept".
  17. Enter the approver's password.
  18. Log on as another approver.
  19. Locate the document in the approver's "My To Do's" widget.
  20. Click on "Approve Document".
  21. Click "Accept".
  22. Enter the approver's password.
  23. Open the "Clinical Document Viewer" form.
  24. Select the document that was just routed/finalized.
  25. Validate that the document displays and prints.
  26. Open the copy of the "Progress Notes (Group and Individual)" form.
  27. Create a progress note and route to several approvers.
  28. Log on as another approver.
  29. Locate the document in the approver's "My To Do's" widget.
  30. Click on "Approve Document".
  31. Click "Accept".
  32. Enter the approver's password.
  33. Repeat steps 12-13 for each additional approver.
  34. Open "Clinical Document Viewer".
  35. Validate the document that was just filed display and prints.
Document Management Definition - Deleting form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Progress Notes (Group and Individual)
  • Clinical Document Viewer
Scenario 1: Document Management Definition - Add/Delete a document
Steps
  1. Open "Document Management Definition".
  2. Add a new form, populating all required fields.
  3. File the form to submit data.
  4. Open "Document Management Definition".
  5. Validate the new form is added.
  6. Click [Delete].
  7. File the form.
  8. Open "Document Management Definition".
  9. Search for the form that was just deleted, but it's no longer there.
Scenario 2: Document Management Definition - Add/Delete with Multiple Root System Codes
Specific Setup:
  • This must be tested in a system that has multiple root system codes.
Steps
  1. Open "Document Management Definition".
  2. Add a new form, populating all required fields.
  3. File the form to submit data.
  4. Open "Document Management Definition".
  5. Validate the new form is added.
  6. Close the form.
  7. Sign onto a system code that is not the main root system code.
  8. Using the "Progress Notes (Group and Individual)" form.
  9. Create and finalize a progress note for an individual.
  10. Finalize the note and route it to one or more additional approvers.
  11. Log on as the additional approvers and approve the note.
  12. Once the final approver has approved the note, sign off and back onto the main root system code.
  13. Open "Document Management Definition".
  14. Attempt to delete the form that was just added in a previous step.
  15. Validate it won't allow you to delete the form type because there are client forms on file.
Topics
• Progress Notes • Progress Notes (Group And Individual) • Document Management
Update 43 Summary | Details
"System Security Defaults" form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • System Security Defaults
  • Microsoft Outlook Calendar
Scenario 1: System Security Defaults - 'Outlook 365 Integration Configuration' setting validations
Specific Setup:
  • The "Microsoft Azure" cloud computing platform or similar platform has been setup by the client's system administrators to integrate with "Microsoft 365", to provide the "Microsoft Outlook" application to users
  • "Microsoft Outlook 365" integration certificate values : "Client ID", "Client Secret" and "Tenant ID", have been generated by the client's system administration and provided to the logged in user
  • Logged in user has access to form, "Registry Settings" and form "System Security Defaults"
Steps
  1. Open form "Registry Settings"
  2. Search for registry setting "Enable Outlook 365 Integration"
  3. Entering a value of "Y" in the "Registry Settings Value" field will:
  4. Enable support for "Outlook 365 Integration" in the system
  5. Create a new section in form "System Security Defaults", called "Outlook 365 Integration Configuration", where integration certificate values may be entered and submitted
  6. Entering a value of "N" in the "Registry Settings Value" field will:
  7. Disables support for "Outlook 365 Integration" in the system
  8. Removes section "Outlook 365 Integration Configuration" in form "System Security Defaults"
  9. Set the value in the "Registry Settings Value" field to a value other than "Y" or "N"
  10. Validate the error message "The selected value is not valid in the current system code for the following reason: Valid values are Y or N", is displayed
  11. Set the value in the "Registry Settings Value" field to "Y"
  12. Validate the value is accepted
  13. Submit the form
  14. Validate the form files successfully
  15. Click "Yes" to return to the form
  16. Search for registry setting "Enable Outlook 365 Integration"
  17. Validate the "Registry Setting Value" is set to "Y", as expected
  18. Close the form
  19. Open form "System Security Defaults"
  20. Click section "Outlook 365 Integration Configuration"
  21. Click the "Enter Outlook 365 Integration Configuration" button
  22. Validate the "Outlook 365 Integration Configuration" dialog box is displayed
  23. Navigate to the "Client ID" field
  24. Enter a value greater than "100" characters
  25. Validate a message "The field name is too long, the maximum length is 100 characters"
  26. Click "OK"
  27. Enter a value less than "100" characters
  28. Validate the value is accepted
  29. Navigate to the "Client Secret" field
  30. Enter a value greater than "100" characters
  31. Validate a message "The field name is too long, the maximum length is 100 characters"
  32. Click "OK"
  33. Enter a value less than "100" characters and include a tilde '~' character
  34. Validate the value is accepted
  35. Navigate to the "Tenant ID"
  36. Enter a value greater than "100" characters
  37. Validate a message "The field name is too long, the maximum length is 100 characters"
  38. Click "OK"
  39. Enter a value less than "100" characters
  40. Validate the value is accepted
  41. Click [OK]
  42. Submit the form
  43. Validate submission is successful
  44. Return to the form "System Security Defaults"
  45. Select section "Outlook 365 Integration Configuration"
  46. Click the "Enter Outlook 365 Integration Configuration" button
  47. Validate the value in the "Client ID" field is as expected
  48. Validate the value in the "Client Secret" field is as expected, and includes the tilde '~' character displayed
  49. Validate the value in the "Tenant ID" field is as expected
  50. Click [Cancel]
  51. Click the "Enter Outlook 365 Integration Configuration" button again to return to the dialog
  52. In the "Client ID", Client Secret" and "Tenant ID" field, make a change to the value in each field
  53. Click [Cancel]
  54. Click the "Enter Outlook 365 Integration Configuration" button
  55. Validate the original value submitted are displayed not the value changed in step 3c, as expected
  56. In the "Client ID", Client Secret" and "Tenant ID" field, make a change to value in each field again
  57. Click [OK]
  58. Click [Submit] to file the form
  59. Return to the form "System Security Defaults"
  60. Select section "Outlook 365 Integration Configuration"
  61. Click the "Enter Outlook 365 Integration Configuration" button
  62. Validate the values in the "Client ID", "Client Secret" and "Tenant ID" fields, including any tilde '~' characters, are displayed as expected
  63. Open form "Registry Settings"
  64. Search for registry setting "Enable Outlook 365 Integration"
  65. Enter a value of "N" in the "Registry Settings Value" field
  66. Submit the form
  67. Validate the form files successfully
  68. Return to the form "System Security Defaults"
  69. Validate the section "Outlook 365 Integration Configuration", is not longer present on the form as expected
  70. Open form "Registry Settings"
  71. Search for registry setting "Enable Outlook 365 Integration"
  72. Enter a value of "Y" in the "Registry Settings Value" field
  73. Submit the form
  74. Validate the form files successfully
  75. Return to the form "System Security Defaults"
  76. Validate the section "Outlook 365 Integration Configuration", is now present on the form again, as expected
Topics
• System Security Defaults
Update 46 Summary | Details
The 'Age Display Format' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Admission (Outpatient)
  • Call Intake
  • Pre Admit
  • Family Registration
Scenario 1: Validate the 'Age Display Format' registry setting in the 'Client Header' and 'Client Information' widget
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Registry Settings' Form.
  2. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting Details' field contains: This registry setting accepts the values "1", "2", or "3", to customize the format of age across various forms and widgets, including 'Admission', 'Admission (OutPatient)', 'Family Registration', 'Pre Admit', 'Call Intake', 'Client Header', and the 'Client Information' widget. Selecting "1" enables a simplified age display, presenting only the clients' age in years across all specified forms and widgets. Selecting "2", a more detailed age field is made visible and the display of age only in years is hidden on the 'Admission', 'Admission (OutPatient)', 'Family Registration', 'Pre Admit' and 'Call Intake' forms. For clients older than three years, age is shown in months and years, while for those under three, age is shown in days, months, and years. Selecting "3" allows for clients under 3 years old to display their age in months, and those under 2 years to display their age in months and days. All clients aged 3 and above will display age in years only.
  5. Enter "1" in the 'Registry Setting Value' field.
  6. Submit the form.
  7. Select "Client A" and access the 'Admission' form.
  8. Click [Edit].
  9. Enter the desired value in the 'Date Of Birth' field.
  10. Submit the form.
  11. Select "Client A" and access the 'Client Information' widget.
  12. Validate the 'Age' field contains the client's age in years.
  13. Select "Client A" and access the 'Admission' form.
  14. Click [Edit].
  15. Validate the 'Client Header' displays the client's age in years.
  16. Close the form.
  17. Access the 'Registry Settings' Form.
  18. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  19. Click [View Registry Settings].
  20. Enter "2" in the 'Registry Setting Value' field.
  21. Submit the form.
  22. Select "Client A" and access the 'Client Information' widget.
  23. Validate the 'Age' field displays the client's age in:
  24. Months and years if the client is older than 3 years old.
  25. Months, years, and days if the client is under 3 years old.
  26. Select "Client A" and access the 'Admission' form.
  27. Click [Edit].
  28. Validate the 'Client Header' displays the client's age in:
  29. Months and years if the client is older than 3 years old.
  30. Months, years, and days if the client is under 3 years old.
  31. Close the form.
  32. Access the 'Registry Settings' Form.
  33. Enter the 'Age Display Format' in the 'Limit Registry Settings to the Following Search Criteria' field.
  34. Click [View Registry Settings].
  35. Enter "3" in the 'Registry Setting Value' field.
  36. Submit the form.
  37. Select "Client A" and access the 'Client Information' widget.
  38. Validate the 'Age' field displays the client's age in:
  39. Years if the client is older than 3 years old.
  40. Months if the client is between 2 and 3 years old.
  41. Months and days if the client is under 2 years old.
  42. Select "Client A" and access the 'Admission' form.
  43. Click [Edit].
  44. Validate the 'Client Header' displays the client's age in:
  45. Years if the client is older than 3 years old.
  46. Months if the client is between 2 and 3 years old.
  47. Months and days if the client is under 2 years old.
  48. Close the form.
Topics
• Registry Settings • Widgets • Client Header • NX
Update 54 Summary | Details
Entity-Based Document Capture - Client ID and Episode
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Staff Document Capture
  • Clinical Document Viewer
  • Entity-Based Document Capture
  • Batch Capture and Indexing
  • Chart Review
  • Client Document Capture
  • Document Capture
Scenario 1: Staff Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • There must be a practitioner defined (Practitioner A).
  • A document must exist for import.
Steps
  1. Access the 'Staff Document Capture' form.
  2. Enter "Practitioner A" in the 'Staff ID' field.
  3. Click [Launch POS Capture].
  4. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  5. Click [Import].
  6. Validate the 'Document Capture' opens in a new window.
  7. Select any value in the 'Document Type' field.
  8. Enter any value in the 'Document Description' field.
  9. Click [Capture] and [Browse].
  10. Locate the file to be imported and click [Open] and [Done].
  11. Validate the image displays.
  12. Click [Save].
  13. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Staff" in the 'Select Type' field.
  16. Select "Individual" in the 'Select All or Individual Staff' field.
  17. Select "Practitioner A" in the 'Select Staff' field.
  18. Click [Process].
  19. Locate and select the document that was saved in the previous steps.
  20. Validate the image displays.
  21. Click [Close All Documents], [Search] and [Close].
  22. Navigate back to the open 'Staff Document Capture' form.
  23. Click [Launch POS Capture].
  24. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?".
  25. Click [Import].
  26. Validate a second document capture window opens.
  27. Navigate back to the open 'Staff Document Capture' form.
  28. Click [Discard].
  29. Validate the document capture windows close and the form discards.
Scenario 2: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • In the "Document Management Defaults" form, select "Program" in the "Select Entity Types to Allow" field.
  • Select a performing provider and a program for the tests.
Steps
  1. Access the 'Entity-Based Document Capture' form.
  2. Select "Performing Provider" in the 'Entity Type' field.
  3. Enter the desired performing provider in the 'Entity' field in the format of "LAST,FIRST".
  4. Validate the 'Results' field displays the performing provider and select it.
  5. Click [Launch POS Capture].
  6. Import in a document saved as a file on the server.
  7. Validate the document renders on screen.
  8. Select the desired value in the 'Document Type' field.
  9. Enter the desired value in the 'Document Description' field.
  10. Click [Save].
  11. Validate that messages display indicating the document was successfully saved.
  12. Close the form.
  13. Access the 'Clinical Document Viewer' form.
  14. Select "Performing Provider" in the 'Entity' field.
  15. Select "Individual" in the 'Select All or Individual Performing Provider' field.
  16. Select the performing provider from the previous steps in the 'Select Performing Provider' field.
  17. Click [Process].
  18. Validate a row was added for the document that was just saved.
  19. View the document to validate it displays as it was captured.
  20. Close the form.
  21. Access the 'Entity-Based Document Capture' form.
  22. Select "Program" in the 'Entity Type' field.
  23. Enter the desired program in the 'Entity' field.
  24. Validate the 'Results' field displays the program and select it.
  25. Click [Launch POS Capture].
  26. Import in a document saved as a file on the server.
  27. Validate the document renders on screen.
  28. Select the desired value in the 'Document Type' field.
  29. Enter the desired value in the 'Document Description' field.
  30. Click [Save].
  31. Validate that messages display indicating the document was successfully saved.
  32. Close the form.
  33. Access the 'Clinical Document Viewer' form.
  34. Select "Program" in the 'Entity' field.
  35. Select "Individual" in the 'Select All or Individual Performing Program' field.
  36. Select the program from the previous steps.
  37. Click [Process].
  38. Validate a row was added for the document that was just saved.
  39. View the document to validate it displays as it was captured.
  40. Close the form.
Scenario 3: Perceptive Batch Capture and Indexing - JxBrowser enabled
Specific Setup:
  • Perceptive storage method must be utilized.
Steps
  1. Open the "Batch Capture and Indexing" form.
  2. Click "Capture" to create a new batch.
  3. Choose "Scanner" for the "Source".
  4. Click "Open Batch".
  5. Scan a document
  6. If Batch Verify is utilized, then click "Send To".
  7. If Batch Verify is not utilized, then click "Submit".
  8. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  9. Select the batch that was sent to this queue.
  10. Open the batch and click "Submit".
  11. Close form.
  12. Open the "Batch Capture and Indexing" form.
  13. Click "Capture" to create a new batch.
  14. Choose "File" for the "Source".
  15. Click "Browse" and browse to the location of where the file is stored on the server.
  16. Click "Open".
  17. Click "Open Batch".
  18. If Batch Verify is utilized, then click "Send To".
  19. If Batch Verify is not utilized, then click "Submit".
  20. If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
  21. Select the batch that was sent to this queue.
  22. Open the batch and click "Submit".
  23. Close form.
  24. Open "Chart Review" form for the client and episode that the documents were just scanned and imported for.
  25. Navigate to the form/category that you want to validate.
  26. Select a document that was scanned in.
  27. Validate that the document displays.
  28. Click the "Print" button.
  29. Print the document.
  30. Validate that the printed document matches what displayed on the viewer.
  31. Select a document that was imported in.
  32. Validate that the document displays.
  33. Click the "Print" button.
  34. Print the document.
  35. Validate that the printed document matches what displayed on the viewer.
  36. Open "Clinical Document Viewer".
  37. Validate you can view and print both the scanned and imported document.
Scenario 4: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: 'Save Was Successful.' and 'Document Added to Avatar!'
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select 'Individual' in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Topics
• Perceptive • Document Capture
Update 56 Summary | Details
Treatment Plan - PCL Date fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Registry Settings (PM)
  • Required User List Management
Scenario 1: Treatment Plan - Validate 'Pending Approval' workflow with PCL date fields
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • Two users must be defined with associated staff members (User A & User B).
  • "User A" and "User B" must be defined as workflow users in the 'Required User List Management' form for the 'Treatment Plan'.
Steps
  1. Log into Avatar NX as "User A".
  2. Select “Client A” and access the ‘Treatment Plan’ form.
  3. Enter the desired date in the 'Plan Date' field.
  4. Enter any value in the 'Plan Name' field.
  5. Select any value in the ‘Plan Type’ field.
  6. Enter the desired date in the 'Plan End Date' field.
  7. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  8. Select "Draft" in the 'Treatment Plan Status' field.
  9. Click [Launch Plan].
  10. Add a problem, goal, objective, and intervention.
  11. Populate all required and desired fields.
  12. Click [Return to Plan] and [OK].
  13. Select "Pending Approval" in the 'Treatment Plan Status' field.
  14. Click [Submit].
  15. Validate that a "Confirm Document" message is displayed.
  16. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are not displayed.
  17. Click [Accept and Route].
  18. Validate a "Verify Password" message is displayed.
  19. Enter the password associated with the logged-in user in the 'Password' field.
  20. Click [Verify].
  21. Select the practitioner associated to "User A" as an approver and the practitioner associated to "User B" as an approver/supervisor.
  22. Click [Submit].
  23. Log out.
  24. Log into Avatar NX as "User B".
  25. Navigate to the 'My To Do's' widget.
  26. Click [Documents to Sign].
  27. Validate the To Do for "Client A" is displayed.
  28. Click [Review].
  29. Validate the 'Document Preview' contains the treatment plan data, without the 'PCL End Date' and 'PCL Finalized Date' fields.
  30. Click [Accept] and [Sign].
  31. Validate a "Verify Password" message is displayed.
  32. Enter the password associated with the logged-in user in the 'Password' field.
  33. Click [Verify].
  34. Validate the To Do for "Client A" is no longer displayed.
  35. Log out.
  36. Log into Avatar NX as "User A".
  37. Navigate to the 'My To Do's' widget.
  38. Click [Documents to Sign].
  39. Validate the To Do for "Client A" is displayed.
  40. Click [Review].
  41. Validate the 'Document Preview' contains the treatment plan data.
  42. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are appended to the end of the document. If there are multiple approvers, these fields will only become visible when the last approver goes to approve the document.
  43. Click [Accept] and [Sign].
  44. Validate a "Verify Password" message is displayed.
  45. Enter the password associated with the logged-in user in the 'Password' field.
  46. Click [Verify].
  47. Validate the To Do for "Client A" is no longer displayed.
Scenario 2: Treatment Plan - Validate 'Final' workflow with PCL Date fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • The logged in user must have an associated practitioner.
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter any value in the 'Plan Name' field.
  4. Select any value in the ‘Plan Type’ field.
  5. Enter the desired date in the 'Plan End Date' field.
  6. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  7. Select "Draft" in the 'Treatment Plan Status' field.
  8. Click [Launch Plan].
  9. Add a problem, goal, objective, and intervention.
  10. Populate all required and desired fields.
  11. Click [Return to Plan] and [OK].
  12. Select "Final" in the 'Treatment Plan Status' field.
  13. Click [Submit].
  14. Validate that a "Confirm Document" message is displayed.
  15. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed in the body of the document.
  16. Click [Accept and Route].
  17. Validate a "Verify Password" message is displayed.
  18. Enter the password associated with the logged-in user in the 'Password' field.
  19. Click [Verify].
  20. Select the practitioner associated to the logged in user as an approver.
  21. Click [Submit].
  22. Navigate to the 'My To Do's' widget.
  23. Click [Documents to Sign].
  24. Validate the To Do for "Client A" is displayed.
  25. Click [Review].
  26. Validate the 'Document Preview' contains the treatment plan data, with the 'PCL End Date' and 'PCL Finalized Date' fields in the body of the document.
  27. Click [Accept] and [Sign].
  28. Validate a "Verify Password" message is displayed.
  29. Enter the password associated with the logged-in user in the 'Password' field.
  30. Click [Verify].
  31. Validate the To Do for "Client A" is no longer displayed.
Topics
• Treatment Plan • Document Routing
Update 57 Summary | Details
The 'Form Deletion' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • All Documents Widget Definition
  • All Documents Widget
  • Form Deletion (PM)
  • Table Deletion (PM)
  • Envelope Deletion (PM)
Scenario 1: 'All Documents Widget Definition' form
Specific Setup:
  • A modeled form has been deleted in the 'Form Deletion' form (Form A).
Steps
  1. Access the 'All Documents Widget Definition' form.
  2. Select "Add" in the 'Add or Edit Tab' field.
  3. Populate the required fields and click [File].
  4. Edit the tab that was just added.
  5. Validate that the tab displays as it was data entered.
  6. Click [Forms Assigned].
  7. Validate "Form A" is not displayed in the list.
  8. Navigate to the 'Multi-Document Tab' section.
  9. Select "Add" in the 'Add or Edit Tab' field.
  10. Populate the required fields and click [File].
  11. Edit the tab that was just added.
  12. Validate that the tab displays as it was data entered.
  13. Navigate to the 'Multi-Progress Notes Tab' section.
  14. Select "Add" in the 'Add or Edit Tab' field.
  15. Populate the required fields and click [File].
  16. Edit the tab that was just added.
  17. Validate the tab displays as it was data entered.
  18. Navigate to the 'All Documents Widget Definition' section.
  19. Select "Add" in the 'Add or Edit Widget' field.
  20. Validate the [New Row] and [Delete Row] buttons are enabled.
  21. Populate the required fields and click [File].
  22. Edit the widget that was just added.
  23. Validate the widget displays as the data was entered with dark grey text.
  24. Close the form.
'Form and Table Documentation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation
Scenario 1: Form and Table Documentation - "All Forms"
Steps
  1. Access the 'Form and Table Documentation' form.
  2. Select "Form" in the 'Type of Documentation' field.
  3. Select "All Forms" in the "Individual or All Forms" field.
  4. Click [Process]
  5. Validate "Option ID" is displayed on the report for all forms.
  6. Click [Close] and close the form.
Topics
• All Documents Widget Definition • Modeling • Forms
Update 59 Summary | Details
Avatar - RxConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Launch RxConnect
Scenario 1: Avatar "NIAM" user login - Verify "RxConnect" launch and login when "RXConnect" NIAM Login functionality "Disabled"
Specific Setup:
  • Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality configured by Netsmart.
  • RxConnect must be installed and configures to communicate with myAvatar
  • The "RxConnect" application is currently configured 'not' to allow login authentication via "NIAM"
  • An Avatar user has two types of login user ID's setup for logging into Avatar, that were set up in form "User Definition"
  • [UserIdA], a standard Avatar user with a password and assigned with the following setup
  • In "Select Forms for User Access"
  • The user is assigned form "Launch RxConnect" under the "Avatar PM" folder
  • Under the "RxConnect" folder the user is assigned an ' RxConnect' specific "Access" permission, for example "Pharmacist",
  • [UserIdB], a "NIAM" type user, configured with the following setup:
  • Field "User External Login" set to "Yes"
  • Field "External Login ID" is populated with the 'External login ID' assigned by a "(ODIC) Identity Provider". For example, provider "Okta".
  • In "Select Forms for User Access"
  • Assigned form "Launch RxConnect", located under the "Avatar PM" folder
  • Under the "RxConnect" folder, the user is assigned an 'RxConnect' specific "Access" permission. For example "Pharmacist"
Steps
  1. At the "Avatar" login screen, click "Login with Enterprise Credentials"
  2. At the "External Login Provider" screen, populate the "Netsmart ID" field with the "External login ID" assigned to [UserIdB] in the setup.
  3. At the Avatar login screen, select the "System" code to log into, from the "System" code field
  4. Enter the password assigned and validate login to Avatar is successful
  5. Search for and open the "Launch RxConnect" form
  6. Click the [Launch RxConnect] button
  7. Validate the "RxConnect" application is launched and the user is automatically logged in
  8. At the top of the screen under the menu's
  9. Validate the "User" field, indicates [UserIdB]
  10. Validate the "Access" field, indicates the access permission stated in the setup
  11. On the menu, click "Logout"
  12. Validate there is a user login and password prompt displayed now, in order to log back in:.
  13. In the "UserName" field, enter the [UserIdB] (the Avatar user set up for "NIAM" set with "RxConnect" access)
  14. In the "Password" field, enter any value or either leave it blank, as they don't get a standard password, as noted in the setup
  15. Click [Login]
  16. Validate access is denied with message, "UserID does not exist in any facilities or is not active in any facility.", as expected.
  17. In the "UserName" field, enter the [UserIdA] (the standard Avatar user set with "RxConnect" access).
  18. In the "Password" field, enter their assigned password
  19. Click [Login]
  20. Validate the user is logged in successfully, as expected
  21. Exit the application
Scenario 2: Avatar "NIAM" user login - Verify "RxConnect" launch and login when "RXConnect" NIAM Login functionality "Enabled"
Specific Setup:
  • Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality configured by Netsmart.
  • RxConnect must be installed and configures to communicate with myAvatar
  • The "RxConnect" application is currently configured to 'allow' login authentication via "NIAM" login
  • Have a user with an "External Login ID" and password assigned to them by a "(ODIC) Identity Provider", For example, provider "Okta".
  • In form "User Definition", a user ID has been defined for that user [UserId] and has the following configured settings:
  • Field "User External Login" set to "Yes"
  • Field "External Login ID" is populated with their assigned 'External login ID'
  • In "Select Forms for User Access"
  • In the "Avatar PM" folder, the user is assigned form "Launch RxConnect"
  • In the "RxConnect" folder the user is assigned an ' RxConnect' specific "Access" permission, for example "Pharmacist"
Steps
  1. At the "Avatar" login screen, Click "Login with Enterprise Credentials"
  2. At the "External Login Provider" screen, populate the "Netsmart ID" field with the external login ID assigned [UserId] and click [Next]
  3. At the Avatar login screen, select the "System" code to log into, from the "System" code field
  4. Validate login is successful into Avatar
  5. Search for and open the "Launch RxConnect" form
  6. Click the [Launch RxConenct] button
  7. Validate the "RxConnect" application is launched and the user is logged in
  8. At the top of the screen under the menu's
  9. Validate the "User" field, indicates [UserId]
  10. Validate the "Access" field, indicates the access permission stated in the setup
  11. On the menu, click "Logout"
  12. Validate there is just a [Login] button and no user login or password prompts
  13. Click [Login]
  14. Validate the user is automatically logged back in successfully
  15. Log out of the application
Topics
• RxConnect
Update 60 Summary | Details
Product Update installer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Global Data
Scenario 1: "Avatar" Monthly/Quarterly Release Methodology (Internal testing) - Validations
Steps
  1. Internal Testing Only
Topics
• Table • Cache • Update Install
2023 Update 104 Summary | Details
Report Definitions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition Export
  • Report Definition Deletion (PM)
  • Report Definition Import (PM)
Scenario 1: 'Report Definition': (MSE) Multi-Server Environment (Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have a "Report Definition" export file, exported from a system outside the current MSE testing systems. [ExternalReport]
  • As the testing user, have separate avatar session open for each system (BLD, UAT, and LIVE), and log in each environment
Steps
  1. In LIVE,
  2. Open form "Report Definition Import"
  3. Select [ExternalReport], the report definition exported from an external system, as noted in the setup
  4. Validate import is not permitted, with a message indicating that the report does not exist in BLD environment
  5. In BLD
  6. Open form "Report Definition Import"
  7. Select [ExternalReport], validate import is permitted
  8. Click to import the report
  9. Validate import is successful
  10. Open form "Report Definition Export"
  11. Select [ExternalReport]
  12. Export the report [ExternalReportExport] and save the file
  13. In LIVE
  14. Open form "Report Definition Import"
  15. Select [ExternalReportExport],
  16. Validate import is now permitted, now that it has been exported from BLD.
  17. Import the report
  18. Validate import is successful
  19. In BLD
  20. Open form "Report Definition" and create a new definition [ReportA] with two or more parameters
  21. Submit the report and validate submission is successful
  22. Open "Report Definition Export"
  23. Export the definition [ReportExportA] and save the file
  24. In one of the other systems, for this test LIVE is used
  25. Open form "Report Definition Import"
  26. Import [ReportExportA] as 'New'
  27. Validate import is successful
  28. In BLD
  29. Open "Report Definition" to edit [ReportA]
  30. Delete one of the existing parameters.
  31. Submit the form
  32. Return to "Report Definition"
  33. Create another new report definition with one or more parameters [ReportB]
  34. Submit the form and validate submission is successful
  35. Open "Report Definition" Export
  36. Select [ReportB] for export
  37. Validate export is successful [ReportExportB]
  38. In LIVE
  39. Open "Report Definition Import"
  40. Import [ReportExportB]
  41. Validate import is successful
  42. In BLD
  43. Open form "Report Definition Deletion"
  44. Select [ReportB]
  45. Validate a warning message indicating that deleting this report definition will also delete from the following Avatar instances via web service calls, LIVE, is displayed. Click [OK]
  46. Click the "Yes" check box to confirm deletion
  47. Click [Submit]
  48. Validate the "Report Definition Deletion Web Service Dialog", is presented and indicates "In addition to the current environment, this report definition has been deleted from the following environments: LIVE"
  49. Click [OK]
  50. Open "Report Definition"
  51. Search for [ReportB]
  52. Validate is not found, as expected. Close the form
  53. In LIVE
  54. Open "Report Definition"
  55. Validate [ReportB] cannot be found, as expected
  56. Close the form
  57. Open "Report Definition" Import
  58. Click [Select Report Import File] and select [ReportExportB]
  59. Validate a critical error preventing import is displayed, as the report definition does not exist in BLD yet since it was deleted in step 8
  60. In BLD
  61. Open "Report Definition Import"
  62. Click [Select Report Import File] and select [ReportExportB]
  63. Validate is import is successful
  64. In LIVE
  65. Open "Report Definition Import"
  66. Click [Select Report Import File] and select [ReportExportB]
  67. Validated is import is successful now, as the report exists in BLD
  68. Close the form
  69. In LIVE
  70. Re-open "Report Definition" Import
  71. Click [Select Report Import File] and select [ReportExportB] again as "New"
  72. Validate is import is blocked, with message "This report already exists within this system. New copies must be created in the BLD environment first, then moved to the other environments"
  73. Open "Report Definition Export""
  74. Select [ReportB] for export
  75. Validate export is blocked with the following message "This form is not accessible in this environment"
  76. Click [OK] and close the form
  77. In BLD, repeat step 12b
  78. Export the file
  79. Validate export from BLD is successful, as expected
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Definition (MSO)
  • Envelope Definition (MSO)
  • Table Definition (MSO)
Scenario 1: 'Modeling ': (MSE) Multi-Server Environment (Modeled Form "Create/Export/Import/Delete") - Validations
Specific Setup:
  • Have three systems, each set up initially with identical databases
  • Configured to communicate with each other over the network in a (MSE) Multi-Server Environment
  • One configured as BLD, one configured as UAT, one configured as LIVE
  • Have an existing envelope [TestEnvelope] containing a form [TestForm], that exists in BLD and also existing in ether UAT or LIVE. For this test UAT is used
  • [TestForm] contains one or more desired fields on the form, but does not yet contain a "Display" type section, a "Label" field or a 'Report" field
  • In BLD, open form "Form Definition" to edit [TestForm]
  • In the existing main section, add a "Label" and a "Report" object
  • Now add a new section, and choose 'Display' as the type of section.
  • Submit the form and validate submission is successful
  • As the testing user, open a separate avatar session for each system (BLD, UAT, and LIVE), and log in
Steps
  1. In BLD
  2. Open form "Envelope Export" and select [TestEnvelope]
  3. Export the envelope and save the export file in a desired location
  4. Validate export is successful
  5. Log into either LIVE or UAT. For this test UAT is used
  6. Open "Envelope Import" and import [TestEnvelope] as an overwrite
  7. Validate the import is successful
  8. In BLD,
  9. Open "Form Definition" and select [TestForm]
  10. Navigate the "Section Definition" section and delete the "Display" section
  11. Navigate to the "Object Definition" section and delete the "Label" and the "Report" fields
  12. Submit the form.
  13. Validate submission is successful
  14. Staying in BLD
  15. Create a new envelope in "Envelope Definition" [NewTestEnvelop]
  16. Create a new table in "Table Definition" [NewTestTable] with any desired field types
  17. Create a new form in "Form Definition" [NewTestForm], that includes the fields from the table
  18. Validate submissions are successful
  19. Open "Envelope Export"
  20. Export [NewTestEnvelope] and save the file
  21. In UAT
  22. Open "Envelope Import" and select [NewTestEnvelope] for import as 'New'
  23. Validate the import is successful
  24. Staying in UAT
  25. Open [NewTestForm] for any client
  26. Populate the fields and submit the form
  27. Validate submission is successful
  28. In BLD,
  29. Open form "Table Deletion"
  30. Select [NewTestTable]
  31. Validate a message " The selected table is used within one or more forms. It must be removed from all forms prior to deletion."
  32. Close the form
  33. Open form 'Table Definition' to edit [NewTestTable]
  34. Navigate to the "Column Definition" section
  35. Select one of the table columns and click "Delete" to remove it from the table
  36. Validate deletion is blocked, with a message "This field is in use in the following environments and cannot be deleted: UAT"
  37. Click [OK] and close the form
  38. Open form "Form Definition"
  39. Select [NewTestForm] for deletion
  40. Validate an error is displayed blocking submission indicating is there is data present in the form in UAT.
  41. Close the form
  42. In UAT
  43. Open form "NewTestForm"
  44. Select the row filed in step 4 in the pre-display
  45. Click [Delete] to remove the row
  46. In BLD
  47. Open form 'Form Deletion' and select [TestForm] for deletion
  48. Validate a message is displayed that contains "Deleting this form will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  49. Click [OK]
  50. At prompt "Are you sure that you want to delete this form", click the "Yes" checkbox
  51. Submit the form
  52. Validate the"Form Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  53. Click [OK]
  54. Validate submission is successful
  55. Open form "Table Deletion" and select [NewTestTable] for deletion
  56. Validate a message is displayed that contains "Deleting this table will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion?"
  57. Click [OK]
  58. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  59. Submit the form
  60. Validate the"Table Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this table has been deleted from the following environments: UAT
  61. Click [OK]
  62. Validate submission is successful
  63. Open form Envelope Deletion' and select [NewTestEnvelope] for deletion
  64. Validate a message is displayed that contains "Deleting this envelope will also delete from the following Avatar instances via web service calls: UAT Are you sure you want to continue with this deletion??"
  65. Click [OK]
  66. At prompt "Remove table from RADplus_audit_database_tables? ", select the desired response, "Yes" or "No"
  67. Submit the form
  68. At prompt "Are you sure that you want to delete this Envelope", click the "Yes" checkbox
  69. Submit the form
  70. Validate the"Envelope Deletion Web Service" dialog is displayed and contains message "In addition to the current environment, this form has been deleted from the following environments: UAT
  71. Validate submission is successful
  72. In UAT
  73. Open "Form Definition" and search for [NewTestForm]
  74. Validate the form is not found, as expected
  75. Open "Table Definition" and search for [NewTestTable]
  76. Validate the table is not found, as expected
  77. Open "Envelope Definition" and search for [NewTestEnvelope]
  78. Validate the envelope is not found, as expected
Modeled form - diagnosis fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Diagnosis
Scenario 1: Modeled Forms - Validate "Diagnosis History (ICD-10)" Table Alias field data
Specific Setup:
  • Have a Modeled form [TestForm], configured in 'Table Definition" to use the "Alias Table", "Diagnosis History (ICD10)"
  • [FieldA] is mapped to alias table column "Diagnoses Search (Row1)"
  • [FieldB] is mapped to alias table column "Diagnoses Search (Row2)"
  • [FieldC] is mapped to alias table column "Diagnoses Search (Row3)"
  • Have a client [TestClient] with up to three diagnosis, submitted in form "Diagnosis"
  • Diagnosis (Row1) in the form, is populated with diagnosis value [Diag1]
  • Diagnosis (Row2) in the form, is populated with diagnosis value [Diag2]
  • Diagnosis (Row3) in the form, is populated with diagnosis value [Diag3]
  • Have access to the "Diagnosis" form
Steps
  1. Open [TestForm]
  2. Select [TestClient]
  3. Navigate to the section of the form where the mapped diagnosis fields reside
  4. Validate [FieldA] is displayed with previous diagnosis [Diag1] submitted in the set up, as expected
  5. Validate [FieldB] is displayed with previous diagnosis [Diag2] submitted in the set up, as expected
  6. Validate [FieldC] is displayed with previous diagnosis [Diag3] submitted in the set up, as expected
  7. Navigate [FieldA]
  8. Search for and select a new diagnosis [NewDiag1]
  9. Navigate [FieldB]
  10. Search for and select a new diagnosis [NewDiag2]
  11. Navigate [FieldC]
  12. Search for and select a new diagnosis [NewDiag2]
  13. Submit the form
  14. Validate the form submits successfully
  15. Select [TestClient]
  16. Open form "Diagnosis"
  17. Navigate to the "Diagnoses" grid
  18. Double click to select Row ID "1"
  19. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag1], submitted in step 1c
  20. Double click to select Row ID "2"
  21. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag2], submitted in step 1d
  22. Double click to select Row ID "3"
  23. Validate the "Diagnosis Search" field is populated with diagnosis [NewDiag3], submitted in step 1e
  24. Close the form
Topics
• Report Definition Import • Modeling • Diagnosis
 

RADplus_2024_Monthly_Release_2024.01.02_Details.csv