Skip to main content

RADplus Client Update 2513-006 Acceptance Tests

  1. Last updated
  2. Save as PDF
AV-79270 Summary | Details
Document Routing - 'Add Members to Acknowledge' search field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Treatment Plan
Scenario 1: Document Routing - Sending and receiving "Acknowledgement" To-Do(s)
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 'Mental Status Assessment' 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 'Mental Status Assessment' form.
  2. Enter the desired date in the 'Assessing Date' field.
  3. Select any value in the 'Assessing Clinician' field.
  4. Enter any value in the 'Assessment Time' field.
  5. Select "Final" in the 'Assessment Status' field.
  6. Click [Submit] and [Accept and Route].
  7. Enter the password associated with "User A" and click [OK].
  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. Navigate to the 'My To Do's' widget.
  13. Validate there is a To-Do for the assessment filed in the previous steps.
  14. Click [Approve Document].
  15. Validate the 'Document Preview' contains the assessment data filed in the previous steps.
  16. Click [Accept].
  17. Enter the password associated with "User A" and click [OK].
  18. Validate the To-Do is no longer present.
  19. Log out.
  20. Login as "User B" and navigate to the 'My To Do's' widget.
  21. Validate there is a To-Do for the assessment filed in the previous steps.
  22. Click [Acknowledge Document] and [Acknowledge].
  23. Enter the password associated with "User B" and click [OK].
  24. Validate the To-Do is no longer present.
Scenario 2: 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 3: Treatment Plan - 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 'Treatment Plan' 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 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select any value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Click [Add New Problem].
  7. Populate any required and desired fields.
  8. Click [Return to Plan] and [OK].
  9. Select "Final" in the 'Treatment Plan Status' field.
  10. Click [Submit] and [Sign and Route].
  11. Enter the password associated with "User A" and click [OK].
  12. Enter the practitioner associated to "User A" in the 'Add Approver' field and click [Add].
  13. Verify the 'Add Members to Acknowledge' field is present.
  14. Search for the practitioner associated to "User B" using only one letter in the 'Add Members to Acknowledge' field.
  15. Click [Add] and [Submit].
  16. Close the form.
  17. Navigate to the 'My To Do's' widget.
  18. Validate there is a To-Do for the treatment plan filed in the previous steps.
  19. Click [Approve Document].
  20. Validate the 'Document Preview' contains the treatment plan data filed in the previous steps.
  21. Click [Accept].
  22. Enter the password associated with "User A" and click [OK].
  23. Validate the To-Do is no longer present.
  24. Log out.
  25. Login as "User B" and navigate to the 'My To Do's' widget.
  26. Validate there is a To-Do for the treatment plan filed in the previous steps.
  27. Click [Acknowledge Document] and [Acknowledge].
  28. Enter the password associated with "User B" and click [OK].
  29. Validate the To-Do is no longer present.
Topics
• Document Routing • Treatment Plan
AV-79440 Summary | Details
Widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
Scenario 1: Envelope Import with Program Maintenance with multiple spaces in description
Specific Setup:
  • Envelope Import has been used to import a modeled form that has an initial selection criterion of 'Program Maintenance'.
  • Program Maintenance has been used to create a program with two or more spaces after all but the last word in the description (example: SPACING TESTING PROGRAM).
Steps
  1. Open the form that was added via Envelope Import.
  2. Enter the first letter of the program description.
  3. Validate that all programs that begin with that letter display in the search results.
  4. Select the program with multiple spaces in the description.
  5. Add desired data to the form and submit the form.
  6. Reopen the form and validate that all fields retained the data correctly.
Topics
• Modeling • NX • Program Maintenance
AV-79508 Summary | Details
User Modeled Forms - "User" entity
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Family Registration
  • Group Registration
  • Order Entry Practitioner Assignment
  • Order Group Setup
  • Site Registration
  • Update Client Data
  • User Definition
Scenario 1: User Modeled Form - "User" entity (PM)
Specific Setup:
  • A user modeled form is defined in PM for the "User" entity (Form A).
  • A user is defined that has a lowercase 'User ID' and 'User Description' (User A).
  • A user is defined that has an uppercase 'User ID' and 'User Description' (User B).
  • A user is defined that has a lowercase 'User ID' and uppercase 'User Description' (User C).
  • A user is defined that has an uppercase 'User ID' and lowercase 'User Description' (User D).
Steps
  1. Access "Form A".
  2. Search for and select "User A" in the 'Select UserID/User Description' field.
  3. Click [OK].
  4. Validate the form displays as expected.
  5. Populate all required and desired fields.
  6. Click [Submit].
  7. Access "Form A".
  8. Search for and select "User B" in the 'Select UserID/User Description' field.
  9. Click [OK].
  10. Validate the form displays as expected.
  11. Populate all required and desired fields.
  12. Click [Submit].
  13. Access "Form A".
  14. Search for and select "User C" in the 'Select UserID/User Description' field.
  15. Click [OK].
  16. Validate the form displays as expected.
  17. Populate all required and desired fields.
  18. Click [Submit].
  19. Access "Form A".
  20. Search for and select "User D" in the 'Select UserID/User Description' field.
  21. Click [OK].
  22. Validate the form displays as expected.
  23. Populate all required and desired fields.
  24. Click [Submit].
Scenario 2: User Modeled Form - "User" entity (CWS)
Specific Setup:
  • A user modeled form is defined in CWS for the "User" entity (Form A).
  • A user is defined that has a lowercase 'User ID' and 'User Description' (User A).
  • A user is defined that has an uppercase 'User ID' and 'User Description' (User B).
  • A user is defined that has a lowercase 'User ID' and uppercase 'User Description' (User C).
  • A user is defined that has an uppercase 'User ID' and lowercase 'User Description' (User D).
Steps
  1. Access "Form A".
  2. Search for and select "User A" in the 'Select UserID/User Description' field.
  3. Click [OK].
  4. Validate the form displays as expected.
  5. Populate all required and desired fields.
  6. Click [Submit].
  7. Access "Form A".
  8. Search for and select "User B" in the 'Select UserID/User Description' field.
  9. Click [OK].
  10. Validate the form displays as expected.
  11. Populate all required and desired fields.
  12. Click [Submit].
  13. Access "Form A".
  14. Search for and select "User C" in the 'Select UserID/User Description' field.
  15. Click [OK].
  16. Validate the form displays as expected.
  17. Populate all required and desired fields.
  18. Click [Submit].
  19. Access "Form A".
  20. Search for and select "User D" in the 'Select UserID/User Description' field.
  21. Click [OK].
  22. Validate the form displays as expected.
  23. Populate all required and desired fields.
  24. Click [Submit].
Scenario 3: "Entity" search based form - Validations
Specific Setup:
  • Have a user [UserA] with access to any or all of the following entity based forms:
  • Family Registration [FormA]
  • Site Registration [FormB]
  • Group Registration [FormC]
  • User Definition [FormD]
  • Form Definition [FormE]
  • Order Entry Practitioner Assignment [FormF]
  • Order Group Setup [FormG]
  • Update Client Data [FormH]
  • Benefit Plans [FormI]
  • For each form have an entity [EntityA] defined, that contains two or more spaces within its entity description. For example in form "User Definition", [EntityA] is user "SYSADM" with a user description set to " System Administrator "
  • For each form have an entity [EntityB] defined, that does not contain two or more spaces within it entity description
  • Log in as [UserA]
Steps
  1. Access [FormA]
  2. In the "Entity" search field, search for [EntityA] using just the first letter in its entity description
  3. Validate [EntityA] is found
  4. Click [OK]
  5. Validate the form displays as expected
  6. Submit the form
  7. Validate the form files successfully
  8. Access [FormA]
  9. In the "Entity" search field, search for [EntityA] using two or more letters in its entity description
  10. Validate [EntityA] is found
  11. Click [OK]
  12. Validate the form displays as expected
  13. Submit the form
  14. Validate the form files successfully
  15. Access [FormA]
  16. In the "Entity" search field, search for [EntityB] using just the first letter in its entity description
  17. Validate [EntityB] is found
  18. Click [OK]
  19. Validate the form displays as expected
  20. Submit the form
  21. Validate the form files successfully
  22. Access [FormA]
  23. In the "Entity" search field, search for [EntityB] using two or more letters in its entity description
  24. Validate [EntityB] is found
  25. Click [OK]
  26. Validate the form displays as expected
  27. Submit the form
  28. Validate the form files successfully
  29. Repeat steps 1 thru 4 for [FormB] thru [FormI] in the setup
  30. Validate the results, are as expected
Topics
• Forms • Modeling • NX