RADplus 2024 Monthly Release 2024.02.00 Acceptance Tests

Last updated
Save as PDF

Update 30 Summary \| Details System Generated Email Settings Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: System Generated Email Settings User Failed Authentication Question Scenario 1: The 'Systems Generated Email Settings' form - Validate submission and functionality ("AWS" enabled systems) Specific Setup: In Avatar, an active user [TestUser] with a valid password exists on the system. (Make note of the password) [TestUser] has an active email address [TestEmailAddress] Have access to form "User Failed Authentication Question" Steps Open form "System Generated Email Settings", Populate the "SMTP Server" field, "Email From Address" field, "Email Authentication User ID", and "Email Authentication Password" fields, with the appropriate values for the system Navigate to the "Use TLS" field, Validate the field is a required field, as expected for "AWS" systems Set the value to "No" In the "Port Number" field, populate the field with a port number, if required for the system Submit the form Validate the form submits successfully Return to "System Generated Email Settings" form Validate all fields are populated as expected Open form "User Failed Authentication Question" Populate the "System Code" Populate the user name for [TestUser] in the "User Name" Populate the password for [TestUser] in the "Password" Populate the "Email Address" field with the email [TestEmailAddress] for [TestUser]i Click [Test Email] Validate an error message is received stating "System is not properly configured for Email" Click [OK] Submit the form Re-open form "System Generated Email Settings", Navigate to the "Use TLS" field, Set the value to "Yes" Submit the form Validate the form submits successfully Re-open form "User Failed Authentication Question" Populate the "System Code" Populate the user name for [TestUser] in the "User Name" Populate the password for [TestUser] in the "Password" Validate all other fields are populated as expected Click [Test Email] Validate the dialog, "An email with the subject Avatar User Failed Authentication Question has been sent to [TestEmailAddress]" is displayed Click [OK] and close the form As [TestUser], navigate to their email inbox Validate [TestUser] has received an email in their inbox with subject "Avatar User Failed Authentication Question" Click to open the email Validate the text of the email states "This is a test Email" Close the email Log in as [TestUser] At the "Password" prompt, enter an incorrect password Validate a message stating "You have entered an invalid password. Do you wish to answer your failed authentication question", is displayed and click [OK] Populate the "Failed Authentication" question, with the appropriate answer and click [OK] Validate the message " An Email will be sent to you containing your new system password" is displayed and click [OK] Navigate to their email inbox Validate [TestUser] has received an email in their inbox with subject "Notice of Change to Avatar Login Information" and open the email Copy the temporary password included in the email Return to the login screen and paste in the temporary password in the password box and click [OK] Validate a message "Your current password is system generated.You must enter a new password", is displayed and click [OK] Populate the "Enter new password" field Populate the "Re-enter new password" field Click [OK] Validate the user is logged in successfully Scenario 2: The 'Systems Generated Email Settings' form - Validate submission and functionality (Non "AWS" enabled systems) Specific Setup: In Avatar, an active user [TestUser] with a valid password exists on the system. (Make note of the password) [TestUser] has an active email address [TestEmailAddress] Have access to form "User Failed Authentication Question" Steps Open form "System Generated Email Settings", Populate the "SMTP Server" field, "Email From Address" field, "Email Authentication User ID", and "Email Authentication Password" fields, with the appropriate values for the system Navigate to the "Use TLS" field, Validate the field is not a required field, since this is not an "AWS" system Set the value to "No" In the "Port Number" field, populate the field with a port number if required for the system Submit the form Validate the form submits successfully Return to "System Generated Email Settings" form and validate all fields are populated as expected Open form "User Failed Authentication Question" Populate the "System Code" Populate the user name for [TestUser] in the "User Name" Populate the password for [TestUser] in the "Password" Populate the "Email Address" field with the email [TestEmailAddress] for [TestUser]i Click [Test Email] Validate the dialog "A test email with the subject 'Avatar User Failed Authentication Question' has been sent to [TestEmailAddress] Click [OK] and close the form As [TestUser Navigate to their email inbox Validate [TestUser] has received an email in their inbox with subject "Avatar User Failed Authentication Question" Click to open the email Validate the text of the email states "This is a test Email" Close the email Re-open form "System Generated Email Settings", Navigate to the "Use TLS" field, Set the value to "Yes" Submit the form Validate the form submits successfully Re-open form "User Failed Authentication Question" Populate the "System Code" Populate the user name for [TestUser] in the "User Name" Populate the password for [TestUser] in the "Password" Validate all other fields are populated as expected Click [Test Email] Validate the dialog "A test email with the subject 'Avatar User Failed Authentication Question' has been sent to [TestEmailAddress] Click [OK] and close the form As [TestUser] Navigate to the email inbox Validate [TestUser] has received an email in their inbox with subject "Avatar User Failed Authentication Question" Click to open the email Validate the text of the email states "This is a test Email" Close the email Log in as [TestUser] At the "Password" prompt, enter an incorrect password Validate a message stating "You have entered an invalid password. Do you wish to answer your failed authentication question", is displayed and click [OK] Populate the "Failed Authentication" question, with the appropriate answer and click [OK] Validate the message " An Email will be sent to you containing your new system password" is displayed and click [OK] Navigate to their email inbox Validate [TestUser] has received an email in their inbox with subject "Notice of Change to Avatar Login Information" and open the email Copy the temporary password included in the email Return to the login screen Paste in the temporary password in the password box and click [OK] Validate a message "Your current password is system generated.You must enter a new password", is displayed and click [OK] Populate the "Enter new password" field Populate the "Re-enter new password" field Click [OK] Validate the user is logged in successfully	Topics • Forms
Update 47 Summary \| Details Document Management - Approval Notifications Scenario 1: User Role Definition - Approval Notifications Steps Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "All Forms". Open the "User Definition". Assign the user to the user role "AllForms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "No Forms". Open the "User Definition". Assign the user to the user role "NoForms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is not received. Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "Specify Forms". Open the "User Definition". Assign the user to the user role "SpecifyForms". Click [Select Forms for Approval Notifications]. Select specific forms. Open the "Client Document Capture" form. Scan or import a document in to one of the forms that were set up in the previous steps for this user role. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Approve the document. Scenario 2: User Role Definition - Validate 'Copy User Roles to Other System Codes' functionality Specific Setup: Have a system defined with two root system codes. [SYSA] and [SYSB]. Both system codes contain the same "Forms" and associated form "ID's" defined in form "Document Management Definition". In [SYSA], create a new form type [FormZ] in form "Document Management Definition". Note the form type ID number, for this example "28" is used. In [SYSA], have or create a new user role [RoleZ]. Have the 'Registry Settings' form, set the 'Copy User Roles to Other System Codes' registry setting to "Y". Log into root code [SYSA]. Steps Open the 'User Role Definition' form. Click [Select User Role]. Select [RoleZ]. In the 'Select Codes To Copy User Role To' field, select [SYSB]. Populate any other required fields in that section. Click the "Document Management" Section. Select "No" in the 'Is this user a Document Management Administrator?' field. Select "Specify Forms" in the 'Forms Allowed To View' field. Select the document created in the setup, [FormZ]. Submit the form. Validate an error is displayed "The following document form types to view do not exist in all selected system codes within 'System Codes To Copy User Role To' and will be unchecked". Document form type '28' does not exist in system code [SYSB]. Click [OK] At the "Submission will be aborted" error message, Click [OK]. Log out of root code [SYSA]. Log into root code [SYSB]. Open form "Document Management Definition". Click [Select Form]. Click [Add New]. Validate the "Form ID" field has been assigned the same form ID number assigned to [FormZ]. in the se up, form ID "28". Populate the "Form Name" field. Populate any other required fields. Submit the form. Log out of root code [SYSB]. Log into root code [SYSA]. Open the 'User Role Definition' form. Click [Select User Role]. Select user role, [RoleZ]. In the 'Select Codes To Copy User Role To' field, select [SYSB]. Populate any other required fields in that section. Click the "Document Management" Section. Select "No" in the 'Is this user a Document Management Administrator?' field. Select "Specify Forms" in the 'Forms Allowed To View' field. Select the document created in the setup, [FormZ]. Select 'Specify Forms' in the "Forms to Send Approval Notifications" field. Click "Select Forms for Approval Notifications". Select the forms you want to use the Approval Notifications functionality. Select "Yes" in the "Limit Approval Notifications to Caseload Only". Submit the form. Validate the form files successfully. Return to the form. Select [RoleZ]. Click the "Document Management" Section. Click "Specify Forms" in the 'Forms Allowed To View' field. Click [Select Forms to View]. Validate [FormZ] is selected, as expected. Log out of root code [SYSA]. Log into root code [SYSB]. Open the 'User Role Definition' form. Click [Select User Role]. Validate the "Select User Role" field contains [RoleZ]. Select [RoleZ]. Click the "Document Management" Section. Select "Specify Forms" in the 'Forms Allowed To View' field. Click [Select Forms to View]. Validate [FormZ] is present and selected in the forms list, as expected. Validate "Forms to Send Approval Notifications" field is set to "Specify Forms". Click "Select Forms for Approval Notifications". Validate the forms you want to use the Approval Notifications functionality. Validate "Limit Approval Notifications to Caseload Only" is set to "Yes". Close the form. User Definition/User Role Definition - Approval notifications fields added Scenario 1: Update user with the "WEBSVC.UserManagement" web service Specific Setup: Have a system with "Avatar Web Services" installed Have the "WEBSVC.UserManagement" web service imported into the program and the "UpdateUser" web service "request" configured for each root system code. Have an existing user created in form "User Definition" Steps Open program "SOAPUI" or other web service program. Click and open the "UpdateUser" request for the first root system code. Set the "<UserId>" property equal to the user's Avatar User id. Update any field property in the request. For example: Set the "<UserDescription>" property to a new user description. Click [Submit]. Validate a message "User successfully updated" is received. Open "User Definition" to edit the user. Validate that the field updated with the web service, is populated as expected. Scenario 2: Create a user with the "WEBSVC.UserManagement" web service Specific Setup: Have a new user who requires an Avatar "UserID". "UserA" Have a system with "Avatar Web Services" installed Have a program to test web services, for example "SoapUI" Have the "WEBSVC.UserManagement" web service imported into the program and the "CreateUser" web service "request" configured Steps Open program "SOAPUI" or other web service program Click and open the "CreateUser" request for the first root system code Populate the "<UserId>" field with a unique user ID to be assigned to "UserA" Populate the "<UserRoles>>" field Populate the "<UserDescription>" field Populate the "<IsAvatarMobileUser>" field Populate the "<IsUserAStaffMember>" field Populate the "<IsUserSystemAdministrator>" field Populate the "<IsUserAUnit>" field Populate the "<WarnNonCaseloadAccess>" field Click [Submit] Validate a message "[UserA] has been created with password : 7K3M" (Note: Password is a temporary password) Log into Avatar as "UserA" and the temporary password Validate the user is prompted to create a permanent password Enter a permanent password Click [Sign In] Validate the user is logged in successfully Log out as "UserA" and log in with the permanent password Validate the user is logged in successfully Document Management - Approval notification To-Dos. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Clinical Document Viewer Review To Do Item (PM) Scenario 1: User Definition - Approval Notifications Steps Open the "User Definition" form. Add a new user. Fill out all necessary fields. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set "Forms to Allow Approval Notifications" to "Specify Forms". Click [Select Forms for Approval Notifications]. Select all forms desired to utilize the approval notification functionality. Select "Yes" in the "Limit Approval Notifications to Caseload Only". Click [Submit] to file the form. Open the "User Definition" form. Navigate to the "Document Management" section. Validate "Is the User a Document Management Administrator" to set to "No". Validate "Forms to Allow Approval Notifications" is set to "Specify Forms". Click [Select Forms for Approval Notifications]. Validate the forms desired to utilize the approval notification functionality are checked. Validate "Limit Approval Notifications to Caseload Only" is set to "Yes". Click [Discard]. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "All Forms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "No Forms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is not received. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "Specify Forms". Open the "User Definition". Assign the user to the user role "SpecifyForms". Click [Select Forms for Approval Notifications]. Select specific forms. Open the "Client Document Capture" form. Scan or import a document in to one of the forms that were set up in the previous steps for this user role. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Approve the document. Scenario 2: User Role Definition - Approval Notifications Steps Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "All Forms". Open the "User Definition". Assign the user to the user role "AllForms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "No Forms". Open the "User Definition". Assign the user to the user role "NoForms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is not received. Open the "User Role Definition" form. Create a user role and set the "Form to Send Approval Notifications" to "Specify Forms". Open the "User Definition". Assign the user to the user role "SpecifyForms". Click [Select Forms for Approval Notifications]. Select specific forms. Open the "Client Document Capture" form. Scan or import a document in to one of the forms that were set up in the previous steps for this user role. Navigate to the "myToDos" widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Approve the document. Document Management - Approval notifications Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Clinical Document Viewer Review To Do Item (PM) Scenario 1: Document Management - Approval Notifications Steps Open the "User Definition" form. Navigate to the "Forms and Tables" section. Give the user access to the "Document Capture Approval" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "All Forms". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Approve" in "Approve/Reject". Click [File Approval/Rejection]. A message pops up stating "Document Approved". Click [OK]. Open "Clinical Document Viewer" form. Locate the document that was approved and validate an additional Electronic signature page is added to the output. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Reject" in "Approve/Reject". Optionally add "Comments" as to why it's rejected. File the form. Click [File Approval/Rejection]. A message pops up stating "Document Rejected". A notification ToDo is sent to the originator of the document to let them know it's been rejected. Open the "Clinical Document Viewer" form. Validate the rejected document is now voided. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "No Forms". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the myToDos' widget. Click [Additional ToDos] Validate no ToDo notification is generated. Open the "User Definition" form. Navigate to the "Forms and Tables" section. Give the user access to the "Document Capture Approval" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "Specify Forms". Set the "Limit Approval Notifications to Caseload Only" to "Yes". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Approve" in "Approve/Reject". Click [File Approval/Rejection]. A message pops up stating "Document Approved". Click [OK]. Open "Clinical Document Viewer" form. Locate the document that was approved and validate an additional Electronic signature page is added to the output. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types not selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the ToDo for the document. Validate there is no [Document Capture Approval] button on the ToDo. Validate there is a [Review To Do Item] button. Click [Review To Do Item]. Mark the ToDo as reviewed. Click [Close]. Open the "Client Document Capture" form Select a client that isn't in the user's caseload. Select an episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types not selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the "myToDos' widget. Click [Additional ToDos] Locate the ToDo for the document. Validate there is no notification generated as this client isn't in the user's caseload. Validate there is a [Review To Do Item] button. Click [Review To Do Item]. Mark the ToDo as reviewed. Click [Close]. Scenario 2: User Definition - Approval Notifications Steps Open the "User Definition" form. Add a new user. Fill out all necessary fields. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set "Forms to Allow Approval Notifications" to "Specify Forms". Click [Select Forms for Approval Notifications]. Select all forms desired to utilize the approval notification functionality. Select "Yes" in the "Limit Approval Notifications to Caseload Only". Click [Submit] to file the form. Open the "User Definition" form. Navigate to the "Document Management" section. Validate "Is the User a Document Management Administrator" to set to "No". Validate "Forms to Allow Approval Notifications" is set to "Specify Forms". Click [Select Forms for Approval Notifications]. Validate the forms desired to utilize the approval notification functionality are checked. Validate "Limit Approval Notifications to Caseload Only" is set to "Yes". Click [Discard]. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "All Forms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "No Forms". Open the "Client Document Capture" form. Scan or import a document. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is not received. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is the User a Document Management Administrator" to "No". Set the "Form to Send Approval Notifications" to "Specify Forms". Open the "User Definition". Assign the user to the user role "SpecifyForms". Click [Select Forms for Approval Notifications]. Select specific forms. Open the "Client Document Capture" form. Scan or import a document in to one of the forms that were set up in the previous steps for this user role. Navigate to the 'myToDos' widget. Validate that a "Document Capture Approval" notification is received. Click [Document Capture Approval]. Approve the document. Document Management - Document Capture Approvals Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Clinical Document Viewer Review To Do Item (PM) Client Document Capture Document Capture Scenario 1: Document Management - Approval Notifications Steps Open the "User Definition" form. Navigate to the "Forms and Tables" section. Give the user access to the "Document Capture Approval" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "All Forms". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Approve" in "Approve/Reject". Click [File Approval/Rejection]. A message pops up stating "Document Approved". Click [OK]. Open "Clinical Document Viewer" form. Locate the document that was approved and validate an additional Electronic signature page is added to the output. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Reject" in "Approve/Reject". Optionally add "Comments" as to why it's rejected. File the form. Click [File Approval/Rejection]. A message pops up stating "Document Rejected". A notification ToDo is sent to the originator of the document to let them know it's been rejected. Open the "Clinical Document Viewer" form. Validate the rejected document is now voided. Open the "User Definition" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "No Forms". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" and optionally set "Description". Click [Save]. Click "Close Document Capture". Navigate to the myToDos' widget. Click [Additional ToDos] Validate no ToDo notification is generated. Open the "User Definition" form. Navigate to the "Forms and Tables" section. Give the user access to the "Document Capture Approval" form. Navigate to the "Document Management" section. Set the "Is this user a Document Management Administrator" field to "No". Set the "Forms To Send Approval Notifications" to "Specify Forms". Set the "Limit Approval Notifications to Caseload Only" to "Yes". Click [Submit] to file the form. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the approval notification for the document. Click the [Document Capture Approval] button on the document notification. Select "Approve" in "Approve/Reject". Click [File Approval/Rejection]. A message pops up stating "Document Approved". Click [OK]. Open "Clinical Document Viewer" form. Locate the document that was approved and validate an additional Electronic signature page is added to the output. Open the "Client Document Capture" form Select a client and episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types not selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the 'myToDos' widget. Click [Additional ToDos] Locate the ToDo for the document. Validate there is no [Document Capture Approval] button on the ToDo. Validate there is a [Review To Do Item] button. Click [Review To Do Item]. Mark the ToDo as reviewed. Click [Close]. Open the "Client Document Capture" form Select a client that isn't in the user's caseload. Select an episode. Select a "Capture Mode". Either scan or import in a document, depending on the "Capture Mode". Set the "Document Type" to one of the document types not selected under "Specify Forms". Click [Save]. Click "Close Document Capture". Navigate to the "myToDos' widget. Click [Additional ToDos] Locate the ToDo for the document. Validate there is no notification generated as this client isn't in the user's caseload. Validate there is a [Review To Do Item] button. Click [Review To Do Item]. Mark the ToDo as reviewed. Click [Close]. Scenario 2: 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 Access the 'Client Document Capture' form. Enter "Client A" in the 'Client ID' field. Select any episode for the 'Episode Number' field. Click [Launch POS Capture]. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?" Click [Import]. Validate the 'Document Capture' opens in a new window. Select any value in the 'Document Type' field. Enter any value in the 'Document Description' field. Click [Capture] and [Browse]. Locate the file to be imported and click [Open] and [Done]. Validate the image displays. Click [Save]. Validate a message stating: 'Save Was Successful.' and 'Document Added to Avatar!' Close the form. Access the undocked 'Clinical Document Viewer' form. Validate the form opens in a new window. Select "Client" in the 'Select Type' field. Select 'Individual' in the 'Select All or Individual Client' field. Enter "Client A" in the 'Select Client' field. Select the episode from the previous steps in the 'Episode' field. Click [Process]. Locate and select the document that was saved in the previous steps. Validate the image displays. Click [Close All Documents], [Search] and [Close]. Document Management - Document Capture Approvals Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: User Merge User Role File Export User Role File Import Scenario 1: 'User Merge' - merge existing user into a new user Specific Setup: A CWS form must be attached to the PM menu using the 'Attach Other Application Form To Menu' form (Form A). A user role must be defined (User Role A) with the following: Access to "Form A" in the 'Select Forms' field in the 'Appointment Scheduling' section. "Approval Notifications" data must be on file for this user role. A user must be defined and associated to "User Role A" (User A). Steps Access the 'User Merge' form. Select "New" in the 'Merge Into New or Existing User' field. Enter "MergeUser" in the 'New User ID' field. Enter "Merge User" in the 'New User Description' field. Select "User A" in the 'Source User 1' field. Click [Submit]. Validate a "Form Return" message is displayed stating: User Merge has completed. Do you wish to return to form? Click [Yes]. Select the "User Merge Process" section. Select "User" in the 'All or User' field. Select "MergeUser" in the 'User Part of Merge' field. Click [Display Progress Log]. Validate the 'User Merge Progress Log' shows 100% complete. This may take a few moments. Close the form. Access the 'User Definition' form. Select "User A" in the 'Select User' field. Validate a message is displayed stating: User ID "User A" is disabled. Only User Description can be updated. Click [OK]. Select "MergeUser" in the 'Select User' field. Validate the 'User ID' field contains "MergeUser". Validate the 'User Description' field contains "Merge User". Validate "User Role A" is selected in the 'User Role(s)' field. Validate the "Approval Notifications" data was transferred to the new user. Close the form. Scenario 2: User Role File Import/Export - Approval Notificatins Specific Setup: A User Role Definition must be on file. Create one if there aren't any. This user role must have the Approval Notifications data filled out. Steps Open the "User Role File Export" form. Export one or more user roles. Sign onto a system that doesn't contain the user role(s) contained in the export file. Open the "User Role File Import" form. Import the exported user role. Open "User Role Definition" form. Validate the user role data matches the system it was exported from.	Topics • User Role Definition • Document Management • Web Services • Perceptive • User Merge • User Role File Import
Update 51 Summary \| Details Guardiant Metric processing Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Guardiant SMP Globals Guardiant Application - Analytics Scenario 1: Guardiant Metric Processing/Data - Validations Specific Setup: Have a system configured for "Guardiant" reporting Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application Steps Open form "Guardiant" Click [Test Daily Collection] Click [Yes] to the warning message Validate message "Test Succeeded" is displayed Click [Test Metrics Collection] Validate message "Test Succeeded" is displayed Click [Yes] to the warning message Validate message "Test Succeeded" is displayed Log into "Guardiant" At the "Client Search", select the desired client account number Click "Analytics" from the selection on menu on the right side From the menu tab selections at the top of the page (License, Application Usage Metrics, RADplus Metrics, Finance, or Clinical): Select the desired tab categories for viewing metrics. For example: Click the "License" tab Navigate to the "Avatar Licensing" metric graph Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Click the "Application Usage Metrics" tab at the top Navigate to the "# of forms Accessed" graph Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Navigate to the "# of Journals Created on Day" Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Click the "RADplus Metrics" tab at the top of the page Navigate to the "# of Modeled Options" graph Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Navigate to the "# of Modeled Tables" graph Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Navigate to the "# of Report Definitions" on Day" Hover over the current date and a previous date on the graph Validate the values displayed, are as expected Navigate to the "# Modeled Table Rows Entered Hover over the current date and a previous date on the graph Validate the values displayed, are as expected	Topics • Guardiant
Update 53 Summary \| Details Smartphone - future functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: System Security Defaults Scenario 1: Smartphone - validate session timeout Steps Internal Testing Only.	Topics • NX Only
Update 55 Summary \| Details Smartphone - future functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Scheduling Calendar ModeledForm Clinical Document Viewer Scenario 1: Smartphone - Validate the 'Restore/Delete Backup Data' dialog Steps Internal Testing Only. Scenario 2: Progress Notes (Group and Individual) - Validate the subsequent submit Steps Internal Testing Only.	Topics • Progress Notes (Group And Individual) • Progress Notes • NX Only • Modeling
Update 58 Summary \| Details Modeled Forms - Labels Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Consent to Treat Clinical Document Viewer Scenario 1: Modeled forms - Validate Modeled form with Document Routing Specific Setup: A user modeled form must be created that includes a label field. Using "Form Designer", change the contents of the label field. Include some html and some bold and/or italicized test. Using "Document Routing Setup", enable document routing for the user modeled form. Steps Open the user modeled form with label field changes. Validate the changes made to the label field in "Form Designer" can be seen. Populate all required fields. Finalize and submit the form. Validate the image generated includes the label changes, any bold or italicized text and that it includes all labels from the form. Validate that all fields are included in the image. Scenario 2: Form Designer - Modeled Form Specific Setup: A user modeled form must be defined and configured with event logic to hide/unhide fields (NX Test Form). A user modeled form must be defined and configured that contains a label field. Using "Form Designer", edit the label field that you added in previous step. Add html code to the label and make some of the text Bold or italicized. Enable registry setting "Include Label Fields In Data Display". Steps Access the 'Form Designer' form. Select "NX Test Form' in the 'Select' field. Select any value in the 'Sections' field. Click [Show Sections]. Validate text stating "Layout adjustments are disabled for this form." Select a field and try to move it. Validate the user is unable to change the layout of the fields. Validate the 'Subsection' field is disabled. Click [Scriptlink - Edit] Validate the 'ScriptLink' dialog displays. Click [Return to Designer]. Click [QuickLinks - Edit]. Search for and select any form in the 'QuickLink Form Search' field Click [Save]. Select any field and un-check the 'Visible' field. Collapse the 'Hidden Elements' region and validate the hidden field is present. Click [Save]. Validate a 'Confirm' dialog stating: "Form Saved." Click [OK] and [Submit]. Access the 'NX Test Form'. Validate the form selected in the previous steps displays as a QuickLink. Validate the field edited in the previous steps displays correctly. Close the form. Open the user modeled form with label field changes. Validate the changes made to the label field in "Form Designer" can be seen. Populate all required fields. Finalize and submit the form. Validate the image generated includes the label changes, any bold or italicized text and that it includes all labels from the form. Validate that all fields are included in the image.	Topics • Modeling
Update 62 Summary \| Details Avatar NX - 'All Documents Widget' Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan All Documents Widget All Documents Widget Definition View Definition CONSOLE WIDGET VIEWER widget Append Progress Notes Console Widget Viewer Practitioner Enrollment Scenario 1: 'All Documents' widget - Validate modeled form records Specific Setup: A client is enrolled in an existing episode (Client A). A modeled form must be defined with XML characters in the form name (Form 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). The 'All Documents' widget must contain a 'Multi-Form Tab' with the "Form A" form assigned. Steps Select "Client A" and access "Form A". Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Submit the form. Select "Client A" and access the 'All Documents' view. Select the 'Multi-Form Tab'. Validate the record filed in "Form A" is displayed and selected. Validate the record is displayed as expected in the 'Console Widget Viewer'. Click [Close All]. Validate the record is no longer displayed. Scenario 2: 'All Documents' widget - Validate modeled form records Specific Setup: A client is enrolled in an existing episode (Client A). A modeled form must be defined with XML characters in the form name (Form 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). The 'All Documents' widget must contain a 'Multi-Form Tab' with the "Form A" form assigned. Steps Select "Client A" and access "Form A". Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Submit the form. Select "Client A" and access the 'All Documents' view. Select the 'Multi-Form Tab'. Validate the record filed in "Form A" is displayed and selected. Validate the record is displayed as expected in the 'Console Widget Viewer'. Click [Close All]. Validate the record is no longer displayed.	Topics • Modeling • All Documents Widget
Update 63 Summary \| Details Treatment Plan - 'Practitioner' validations Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan Scenario 1: Treatment Plan - Staff member "Look-up" field results validation Specific Setup: In form "Treatment Plan", have a client [TestClient] with an existing treatment plan created. Note the current "Plan Date" set on the plan. [TestDate]. Have or create a staff member [StaffA] in form "Practitioner Enrollment" that has a "Start Date" submitted that set to a date later than [TestDate]. Have or create a staff member [StaffB] in form "Practitioner Enrollment", that has a "Start Date" submitted that is set to a date prior to [TestDate]. Have registry setting "'Practitioner Not Enrolled Warning" set to "W". Have access to form "Registry Settings". Steps Select [TestClient] and open the "Treatment Plan" form. In the pre-display, select the existing row for edit. Click [Launch Plan]. Click [Add New Problem]. Populate any required fields. Navigate to either the "Staff Assigning" field or "Staff Responsible" search field. Enter [StaffA] and click search. Validate the practitioner is found and the entry is accepted. Clear the search field. Enter [StaffB] and click search. Validate a "Warning" dialog is displayed stating "Warning! Clinician [TestClient] is Not Active for Treatment Plan Date". Click [OK]. Validate the entry for [StaffB] remains in the "Staff Responsible" field as expected, since this was only a warning message. Click [Add New Goal]. Repeat step 1d. Validate results are as expected. Click [Add New Objective]. Repeat step 1d. Validate results are as expected. Click [Add New Intervention]. Repeat step 1d. Validate results are as expected. Submit the form. Validate submission is successful. Open form "Registry Settings". Search for setting "'Practitioner Not Enrolled Warning". Set to registry setting value to "E". Submit the form. Select [TestClient] and reopen the "Treatment Plan" form. In the pre-display, select the existing row for edit again. Click [Launch Plan]. Click [Add New Problem] to add another problem. Populate any required fields. Navigate to either the "Staff Assigning" field or "Staff Responsible" search field. Enter [StaffA] and click search. Validate the practitioner is found and the entry is accepted. Clear the search field. Enter [StaffB] and click search. Validate this time an "Error" dialog is displayed stating, "Warning! Clinician [TestClient] is Not Active for Treatment Plan Date". Click [OK]. Validate the entry for [StaffB] has been cleared from the field and replaced with the previous valid entry of [StaffA], as expected since this was an "Error" message. Click [Add New Goal] to add another goal. Repeat step 3d. Validate results are as expected. Click [Add New Objective] to add another objective. Repeat step 3d. Validate results are as expected. Click [Add New Intervention] to add another intervention. Repeat step 3d. Validate results are as expected. Submit the form. Validate submission is successful.	Topics • Registry Settings • Treatment Plan • Practitioner
Update 64 Summary \| Details Quick Links - Form Bundles Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Update Client Data Diagnosis Append Progress Notes Next Of Kin Scenario 1: QuickLinks to a Simultaneous Bundle Specific Setup: A client is enrolled in an existing episode (Client A). A form bundle with multiple forms must be defined in the 'Form Bundler' form (Bundle A). "Bundle A" must be added to the 'Progress Notes (Group and Individual)' form as a quick link. This can be done in 'Form Designer'. Steps Access the 'Progress Notes (Group and Individual)' form. Select "Client A" in the 'Select Client' field. Click on the quick link for "Bundle A". Validate the forms in "Bundle A" are launched as expected. Close all forms. Form Designer - Import Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Form Designer (CWS) Dynamic Form - Document Management Form Re-Mapping - Selection Envelope Export (PM) Scenario 1: Form Designer - Export/Import Layout Changes Specific Setup: Have a robust form containing several sections and several fields on each section (Form A). Edit any section (Section A) of "Form A" and make any type of form designer change in the section. For this example, a field is moved to different location (Field A). Steps Access "Form A". Navigate to "Section A". Validate the form designer change made in the setup is present and "Field A" is in a new location. Access the 'Form Designer' form. Select "Form A" from the 'Forms' field. Click [Export Form Designer Copy]. Validate a 'Confirm' dialog stating "Export Complete." and click [OK] (Note: Export files are saved in the "Downloads" folder) Close the form. Access the 'Form Designer' form. Select "Form A" from the 'Forms' field. Select "Section A" in the "Sections" field. Click [Show Section]. Revert the form designer change confirmed in step 1b so "Field A" is returned to its original location. Click [Save], [OK] and [Submit]. Access "Form A". Navigate to "Section A". Validate the form designer change made in step 3d is present. Close the form. Access the 'Form Designer' form. Select "Form A" from the 'Forms' field. Click [Import Form Designer Copy] Navigate to the location of the export file. Select the file. Click [Show Section]. Validate the screen opens and displays as expected. Click [Cancel] and [Yes]. Click [Submit]. Access "Form A". Navigate to "Section A". Validate the form designer change imported is present and "Field A" is in a new location. Close the form.	Topics • Form Bundles • Form Designer
Update 65 Summary \| Details FTP Setup Form - password limit changed from 20 characters to 40 characters Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: FTP Setup Scenario 1: Validate FTP Setup Form has password limit changed from 20 characters to 40 characters Specific Setup: An FTPS connection must exist in the 'FTP Setup' form. (FTPS) Steps Access the 'FTP Setup' form. Select "Edit" from the 'Add/Edit' field. Select the server associated with the environment where this is tested in the 'Cache Server Name' field. Select “FTPS” in the ‘Select FTP Setup' field. Validate "Yes" is selected in the 'Active' field. Set the 'Server Password' field to 45 characters and validate it is truncated to 40 characters. Click [File].	Topics • FTP Setup
Update 67 Summary \| Details User Role Definition - 'SYSTEM.RADplus_audit_user_roles' SQL table Scenario 1: Validate adding a user in form 'User Definition' Specific Setup: A form must be defined in 'Document Management Definition' with an apostrophe (Form A). Steps Access the 'User Definition' form. Enter the desired value in the 'User ID' field. Enter the desired value in the 'User Description' field. Populate all required and desired fields. Navigate to 'Document Management' tab. Select "No" in the 'Is this user a Document Management Administrator' item. Select "Specify forms" in the 'Forms Allowed to Print' field. Click [Select Forms to Print]. Select "Form A" in the 'Select Forms' field. Click [OK]. Click [Select Forms to Print]. Validate "Form A" is still selected. Click [OK]. Submit the form. Access the 'User Definition' form. Select the user created in the previous steps. Navigate to 'Document Management' tab. Click [Select Forms to Print]. Validate "Form A" is still selected. Click [OK] and close the form. Scenario 2: User Role Definition - Add/Editing Roles Steps Access the 'User Role Definition' form. Create a new user role. Populate all required and desired fields. Click [Submit] and close the form. Access Crystal Reports or other SQL Reporting tool. Create a report using the 'SYSTEM.RADplus_audit_user_roles' SQL table. Validate a row is displayed for the user role created in the previous steps. Close the report.	Topics • User Definition • User Role Definition • Query/Reporting
Update 68 Summary \| Details Form and Table Documentation - 'Generate Form To Map' Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Form and Table Documentation (PM) Scenario 1: "Form and Table Documentation" form (Modeled Forms) - Validate "Generate Form Map' report results Specific Setup: Have a "Modeled" form that contains a table column of Single response dictionary type and event logic defined on the form [FormA]. Event logic must be defined as: 'Type of Event' set to "Input Validation" and 'Compare With for Event' set to "Specific Value". Have a "Modeled" form that does 'not' contain event logic defined on the form [FormB]. Make a note or all the fields on the form. Have access to form "Form and Table Documentation". Steps Open 'Form and Table Documentation'. Set 'Type of Documentation' to 'Form'. Select "Individual" in the "Individual or All Forms" field. Select [FormA] from the 'Form to be Documented' field. (Modeled form with event logic defined) Navigate to the "Generate Form Map" button. Validate form is generated without any error. Validate the user is presented with a file explorer dialog [Note: In Avatar NX the file will automatically be created and saved in the windows "Downloads" directory on the server]. Validate the (.htm) type file name field is populated in the file name field. Validate the file name includes the associated internal "FormID' for [FormA], followed by its form "Name". For example: "NetsmartFormMap_USER9_Modeled Form with Event logic". Select a folder location to save the file and click [Save]. Navigate to the location of the (.htm) file. Click to open the file. Validate the title of the report reflects the name of [FormA] and its associated internal "FormID". Validate each "Section" name is displayed on the form as expected with each field contained in that section listed beneath it. Validate the field names contain both the name and its associated field number in brackets, for example "Date of Entry (777.77)". Locate a field on the form that contains event logic defined. Validate the event logic noted in the setup is displayed as expected. For example: Date of Entry(777.77) Type of Event: Input Validation Compare with For Event: Specific Value Specific Value : Dictionary Value configured Relationship To Comparison Value to Trigger Event: Equal To Type of Validation Message: Message with [OK] and [Cancel] Buttons Validation Message: Test Validation Message Close the page Select [FormB] from the 'Form to be Documented' field. (Modeled form with 'no' event logic defined) Repeat steps 1a through 1e. Validate results are as expected. Close the form.	Topics • Modeling • Forms
Update 69 Summary \| Details Smartphone Layout - future functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Individual Progress Note Client Lookup/Header Configuration Manager Scenario 1: Smartphone - Client header validations Steps Internal Testing Only.	Topics • NX Only
Update 70 Summary \| Details Console Widget Viewer - 'Treatment Plan' records Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan All Documents Widget All Documents Widget Definition View Definition CONSOLE WIDGET VIEWER widget Append Progress Notes Console Widget Viewer Practitioner Enrollment Pre Admit Scenario 1: 'All Documents' widget - Validate 'Treatment Plan' 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). A 'Mutli-Select Dictionary' field is added to the 'Goals' section the 'Treatment Plan' form. This can be done via 'Site Specific Section Modeling'. Steps Select "Client A" and access the 'Treatment Plan' form. Enter the desired date in the 'Plan Date' field. Select the desired value in the 'Plan Type' field. Populate any required and desired fields. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Add any problem. Populate all desired fields. Add New Goal. Populate all desired fields. Select the desired values in the 'Multi-Select dictionary' field. Click [Return To Plan]. Validate a 'Plan Save' dialog stating: "Plan saved successfully." Click [OK]. Submit the form. Navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Verify the record is present and displays "Draft" in the 'Workflow Status' field and select it. Validate the 'Console Widget Viewer' displays the plan in the previous steps. Click [Open Record]. Validate the 'Treatment Plan' form opens with the draft from the previous steps. Make and desired changes. Select "Final" in the 'Treatment Plan Status' field. Click [Submit] Validate a 'Confirm Document' dialog containing the treatment plan. Click [Sign]. Enter the password associated with the logged in user and click [Verify]. Navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Verify the record is present and displays "Final" in the 'Workflow Status' field and select it. Validate the 'Console Widget Viewer' displays the finalized plan from the previous steps. Validate the treatment plan data displays as expected. Validate the value(s) selected in the 'Multi-Select Dictionary' field are not duplicated. Click [Close All]. Scenario 2: 'All Documents' widget - Validate 'Progress Notes' records Specific Setup: Please note: this is for Avatar NX only. A client must be enrolled in an existing episode (Client A). "Client A" must have more than one hundred records on file for 'Progress Notes (Group and Individual)'. "Client A" must have one or more 'Ambulatory Progress Notes' records on file. 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). The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form. The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Ambulatory Progress Notes' form assigned. A copy of the 'Progress Notes (Group and Individual)' form must be defined and named with XML characters, such as '<Progress Notes (Group and Individual)>'. Steps Select "Client A" and navigate to the 'All Documents' view. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'. Validate all 'Progress Notes (Group and Individual)' records are displayed for the client (more than one hundred). Validate the 'Workflow Status' column contains either "Draft" or "Final" for each row. In the 'All Documents' widget, select the 'Multi-Form Tab'. Validate all 'Ambulatory Progress Notes' records are displayed for the client. Validate the 'Time' field contains the proper time the note(s) were filed. Scenario 3: 'All Documents' widget - Validate modeled form records Specific Setup: A client is enrolled in an existing episode (Client A). A modeled form must be defined with XML characters in the form name (Form 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). The 'All Documents' widget must contain a 'Multi-Form Tab' with the "Form A" form assigned. Steps Select "Client A" and access "Form A". Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Submit the form. Select "Client A" and access the 'All Documents' view. Select the 'Multi-Form Tab'. Validate the record filed in "Form A" is displayed and selected. Validate the record is displayed as expected in the 'Console Widget Viewer'. Click [Close All]. Validate the record is no longer displayed. Scenario 4: 'All Documents' widget - Validate 'Treatment Plan' 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). The logged in user must have an associated staff member. Steps Select "Client A" and access the 'Treatment Plan' form. Enter the desired date in the 'Plan Date' field. Select the desired value in the 'Plan Type' field. Populate any required and desired fields. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Add any problem. Populate all desired fields. Click [Return To Plan]. Validate a 'Plan Save' dialog stating: "Plan saved successfully." Click [OK]. Submit the form. Select "Client A" and navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Verify the record is present and displays "Draft" in the 'Workflow Status' field and select it. Validate the 'Console Widget Viewer' displays the plan in the previous steps. Click [Open Record]. Validate the 'Treatment Plan' form opens with the draft from the previous steps. Make and desired changes. Select "Final" in the 'Treatment Plan Status' field. Click [Submit]. Validate a 'Confirm Document' dialog is displayed with the treatment plan data. Click [Accept and Route]. Enter the password associated to the logged in user and click [Verify]. Select the practitioner associated to the logged in user as an approver and click [Submit]. Refresh the 'All Documents' widget. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Verify the record is present and displays "Final" in the 'Workflow Status' field and select it. Validate the treatment plan is displayed in the 'Console Widget Viewer'. Validate the [Append] button is not displayed since the document has not yet been approved. Click [Close All]. Navigate to 'My To Do's' widget. Validate a To Do is displayed for "Client A". Approve the To Do. Validate the To Do is no longer displayed for "Client A". Select "Client A" and navigate to the 'All Documents' view. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Select the finalized treatment plan. Validate the treatment plan is displayed in the 'Console Widget Viewer'. Validate the [Append] button is now displayed. Click [Append]. Validate the 'Append Documents' form is displayed. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate a 'Confirm Document' dialog is displayed. Click [Accept]. Enter the password for the logged in user and click [Verify]. Click [No] to close the form. Refresh the 'All Documents' view. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Select the finalized treatment plan. Validate the treatment plan is displayed in the 'Console Widget Viewer' with the comments appended to the end. Click [Close All].	Topics • All Documents Widget • Progress Notes • Modeling • Treatment Plan
Update 72 Summary \| Details Form Definition - SQL Query Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Table Definition (PM) Dictionary Update (PM) Scenario 1: Modeling - Form Definition - Validate forms containing an SQL query Specific Setup: A modeled form (Form A) is defined with an SQL query field (Field A). A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access "Form A". Populate all required and desired fields. Validate "Field A" is displayed and contains the proper results based on the SQL query. Select the desired value in "Field A". Submit the form. Select "Client A" and access "Form A". Select the record filed in the previous steps and click [Edit]. Validate all previously filed data is displayed. Close the form. Modeled Forms - Signature fields Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Table Definition (PM) Dictionary Update (PM) Scenario 1: Modeled Form - Validate signature fields Specific Setup: Signatures must be enabled in 'System Security Defaults'. A modeled form (Form A) is defined with the following: A binary table (Table A) for storage A signature field Supports Automatic Backup set to "Yes" Two clients are enrolled in existing episodes (Client A & Client B). Steps Select "Client A" and access "Form A". Populate all required and desired fields. Sign in the 'Signature' field. Submit the form. Select "Client B" and access "Form A". Populate all required and desired fields. Sign in the 'Signature' field. Click [Backup] and close the form. Select "Client B" and access "Form A". Click [Yes] to restore from backup. Validate the previously filed data is displayed. Click [Submit]. Access Crystal Reports or other SQL Reporting tool. Create a report using "Table A". Validate the rows for "Client A" and "Client B" are displayed. Validate both rows contain data in the 'sign_capture_date' and 'sign_capture_time' fields. Close the report.	Topics • Forms • Modeling • Signatures
Update 74 Summary \| Details SQL Table access Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Print Error Log (PM) Scenario 1: Validate a users SQL query (ODBC) table permissions when querying tables via a "Database" and/or "ECP" server Specific Setup: Have a standard cache "Database" server for testing and if applicable an "ECP" server configured with the database server as its remote database, so that reports can be run via the "ECP" server to display data in the database server In form "User Definition" create a new user [SqlUser] In field "Select Tables for Product SQL Access" assign the user access to tables in two or more applications. For this test: [TableA] and [TableB] are assigned in application "PM" [TableC] and [TableD] are assigned in application "CWS" Populate all other required fields and submit the form Create a second user in form "User Definition" with no SQL table access assigned [NoSqlAccess] Populate all other required fields and submit the form Using the windows "ODBC Data Source Administrator" setup the following connections for [SqlUser] [ConnectionA] configured to point to application "PM" on the "Database" server [ConnectionB] configured to point to application "CWS" on the "Database" server [ConnectionC] configured to point to application "PM on the "ECP" server [ConnectionD] configured to point to application "CWS" on the "ECP" server Test and validate each connection is successful Have access to form "Registry "Settings" Steps Open the desired reporting software, for example "Crystal Reports" Select the "ODBC" [ConnectionA], set to connect to the "PM" application on the "Database" server Validate [TableA] and [TableB] are accessible, as expected Close that connection Select database "ODBC" connection [ConnectionB], set to connect to the "CWS" application on the "Database" server Validate [TableC] and [TableD] are accessible, as expected Close that connection Repeat step 1a for "ECP" connection [ConnectionC] Validate results are the same, as expected Repeat step 1b for the "ECP" [ConnectionD] Validate results are the same, as expected Open the "ODBC Data Source Administrator" application Populate the "Host(IPAddress)", "Port" fields with the proper credentials for the "Database" server and set the "Cache Namespace" field to the "PM" In the "User Name" field, populate the 'UserID' for the user [NoSqlAccess] Populate the password for user [NoSqlAccess] in the "Password" field Click to [Test Connection] Validate the message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Repeat step 2a for the "Database" server, but change "Cache Namespace" field to the "CWS" Click to [Test Connection] Validate the results are the same Populate the "Host(IPAddress)", "Port" fields with the proper credentials for the "ECP" server and set the "Cache Namespace" field to the "PM" Leave the user name and password field set to [NoSQLAccess] Click to [Test Connection] Validate message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Repeat step 2c, but change "Cache Namespace" field to the "CWS" Click to [Test Connection] Validate message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Log into Avatar on the "Database" server Open form 'User Definition' Select [SqlUser] and navigate to field "Select Tables for Product SQL Access" Revoke access to [TableA] in the "PM" application and [TableC] in the "CWS" application Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate [TableA] is not accessible and [TableB] is accessible Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate [TableC] is not accessible and [TableD] is accessible Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate [TableA] is not accessible and [TableB] is accessible Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate [TableC] is not accessible and [TableD] is accessible Open form 'User Definition' Select [SqlUser] and navigate to field "Select Tables for Product SQL Access" Revoke all table access in one of the applications, for this example "CWS" is used Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate [TableA] and [TableB] are accessible Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate the connection fails as expected, as the user does not have any access to tables in that application Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate [TableA] and [TableB] are accessible Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate the connection fails as expected, as user does not have any access to tables in that application Open form "Registry Settings" Select registry setting "Avatar Report Multiple System Codes" Set the registry setting value to "Y" Submit the form Open form "User Definition", and select user [NoSqlAccess] Set prompt "Allow Product SQL Access" to "Yes" Click "Select Tables for Product SQL Access" and Assign the user access to [TableA] in "PM" and [TableC] in "CWS" Click [Save] Set prompt "Allow Product SQL Access to Additional Datasets" to "Yes" In the "Product SQL Access Datasets" field Select root system codes, [RootA] and [RootB] Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate data rows for [TableA] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate data rows for [TableC] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate data rows for [TableA] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate data rows for [TableC] are displayed for the [RootA] system code and the [RootB] system code, as expected Scenario 2: Validate a users (ODBC) SQL table permissions when querying tables via a "Database" and/or "ECP" server Specific Setup: Have a standard cache "Database" server for testing and if applicable an "ECP" server configured with the database server as its remote database, so that reports can be run via the "ECP" server to display data in the database server In form "User Definition" create a new user [SqlUser] In field "Select Tables for Product SQL Access" assign the user access to tables in two or more applications. For this test: [TableA] and [TableB] are assigned in application "PM" [TableC] and [TableD] are assigned in application "CWS" Populate all other required fields and submit the form Create a second user in form "User Definition" with no SQL table access assigned [NoSqlAccess] Populate all other required fields and submit the form Using the windows "ODBC Data Source Administrator" setup the following connections for [SqlUser] [ConnectionA] configured to point to application "PM" on the "Database" server [ConnectionB] configured to point to application "CWS" on the "Database" server [ConnectionC] configured to point to application "PM on the "ECP" server [ConnectionD] configured to point to application "CWS" on the "ECP" server Test and validate each connection is successful Have access to form "Registry "Settings" Steps Open the desired reporting software, for example "Crystal Reports" Select the "ODBC" [ConnectionA], set to connect to the "PM" application on the "Database" server Validate [TableA] and [TableB] are accessible, as expected Close that connection Select database "ODBC" connection [ConnectionB], set to connect to the "CWS" application on the "Database" server Validate [TableC] and [TableD] are accessible, as expected Close that connection Repeat step 1a for "ECP" connection [ConnectionC] Validate results are the same, as expected Repeat step 1b for the "ECP" [ConnectionD] Validate results are the same, as expected Open the "ODBC Data Source Administrator" application Populate the "Host(IPAddress)", "Port" fields with the proper credentials for the "Database" server and set the "Cache Namespace" field to the "PM" In the "User Name" field, populate the 'UserID' for the user [NoSqlAccess] Populate the password for user [NoSqlAccess] in the "Password" field Click to [Test Connection] Validate the message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Repeat step 2a for the "Database" server, but change "Cache Namespace" field to the "CWS" Click to [Test Connection] Validate the results are the same Populate the "Host(IPAddress)", "Port" fields with the proper credentials for the "ECP" server and set the "Cache Namespace" field to the "PM" Leave the user name and password field set to [NoSQLAccess] Click to [Test Connection] Validate message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Repeat step 2c, but change "Cache Namespace" field to the "CWS" Click to [Test Connection] Validate message states "Connectivity Test Failed" as expected, as the user has no SQL tables assigned to them Log into Avatar on the "Database" server Open form 'User Definition' Select [SqlUser] and navigate to field "Select Tables for Product SQL Access" Revoke access to [TableA] in the "PM" application and [TableC] in the "CWS" application Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate [TableA] is not accessible and [TableB] is accessible Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate [TableC] is not accessible and [TableD] is accessible Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate [TableA] is not accessible and [TableB] is accessible Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate [TableC] is not accessible and [TableD] is accessible Open form 'User Definition' Select [SqlUser] and navigate to field "Select Tables for Product SQL Access" Revoke all table access in one of the applications, for this example "CWS" is used Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate [TableA] and [TableB] are accessible Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate the connection fails as expected, as the user does not have any access to tables in that application Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate [TableA] and [TableB] are accessible Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate the connection fails as expected, as user does not have any access to tables in that application Open form "Registry Settings" Select registry setting "Avatar Report Multiple System Codes" Set the registry setting value to "Y" Submit the form Open form "User Definition", and select user [NoSqlAccess] Set prompt "Allow Product SQL Access" to "Yes" Click "Select Tables for Product SQL Access" and Assign the user access to [TableA] in "PM" and [TableC] in "CWS" Click [Save] Set prompt "Allow Product SQL Access to Additional Datasets" to "Yes" In the "Product SQL Access Datasets" field Select root system codes, [RootA] and [RootB] Submit the form Open the desired reporting software Click to make a connection to application "PM" the "Database" server via [ConnectionA] Validate data rows for [TableA] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "CWS" on the "Database" server via [ConnectionB] Validate data rows for [TableC] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "PM" on "ECP" server via [ConnectionC], Validate data rows for [TableA] are displayed for the [RootA] system code and the [RootB] system code, as expected Click to make a connection to application "CWS" on "ECP" server via [ConnectionD], Validate data rows for [TableC] are displayed for the [RootA] system code and the [RootB] system code, as expected Open the "Print Error Log" report Run the report Validate results show there are no errors reported	Topics • SQL Data Access
Update 75 Summary \| Details Registry Settings Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Service Codes Service Documentation Notes Client Ledger Scenario 1: Validating the error message Registry Setting -'Unit Calculation with Minimum Duration' in 'Service Documentation' Form Specific Setup: Registry Settings: Set the value 'Unit Calculation with minimum duration' = "Y". Client: Identify an existing client or create a new client. Note the client’s admission date. Verify existing or add a Financial Eligibility record. Service Code: ‘An existing service code is identified that has a value defined for the 'Minimum Duration for Unit Calculation' field (Service Code 1). Note the value. Progress Note entry and Service Documentation entry need to be updated to compare service duration entered in Notes against the Service Code’s configuration for “Minimum Duration for Unit Calculation”. A modeled form containing Progress Note fields (Service Documentation) must be imported through 'Envelope Import' and the logged in user must have access to it. Steps Open "Service Documentation Notes Form". Enter the 'Client ID' in 'Search Client'. Enter any value in 'Date of Service'. Enter 'Service Code 1' created in setup in 'Service Code'. Enter a value in 'Service Duration' greater than value of 'Minimum Duration for Unit Calculation' in 'Service Codes' form. Click [Final] in 'Draft/Final'. Validate the dialog displays: 'Final Prevents Future Edits'. Click [OK]. Click [Submit]. Validate Form Return Dialog Click [No]. Open "Client Ledger" form. Enter the 'Client ID'. Click [All Episodes] in 'Claim/Episode/All Episodes'. Click [Simple] in 'Ledger Type'. Click [Yes] in 'Include Zero Charges'. Click [Process]. Validate that the services created in "Service Documentation notes" has been assigned to appropriate guarantor. Click [X]. Click [Yes]. Click [Discard]. Repeat Steps 1-21, with a value in 'Service Duration' less than the 'Minimum Duration for Unit Calculation' set in the "Service Codes" form. Open the "Registry Settings" form. Change the value of the ‘Unit Calculation with Minimum Duration‘ setting to ‘YW’. Validate the message displays: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes. Click [OK]. Click [Submit]. Open the "Registry Settings" form. Set 'Limit Registry Settings to the Following Search Criteria' to ‘Unit Calculation with Minimum Duration‘. Set 'Registry Setting Value' to ‘YW’. Repeat steps 1-6. Validate the message displays: The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes. Click [OK]. Enter a value in 'Service Duration' greater than value of 'Maximum Duration' in 'Service Codes' form. Validate the message displays: 'Maximum duration per service is exceeded [Service Code 1]. The duration should not exceed X minutes'. Click [OK]. Enter a value in 'Service Duration' greater than 'Minimum Duration for Unit Calculation' but less than 'Maximum Duration'. Click [Final] in 'draft\final'. Validate the dialog displays: 'Final Prevents Future Edits'. Click [OK]. Click [Submit]. Validate Form Return Dialog Click [No]. Repeat steps 12-21,to validate 'Client Ledger' report data. Open the "Registry Settings" form. Set 'Limit Registry Settings to the Following Search Criteria' to ‘Unit Calculation with Minimum Duration‘. Set 'Registry Setting Value' to ‘YE’. Repeat Step 31 - 44, to validate the message: 'The service [Service Code 1] does not meet the minimum duration requirements for unit calculation and cannot be filed. A unit will only be calculated once the duration is at least X minutes'. Repeat steps 12-21, to validate 'Client Ledger' report data.	Topics • Registry Settings
Update 76 Summary \| Details Configure Database Size - 'New Database Size (MB)' field Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Configure Database Size Scenario 1: Configure Database Size Steps Access the 'Configure Database Size' form. Validate the 'Current Database Size (MB)' field contains the previously configured value. Enter any 7-digit number in 'New Database Size (MB)' field. Validate the 'New Database Size (MB)' field accept 7 digit number. Click [Submit]. Access the 'Configure Database Size' form. Validate the data filed in the previous steps is displayed as expected. Close the form.	Topics • RADplus Utilities
Update 79 Summary \| Details Site Specific Section Modeling - 'Exclude from DCI' field Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Site Specific Section Modeling Import/Export (CWS) Scenario 1: Site Specific Section Modeling - Progress Note Forms Steps Access the 'Site Specific Section Modeling' CWS form. Select any 'Progress Notes (Group and Individual)' form in the 'Site Specific Section' field. Click [OK]. Select the "Prompt Definition" section. Select "Session Start Time" from the 'Prompt Definition' grid. Click [Edit Selected Item]. Validate the 'Exclude from Data Collection Instrument' field is disabled and "Controlled by product" is selected. Click [Add New Item]. Select the desired site specific field to add. Validate the 'Exclude from Data Collection Instrument' field contains the following values: Yes No Controlled by product Validate "No" is selected by default in the 'Exclude from Data Collection Instrument' field. Select "Controlled by product" in the 'Exclude from Data Collection Instrument' field. Validate a message is displayed stating: Cannot select "Controlled by product". Click [OK]. Validate "No" is selected in the 'Exclude from Data Collection Instrument' field. Submit the form. Scenario 2: Site Specific Section Modeling Import/Export - Validate Progress Notes import Steps Access the 'Registry Settings' form. Enter "Multiple Start and End Times to Document" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select the 'Multiple Start and End Times to Document Sessions' registry setting for the 'Progress Notes (Group and Individual)' form and click [OK]. Enter "N" in the 'Registry Setting Value' field. Submit the form. Access the 'Site Specific Modeling Import/Export' Form. Choose the "Progress Notes (Group and Individual)" from 'Select Form to Export' Field. Click [Begin Export]. Save the export file to the desired location. Access the 'Registry Settings' form. Enter "Multiple Start and End Times to Document" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select the 'Multiple Start and End Times to Document Sessions' registry setting for the 'Progress Notes (Group and Individual)' form and click [OK]. Enter "Y" in the 'Registry Setting Value' field. Submit the form. Access the 'Site Specific Modeling Import/Export' Form. Click on [Select Import File]. Navigate to the location of the export file from the previous steps and select it. Click [Begin Import Scan]. Validate the 'Import File Scan Results' field contains: No errors or warnings found. Click [Process Import File]. Validate a message is displayed stating: Import Complete. Click [OK] and close the form. Access the 'Progress Notes (Group and Individual)' form. Validate the form is displayed as expected. Close the form.	Topics • Site Specific Section Modeling • Registry Settings • Progress Notes
Update 80 Summary \| Details "Greenspace" Integration - "NX View Definition" Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: View Definition User Merge Scenario 1: Greenspace (Third Party Application) Integration - 'NX View Definition' setup and validations Specific Setup: Have an active user [UserA], that is not assigned to a user role Have an active user [UserB], that is assigned to any user role [TestRole] Steps Open form "NX View Definition" Validate field "Third Party Application" is present on the form Select "User" in the "User or Role" field Select [UserA] in the "Select User" field In the "Third Party Application" field, select "Greenspace" option Click [File] Re-select [UserA] in the "Select User" field Validate all fields are populated as expected Close the form Re-open form "NX View Definition" Select "Role" in the "User or Role" From the "Select User Role" field, select [TestRole] In the "Third Party Application" field select the "Greenspace" option Click [File] Re-select [TestRole] in the "Select User Role" field Validate all fields are populated as expected Close the form Return to the "NX View Definition" Navigate to the "Third Party Integrations" section. In the "Configuration to Edit", select the current testing server In the "Third-Party Application" field, select "Greenspace" Validate the "Active" field has defaulted to "No" Select "Yes" in the field In the "Application URL" field, enter the following URL to connect to the "Greenspace" login page: "https://app.staging.grnspace.ca/acco...results/search" Click [File] Close the form Return "NX View Definition" Navigate to the elect the "Third Party Integrations "section. In the "Configuration to Edit", select the current testing server Validate "Greenspace" is selected in the "Third-Party Application" field Validate "Yes" is selected in the "Active" field Validate "https://app.staging.grnspace.ca/acco...results/search" is selected in the "Application URL" field Close the form Close the form Scenario 2: Greenspace (Third Party Application) URL Launch/Login - "Widget" and "Control Panel" setup and validations Specific Setup: In form "NX View Definition": [UserA] (Not assigned to a user role) has been configured with "Greenspace" selected in field "Third Party Application" and the "Third Party Integrations" section" configured and set to "Active" [UserB] is assigned to a role [TestRole] [TestRole] has been configured with "Greenspace" selected in field "Third Party Application" and the "Third Party Integrations" section" configured and set to "Active" Both users have credentials to login into the "Greenspace" website when the URL is launched Have access to forms "View Definition" and "NX View Definition" Steps Open form "View Definition" Click "Select View" Select "Add New" and click [OK] to create a new view Populate the "View ID" and "View Description" with the desired values to indicate that this will be a view that will contain the "Greeenspace" widget. For example "Greenspace_Widget_View" Populate the other required fields Click [Launch View Designer] From the " Available Widgets" list, select the "Third Party Integrations - Greenspace" widget Drag the widget to the view layout section Click [Submit] Click [Submit] to file the new view Validate submission is successful Open form "NX View Definition" Select user [UserA] for edit Validate "Greenspace" is selected in the "Third-Party Application" field Click [Associated myDay Views] From the "Select Additional Views" list, select new view "Greenspace" view Click [OK] Click [File] Validate the form submits successfully Close the form Re-open form "NX View Definition" Select "Role" in the "User or Role" From the "Select User Role" field, select [TestRole] From the "Select Additional Views" list, select new view "Greenspace" view Click [OK] Click [File] Validate the form submits successfully Log in as the [UserA] From the "Console Views" menu bar, select new "Greenspace" view Validate the "Greenspace" widget is displayed Validate a message is displayed in the widget "Resource cannot be viewed in the widget, click here to open in New tab" Search for or select any client [TestClient] in the search field on the left side panel Click on the "Resource cannot be viewed in the widget, click here to open in New tab" message Validate a new tab is opened, navigating the user to the "Greenspace" login page, as expected Enter the proper username and password credentials assigned to [UserA], in the "Email Address" and "Password" fields. Click [Sign In] Validate the user is logged in successfully and the "Assessment Results" page is displayed Validate the page indicates [TestClient] has been selected At the top right of the page, click to log out Close the tab Navigate back to the Home View In the "Control Panel" section, validate a "Greenspace" green square icon with the letter "G" is present for selection Search for or select any client [TestClient] in the search field on the left side panel Click the "Greenspace" icon in the "Control Panel" Validate a new window is opened, navigating the user to the "Greenspace" login page, as expected Enter the proper username and password credentials assigned to [UserA], in the "Email Address" and "Password" fields. Click [Sign In] Validate the user is logged in successfully and the "Assessment Results" page is displayed for [UserA] Validate the page indicates [TestClient] has been selected At the top right of the page, click to log out Close the tab Repeat steps 4 and 5, logging in as [UserB] who is assigned to [TestRole] Validate all results are successful, as expected Return to "NX View Definition" Navigate to the "Third Party Integrations" section. In the "Configuration to Edit", select the current testing server Set the value in the "Active" field to "No" Click [File] to submit the changes Close the form As [UserA], navigate back to the Home View In the "Control Panel" section, validate a "Greenspace" green square icon is no longer present, as expected From the "Console Views" menu bar, select new "Greenspace" view Validate the "Greenspace" widget is displayed Validate a message is displayed in the widget "Resource cannot be viewed in the widget, click here to open in New tab" Click on the message Validate a new tab is opened but a page is displayed with the message "Page not found", as expected. Repeat step 8, logged in as [UserB] Validate all results are as expected	Topics • NX View Definition • User Definition
2023 Update 119 Summary \| Details Client Delete Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Change MR# Delete Last Movement Client Ledger Scenario 1: "Client Delete" Form - Submission and data validations Specific Setup: Have a modeled table [TableA], that exists in [FormA] which is based on the "GA ASO" entity database Have a modeled table [TableB], that exists in [FormB] which is based on any other entity database, for example the "Client" entity database [TestClient] has a row of data submitted in both [FormA] and [FormB] [TestClient] also has a row of data submitted in a product form based table.[TableC] For this test, the "Inpatient Progress Notes" form table, "SYSTEM.cw_patient_notes" is used Have a report created [ReportA] to display data in [TableA] Have a report created [ReportB] to display data in [TableB] Have a report created [ReportC] to display data in desired product form based table [TableC] Logged in user has access to form "Client Delete" and "Delete Last Movement" Steps Run the report for [ReportA] Validate the row of data submitted for [TestClient] in [TableA], is displayed as expected Run the report for [ReportB] Validate the row of data submitted for [TestClient] in [TableB], is displayed as expected Run the report for [ReportC] Validate the row of data submitted for [TestClient] in [TableC], is displayed as expected Open "Client Delete" form. Select [TestClient] in the "Client ID" field. Validate an error message is received "Client Must Be Removed From All Families Before Client Can Be Deleted." Click [OK]. Close the form. Open form "Delete Last Movement". Select [TestClient] Select the admission episode from the "Episode Number" field. Click [Submit]. Click [Yes] to continue. Validate the form submits successfully. Open "Client Delete" form. Select[TestClient] in the "Client ID" field. Click [Submit]. Validate the form submits successfully. At the Home View, search for [TestClient] Validate there are no results, as expected. Run [ReportA] to display data in table, [TableA]. Validate there is no longer a row displayed for [TestClient], as expected Run [ReportB] to display data in table, [TableB]. Validate there is no longer a row displayed for [TestClient], as expected Run [ReportC] to display data in product table noted in the setup. For this test, the "SYSTEM.cw_patient_notes" table Validate there is no longer a row displayed for [TestClient], as expected	Topics • Client Search
2023 Update 140 Summary \| Details Medical Note - Reviewing 'My To Dos' Scenario 1: Medical Note - In-Office Administration - ToDo's - Administer and refusal Specific Setup: The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N". Please log out of the application and log back in after completing the above configuration. Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B) An outpatient program must exist. (Program A) A client must have an active episode in "Program A". (Client A) Two users must exist in the application. (User A and User B) "User A" is configured as a "Nurse" and "User B" is configured as a "Provider". "User A" must be logged into the application. Steps Search for and select "Client A" and navigate to the 'Medical Note'. Click [Add Note] and create a new note. Select the 'Document' tab and then navigate to the 'In-Office Administration' section. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field. Populate any required fields and click [Order]. Validate the 'Pending Administrations' field contains a row for "Medication A". Click [Add] and select "Medication B" from the 'In-Office Administration Search' field. Populate any required fields and click [Order]. Validate the 'Pending Administrations' field contains a row for "Medication B". Click [Send To Do]. Set "User B" in the 'To-Do Recipient'. Set the 'Notes' field to any value and click [Send]. Log out of the application and log back in as "User B". Access the 'My To Do's' widget. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item]. Click 'In-Office Administrations'. Validate the 'Pending Administrations' field contains a row for "Medication A". Click the ellipses under the 'Action' column for "Medication A" and click [Administer]. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and disabled. Populate any required fields and click [Save]. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse]. Select any value in the 'Refused Reason' field and click [Save]. Expand the 'Administration History' field and validate it contains a row for "Medication B" with a status of 'Refused'. Click the [Complete] button for the To Do and then click [Close]. Validate that the 'To Do' for "Client A" is no longer listed in the 'Additional ToDos' section. Scenario 2: Medical Note - Pediatric Immunization - ToDo's - Administer and refusal Specific Setup: The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N". The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A) Please log out of the application and log back in after completing the above configuration. A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A) A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A) A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication B) An outpatient program must exist that is configured as a 'Primary Care' program. (Program A) A client must have an active episode associated with "Program A" and is pediatric patient. (Client A) Two users must exist in the application: One who is configured as a "Nurse" (User A) and one who is configured as a "Provider". (User A and User B). "User A" must be logged into the application. Steps Search for and select "Client A" and navigate to the 'Medical Note'. Click [Add Note]. Create a 'Primary Care' note. Select the 'Document' tab and then navigate to the 'Immunization' section. Click [Add] and select "Medication A" from the 'Immunization Search' field. Populate all required fields and click [Order]. Validate the 'Pending Administrations' field contains a row for "Medication A". Click [Add] and select "Medication B" from the 'Immunization Search' field. Populate all required fields and click [Order]. Validate the 'Pending Administrations' field contains a row for "Medication B". Click [Send To Do]. Set "User A" in the 'To-Do Recipient'. Set the 'Notes' field to any value and click [Send]. Log out of the application and log back in as "User B". Access the 'My To Do's' widget. Select "Client A" from the 'Additional To Dos' list and click [Review To Do Item]. Select the 'Immunization' section. Validate the 'Pending Administrations' field contains a row for "Medication A". Click the ellipses under the 'Action' column for "Medication A" and click [Administer]. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled. Select "Yes" for the 'Consent Obtained' radio button. Select "Not VFC eligible" from the 'VFC Eligibility Code' field. Select "Facility" from the 'Provided BY' field. Populate all required fields and click [Save]. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse]. Select any value for the 'Refused Reason' field and click [Save]. Expand the 'Immunization History' field and validate it contains a row for "Medication B" with a status of "Refused". Click the [Complete] button for the To Do and then click [Close]. Validate that the 'To Do' for "Client A" is no longer listed in the 'Additional ToDos' section.	Topics • Medical Note • To Dos

RADplus_2024_Monthly_Release_2024.02.00_Details.csv