Skip to main content

RADplus 2023 Monthly Release 2023.01.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)
  • Document Routing Setup (PM)
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 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 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:
  • Progress Notes (Group and Individual)
  • Treatment Plan
  • Diagnosis
  • 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 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 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
  • Registry Settings (PM)
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:
  • Document Management Definition
  • 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 39 Summary | Details
Widget - form launch links
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
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
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Progress Notes (Group and Individual)
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 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:
  • Registry Settings (PM)
  • Progress Notes (Group and Individual)
  • Clinical Document Viewer
  • Document Routing Setup (PM)
  • 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 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:
  • Registry Settings (PM)
  • Document Routing Setup (PM)
  • Client
  • Disclosure Management
  • Disclosure Management Configuration
  • Progress Notes (Group and Individual)
  • 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 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