Skip to main content

RADplus 2023 Quarterly Release 2023.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 6 Summary | Details
Form Definition - Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Definition (CWS)
Scenario 1: Form Definition (Document Routing) - 'Skip Display of Document Image' and 'Skip Password' validations
Specific Setup:
  • Have a user [TestUser] who is a staff member and has the "My To Do's" widget on their home view.
  • Have a modeled form [FormA] with a "Draft/Final" field and any other desired fields on the form.
  • A client must be admitted in an existing episode. [ClientA].
  • [TestUser] has access to form "Document Routing Setup" and "Form Definition".
  • Login as [TestUser]
Steps
  1. Open form "Form Definition" and select [FormA].
  2. Navigate to the "Document Routing" section.
  3. Set field "Enable Document Routing" to "Yes".
  4. Click [Select Type] and select a desired form type.
  5. Populate the "Void Reason Code" field.
  6. Set field "Skip Display of Document Image" to "Yes".
  7. Validate field "Skip Password Entry" is set to "Yes" and is "Disabled".
  8. Submit the form.
  9. Open form "Document Routing Setup".
  10. Select [TestForm].
  11. Validate field "Enable Document Routing" to "Yes".
  12. Validate the "Type Name" field is populated with the form type selected in step1a.
  13. Validate the "Void Reason Code" field is populated with the value selected in step1a.
  14. Validate the "Skip Display of Document Image" to "Yes".
  15. Validate field "Skip Password Entry" is set to "Yes" and is "Disabled".
  16. Close the form.
  17. Select [Client A] and open [FormA].
  18. Populate the desired fields on form and submit the form as "Final".
  19. Validate the 'Document Preview' screen does not display, as expected.
  20. Validate the "Password Entry" dialog does not display.
  21. At the "Route Document To" screen.
  22. Search and select [UserA] as the "Approver" and click [Add] to add the user as an approver.
  23. Click [Submit].
  24. Navigate to the 'My To Do's' widget..
  25. Validate there is a To-Do present for [FormA] routed in the previous step.
  26. Click [Approve Document].
  27. Validate the 'Document Preview' displays the expected data.
  28. Click [Accept].
  29. Enter the password associated with "User A" and click [OK].
  30. Validate the To Do is no longer present in the "My To Do's" widget.
  31. Open form "Form Definition" and select [FormA].
  32. Navigate to the "Document Routing" section.
  33. Set field "Skip Display of Document Image" to "No".
  34. Validate field "Skip Password Entry" is now enabled.
  35. Set the value to "No".
  36. Submit the form.
  37. Open form "Document Routing Setup".
  38. Select [TestForm].
  39. Validate field "Skip Display of Document Image" to "No" as expected.
  40. Validate field "Skip Password Entry" to "Yes", as expected.
  41. Close the form.
  42. Select [Client A] and open [FormA].
  43. Populate the desired fields on form and submit the form as "Final".
  44. At the "Confirm Document" screen, validate the 'Document Preview' is displayed and populated as expected.
  45. Click the [Accept and Route] button.
  46. Validate the user is not prompted to enter their password, as expected.
  47. At the "Route Document To" screen.
  48. Search and select [UserA] as the "Approver" and click [Add] to add the users as an approver.
  49. Click [Submit].
  50. Repeat step 4
  51. Validate results are as expected.
  52. Open form "Form Definition" and select [FormA].
  53. Navigate to the "Document Routing" section.
  54. Validate field "Skip Display of Document Image" to "No" as expected.
  55. This time set field "Skip Password Entry" to "No".
  56. Submit the form.
  57. Open form "Document Routing Setup".
  58. Select [TestForm].
  59. Validate field "Skip Display of Document Image" to "No" as expected.
  60. Validate field "Skip Password Entry" to "No", as expected.
  61. Close the form.
  62. Select [Client A] and open [FormA].
  63. Populate the desired fields on form and submit the form as "Final".
  64. Validate the 'Document Preview' is displayed and populated, as expected.
  65. Click the [Accept and Route] button.
  66. Validate the user is prompted this time to enter their password.
  67. Populate the password field.
  68. At the "Route Document To" screen.
  69. Search and select [UserA] as the "Approver" and click [Add] to add the users as an approver.
  70. Click [Submit]..
  71. Repeat step 4
  72. Validate results are as expected.
Scenario 2: Form Definition (Document Routing) - "Acknowledgment" field and functionality validations
Specific Setup:
  • Have two users [StaffA] and [StaffB].
  • Both users have the "My To Do's" widget on their home view.
  • Have a modeled form [TestFormA] with a "Draft/Final" field and any other desired fields on the form.
  • A client [TestClient] has been admitted in an existing episode and his "Admitting Practitioner" is [StaffA].
  • Login as [StaffA].
Steps
  1. Open form "Form Definition" and select [TestFormA].
  2. Select the "Document Routing" section.
  3. Set field "Enable Document Routing" to "Yes".
  4. Click [Select Type] and select a desired form type.
  5. Populate the "Void Reason Code" field.
  6. Set field 'Approver Required' to "Yes".
  7. Navigate to the "Acknowledgments" sub-section.
  8. Validate field "Acknowledgments Allowed" is set to "No" and enabled.
  9. Validate all other fields in the section are disabled.
  10. Set field 'Acknowledgment Allowed' field set to "Yes".
  11. Validate the following fields are present and now are enabled.
  12. "Acknowledgment List Defaults".
  13. "Verification Level of Acknowledgments".
  14. "Days after finalized document to alert".
  15. "Forms to error when accessed".
  16. In the "Acknowledgment List Defaults" field select a desired value, for example "Admitting Practitioner".
  17. In the "Verification Level of Acknowledgments" field select a desired value, for example "Warn User if Acknowledgment is Missing".
  18. Set field "Days After Finalized document to alert" to the desired value.
  19. In the "Forms to error when access" select any desired form [TestFormB] from the selection list.
  20. Submit the form.
  21. Validate the form files successfully.
  22. Open form "Document Routing Setup".
  23. Select [TestForm].
  24. Validate the fields set in step1b are set with the same values.
  25. Close the form.
  26. Select [TestClient] and open [TestFormA].
  27. Populate the desired fields on form and submit the form as "Final".
  28. Validate the 'Document Preview' displays the expected data.
  29. At the "Confirm Document" screen.
  30. Validate the document contains the expected values.
  31. Click the [Accept and Route] button.
  32. Populate the "Verify Password Prompt" with a password and click [OK].
  33. At the "Route Document To" screen.
  34. Validate "Admitting Practitioner" is selected in the "Add Members to Acknowledge" selection box.
  35. Validate [StaffA] has been automatically added and selected as an acknowledger.
  36. Validate the [Submit] button is disabled.
  37. In the "Add" approver search field, select [StaffB].
  38. Validate [StaffB] has been added and selected as an "Approver".
  39. Validate the [Submit] button is now enabled.
  40. Click [Submit].
  41. Logout a [StaffA].
  42. Login as [StaffB].
  43. Select [TestClient].
  44. Navigate to the 'My To Do's' widget.
  45. Validate there is a To-Do present for [TestFormA] routed in step 2a.
  46. Click [Approve Document].
  47. Validate the 'Document Preview' displays the expected data.
  48. Click [Accept].
  49. Enter the users password and click [OK].
  50. Validate the To Do is no longer present in the "My To Do's" widget.
  51. Logout a [StaffB].
  52. Login as [StaffA].
  53. Select [TestClient].
  54. Access [TestFormB].
  55. Validate a "Verification Acknowledgment" dialog is displayed, indicating "[TestFormB] has an acknowledgment that has not been addressed. Please provide a reason for not acknowledging".
  56. Populate the text field with a reason and click [OK].
  57. Validate [TestFormB] loads as expected.
  58. Populate the form and submit it.
  59. Validate the form files successfully.
  60. Navigate to the 'My To Do's' widget.
  61. Validate there is an "Acknowledgments" To Do present for [TestFormA] in the To Do list.
  62. Click [Acknowledge Document].
  63. Validate the 'Document Preview' displays the expected data.
  64. Click [Acknowledge].
  65. Enter the password associated with user and click [OK].
  66. Validate the To Do is no longer present in the "My To Do's" widget.
  67. Access [TestFormB].
  68. Validate this time there is no "Verification Acknowledgment" dialog displayed, as the user has already acknowledged the 'To Do' waiting for the form.
  69. Validate the form opens successfully.
  70. Populate the form and submit it.
  71. Validate the form files successfully.
Scenario 3: Envelope Import - Validate "Document Routing" settings set on forms after import
Specific Setup:
  • Have or create a modeled envelope [TestEnvelope] that contains a modeled form [TestForm].
  • Configure [TestForm] in the document routing section of "Form Definition" or in form "Document Routing Setup", with the following document routing fields set as well as any other desired fields:
  • "Enable Document Routing" ; "Void Reason Code" ; "Create Document Only" ; "Skip Display of Document Image" ; "Skip Password Entry" ; "Require Final Approver" ; "Allow Transcriber" ; "Allow Notifications When Final" ; "Allow Notification With No Approvers" ; "Allow Comments During Approval" ; "Acknowledgment Allowed" ; "Acknowledgement List Defaults" ; "Verification Level of Acknowledgments" ; "Days after finalized document to alert" ; "Forms to error when accessed".
  • In form "Envelope Export", have envelope [TestEnvelope], exported and saved.
Steps
  1. Open form "Envelope Import".
  2. Click [Select Envelope Import File].
  3. In Windows Explorer, navigate to the location of [TestEnvelope].
  4. Select the file.
  5. Click [Save].
  6. In the "Overwrite Existing or Create New Envelope" field.
  7. Select "Overwrite Existing" if [TestEnvelope] already exists in the testing environment.
  8. Select "Create New" if [TestEnvelope] does not already exist in the current environment.
  9. Click [Begin Import Scan].
  10. Validate the import scan is successful.
  11. Click [Begin Import].
  12. Validate the envelope imports successfully.
  13. Open form "Document Routing Setup".
  14. Select [TestForm].
  15. Validate each of the document routing fields set in the setup are populated as expected.
  16. Validate any fields not set in the set up are not populated, as expected.
  17. Close the form.
  18. Open form "Form Definition".
  19. Navigate to the "Document Routing Section".
  20. Validate each of the document routing fields set in the setup are populated as expected.
  21. Validate any fields not set in the set up, are not populated as expected.
Topics
• Modeling • NX • Document Routing • Envelope Import • Envelope Export
Update 13 Summary | Details
Avatar NX - Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Alerts (PM)
Scenario 1: Avatar NX - Validate the 'See more...' text color in the Client Header
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Information' header should be included on the users myDay view.
Steps
  1. Select "Client A" and access the 'Client Alerts' form.
  2. Select "Warning (Custom)" in the 'Type Of Alert' field.
  3. Select "All Forms" in the 'Applicable Forms' field.
  4. Enter the desired value in the 'Custom Message' field.
  5. Click [Submit].
  6. Repeat steps 1-5 to create 3 additional client alerts.
  7. Once complete, navigate to the 'Client Header'.
  8. Validate the 'See more...' text is readable and displayed in white color.
  9. Mouse over the 'See more...' text and validate the client alerts created in the previous steps are displayed.
Widget Wizard - Widget Deletion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Widget Wizard (PM)
Scenario 1: Widget Wizard - Validate ability to delete user created widgets that have been imported
Specific Setup:
  • A user created widget must be defined (Widget A).
Steps
  1. Access the 'Widget Import' form.
  2. Click [Select Import File].
  3. Select the "Widget A".
  4. Validate the 'Import Scan Results' field contains: No errors found.
  5. Click [Begin Import].
  6. Validate a message is displayed stating: Import Complete.
  7. Click [OK] and close the form.
  8. Access the 'Widget Wizard' form.
  9. Click [Select Widget].
  10. Select "Widget A" and click [OK].
  11. Validate the data for "Widget A" is populated.
  12. Validate the 'Delete Widget' button is enabled.
  13. Click [Delete Widget].
  14. Validate a message is displayed stating: Delete Widget "Widget A"?
  15. Click [Yes].
  16. Click [Select Widget].
  17. Validate "Widget A" is no longer displayed in the 'Select Widgets' dialog.
  18. Click [Cancel] and close the form.
Topics
• Client Alerts • Widgets
Update 15 Summary | Details
Import Reports - "Report Description" field.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Import Reports (PM)
Scenario 1: "Import Reports" Form - Field Validations
Specific Setup:
  • One or more "Crystal Report's" have been imported in the system using form "Import Reports".
Steps
  1. Open the ‘Import Reports’ form.
  2. Select “Import Report as Form” in the ‘Select Import Type’ field.
  3. Select “Update Existing Report” in the ‘New or Existing Report’ field.
  4. Select the desired report in the ‘Existing Report’ dropdown.
  5. Validate the ‘Report Description’ field updated with the name of the report selected in the ‘Existing Report’ field.
  6. Select “Import New Report” in the ‘New or Existing Report’ field.
  7. Validate the ‘Report Description’ field has cleared as expected.
  8. With “Import Report as Form” still selected also select “Import Report for Document Routing” in the ‘Select Import Type’ field.
  9. Select “Update Existing Report” in the ‘New or Existing Report’ field.
  10. Select the desired report in the ‘Existing Report’ dropdown.
  11. Validate the ‘Report Description’ field updated with the name of the report selected in the ‘Existing Report’ field.
  12. Close the form.
  13. Open the ‘Import Reports’ form.
  14. Select “Import Report as Form” in the ‘Select Import Type’ field.
  15. Select “Yes” in the ‘Does This Report Require ODBC Connections In Addition To The Current Database’ field.
  16. Validate the "ODBC" section of the form is enabled and select a value in the "Connection Type" field.
  17. Select “Import Report for Document Routing” in the ‘Select Import Type’ field.
  18. Validate "Yes" is still selected in the ‘Does This Report Require ODBC Connections" field.
  19. Validate the "ODBC" section of the form is still enabled and select a value in the "Connection Type" field.
  20. De-Select “Import Report for Document Routing” in the ‘Select Import Type’ field.
  21. Validate "Yes" is still selected in the ‘Does This Report Require ODBC Connections" field.
  22. Validate the "ODBC" section of the form is still enabled and select a value in the "Connection Type" field.
  23. Select “No” in the ‘Does This Report Require ODBC Connections In Addition To The Current Database’ field.
  24. Validate the "ODBC" section of the form is removed from the form.
  25. Close the form.
Topics
• Import Reports • NX
Update 19 Summary | Details
Root system code creation
Scenario 1: New "Root" System Code creation (Internal Only) - Table data validations
Steps
  1. Internal Testing Only
Topics
• Forms
Update 22 Summary | Details
Table Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
  • Form Definition (CWS)
Scenario 1: Modeled Form - Validate results after submitting form and table definition changes
Specific Setup:
  • Have a modeled "Table" [TestTable] included in form [TestForm], that contains the following fields:
  • [FieldA]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Half Screen"
  • [FieldB]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Full Screen"
  • [FieldC]
  • Set in "Table Definition", with prompt "Always Required" set to "No"
  • Set in "Form Definition", with prompt "Object Width" prompt set to "Full Screen"
  • A "Draft/Final field"
  • A "Workflow Controlling Notification" field. (Note: workflow notification fields are created in form "Notification Type Definition" and then become available as a column in "Table Definition")
  • Any other desired fields
Steps
  1. Open form [TestForm]
  2. Validate [FieldA] is display in "Half Screen" width and is not a required field, as per the setup
  3. Validate [FieldB] and [FieldC] are displayed in "Full Screen" width and are not required fields, as per the setup
  4. Validate all other fields display as expected
  5. Close the form
  6. Open form "Table Definition"
  7. Select table [TestTable]
  8. Select [FieldB]
  9. Set prompt "Always Required" to "Yes"
  10. Submit the form
  11. Open form [TestForm]
  12. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  13. Validate [FieldB] is still displayed in "Full Screen" width and is now displayed as a required field, as expected
  14. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  15. Validate all other fields display as expected
  16. Close the form
  17. Open form "Form Definition"
  18. Select form [TestForm]
  19. Select [FieldB]
  20. Set prompt "Object Width" prompt set to "Half Screen"
  21. Submit the form
  22. Open form [TestForm]
  23. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  24. Validate [FieldB] is now displayed in "Half Screen" width and is still displayed as required, as expected
  25. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  26. Validate all other fields display as expected
  27. Close the form
  28. Open form "Table Definition"
  29. Select table [TestTable]
  30. Click [Add New Item]
  31. Select a "Column" type
  32. Populate the "Column Name" with the new field [FieldD]
  33. Populate any other required fields
  34. Submit the form
  35. Open form "Form Definition"
  36. Select form [TestForm]
  37. Select [FieldB]
  38. Click to the "Object Def" section
  39. Click [Add New Item]
  40. Select [FieldD]
  41. Submit the form
  42. Open form [TestForm]
  43. Validate [FieldA] is still displayed in "Half Screen" width and is not a required field
  44. Validate [FieldB] is now displayed in "Half Screen" width and is still displayed as required, as expected
  45. Validate [FieldC] is still displayed in "Full Screen" width and is not a required field
  46. Validate [FieldD] is displayed on the form
  47. Populate the field
  48. Populate all the fields on the form
  49. Submit the form
  50. Validate the form files successfully
Topics
• Modeling
Update 24 Summary | Details
Console Widget Viewer - Printing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Console Widget Viewer
Scenario 1: Console Widget Viewer - validate print preview and print output
Specific Setup:
  • 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 (Client A).
  • "Client A" has data filed in various forms:
  • A diagnosis entry (Diagnosis A)
  • A Problem (Problem List A)
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. Select 'All Forms'.
  3. Select the first desired form, for example "Diagnosis A".
  4. Click [Print] and [Print Current].
  5. Validate the 'Print' dialog displays a header containing the client, episode, and submission information at the top.
  6. Click [Cancel].
  7. Select several other desired forms.
  8. Click [Print] and [Print All].
  9. Validate the 'Print' dialog displays a header containing at least the client name and there are no empty headers. Please note: Certain forms do not generate a full form header containing client, episode, and submission information, but the client name will always display.
  10. Click [Print].
  11. Validate the printed forms display as expected, without any truncation.
Scenario 2: Console Widget Viewer - Progress Notes
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for Progress Notes in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
  • The 'Limit Console Widget Viewer To Text Only' registry setting must be enabled.
  • Please note: This is for Avatar NX systems only.
Steps
  1. Access 'Progress Notes (Group and Individual)' for "Client A".
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Draft" in the 'Draft/Final' field.
  6. Submit the note.
  7. Select "Client A" and navigate to "View A".
  8. Validate the 'Progress Notes' console widget contains the draft note filed in the previous steps and select it.
  9. Click [View].
  10. Validate the 'Console Widget Viewer' displays the draft progress note details filed in the previous steps as text.
  11. Click [Print] and [Print Current].
  12. Validate the 'Print' dialog displays a header containing the client, episode, and submission information at the top.
  13. Close the dialog.
  14. Click [Open Record].
  15. Validate the draft note is opened.
  16. Select "Final" in the 'Draft/Final' field.
  17. Submit the note.
  18. Select "Client A" and navigate back to "View A".
  19. Validate the 'Progress Notes' console widget contains the finalized note filed in the previous steps and select it.
  20. Click [View].
  21. Validate the 'Console Widget Viewer' displays the finalized progress note details filed in the previous steps as text.
  22. Click [Open Record].
  23. Validate a message is displayed stating "This note is already set to 'Final'."
  24. Click [OK] and validate the finalized note is not displayed.
Scenario 3: Console Widget Viewer - Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A user must have a console widget configured for the Treatment Plan in the 'Console Widget Configuration' form.
  • A user must have a view configured containing the Console Widget and Console Widget Viewer (View A).
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add any problem.
  7. Click [Return To Plan] and [OK].
  8. Submit the form.
  9. Select "Client A" and navigate to "View A".
  10. Validate the 'Treatment Plan' console widget contains the draft treatment plan filed in the previous steps and select it.
  11. Click [View].
  12. Validate the 'Console Widget Viewer' displays the draft treatment plan details filed in the previous steps.
  13. Click [Print] and [Print Current].
  14. Validate the 'Print' dialog displays a header containing the client, episode, and submission information at the top.
  15. Close the dialog.
  16. Click [Open Record].
  17. Validate the draft treatment plan is opened.
  18. Select "Final" in the 'Treatment Plan Status' field.
  19. Submit the note.
  20. Select "Client A" and navigate back to "View A".
  21. Validate the 'Treatment Plan' console widget contains the finalized treatment plan filed in the previous steps and select it.
  22. Click [View].
  23. Validate the 'Console Widget Viewer' displays the finalized treatment plan details filed in the previous steps.
  24. Click [Open Record].
  25. Validate a message is displayed stating "This plan is marked as Final. Changes are not allowed. Do you want to continue?"
  26. Click [No].
Scenario 4: 'All Documents' widget - Validate 'Diagnosis' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • Please note: This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select "Admission" in the 'Type Of Diagnosis' field.
  3. Enter the desired time in the 'Time Of Diagnosis' field.
  4. Click [New Row].
  5. Select the desired value in the 'Diagnosis Search' field.
  6. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  7. Click [Submit].
  8. Select "Client A" and navigate to the 'All Documents' view.
  9. Select 'All Forms'.
  10. Select "Diagnosis" in the 'Form Description' field.
  11. Validate the entry from the previous steps is present.
  12. Validate the 'Time' field displays.
  13. Select the entry and validate it displays in the 'Console Widget Viewer'.
  14. Click [Print] and [Print Current].
  15. Validate the 'Print' dialog displays a header containing the client, episode, and submission information at the top.
  16. Close the dialog.
Topics
• NX • All Documents Widget • Progress Notes (Group And Individual) • Console Widget • Treatment Plan • Diagnosis
Update 25 Summary | Details
Document Routing - Approver Comments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Document Routing (Progress Notes) - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a "Progress Notes" form [TestForm], for example form "Progress Notes (Group and Individual)", that has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the 'Co Signer for Other Practitioners' prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users are set with the "My To Do's" widget on their home view
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Document Routing - Signature Images
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Document Routing - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a form [TestForm], for example a "Modeled" form or "Treatment Plan" form that has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the "Co Signer for Other Practitioners" prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users have the "My To Do's" widget on their home views
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Topics
• Progress Notes • NX • Modeling
Update 26 Summary | Details
SQL table permissions
Scenario 1: User Definition - Validate a user's SQL "ODBC" Table permissions
Specific Setup:
  1. Two users exist on the system that have the same "User ID", but which differ by where the period within their user ID is placed. For this example: "U.serA" and "User.A"
  2. "U.serA" has access to the "SYSTEM.patient_current_demographics" table
  3. "U.serA" does not have access "SYSTEM.Admission_data" and "SYSTEM.Appoinment_data" table
  4. "User.A" also has access to "SYSTEM.patient_current_demographics" table
  5. "User.A" does have access to the "SYSTEM.Admission_data" and "SYSTEM.Appiontment_data" tables'
  6. Each user has access to 'Crystal Reports" or other database program to make an ODBC connection and view their assigned SQL Table
Steps
  1. Open the database program, for this example "Crystal Reports" is used
  2. Click "File" on the menu and then "New" to create a new report
  3. At the "Data" dialog, click "Create New Connection"
  4. Double-click "ODBC"
  5. From the "Data Source Selection" dialog, locate the data source name created for user ID "U.serA" and double-click to select it
  6. Populate the "User ID" field and "Password" with the credentials for "U.serA"
  7. Click "Finish"
  8. At the table tree list
  9. Click the "SYSTEM" schema folder and then click "Tables"
  10. Validate the "SYSTEM.patient_current_demographics' table is present in the list
  11. Validate the "SYSTEM.Admission_data" and "SYSTEM.Apppintmentt_data" tables are "not" present, as expected
  12. Click 'Cancel"
  13. Click "File" on the menu and then "New" to create a new report
  14. At the "Data" dialog, click "Create New Connection"
  15. Double-click "ODBC"
  16. From the "Data Source Selection" dialog, locate the data source name created for user ID "User.A"
  17. Populate the "User ID" field and "Password" with the credentials for "User.A"
  18. Click "Finish"
  19. At the table tree list
  20. At the table tree list
  21. Click the "SYSTEM" schema folder and then click "Tables"
  22. Validate the "SYSTEM.patient_current_demographics' table is present in the list
  23. Validate the "SYSTEM.Admission_data" and "SYSTEM.Appointment_data" tables "are" present, as expected
Topics
• SQL Data Access
Update 29 Summary | Details
My To Do's Widget - Client name
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView - My To Do's widget
Scenario 1: Validate display of the clients name in the "My To Do's" widget
Specific Setup:
  • In form "Dictionary Update", have the "Client Prefix (175)" and the "Client Suffix (174)" dictionary's, populated with dictionary values.
  • Have clients admitted on the system defined that have client names in the following formats::
  • [ClientA] has just a "first and last name" defined.
  • [ClientB] has a "first name, middle name, last name" defined.
  • [ClientC] has a "first name, middle name, last name and a suffix" defined.
  • [ClientD] has a "prefix, first name, middle name, last name" defined.
  • [ClientE] has a "prefix, first name, middle name, last name and a suffix defined.
  • Have a user [TestUser] who is a staff member and has the "My To Do's" widget on their home view
  • For each client in step 2, have a "To Do" item generated and sent to [TestUser]. (For example, this can be done using form "Send To Do Notification" or any form enabled for document routing)
  • Log in as [TestUser]
Steps
  1. Navigate to the "My To Do's" widget
  2. In the "Client" column, locate the To Do generated for [ClientA]
  3. Validate the clients name displays in the format "First Name Last Name" as expected
  4. Click "Review To Do Item" in the "Action" column to launch the "Review To Do Item" form
  5. Validate the "Client Header" displays the name as expected, in the format "First Name Last Name"
  6. Click the "Reviewed" check box
  7. Submit the form
  8. Validate the To Do is removed from the To Do's list
  9. In the "Client" column locate the To Do generated for [ClientB]
  10. Repeat step 1a,
  11. Validate results are as expected, ensuring the clients name displays in the format, "First Name Middle Name Last name"
  12. In the "Client" column locate the To Do generated for [ClientC]
  13. Repeat step 1a
  14. Validate results are as expected, ensuring the clients name displays in the format, "First Name Middle Name Last name Suffix"
  15. In the "Client" column locate the To Do generated for [ClientD]
  16. Repeat step 1a
  17. Validate results are as expected, ensuring the clients name displays in the format, "Prefix First Name Middle Name Last Name"
  18. In the "Client" column locate the To Do generated for [ClientE]
  19. Repeat step 1a
  20. Validate results are as expected, ensuring the clients name displays in the format, "Prefix First Name Middle Name Last name Suffix"
Topics
• NX
Update 30 Summary | Details
All Doc Widget - Time field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • LookupTypes
  • UserModeledFormA
Scenario 1: 'All Documents' widget - Modeled Form data row validations
Specific Setup:
  • A client is enrolled in an existing episode [TestClient]
  • Have two modeled forms [FormA] and [FormB]
  • [FormA] is based on a table that is "Date" sorted. [Note: this is configured with prompt "Is This Table Date Sorted" set to "Yes" in "Table Definition"]
  • [FormB] is not based on a table that is "Date Sorted"
  • Have the "Primary All Documents Widget" on the users home view
  • [FormA] and [FormB] have been added to the "All Forms" tab of the widget using form "All Documents Widget Definition"
  • [FormB] have been added to the "All Forms" tab of the widget using form "All Documents Widget Definition"
  • Please note: The "Primary All Documents Widget" is for Avatar NX systems only.
Steps
  1. Select a client [TestClient]
  2. Open [FormA] (Modeled Form 'Date Sorted')
  3. Select an episode
  4. Populate any desired fields
  5. Submit the form
  6. Validate the form files successfully
  7. Note the data entry date and time
  8. Open [FormB] (Modeled form not 'Date Sorted')
  9. Select an episode
  10. Populate any desired fields
  11. Submit the form
  12. Validate the form files successfully
  13. Note the data entry date and time
  14. At the home view, select [TestClient]
  15. Navigate to the "Primary All Documents Widget" and click the "Refresh" button
  16. Click the "All Forms" tab
  17. Select [FormA] from the 'Form Description' field.
  18. Validate the "Form Description" field is populated with the form name for [FormA]
  19. Select the episode from the "Episode" field
  20. Validate the "Date" column is populated with date noted in step 2
  21. Validate the "Time" field is 'not' populated, as expected
  22. Validate each of the columns are populated, as expected
  23. Select [FormB] from the 'Form Description' field.
  24. Validate the "Form Description" field is populated with the form name for [FormB]
  25. Select the episode from the "Episode" field
  26. Validate the "Date" column is populated with date noted in step 3
  27. Validate the "Time" field is populated, as expected with time noted in step 3
  28. Validate each of the columns are populated, as expected
Topics
• All Documents Widget
Update 31 Summary | Details
Client Purge Setup - Deleting record
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Purge Setup
Scenario 1: Client Purge Setup - Define Exception Rules - Adding / Deleting rules
Specific Setup:
  • User Definition:
  • The 'Client Purge Setup' form is available in the list of forms.
  • The 'Client Purge Setup' form is selected to enable them in the Avatar menu.
Steps
  1. Open the 'Client Purge Setup' form.
  2. Enter the number of years since the last movement or service for a client to be eligible for purge in the field ‘Years After Last Contact to Be Excluded From Purge’.
  3. In the field 'Months After Last Payment/Adjustment To Be Eligible From Purge', enter the number of months since the last payment/adjustment a client should have to be eligible for purge.
  4. In the ‘Default Reason for Exclusion’ field, select a default reason value to be used by the purge form when clients qualified to be purged are manually excluded.
  5. Click [Define Exception Rules].
  6. Verify the grid opens successfully.
  7. Enter one exception rule to be used by the 'Client Purge' form.
  8. Enter the name of the table to be used for the exception criteria in the 'System Table' field.
  9. Enter the name of the field to be used for the exception criteria in the 'Field' field.
  10. Enter one of the operators to be used for the exception criteria in the 'Conditional' field. Note - The ‘BT’(Between) conditional requires a properly formatted value in the ‘Field Value’ column formatted as number, comma, number. When the ‘Exists’ conditional is selected the ’Field Value’ column is not required but it remains a required field for all other conditionals.
  11. Enter desired value in the 'Field Value' field.
  12. Enter desired value in the 'Record Selection' field, select 'Most Recent’ to use the most recent records regardless of the date and time. Select ‘Past (Minutes)’ to use only records from today created in the past minutes as defined in the field ‘Record Selection Range (Minutes)’.
  13. In the field ‘Record Selection Range (Minutes)’, enter the number of minutes to be used when evaluating a Record Selection defined as ‘Past (Minutes)’
  14. Ensure the field ‘Record Selection Date Field’ displays only date properties and will default to the data entry date field if it exists in the table.
  15. Click [Save].
  16. Click [Yes].
  17. Click [Submit].
  18. Open the 'Client Purge Setup' form.
  19. Click [Define Exception Rules].
  20. Verify the exception rule created displays correctly as entered.
  21. Select the rule.
  22. Click [Delete].
  23. Click [Save].
  24. Click [Submit].
  25. Open the 'Client Purge Setup' form.
  26. Click [Define Exception Rules].
  27. Verify the exception rule does not display and deleted permanently.
  28. Close the grid.
  29. Click [Discard].
Topics
• RADplus Utilities
Update 32 Summary | Details
Form Designer - field labels
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
Scenario 1: Envelope Import (with Form Designer changes) - Field validations after import
Specific Setup:
  • Have an existing modeled envelope [TestEnvelope] that contains a form [TestForm] that includes a "Date" type field and any other desired field types
  • Using "Form Designer", edit [TestForm] and navigate to any field [TestField] on the form.
  • Edit the field label name of the field to include a '~' tilde character within the field label name. For example a field label name of "Te~stField"
Steps
  1. Open form [TestForm]
  2. Navigate to [TestField]
  3. Validate the form designer change to add a '~' tilde character within the field label name, is displayed as expected
  4. Navigate to the "Date" field
  5. Enter a desired date
  6. Click the 'T' and 'Y' buttons of date field
  7. Validate the date field reflects the expected value
  8. Click the 'Calendar' icon and select a date
  9. Validate the date field reflects the expected value
  10. Populate any other fields on the form
  11. Submit the form
  12. Validate the form files successfully
  13. Open form "Envelope Export"
  14. Select [TestEnvelope] for export
  15. Select "Yes" in prompt "Include Form Design Changes"
  16. Click to [Export] the file and save the file to a folder location
  17. Validate the export is successful
  18. Close the form
  19. Open form "Envelope Import"
  20. Click [Select Envelope For Import]
  21. Navigate the location of export file for [TestEnvelope] saved in step 2
  22. Select the file
  23. Select "Yes" in prompt "Include Form Design Changes"
  24. In the "Overwrite Existing Envelope or Create New Envelope" field, select "Create New"
  25. At the dialog prompt, "This envelope already exists within this system. Are you sure that you would like to create a new envelope?"
  26. Click [Yes]
  27. Click [Begin Import Scan]
  28. In the "Import Scan Results" field, validate there are the following warnings:
  29. Warning: Envelope The import file contains an envelope name which is already in use. The import process will assign a new envelope name based upon the existing name and a counter.
  30. Warning: Table: The import file contains a table name which is already in use. The import process will assign a new table name based upon the existing name and a counter.
  31. Click [Begin Import]
  32. Validate the following "Import" warning is received
  33. Import: The envelope to be imported is currently defined and can be imported as an 'Overwrite' with no errors. Selecting 'Create New' may cause conflicts in future envelope imports. Are you sure that you want to 'Create New'?
  34. Click [Yes]
  35. Validate import is completed successfully
  36. Close the form
  37. Open "Form Definition" and select the new import version of [TestForm]. Note: the new copy form will have the same name as the original, but the (ID#) of the form next to the form name will be a higher number
  38. Rename the form to a desired name [TestFormNew] and submit the form
  39. Open the new form [TestFormNew]
  40. Navigate to [TestField]
  41. Validate the form designer change, to add a '~' tilde character within the field label name, is displayed as expected
  42. Navigate to the "Date" field
  43. Enter a desired date
  44. Click the 'T' and 'Y' buttons of date field
  45. Validate the date reflects the expected value
  46. Click the 'Calendar' icon and select a date
  47. Validate the date field reflects the expected value
  48. Populate any other desired fields on the form
  49. Submit the form
  50. Validate the form files successfully
  51. Repeat step 5 for the original version of the form [TestForm]
  52. Validate results are as expected
Form Designer - Date field components
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
Internal Test Only
Form Designer- ScriptLink settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
Scenario 1: Form Designer (Export/Import) - Validate "ScriptLink" configuration" settings after form designer changes
Specific Setup:
  • Have a form [TestForm] with one or more fields on the form
  • Have a "ScriptLink" script configured [ScriptTest] that exists in the system
  • In "Form Designer", the "WSDL" for [ScriptTest] has already been imported for form [TestForm]
  • The logged in user must have access to 'Form Designer'.
Steps
  1. Access 'Form Designer'.
  2. Select "TestForm" from the 'Forms' field.
  3. Select a section [TestSection] from the 'Sections' field.
  4. Click [Show Section].
  5. Navigate to the "ScriptLink" settings section
  6. Click the "Post-File" field in the "Available Scripts" column
  7. Select [TestScript]
  8. Populate the "Script Parameter" field with a parameter [TestParam]
  9. Return to the form layout section
  10. Click to select any field [TestField]
  11. On the left side panel in the "General" settings section
  12. Click the "ScriptLink" setting link
  13. From the "Available Scripts" field, select [TestScript]
  14. Populate the "Script Parameter" field with a parameter [TestParam]
  15. Click [Apply]
  16. Click [Save]
  17. Submit the form
  18. Validate the form submits successfully
  19. Return to "Form Designer"
  20. Navigate to the form layout and make any desired form designer change to the layout. For this example, [TestField] is moved to a new location on the layout
  21. Click [Save]
  22. Submit the form
  23. Return to "Form Designer"
  24. Select "TestForm"
  25. Select [TestSection]
  26. From the "Export All Tabs or Select Tab" field?
  27. Select "Selected Section"
  28. Click "Export Form Designer Copy"
  29. Navigate to a folder location and save the file
  30. Close the form
  31. Re-open "Form Designer"
  32. Select "TestForm"
  33. Select [TestSection]
  34. Click "Import Form Designer Copy"
  35. Navigate the folder location of the export file saved in step 3, and select the file
  36. Submit the form
  37. Return to "Form Designer"
  38. Select "TestForm"
  39. Select [TestSection]
  40. Click [Show Section].
  41. Navigate to the "ScriptLink" settings section
  42. Click the "Post-File" field in the "Available Scripts" column
  43. Validate script [TestScript] is selected as expected
  44. Validate the "Script Parameter" field is populated with parameter [TestParam] as expected
  45. Return to the form layout section
  46. Validate the form designer change made to [TestField] in step 2 is displayed as expected
  47. Select [TestFeild]
  48. Click to select the "General" settings section on the left side panel
  49. Click the "ScriptLink" setting link
  50. From the "Available Scripts" field, validate script [TestScript] is selected as expected
  51. Validate the "Script Parameter" field is populated with parameter [TestParam] as expected
  52. Re-submit the form
  53. Return to "Form Designer"
  54. Repeat step 5c and 5d
  55. Validate all "ScriptLink" configuration setting are still present, as expected
Console Widgets - SQL query override
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: Validate data displayed in the "Console Widget Viewer" widget
Specific Setup:
  • Have registry setting "Enable Console Widgets/Views" is set to "Y"
  • Have access to the 'Admission' form
  • Have an episodic modeled form [TestForm] created
  • In form "Console Widget Configuration":
  • Create a console widget for the "Admission" form [AdminWidget] with "SQL Query override" field populated with a query that does not include an episode in the link. For example: "SELECT <LINK:PATIENT510:PATID:EPN_uniqueid>PATID,EPN_uniqueid FROM SYSTEM.episode_history WHERE FACILITY=?FACILITY AND PATID=?PATID"
  • Create a console widget for the "Modeled" form [ModeledWidget] with "SQL Query override" field populated with a query that does not include an episode in the link. For example: "SELECT <LINK:USER19:PATID:CUSTHAAS_UID>PATID,CUSTHAAS_UID FROM SYSTEM.testtable1 WHERE FACILITY=?FACILITY AND PATID=?PATID" Note: (replace the row ID and option ID values as applicable)
  • Add the two widgets and the 'Console Widget Viewer' widget to the logged in users home view
  • Have a client [TestClient] admitted in two episodes
  • In each episode, have a row filed for that client in the modeled form
Steps
  1. At the homeview, select [TestClient]
  2. Select 'All Episodes' from the episode dropdown field.
  3. Navigate to the [AdminWidget]
  4. Validate a row for both admission episodes are present in the widget
  5. Click the "View" button for "Episode 1" row
  6. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  7. Click the "View" button for "Episode 2" row
  8. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  9. Select "Episode 1" from the episode dropdown field.
  10. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  11. Select "Episode 2" from the episode dropdown field.
  12. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  13. Select 'All Episodes' from the episode dropdown field.
  14. Navigate to the [ModeledWidget]
  15. Validate a row for both modeled form episodes are present in the widget
  16. Click the "View" button for "Episode 1" row
  17. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  18. Click the "View" button for "Episode 2" row
  19. Validate data is displayed for that episode in the 'Console Widget Viewer", as expected
  20. Select "Episode 1" from the episode dropdown field.
  21. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
  22. Select "Episode 2" from the episode dropdown field.
  23. Validate the following message is displayed in the widget, as expected "The LINK tag in the SQL query does not contain an EPISODE value".
Topics
• Envelope Import • NX • Scriptlink • Console Widget
Update 33 Summary | Details
Integrated eSignature - 'Send Document' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Send Document
  • Clinical Document Viewer
  • Pending eSignatures
Scenario 1: Integrated eSignature - 'Send Document' form - Send Document Only
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • User must have access to the 'Send Document' form.
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password for the logged in user in the 'Password' field and click [Verify].
  11. Validate a message is displayed stating: Note Filed.
  12. Click [OK] and close the form.
  13. Access the 'Send Document' form.
  14. Select the form type associated to 'Progress Notes (Group and Individual)' in the 'Form Type' field.
  15. Select "Client A" in the 'Entity' field.
  16. Validate 'Episode Number' field contains "All Episodes".
  17. Enter the current date in the 'From Date' and 'To Date' fields.
  18. Select the progress note filed in the previous steps in the 'Select Document' field.
  19. Click [Display Document].
  20. Validate the document displays as filed.
  21. Click [Close All Documents and Exit].
  22. Validate "Send Document Only" is defaulted in the 'Reason for Sending' field.
  23. Once the document has received all approvals, it is considered finalized and may not be sent for eSignature but the document can still be sent for review only.
  24. Click [Send Request].
  25. Validate a message is displayed stating: Request Sent.
  26. Click [OK] and close the form.
  27. Access the 'Clinical Document Viewer' form.
  28. Select "Client" in the 'Select Client:' field.
  29. Select "Individual" in the 'Select All or Individual Client' field.
  30. Select "Client A" in the 'Select Client' field.
  31. Click [Process].
  32. Validate two document rows are displayed for the client:
  33. One 'Document Description' contains "Document sent for review" - this is what was sent to myHealthPointe for review.
  34. One 'Document Description' contains "Progress Notes (Group and Individual)" - this is the finalized progress note form finalized via document routing.
  35. Select both documents for viewing and click [View].
  36. Validate the documents display as expected.
  37. Click [Close All Documents] and close the form.
  38. Log in to myHealthPointe for "Client A".
  39. Select the "Documents" section.
  40. Validate the document sent via the 'Send Document' form is displayed.
  41. Select the document and validate the pdf opens and displays as expected.
  42. Close the document.
Scenario 2: Integrated eSignature - 'Send Document' form - Send for eSignature
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • User must have access to the 'Send Document' form.
  • Document Routing is enabled on the 'Treatment Plan' form.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Add the staff associated to the logged in user as an approver.
  11. Select "None" in the 'Send to myHealthPointe' field.
  12. Click [Submit].
  13. Navigate to the 'My To Do's' widget.
  14. Validate a To-Do is displayed for "Client A" but do not approve it.
  15. Click [Close].
  16. Access the 'Send Document' form.
  17. Select the form type associated to 'Treatment Plan' in the 'Form Type' field.
  18. Select "Client A" in the 'Entity' field.
  19. Validate 'Episode Number' field contains "All Episodes".
  20. Enter the current date in the 'From Date' and 'To Date' fields.
  21. Select the treatment plan filed in the previous steps in the 'Select Document' field.
  22. Click [Display Document].
  23. Validate the document displays as filed.
  24. Click [Close All Documents and Exit].
  25. Validate both "Send Document Only" and "Send for eSignature" are enabled in the 'Reason for Sending' field.
  26. "Re-send for eSignature" is disabled because the document has not been sent for eSignature yet.
  27. Validate "Send for eSignature" is the default value in the 'Reason for Sending' field.
  28. Click [Send Request].
  29. Validate a message is displayed stating: Request Sent.
  30. Click [OK] and close the form.
  31. Navigate to the 'Pending eSignatures' widget.
  32. Validate a row is displayed for the eSignature request sent for "Client A".
  33. Navigate to the 'My To Do's' widget.
  34. Validate the To-Do is no longer displayed for "Client A".
  35. The To-Do will display after the eSignature has been collected.
  36. Click [Close].
  37. Log in to myHealthPointe for "Client A".
  38. Select the "Documents Awaiting Signature" section.
  39. Validate the document sent for eSignature is displayed.
  40. Click [Sign and Submit].
  41. Enter an eSignature in the 'Enter the Signature' field.
  42. Click [Sign and Submit].
  43. Validate the document is no longer displayed.
  44. Navigate to the 'Pending eSignatures' widget.
  45. Validate the row is no longer displayed for "Client A".
  46. Navigate to the 'My To Do's' widget.
  47. Validate a To-Do is displayed for "Client A".
  48. Click [Review] and [Accept].
  49. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  50. Electronically signed by Author
  51. Electronically signed by "Client A"
  52. Electronically signed by Approver
  53. Click [Sign].
  54. Enter the password for the logged in user in the 'Password' field and click [Verify].
  55. Validate the To-Do is no longer displayed.
  56. Click [Close].
  57. Access the 'Clinical Document Viewer' form.
  58. Select "Client" in the 'Select Client:' field.
  59. Select "Individual" in the 'Select All or Individual Client' field.
  60. Select "Client A" in the 'Select Client' field.
  61. Click [Process].
  62. Validate two document rows are displayed for the client:
  63. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  64. One 'Document Description' contains "Treatment Plan" - this is the finalized treatment plan form finalized via document routing.
  65. Select both documents for viewing and click [View].
  66. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  67. Validate the "Treatment Plan" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  68. Click [Close All Documents] and close the form.
Scenario 3: Integrated eSignature - 'Send Document' form - Re-Send for eSignature
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • User must have access to the 'Send Document' form.
  • Document Routing is enabled on the 'Treatment Plan' form.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Add the staff associated to the logged in user as an approver.
  11. Select "None" in the 'Send to myHealthPointe' field.
  12. Click [Submit].
  13. Navigate to the 'My To Do's' widget.
  14. Validate a To-Do is displayed for "Client A" but do not approve it.
  15. Click [Close].
  16. Access the 'Send Document' form.
  17. Select the form type associated to 'Treatment Plan' in the 'Form Type' field.
  18. Select "Client A" in the 'Entity' field.
  19. Validate 'Episode Number' field contains "All Episodes".
  20. Enter the current date in the 'From Date' and 'To Date' fields.
  21. Select the treatment plan filed in the previous steps in the 'Select Document' field.
  22. Click [Display Document].
  23. Validate the document displays as filed.
  24. Click [Close All Documents and Exit].
  25. Validate both "Send Document Only" and "Send for eSignature" are enabled in the 'Reason for Sending' field.
  26. "Re-send for eSignature" is disabled because the document has not been sent for eSignature yet.
  27. Validate "Send for eSignature" is the default value in the 'Reason for Sending' field.
  28. Click [Send Request].
  29. Validate a message is displayed stating: Request Sent.
  30. Click [OK] and close the form.
  31. Navigate to the 'Pending eSignatures' widget.
  32. Validate a row is displayed for the eSignature request sent for "Client A".
  33. Navigate to the 'My To Do's' widget.
  34. Validate the To-Do is no longer displayed for "Client A".
  35. The To-Do will display after the eSignature has been collected.
  36. Click [Close].
  37. Log in to myHealthPointe for "Client A".
  38. Select the "Documents Awaiting Signature" section.
  39. Validate the document sent for eSignature is displayed but do not sign it.
  40. Access the 'Send Document' form.
  41. Select the form type associated to 'Treatment Plan' in the 'Form Type' field.
  42. Select "Client A" in the 'Entity' field.
  43. Validate 'Episode Number' field contains "All Episodes".
  44. Enter the current date in the 'From Date' and 'To Date' fields.
  45. Select the treatment plan filed in the previous steps in the 'Select Document' field.
  46. Validate both "Send Document Only" and "Re-send for eSignature" are enabled in the 'Reason for Sending' field.
  47. Validate "Re-send for eSignature" is the default value in the 'Reason for Sending' field.
  48. Click [Send Request].
  49. Validate a message is displayed stating: Request Sent.
  50. Click [OK] and close the form.
  51. Navigate to the 'Pending eSignatures' widget.
  52. Validate the row for "Client A" is updated with the current time for 'Time Sent'.
  53. Log in to myHealthPointe for "Client A".
  54. Select the "Documents Awaiting Signature" section.
  55. Validate the document sent for eSignature is displayed with an updated time uploaded.
  56. Click [Sign and Submit].
  57. Enter an eSignature in the 'Enter the Signature' field.
  58. Click [Sign and Submit].
  59. Validate the document is no longer displayed.
  60. Navigate to the 'My To Do's' widget.
  61. Validate a To-Do is displayed for "Client A".
  62. Click [Review] and [Accept].
  63. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  64. Electronically signed by Author
  65. Electronically signed by "Client A"
  66. Electronically signed by Approver
  67. Click [Sign].
  68. Enter the password for the logged in user in the 'Password' field and click [Verify].
  69. Validate the To-Do is no longer displayed.
  70. Click [Close].
  71. Access the 'Clinical Document Viewer' form.
  72. Select "Client" in the 'Select Client:' field.
  73. Select "Individual" in the 'Select All or Individual Client' field.
  74. Select "Client A" in the 'Select Client' field.
  75. Click [Process].
  76. Validate three document rows are displayed for the client with the following:
  77. 'Document Description' contains "Integrated eSignature request" - this is the initial request sent to myHealthPointe for eSignature.
  78. 'Document Description' contains "Integrated eSignature request" - this is the re-sent request sent to myHealthPointe for eSignature.
  79. 'Document Description' contains "Treatment Plan" - this is the finalized treatment plan form finalized via document routing.
  80. Select the documents for viewing and click [View].
  81. Validate the initial "Integrated eSignature request" displays the document with the author's signature.
  82. Validate the latest "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  83. Validate the "Treatment Plan" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  84. Click [Close All Documents] and close the form.
Scenario 4: Integrated eSignature - Validate the 'Enable Send Document to myHealthPointe functionality' registry setting
Specific Setup:
  • Please note: this is for Avatar NX systems only.
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Send Document To" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting' field contains "RADplus->Document Routing->->->->Enable Send Document to myHealthPointe functionality".
  5. Validate the 'Registry Setting Detail' field contains "Documents may be sent to myHealthPointe for client eSignature or review. When enabled, the form 'Send Document' will be made available, and the field 'Send to myHealthPointe' will be added to the 'Route Document To' screen in the 'Accept and Route' document routing process. Set to 'Y' to enable this functionality, or 'N' to disable."
  6. Validate the 'Registry Setting Value' field contains "N" as this is the default value.
  7. Enter "Y" in the 'Registry Setting Value' field.
  8. Click [Submit] and close the form.
  9. Access the 'User Definition' form.
  10. Select the logged in user in the 'Select User' field.
  11. Select the "Forms and Tables" section.
  12. Click [Select Forms for User Access].
  13. Validate the 'Send Document' form is available for selection under "Avatar PM" forms and select it.
  14. Click [OK] and [Submit].
  15. Navigate to the 'User Menu'.
  16. Click [Refresh Forms].
  17. Access the 'Send Document' form.
  18. Validate the 'Send Document' form is displayed as expected.
  19. Close the form.
Integrated eSignature - 'DocR.esignature' SQL table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Final to Draft Override (CWS)
  • Clinical Document Viewer
  • Ambulatory Progress Notes
  • Treatment Plan
  • Void Progress Notes
  • Select Note To Void
  • Progress Note Corrections
  • Treatment Plan Status Override (CWS)
Scenario 1: Integrated eSignature - Void Sent Documents
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
  • User must have access to the 'DocR.esignature' SQL table in 'User Definition'.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select the staff associated to the logged in user as an approver.
  11. Select "Document Only" in the 'Send to myHealthPointe' field.
  12. Click [Submit].
  13. Log in to myHealthPointe for "Client A".
  14. Select the "Documents" section.
  15. Validate the document sent via document routing is displayed.
  16. Select the document and validate the pdf opens and displays as expected.
  17. Close the document.
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'DocR.esignature' SQL table.
  20. Validate a row is displayed for the document sent to myHealthPointe for "Client A".
  21. Validate the 'eSignature_status' field contains "Sent - No Signature Requested".
  22. Navigate to the 'My To Do's' widget.
  23. Click [Review] for the To-Do for "Client A".
  24. Click [Reject].
  25. Enter the desired value in the 'Comments for Rejected' field.
  26. Click [Sign].
  27. Validate the To-Do is no longer displayed.
  28. Log in to myHealthPointe for "Client A".
  29. Select the "Documents" section.
  30. Validate the rejected document is no longer displayed.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Refresh the report using the 'DocR.esignature' SQL table.
  33. Validate the 'eSignature_status' field now contains "Voided".
  34. Close the report.
Scenario 2: Integrated eSignature - Collect eSignature via Document Routing - Reject and Delete Document
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • A "Client" entity modeled form must be defined (Form A).
  • Document Routing is enabled on "Form A".
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Treatment Plan Status' field.
  4. Click [Submit].
  5. Validate a 'Confirm Document' dialog is displayed.
  6. Click [Accept and Route].
  7. Enter the password for the logged in user in the 'Password' field and click [Verify].
  8. Add the staff associated to the logged in user as an approver.
  9. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  10. Click [Submit].
  11. Navigate to the 'Pending eSignatures' widget.
  12. Validate a row is displayed for the eSignature request sent for "Client A".
  13. Access Crystal Reports or other SQL Reporting tool.
  14. Create a report using the 'DocR.esignature' SQL table.
  15. Validate a row is displayed for the eSignature request sent for "Client A".
  16. Validate the 'eSignature_status' field contains "Pending".
  17. Navigate to the 'My To Do's' widget.
  18. Validate a To-Do is not displayed for the document for "Client A" that has eSignature requested.
  19. The To-Do will only be generated after the document has been signed by the client in myHealthPointe.
  20. Log in to myHealthPointe for "Client A".
  21. Select the "Documents Awaiting Signature" section.
  22. Validate the document sent for eSignature is displayed.
  23. Click [Sign and Submit].
  24. Enter an eSignature in the 'Enter the Signature' field.
  25. Click [Sign and Submit].
  26. Validate the document is no longer displayed.
  27. Navigate to the 'Pending eSignatures' widget.
  28. Validate the row is no longer displayed for "Client A".
  29. Access Crystal Reports or other SQL Reporting tool.
  30. Refresh the report using the 'DocR.esignature' SQL table.
  31. Validate the 'eSignature_status' field now contains "Approved".
  32. Close the report.
  33. Navigate to the 'My To Do's' widget.
  34. Validate a To-Do is displayed for "Client A".
  35. Click [Review] and [Reject].
  36. Enter the desired value in the 'Comments for Rejected' field.
  37. Click [Sign].
  38. Validate the To-Do is no longer displayed.
  39. Click [Close].
  40. Select "Client A" and access "Form A".
  41. Validate the rejected document has been reverted to draft.
  42. Delete the draft row.
  43. Access the 'Clinical Document Viewer' form.
  44. Select "Client" in the 'Select Client:' field.
  45. Select "Individual" in the 'Select All or Individual Client' field.
  46. Select "Client A" in the 'Select Client' field.
  47. Click [Process].
  48. Validate the "Integrated eSignature Request" is displayed with "Void" as the 'Document Status'.
  49. Close the form.
  50. Access Crystal Reports or other SQL Reporting tool.
  51. Refresh the report using the 'DocR.esignature' SQL table.
  52. Validate the row for "Client A" is no longer displayed since the document has been deleted.
Scenario 3: Integrated eSignature - Modeled Form - Collect eSignature via Document Routing (No Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • A "Client" entity modeled form must be defined (Form A).
  • Document Routing is enabled on "Form A" and an approver is not required.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Treatment Plan Status' field.
  4. Click [Submit].
  5. Validate a 'Confirm Document' dialog is displayed.
  6. Click [Accept and Route].
  7. Enter the password for the logged in user in the 'Password' field and click [Verify].
  8. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  9. Click [Submit].
  10. Navigate to the 'Pending eSignatures' widget.
  11. Validate a row is displayed for the eSignature request sent for "Client A".
  12. Access Crystal Reports or other SQL Reporting tool.
  13. Create a report using the 'DocR.esignature' SQL table.
  14. Validate a row is displayed for the eSignature request sent for "Client A".
  15. Validate the 'eSignature_status' field contains "Pending".
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed.
  19. Click [Sign and Submit].
  20. Enter an eSignature in the 'Enter the Signature' field.
  21. Click [Sign and Submit].
  22. Validate the document is no longer displayed.
  23. Navigate to the 'Pending eSignatures' widget.
  24. Validate the row is no longer displayed for "Client A".
  25. Access Crystal Reports or other SQL Reporting tool.
  26. Refresh the report using the 'DocR.esignature' SQL table.
  27. Validate the 'eSignature_status' field now contains "Approved".
  28. Close the report.
  29. Access the 'Clinical Document Viewer' form.
  30. Select "Client" in the 'Select Client:' field.
  31. Select "Individual" in the 'Select All or Individual Client' field.
  32. Select "Client A" in the 'Select Client' field.
  33. Click [Process].
  34. Validate two document rows are displayed for the client:
  35. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  36. One 'Document Description' contains "Form A" - this is the modeled form finalized via document routing.
  37. Select both documents for viewing and click [View].
  38. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  39. Validate the "Form A" finalized document displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  40. Click [Close All Documents] and close the form.
Scenario 4: Integrated eSignature - Void Progress Notes
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  13. Click [Submit].
  14. Validate a message is displayed stating: Note Filed.
  15. Click [OK] and close the form.
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed but do not sign it.
  19. Access Crystal Reports or other SQL Reporting Tool.
  20. Create a report using the 'DocR.esignature' SQL table.
  21. Validate a row is displayed for the document pending eSignature for "Client A".
  22. Validate the 'eSignature_status' field contains "Pending".
  23. Access the 'Void Progress Notes' form.
  24. Select "Client A" in the 'Client ID' field.
  25. Select the episode used in the previous steps in the 'Episode Number' field.
  26. Enter the current date in the 'Start Date' and 'End Date' fields.
  27. Click [Select Note To Void].
  28. Validate the 'Select Note To Void' dialog contains the note filed in the previous steps with an indicator stating: [eSignature Requested on XX/XX/XXXX at XX:XX].
  29. Select the note and click [OK].
  30. Select the desired value in the 'Reason For Voiding The Note' field.
  31. Enter the desired value in the 'Comments' field.
  32. Click [Submit] and close the form.
  33. Log in to myHealthPointe for "Client A".
  34. Select the "Documents Awaiting Signature" section.
  35. Validate the voided document is no longer displayed.
  36. Access Crystal Reports or other SQL Reporting Tool.
  37. Refresh the report using the 'DocR.esignature' SQL table.
  38. Validate the row for "Client A" is no longer displayed.
  39. Close the report.
  40. Access the 'Clinical Document Viewer' form.
  41. Select "Client" in the 'Select Type:' field.
  42. Select "Individual" in the 'Select All or Individual Client' field.
  43. Select "Client A" in the 'Select Client' field.
  44. Click [Process].
  45. Validate there is a row for the voided note with the following:
  46. Document Description of "Integrated eSignature Request"
  47. Document Status of "Void"
  48. Close the form.
Scenario 5: Integrated eSignature - Progress Note Corrections
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  13. Click [Submit].
  14. Validate a message is displayed stating: Note Filed.
  15. Click [OK] and close the form.
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed but do not sign it.
  19. Access Crystal Reports or other SQL Reporting Tool.
  20. Create a report using the 'DocR.esignature' SQL table.
  21. Validate a row is displayed for the document pending eSignature for "Client A".
  22. Validate the 'eSignature_status' field contains "Pending".
  23. Access the 'Progress Note Corrections' form.
  24. Select "Client A" in the 'Client ID' field.
  25. Select the episode used in the previous steps in the 'Episode Number' field.
  26. Enter the current date in the 'Start Date' and 'End Date' fields.
  27. Click [Select Note To Correct].
  28. Validate the 'Select Note To Correct' dialog contains the note filed in the previous steps with an indicator stating: [eSignature Requested on XX/XX/XXXX at XX:XX].
  29. Select the note and click [OK].
  30. Select "Revert Final Note to Draft" in the 'Correction Action' field.
  31. Select the desired value in the 'Reason for Correction' field.
  32. Enter the desired value in the 'Comments' field.
  33. Click [Submit].
  34. Log in to myHealthPointe for "Client A".
  35. Select the "Documents Awaiting Signature" section.
  36. Validate the document is no longer displayed.
  37. Access Crystal Reports or other SQL Reporting Tool.
  38. Refresh the report using the 'DocR.esignature' SQL table.
  39. Validate the 'eSignature_status' field now contains "Rescinded".
  40. Close the report.
Scenario 6: Integrated eSignature - Treatment Plan Status Override
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Log in to myHealthPointe for "Client A".
  13. Select the "Documents Awaiting Signature" section.
  14. Validate the document sent for eSignature is displayed but do not sign it.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'DocR.esignature' SQL table.
  17. Validate a row is displayed for the document pending eSignature for "Client A".
  18. Validate the 'eSignature_status' field contains "Pending".
  19. Access the 'Treatment Plan Status Override' form.
  20. Select "Client A" in the 'Select Client' field.
  21. Select "(60000) Treatment Plan" in the 'Select Treatment Plan' field.
  22. Select the treatment plan filed in the previous steps in the 'Select Client Plan' field.
  23. Enter the desired value in the 'Override Reason' field.
  24. Click [Submit].
  25. Validate a message is displayed stating: Are you sure you want to change this treatment plan status back to draft?
  26. Click [Yes].
  27. Log in to myHealthPointe for "Client A".
  28. Select the "Documents Awaiting Signature" section.
  29. Validate the document is no longer displayed.
  30. Access Crystal Reports or other SQL Reporting Tool.
  31. Refresh the report using the 'DocR.esignature' SQL table.
  32. Validate the 'eSignature_status' field now contains "Rescinded".
  33. Close the report.
Integrated eSignature - 'Pending eSignatures' widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • View Definition
  • Pending eSignatures
  • Ambulatory Progress Notes
  • Treatment Plan
Scenario 1: Integrated eSignature - Validate the 'Pending eSignatures' widget
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • Multiple clients are enrolled in existing episodes with the following:
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • Various documents pending eSignature in myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Navigate to the 'Pending eSignatures' widget.
  2. Validate the 'Filter By Program' field is displayed.
  3. Validate the following columns are displayed:
  4. Client Name
  5. Client ID
  6. Episode
  7. Program
  8. Form Name
  9. Date Sent
  10. Time Sent
  11. Sent By Staff Name
  12. Status
  13. Validate all documents pending eSignature are displayed for all clients.
  14. Select the desired program in the 'Filter By Program' field.
  15. Validate only documents associated to the selected program are displayed (if any).
  16. Clear the program in the 'Filter By Program' field.
  17. Select a client with documents pending eSignature from the 'My Clients' list.
  18. Validate only documents pending eSignature for the selected client are displayed.
  19. De-select the client.
  20. Validate all documents pending eSignature for all clients are displayed.
  21. Click on the 'Client Name' column.
  22. Validate the documents are sorted by 'Client Name'.
  23. Click on the 'Client ID' column.
  24. Validate the documents are sorted by 'Client ID'.
  25. Click on the 'Date Sent' column.
  26. Validate the documents are sorted by 'Date Sent'.
Scenario 2: Integrated eSignature - Treatment Plan - Collect eSignature via Document Routing (No Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
  • The 'Pending eSignatures' widget must be accessible on the HomeView.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Navigate to the 'Pending eSignatures' widget.
  13. Validate a row is displayed for the eSignature request sent for "Client A".
  14. Access Crystal Reports or other SQL Reporting tool.
  15. Create a report using the 'DocR.esignature' SQL table.
  16. Validate a row is displayed for the eSignature request sent for "Client A".
  17. Validate the 'eSignature_status' field contains "Pending".
  18. Log in to myHealthPointe for "Client A".
  19. Select the "Documents Awaiting Signature" section.
  20. Validate the document sent for eSignature is displayed.
  21. Click [Sign and Submit].
  22. Enter an eSignature in the 'Enter the Signature' field.
  23. Click [Sign and Submit].
  24. Validate the document is no longer displayed.
  25. Navigate to the 'Pending eSignatures' widget.
  26. Validate the row is no longer displayed for "Client A".
  27. Access Crystal Reports or other SQL Reporting tool.
  28. Refresh the report using the 'DocR.esignature' SQL table.
  29. Validate the 'eSignature_status' field now contains "Approved".
  30. Close the report.
  31. Access the 'Clinical Document Viewer' form.
  32. Select "Client" in the 'Select Client:' field.
  33. Select "Individual" in the 'Select All or Individual Client' field.
  34. Select "Client A" in the 'Select Client' field.
  35. Click [Process].
  36. Validate two document rows are displayed for the client:
  37. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  38. One 'Document Description' contains "Treatment Plan" - this is the treatment plan document finalized via document routing.
  39. Select both documents for viewing and click [View].
  40. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  41. Validate the "Treatment Plan" finalized document displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  42. Click [Close All Documents] and close the form.
Integrated eSignature - Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Final to Draft Override (CWS)
  • Clinical Document Viewer
  • Ambulatory Progress Notes
  • Treatment Plan
  • Approver Override
  • Void Progress Notes
  • Select Note To Void
  • Progress Note Corrections
  • Treatment Plan Status Override (CWS)
Scenario 1: Integrated eSignature - Collect eSignature via Document Routing - Reject and Delete Document
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • A "Client" entity modeled form must be defined (Form A).
  • Document Routing is enabled on "Form A".
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Treatment Plan Status' field.
  4. Click [Submit].
  5. Validate a 'Confirm Document' dialog is displayed.
  6. Click [Accept and Route].
  7. Enter the password for the logged in user in the 'Password' field and click [Verify].
  8. Add the staff associated to the logged in user as an approver.
  9. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  10. Click [Submit].
  11. Navigate to the 'Pending eSignatures' widget.
  12. Validate a row is displayed for the eSignature request sent for "Client A".
  13. Access Crystal Reports or other SQL Reporting tool.
  14. Create a report using the 'DocR.esignature' SQL table.
  15. Validate a row is displayed for the eSignature request sent for "Client A".
  16. Validate the 'eSignature_status' field contains "Pending".
  17. Navigate to the 'My To Do's' widget.
  18. Validate a To-Do is not displayed for the document for "Client A" that has eSignature requested.
  19. The To-Do will only be generated after the document has been signed by the client in myHealthPointe.
  20. Log in to myHealthPointe for "Client A".
  21. Select the "Documents Awaiting Signature" section.
  22. Validate the document sent for eSignature is displayed.
  23. Click [Sign and Submit].
  24. Enter an eSignature in the 'Enter the Signature' field.
  25. Click [Sign and Submit].
  26. Validate the document is no longer displayed.
  27. Navigate to the 'Pending eSignatures' widget.
  28. Validate the row is no longer displayed for "Client A".
  29. Access Crystal Reports or other SQL Reporting tool.
  30. Refresh the report using the 'DocR.esignature' SQL table.
  31. Validate the 'eSignature_status' field now contains "Approved".
  32. Close the report.
  33. Navigate to the 'My To Do's' widget.
  34. Validate a To-Do is displayed for "Client A".
  35. Click [Review] and [Reject].
  36. Enter the desired value in the 'Comments for Rejected' field.
  37. Click [Sign].
  38. Validate the To-Do is no longer displayed.
  39. Click [Close].
  40. Select "Client A" and access "Form A".
  41. Validate the rejected document has been reverted to draft.
  42. Delete the draft row.
  43. Access the 'Clinical Document Viewer' form.
  44. Select "Client" in the 'Select Client:' field.
  45. Select "Individual" in the 'Select All or Individual Client' field.
  46. Select "Client A" in the 'Select Client' field.
  47. Click [Process].
  48. Validate the "Integrated eSignature Request" is displayed with "Void" as the 'Document Status'.
  49. Close the form.
  50. Access Crystal Reports or other SQL Reporting tool.
  51. Refresh the report using the 'DocR.esignature' SQL table.
  52. Validate the row for "Client A" is no longer displayed since the document has been deleted.
Scenario 2: Integrated eSignature - Modeled Form - Collect eSignature via Document Routing (No Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • A "Client" entity modeled form must be defined (Form A).
  • Document Routing is enabled on "Form A" and an approver is not required.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Treatment Plan Status' field.
  4. Click [Submit].
  5. Validate a 'Confirm Document' dialog is displayed.
  6. Click [Accept and Route].
  7. Enter the password for the logged in user in the 'Password' field and click [Verify].
  8. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  9. Click [Submit].
  10. Navigate to the 'Pending eSignatures' widget.
  11. Validate a row is displayed for the eSignature request sent for "Client A".
  12. Access Crystal Reports or other SQL Reporting tool.
  13. Create a report using the 'DocR.esignature' SQL table.
  14. Validate a row is displayed for the eSignature request sent for "Client A".
  15. Validate the 'eSignature_status' field contains "Pending".
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed.
  19. Click [Sign and Submit].
  20. Enter an eSignature in the 'Enter the Signature' field.
  21. Click [Sign and Submit].
  22. Validate the document is no longer displayed.
  23. Navigate to the 'Pending eSignatures' widget.
  24. Validate the row is no longer displayed for "Client A".
  25. Access Crystal Reports or other SQL Reporting tool.
  26. Refresh the report using the 'DocR.esignature' SQL table.
  27. Validate the 'eSignature_status' field now contains "Approved".
  28. Close the report.
  29. Access the 'Clinical Document Viewer' form.
  30. Select "Client" in the 'Select Client:' field.
  31. Select "Individual" in the 'Select All or Individual Client' field.
  32. Select "Client A" in the 'Select Client' field.
  33. Click [Process].
  34. Validate two document rows are displayed for the client:
  35. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  36. One 'Document Description' contains "Form A" - this is the modeled form finalized via document routing.
  37. Select both documents for viewing and click [View].
  38. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  39. Validate the "Form A" finalized document displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  40. Click [Close All Documents] and close the form.
Scenario 3: Integrated eSignature - Progress Notes - Send Document Only via Document Routing
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Ambulatory Progress Notes' form and an approver is not required.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Document Only" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Access the 'Clinical Document Viewer' form.
  13. Select "Client" in the 'Select Client:' field.
  14. Select "Individual" in the 'Select All or Individual Client' field.
  15. Select "Client A" in the 'Select Client' field.
  16. Click [Process].
  17. Validate two document rows are displayed for the client:
  18. One 'Document Description' contains "Document sent for review" - this is what was sent to myHealthPointe for review.
  19. One 'Document Description' contains "Ambulatory Progress Notes" - this is the finalized progress note form finalized via document routing.
  20. Select both documents for viewing and click [View].
  21. Validate the documents display as expected.
  22. Click [Close All Documents] and close the form.
  23. Log in to myHealthPointe for "Client A".
  24. Select the "Documents" section.
  25. Validate the document sent via document routing is displayed.
  26. Select the document and validate the pdf opens and displays as expected.
  27. Close the document.
Scenario 4: Integrated eSignature - Treatment Plan - Collect eSignature via Document Routing (With Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Add the staff associated to the logged in user as an approver.
  11. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  12. Click [Submit].
  13. Navigate to the 'Pending eSignatures' widget.
  14. Validate a row is displayed for the eSignature request sent for "Client A".
  15. Access Crystal Reports or other SQL Reporting tool.
  16. Create a report using the 'DocR.esignature' SQL table.
  17. Validate a row is displayed for the eSignature request sent for "Client A".
  18. Validate the 'eSignature_status' field contains "Pending".
  19. Navigate to the 'My To Do's' widget.
  20. Validate a To-Do is not displayed for the document for "Client A" that has a pending eSignature.
  21. The To-Do will only be generated after the document has been signed by the client in myHealthPointe.
  22. Log in to myHealthPointe for "Client A".
  23. Select the "Documents Awaiting Signature" section.
  24. Validate the document sent for eSignature is displayed.
  25. Click [Sign and Submit].
  26. Enter an eSignature in the 'Enter the Signature' field.
  27. Click [Sign and Submit].
  28. Validate the document is no longer displayed.
  29. Navigate to the 'Pending eSignatures' widget.
  30. Validate the row is no longer displayed for "Client A".
  31. Access Crystal Reports or other SQL Reporting tool.
  32. Refresh the report using the 'DocR.esignature' SQL table.
  33. Validate the 'eSignature_status' field now contains "Approved".
  34. Close the report.
  35. Navigate to the 'My To Do's' widget.
  36. Validate a To-Do is displayed for "Client A".
  37. Click [Review] and [Accept].
  38. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  39. Electronically signed by Author
  40. Electronically signed by "Client A"
  41. Electronically signed by Approver
  42. Click [Sign].
  43. Enter the password for the logged in user in the 'Password' field and click [Verify].
  44. Validate the To-Do is no longer displayed.
  45. Click [Close].
  46. Access the 'Clinical Document Viewer' form.
  47. Select "Client" in the 'Select Client:' field.
  48. Select "Individual" in the 'Select All or Individual Client' field.
  49. Select "Client A" in the 'Select Client' field.
  50. Click [Process].
  51. Validate two document rows are displayed for the client:
  52. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  53. One 'Document Description' contains "Treatment Plan" - this is the treatment plan finalized via document routing.
  54. Select both documents for viewing and click [View].
  55. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  56. Validate the "Treatment Plan" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  57. Click [Close All Documents] and close the form.
Scenario 5: Integrated eSignature - Request eSignature and add approvers via 'Approver Override'
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Navigate to the 'Pending eSignatures' widget.
  13. Validate a row is displayed for the eSignature request sent for "Client A".
  14. Access Crystal Reports or other SQL Reporting tool.
  15. Create a report using the 'DocR.esignature' SQL table.
  16. Validate a row is displayed for the eSignature request sent for "Client A".
  17. Validate the 'eSignature_status' field contains "Pending".
  18. Access the 'Approver Override' form.
  19. Select the form type associated to the 'Treatment Plan' form in the 'Form Type' field.
  20. Select "Client A" in the 'Entity' field.
  21. Enter the current date in the 'From Date' and 'To Date' fields.
  22. Validate the 'List of Documents' field contains the treatment plan filed in the previous steps with an indicator stating: [eSignature Requested on XX/XX/XXXX at XX:XX].
  23. Click [Display Document].
  24. Validate the document displays as filed.
  25. Click [Close].
  26. Validate the 'List of Approvers' field does not contain any approvers.
  27. Click [Update Approvers].
  28. Validate the 'Send to myHealthPointe' field is disabled and "Collect eSignature" is selected.
  29. Add the staff associated to the logged in user as an approver.
  30. Click [Submit] and close the form.
  31. Log in to myHealthPointe for "Client A".
  32. Select the "Documents Awaiting Signature" section.
  33. Validate the document sent for eSignature is displayed.
  34. Click [Sign and Submit].
  35. Enter an eSignature in the 'Enter the Signature' field.
  36. Click [Sign and Submit].
  37. Validate the document is no longer displayed.
  38. Navigate to the 'Pending eSignatures' widget.
  39. Validate the row is no longer displayed for "Client A".
  40. Access Crystal Reports or other SQL Reporting tool.
  41. Refresh the report using the 'DocR.esignature' SQL table.
  42. Validate the 'eSignature_status' field now contains "Approved".
  43. Close the report.
  44. Navigate to the 'My To Do's' widget.
  45. Validate a To-Do is displayed for "Client A".
  46. Click [Review] and [Accept].
  47. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  48. Electronically signed by Author
  49. Electronically signed by "Client A"
  50. Electronically signed by Approver
  51. Click [Sign].
  52. Enter the password for the logged in user in the 'Password' field and click [Verify].
  53. Validate the To-Do is no longer displayed.
  54. Click [Close].
  55. Access the 'Clinical Document Viewer' form.
  56. Select "Client" in the 'Select Client:' field.
  57. Select "Individual" in the 'Select All or Individual Client' field.
  58. Select "Client A" in the 'Select Client' field.
  59. Click [Process].
  60. Validate two document rows are displayed for the client:
  61. One 'Document Description' contains "Integrated eSignature request" - this is what was sent via document routing.
  62. One 'Document Description' contains "Treatment Plan" - this is the finalized treatment plan form finalized via document routing.
  63. Select both documents for viewing and click [View].
  64. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  65. Validate the "Treatment Plan" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  66. Click [Close All Documents] and close the form.
Scenario 6: Integrated eSignature - Approver Override - Collect eSignature
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
  • The logged in user must have an associated staff member (Staff A).
  • Another user must have an associated staff member (Staff B).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Add "Staff B" as an approver.
  13. Select "None" in the 'Send to myHealthPointe' field.
  14. Click [Submit].
  15. Validate a message is displayed stating: Note Filed.
  16. Click [OK] and close the form.
  17. Access the 'Approver Override' form.
  18. Select the form type associated to the 'Progress Notes (Group and Individual)' form in the 'Form Type' field.
  19. Select "Client A" in the 'Entity' field.
  20. Enter the current date in the 'From Date' and 'To Date' fields.
  21. Validate the 'List of Documents' field contains the progress note filed in the previous steps.
  22. Click [Display Document].
  23. Validate the document displays as filed.
  24. Click [Close].
  25. Validate the 'List of Approvers' field contains "Staff B".
  26. Click [Update Approvers].
  27. Validate "None" is selected in the 'Send to myHealthPointe' field.
  28. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  29. De-select "Staff B" as an approver.
  30. Select "Staff A" as an approver.
  31. Click [Submit] and close the form.
  32. Navigate to the 'Pending eSignatures' widget.
  33. Validate a row is displayed for the eSignature request sent for "Client A".
  34. Access Crystal Reports or other SQL Reporting tool.
  35. Create a report using the 'DocR.esignature' SQL table.
  36. Validate a row is displayed for the eSignature request sent for "Client A".
  37. Validate the 'eSignature_status' field contains "Pending".
  38. Log in to myHealthPointe for "Client A".
  39. Select the "Documents Awaiting Signature" section.
  40. Validate the document sent for eSignature is displayed.
  41. Click [Sign and Submit].
  42. Enter an eSignature in the 'Enter the Signature' field.
  43. Click [Sign and Submit].
  44. Validate the document is no longer displayed.
  45. Navigate to the 'Pending eSignatures' widget.
  46. Validate the row is no longer displayed for "Client A".
  47. Access Crystal Reports or other SQL Reporting tool.
  48. Refresh the report using the 'DocR.esignature' SQL table.
  49. Validate the 'eSignature_status' field now contains "Approved".
  50. Close the report.
  51. Navigate to the 'My To Do's' widget.
  52. Validate a To-Do is displayed for "Client A".
  53. Click [Review] and [Accept].
  54. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  55. Electronically signed by Author
  56. Electronically signed by "Client A"
  57. Electronically signed by Approver
  58. Click [Sign].
  59. Enter the password for the logged in user in the 'Password' field and click [Verify].
  60. Validate the To-Do is no longer displayed.
  61. Click [Close].
  62. Access the 'Clinical Document Viewer' form.
  63. Select "Client" in the 'Select Client:' field.
  64. Select "Individual" in the 'Select All or Individual Client' field.
  65. Select "Client A" in the 'Select Client' field.
  66. Click [Process].
  67. Validate two document rows are displayed for the client:
  68. One 'Document Description' contains "Integrated eSignature request" - this is what was sent via the 'Approver Override' form.
  69. One 'Document Description' contains "Progress Notes (Group and Individual)" - this is the progress note form finalized via document routing.
  70. Select both documents for viewing and click [View].
  71. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  72. Validate the "Progress Notes (Group and Individual)" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  73. Click [Close All Documents] and close the form.
Scenario 7: Integrated eSignature - Void Progress Notes
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  13. Click [Submit].
  14. Validate a message is displayed stating: Note Filed.
  15. Click [OK] and close the form.
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed but do not sign it.
  19. Access Crystal Reports or other SQL Reporting Tool.
  20. Create a report using the 'DocR.esignature' SQL table.
  21. Validate a row is displayed for the document pending eSignature for "Client A".
  22. Validate the 'eSignature_status' field contains "Pending".
  23. Access the 'Void Progress Notes' form.
  24. Select "Client A" in the 'Client ID' field.
  25. Select the episode used in the previous steps in the 'Episode Number' field.
  26. Enter the current date in the 'Start Date' and 'End Date' fields.
  27. Click [Select Note To Void].
  28. Validate the 'Select Note To Void' dialog contains the note filed in the previous steps with an indicator stating: [eSignature Requested on XX/XX/XXXX at XX:XX].
  29. Select the note and click [OK].
  30. Select the desired value in the 'Reason For Voiding The Note' field.
  31. Enter the desired value in the 'Comments' field.
  32. Click [Submit] and close the form.
  33. Log in to myHealthPointe for "Client A".
  34. Select the "Documents Awaiting Signature" section.
  35. Validate the voided document is no longer displayed.
  36. Access Crystal Reports or other SQL Reporting Tool.
  37. Refresh the report using the 'DocR.esignature' SQL table.
  38. Validate the row for "Client A" is no longer displayed.
  39. Close the report.
  40. Access the 'Clinical Document Viewer' form.
  41. Select "Client" in the 'Select Type:' field.
  42. Select "Individual" in the 'Select All or Individual Client' field.
  43. Select "Client A" in the 'Select Client' field.
  44. Click [Process].
  45. Validate there is a row for the voided note with the following:
  46. Document Description of "Integrated eSignature Request"
  47. Document Status of "Void"
  48. Close the form.
Scenario 8: Integrated eSignature - Progress Note Corrections
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  13. Click [Submit].
  14. Validate a message is displayed stating: Note Filed.
  15. Click [OK] and close the form.
  16. Log in to myHealthPointe for "Client A".
  17. Select the "Documents Awaiting Signature" section.
  18. Validate the document sent for eSignature is displayed but do not sign it.
  19. Access Crystal Reports or other SQL Reporting Tool.
  20. Create a report using the 'DocR.esignature' SQL table.
  21. Validate a row is displayed for the document pending eSignature for "Client A".
  22. Validate the 'eSignature_status' field contains "Pending".
  23. Access the 'Progress Note Corrections' form.
  24. Select "Client A" in the 'Client ID' field.
  25. Select the episode used in the previous steps in the 'Episode Number' field.
  26. Enter the current date in the 'Start Date' and 'End Date' fields.
  27. Click [Select Note To Correct].
  28. Validate the 'Select Note To Correct' dialog contains the note filed in the previous steps with an indicator stating: [eSignature Requested on XX/XX/XXXX at XX:XX].
  29. Select the note and click [OK].
  30. Select "Revert Final Note to Draft" in the 'Correction Action' field.
  31. Select the desired value in the 'Reason for Correction' field.
  32. Enter the desired value in the 'Comments' field.
  33. Click [Submit].
  34. Log in to myHealthPointe for "Client A".
  35. Select the "Documents Awaiting Signature" section.
  36. Validate the document is no longer displayed.
  37. Access Crystal Reports or other SQL Reporting Tool.
  38. Refresh the report using the 'DocR.esignature' SQL table.
  39. Validate the 'eSignature_status' field now contains "Rescinded".
  40. Close the report.
Scenario 9: Integrated eSignature - Treatment Plan Status Override
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Log in to myHealthPointe for "Client A".
  13. Select the "Documents Awaiting Signature" section.
  14. Validate the document sent for eSignature is displayed but do not sign it.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'DocR.esignature' SQL table.
  17. Validate a row is displayed for the document pending eSignature for "Client A".
  18. Validate the 'eSignature_status' field contains "Pending".
  19. Access the 'Treatment Plan Status Override' form.
  20. Select "Client A" in the 'Select Client' field.
  21. Select "(60000) Treatment Plan" in the 'Select Treatment Plan' field.
  22. Select the treatment plan filed in the previous steps in the 'Select Client Plan' field.
  23. Enter the desired value in the 'Override Reason' field.
  24. Click [Submit].
  25. Validate a message is displayed stating: Are you sure you want to change this treatment plan status back to draft?
  26. Click [Yes].
  27. Log in to myHealthPointe for "Client A".
  28. Select the "Documents Awaiting Signature" section.
  29. Validate the document is no longer displayed.
  30. Access Crystal Reports or other SQL Reporting Tool.
  31. Refresh the report using the 'DocR.esignature' SQL table.
  32. Validate the 'eSignature_status' field now contains "Rescinded".
  33. Close the report.
Scenario 10: Integrated eSignature - Approver Override - Document Only
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
  • The logged in user must have an associated staff member (Staff A).
  • Another user must have an associated staff member (Staff B).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Select "Final" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a 'Confirm Document' dialog is displayed.
  10. Click [Accept and Route].
  11. Enter the password for the logged in user in the 'Password' field and click [Verify].
  12. Add "Staff B" as an approver.
  13. Select "None" in the 'Send to myHealthPointe' field.
  14. Click [Submit].
  15. Validate a message is displayed stating: Note Filed.
  16. Click [OK] and close the form.
  17. Access the 'Approver Override' form.
  18. Select the form type associated to the 'Progress Notes (Group and Individual)' form in the 'Form Type' field.
  19. Select "Client A" in the 'Entity' field.
  20. Enter the current date in the 'From Date' and 'To Date' fields.
  21. Validate the 'List of Documents' field contains the progress note filed in the previous steps.
  22. Click [Display Document].
  23. Validate the document displays as filed.
  24. Click [Close].
  25. Validate the 'List of Approvers' field contains "Staff B".
  26. Click [Update Approvers].
  27. Validate "None" is selected in the 'Send to myHealthPointe' field.
  28. Select "Document Only" in the 'Send to myHealthPointe' field.
  29. De-select "Staff B" as an approver.
  30. Select "Staff A" as an approver.
  31. Click [Submit] and close the form.
  32. Navigate to the 'My To Do's' widget.
  33. Validate a To-Do is displayed for "Client A".
  34. Click [Review] and [Accept].
  35. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  36. Electronically signed by Author
  37. Electronically signed by Approver
  38. Click [Sign].
  39. Enter the password for the logged in user in the 'Password' field and click [Verify].
  40. Validate the To-Do is no longer displayed.
  41. Click [Close].
  42. Access the 'Clinical Document Viewer' form.
  43. Select "Client" in the 'Select Client:' field.
  44. Select "Individual" in the 'Select All or Individual Client' field.
  45. Select "Client A" in the 'Select Client' field.
  46. Click [Process].
  47. Validate two document rows are displayed for the client:
  48. One 'Document Description' contains "Document sent for review" - this is what was sent via the 'Approver Override' form
  49. One 'Document Description' contains "Progress Notes (Group and Individual)" - this is the progress note form finalized via document routing.
  50. Select both documents for viewing and click [View].
  51. Validate the "Document sent for review" displays the document with the author's signature.
  52. Validate the "Progress Notes (Group and Individual)" finalized document displays the document with the author's signature and the approving practitioner signature.
  53. Click [Close All Documents] and close the form.
  54. Log in to myHealthPointe for "Client A".
  55. Select the "Documents" section.
  56. Validate the document sent via the 'Approver Override' form is displayed.
  57. Select the document and validate the pdf opens and displays as expected.
  58. Close the document.
Entity-Based Document Capture
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Entity-Based Document Capture
  • Clinical Document Viewer
Scenario 1: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • Select a client, staff, provider, incident and performing provider 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.
Move Selected Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Move Selected Data (CWS)
  • Move Selected Data (PM)
  • Clinical Document Viewer
Scenario 1: Move Selected Data [CWS] - Move data from one episode to another when document routing is enabled
Specific Setup:
  • A client is enrolled in two existing episodes (Client A).
Steps
  1. Access the 'Document Routing Setup' form.
  2. Select "Avatar CWS" in the 'Application' field.
  3. Click [Select Form].
  4. Select "Progress Notes (Group and Individual)" in the 'Select a form to enable Document Routing' field and click [OK].
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Select "Yes" in the 'Allow Comments During Approval' field.
  7. Click [File] and close the form.
  8. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  9. Select "Episode 1" in the 'Select Episode' field.
  10. Select "Independent Note" in the 'Progress Note For' field.
  11. Select the desired value in the 'Note Type' field.
  12. Enter the desired value in the 'Notes Field' field.
  13. Select "Final" in the 'Draft/Final' field.
  14. Click [File Note].
  15. Validate the 'Confirm Document' dialog is displayed.
  16. Click [Accept].
  17. Enter the password for the logged in user in the 'Password' field and click [Verify].
  18. Enter the desired comments in the 'Approval Comments' field and click [OK].
  19. Validate a message is displayed stating: Note Filed.
  20. Click [OK] and close the form.
  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 document filed is displayed for "Episode 1" and select it for viewing.
  27. Click [View].
  28. Validate the document displays as expected with the approver signature and approval comments.
  29. Click [Close All Documents] and close the form.
  30. Access the 'Move Selected Data' CWS form.
  31. Select "Client" in the 'Entity Database' field.
  32. Select "Progress Notes (Group and Individual)" in the 'Form' field.
  33. Select "Client A" in the 'Old Entity' field.
  34. Select "Episode 1" in the 'Old Episode' field.
  35. Click [Select Row to be Moved].
  36. Select the record filed in the previous steps and click [OK].
  37. Validate a message is displayed stating: Warning!! The selected row is marked as "Final" and is associated with a finalized document. This row can only be moved to a different episode of the same entity.
  38. Click [OK].
  39. Select "Client A" in the 'New Entity' field.
  40. Select "Episode 2" in the 'New Episode' field.
  41. Enter the desired value in the 'Reason for Moving Data' field.
  42. Click [Submit].
  43. Validate the 'Confirm Document' dialog is displayed.
  44. Click [Accept].
  45. Enter the password for the logged in user in the 'Password' field and click [Verify].
  46. Enter the desired comments in the 'Approval Comments' field and click [OK].
  47. Access the 'Clinical Document Viewer' form.
  48. Select "Client" in the 'Select Type:' field.
  49. Select "Individual" in the 'Select All or Individual Client' field.
  50. Select "Client A" in the 'Select Client' field.
  51. Click [Process].
  52. Validate the document filed is displayed for "Episode 2" and select it for viewing.
  53. Click [View].
  54. Validate the document displays as expected with the initial approver's signature and approval comments, information from 'Move Selected Data', and the appending author's signature and approval comments.
  55. Click [Close All Documents] and close the form.
Scenario 2: Move Selected Data [PM] - Move data from one episode to another when document routing is enabled
Specific Setup:
  • Must have a PM modeled form defined with a 'Draft/Final' field (Form A).
  • A client is enrolled in two existing episodes (Client A).
Steps
  1. Access the 'Document Routing Setup' form.
  2. Select "Avatar PM" in the 'Application' field.
  3. Click [Select Form].
  4. Select "Form A" in the 'Select a form to enable Document Routing' field and click [OK].
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Select "Yes" in the 'Allow Comments During Approval' field.
  7. Click [File] and close the form.
  8. Select "Client A" and access "Form A".
  9. Select "Episode 1" and click [OK].
  10. Populate all required and desired fields.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit].
  13. Validate the 'Confirm Document' dialog is displayed.
  14. Click [Accept].
  15. Enter the password for the logged in user in the 'Password' field and click [Verify].
  16. Enter the desired comments in the 'Approval Comments' field and click [OK].
  17. Access the 'Clinical Document Viewer' form.
  18. Select "Client" in the 'Select Type:' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Select "Client A" in the 'Select Client' field.
  21. Click [Process].
  22. Validate the document filed is displayed for "Episode 1" and select it for viewing.
  23. Click [View].
  24. Validate the document displays as expected with the approver signature and approval comments.
  25. Click [Close All Documents] and close the form.
  26. Access the 'Move Selected Data' PM form.
  27. Select "Client" in the 'Entity Database' field.
  28. Select "Form A" in the 'Form' field.
  29. Select "Client A" in the 'Old Entity' field.
  30. Select "Episode 1" in the 'Old Episode' field.
  31. Click [Select Row to be Moved].
  32. Select the record filed in the previous steps and click [OK].
  33. Validate a message is displayed stating: Warning!! The selected row is marked as "Final" and is associated with a finalized document. This row can only be moved to a different episode of the same entity.
  34. Click [OK].
  35. Select "Client A" in the 'New Entity' field.
  36. Select "Episode 2" in the 'New Episode' field.
  37. Enter the desired value in the 'Reason for Moving Data' field.
  38. Click [Submit].
  39. Validate the 'Confirm Document' dialog is displayed.
  40. Click [Accept].
  41. Enter the password for the logged in user in the 'Password' field and click [Verify].
  42. Enter the desired comments in the 'Approval Comments' field and click [OK].
  43. Access the 'Clinical Document Viewer' form.
  44. Select "Client" in the 'Select Type:' field.
  45. Select "Individual" in the 'Select All or Individual Client' field.
  46. Select "Client A" in the 'Select Client' field.
  47. Click [Process].
  48. Validate the document filed is displayed for "Episode 2" and select it for viewing.
  49. Click [View].
  50. Validate the document displays as expected with the initial approver's signature and approval comments, information from 'Move Selected Data', and the appending author's signature and approval comments.
  51. Click [Close All Documents] and close the form.
Integrated eSignature - Append Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • Ambulatory Progress Notes
Scenario 1: Integrated eSignature - Append Documents
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form and an approver is not required.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field' field.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Navigate to the 'Pending eSignatures' widget.
  13. Validate a row is displayed for the eSignature request sent for "Client A".
  14. Access Crystal Reports or other SQL Reporting tool.
  15. Create a report using the 'DocR.esignature' SQL table.
  16. Validate a row is displayed for the eSignature request sent for "Client A".
  17. Validate the 'eSignature_status' field contains "Pending".
  18. Log in to myHealthPointe for "Client A".
  19. Select the "Documents Awaiting Signature" section.
  20. Validate the document sent for eSignature is displayed.
  21. Click [Sign and Submit].
  22. Enter an eSignature in the 'Enter the Signature' field.
  23. Click [Sign and Submit].
  24. Validate the document is no longer displayed.
  25. Navigate to the 'Pending eSignatures' widget.
  26. Validate the row is no longer displayed for "Client A".
  27. Access Crystal Reports or other SQL Reporting tool.
  28. Refresh the report using the 'DocR.esignature' SQL table.
  29. Validate the 'eSignature_status' field now contains "Approved".
  30. Close the report.
  31. Access the 'Append Documents' form.
  32. Select the note type associated to the 'Progress Notes (Group and Individual)' form in the 'Form Type' field.
  33. Select "Client A" in the 'Entity' field.
  34. Enter the current date in the 'From Date' and 'To Date' fields.
  35. Select the progress note filed in the previous steps in the 'List of Documents' field.
  36. Click [Display Document].
  37. Validate the document displays with the signature for "Client A" appended to the bottom right corner.
  38. Click [Close All Documents and Exit].
  39. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field.
  40. Click [Submit].
  41. Validate a 'Confirm Document' dialog is displayed.
  42. Validate the document is displayed with the signature for "Client A" in the bottom right corner and the new comments appended to the end of the original document.
  43. Click [Accept].
  44. Enter the password for the logged in user in the 'Password' field and click [Verify].
  45. Access the 'Clinical Document Viewer' form.
  46. Select "Client" in the 'Select Client:' field.
  47. Select "Individual" in the 'Select All or Individual Client' field.
  48. Select "Client A" in the 'Select Client' field.
  49. Click [Process].
  50. Validate two document rows are displayed for the client:
  51. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  52. One 'Document Description' contains "Progress Notes (Group and Individual)" - this is the finalized progress notes form finalized via document routing.
  53. Select both documents for viewing and click [View].
  54. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  55. Validate the "Progress Notes (Group and Individual)" finalized document displays the document with the author's signature, the signature for "Client A" in the bottom right corner, and the new comments appended to the end of the original document.
  56. Click [Close All Documents] and close the form.
'Add Non-User Signature' - Appending Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • Add Non-User Signature (PM)
  • Clinical Document Viewer
Scenario 1: Progress Notes - Validate 'Add Non-User Signature' functionality
Specific Setup:
  • A client is enrolled in an existing outpatient episode (Client A).
Steps
  1. Access the 'Document Routing Setup' form.
  2. Select "Avatar CWS" in the 'Application' field.
  3. Click [Select Form].
  4. Select "Ambulatory Progress Notes" in the 'Select a form to enable Document Routing' field and click [OK].
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Select "No" in the 'Use Crystal Report Template' field.
  7. Click [File] and close the form.
  8. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  9. Select "Independent Note" in the 'Progress Note For' field.
  10. Select the desired value in the 'Note Type' field.
  11. Enter the desired value in the 'Notes Field' field.
  12. Select "Final" in the 'Draft/Final' field.
  13. Click [Submit].
  14. Validate a 'Confirm Document' dialog is displayed.
  15. Click [Accept].
  16. Enter the password associated to the logged in user and click [Verify].
  17. Access the 'Document Routing Setup' form.
  18. Select "Avatar CWS" in the 'Application' field.
  19. Click [Select Form].
  20. Select "Ambulatory Progress Notes" in the 'Select a form to enable Document Routing' field and click [OK].
  21. Select "Yes" in the 'Use Crystal Report Template' field.
  22. Select the desired crystal report template in the 'Crystal Report' field.
  23. Click [File] and close the form.
  24. Access the 'Add Non-User Signature' form.
  25. Select the form type for 'Ambulatory Progress Notes' in the 'Form Type' field.
  26. Select "Client A" in the 'Entity' field.
  27. Enter the current date in the 'From Date' and 'To Date' fields.
  28. Select the progress note filed in the previous steps in the 'List of Option Documents and Snapshots' field.
  29. Click [Display Document].
  30. Validate the document is displayed as expected.
  31. Click [Close All Documents and Exit].
  32. Enter the desired value in the 'Comments' field.
  33. Click [Sign].
  34. Sign in the 'Please Sign Below' dialog and click [OK].
  35. Validate the signature is displayed.
  36. Click [Submit].
  37. Validate a 'Confirm Document' dialog is displayed.
  38. Validate the document preview displays as expected and the non-user signature is appended to the end of the document.
  39. Click [Accept].
  40. Enter the password associated to the logged in user and click [Verify].
  41. Close the form.
  42. Access the 'Clinical Document Viewer' form.
  43. Select "Client" in the 'Select Type:' field.
  44. Select "Individual" in the 'Select All or Individual Client' field.
  45. Select "Client A" in the 'Select Client' field.
  46. Click [Process].
  47. Validate the document filed is displayed and select it for viewing.
  48. Click [View].
  49. Validate the document displays as expected with the non-user signature appended to the end of the document.
  50. Click [Close All Documents] and close the form.
Scenario 2: Treatment Plan - Validate 'Add Non-User Signature' functionality
Specific Setup:
  • A client is enrolled in an existing outpatient episode (Client A).
Steps
  1. Access the 'Document Routing Setup' form.
  2. Select "Avatar CWS" in the 'Application' field.
  3. Click [Select Form].
  4. Select "Treatment Plan" in the 'Select a form to enable Document Routing' field and click [OK].
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Select "No" in the 'Use Crystal Report Template' field.
  7. Click [File] and close the form.
  8. Select "Client A" and access the 'Treatment Plan' form.
  9. Enter the desired date in the 'Plan Date' field.
  10. Enter the desired value in the 'Plan Name' field.
  11. Select the desired value in the 'Plan Type' field.
  12. Populate all required and desired fields.
  13. Select "Final" in the 'Treatment Plan Status' field.
  14. Click [Submit].
  15. Validate a 'Confirm Document' dialog is displayed.
  16. Click [Accept].
  17. Enter the password associated to the logged in user and click [Verify].
  18. Access the 'Document Routing Setup' form.
  19. Select "Avatar CWS" in the 'Application' field.
  20. Click [Select Form].
  21. Select "Treatment Plan" in the 'Select a form to enable Document Routing' field and click [OK].
  22. Select "Yes" in the 'Use Crystal Report Template' field.
  23. Select the desired crystal report template in the 'Crystal Report' field.
  24. Click [File] and close the form.
  25. Access the 'Add Non-User Signature' form.
  26. Select the form type for 'Treatment Plan' in the 'Form Type' field.
  27. Select "Client A" in the 'Entity' field.
  28. Enter the current date in the 'From Date' and 'To Date' fields.
  29. Select the treatment plan filed in the previous steps in the 'List of Option Documents and Snapshots' field.
  30. Click [Display Document].
  31. Validate the document is displayed as expected.
  32. Click [Close All Documents and Exit].
  33. Enter the desired value in the 'Comments' field.
  34. Click [Sign].
  35. Sign in the 'Please Sign Below' dialog and click [OK].
  36. Validate the signature is displayed.
  37. Click [Submit].
  38. Validate a 'Confirm Document' dialog is displayed.
  39. Validate the document preview displays as expected and the non-user signature is appended to the end of the document.
  40. Click [Accept].
  41. Enter the password associated to the logged in user and click [Verify].
  42. Close the form.
  43. Access the 'Clinical Document Viewer' form.
  44. Select "Client" in the 'Select Type:' field.
  45. Select "Individual" in the 'Select All or Individual Client' field.
  46. Select "Client A" in the 'Select Client' field.
  47. Click [Process].
  48. Validate the document filed is displayed and select it for viewing.
  49. Click [View].
  50. Validate the document displays as expected with the non-user signature appended to the end of the document.
  51. Click [Close All Documents] and close the form.
Topics
• NX • Integrated eSignature • Registry Settings • Perceptive • Move Selected Data • Clinical Document Viewer • Progress Notes • Add Non-User Signature • Treatment Plan
Update 34 Summary | Details
eMAR Downtime reports
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Forms Definition
  • FTP Setup
  • eMAR Downtime Automation
Scenario 1: NX - eMAR Downtime Automation - 7 Day Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (7 day grid)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 7 day grid"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "Military".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "Yes"
  • 'Include Future-Discontinued Orders' = "Yes"
  • An active 'SFTP - Password' configuration must exist for the server where the application resides that communicates with the FTP server.
  • An active configuration must exist for the 'Administration Record - 7 day grid' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "No"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "Yes"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Send File to FTP Server' = "Yes"
  • 'FTP Definition' = the definition configured for "SFTP - Password" in the 'FTP Setup' form.
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate a file is displayed in the following format: YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'. (ex. 2023-05-31_1036_7 day Administration Record)
  3. Open the pdf and validate that the 'Administration Record - 7 day grid' report is displayed and contains the following:
  4. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
  9. Access the FTP server and access the directory where the pdf's will be stored.
  10. Validate a file is displayed in the following format: YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'. (ex. 2023-05-31_1036_7 day Administration Record)
  11. Open the pdf and validate that the 'Administration Record - 7 day grid' report is displayed and contains the following:
  12. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  13. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  14. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  15. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  16. Close the report and log off of the server.
Scenario 2: NX - eMAR Downtime Automation - 1 Day Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (1 day grid)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 1 day"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "AM/PM".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Programs"
  • 'Include All Programs' = "No"
  • 'Outpatient/Partial Hospitalization Programs to Include' = "(302) O.P. Adult Psych", "(303) O.P. Mature Adult Psych", and "(307) O.P. Mature Adult S.A".
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "5"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • The user logged into the application must have their action require validation. (User A)
  • Three clients must have active episodes for the following programs with qualifying orders:
  • "(302) O.P. Adult Psych" (Client A)
  • "(303) O.P. Mature Adult Psych" (Client B)
  • "(307) O.P. Mature Adult S.A" (Client C)
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there are 3 files, one for every Outpatient and Partial Hospitalization program that was selected that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult Psych_2023-06-06_1638_1 Day Administration Record).
  3. Open one of the pdf's and validate that the 'Administration Record - 1 Day' report is displayed and contains the following:
  4. Validate that the pdf will contain all clients in that program sorted in alphabetical order by client's last name, first name.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
Scenario 3: NX - eMAR Downtime Automation - Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "24-Hr (colon)".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "Yes"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "By Unit or Program, then by Room/Bed (for Units) or alphabetically by Client Name (for Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Both"
  • 'Include All Units' = "Yes"
  • 'Include All Programs' = "Yes"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there are files for every unit that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex.1East_2023-06-01_1038_Administration Record).
  3. Validate there are files for every Outpatient and Partial Hospitalization program that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult Psych_2023-06-01_1038_Administration Record).
  4. Open one of the pdf's and validate that the 'Administration Record' report is displayed and contains the following:
  5. Validate that the pdf for units will contain all clients in that unit and then sorted in Room/Bed order.
  6. Validate that the pdf for programs will contain all client in that program sorted in alphabetical order by client's last name, first name.
  7. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  8. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  9. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  10. Close the report and log off of the server.
Scenario 4: NX - eMAR Downtime Automation - 1 Day Alt Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (1 day grid Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 1 Day Alternate"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "AM/PM".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "Yes"
  • 'Incl. Exp. Orders For How Many Days Past Order's Stop Date' = "5"
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "By Unit or Program, then alphabetically by Client Name"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "No"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "No"
  • 'Units to Include' = "(1E) 1East" and "(1N) 1North"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there is one pdf that contains clients with qualifying orders in the following format "YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 2023-06-06_1638_1 Day Administration Record - Alternate).
  3. Open the pdf and validate that the 'Administration Record - 1 Day Alternate' report is displayed and contains the following:
  4. Validate that the pdf will contain all clients in the two units selected, sorted in alphabetical order by client's last name, first name.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
Scenario 5: eMAR Downtime Automation - 7 Day Alt Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (7 day grid Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 7 Day Alt"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "Military"
  • 'Include Routine / PRN / STAT/ Other' = all values checked
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "Yes"
  • 'Incl. Exp. Orders For How Many Days Past Order's Stop Date' = "5"
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active 'SFTP - Key Pair' configuration must exist for the server where the application resides that communicates with the FTP server.
  • An active configuration must exist for 'Administration Record - 7 Day Alt' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "No"
  • 'Units to Include' = "1North"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Send File to FTP Server' = "Yes"
  • 'FTP Definition' = the definition configured for "SFTP - Key Pair" in the 'FTP Setup' form.
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate a file is displayed in the following format: "Units selected_YYYY-MM-DD_time in military format_Form Description name" set up in 'Order Entry Forms Definition'. (ex.1North_2023-05-31_1651_Administration Record - 7 Day Alternate)
  3. Open the pdf and validate that the 'Administration Record - 7 Day Alt' report is displayed and contains the following:
  4. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
  9. Access the FTP server and access the directory where the pdf's will be stored.
  10. Validate a file is displayed in the following format: "Units selected_YYYY-MM-DD_time in military format_Form Description name" set up in 'Order Entry Forms Definition'. (ex.1North_2023-05-31_1651_Administration Record - 7 Day Alternate)
  11. Open the pdf and validate that the 'Administration Record - 7 Day Alt' report is displayed and contains the following:
  12. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  13. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  14. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  15. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  16. Close the report and log off of the server.
Scenario 6: NX - eMAR Downtime Automation - Administration Record Alternate
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - Alternate"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "Military".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Both"
  • 'Include All Units' = "No"
  • 'Units to Include' = "(1N) 1North"
  • 'Include All Programs' = "No"
  • 'Programs to Include' = "(306) O.P. Adult S.A."
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there is a file for the unit selected (1North) that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 1North_2023-05-30_1039_Administration Record - Alternate).
  3. Validate there is a file for every the program selected (O.P. Adult S.A.) that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult S.A._2023-05-30_1039_Administration Record - Alternate).
  4. Open one of the pdf's and validate that the 'Administration Record - Alternate' report is displayed and contains the following:
  5. Validate that the pdf for units will contain all clients in that unit and then sorted in Room/Bed order.
  6. Validate that the pdf for programs will contain all client in that program sorted in alphabetical order by client's last name, first name.
  7. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  8. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  9. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  10. Close the report and log off of the server.
  11. After 2 days and after the 'eMAR Downtime Automation' task has run for the day,
  12. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  13. Validate the "1North_2023-06-01_1039_Administration Record - Alternate" and "O.P. Adult S.A._2023-06-01_1039_Administration Record - Alternate" files are no longer displayed.
  14. Validate there is a new file for the unit selected (1North) that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 1North_2023-06-01_1039_Administration Record - Alternate)
  15. Validate there is a file for every the program selected (O.P. Adult S.A.) that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult S.A._2023-06-01_1039_Administration Record - Alternate)
Topics
• NX • eMAR Downtime Automation
Update 36 Summary | Details
Perceptive - Scanning/Importing Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Batch Capture and Indexing
  • Chart Review
  • Clinical Document Viewer
  • Client Document Capture
  • Document Capture
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: Perceptive Individual Scanning/Importing/Viewing/Printing Workflow - Client Terminology Modified
Specific Setup:
  • Test only in Perceptive enabled environments.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client and episode.
  3. Open the "Document Management" form within Chart.
  4. Scan a document.
  5. Assign the document to a particular "Document Type".
  6. Save the document.
  7. Open the "Document Management" form within Chart.
  8. Import a document.
  9. Assign the document to a particular "Document Type".
  10. Save the document.
  11. Navigate to the section designated by the "Document Type" the document was saved under.
  12. Navigate to the "Episode" tab.
  13. Open the document(s).
  14. Validate the document(s) can be viewed and display as scanned.
  15. Validate the document(s) can be printed and display as scanned.
  16. Close the document.
  17. Open the "Clinical Document Viewer".
  18. Select the desired client and episode.
  19. Locate the document(s) that were just scanned in or imported.
  20. Validate the document(s) can be viewed and display as scanned.
  21. Validate the document(s) can be printed and display as scanned.
  22. Close the form.
Scenario 5: 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.
Document Management Definition - Duplicate Forms created
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Document Capture
  • Clinical Document Viewer
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field
  6. Select the desired entity in the "Entity" field
  7. Populate any other desired fields in the "Form" section
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report"
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section
  19. Click [File].
  20. Validate the form files successfully
  21. Click [Select Form].
  22. Select the form just submitted in 5
  23. Validate all fields populated in steps 1 thru 5, are populated as expected
  24. Click back to the [Form] section
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list
  29. Click [Select Form].
  30. Select the form "Inbox Attachments"
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed."
  33. Click [OK]
  34. Click [Select Form].
  35. Select the form "Results Document"
  36. Click [Delete]
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed."
  38. Click [OK]
  39. Close the form
Scenario 2: Document Management Definition - Perceptive Syncing Form Definitions in Multiple Server environment
Specific Setup:
  • To be tested in a multiple server environment that has multiple root system codes.
  • Using the "Document Management Definition" form:
  • Identify a form that exists in all system codes.
Steps
  1. Using the "Document Management Definition" form
  2. Edit the existing form identified as existing in all root system codes.
  3. File t he form.
  4. Open the "Client Document Capture" form.
  5. Scan or import a document.
  6. Select the form edited in "Document Management Definition".
  7. Scan or import the document.
  8. Using "Clinical Document Viewer", select the test client.
  9. Validate the document that was just filed for the form that exists in all root system codes displays as it was previously filed.
Topics
• Document Scan/Import • Document Import/Scan • Document Management • NX
Update 37 Summary | Details
'Create New Treatment Plan' process - Registry Setting creation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Create New Treatment Plan
  • Registry Settings (CWS)
  • Treatment Plan
Scenario 1: Create a new copy of the 'Treatment Plan' form using 'Create New Treatment Plan'
Steps
  1. Access the 'Create New Treatment Plan' form.
  2. Enter the desired value in the 'Treatment Plan Name' field.
  3. Select the desired value in the 'Episode Required' field.
  4. Click [Submit].
  5. Validate a message is displayed stating: Are you sure you want to create a new copy of the Treatment Plan?
  6. Click [Yes].
  7. Validate a message is displayed indicating the Treatment Plan form has been created.
  8. Click [OK] and close the form.
  9. Access the 'Registry Settings' form.
  10. Enter "Level of Care" in the 'Limit Registry Settings to the Following Search Criteria' field.
  11. Click [View Registry Settings].
  12. Validate the 'Enable Level of Care Functionality' registry setting is displayed for all 'Treatment Plan' forms, including the newly created 'Treatment Plan' copy.
  13. Close the form.
Topics
• Registry Settings • Treatment Plan
Update 38 Summary | Details
State Form Definition - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Definition
  • State Form File Generation
Scenario 1: State Form Definition - Field and data validation's
Specific Setup:
  • Have a "State Form Definition" file [TestFile] created based on a table [TestTable] that contains two or more numerical fields and any other fields
  • For this test, numerical fields [FieldA], [FieldB] and [FieldC] exist and are set to display data when the file is generated
  • Have access to the form [TestForm] where data can filed in table [TestTable]
  • Have access to form "State Form Definition" and "State Form File Generation"
  • An active client [TestClient] exists on the system
Steps
  1. Open [TestForm]
  2. Select [TestClient]
  3. Set [FieldA] to a desired value. For this test "10"
  4. Set [FieldB] to a desired value. For this test "20"
  5. Set [FieldC] to a desired value. For this test "5"
  6. Populate any other desired fields
  7. Submit the form
  8. Open the 'State Form Definition' form
  9. Select "Existing" in the 'New or Existing' field
  10. Select the [TestFile] from the 'Select State Form' field drop down list
  11. Click the [Record Definition] section
  12. Select "Update" in the "Add or Update Record" field
  13. Select the existing record in the "Select Record" field
  14. Click [Define Record Data Elements]
  15. Click [New Row]
  16. In the "Element Name" field, enter a description of a math function to perform using the numerical fields stated in the set up fields in the file.
  17. For this test, "Add fields FieldA, FieldB subtract FieldC" is entered
  18. Tab over to the "SQL Generated Data" field
  19. Add a math function to accomplish the result
  20. For this example, the following expression would be used:
  21. MATH(MATH(p.FIELDA,p.FIELDB,'+'),p.FIELDC,'-')
  22. Click [New Row] again to add another math function
  23. In the "Element Name" field, enter a description of another math function to perform using the numerical fields stated in the set up fields in the file.
  24. For this test, "Multiply fields FieldA and FieldB divide by FieldC" is entered
  25. Tab over to the "SQL Generated Data" field
  26. Add a math function to accomplish the result
  27. For this example, the following expression would be used.
  28. MATH(MATH(p.FIELDA,p.FIELDB,'*'),p.FIELDC,'/')
  29. Click [Save] to save the changes
  30. Click [File Record]
  31. Click back to the "State Form Definition" section
  32. Click [File Form]
  33. Validate the definition files successfully
  34. Open form "State Form File Generation"
  35. In the "State Form" field, select [TestFile]
  36. Select the "Compile" button in the "File Generations Options" field
  37. Click [Process]
  38. Click [OK] at the "Compile Complete" message
  39. Select the "Dump File" button in the "File Generations Options" field
  40. Click [Process]
  41. The "RADplus_SF_File_Dump" report will display
  42. Locate the record row for [TestClient]
  43. Validate the resulting value for the math calculation set up in step 2g is correct.
  44. For this test (10+20-5), the expected result would be "15"
  45. Validate the resulting value for the math calculation set up in step 2h is correct.
  46. For this test (10 x 20 divided by 5), the result would be "40"
Scenario 2: State Form Definition -Validate 'Automatically Purge Posted Compiles' with "Days To Save Compile Data" set to "0"
Specific Setup:
  • Have a state form definition file created [SFfile] in form "State Form Definition" that has not yet been complied in form "State Form File Definition"
Steps
  1. Open the 'State Form Definition' form
  2. Select 'Existing' in the 'New or Existing' field
  3. Select the [SFfile]
  4. Scroll to the bottom of the form
  5. Set the 'Days to Save Compile Data' field to "0".
  6. Navigate to the 'Definition Options' field. Click the help message icon next to field label.
  7. Validate message includes information regarding the "Automatically Purge Posted Compiles" selection that states, If selected, compiles automatically deleted based on the selection in the 'Days To Save Compile Data' field value will "also" delete Posted files (where a file has been generated on server)
  8. Leave the 'Automatically Purge Posted Compiles' selection, not selected
  9. File the definition
  10. Open the 'State Form File Generation' form
  11. Select the [SFfile]
  12. Select "Compile" in the "File Generations Options" field
  13. Click [Process] to create the compile. [CompileA]
  14. Validate "Process Complete" is displayed
  15. Click to [Dump the File] in the "File Generations Options" field
  16. Click [Process].
  17. Validate the dump file report displays data
  18. Repeat step 4b to compile another file. [CompileB]
  19. Click the "Select File" dropdown to view the compiles
  20. Validate [CompileA] is not present as expected, as prompt 'Days to Save Compile Data' field was set to "0".
  21. Validate the new compile [CompileB], is available for selection
  22. Select [CompileB]
  23. Select "Create File on Server" in the "File Generations Options" field
  24. Click [Process].
  25. Validate "Process Complete" is displayed
  26. Repeat step 8b to create another compile. [CompileC]
  27. Click the 'Select File" dropdown to view the compiles
  28. Validate the new compile is present [CompileC]
  29. Validate [CompileB] the one created on the server is present as well as expected, since prompt 'Automatically Purge Posted Compiles' was not selected in step 3d
  30. Re-open the 'State Form Definition' form
  31. Select the [SFfile] for edit
  32. Navigate to the 'Definition Options' field
  33. This time select the 'Automatically Purge Posted Compiles' selection
  34. File the definition
  35. Return to the 'State Form File Generation' form
  36. Select the [SFfileA]
  37. Select "Compile" in the "File Generations Options" field
  38. Click [Process] to create another compile. [CompileD]
  39. Validate "Process Complete" is displayed
  40. Click the 'Select File" dropdown to view the compiles
  41. Validate the new compile is present [CompileD]
  42. Validate [CompileC] is not present as 'Days to Save Compile Data' field to "0".
  43. Validate [CompileB] the one created on the server is also not present this time, since prompt 'Automatically Purge Posted Compiles' was selected in step 5
Scenario 3: State Form Definition -Validate 'Automatically Purge Posted Compiles' with "Days To Save Compile Data" greater than "0"
Specific Setup:
  • Have a state form definition file created [SFfile] in form "State Form Definition" that has not yet been complied in form "State Form File Definition"
Steps
  1. Open the 'State Form Definition' form
  2. Select 'Existing' in the 'New or Existing' field
  3. Select the [SFfile]
  4. Scroll to the bottom of the form
  5. Set the 'Days to Save Compile Data' field to any value greater than "0".
  6. Navigate to the 'Definition Options' field. Click the help message icon next to field label.
  7. Validate message includes information regarding the "Automatically Purge Posted Compiles" selection that states, If selected, compiles automatically deleted based on the selection in the 'Days To Save Compile Data' field value will "also" delete Posted files (where a file has been generated on server)
  8. Leave the 'Automatically Purge Posted Compiles' selection, not selected
  9. File the definition
  10. Open the 'State Form File Generation' form
  11. Select the [SFfile]
  12. Select "Compile" in the "File Generations Options" field [CompileA]
  13. Click [Process] to create the compile [CompileA]
  14. Validate "Process Complete" is displayed
  15. Click to [Dump the File] in the "File Generations Options" field
  16. Click [Process].
  17. Validate the dump file report displays data
  18. Repeat step 4b to compile the file again, to create another compile [CompileB]
  19. Click the "Select File" dropdown to view the compiles
  20. Validate [CompileA] is present as expected, as prompt 'Days to Save Compile Data' field was set to greater than "0".
  21. Validate the new compile [CompileB], is also available for selection
  22. Select [CompileB]
  23. Select "Create File on Server" in the "File Generations Options" field
  24. Click [Process]. Validate "Process Complete" is displayed
  25. Repeat step 8b to compile the file again to create another compile [CompileC]
  26. Click the "Select File" dropdown to view the compiles
  27. Validate the new compile is present [CompileC]
  28. Validate [CompileA] is still present
  29. Validate [CompileB] the one created on the server is present as well as expected, since prompt 'Automatically Purge Posted Compiles' was not selected in step 3d
  30. Re-open the 'State Form Definition' form
  31. Select the [SFfile] for edit
  32. Navigate to the 'Definition Options' field
  33. This time select the 'Automatically Purge Posted Compiles' selection
  34. File the definition
  35. Return to the 'State Form File Generation' form
  36. Select the [SFfile]
  37. Select "Compile" in the "File Generations Options" field
  38. Click [Process] to create the new compile. [CompileD]
  39. Validate "Process Complete" is displayed
  40. Click the "Select File" dropdown to view the compiles
  41. Validate the new compile is present [CompileD]
  42. Validate [CompileA], [CompileB] and [CompileC] are also still present, since the 'Days to Save Compile Data' field is set greater than "0".
Topics
• State Form Tools • NX
Update 39 Summary | Details
Widget - form launch links
Scenario 1: Validate data in Widgets enabled with "Enhanced Widget View" functionality
Specific Setup:
  • [TestClientA] has a row [RowA] submitted in a "Progress Notes" form [TestForm]. For this test form "Progress Notes (Group and Individual)" is used
  • [TestClientB] does not have a row filed yet in [TestForm]
  • Have the following widgets created to display "Progress Notes" data in the "SYSTEM.cw_patient_notes" table
  • [WidgetA] created in form "Widget Definition" with prompt "Enhanced Widget View" set to "Yes"
  • [WidgetB] created in form "Widget Wizard" with prompt "Enhanced Widget View" set to "Yes"
  • Each widget includes the field "NOT_uniqueid", which is configured as a link that will launch [TestForm] and populate the form with the data filed in [RowA]
  • Logged in user has all widgets set up on their home view or alternate view
Steps
  1. At the home view, select [TestClientA]
  2. Validate [WidgetA] is populated with the expected column data filed in [RowA] for form [TestForm]
  3. Verify each column has "Up/Down" arrows and a "Search" filter box below each column name, indicative that enhanced widget functionality is enabled for the widget as expected
  4. Click the highlighted data link in column "NOT_uniqueid"
  5. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  6. Close the form, to return to the home view
  7. Validate [WidgetB] is populated with the expected column data filed in [RowA] for form [TestForm]
  8. Verify each column does "not" have "Up/Down" arrows and a "Search" filter box below each column name as expected, indicative that enhanced widget functionality is "not" enabled for the widget
  9. Click the highlighted data link in column "NOT_uniqueid"
  10. Validate [TestForm] is launched and contains the expected data filed for [RowA]
  11. Close the form, to return to the home view
  12. At the home view, select [TestClientB]
  13. Open [TestForm]
  14. Populate all the desired fields and submit the row [RowA] for [TestClientB]
  15. At the home view, select [TestClientB]
  16. Validate [WidgetA] is populated with the expected column data filed in [RowA] for form [TestForm]
  17. Verify each column has "Up/Down" arrows and a "Search" filter box below each column name, indicative that enhanced widget functionality is enabled for the widget as expected
  18. Click the highlighted data link in column "NOT_uniqueid"
  19. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  20. Close the form, to return to the home view
  21. Validate [WidgetB] is populated with the expected column data filed in [RowA] for form [TestForm]
  22. Click the highlighted data link in column "NOT_uniqueid"
  23. Validate [TestForm] is launched and contains the expected data filed for [RowA]
  24. Close the form, to return to the home view
Scenario 2: Validate data in Widgets 'not' enabled with "Enhanced Widget View" functionality
Specific Setup:
  • [TestClientA] has a row [RowA] submitted in a '"Progress Notes" form [TestForm]. For this test form "Progress Notes (Group and Individual)" is used
  • [TestClientB] does not have a row filed yet in [TestForm]
  • Have the following widgets created to display "Progress Notes" data in the "SYSTEM.cw_patient_notes" table
  • [WidgetA] created in form "Widget Definition" with prompt "Enhanced Widget View" set to "No"
  • [WidgetB] created in form "Widget Wizard" with prompt "Enhanced Widget View" set to "No"
  • Each widget includes the field "NOT_uniqueid", which is configured as a link that will launch [TestForm] and populate the form with the data filed in [RowA]
  • Logged in user has all widgets set up on their home view or alternate view
Steps
  1. At the home view, select [TestClientA]
  2. Validate [WidgetA] is populated with the expected column data filed in [RowA] for form [TestForm]
  3. Verify each column does "not" have "Up/Down" arrows and a "Search" filter box below each column name indicative that enhanced widget functionality is "not" enabled for the widget, as expected
  4. Click the highlighted data link in column "NOT_uniqueid"
  5. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  6. Close the form, to return to the home view
  7. Validate [WidgetB] is populated with the expected column data filed in [RowA] for form [TestForm]
  8. Verify each column does "not" have "Up/Down" arrows and a "Search" filter box below each column name as expected, indicative that enhanced widget functionality is "not" enabled for the widget
  9. Click the highlighted data link in column "NOT_uniqueid"
  10. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  11. Close the form, to return to the home view
  12. At the home view, select [TestClientB]
  13. Open [TestForm]
  14. Populate all the desired fields and submit row [RowA] for [TestClientB]
  15. At the home view, select [TestClientB]
  16. Validate [WidgetA] is populated with the expected column data filed in [RowA] for form [TestForm]
  17. Verify each column does "not" have "Up/Down" arrows and a "Search" filter box below each column name, indicative that enhanced widget functionality is "not" enabled for the widget as expected
  18. Click the highlighted data link in column "NOT_uniqueid"
  19. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  20. Close the form, to return to the home view
  21. Validate [WidgetB] is populated with the expected column data filed in [RowA] for form [TestForm]
  22. Click the highlighted data link in column "NOT_uniqueid"
  23. Validate [TestForm] is launched and contains the expected data filed in [RowA]
  24. Close the form, to return to the home view
ScriptLink - Multiple Iteration Grids
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • TestFormA (Modeled form with Multiple Iteration Table)
Scenario 1: Validate a "ScriptLink" script is triggered on a forms containing a "Multiple Iteration" grid
Specific Setup:
  1. Have a modeled form [TestForm] that contains a "Multiple Iteration" section on the form
  2. The "Multiple Iteration" section contains a "Scrolling Text Field" and any other desired field types
  3. Have any "ScriptLink" script imported in the section containing the "Multiple Iteration" grid. For this example, a script is used that will display a test warning when a value is entered in a specific field [FieldA]
Steps
  1. Open form [TestFormA] and select a desired client [TestClient]
  2. Click to the main section of the form
  3. Populate all the desired fields in that section
  4. Click to the "Multiple Iteration Section"
  5. Click to add the first row to the grid
  6. Populate the "Scrolling Text Field" with the desired text [TextFirstRow]
  7. Navigate to [FieldA] and enter a value
  8. Validate the "ScriptLink" script is triggered and warning message is displayed and click [OK]
  9. Populate any other desired fields in the section
  10. Click to add the second row to the grid
  11. Populate the "Scrolling Text Field" with the desired text [TextSecondRow]
  12. Navigate to [FieldA] and enter a value
  13. Validate the "ScriptLink" script is triggered and warning message is displayed and click [OK]
  14. Populate any other desired fields in the section
  15. Click to add the third row to the grid
  16. Populate the "Scrolling Text Field" with the desired text [TextThridRow]
  17. Navigate to [FieldA] and enter a value
  18. Validate the "ScriptLink" script is triggered and warning message is displayed and click [OK]
  19. Populate any other desired fields in the section
  20. Submit the form
  21. Return to form [TestForm] and select [TestClient]
  22. Select the row filed in step 1 for edit
  23. Click to the main section of the form
  24. Validate all the other fields are populated as expected
  25. Click to the "Multiple Iteration Section"
  26. Select the first row to the grid and click [Edit]
  27. Validate the "Scrolling Text Field" is populated with [TextFirstRow] populated in step 1
  28. Validate all the other fields are populated as expected
  29. Select the second row to the grid and click [Edit]
  30. Validate the "Scrolling Text Field" is populated with [TextSecondRow] populated in step 1
  31. Validate all the other fields are populated as expected
  32. Select the third row to the grid and click [Edit]
  33. Validate the "Scrolling Text Field" is populated with [TextThirdRow] populated in step 1
  34. Validate all the other fields are populated as expected
  35. Select the first row to the grid again and click [Edit]
  36. Change the text in the "Scrolling Text Field" to a new value [TextNewValue]
  37. Click the [Add] button to add a new row
  38. Populate the "Scrolling Text Field" with the desired text [TextFourthRow]
  39. Populate any other desired fields in the section
  40. Submit the form
  41. Return to form [TestForm] and select [TestClient]
  42. Click to the "Multiple Iteration Section"
  43. Select the first row to the grid and click [Edit]
  44. Validate the "Scrolling Text Field" is populated with the new text [TextNewValue] entered in step 2
  45. Select the second row to the grid and click [Edit]
  46. Validate the "Scrolling Text Field" is populated with [TextSecondRow] populated in step 1
  47. Select the third row to the grid and click [Edit]
  48. Validate the "Scrolling Text Field" is populated with [TextThirdRow] populated in step 1
  49. Select the fourth row to the grid and click [Edit]
  50. Validate the "Scrolling Text Field" is populated with [TextFourthRow] populated in step 2
Topics
• Widget Definition • Widgets • NX • Scriptlink
Update 42 Summary | Details
Client Chart - Credentialing information
Scenario 1: Chart View - Form data row validations
Specific Setup:
  • In form "Practitioner Enrollment":
  • [StaffA] and [StaffB] both have "Practitioner Credentials" added with an "Effective" date that ends after today. [CredToday]
  • In addition, [StaffA] and [StaffB] both have "Practitioner Credentials" added with an "Effective" date that starts tomorrow. [CredTomorrow]
  • Have a form [TestForm] enabled for document routing
  • [StaffB] has [TestForm] added to their "Chart" view
  • [StaffB] has the "My To Do's" widget on their home view
  • Have registry setting "Display Document Routing Status on Chart Items" set to "Yes"
  • Log in as [StaffA]
Steps
  1. Open form [TestForm]
  2. Populate any desired fields
  3. Submit the form as "Final"
  4. Click to accept and route the document
  5. At the "Route To Document" screen, add [StaffB] as the approver
  6. Submit the form to route the document
  7. Log out as [StaffA]
  8. Log in as [StaffB]
  9. Navigate to the "My To Do's" widget
  10. Locate the to sent in step 1
  11. Click to review the To Do
  12. Validate information is displayed as expected
  13. Click [Accept] to approve the To Do
  14. Navigate to the home view
  15. Select [TestClient] and double click to open their chart
  16. In "Chart", select [TestForm] from the forms list to review the record filed
  17. Validate record header data bar indicates the record was submitted by [StaffA] and based on the "Effective" date in the setup, their expected credentials [CredToday]. For example "Submitted by [StaffA] Certified Drug/Alcohol Counselor (CADC)"
  18. Validate the record data (Main Section) region contains the expected data submitted
  19. Validate the record data (Document Routing) region contains the "Approvers" field populated with [StaffB] and based on the "Effective" date in the setup, their expected credentials [CredToday]. For example "Approvers: [StaffB] Certified Pediatric Nurse (CPN)"
  20. Close Chart
  21. The following day, repeat steps 1 thru 4 again
  22. Navigate to the home view
  23. Select [TestClient] and double click to open their chart
  24. In "Chart", select [TestForm] from the forms list to review the record filed
  25. Validate record header data bar indicates the record was submitted by [StaffA] and based on the "Effective" date in the setup, their expected credentials [CredTomorrow]
  26. Validate the record data (Main Section) region contains the expected data submitted
  27. Validate the record data (Document Routing) region contains the "Approvers" field populated with [StaffB] and based on the "Effective" date in the setup, their expected credentials [CredTomorrow]
Topics
• Chart Review
Update 43 Summary | Details
Identity Manager - logins
Scenario 1: Avatar "Identity Manager" - User Login validation
Specific Setup:
  • Have a system with the "Identity Manager" module installed and configured
  • Have an active "Identity Manager" user set up in form "User Definition" [TestUser]
  • Have a query or report to display data in the "SYSTEM.radplus_audit_failed_login" table
Steps
  1. Launch the Avatar login screen
  2. Select the desired system code in the "System Code" field
  3. Populate the "Username" field with any invalid user name [InvalidUser]
  4. Populate the "Password" field with any desired password [DesiredPassword]
  5. Click [Sign In]
  6. Validate the presented with a "Sign In" dialog error message that states, "'Login Failed'.
  7. Note the current date and time and click [OK]
  8. Validate the user is returned to the login screen
  9. Run the query or report on the "SYSTEM.radplus_audit_failed_login' table.
  10. Validate the results include the failed login information for [InvalidUser] for the date and time noted in step 1
  11. Validate the "login_failed_reason" field is populated with "Invalid User"
  12. At the login screen
  13. Select the desired system code in the "System Code" field
  14. Populate the "Username" field with a valid "Identity Manager" user name [TestUser]
  15. Populate the "Password" field with an invalid password [InvalidPassword]
  16. Click [Sign In]
  17. Validate the presented with a "Sign In" dialog error message that states, "Login Failed"
  18. Note the current date and time and click [OK]
  19. Validate the user is returned to the login screen
  20. Run the query or report on the "SYSTEM.radplus_audit_failed_login" table.
  21. Validate the results include the failed login information for [TestUser], for the date and time noted in step 3
  22. Validate the "login_failed_reason" field is populated with "Invalid Password"
  23. At the login screen
  24. Select the desired system code in the "System Code" field
  25. Populate the "Username" field with the user name for user [TestUser]
  26. Populate the "Password" field with the valid password for user [TestUser]
  27. Click [Sign In]
  28. Validate the user has logged in successfully.
  29. In the "Search Forms" search box, search for any form
  30. Validate the form is launched as expected
  31. Populate any desired fields in the form
  32. Submit the form
  33. Validate submission is successful
Topics
• Identity Manager
Update 44 Summary | Details
"Registry Settings" form -
Scenario 1: Registry Settings - submitting a registry setting
Specific Setup:
  • In form "Registry Settings", have two registry settings whose current submitted value haves the following character lengths. For example the "URL" type registry setting, "ICD-10 Diagnosis Search"
  • [RegA] has a value [CurrValue] that is greater than "50" characters in length
  • [RegB] has a value [CurrValue] that is less than or equal to "50" characters in length.
Steps
  1. Access the "Registry Settings" form.
  2. In the registry settings search field, search for [RegA]
  3. Validate the "Registry Setting Value" field is populated with value [CurrValue], whose length is greater than "50" characters
  4. Change the current value to any other value greater that's greater than "50" characters [NewValue]
  5. Submit the form
  6. Validate the submission results indicate that the registry setting has been submitted successfully
  7. Click "Yes" to return to the form
  8. In the registry settings search field, search for [RegA] again
  9. Validate the current value is the [NewValue] entered in step 1a
  10. Change the current value to a value greater less than "50" characters
  11. Submit the form
  12. Validate the submission results indicate that the registry setting has been submitted successfully
  13. Click "Yes" to return to the form
  14. In the registry settings search field, search for registry setting [RegA] again
  15. Validate the current value is the [NewValue] entered in step 1b
  16. Close the form
  17. Re-open form "Registry Settings"
  18. In the registry settings search field, search for [RegB]
  19. Validate the "Registry Setting Value" field is populated with value [CurrValue], whose length is less than or equal to "50" characters
  20. Change the current value to a value greater than "50" characters [NewValue]
  21. Submit the form
  22. Validate the submission results indicate that the registry setting has been submitted successfully
  23. Click "Yes" to return to the form
  24. In the registry settings search field, search for [RegB] again
  25. Validate the current value is the [NewValue] entered in step 2a
  26. Change the current value to a value that is less than or equal to "50" characters [NewValue]
  27. Submit the form
  28. Validate the submission results indicate that the registry setting has been submitted successfully
  29. Click "Yes" to return to the form
  30. In the registry settings search field, search for [RegB] again
  31. Validate the current value is the [NewValue] entered in step 2b
  32. Close the form
Topics
• Registry Settings • NX
Update 45 Summary | Details
Tabular Data Editor - grids
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Guarantors/Payors
Scenario 1: Validate results adding multiple rows in "Tabular Data Editor" (TDE) grids
Specific Setup:
  • Have access to one or more forms that contain a "(TDE) Tabular Data Editor" grid on the form. For this test, the "Treatment Plan" and the "Guarantor/Payers" forms are used
  • Admit a new client or have an existing client on the system for testing [TestClient]
  • Multiple "Guarantors" exist on the system, for example ten or more
  • Multiple "Problem" codes exist in the system, for example ten or more
Steps
  1. Open the "Treatment Plan" form
  2. Select [TestClient].
  3. Populate any required fields on the main form.
  4. Navigate to the "Problems" grid and click [New Row]
  5. Add a problem to the grid
  6. Add another new row the same problem as in the previous step
  7. Validate a message displays blocking entry that states "Problem already exists", as expected.
  8. Continue adding ten or more rows to the grid
  9. Click [Launch Plan].
  10. Validate the treatment plan tree view loads without any warnings.
  11. Validate all the problems entered in step 1c are present are displayed in the view as expected
  12. Click [Back to Plan Page]
  13. Navigate to the "Problems" grid and add one or more problems
  14. Click [Launch Plan].
  15. Validate the treatment plan tree view loads without any warnings.
  16. Validate all the problems added in the previous steps are displayed in the view as expected
  17. Click [Back to Plan Page]
  18. Submit the treatment plan as "Draft"
  19. Validate submission is successful
  20. Re-open "Treatment Plan form"
  21. Select [TestClient].
  22. Click to edit the row submitted in step 1
  23. Navigate to the "Problems" grid
  24. Add one more problems to the grid
  25. Click [Launch Plan].
  26. Validate the treatment plan tree view loads without any warnings.
  27. Validate all the problems entered in step 1 and in the previous step, are present are displayed in the tree view as expected
  28. Click [Back to Plan Page]
  29. Submit the treatment plan
  30. Validate submission is successful
  31. Re-open "Treatment Plan form"
  32. Select [TestClient].
  33. Click to edit the row just submitted
  34. Click [Launch Plan].
  35. Validate the treatment plan tree view loads without any warnings.
  36. Validate all the problems added in the previous steps are present are displayed in the tree view as expected
  37. Open the "Guarantors/Payors" form
  38. Click "Edit"
  39. In the "Guarantor Code" field, select a desired guarantor [TestGuarantor]
  40. Navigate to the "Carrier Codes" section
  41. In the "Carrier Codes for Secondary Billing" grid, click [New Row]
  42. Select any guarantor in the "Guarantor" field
  43. Enter a desired code in the "Carrier Code" field
  44. Click [File]
  45. Validate the guarantor and carrier code are added to the grid
  46. Click [New Row] again to add another guarantor
  47. Select the same guarantor as in the previous step
  48. Validate the error "Please select a different Guarantor, Guarantor is already in the grid", is displayed
  49. Click [OK]
  50. Click [New Row] again, this time add a different guarantor
  51. Enter a desired code in the "Carrier Code" field
  52. Click [File]
  53. Validate the guarantor and carrier code are added to the grid
  54. Repeat the previous step ten or more times
  55. Validate all rows added are displayed as expected in the grid
  56. Navigate back to the "Guarantor/Payors" section
  57. Click [File] to submit the changes
  58. Close the form
  59. Re-open "Guarantors/Payors" form
  60. Click "Edit"
  61. In the "Guarantor Code" field, select [TestGuarantor]
  62. Navigate to the "Carrier Codes" section
  63. Validate all the rows added in the "Carrier Codes for Secondary Billing" grid in step 4, are present and populated as expected
  64. Add one or more rows to the grid
  65. Navigate back to the "Guarantor/Payors" section
  66. Click [File] to submit the changes
  67. Close the form
  68. Re-open "Guarantors/Payors" form
  69. Click "Edit"
  70. In the "Guarantor Code" field, select [TestGuarantor]
  71. Navigate to the "Carrier Codes" section
  72. Validate all the rows added in the "Carrier Codes for Secondary Billing" grid in step 4 and 5, are present and populated as expected in the grid
Topics
• Tabular Data Editor
Update 46 Summary | Details
Progress Notes (Group and Individual) - Open to Group Default Notes Section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • Group Registration
  • Create New Progress Notes Form
  • Progress Notes (Group and Individual) 11
Scenario 1: Progress Notes (Group and Individual) - Open To Group Default Notes
Specific Setup:
  • Enable the registry setting "Open To 'Group Default Notes' Section" by setting it to "Y".
  • Using "Document Routing Setup", enable document routing for the "Progress Notes (Group and Individual)" form.
  • Create a group with 2 or more group members using the "Group Registration" form.
Steps
  1. Open the "Progress Notes (Group and Individual)" form.
  2. Validate the form opens to the "Group Default Notes" section.
  3. Fill out all required fields and create a group note.
  4. Edit the group note.
  5. Navigate to the "Individual Note" section.
  6. Individualize the progress notes for each group member.
  7. Using the "Clinical Document Viewer" form, validate the documents were filed.
  8. Open the "Registry Settings" form.
  9. Disable the "Open To 'Group Default Notes' Section" registry setting by setting it to "N".
  10. Open the "Progress Notes (Group and Individual)" form.
  11. Validate the form opens to the "Individual Notes" section.
  12. Navigate to the "Group Default Notes" section.
  13. Fill out all required fields and create a group note.
  14. Edit the group note.
  15. Navigate to the "Individual Note" section.
  16. Individualize the progress notes for each group member.
  17. Using the "Clinical Document Viewer" form, validate the documents were filed.
Scenario 2: Registry Setting - Open to 'Group Default Notes' Section
Specific Setup:
  • Disable the registry setting "Open To 'Group Default Notes' section" registry setting by setting it to "N".
Steps
  1. Open the "Progress Notes (Group and Individual)" form.
  2. Validate the form opens to the "Individual Progress Notes" section.
  3. Open the "Registry Settings" form.
  4. Enable the registry setting "Open To 'Group Default Notes' Section" by setting it to "Y".
  5. Open the "Progress Notes (Group and Individual)" form.
  6. Validate the form opens to the "Group Default Notes" section.
Scenario 3: Copy of Progress Notes (Group and Individual) - Open To Group Default Notes section
Specific Setup:
  • Using the "Create New Progress Notes" form, create a new copy of the Progress Notes (Group and Individual).
  • Note the copy number.
  • Using the "User Definition" or "User Role Definition" form:
  • Give the user access to this new progress notes form on the "Forms and Tables" section under the "Select forms for User Access" button.
  • Using the "Registry Settings" form, enable "Open To 'Group Default Notes' Section" registry setting by setting it to "Y" for the form created in previous steps.
  • Using the "Document Routing Setup" form, enable document routing for the form created in previous steps.
  • Create a group of 2 or more clients using the "Group Registration" form.
Steps
  1. Using the new group progress note form:
  2. Validate the form opens to the "Group Default Note" section.
  3. Generate a group default note and click [Submit Note].
  4. Edit the "Group Default Note".
  5. Navigate to the "Individual Note" section and individualize, finalize and route the document to an approver.
  6. Repeat above until all group members are processed.
  7. Navigate to the "ToDo" widget:
  8. Approve the "ToDo" for each group member.
  9. Using the "Clinical Document Viewer" form:
  10. Validate the documents were filed by viewing/print each one.
  11. Using the "Registry Settings" form:
  12. Enable "Open To 'Group Default Notes' Section" registry setting by setting it to "Y" for the form created in setup.
  13. Using the new group progress note form:
  14. Validate the form opens to the "Individual Note" section.
  15. Navigate to the "Group Default Note" section.
  16. Generate a group default note and click [Submit Note].
  17. Edit the "Group Default Note".
  18. Navigate to the "Individual Note" section and individualize, finalize and route the document to an approver.
  19. Repeat above until all group members are processed.
  20. Navigate to the "ToDo" widget:
  21. Approve the "ToDo" for each group member.
  22. Using the "Clinical Document Viewer" form.
  23. Validate the documents were filed by viewing/print each one.
Topics
• Progress Notes • NX
Update 47 Summary | Details
Form Launch events
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Call Intake
  • Practitioner Enrollment
Scenario 1: Validate triggering site specific event logic to launch an additional form
Specific Setup:
  • Have access to any "Progress" note form [FormA]
  • Have access to any "Client" based modeled form [FormB]
  • Have access to any "Staff" based modeled form [FormC]
  • Have access to form "Call Intake" and form "Practitioner" enrollment
  • In form "Dictionary Update", select the "Client" database and search for any "SS Call Intake Dictionary" field
  • Add three dictionary values: [DictA], [DictB] and [DictC]
  • Open form "Site Specific Section Modeling", select form "Site Specific Call Intake" form
  • Select "Yes" in prompt "Enable Site Specific Section"
  • Click the "Prompt Definition" section and add the "SS Call Intake Dictionary"
  • Set field "Initially Required" to "No"
  • In the "Event Definition" section, add three events
  • The first event set will launch [FormA] with [DictA] is selected in the field
  • The second event set will launch [FormB] with [DicB] is selected in the field
  • The third event set will launch [FormC] with [DictAC] is selected in the field
  • Submit the form
  • Open form "Site Specific Section Modeling", select form "(Practitioner Enrollment) Site Specific Enrollment" form
  • Select "Yes" in prompt "Enable Site Specific Section"
  • Click the "Prompt Definition" section and add any "SS Enrollment Dictionary"
  • Set field "Initially Required" to "No"
  • In the "Event Definition" section, add three events
  • The first event set will launch [FormA] with [DictA] is selected in the field
  • The second event set will launch [FormB] with [DicB] is selected in the field
  • The third event set will launch [FormC] with [DictAC] is selected in the field
  • Submit the form
  • The logged in user has the "Client & Staff" widget on their home view
Steps
  1. Open the "Call Intake" form
  2. At the "Select Client" dialog
  3. Populate the last and first name for a new client [NewClientA]
  4. Click Search
  5. Click [OK] to the no records found
  6. Click [New] client to launch the "Call Intake" form
  7. On the "Call Intake" section
  8. Validate the client name field indicates [NewClient]
  9. Populate any required and desired fields on that section
  10. Click the "Site Specific Call Intake" section
  11. Click the "SS Call intake dictionary" field drop down list and select [DictA]
  12. At the "Form Launch" dialog, click [OK] to launch the "Progress Note" form
  13. Validate a message is received "Based on your inputs the [FormA] should launch, however this form cannot be launched for a Client not submitted to the database"
  14. Click [OK]
  15. Validate the user is returned to the form
  16. Click the "SS Call intake dictionary" field drop down list and select [DictB]
  17. At the "Form Launch" dialog, click [OK] to launch the "Client" based modeled form
  18. Validate a message is received "Based on your inputs the [FormB] should launch, however this form cannot be launched for a Client not submitted to the database"
  19. Click [OK]
  20. Validate the user is returned to the form
  21. Click the "SS Call intake dictionary" field drop down list and select [DictC]
  22. At the "Form Launch" dialog, click [OK] to launch the "Staff" based modeled form
  23. Enter a valid "Staff" member [TestStaff] in the search field and click [Select]
  24. On [FormC], populate the desired fields on the form
  25. Submit the form
  26. Validate the form files successfully
  27. Click [Submit] to submit the "Call Intake" form
  28. Validate the form files successfully
  29. At the home view, navigate to the "Client & Staff" widget
  30. Search for [NewClientA]
  31. Validate the client is found
  32. Open the "Practitioner Enrollment" form
  33. At the "Select Staff" dialog, enter the desired name for the new staff member [StaffNew]
  34. Validate there are no matches found
  35. Click [New Staff] to launch the "Practitioner Enrollment" form
  36. Click the "Practitioner Enrollment" section
  37. Populate the required fields and any other desired fields in that section
  38. Click the "Site Specific Enrollment" section
  39. Click the "SS Enrollment Dictionary" field and select [DictA]
  40. At the "Form Launch" dialog, click [OK] to launch the "Progress Note" form
  41. On [FormA], populate the required and desired fields
  42. Submit the form
  43. Validate the form files successfully
  44. Navigate back to the "Practitioner Enrollment" form
  45. Click the "SS Enrollment Dictionary" field and select [DictB]
  46. At the "Form Launch" dialog, click [OK] to launch the "Client" based modeled form
  47. Select any client and click [OK]
  48. On [FormB], populate the required and desired fields on the form
  49. Submit the form
  50. Validate the form files successfully
  51. Navigate back to the "Practitioner Enrollment" form
  52. Click the "SS Enrollment Dictionary" field and select [DictC]
  53. Validate a message is received "Based on your inputs the [FormC] should launch, however this form cannot be launched for a Staff not submitted to the database"
  54. Click [OK]
  55. Validate the user is returned to the form
  56. Click [Submit] to submit the form
  57. Validate the form files successfully
  58. At the home view, navigate to the "Client & Staff" widget
  59. Click the "Staff" tab
  60. Search for [StaffNew]
  61. Validate the staff member is found
Topics
• Site Specific Section Modeling • NX
Update 48 Summary | Details
Document Routing - Replace ‘Date Created’ with ‘Date Signed’ on Document Routing Images.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client
  • Disclosure Management
  • Disclosure Management Configuration
  • Treatment Plan
  • Clinical Document Viewer
Scenario 1: Disclosure Management - Date Created vs. Date Signed - Document Routing disabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, disable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize the note.
  4. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  5. Using the "Treatment Plan" form:
  6. Generate a new treatment plan.
  7. Finalize the note.
  8. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  9. Using a user modeled form:
  10. Generate a new form.
  11. Finalize the form.
  12. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  13. Open the "Disclosure Management" form:
  14. Generate a disclosure packet.
  15. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test.
  16. Click "Apply Filters to Document Images" button.
  17. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual)", Treatment Plan, user modeled forms you want to include in the disclosure packet.
  18. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  19. Navigate to the "Authorization" section.
  20. Select the same Episode and the Authorization Start and End Dates.
  21. Click "Yes - Default All Chat Items to Yes" radio button.
  22. Click "Update Chart Items Authorized for Disclosure" button.
  23. Click "Save" button.
  24. Click "Refresh Chart Items" button.
  25. Click "Yes - Default All Document Items To Yes" radio button.
  26. Click the "Update Document Images Authorized for Disclosure" button.
  27. Click "Save" button.
  28. Click "Refresh Document Images" button.
  29. Navigate to the "Disclosure" section.
  30. Populate the "Disclosure Date" and "Disclosure Time".
  31. Select all items in the "Chart Disclosure Information" box.
  32. Select all items in the "Disclosure Images" box.
  33. Select "Electronic" in the "Disclosure Method" field.
  34. Click "Process" button.
  35. Select various forms and then press "View".
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Disclose" button.
  38. The final disclosure packet is presented.
  39. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  40. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization and disclosure.
  41. Open the "Disclosure Management" form:
  42. Select to edit the disclosure that was just filed.
  43. Validate it displays as it was previously saved.
Scenario 2: Disclosure Management - Form Validations
Specific Setup:
  • In the 'View Attachment Types field on the 'Disclosure Management Configuration' form, select various modeled and product form type attachments to include for requesting and authorizing document images for disclosure.
  • In the product and modeled forms selected in the previous step, have documents generated for a client in multiple episodes (Client A).
  • The 'Sort Episodes by Admission Date' registry setting must be enabled.
Steps
  1. Select "Client A" and access the 'Disclosure Management' form.
  2. Enter a date in the 'Request Date' field.
  3. Enter a date in the 'Request Information Start Date' field.
  4. Enter a date in the 'Request Information End Date' field.
  5. In the 'Requested Episode(s)' field, validate all episodes are listed and displayed in a readable format.
  6. Select the desired episodes to include.
  7. Click [Apply Filter to Document Images].
  8. Select the desired items in the 'Requested Chart Items' field.
  9. Select the desired documents in the 'Requested Document Images' field.
  10. Enter an organization name in the 'Organization' field.
  11. Go to the 'Authorization' section.
  12. Select "Yes" in the 'Signed Authorization On File' field.
  13. Enter a date in the 'Authorization Start Date' field.
  14. Enter a date in the 'Authorization End Date' field.
  15. Validate all episodes are listed and displayed in a readable format in the 'Authorization Episode(s)' field.
  16. Select desired episodes to include in the 'Authorization Episode(s)' field.
  17. Click [Update Chart Items Authorized For Disclosure].
  18. Validate all items are set to "Yes" in the 'Authorized' field.
  19. Click [Save].
  20. Click [Refresh Chart Items].
  21. Click [Apply Filter to Document Images].
  22. Click [Update Document Images Authorized for Disclosure].
  23. Validate all items are set "Yes" in the 'Authorized' field.
  24. Click [Save].
  25. Click [Refresh Document Images].
  26. Go to the 'Disclosure' section.
  27. Enter a date in the 'Disclosure Date' field
  28. Enter a time in the 'Disclosure Time' field.
  29. Select "Electronic" in the 'Disclosure Method' field.
  30. Click [Process].
  31. Validate the items list in the 'Disclosure Management' panel are as expected.
  32. Select the item and click [View].
  33. Validate the documents displays as expected.
  34. Click [Disclose].
  35. Validate the disclosure displays as expected and 'Save' displays.
  36. Click [Save].
  37. Validate a 'Confirm' dialog stating: "Save PDF on your computer?" and click [OK].
  38. Validate the file downloads.
  39. Validate a 'Disclosure' dialog stating: "Once this Disclosure Management record is filed with a Disclosure Date entered it will no longer be available for edit. This record will be available to view and print items." and click [Cancel].
  40. Validate a dialog stating: "Filing cancelled." and click [OK].
  41. Click [Save].
  42. Validate a 'Confirm' dialog stating: "Save PDF on your computer?" and click [Cancel].
  43. Validate nothing downloads.
  44. Validate a 'Disclosure' dialog stating: "Once this Disclosure Management record is filed with a Disclosure Date entered it will no longer be available for edit. This record will be available to view and print items." and click [OK].
  45. Validate the form closes.
Scenario 3: Registry Setting - Replace 'Date Created' with 'Date Signed'
Steps
  1. Open the "Registry Setting" form.
  2. Set the "RADplus->Document Routing->Document Routing Setup->->->Replace 'Date Created' with 'Date Signed' on Document Routing Images' to any value other than "Y" or "N".
  3. Validate the error message "The selected value is not valid in the current system code for the following reason: Please enter "Y" or "N".
  4. Set registry setting to "N".
  5. Using the "Document Routing Setup" form, enable document routing for the "Progress Notes (Group and Individual)" form,
  6. Open the "Progress Notes (Group and Individual)" form.
  7. File an individual progress note.
  8. Finalize and route the note.
  9. Navigate to the "ToDo" widget for the approver.
  10. Validate the first line of every page of the document begins with "Date Created" followed by the date and time the document was finalized.
  11. Click "Accept".
  12. Click "Sign".
  13. Using the "Clinical Document Viewer", validate the document displays as it was filed with "Date Crated" on the first line of every page.
  14. Open the "Registry Setting" form.
  15. Set registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" to "Y".
  16. Using the "Document Routing Setup" form, enable document routing for the "Progress Notes (Group and Individual)" form, form.
  17. Open the "Progress Notes (Group and Individual)" form.
  18. File and individual progress note.
  19. Finalize and route the note.
  20. Navigate to the "ToDo" widget for the approver.
  21. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  22. Click "Accept".
  23. Click "Sign".
  24. Using the "Clinical Document Viewer", validate the document displays as it was filed with "Date Signed" on the first line of every page.
Scenario 4: Progress Notes (Group and Individual) - Date Created vs. Date Signed
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be disabled.
  • Using the "Document Routing Setup" form, enable document routing for the "Progress Notes (Group and Individual)" form.
  • Using "Disclosure Management Configuration", the "Progress Notes (Group and Individual)" form among the forms available to the "Disclosure Management" form.
Steps
  1. Open the "Progress Notes (Group and Individual) form.
  2. Create a form.
  3. Finalize and route the document.
  4. Navigate to the "ToDo" widget.
  5. Validate the first lien of every document begins with "Date Created" followed by the date and time the document was finalized.
  6. Click "Accept".
  7. Click "Sign".
  8. Close the "ToDo" widget.
  9. Open the "Registry Setting" form.
  10. Enable the registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing images".
  11. Open the "Progress Notes (Group and Individual)" form.
  12. Create a form.
  13. Finalize and route the document.
  14. Navigate to the "ToDo" widget.
  15. Validate the first lien of every document begins with "Date Signed" followed by the date and time the document was finalized.
  16. Click "Accept".
  17. Click "Sign".
  18. Close the "ToDo" widget.
  19. Open the "Clinical Document Viewer" form.
  20. View both documents that were just saved with the different labels.
  21. Validate the first one finalized includes the "Date Created" label.
  22. Validate the second one finalized includes the "Date Signed" label.
Scenario 5: Treatment Plan - Date Created vs. Date Signed
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be disabled.
  • Using the "Document Routing Setup" form, enable document routing for the "Treatment Plan" form.
  • Using "Disclosure Management Configuration", the "Progress Notes (Group and Individual)" form among the forms available to the "Disclosure Management" form.
Steps
  1. Open the "Treatment Plan" form.
  2. Create a form.
  3. Finalize and route the document.
  4. Navigate to the "ToDo" widget.
  5. Validate the first lien of every document begins with "Date Created" followed by the date and time the document was finalized.
  6. Click "Accept".
  7. Click "Sign".
  8. Close the "ToDo" widget.
  9. Open the "Registry Setting" form.
  10. Enable the registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing images".
  11. Open the "Treatment Plan" form.
  12. Create a form.
  13. Finalize and route the document.
  14. Navigate to the "ToDo" widget.
  15. Validate the first lien of every document begins with "Date Signed" followed by the date and time the document was finalized.
  16. Click "Accept".
  17. Click "Sign".
  18. Close the "ToDo" widget.
  19. Open the "Clinical Document Viewer" form.
  20. View both documents that were just saved with the different labels.
  21. Validate the first one finalized includes the "Date Created" label.
  22. Validate the second one finalized includes the "Date Signed" label.
Scenario 6: User Modeled Form - Date Created vs. Date Signed
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be disabled.
  • Using the "Document Routing Setup" form, enable document routing for a user modeled form.
  • Using "Disclosure Management Configuration", the user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Open the user modeled form.
  2. Create a form.
  3. Finalize and route the document.
  4. Navigate to the "ToDo" widget.
  5. Validate the first lien of every document begins with "Date Created" followed by the date and time the document was finalized.
  6. Click "Accept".
  7. Click "Sign".
  8. Close the "ToDo" widget.
  9. Open the "Registry Setting" form.
  10. Enable the registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing images".
  11. Open the user modeled form.
  12. Create a form.
  13. Finalize and route the document.
  14. Navigate to the "ToDo" widget.
  15. Validate the first lien of every document begins with "Date Signed" followed by the date and time the document was finalized.
  16. Click "Accept".
  17. Click "Sign".
  18. Close the "ToDo" widget.
  19. Open the "Clinical Document Viewer" form.
  20. View both documents that were just saved with the different labels.
  21. Validate the first one finalized includes the "Date Created" label.
  22. Validate the second one finalized includes the "Date Signed" label.
Scenario 7: Disclosure Management - Date Created vs. Date Signed - Document Routing Enabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, enable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize and route the note.
  4. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  5. Using the "Treatment Plan" form:
  6. Generate a new treatment plan.
  7. Finalize and route the note.
  8. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  9. Using a user modeled form:
  10. Generate a new form.
  11. Finalize and route the form.
  12. Validate the first line of ever page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  13. Open the "Disclosure Management" form:
  14. Generate a disclosure packet.
  15. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test..
  16. Click "Apply Filters to Document Images" button.
  17. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual), Treatment Plan, user modeled forms you want to include in the disclosure packet.
  18. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  19. Navigate to the "Authorization" section.
  20. Select the same Episode and the Authorization Start and End Dates.
  21. Click "Yes - Default All Chat Items to Yes" radio button.
  22. Click "Update Chart Items Authorized for Disclosure" button.
  23. Click "Save" button.
  24. Click "Refresh Chart Items" button.
  25. Click "Yes - Default All Document Items To Yes" radio button.
  26. Click the "Update Document Images Authorized for Disclosure" button.
  27. Click "Save" button.
  28. Click "Refresh Document Images" button.
  29. Navigate to the "Disclosure" section.
  30. Populate the "Disclosure Date" and "Disclosure Time".
  31. Select all items in the "Chart Disclosure Information" box.
  32. Select all items in the "Disclosure Images" box.
  33. Select "Electronic" in the "Disclosure Method" field.
  34. Click "Process" button.
  35. Select various forms and then press "View".
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Disclose" button.
  38. The final disclosure packet is presented.
  39. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  40. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization and disclosure.
  41. Open the "Disclosure Management" form ;
  42. Select to edit the disclosure that was just filed.
  43. Validate it displays as it was previously saved.
Topics
• Disclosure • NX • Progress Notes (Group And Individual) • Treatment Plan • Modeling
Update 49 Summary | Details
Widget - Data display
Scenario 1: Validate "Widget" data load and data refresh
Specific Setup:
  • Have a system with various types of widgets defined. For example a "Widget Wizard", "Widget Definition", "SQL Query" and "Console Widget" type widgets
  • Each widget has the field "Allow Refresh" selected
  • For two clients [ClientA] and [ClientB] and any other desired clients, have data filed in the tables that are defined in each widget
  • All widgets have been assigned to a user's [TestUser] home view or additional view
  • Log in as [TestUser]
Steps
  1. Select [ClientA]
  2. Validate all widgets display data as expected
  3. Click the "Refresh" button on each widget
  4. Validate data displays as expected
  5. Repeat step b three or more times for each widget
  6. Validate each time, data is returned and displays as expected
  7. Select [ClientB]
  8. Validate all widgets display data as expected
  9. Click the "Refresh" button on each widget
  10. Validate data displays as expected
  11. Repeat step b three or more times for each widget
  12. Validate each time, data is returned and displays as expected
  13. Repeat step 2 for any other desired clients
  14. Validate results are as expected
  15. From the recent client list
  16. Click thru each client selected in the previous steps, consecutively
  17. As each client is selected:
  18. Validate all widgets return and display data as expected
My To Do's - Widget
Scenario 1: My To Do's Widget - Validate To Do's sent for review or approval
Specific Setup:
  1. Have a system that has two forms set up, that will generate To Do's. For example forms enabled for document routing
  2. [FormA] is a "PM" form
  3. [FormB] is a "CWS" form
  4. Each form also has the "Enable To Do Creation from Form" functionality set on the form. (This can be done in "Form Definition" or in form "To Do Button Settings")
  5. User [StaffA] has access to both [FormA] and [FormB]
  6. User [StaffB] has the "My To Do's widget on their home view
  7. Log in as [StaffA]
Steps
  1. Open [FormA]
  2. Populate all the desired fields on the form
  3. On the left side panel click on the "Create To Do" icon
  4. In the "Select Staff" field, select and [StaffB]
  5. Click [Add]
  6. Validate [StaffB] is added to the "Send To" box
  7. In the "Note" field, add a message that will be sent with the To Do
  8. Click [Save]
  9. Set the form to "Final"
  10. At the "Confirm Document" screen, click [Sign and Route]
  11. At the "Route To Document" screen, select [StaffB] as the approver
  12. Submit the form
  13. Validate the form files successfully
  14. Repeat step 1 for [FormB]
  15. Logout as [StaffA]
  16. Log in as [StaffB]
  17. Navigate to the "My To Do's: widget
  18. Validate for [FormA] there is an "Approve Document" To Do for the for document routed in step 1
  19. Click [Approve Document]
  20. Click [Sign] to approve the document
  21. Validate for [FormA] there is a "Review To Do Item" To Do for the "Create To Do" sent in step 1
  22. Click the [Review To Do Item] button
  23. Click the "Reviewed" check box
  24. Click [Submit]
  25. Validate for [FormB] there is an "Approve Document" To Do for the for document routed in step 2
  26. Click [Approve Document]
  27. Click [Sign] to approve the document
  28. Validate for [FormB] there is a "Review To Do Item" To Do for the "Create To Do" sent in step 2
  29. Click the [Review To Do Item] button
  30. Click the "Reviewed" check box
  31. Click [Submit]
  32. Validate all To Do's approved and reviewed have been cleared from the "My To Do's" widget
Topics
• Widgets • NX • My To Do's • "My To Do's" widget
Update 50 Summary | Details
View Definition - "View Type"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
Scenario 1: View Definition - Validate fields
Specific Setup:
  • Create or modify a view that is associated with other views in "View Definition".
  • Registry Setting "RADplus->General->Enable Console Widget/Views" must be enabled.
Steps
  1. Access the 'View Definition' form.
  2. Click [Select View].
  3. Select "Add New View" in the 'Select Views' field and click [OK].
  4. Enter "View A" in the 'View ID' field.
  5. Enter any value in the 'View Description' field.
  6. Select "Home View" in the 'View Type' field.
  7. Select any value in the 'Allow User To Customize View' field.
  8. Click [Associated Views].
  9. Check all applicable "Associated Views" in the left pane.
  10. Validate that the selected views show up in the right pane.
  11. Rearrange the views in desired order and click [OK].
  12. Click [Launch View Designer].
  13. Validate that the Widgets are listed in alphabetical order in the Widgets pane.
  14. Select one or more widgets and click the right arrow.
  15. Validate the selected widgets appear in the 'Available Widgets' field.
  16. Drag the Available widgets and drop it onto the 'Default Role Layout' field.
  17. Click [Submit], [Submit] and [No].
  18. Access the 'User Definition' form.
  19. Enter "User B" in the 'User ID' field.
  20. Select "Yes" in the 'Is this user a system administrator' field.
  21. Select "No" in the 'Associate User with a User Role' field.
  22. Select 'Forms and Tables'.
  23. Click [Select Forms for User Access].
  24. Select the 'Avatar PM' item and click [OK].
  25. Select "Level 4" in the 'User Security Level' field.
  26. Select "View A" in the 'Home View' field.
  27. Populate any desired and required fields.
  28. Select 'User Definition' section
  29. Click [Generate New Password].
  30. Take note of password and click [Submit].
  31. Validate a 'Form Access' dialog stating: "The following forms are on the menu more than once, and different access levels were selected. The highest selected access will be applied to all menu locations."
  32. Click [OK] and [No].
  33. Logout.
  34. Log into Avatar as "User B".
  35. Validate that the views are displaying on the home view and that they are in the order as rearranged.
  36. Access the 'Registry Setting' form.
  37. Enter "Enable Documentation View" in the 'Limit Registry Settings to the Following Search Criteria' field.
  38. Enter "Y" in the 'Registry Setting Value' field.
  39. Click [Submit], [OK], and [No].
  40. Access the 'View Definition' form.
  41. Click [Select View].
  42. Select "Add New View" in the 'Select Views' field and click [OK].
  43. Enter "View B" in the 'View ID' field.
  44. Enter any value in the 'View Description' field.
  45. Navigate to the "View Type" field
  46. Validate three selections are available, "Home View", "Chart View" and "Documentation View"
  47. Click the "Help Message"(Light bulb) icon
  48. Validate the help message displayed indicates "The 'Documentation' view type is only supported in myAvatar NX."
  49. Click [OK] to return to the form
  50. Select "Documentation View" in the 'View Type' field.
  51. Validate the 'Allow Users to Customize View' field is disabled.
  52. Click [Associated Views].
  53. Check all applicable "Associated Views" in the left pane.
  54. Validate that the selected views show up in the right pane.
  55. Rearrange the views in desired order and click [OK].
  56. Validate the 'All Documents Widget' field is enabled.
  57. Select any value in the 'All Documents Widget' field.
  58. Click [Submit] and [Yes].
  59. Click [Select View].
  60. Select "View B" in the "Select Views" field and click [OK].
  61. Validate that the view displays as it was entered.
  62. Click [Delete View] and [Yes].
  63. Click [Select View].
  64. Validate the view has been removed.
  65. Close the form.
Topics
• NX • NX View Definition
Update 51 Summary | Details
Modeled Forms - Table Alias
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
Scenario 1: Modeled Forms - "Table Alias" field and data validations
Specific Setup:
  • Have a client [TestClient] who is active in an existing episode
  • Have a modeled form [TestForm] that contains:
  • A field [TestField] that is not mapped to any of the field in the "Vital Signs" alias table. For this example a "Dictionary" type field is used
  • Mapped "Table" aliased fields. For this test [TestForm] has the following fields in its table [TestTable], that are mapped in "Table Definition" to the following fields in the "CWS" table alias, "Vital Signs":
  • Date
  • Time
  • Diastolic Blood Pressure
  • Systolic Blood Pressure
  • Respiration
  • Please Note: For the "CWS" "Vital Signs" table alias used in this test, the "Date" and "Time" alias fields are required to be populated at the time submission in order to file the data submitted in the mapped alias fields, into the "SYSTEM.cw_vital_signs" table.
  • Have a report created to display data in the modeled table [TestTable]
  • Have a report created to display data in the "SYSTEM.cw_vital_signs" table
  • Have a report created to display data in the "SYSTEM.RADplus_error_log" table
Steps
  1. On the home view, select [TestClient]
  2. Open form [TestForm]
  3. Populate the field [TestField]
  4. Populate the table alias mapped "Date" and "Time" fields
  5. Populate the other mapped alias fields noted in the setup.
  6. Submit the form
  7. Validate the form submits successfully
  8. Run the report to display data in the modeled table [TestTable]
  9. Validate data for all fields populated in step 2a and b, are displayed as expected
  10. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  11. Validate rows for all the mapped table alias fields populated in step 2b, are displayed as expected
  12. Run the report to display data in the "SYSTEM.RADplus_error_log"
  13. Validate there are no messages related to the table alias submission displayed, as expected
  14. Open form [TestForm] and add a new row
  15. Populate just the field [TestField], which is not a mapped alias field
  16. Submit the form
  17. Validate the form files successfully
  18. Run the report to display data in the modeled table [TestTable]
  19. Validate data for field [TestField] populated in step 3a is displayed populated as expected
  20. Validate none of the other fields are populated in the report, as expected
  21. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  22. Validate there are no rows populated from the form submission in step 4a, as the required table alias mapped "Date" and "Time" fields were both not populated.
  23. Run the report to display data in the "SYSTEM.RADplus_error_log"
  24. Validate there are no messages related to table alias submission, as both of the required alias mapped fields were not populated, indicating no attempt to file data in the alias table
  25. Open form [TestForm] and add a new row
  26. Populate field [TestField]
  27. Leave either the alias mapped "Date" or mapped "Time" field unpopulated, and populate any of the other alias mapped fields.
  28. Submit the form
  29. Validate the form submits successfully
  30. Run the report to display data in the modeled table [TestTable]
  31. Validate data for all fields populated in step 4a and 4b, are displayed as expected
  32. Run the report to display data in the "SYSTEM.cw_vital_signs" table
  33. Validate there are no rows populated for the submission in step 4c, as one of the two required fields for alias table submission was not populated.
  34. Run the report to display data in the "SYSTEM.RADplus_error_log"
  35. Validate there is a row with a message stating "Table Alias Submission Failed Validation" displayed
Topics
• Diagnosis • NX
Update 53 Summary | Details
All Documents Widget - Episode selection
Scenario 1: Avatar NX "All Documents Widget" - Validate a users "Episode" access to documents
Specific Setup:
  • Have a system with two sub system codes:
  • Sub code [Test1] is assigned to [Program1]
  • Sub code [Test2] is assigned to [Program2]
  • Have two users defined with the following permissions assigned in the user definition or assigned user role:
  • [User1] has permission to sub code [Test1], but not to sub code [Test2]
  • [User2] has permissions to both sub code [Test1] and [Test2]
  • [User1] and [User2] have prompt "Limit Episodes to Current System Code in Chart View" set to "N", in the user definition or assigned user role
  • [User1] and [User2]
  • Client [TestClient] has been admitted in two episodes: in [Episode1] to [Program1] and in [Episode2] to [Program2]
  • Client [TestClient] has a row of data filed in [TestForm] in both [Episode1] and [Episode2]
  • Form [TestForm] has been added to the users chart view
  • [User1] and [User2] have the "All Document Widget" on their home view
  • Log into the [Test1] sub code as [User2]
Steps
  1. Select client [TestClient]
  2. In the upper right-hand corner, click the "Episodes" field and choose "All Episodes"
  3. Navigate to the "All Documents Widget"
  4. Click on the tab containing [TestForm], for example the "All Forms" tab
  5. Click the "Form Description" filter and select [TestForm]
  6. Click "Episodes" filter
  7. Validate both [Episode1] and [Episode2] are displayed, as expected
  8. Select [Episode1] and click [Open]
  9. Validate data is displayed as expected
  10. Close the form
  11. Repeat the last step for [Episode2]
  12. Validate results are as expected
  13. Log out of sub code [Test1] as [User2]
  14. Log into sub code [Test2] as [User2]
  15. Repeat step 1
  16. Validate results are the same, as [User2] has permissions to both sub system codes
  17. Log out of sub code [Test2] as [User2]
  18. Log into sub code [Test1] as [User1], who only has permissions to episodes in sub code [Test1]
  19. Select client [TestClient]
  20. In the upper right-hand corner, click the "Episodes" field and choose "All Episodes"
  21. Navigate to the "All Documents Widget"
  22. Click on the tab containing [TestForm], for example the "All Forms" tab
  23. Click the "Form Description" filter and select [TestForm]
  24. Click "Episodes" filter
  25. Validate only [Episode1] are displayed for selection, as expected
  26. Select [Episode1] and click [Open]
  27. Validate data is displayed as expected
  28. Close the form
  29. Log out of sub code [Test1] as [User1]
  30. Attempt to login into sub code [Test2] as [User1]
  31. Validate login is unsuccessful as expected as [User1] does not have permissions to log into sub code [Test2]
Topics
• All Documents Widget • Episodes
Update 55 Summary | Details
Dictionary Import - values
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Import (PM)
Scenario 1: Dictionary Import - Data import validations
Specific Setup:
  • Have a form [TestForm] that contains a "Dictionary" type field [TestDict] on the form
  • Have access to form "Dictionary Update"
  • Have two "Dictionary Import" files available to import values in field [TestDict]
  • [FileA] is an import file created that contains dictionary codes for import, whose values all include an unsupported character:
  • [Code1] includes a dictionary value containing a less than sign (<)
  • [Code2] includes a dictionary value containing a caret symbol (^)
  • [Code3] includes a dictionary value containing an equal sign (=)
  • [Code4] includes a dictionary value containing a tilde symbol (~)
  • [FileB] does "not" contain any dictionary codes for import, whose values include any of the unsupported characters
  • [FileB] also contains a dictionary code that is flagged as "Inactive". (Note: an "X" needs to be placed in the "Inactive" column in the import file in order for the dictionary code being imported, to be considered "Inactive")
Steps
  1. Open form "Dictionary Import"
  2. Click [Select File]
  3. Navigate the location of [FileA] and select it
  4. Click "Scan Import File"
  5. Validate the scan results indicate
  6. Error in row 1: Caret(s) found in dictionary value.
  7. Error in row 2: Equal sign(s) found in dictionary value.
  8. Error in row 3: Tilde(s) found in dictionary value.
  9. Error in row 4: Less than sign(s) found in dictionary value.
  10. Import file cannot be processed due to critical errors.
  11. Click [OK]
  12. Click [Select File]
  13. Navigate the location of [FileB] and select it
  14. Click "Scan Import File"
  15. Validate the scan results indicate "No errors or warnings found in file."
  16. Click "Begin Import"
  17. At the "Dictionary Import Complete" dialog, click [OK]
  18. Open [TestForm]
  19. Navigate to the [TestDict] field, and click on the field
  20. Validate all 'Active' dictionaries imported in [FileB] in step 1, are present in the selection list as expected
  21. Validate any 'Inactive' dictionaries imported are not displayed, as expected. Note: Inactive dictionary values are not displayed on forms
  22. Close the form
  23. Open form "Dictionary Update"
  24. Click the "Print Dictionary" section
  25. Select the file in "File" field where [TestDict] resides
  26. Select "Individual Data Element"
  27. Select [TestDict] in the "Data Element" field
  28. Click [Print Dictionary]
  29. Validate all 'Active' and 'Inactive' dictionaries imported in [FileB] in step 1, are present in the results
Topics
• Dictionary
Update 56 Summary | Details
Report Definition and Site Specific Section Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Report Definition Export
  • Report Definition (PM)
  • Report Definition Import (PM)
  • Site Specific Section Modeling Import/Export (CWS)
  • Site Specific Section Modeling (CWS)
Scenario 1: Report Definition "Export/Import" - "Version" number and "Audit" data validations
Specific Setup:
  • Have report [TestReport] form created using form "Report Definition"
  • The logged in user has access to form "Report Definition", "Report Definition Import" and "Report Definition Export"
  • Have a report or query to display data in tables 'SYSTEM.RADplus_Import_Audit' and 'SYSTEM.RADplus_Export_Audit'
Steps
  1. Open form "Report Definition Export"
  2. Select [TestReport]
  3. Validate the "Report Version Number" field present and arranged on the form layout along with the other expected fields
  4. Validate the "Report Version Number" field is populated with the current version number. For this test "1.01" is used. Note the version number value
  5. Validate the field is disabled
  6. Click [Begin Export]
  7. Validate the report export file name automatically includes the report definition name and the "Version" number noted in step 1a. For example: "ReportExportReportTestReportV1_01.TXT"
  8. Save the file in a desired folder location. Note the current date and time
  9. Close the form
  10. Navigate to the location of the export file saved in step 1b
  11. Open the exported file in a text editor, confirm the file is encrypted.
  12. Run a report or query on the "SYSTEM.RADplus_export_audit" table, displaying field data
  13. Validate the "Version" number field is populated with same value of the version field noted in step 1a
  14. Validate "data_entry_user_name" field is the logged in user
  15. Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 1b
  16. Validate the "Report Name" field contains [TestReport]
  17. Open form "Report Definition"
  18. Select [TestReport]
  19. Validate the "Report Version Number" field reflects the value in step 1a
  20. Validate the field is disabled
  21. Make any change to a prompt or parameter on the form
  22. Set field "Is Report Eligible for Export * to "Yes"
  23. Validate the "Report Version Number" has incremented. For this test the version number is now "1.02". Note the version number. Note: "Version Number" will be increased by ".01" whenever the form is updated i
  24. Submit the form
  25. Validate the form files successfully
  26. Open form "Report Definition Export"
  27. Select [TestReport]
  28. Validate the "Report Version Number" field is populated with the current version number noted in step 2a
  29. Click [Begin Export]
  30. Validate the report export file name automatically includes the report definition name and the "Version" number noted in step 2a. For example: "ReportExportReportTestReportV1_02.TXT"
  31. Save the file in a desired folder location. Note the date and time
  32. Close the form
  33. Run a report or query on the "SYSTEM.RADplus_export_audit" table, displaying field data
  34. Validate the "Version" number is populated with same value of the version number field noted in step 3a.
  35. Validate "data_entry_user_name" field is the logged in user
  36. Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 3b
  37. Validate the "Report Name" field contains [TestReport]
  38. Open the form 'Report Definition Import'
  39. Click [Select Report Import File]
  40. Navigate to the location of the original file version exported in step 1b
  41. Validate the field "Report Version Number To Be Imported" is populated with expected version number. For this example "1.01"
  42. Select the "Overwrite Existing" radio button
  43. Click [Begin Import Scan]
  44. Validate the "Import Scan Results" box contains: "Critical Error: Report Name: Report [TestReport]. The import file report version (1.01) is prior to the current report version (1.02). The file contains one or more critical errors and therefore can not be imported. Note the version number of the import file
  45. Validate the [Begin Import] button is disabled
  46. Select the "Create New" radio button
  47. Click [Yes] when prompted with the dialog "This report already exists within this system. Are you sure that you would like to create a new report
  48. Click [Begin Import Scan]
  49. Validate the "Import Scan Results" box contains "There are no errors/warnings found within the import file."
  50. Click [Begin Import]
  51. Click [Yes] at "Are you sure that you want to 'Create New'?" import dialog
  52. Click [OK] at the "Import Complete" dialog. Note the date and time
  53. Close the form. [Please Note: An export file that has been exported with update "RADplus 2023 Update 56" installed, will not be able to imported in systems that do not have that update installed yet]
  54. Run a report or query on the "SYSTEM.RADplus_import_audit" table, displaying field data
  55. Validate the "Version" number is populated with same value version number noted in step 4a
  56. Validate "data_entry_user_name" field is the logged in user
  57. `Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 4a
  58. Validate the "Report Name" field contains [TestReport]
  59. Open form "Report Definition"
  60. Search for [TestReport]
  61. Validate the search display two results for [TestReport], the original version and new copy of the report imported in step 4.
  62. Note: the search results will include the form name of the report appended by the form ID# in parenthesis. Note that the newly imported copy in step 4, will have the higher form (ID#) number. For example:
  63. TestReport (3)
  64. TestReport (4)
  65. Select the first selection, the current updated report
  66. Validate the "Report Version Number" is populated with the current version of the report, for example "1.02"
  67. Validate the change made to the prompt or parameter on the form in step 2a, is displayed as expected
  68. Close the form
  69. Re-open form "Report Definition"
  70. Search for [TestReport]
  71. From the search results select the second selection, which is the imported copy containing the original version of the report
  72. Validate the "Report Version Number" is populated with the version number of the original version of the report, for this example "1.01"
  73. Validate the change made to the prompt or parameter in step 2a is not present, as expected
  74. Close the form
Scenario 2: Site Specific Section Modeling "Export/Import" File - "Version" number and "Audit" data validations
Specific Setup:
  • Have a form [TestForm] that's available for site specific section modeling in form "Site Specific Section Modeling", for example form "Vitals Entry"
  • The logged in user has access to form "Site Specific Section Modeling" and "Site Specific Section Modeling Import/Export"
  • Have a report or query to display data in tables 'SYSTEM.RADplus_Import_Audit' and 'SYSTEM.RADplus_Export_Audit'
Steps
  1. Open form "Site Specific Section Modeling Import/Export"
  2. In the "Select Form to Export" field, select [TestForm]
  3. Validate the "Version Number" field is populated with the current version number and the field is disabled. For this test "1" is used. Note the version number value
  4. Click on the "light bulb" icon to display the help message for the field. Validate the help message is updated to include the following verbiage: "The 'Site Specific Section Modeling Version' is increased by .01 whenever the form is updated in 'Site Specific Section Modeling'. When the 'Site Specific Section Modeling Import/Export' form is used for importing, then the 'Site Specific Section Modeling Version' value will be set to the value from the imported file."
  5. Click [Begin Export]. Note the current date and time
  6. Navigate to a desired file location to save the file
  7. Save the file name with a desired file name and append the version number noted in step 1a to the name. For example, "SSTabExportTestFormV1"
  8. Note the current date and time the file is saved
  9. Close the form
  10. Run a report or query on the "SYSTEM.RADplus_export_audit" table, displaying field data
  11. Validate the "Version" number field is populated with same value of the version field noted in step 1a
  12. Validate "data_entry_user_name" field is the logged in user
  13. Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 1b
  14. Validate the "option_desc" field contain [TestForm]
  15. Open form "Site Specific Section Modeling"
  16. Select [TestForm]
  17. Validate the "Version Number" field reflects the value in step 1a and the field is disabled
  18. Make any change to a prompt or parameter on the form
  19. Submit the form
  20. Validate the form files successfully
  21. Open form "Site Specific Section Modeling Import/Export"
  22. Select [TestForm]
  23. Validate the "Version Number" field has been incremented. For this example "1.01".
  24. Click [Begin Export].
  25. Navigate to a desired file location to save the file
  26. Save the file name with a desired file name and append the new version number noted in step 3a to the name. For example, "SSTabExportTestFormV1.01"
  27. Note the current date and time the file is saved
  28. Close the form
  29. Run a report or query on the "SYSTEM.RADplus_export_audit" table, displaying field data
  30. Validate the "Version" number field is populated with same value of the version field noted in step 3a
  31. Validate "data_entry_user_name" field is the logged in user
  32. Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 3b
  33. Validate the "option_desc" field contain [TestForm]
  34. Open the form "Site Specific Section Modeling Import/Export"
  35. Click [Select Import File]
  36. Navigate to the location of the original file version exported in step 1b. For this test "SSTabExportTestFormV1"
  37. Validate the field "Version Number" is populated with expected version number. For this example "1".
  38. Click [Begin Import Scan]
  39. Validate the "Import Scan Results" box contains: " Warning: The Form Version Number In The System Is Higher Than The Form Version Number In The File"
  40. Click [OK]
  41. Click [Process Import File]. Note the current date and time of the import
  42. Close the form
  43. Run a report or query on the "SYSTEM.RADplus_import_audit" table, displaying field data
  44. Validate the "Version" number is populated with same value version number noted in step 4a
  45. Validate "data_entry_user_name" field is the logged in user
  46. `Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 4a
  47. Validate the "option_desc" field contain [TestForm]
  48. Open form "Site Specific Section Modeling"
  49. Select [TestForm]
  50. Validate the "Version Number" is populated with the original version exported in step 1. For this test "1" is noted.
  51. Validate the change made to the prompt or parameter on the form in step 2, is 'not' present as expected
  52. Close the form
  53. Open the form "Site Specific Section Modeling Import/Export"
  54. Click [Select Import File]
  55. Navigate to the location of the update file version exported in step 3. For this test "SSTabExportTestFormV1.01"
  56. Validate the field "Version Number" is populated with expected version number. For this example "1.01". Note the version number value.
  57. Click [Begin Import Scan]
  58. Validate the "Import Scan Results" box contains: "No errors or warnings found"
  59. Click [Process Import File]
  60. Click [OK] at the "Import Complete" dialog. Note the current date and time of the import
  61. Close the form
  62. Run a report or query on the "SYSTEM.RADplus_import_audit" table, displaying field data
  63. Validate the "Version" number is populated with same value version number noted in step 6a
  64. Validate "data_entry_user_name" field is the logged in user
  65. `Validate the "data_entry_date" and "data_entry_time" fields are consistent with the date and time noted in step 6a
  66. Validate the "option_desc" field contain [TestForm]
  67. Close the form
  68. Open form "Site Specific Section Modeling"
  69. Select [TestForm]
  70. Validate the "Version Number" is populated with the version number noted in step 6a
  71. Validate the change made to the prompt or parameter on the form in step 2, is present as expected
  72. Close the form
Topics
• Report Definition Import • NX • 835 Health Care Claim Payment/Advice • 835 • Site Specific Section Modeling
Update 58 Summary | Details
My To Do's Widget- to do approval
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView - My To Do's widget
  • Clinical Document Viewer
Scenario 1: 'My To Do's' Widget - Co-signing a To Do document sent to a Staff member('Final Approver')
Specific Setup:
  • A client [TestClient] must be enrolled in an existing episode.
  • Document routing must be enabled for a form [TestForm].
  • [StaffA], [StaffB] and [StaffC] have permissions set in their user definition or user role as "Final Approver", with [TestForm] selected as one of the forms they can be final approver on
  • [StaffC] also has "Co-Signer for Other Practitioners' set to "Yes" in their user definition or user role This allows a staff member to sign to do's for other staff members
  • All three staff members have the 'My To Do's' widget on their home view
  • Log in as [StaffA]
Steps
  1. Access [TestForm]
  2. Select [TestClient]
  3. Populate any required and desired fields
  4. File the form as "Final"
  5. At the 'Confirm Document" screen
  6. Validate the document preview displays data as expected
  7. Click to accept and route the document [TestDoc]
  8. At the "Route Document To" screen
  9. Add [StaffB] as an approver
  10. Validate [StaffB] is added to the approver list
  11. Click the check box for "Final Approver"
  12. Click [Submit]
  13. Validate submission is successful
  14. Log out a [StaffA]
  15. Log in as [StaffC]
  16. Navigate to the "My To Do's" list
  17. Click the [Sign Tab]
  18. In the "Staff" search field, search for [StaffB]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  19. Validate the To Do for [TestDoc] sent to [StaffB] in step 1 is present in the To Do list
  20. Select the To Do
  21. Validate the document preview displays data as expected
  22. Click [Accept]
  23. Validate the To do is removed from the To Do's widget, as expected
  24. Log out as [StaffC]
  25. Log in as [StaffB]
  26. Navigate to the "My To do's" list
  27. Validate the To Do for [TestDoc] sent to [StaffB] is not present in the To Do list, as expected
  28. Log out as [StaffB]
  29. Log in as [StaffA]
  30. Navigate to the "My To do's" list
  31. Validate there are no To Do's present, relating the To Do [TestDoc] sent to [StaffB] in step 1
  32. Open form "Clinical Document Viewer"
  33. Select [TestClient] in the "Select Client" field
  34. Click [Process]
  35. Click the [Results] tab
  36. Locate the row for the [TestDoc] and select the document
  37. Click [View]
  38. Validate the "Document" preview pane displays data as expected for the document
  39. Navigate to the end of the document
  40. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  41. Click [Close All Documents]
Topics
• NX • "My To Do's" widget
Update 61 Summary | Details
Modeled forms - table aliasing
Scenario 1: Modeled Forms - "Table Alias" field and data validations
Specific Setup:
  • Have two clients who are active in an existing episode's. [TestClientA], [TestClientB] and [TestClientC]
  • Have a modeled form [TestAlias] that contains a table with:
  • Mapped "Table" aliased fields. For example "Service" alias type fields:
  • "Date of Service", "Service Code", "Practitioner", "Program", and "Duration". (Note: these fields all must be populated to file the table alias)
  • Any other fields. For example, a "Draft/Final" or a "Date" field
  • Have a report [ReportA] created to display data in the "SYSTEM.Billing_tx_history" table
  • Have a report [ReportB] created to display data filed in the table used in form [TestAlias]
Steps
  1. Open [AliasForm]
  2. Select [TestClientA]
  3. Populate all the required fields to file the table alias: "Date of Service", "Service Code", "Practitioner", "Program", and "Duration"
  4. Populate any other desired fields on the form
  5. Submit the form as "Final".
  6. Validate submission is successful
  7. Close the form
  8. Generate [ReportA] to display the fields in the "SYSTEM.billing_tx_history" table
  9. Validate a new row is found for the service created by the modeled form in step1a
  10. Validate the "Date of Service", "Service Code", "Practitioner, Program", "Duration" and "Join_To_Tx_history" fields are populated as expected
  11. Generate [ReportB] to display data in the table field in the modeled form
  12. Validate all fields populated in step1a, are populated as expected
  13. Open [AliasForm]
  14. Select [TestClientB]
  15. Populate just one or more but "not" all the required fields necessary, to file the table alias data
  16. Populate any other desired fields on the form
  17. Submit as the form as "Final"
  18. Validate there are no messages indicating required fields are missing and the form files successfully
  19. Generate [ReportA] to display the fields in the "SYSTEM.billing_tx_history" table
  20. Validate there is not a new row in the table for the row filed in step 2a as expected, since not all the required fields to file the table alias were not populated when submitting the form
  21. Generate [ReportB] to display data in the table field in the modeled form
  22. Validate all fields populated in step 2a, are populated as expected
  23. Open [AliasForm]
  24. Select [TestClientC]
  25. Populate none of the required fields necessary to file the table alias data
  26. Populate any other desired fields on the form
  27. Submit as the form as "Final"
  28. Validate there are no messages indicating required fields are missing and the form files successfully
  29. Generate [ReportA], to display the fields in the "SYSTEM.billing_tx_history" table
  30. Validate there is not a new row in the table for the row filed in step 3a as expected, since all the required fields to file the table alias were not populated when submitting the form
  31. Generate [ReportB] to display data in the table field in the modeled form
  32. Validate any fields populated in step 3a, are populated as expected
Topics
• Diagnosis • NX
Update 62 Summary | Details
Service Documentation - New "Registry" settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
Scenario 1: Service Documentation - Validate Registry Setting - "Default Staff Associated With Current Login User"
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • [UserA] is a staff member [StaffA]
  • [UserB] is not a staff member
  • [TestClient] has an existing appointment [TestAppt] scheduled with staff member [StaffB]
  • [TestClient] has an existing service [TestService] filed staff member [StaffC]
  • Log in as [UserA]
Steps
  1. Open form "Registry setting"
  2. Set setting "Default Staff Associated With Current Login User" to "Y." [Note: This will default the Service Documentation "Practitioner" field with the current user's staff member set in form "User Definition", if defined. Selecting 'N' will leave the Practitioner field blank]
  3. Open [TestForm]
  4. Select client [TestClient]
  5. Select "New Service" in the "Documentation For" selection field
  6. Navigate to the "Practitioner" field
  7. Validate the field has defaulted in [StaffA] who associated with user [UserA], as expected
  8. Navigate back to the "Documentation For" selection field
  9. Select "Existing Appointment"
  10. Select [TestAppt] from the drop down list
  11. Navigate back to the "Practitioner" field
  12. Validate the field is now populated with [StaffB] not [StaffA], since [StaffB] is who the appointment was scheduled with
  13. Navigate back to the "Documentation For" selection field
  14. Select "Existing Service"
  15. Select [TestService] from the drop down list
  16. Navigate back to the "Practitioner" field
  17. Validate the field is now populated with [StaffC] not [StaffA], since [StaffC] is who the service was filed with
  18. Close the form
  19. Log out a [UserA]
  20. Log in as [UserB], who is not a staff member
  21. Open [TestForm]
  22. Select client [TestClient]
  23. Select 'New Service" in the "Documentation For" selection field
  24. Navigate to the "Practitioner" field
  25. Validate the field is not populated as expected, as the logged in user is not associated with a staff member
  26. Navigate back to the "Documentation For" selection field
  27. Select "Existing Appointment"
  28. Select [TestAppt] from the drop down list
  29. Navigate back to the "Practitioner" field
  30. Validate the field is populated with [StaffB], as expected
  31. Navigate back to the "Documentation For" selection field
  32. Select "Existing Service"
  33. Select [TestService] from the drop down list
  34. Navigate back to the "Practitioner" field
  35. Validate the field is populated with [StaffC], as expected
  36. Open form "Registry setting"
  37. Set setting "Default Staff Associated With Current Login User" to "N".
  38. Open [TestForm]
  39. Select client [TestClient]
  40. Select "New Service" in the "Documentation For" selection field
  41. Navigate to the "Practitioner" field
  42. Validate the Practitioner field is blank, as expected based on the registry setting
  43. Navigate back to the "Documentation For" selection field
  44. Select "Existing Appointment"
  45. Select [TestAppt] from the drop down list
  46. Navigate back to the "Practitioner" field
  47. Validate the field is populated with [StaffB], as expected
  48. Navigate back to the "Documentation For" selection field
  49. Select "Existing Service"
  50. Select [TestService] from the drop down list
  51. Navigate back to the "Practitioner" field
  52. Validate the field is populated with [StaffC], as expected
  53. Log out a [TestUserB]
  54. Log in as [TestUserA]
  55. Repeat step 7
  56. Validate results are the same, as expected
Scenario 2: Service Documentation - Validate Registry Setting - "Allow Appointment Modifications"
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Have two appointments set for a client [TestClient] for today, one set earlier than the other. For this example:
  • [ApptA] exists for staff [StaffA] from 7am to 8am today
  • [ApptB] exists for staff [StaffB] from 8am to 9am today
  • Have access to the "Registry Settings", "Scheduling Calendar" and form [TestForm]
Steps
  1. Open form "Registry Settings"
  2. Search for and select setting "Allow Appointment Modifications" for edit. Note: Selecting 'Y' will enable the Service Code, Location, Duration, Start Time and End Time fields on Service Documentation-enabled modeled forms when editing an existing appointment. Changes to these values will be applied to the appointment when the data is filed as Final. Selecting 'N' will disable the service documentation fields."
  3. Set the registry setting value to "N" and submit the form
  4. Open form [TestForm]
  5. Select client [TestClient]
  6. In the "Documentation For" selection field
  7. Select "Existing Appointment"
  8. Select [ApptA] from the drop down list
  9. Validate fields "Service Charge Code", "Location", "Duration, "Start Time" and "End Time" are "Disabled" as expected, based on the registry setting.
  10. Close the form
  11. Open form "Registry Settings"
  12. Search for and select setting "Allow Appointment Modifications" for edit.
  13. Set the registry setting value to "Y"
  14. Submit the form
  15. Open form [TestForm]
  16. Select client [TestClient]
  17. In the "Documentation For" selection field, select "Existing Appointment"
  18. Select [ApptA] from the drop down list
  19. Validate fields "Service Charge Code", "Location", "Duration', "Start Time" and "End Time" are "Enabled" this time as expected, based on the registry setting.
  20. Change the appointment start and end times for [ApptA] to the same times as those of [ApptB]
  21. Set the "Draft/Final" field to "Final
  22. Validate there's a message displayed blocking the change, indicating the [TestClient] already has an appointment for the new start and end times inputted.
  23. Change the appointment start and end times for [ApptA] to a start and end time that does not conflict with another appointment
  24. Set the "Duration" field to the correct value based on the appointment start and end times entered
  25. Change the "Service Charge Code" field to a new value
  26. Validate the value is accepted
  27. Change the "Service Location" to a new value
  28. Validate the value is accepted
  29. Populate the other required fields and any other fields on the form
  30. Set the "Draft/Final" field to "Final
  31. Click [OK] at the "Selecting 'Final' prevents further edits dialog
  32. Click [Submit]
  33. Validate submission is successful
  34. Open form "Scheduling Calendar"
  35. Navigate to [ApptA] in the appointment grid
  36. Validate the start and end times of the appointment on the grid is match new values entered in step 1c
  37. Click to edit the appointment
  38. Validate the value "Service Start Time" field, is the new value entered in step 1c
  39. Validate the value "Service End Time" field, is the new value entered in step 1c
  40. Validate the value "Duration" field, is the new value entered in step 1d
  41. Validate the "Service Code" field, is the new value entered in step 1e
  42. Validate the "Location" field, is the new value entered in step 1f
  43. Validate all other fields are populated, as expected
  44. Close the form
Scenario 3: Service Documentation - Validate Registry Setting - "Check Service Programs"
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • In form "Program Maintenance"
  • [ProgramA] has [ProgramB] selected as an associated service program in the field "Associated Service Programs"
  • [ProgramA] does not have [ProgramC] selected as and associated service program in the field "Associated Service Programs"
  • [TestClient] is admitted in [ProgramA]
  • Have registry setting "Restrict Practitioner Search By Program" set to "Y"
  • In form "Practitioner Enrollment",
  • [StaffA] has [ProgramA] selected as a program their associated to in the "Program Association" field
  • [StaffA] does not have [ProgramD] selected as a program their associated to in the "Program Association" field
  • Logged in user has access to the "Registry Settings" and [TestForm]
Steps
  1. Open form "Registry Settings"
  2. Search for and select setting "Check Service Program".
  3. Set the registry setting value to 'W'
  4. Note: a registry setting value set of 'W' or 'E' will enable checks on any "Service Documentation" enabled forms to ensure the "Service Program" value is a valid selection based on the practitioner's program associations and the current episodes program association. A registry setting value set of 'N', will disable these checks, and no error or warning will display to the user."
  5. Submit the form
  6. Open [TestForm]
  7. Select [TestClient]
  8. Select to create a "New Service"
  9. In the "Practitioner" field select [StaffA]
  10. Populate all the other required and desired fields other than the "Service Program" field
  11. In the "Service Program" field select [ProgramB]
  12. Validate the value is accepted and there are no messages
  13. In the "Service Program" field select [ProgramC]
  14. Validate a warning message indicating the following is displayed, "WARNING: Service program not valid for the given episodes program. Do you wish to continue do you want to continue?
  15. Click [No]
  16. Click [OK] in the "Action Cancelled" dialog
  17. Validate the Service Program" field is cleared
  18. In the "Service Program" field select [ProgramC] again
  19. This time at the "Warning" message, click [Yes] to continue
  20. Validate the Service Program" field is still populated with [ProgramC]
  21. In the "Service Program" field select [ProgramD]
  22. Validate a message is displayed, "WARNING: Service program not associated with the selected practitioner. Do you wish to continue?
  23. Click [No]
  24. Click [OK] in the "Action Cancelled" dialog
  25. Validate the Service Program" field is returned to its previous value [ProgramC]
  26. In the "Service Program" field select [ProgramD] again
  27. This time at the "Warning" message, click [Yes] to continue
  28. Validate the Service Program" field is still populated with [ProgramD]
  29. Select a "Final" in the "Draft/Final" field
  30. Validate a warning message indicating the following is displayed again as a final check, "WARNING: Service program not associated with the selected practitioner. Do you wish to continue finalizing?
  31. Click [Yes]
  32. At the "Selecting "Final" prevents future edits\" dialog
  33. Click [OK]
  34. Click [Submit]
  35. Validate the form files successfully
  36. Open form "Registry Settings", search for and select setting "Check Service Program".
  37. Set the registry setting value to 'E' and submit the form
  38. Open [TestForm]
  39. Select [TestClient]
  40. Select to create a "New Service"
  41. In the "Practitioner" field select [StaffA]
  42. Populate all the other required and desired fields other than the "Service Program" field
  43. In the "Service Program" field select [ProgramB]
  44. Validate the value is accepted and there are no messages
  45. In the "Service Program" field select [ProgramC]
  46. Validate an "Error" message is displayed stating, "Service program not valid for the given episodes program"
  47. Click [OK]
  48. Validate the Service Program" field is cleared
  49. In the "Service Program" field select [ProgramD]
  50. Validate there is an "Error" message stating "Service program not associated with the selected practitioner"
  51. Click [OK]
  52. Validate the Service Program" field is cleared
  53. In the "Service Program" field select [ProgramA]
  54. Validate there are no messages blocking entry
  55. Validate the Service Program" field is populated with [ProgramA], as expected
  56. Select a "Final" in the "Draft/Final" field
  57. Validate there are no messages blocking entry
  58. At the "Selecting "Final" prevents future edits." dialog
  59. Click [OK]
  60. Click [Submit]
  61. Validate the form files successfully
  62. Open form "Registry Settings"
  63. Search for and select setting "Check Service Program".
  64. Set the registry setting value to any value other than 'W', 'E', or 'N'
  65. Validate an error is displayed "The selected value is not valid in the current system code for the following reason: Please enter 'N', 'W' or 'E'
  66. Set the registry setting value to 'N'
  67. Submit the form
  68. Open [TestForm]
  69. Select [TestClient]
  70. Select to create a "New Service"
  71. In the "Practitioner" field select [StaffA]
  72. Populate all the other required and desired fields other than the "Service Program" field
  73. In the "Service Program" field select [ProgramB]
  74. Validate the value is accepted and there are no messages
  75. Validate the Service Program" field is populated with [ProgramB], as expected
  76. In the "Service Program" field select [ProgramC]
  77. Validate the value is accepted and there are no messages
  78. Validate the Service Program" field is populated with [ProgramC], as expected
  79. In the "Service Program" field select [ProgramD]
  80. Validate the value is accepted and there are no messages
  81. Validate the Service Program" field is populated with [ProgramD], as expected
  82. In the "Service Program" field select [ProgramA]
  83. Validate the value is accepted and there are no messages
  84. Validate the "Service Program" field is populated with [ProgramD], as expected
  85. Select a "Final" in the "Draft/Final" field
  86. Validate there are no messages blocking entry
  87. At the "Selecting "Final" prevents future edits." dialog
  88. Click [OK]
  89. Click [Submit]
  90. Validate the form files successfully
Topics
• Service Documentation • NX
Update 63 Summary | Details
GA ASO - Entity dictionaries
Scenario 1: Validate the "SYSTEM.RADplus_dict_user_def_gaaso table
Specific Setup:
  • Have a modeled envelope [TestEnvelope] set to use "GA ASO" entity database
  • Have a modeled table[TestTable] created in [TestEnvelope] that contains the following dictionary fields. For this test the following will be used:
  • A 'Single-select" dictionary: Field number '1.01", with field description of "Dictionary 1".
  • Has the following dictionary code/values added:
  • Dictionary Code "1" with a dictionary value of "Single 1"
  • Dictionary Code "2" with a dictionary value of "Single 2'
  • A 'Multiple-select" dictionary: Field number '1.02", with a field description of "Dictionary 2"
  • Has the following dictionary code/values added:
  • Dictionary Code "5" with a dictionary value of "Mult 1"
  • Dictionary Code "6" with a dictionary value of "Mult 2"
  • Have a report or query created for table 'RADplus_dict_user_def_gaaso', to display dictionary codes, values and descriptions
Steps
  1. Generate the report or query created for table 'RADplus_dict_user_def_gaaso', to display field values
  2. Based on the set up, validate the report results display rows with the expected data populated in each column. For example, in this test following results would be expected:
  3. Field Number: "1.01" ; Field Description: "Dictionary 1" ;Dictionary Code: "1 ; Dictionary Value : "Single 1"
  4. Field Number: "1.01" ; Field Description: "Dictionary 1" ;Dictionary Code: "2" ; Dictionary Value : "Single 2"
  5. Field Number: "1.02" ; Field Description: "Dictionary 2" ;Dictionary Code: "5" ; Dictionary Value : "Mult 1"
  6. Field Number: "1.02" ; Field Description: "Dictionary 2" ;Dictionary Code: "6" ; Dictionary Value : "Mult 2"
State Form - Modeling table
Scenario 1: Validate table 'SYSTEM.RADplus_dict_user_def_stateform'
Specific Setup:
  • Have a modeled envelope [TestEnvelope] set to use "Stateform" entity database
  • Have a modeled table[TestTable] created in [TestEnvelope] that contains the following dictionary fields. For this test the following will be used:
  • A 'Single-select" dictionary: Field number '1.02", with field description of "Single Dictionary".
  • Has the following dictionary code/values added:
  • Dictionary Code "1" with a value of "One"
  • Dictionary Code "2" with a value of "Two"
  • Dictionary Code "3" with a value of "Three"
  • A 'Multiple-select" dictionary: Field number "1.03", with a field description of "Multiple Dictionary"
  • Has the following dictionary code/values added:
  • Dictionary Code "1" with a value of "One"
  • Dictionary Code "2" with a value of "Two"
  • Dictionary Code "3" with a value of "Three"
  • Have a report or query created for table 'SYSTEM.RADplus_dict_user_def_stateform', to dicitonary codes, values and descriptions
Steps
  1. Generate the report or query created for table 'SYSTEM.RADplus_dict_user_def_stateform' to display field values
  2. Based on the set up, validate the report results display rows with the expected data populated in each column. For example, in this test following results would be expected:
  3. Field Number: "1.02" ; Field Description: "Single Dictionary"; Dictionary Code: "1" ; Dictionary Value : "One"
  4. Field Number: "1.02" ; Field Description: "Single Dictionary"; Dictionary Code: "2" ; Dictionary Value : "Two"
  5. Field Number: "1.02" ; Field Description : "Single Dictionary"; Dictionary Code: "3"; Dictionary Value : "Three"
  6. Field Number: "1.03"; Field Description : "Multiple Dictionary" ;Dictionary Code: "1" ; Dictionary Value : "One"
  7. Field Number: "1.03"; Field Description : "Multiple Dictionary" ;Dictionary Code: "2" ; Dictionary Value : "Two
  8. Field Number: "1.03"; Field Description : "Multiple Dictionary" ;Dictionary Code: "3" ; Dictionary Value : "Three
Topics
• SQL Data Access • NX • State Form Tools
Update 65 Summary | Details
Document Management Definition - Syncing multiple root system environments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Document Capture
  • Clinical Document Viewer
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field.
  6. Select the desired entity in the "Entity" field.
  7. Populate any other desired fields in the "Form" section.
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list.
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report".
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section.
  19. Click [File].
  20. Validate the form files successfully.
  21. Click [Select Form].
  22. Select the form just submitted in step 5.
  23. Validate all fields populated in steps 1 thru 5, are populated as expected.
  24. Click back to the [Form] section.
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list.
  29. Click [Select Form].
  30. Select the form "Inbox Attachments".
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  33. Click [OK].
  34. Click [Select Form].
  35. Select the form "Results Document".
  36. Click [Delete].
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  38. Click [OK].
  39. Close the form.
Scenario 2: Document Management Defaults - Perceptive Synchronization Options field
Steps

Internal Testing Only

Scenario 3: Document Management Definition - Perceptive Syncing Form Definitions in Multiple Server environment
Specific Setup:
  • To be tested in a multiple server environment that has multiple root system codes.
  • Using the "Document Management Definition" form:
  • Identify a form that exists in all system codes.
Steps
  1. Using the "Document Management Definition" form:
  2. Edit the existing form identified as existing in all root system codes.
  3. File the form.
  4. Open the "Client Document Capture" form.
  5. Scan or import a document.
  6. Select the form edited in "Document Management Definition".
  7. Scan or import the document.
  8. Using "Clinical Document Viewer", select the test client.
  9. Validate the document that was just filed for the form that exists in all root system codes displays as it was previously filed.
Scenario 4: Clinical Document Viewer - Filters, Selections and Restrictions
Specific Setup:
  • Select an existing client who has multiple documents on file that have been scanned, imported or routed via document routing, scanned.
Steps
  1. Open the "Clinical Document Viewer" form.
  2. Validate the filters such as "Select All or Individual", "User", "Document Status", "Program", "Episode", "Document Source", "Document Origination Date Start", "Document Origination Date End" all filter in the appropriate manner.
  3. Under Form Selection, validate that you can choose the form selection by "Categories/Forms" and only those documents appear in the document list.
  4. Using the "Document Management Definition" form, identify a form as to "Exclude from Electronic Medical Record".
  5. Validate the document list doesn't include documents that are to be excluded.
  6. Using the "Document Management Definition" form, identify a form as "Do Not Print".
  7. Going back to the "Clinical Document Viewer" form, validate the forms marked as "Do Not Print" are excluded,
  8. Using "Document Management Definition" form, mark a document type as "Do not release".
  9. Going back to the "Clinical Document Viewer" form, validate the forms marked as "Do Not Release" are excluded.
Document Management Definition - Syncing multiple root system environments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Document Capture
  • Clinical Document Viewer
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field.
  6. Select the desired entity in the "Entity" field.
  7. Populate any other desired fields in the "Form" section.
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list.
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report".
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section.
  19. Click [File].
  20. Validate the form files successfully.
  21. Click [Select Form].
  22. Select the form just submitted in step 5.
  23. Validate all fields populated in steps 1 thru 5, are populated as expected.
  24. Click back to the [Form] section.
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list.
  29. Click [Select Form].
  30. Select the form "Inbox Attachments".
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  33. Click [OK].
  34. Click [Select Form].
  35. Select the form "Results Document".
  36. Click [Delete].
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  38. Click [OK].
  39. Close the form.
Scenario 2: Document Management Definition - Perceptive Syncing Form Definitions in Multiple Server environment
Specific Setup:
  • To be tested in a multiple server environment that has multiple root system codes.
  • Using the "Document Management Definition" form:
  • Identify a form that exists in all system codes.
Steps
  1. Using the "Document Management Definition" form:
  2. Edit the existing form identified as existing in all root system codes.
  3. File the form.
  4. Open the "Client Document Capture" form.
  5. Scan or import a document.
  6. Select the form edited in "Document Management Definition".
  7. Scan or import the document.
  8. Using "Clinical Document Viewer", select the test client.
  9. Validate the document that was just filed for the form that exists in all root system codes displays as it was previously filed.
Document Management Definition - Syncing multiple root system environments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Document Capture
  • Document Capture
  • Clinical Document Viewer
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field.
  6. Select the desired entity in the "Entity" field.
  7. Populate any other desired fields in the "Form" section.
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list.
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report".
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section.
  19. Click [File].
  20. Validate the form files successfully.
  21. Click [Select Form].
  22. Select the form just submitted in step 5.
  23. Validate all fields populated in steps 1 thru 5, are populated as expected.
  24. Click back to the [Form] section.
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list.
  29. Click [Select Form].
  30. Select the form "Inbox Attachments".
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  33. Click [OK].
  34. Click [Select Form].
  35. Select the form "Results Document".
  36. Click [Delete].
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  38. Click [OK].
  39. Close the form.
Scenario 2: Document Management Defaults - Perceptive Synchronization Options field
Steps

Internal Testing Only

Scenario 3: Document Management Definition - Perceptive Syncing Form Definitions in Multiple Server environment
Specific Setup:
  • To be tested in a multiple server environment that has multiple root system codes.
  • Using the "Document Management Definition" form:
  • Identify a form that exists in all system codes.
Steps
  1. Using the "Document Management Definition" form:
  2. Edit the existing form identified as existing in all root system codes.
  3. File the form.
  4. Open the "Client Document Capture" form.
  5. Scan or import a document.
  6. Select the form edited in "Document Management Definition".
  7. Scan or import the document.
  8. Using "Clinical Document Viewer", select the test client.
  9. Validate the document that was just filed for the form that exists in all root system codes displays as it was previously filed.
Topics
• Document Management • NX • Document Routing
Update 70 Summary | Details
Envelope Import - UTC data entry fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
Scenario 1: Validate Envelope "Export/Import" in "UTC" Date/Time enabled systems
Specific Setup:
  • Have a system enabled to use "UTC" date and time. Please note: this must be done by a Netsmart Representative.
  • [EnvelopeA] contains modeled form [FormA], which contains one or more of the available "UTC" related date/time fields as one of the fields in the forms "Pre-display". For example: "Data Entry Calculated Timezone", "Data Entry Offset", "Data Entry UTC Timestamp" or "Data Entry Workstation Timezone".
  • [EnvelopeB] contains modeled form [FormB] which does not contain any of the available "UTC" related date/time fields as one of the fields in the forms "Pre-display".
Steps
  1. Open form "Envelope Export"
  2. Select [EnvelopeA]
  3. Click [Begin Export]
  4. In the "File Explorer" dialog, select a folder location in the "Save In" field to save the export file.
  5. Click [Save]
  6. Close the form
  7. Open file "Envelope Import"
  8. Click [Select Envelope Import File]
  9. In the "File Explorer" dialog, navigate to the location of the [EnvelopeA] export file
  10. Select the file and click [Open]
  11. Select the "Overwrite Existing" radio button
  12. Click [Begin Import Scan]
  13. Click [Begin Import]
  14. At the "Import Complete" dialog, click [OK]
  15. Close the form
  16. At the Home View, search for [FormA] and open the form
  17. Populate the desired fields on the form
  18. Submit the form
  19. Validate the form files successfully
  20. Re-open [FormA]
  21. Select the row just submitted in step 3
  22. At the "Pre-Display" screen, validate the values for all pre-display fields selected in the setup, are displayed as expected
  23. Click to edit the row
  24. Validate al fields are populated as expected
  25. Repeat steps 1 thru 4 for [EnvelopeB]
  26. Validate results are as expected
Topics
• Envelope Import • NX • Envelope Export
2022 Update 124 Summary | Details
Chart View
Scenario 1: "Chart" view - 'Sort/Filter' data row validations
Specific Setup:
  • Have a modeled form [TestForm] that contains an "SQL Multiple Dictionary" field [MultField]
  • [Multfield] contains several dictionary values with various character counts. For this example:
  • [ValueA] has a character count of "32"; [ValueB] has a character count of "64"; [ValueC] has a character count of "128; [ValueD] has a character count of "256"; [ValueE] has a character count of "299"
  • [ClientA], [ClientB] and [ClientC] that have data rows submitted in [TestForm]
  • [ClientA] has two rows submitted
  • [Row1] with [ValueA] selected
  • [Row2] with [ValueB] selected
  • [ClientB] has four rows submitted
  • [Row1] with [ValueA] selected
  • [Row2] with [ValueB] selected
  • [Row3] with [ValueC] selected
  • [Row4] with [ValueC], [ValueD] and [ValueE] selected
  • [ClientC] has one row submitted
  • Row1 with [ValueB], [ValueC] and [ValueE] selected
  • [TestUser] has form [TestForm] added to their "Chart" view forms
Steps
  1. At the home view, select [ClientA] and then right click to open their chart
  2. Select [TestForm] from the chart forms section
  3. Validate the data row preview section, displays all the rows filed for [ClientA] in the setup
  4. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField],
  5. Click the "Sort/Filter" dropdown list
  6. Validate the "Filter" box contains each row submitted for [ClientA] in the setup
  7. Select one or more values from list and click [OK]
  8. Validate just the row(s) selected are displayed in the preview section
  9. Validate the dictionary value(s) submitted in each row, are displayed as expected
  10. Close the clients chart
  11. At the home view, select [ClientB] and then right click to open their chart
  12. Select [TestForm] from the chart forms section
  13. Validate the data row preview section, displays all the rows filed for [ClientB] in the setup
  14. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField]
  15. Click the "Sort/Filter" dropdown list
  16. Validate the "Filter" box contains each row submitted for [ClientB] in the setup
  17. Select one or more values from list and click [OK]
  18. Validate just the row(s) selected are displayed in the preview section
  19. Validate the dictionary value(s) submitted in each row, are displayed as expected
  20. Close the clients chart
  21. At the home view, select [ClientC] and then right click to open their chart
  22. Select [TestForm] from the chart forms section
  23. Validate the data row preview section, displays all the rows filed for [ClientC] in the setup
  24. Validate the "Sort/Filter" selection field is displayed and is populated with field [MultField]
  25. Click the "Sort/Filter" dropdown list
  26. Validate the "Filter" box contains each row submitted for [ClientC] in the setup
  27. Select one or more values from list and click [OK]
  28. Validate just the row(s) selected are displayed in the preview section
  29. Validate the dictionary value(s) submitted in each row, are displayed as expected
  30. Close the clients chart
Guarantor Search fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Fast Financial Eligibility
Scenario 1: "Guarantor" lookup - search results validation
Specific Setup:
  • In form "Guarantor/Payors", have or create two guarantors:
  • [GuarA] has a value populated in "Guarantor Name for Alpha Lookup" field that include parenthesis. (Make a note of their "Guarantor" number assigned)
  • [GuarB] does not have a value populated in "Guarantor Name for Alpha Lookup" field that includes parenthesis. (Make a note of their "Guarantor" number assigned)
  • Have access to a form that contains a "Guarantor" lookup field. For this example, form "Fast Financial Eligibility" is used
Steps
  1. Open the form "Fast Financial Eligibility"
  2. Select any client
  3. Navigate to the "Guarantor #1" search field
  4. Enter a search for [GuarA] using their entire "Guarantor Name for Alpha Lookup" value
  5. Validate the expected value is found and displays without truncation
  6. Enter a search for [GuarA] using just the first letter of their "Guarantor Name for Alpha Lookup" value
  7. Validate the expected value is found and displays without truncation
  8. Enter a search for [GuarA] using the first two or more letters of their "Guarantor Name for Alpha Lookup" value
  9. Validate the expected value is found and displays without truncation
  10. Enter a search for [GuarA] using their assigned "Guarantor" number
  11. Validate the expected value is found and displays without truncation
  12. Populate any other desired fields on the form
  13. Submit the form
  14. Validate the form files successfully
  15. Return to the "Fast Financial Eligibility" form
  16. Select the client used in step 1
  17. Select the row submitted in step 1
  18. Validate that all field are populated, as expected
  19. Open the form "Fast Financial Eligibility"
  20. Select any client
  21. Navigate to the "Guarantor #1" search field
  22. Enter a search for [GuarB] using their entire "Guarantor Name for Alpha Lookup" value
  23. Validate the expected value is found and displays without truncation
  24. Enter a search for [GuarB] using just the first letter of their "Guarantor Name for Alpha Lookup" value
  25. Validate the expected value is found and displays without truncation
  26. Enter a search for [GuarB] using the first two or more letters of their "Guarantor Name for Alpha Lookup" value
  27. Validate the expected value is found and displays without truncation
  28. Enter a search for [GuarB] using their assigned "Guarantor" number
  29. Validate the expected value is found and displays without truncation
  30. Submit the form
  31. Validate the form files successfully
  32. Return to the "Fast Financial Eligibility" form
  33. Select the client used in step 3
  34. Select the row submitted in step 3
  35. Validate that all field are populated, as expected
Appointment Scheduling - notifications
Scenario 1: Scheduling Calendar - Validate appointment status To Do notifications
Specific Setup:
  • In form "Appointment Scheduling Notification Type Definition", have notification status submitted within form for an "Appointment Status". For this example appointment status "Cancelled" is used.
  • In form "Notifications Setup", have a notification created with the following setup:
  • The "Appointment Canceled" selected in the "Notification Type" field.
  • The "Appointment Practitioner" selected in the "Send Notification(s) to field.
  • "To Do" selected in the "Notification Method" field.
  • The 'Notification Text' field, has text populated in the field that contains greater than or less than symbols. For example, text that may include keyword values: "Your <APPOINTMENT_DATE> appointment with <PATIENT_NAMES> scheduled for <CURRENT_DATE> has been cancelled".
  • [TestUser] is a staff member and has the "My To Do's" widget on their home view.
  • For any client, have an appointment [TestAppt] scheduled with [TestUser] in form "Scheduling Calendar".
  • Log in as [TestUser]
Steps
  1. Open form "Scheduling Calendar"
  2. Navigate to [TestAppt] on the scheduling calendar
  3. Right-Click on the appointment and select "Details/Edit"
  4. In the "Scheduling Calendar - Appointment Details" form, click on the "Appointment Status" field and select "Cancelled"
  5. Submit the form
  6. Close the Scheduling Calendar" form
  7. At the home view, navigate to the "My To Do's" widget"
  8. Locate the To Do with "Scheduling Calendar - Appointment Details" populated In the "Form" column
  9. Click [Review To Do Item]
  10. Validate the information displayed in the "To Do Information" field is as expected and consistent with the notification message text entered in form "Notifications Setup", in the set up
  11. Click the "Reviewed" check box
  12. Click [Submit]
  13. Validate the To Do has been removed from the "My To Do's" widget
Topics
• Chart Review • Guarantor • NX • Appointment Management
2022 Update 139 Summary | Details
ScriptLink - launch form
Scenario 1: Validate a "ScriptLink" script set on a field to launch another form
Specific Setup:
  • Have a "ScriptLink" script that is configured to launch a specific form. For this example, form "Update Client Data" is used
  • In "Form Designer" the script has been imported in any desired form [TestForm] and is set to trigger when a field [TestField] is populated
Steps
  1. Open form [TestForm]
  2. Select a client [TestClient]
  3. Navigate to field [TestField]
  4. Populate the field
  5. Validate the form configured to launch via the "ScriptLink" script, has launched for [TestClient]. For this exampled form "Update Client Data" has launched
  6. Populate the form
  7. Submit the form
  8. Validate the form files successfully
  9. Back on [TestForm], populate the desired fields on form
  10. Submit the form
  11. Validate the form files successfully
  12. Return to form [TestForm]
  13. Select [TestClient]
  14. Select the row just submitted in step 1
  15. Validate field [TestField] is populated as expected
  16. Validate all other fields are populated as expected
  17. Close the form
  18. Open form "Update Client Data"
  19. Select [TestClient]
  20. Validate all fields are populated as expected
Topics
• Scriptlink • Form Designer • NX
 

RADplus_2023_Quarterly_Release_2023.02_Details.csv