RADplus 2022 Quarterly Release 2022.04 Acceptance Tests

Last updated
Save as PDF

Update 16 Summary \| Details Document Management - Perceptive 2022.01 Release Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Batch Capture and Indexing Client Document Capture Document Capture Staff Document Capture Entity-Based Document Capture Document Management Definition Family Registration Delete Document Scenario 1: Perceptive Batch Capture and Indexing - JxBrowser enabled Specific Setup: Perceptive storage method must be utilized. Steps Open the "Batch Capture and Indexing" form. Click "Capture" to create a new batch. Choose "Scanner" for the "Source". Click "Open Batch". Scan a document If Batch Verify is utilized, then click "Send To". If Batch Verify is not utilized, then click "Submit". If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane. Select the batch that was sent to this queue. Open the batch and click "Submit". Close form. Open the "Batch Capture and Indexing" form. Click "Capture" to create a new batch. Choose "File" for the "Source". Click "Browse" and browse to the location of where the file is stored on the server. Click "Open". Click "Open Batch". If Batch Verify is utilized, then click "Send To". If Batch Verify is not utilized, then click "Submit". If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane. Select the batch that was sent to this queue. Open the batch and click "Submit". Close form. Open "Chart Review" form for the client and episode that the documents were just scanned and imported for. Navigate to the form/category that you want to validate. Select a document that was scanned in. Validate that the document displays. Click the "Print" button. Print the document. Validate that the printed document matches what displayed on the viewer. Select a document that was imported in. Validate that the document displays. Click the "Print" button. Print the document. Validate that the printed document matches what displayed on the viewer. Open "Clinical Document Viewer". Validate you can view and print both the scanned and imported document. Scenario 2: Perceptive Individual Scanning/Importing/Viewing/Printing through Chart Review Specific Setup: Perceptive storage method must be utilized. Steps Open the "Chart Review" form. Select the desired client and episode. Open the "Document Capture" form within Chart. Scan a document. Assign the document to a particular "Document Type". Save the document. Import a document. Assign the document to a particular "Document Type". Save the document. Navigate to the section designated by the "Document Type" the document was saved under. Navigate to the "Episode" tab. Open the document(s). Validate the document(s) can be viewed and display as scanned. Validate the document(s) can be printed and display as scanned. Close the document. Open the "Clinical Document Viewer". Select the desired client and episode. Locate the document(s) that were just scanned in or imported. Validate the document(s) can be viewed and display as scanned. Validate the document(s) can be printed and display as scanned. Close the form. Scenario 3: Client Document Capture - Validation Specific Setup: Perceptive storage method must be utilized. A client must be enrolled in an existing episode (Client A). A document must exist for import. Steps 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]. Scenario 4: Staff Document Capture - Validation Specific Setup: Perceptive storage method must be utilized. There must be a practitioner defined (Practitioner A). A document must exist for import. Steps Access the 'Staff Document Capture' form. Enter "Practitioner A" in the 'Staff ID' 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!" Access the 'Clinical Document Viewer' form. Select "Staff" in the 'Select Type' field. Select "Individual" in the 'Select All or Individual Staff' field. Select "Practitioner A" in the 'Select Staff' 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]. Navigate back to the open 'Staff Document Capture' form. Click [Launch POS Capture]. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?" Click [Import]. Validate a second document capture window opens. Navigate back to the open 'Staff Document Capture' form. Click [Discard]. Validate the document capture windows close and the form discards. Scenario 5: Entity-Based Document Capture - Validation Specific Setup: Perceptive storage method must be utilized. Select a client, staff, provider, family and performing provider for the tests. Steps Open the "Entity-Based Document Capture" form. Select "Client" in the "Entity Type" dropdown. Select "Non-episodic" in the "Episode Number" dropdown. Click "Launch POS Capture" button. Import in a document saved as a file on the server. Validate the document renders on screen. Select a "Document Type". Optionally, set the "Document Description" to desired text. Click the "Save" button. Validate that messages display indicating the document was successfully saved. Click the "Close" button. Close the form. Open the "Clinical Document Viewer". Select the "Client" Entity. Select the client from the document capture above. Validate a row was added for the document that was just saved. View the document to validate it displays as it was captured. Print the document to ensure it prints as it was captured. Open the "Entity-Based Document Capture" form. Select "Staff" in the "Entity Type" dropdown. Click "Launch POS Capture" button. Import in a document saved as a file on the server. Validate the document renders on screen. Select a "Document Type". Optionally, set the "Document Description" to desired text. Click the "Save" button. Validate that messages display indicating the document was successfully saved. Click the "Close" button. Close the form. Open the "Clinical Document Viewer". Set "Select Type" to "Staff". Select the staff from the document capture above. Validate a row was added for the document that was just saved. View the document to validate it displays as it was captured. Print the document to ensure it prints as it was captured. Open the "Entity-Based Document Capture" form. Select "Performing Provider" in the "Entity Type" dropdown. Click "Launch POS Capture" button. Import in a document saved as a file on the server. Validate the document renders on screen. Select a "Document Type". Optionally, set the "Document Description" to desired text. Click the "Save" button. Validate that messages display indicating the document was successfully saved. Click the "Close" button. Close the form. Open the "Clinical Document Viewer". Set "Select Type to "Performing Provider". Select the client from the document capture above. Validate a row was added for the document that was just saved. View the document to validate it displays as it was captured. Print the document to ensure it prints as it was captured. Open the "Entity-Based Document Capture" form. Select "Provider" in the "Entity Type" dropdown. Click "Launch POS Capture" button. Import in a document saved as a file on the server. Validate the document renders on screen. Select a "Document Type". Optionally, set the "Document Description" to desired text. Click the "Save" button. Validate that messages display indicating the document was successfully saved. Click the "Close" button. Close the form. Open the "Clinical Document Viewer". Set "Select Type" to "Provider". Select the client from the document capture above. Validate a row was added for the document that was just saved. View the document to validate it displays as it was captured. Print the document to ensure it prints as it was captured. Open the "Entity-Based Document Capture" form. Select "Family" in the "Entity Type" dropdown. Click "Launch POS Capture" button. Import in a document saved as a file on the server. Validate the document renders on screen. Select a "Document Type". Optionally, set the "Document Description" to desired text. Click the "Save" button. Validate that messages display indicating the document was successfully saved. Click the "Close" button. Close the form. Open the "Clinical Document Viewer". Set "Select Type" to "Family". Select the client from the document capture above. Validate a row was added for the document that was just saved. View the document to validate it displays as it was captured. Print the document to ensure it prints as it was captured. Close all forms. Scenario 6: Chart Review - Document Capture - Scan Nonepisodic Specific Setup: Perceptive must be configured and enabled. Steps Open the "Chart Review" form. Select the desired client. Navigate to the "Chart". Click "Document Capture". Scan a document and identify it was non-episodic. Note the document type. Save the document. Click the document type the document was just saved under. Locate the document that was just saved. Validate the document displays as it was scanned. Print the document and validate it prints as it was scanned. Close the forms. Scenario 7: Chart Review - Document Capture - Import Non Episodic Specific Setup: Perceptive must be configured and enabled. Steps Open the "Chart Review" form. Navigate to the "Chart". Click "Document Capture". Import a non-episodic document. Assign a "Document Type" to the document. Optionally, add a "Document Description". Save the document. Validate messages display that indicate the document was successfully saved. Select the document type from the list that the document was just saved under. Select the document that was just saved from the document list. Validate the document displays and prints as it was rendered upon import. Close all forms. Scenario 8: Chart Review - Document Capture - Import Episodic Specific Setup: Perceptive must be configured and enabled. Steps Open the "Chart Review" form. Select the desired client. Navigate to the "Chart". Click "Document Capture". Import a document and select an episode. Note the document type. Save the document. Click the document type the document was just saved under. Locate the document that was just saved. Validate the document displays as it was imported. Print the document and validate it prints as it was imported. Close the forms. Scenario 9: Chart Review - Document Capture - Scan Episodic Specific Setup: Perceptive must be configured and enabled. Steps Open the "Chart Review" form. Select the desired client. Navigate to the "Chart". Click "Document Capture". Scan a document and identify an episode. Note the document type. Save the document. Click the document type the document was just saved under. Locate the document that was just saved. Validate the document displays as it was scanned. Print the document and validate it prints as it was scanned. Close the forms. Scenario 10: Client Document Capture - Scan Episodic Specific Setup: Perceptive must be configured and enabled. Steps Open the "Chart Review" form. Select the desired client. Navigate to the "Chart". Click "Document Capture". Scan a document and identify an episode. Note the document type. Save the document. Click the document type the document was just saved under. Locate the document that was just saved. Validate the document displays as it was scanned. Print the document and validate it prints as it was scanned. Close the forms. Scenario 11: Family Entity - Validation Specific Setup: Perceptive must be installed and configured. Family entity must be configured on the perceptive server. Using the "Document Management Defaults" form: Select "Family" in the "Select Entity Types Allowed" checklist. Using the "Document Management Definition" form Add new document type(s) for the Family entity documents. Using "Family Registration", create a family and add family members. Steps Open the "Entity-Based Document Capture" form. Select "Family" in the "Entity Type" field. Select the Family created in setup. Scan a document. Save the document and validate messages are received saying it was saved successfully and added to Avatar. Open the "Clinical Document Viewer". Retrieve the family document that was scanned in. Validate the document displays as it was captured. Print the document and validate it prints as it displays. Open the "Entity-Based Document Capture" form. Select "Family" in the "Entity Type" field. Select the Family created in setup. Import a document. Save the document and validate messages are received saying it was saved successfully and added to Avatar. Open the "Clinical Document Viewer". Retrieve the family document that was imported in. Validate the document displays as it was captured. Print the document and validate it prints as it displays. Scenario 12: Clinical Document Viewer - "Void & Copy" documents Specific Setup: Perceptive is enabled. In "User Definition", validate user has permissions to void documents. The entity being tested must have imported or scanned documents on file. Steps Access the 'Clinical Document Viewer' form. Select the desired entity in the "Entity Type field". Select "Individual" in the 'Select All or Individual' entity field. Select the desired entity (Client ID, Staff ID, Family ID, etc). Click [Process]. Select a document and view it. Click [Void] and then [Void & Copy] Select a target entity to copy the document to. If the entity is a client, select the desired episode in the 'Select Episode' field. Click [Void]. Validate the document list now has a Status of "Void" for the original document. Select the "Search" section. Select the target entity. Click [Process]. Validate the copied document is now in the document list for this entity. View the copied document and validate it displays as expected. Click [Close All Documents]. Select the "Search" section. Click [Close]. Scenario 13: Clinical Document Viewer - "Void" documents Specific Setup: Perceptive is enabled. User has permissions to void documents. A client must have non-routed documents on file in the 'Clinical Document Viewer' (Client A). A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer'. Steps Access the 'Clinical Document Viewer' form. Select "Individual" in the 'Select All or Individual Client' field. Select "Client A" in the 'Select Client' field. Click [Process]. Select any non-routed document and view it. Click [Void] and [Void] again. Select the desired value in the 'Void Reason' field. Enter the desired value in the 'Void Comments' field. Click [Void] and [Close All Documents]. Select the "Search" section. Click [Close]. Select "Client A" and navigate to the 'All Documents' view. Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void". Select the document. Validate the document displays with "Voided" in the 'Console Widget Viewer'. Scenario 14: Clinical Document Viewer - View and Print Specific Setup: Select a client who has documents that have been routed, scanned and imported. Steps Open the "Clinical Document Viewer" form. Open a document that was imported from a .bmp file. Validate you can view and print this document. Open a document that was imported from a .gif file. Validate you can view and print this document. Open any document that was imported from a .jpg file. Validate you can view and print this document. Open any document that was imported from a .tif file. Validate you can view and print this document. Open any document that was imported from a .txt file. Validate you can view and print this document. Open any document that was imported from a .xls file. Validate you can view and print this document. Open any document that was imported from a .xml file. Validate you can view and print this document. Open any document that was imported from a .doc file. Validate you can view and print this document. Open any document that was imported from a .png file. Validate you can view and print this document. Open any document that was imported from a .docx file. Validate you can view and print this document. Open any document that was imported from a .xslx file. Validate you can view and print this document. Open any routed progress note or treatment plan type of document. Validate you can view and print this document. Open any documents that were imported from a .pdf file. Validate you can view and print this document. Select 4 random documents to view. Validate that all 4 documents open for display and that all of them display. Click "Close All Documents". Select the same 4 random documents to print. Click "Print All". Validate all 4 documents preview and print out as if it's one file. Scenario 15: Clinical Document Viewer - Undocked Specific Setup: Select a test client who has multiple documents on file. Steps Click the "Undocked" icon on the "Clinical Document Viewer" form. Open a random document. Validate you can view and print the document. Select 4 documents to view. Validate you can display all 4 documents. Select 4 documents to print. Validate all 4 documents print as one document.	Topics • Perceptive • Clinical Document Viewer • NX
Update 67 Summary \| Details State Form Field Translation - form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form Field Translation Scenario 1: State Form Field Translation Form - field entry and validation Specific Setup: Have a state form file created in form "State Form Definition" [FileA] Steps Open form "State Form Field Translation" Select the state form [FileA] from the "State Form" field drop-down list. In the "Record" field, select a record. In the "Table" field, select the desired table. In the "Table Property" field, select the desired table property. In the "Action field", select "Single Translation" In the "Dictionary Code" field, enter a dictionary code [Code1] In the "State Forms Dictionary Code" field, enter a desired state form dictionary code [StateCode1] Click [Submit] to record the changes. Click [Yes] to return to the form In the "Dictionary Code" field, enter another dictionary code [Code2] In the "State Forms Dictionary Code" field, enter another desired state form dictionary code [StateCode2] Click [Submit] to record the changes. Click [Yes] to return to the form In the "Dictionary Code" field, enter another dictionary code [Code3] In the "State Forms Dictionary Code" field, enter another desired state form dictionary code [StateCode3] Click [Submit] to record the changes. Click [No] not to return to the form Open form "State Form Field Translation" Click the [Print Translations] button Validate the "File Name Override Field Translations" report contains the three codes filed in the previous steps Repeat step 2 In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4 Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode1] In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6 Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode2] In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8 Validate the "State Forms Dictionary Code" field, contains the expected value [StateCode3] Click the [Select Translations to Delete] button Validate all three translations are preset Click the check box for each item Click [OK] and [Yes] to continue Click [Submit] Click [Yes] to return to the form Repeat step 2 In the "Dictionary Code" field, enter dictionary code [Code1] entered in step 4 Validate the "State Forms Dictionary Code" field is blank, as expected In the "Dictionary Code" field, enter dictionary code [Code2] entered in step 6 Validate the "State Forms Dictionary Code" field is blank, as expected In the "Dictionary Code" field, enter dictionary code [Code3] entered in step 8 Validate the "State Forms Dictionary Code" field is blank, as expected Application Namespace Validation Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Application Namespace Connections Validation Scenario 1: Application Namespace Connection Validation Specific Setup: Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces Steps Open form "Applications Namespace Connection Validations" Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s): Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection errors. Click [Process] Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s):	Topics • State Form Tools • NX
Update 69 Summary \| Details CarePOVClinician - modeled forms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Mobile Application Build Scenario 1: Clinician<>Avatar: Validate synchronization of Modeled Form data Specific Setup: Have a modeled form in Avatar [FormA] Have an active client [ClientA] Have "CarePOV.Clinician" application installed and configured to connect to Avatar Have a user who is staff member configured as mobile user in form "User Definition" [UserA] [UserA] has launched and logged into Clinician Log into Avatar as [UserA] Steps In Avatar, open the "Mobile Application Build" form Select [FormA] in the "Select RADplus Forms" field Click [Submit] Validate submission is successful Log into Clinician Click [Synchronize] Verify synchronization is successful Verify [FormA] displays in the "All Forms" field Select [ClientA] Open [FormA] Populate the desired fields Click [Submit] Click [Synchronize] Validate synchronization is successful Log into Avatar Select [ClientA] Open [FormA] Edit the row filed in Clinician [RowA], in step 2 Validate fields on the modeled form are populated as expected Select a field [FieldA] and change the value in the field [NewValue] Submit the form In Clinician Click [Synchronize] Verify synchronization is successful Select [ClientA] Open [FormA] Edit [RowA] filed in Avatar, in step 3 Validate the field value [NewValue] is present in [FieldA], as expected Close the form Scenario 2: Clinican<>Avatar - Validate synchronization of client demographics data Specific Setup: Have an active client on the system [ClientA] [UserA] has access to form "Update Client Data" Steps Log into Clinician Select [ClientA] Open form "Update Client Data" Make a change to any field [FieldA], for example the "Address" field Submit the form Click [Synchronize] Verify synchronization is successful Log into Avatar Select [ClientA] Open form "Update Client Data" Validate the change made to the [FieldA] in step 1, is present on the form Make a change to another field [FieldB] Submit the form In Clinician Click [Synchronize] Verify synchronization is successful Select [ClientA] Open form "Update Client Data" Validate the change made to [FieldB] in step 2 is present as expected Close the form	Topics • Modeling • Admission • 835 Health Care Claim Payment/Advice • 835 • 837 Professional • 837 Institutional • Administration Location • Add New Appointment
Update 86 Summary \| Details Cache - process cleanup Scenario 1: Verify cleanup of cache internal background processes Steps Internal Testing Only	Topics • Cache
Update 87 Summary \| Details API Gateway Dashboard Scenario 1: MyAvatar (API Gateway) Dashboard - functionality Steps Internal Testing Only	Topics • Cache • NX
Update 90 Summary \| Details Client Name Display Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Chart Scenario 1: Validate client name display in the "My Clients" widget and "Chart" view header Specific Setup: Have a client with just first and last name defined. [ClientA] Have a client with first name, last name and middle name defined. [ClientB] Have a client with first name, middle name, last name and a suffix defined. [ClientC] Have a client with a prefix, first name, middle name, last name and a suffix defined. [ClientD] Have the "My Clients" widget on a user's [UserA] home view Have a client based form available for testing. For example "Update Client Data" [FormA] Have [FormA] added to the users home view Log in as [UserA] Steps In the "Search Clients" field of the "My Clients" widget, search for and select [ClientA] Validate the selected clients first and last name are displayed in both the "My Clients" and "Recent Clients" lists, as expected Right-click on the clients name and click to display the clients chart Validate the name in the client chart header displays clients first and last name, as expected Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their last name(in uppercase) Click back to the Home View Search and open [FormA] Validate the name in the client header displays clients first and last name, as expected Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their last name(in uppercase) Close or submit [FormA] Validate the name in the client header displays clients first and last name, as expected Validate the "Tab" above the client header, displays the client first name followed by the first initial of their last name(in uppercase) In the "Search Clients" field of the "My Clients" widget, search for and select [ClientB] Validate the selected clients first, middle and last name are displayed in both the "My Clients" and "Recent Clients" lists, as expected Right-click on the clients name and click to display the clients chart Validate the name in the client chart header displays clients first, middle and last name, as expected Validate the "Tab" above the client header, displays the client first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase) Click back to the Home View Search and open [FormA] Validate the name in the client header displays clients first, middle and last name, as expected Validate the "Tab" above the client header, displays the client first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase) Close or submit [FormA] Validate the name in the client header displays clients first, middle and last name, as expected Validate the "Tab" above the client header, displays the clients first name followed by the first initial of their middle name(in uppercase) and the first initial of their last name(in uppercase) In the "Search Clients" field of the "My Clients" widget, search for and select [ClientC] Validate the selected clients first, middle, last name and suffix(in uppercase letters) are displayed in both the "My Clients" and "Recent Clients" lists, as expected Right-click on the clients name and click to display the clients chart Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase) Click back to the Home View Search and open [FormA] Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase) Close or submit [FormA] Validate the name in the client chart header displays the clients first, middle, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase) In the "Search Clients" field of the "My Clients" widget, search for and select [ClientD] Validate the selected clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters) are displayed in both the "My Clients" and "Recent Clients" lists, as expected Right-click on the clients name and click to display the clients chart Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase) Click back to the Home View Search and open [FormA] Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase) Close or submit [FormA] Validate the name in the client chart header displays the clients prefix(in uppercase letters), first name, middle name, last name and suffix(in uppercase letters) Validate the "Tab" above the client header, displays the clients first name, first initial of their middle name(in uppercase), first initial of their last name(in uppercase)	Topics • Client Search
Update 94 Summary \| Details Root System Code - creation Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Document Management Definition Form Bundler (PM) User Role Definition Data Trail Configuration Launch RxConnect Scenario 1: New "Root" System Code - Data Validations after root system code creation Specific Setup: Have a system with a root system code defined [RootA] [RootA] has Avatar "PM", "CWS", "MSO" and "CFMS" installed In addition, [RootA] is configured with the following: "Avatar Identity Manager" is installed The 'Enable Avatar Identity Manager' registry setting is not set to 'Y "RXConnect" installed and configured [UserA] has permissions in form "User Definition" to "RxConnect" to login to the application "Avatar Order Entry" is installed In form 'Ask on Order Entry Definition' form, two questions are defined [TestA] and [TestB] Have a report or query to display data in the "OrderEntry.index_order_code" table [OrderRptA] "Avatar Data Trail" is installed Open form "Data Trail Configuration" and run the report by "Option" Expand the group tree for each namespace on left side panel and make a note of the forms listed under each namespace In form "Document Management Definition" a form name is defined [FormA] with a "Form Type" [FTypeA] that has two categories [CatA] and [CatB], selected in the "Categories" field In each namespace ("PM", "CWS", "MSO" and "CFMS") a form bundle [BundleA] has been created in form "Form Bundler", that contains two forms, [BformA] and [BformB]. In each namespace a modeled form [FormA] has been created using form "Form Definition" In each namespace a report definition [ReportA] has been created using form "Report Definition" A user role [RoleA] has been created in form "User Role Definition" Netsmart has created a new root system code, using [RootA] to copy data from. For this example [RootB] with Facility [5] assigned is used [UserA] has been assigned full form and table access in [RootA] and [RootB] Log in to [RootB] as [UserA] Steps Open form "Registry Settings" Search for setting 'Enable Avatar Identity Manager' Validate the setting is found, as the module is installed Validate the setting is set to "N", as the module has not been enabled and configured yet in the new root system code Close the form Open form "'Ask on Order Entry Definition'" Click the "Edit" radio button In the "AOE to Edit" search field, enter [TestA] Validate the question is found, and results are as expected In the "AOE to Edit" search field, enter [TestB] Validate the question is found, and results are as expected Run the "OrderEntry.index_order_code" table report [OrderRptA] Validate a row is present with the "Order Code" column populated with [TestA] and the "Facility" column contains "7" the new facility number for [RootB] Validate a row is present with the "Order Code" column populated with [TestB] and the "Facility" column contains "7" the new facility number for [RootB] Close the report Close the form Open form "Document Management Definition" Click [Select Form] Select [FormA] Select [FTypeA] in the "Form Type" field Click [Select Categories] Validate categories [CatA] and [CatB] are displayed Close the form Open form "Form Bundler" in "PM" Click [Edit Existing] Validate [BundleA] is present in the list and click [OK] to select the bundle Click [Included Forms] Validate [BformA] and [BformB] are listed, as expected Close the form Open form "Form Bundler" in each of the child namespaces Repeat steps 4 a and b Validate results are as expected Close the form From the "Search Forms" field on the home view, search for the "Report Definition" form [ReportA] in "PM" Select the form Validates the form opens successfully Close the form Repeat step 6 opening [ReportA] in each of the child namespaces Validate results are as expected From the "Search Forms" field on the home view, search for the "Modeled" form [FormA] in "PM" Select the form Validate the form opens successfully Close the form Repeat step 8, searching for the modeled [FormA] in each of the child namespaces Validate results are as expected Open form "User Role Definition" Click [Select User Role] Validate [RoleA] is present in the results Click to open the role Validate data is populated as expected Close the form Open form "Data Trail Configuration" Select "Option" in the "Sort Report By" field Click [Run Report] Expand the group tree for each namespace on left side panel Compare the forms listed under each namespace with ones noted in the set up Validate the forms listed are the same in both root system codes At the home screen, search for form "Launch RXConnect" Click [Launch RXConnect] Validate the "RXConnect" application is launched in separate window Validate the user is automatically logged in Click logout At the login screen, enter the Avatar user name and password Click login Validate the user is logged in successfully Click [Logout] In Avatar, close the form Root System Code - Facility numbers Scenario 1: New "Root" System Code creation Steps Internal Testing Only	Topics • Forms • NX
Update 96 Summary \| Details RADPlus - Family Entity Modeling Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Change MR# Family Registration Delete Last Movement Table Definition (PM) Family Entity User Modeled Form Delete Family Scenario 1: Change MR# - "Family" Entity Data validations Specific Setup: Have an active test client on the system [ClientA], note their current PatID# [OrigPatID#] In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form. Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved Have a report [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table Steps Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is a row displayed for [FamilyA] and [ClientA] Open "Change MR#" form in Avatar PM. Select [ClientA] in the "Client ID" field and note their current PatID# [OrigPatID#] Click [Assign MR#]. Note the new PatID# assigned, [NewPatID#] Click [Submit]. Validate the form files successfully At the home view, search for the [OrigPatID#] noted in step 3a Validate there are no results Now search for the [NewPatID#] noted in step 3b Validate the [NewPatID#] is found and the associated client is [ClientA] Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is a row displayed for [FamilyA] and with new PatID# [NewPatID#] displayed for [ClientA] Scenario 2: Client Delete - "Family" Entity Data validations Specific Setup: Have an active test client on the system [ClientA] In form "Family Registration", have a family created [FamilyA] with [ClientA] added as a family member in "Family Members" section of the form. Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table User has launched [ReportA] and has logged into the system Steps Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is a row displayed for [FamilyA] and [ClientA] Open "Client Delete" form. Select [ClientA] 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 "Family Registration" Select [FamilyA] Click the "Family Members" section Select the row for [ClientA] Click [Delete] Validate the client is removed as a family member Submit the form Open "Client Delete" form. Select [ClientA] in the "Client ID" field. Validate an error message is received "All Movements must be deleted before Client can be deleted" Click [OK] Close the form Open form "Delete Last Movement" Select [ClientA] Select the admission episode from the "Episode Number" drop down list Click [Submit] Click [Yes] to continue Validate the form submits successfully Open "Client Delete" form. Select [ClientA] in the "Client ID" field. Click [Submit] Validate the form submits successfully At the home view, search for [ClientA] Validate there are no results Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is no longer a row displayed for [FamilyA] and [ClientA] Scenario 3: "Family" Entity User Modeled Form - Create a new form Specific Setup: In form "Family Registration" have a family created [FamilyA] with one or more clients added as family member's in "Family Members" section of the form. For this test, [ClientA], [ClientB] and [ClientC] are used Steps Open form "Envelope Definition" Click the [New Avatar Envelope] Set the "Envelope Description" field to the desired name [EnvelopeA], for the envelope Select "Family" in the "Entity Database" field Click the "Yes - Is Envelope Eligible for Export" radio button Click the "Yes - Always Allow Export" radio button Click [Submit] Validate the form files successfully Open form "Table Definition" At the "Select Avatar Table" prompt enter the desired table name [TableA] Click the [New Avatar Table] button From the "Envelope" dialog drop down list, select [EnvelopeA] Populate the "Table Name" field with the desired table name [TableA] Populate the "Table Description" field with the desired description of the table Select the "Column Definition" section Click the [Add New Item] button Select "Family Member(s)" column from the "Type of Column" drop down list Populate the "Column Name" field Populate the "Column Description" field Populate the "Column Label" field Validate the "Column Definition" grid contains a row with values just populated Click the [Add New Item] button Select "Draft/Final (Document Routing)" column from the "Type of Column" drop down list Populate the "Column Name" field Populate the "Column Description" field Populate the "Column Label" field Validate the "Column Definition" grid contains a row with values just populated Repeat step 4 for any other desired prompts to be added from the "Type of Column" drop down list Validate results are as expected Click [Submit] Validate the form files successfully Open form "Form Definition" At the "Select Avatar Table" prompt enter the desired form name [FormA] Click the [New Avatar Form] button From the "Envelope" dialog drop down list, select [EnvelopeA] Populate the "Table Name" field with the desired table name [TableA] Populate the "Table Description" field with the desired description of the table Select a menu location for the form from the "Menu to Place Form Under" field Populate the "Form Name" field [FormA] In the "Primary Table" field, select [TableA] Click the "Pre-display" section Select one or more pre-display columns from the "Primary Table Pre-display" column prompts Click the "Section Definition" section Click [Add New Item] and populate the "Section Description" field Click the "Object Definition" section Click [Add New Item] From the "Table Column" field, select the "Family Member's" column Validate the "Object Definition" grid reflect the column added From the "Table Column" field, select the "Draft/Final" column Validate the "Object Definition" grid reflect the column added Repeat step b adding any other columns desired from the "Table Column" field Validate the "Object Definition" grid reflect the columns added Click [Submit] Validate the form files successfully Open [FormA] At the "Select Family" prompt, select [FamilyA] Validate the form loads successfully Verify the "Family Member's" field is present and contains each client added as a family member in the set up, along with a check box next to their name. Verify the "Draft/Final" field is present on the form. Verify any other fields added during "Form Definition" are present on the form, as expected. Select values for any desired fields on the form Submit the form Validate the form files successfully. Scenario 4: "Family" Entity User Modeled Form- Form submission and Doc Routing Validations Specific Setup: The "Document Management Defaults" form has "Family - User Defined Family" selected in the field "Select Entity Types Allowed" The "Document Management Definition" form has been submitted with a "Form Name" [FName] associated to the "Family" entity in the "Entity Database" field. In form "Family Registration" have a family created [Family] with family members added in "Family Members" section of the form. For the test [ClientA] and [ClientB] Have a user modeled form [Form] created based on the "Family - User Defined Family" entity database [Form] contains fields from [Table] that include a "Family Member(s)" column type, a field using a "Draft/Final" column type and any other desired field types [Form] is enabled for document routing with form name [FName] selected in the "Select Type" field [User] is a staff member who has access to [Form] and [Table] [User] has the "My To do's" widget on their home view Have a report [Report], set to display data in the "SYSTEM.user_modelled_fam_members" table Log in as [User] Steps Access [Form] In the "Select Family" prompt, select [Family] Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB] Click "All", to select all members Populate any other desired fields on the form Select "Draft" in the 'Draft/Final' field. Click [Submit] Validate the form files successfully Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is a row displayed for [Family] and [ClientA] Validate there is a row displayed for [Family] and [ClientB] Access [Form] In the "Select Family" prompt, select [Family] In the pre-display screen, click [Edit] to select the row filed in step 1 Validate all fields are populated, as expected Close the form Access [Form] In the "Select Family" prompt, select [Family] In the pre-display screen, select the row filed in step1 Click [Delete] Validate the row is removed from the pre-display Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table Validate the row field for [Family] and [ClientA], has been deleted Validate the row field for [Family] and [ClientB], has been deleted Access [Form] In the "Select Family" prompt, select [Family] Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB] Click "All", to select all members Populate any other desired fields on the form Select "Final in the 'Draft/Final' field. Click [Submit] and then [OK] Validate the "Confirm Document" screen displays all data submitted, including clients [ClientA] and [ClientB] listed in the "Family Member's field. Click [Accept and Route] Enter the password for the user in the 'Password' field and click [OK]. At the "Route Document to" dialog, add [User] as an approver Click [Submit] Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table Validate there is a row displayed for [Family] and [ClientA] Validate there is a row displayed for [Family] and [ClientB] Navigate to the "My To Do's" widget Click the "New" tab Validate the To Do for [Form] is present in the list Validate the "Client" column indicates [Family] Click [Approve Document] Validate the document displays all data submitted, including clients [ClientA] and [ClientB] in the "Family Member's" field. Click [Accept] Validate the To Do is removed the widget, as expected In the "My Clients" widget, select any one of the clients selected as a family member in submission of [Form] in step 1. For example [Client] Double click on the client to open their "Chart" In the "Documents" section on left side panel, click the form type [Fname], associated with [Form] Locate the row listed for the document approved for [Form] in step 2 Click the "View" check box and then the [View] button to display the document Validate the document displays all the data submitted as expected Close the chart Scenario 5: Delete Family - Form (Submission and Validations) Specific Setup: Have an active test client on the system [ClientA] In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form. Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing File a row for [FamilyA], selecting [ClientA] selected in the "Family Members" field and routing the document to [UserA] to create To do [UserA] has the "My To do's" widget on their home view Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table [UserA] has launched [ReportA] and has logged into the system Steps Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table Verify a data row is displayed for the row filed in the set up for [FamilyA] that includes [ClientA] On the home view, validate a To do exists in the "My To do's" widget for the row filed in [FormA] in the set up Open form "Delete Family" Select [FamilyA] Validate an error message is displayed stating "The Family has members on file. You must delete all family members in the Family Registration form prior to deleting the family" Click [OK] Open form "Family Registration" Select [FamilyA] Click the "Family Members" section Select each family member row and click delete to remove the row Submit the form Open form "Delete Family" Select [FamilyA] Click [Submit] At the "Delete Family" dialog, click [Yes] Validate the message "Family has been Deleted" displays Click [OK] Open form "Delete Family" Search for [FamilyA] Validate [FamilyA] is not found Return to the "My To Do's" widget Validate a To do is no longer present for [FormA] for [ClientA] Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table Verify there are no rows displayed for [FamilyA]	Topics • Client Merge • NX • Database Tables
Update 98 Summary \| Details ECP Server - Reports Scenario 1: Validate report data results when run from an "ECP" server Specific Setup: Have an Avatar system that also has an "ECP" server configured (by Netsmart) to connect to the Avatar server via the "ECP" server, so that reports can be generated from the "ECP" server Have access to two forms run from within Avatar, that launch a report A "PM" form [FormA], for example the "PM" report, "Client Ledger" A child namespace form [FormB], for example "CWS" form "Problem List" Have two reports that can be run from outside the Avatar application, for example via "Crystal Reports" A "PM" table based report [ReportA], for example the "SYSTEM.patient_demographic_history" table A child namespace based table [ReportB] for example "CWS" table, "SYSTEM.cw_patient_notes" [UserA] has permissions to run the forms and reports outlined in the setup Log in as [UserA] Steps Navigate to [FormA] Populate all desired fields Click to launch the report Validate the data results in the report, are as expected Close the report Wait one minute or more Repeat step b Validate the data results in the report, are as expected Navigate to [FormB] Populate all desired fields Click to launch the report Validate the data results in the report, are as expected Close the report Wait one minute or more Repeat step b Validate the data results in the report, are as expected Launch [ReportA] Click "Preview" Validate the data results in the report, are as expected Wait one minute or more Repeat step a Validate the data results in the report, are as expected Close the report Launch [ReportB] Click "Preview" Validate the data results in the report, are as expected Wait one minute or more Repeat step a Validate the data results in the report, are as expected Close the report RADplus - processing Scenario 1: Validate cache internal processing "User.RadPlusProcessStorage" table Steps Internal Testing Only	Topics • Cache • NX
Update 101 Summary \| Details DocR.document_history table Scenario 1: Validate data in 'DocR.document' table Specific Setup: [UserA] is a staff member and also has permissions to co-sign to do's for other staff members [UserB] is a staff member and has the 'My To Do's' widget on the Home View. A client [ClientA] is enrolled in an open episode Document routing is enabled for a form [FormA]. For example, a progress note or modeled form Have a report [ReportA] to display data in the "DocR.document_history" table Log in as [UserB] Steps Access [FormA] Select [ClientA] in the 'Select Client' field. Select [Episode1] where the client is enrolled in [ProgramA] Populate all required fields any desired fields in the form Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate that the 'Confirm Document' dialog is displayed with expected data Click [Accept and Route]. Validate the 'Route Document To' dialog is displayed. Select the [UserA] as the 'Approver'. Click [Submit]. Validate submission is successful Navigate to the 'My To Do's' widget. Select the "Sign" tab. Validate the 'Search Documents' field contains a row for the To do document routed in step 1 Log out as [UserB] Log in as [UserA] Navigate to the 'My To Do's' widget. Select the "Sign" tab. Search for [UserA] in the "Staff" field Validate the To do document routed to [UserA] in step 1 is listed in the "Search Document" list box Select the To Do row Click [Accept]. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section Select the row in the "Accepted Documents" section Validate the document preview, contains the expected data Click [Sign All] Enter the password for [UserA] in the 'Verify Password' dialog and click [OK]. Validate the 'Accepted Documents' field no longer contains the To do. (Note the approval submission date and time). Launch [ReportA] In the "Action Date" and "Action Time" columns, locate the row based on the approval submission date and time noted in step 5 Validate the "User_Task" column indicates "Approver" and the "UserID" column indicates the user ID or [UserA], the co-signer My To Do's Widget - Sign Tab Scenario 1: 'My To Do's' widget - Validate approving documents from the "Sign" Tab Specific Setup: Have a system with a root system code [RootA] and sub system code defined [SubA] [SubA] is set up to be restricted to only [ProgramA] [UserA] is a staff member and also has permissions to co-sign to do's for other staff members A client [ClientA] is enrolled in [ProgramA] in [Episode1] and [ProgramB] in [Episode2] Document routing is enabled for a form[FormA]. For example a progress note or modeled form [UserA] has access to log into [SubA] but does not have access to [RootA] [UserB] has access to [SubA] and [RootA] Both users have the 'My To Do's' widget on the Home View. Log in as [UserB] Steps Access [FormA] Select [ClientA] in the 'Select Client' field. Select [Episode1] where the client is enrolled in [ProgramA] Populate all required fields any desired fields in the form Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate that the 'Confirm Document' dialog is displayed with expected data Click [Accept and Route]. Validate the 'Route Document To' dialog is displayed. Select the [UserB] as the 'Approver'. Click [Submit]. Validate submission is successful Return to [FormA] Select [ClientA] in the 'Select Client' field. Select [Episode2] where the client is enrolled in [ProgramB] Repeat steps1c thru e Validate routing and submission is successful Navigate to the 'My To Do's' widget. Select the "Sign" tab. Validate the 'Search Documents' list box contains the row for the To Do routed for [Episode1] / [ProgramA] and a row for the To Do document routed for [Episode2] / [ProgramB] Log out as [UserB] Log in as [UserA] to sub code [SubA] Navigate to the 'My To Do's' widget. Select the "Sign" tab. Search for [UserA] in the "Search Documents" field Validate the To Do document routed for [Episode1] / [ProgramA] in step 1 Validate the To Do document routed for [Episode2] / [ProgramB] in step 2 is not present, as sub code [SubA] is restricted to only episodes admitted in [ProgramA] Select the To Do row Click [Accept]. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section Select the row in the "Accepted Documents" section Validate the document preview, contains the expected data Click [Sign All] Enter the password for [UserA] in the 'Verify Password' dialog and click [OK]. Validate the 'Accepted Documents' field no longer contains the To Do row for [Episode1] / [ProgramA] Log out as [UserB] and login as [UserA] Access the 'Clinical Document Viewer' form. Select "Client" in the 'Select All or Individual Client' field. Select [ClientA] in the 'Select Client' field. Click [Process]. Validate the document row for the To Do approved in step 4 is present Double click on the row Validate the document preview, contains the expected data Close the form. Guardiant - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Guardiant Scenario 1: Guardiant form - Field validations Specific Setup: Have a system configured for "Guardiant" reporting Have a user with access to the "Guardiant" form Steps Open form "Guardiant" Click the "Guardiant Configuration" section Click [Test Connectivity] Validate message "Connectivity Test Successful" is displayed Click [OK] Click [Test Daily Collection] Click [Yes] to the warning message Validate message "Test Succeeded" is displayed Click [Test Metrics Collection] Click [Yes] to the warning message Validate message "Test Succeeded" is displayed Click "Export Configuration" In "File Explorer", select a directory to save file Click [Save] Go to the directory where the file was saved Open the "GuardiantConfiguration.txt" file Validate data is present in the file	Topics • My To Do's • NX • Guardiant
Update 111 Summary \| Details Dictionary Values Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Dictionary Import (PM) Scenario 1: Validate updating dictionary fields via the right-click "Update Dictionary" grid functionality Specific Setup: Have a form [FormA] that includes an "Unlocked" dictionary field [FieldA], that includes existing dictionary values. Steps Open [FormA] Right-click on [FieldA] Click [Yes] to update the dictionary In the grid, click on any dictionary value in the "Dictionary Value" column Change the existing value to a value that includes a less than sign (<) Validate an error is displayed "Can Not Contain '<' Click [OK] Change the existing value to a value that does not include a less than sign (<) Validate the value is accepted Change the existing value in the "Active" column to a new value Click on any other row in the grid Click [Delete Row] Click [Yes] at the "Confirm Delete" dialog Validate an error is displayed stating existing dictionary codes cannot be deleted Click [OK] Click [New Row] Validate a new row is inserted at the bottom of the grid Populate the "Dictionary Code" field Populate the "Dictionary Value" field Enter a value that includes a less than sign (<) Validate an error is displayed "Can Not Contain '<' Click [OK] Enter a value that does not include a less than sign (<) Validate the value is accepted Select a value in the "Active" column to a new value Click [Save] Click [OK] to exit the grid Click [OK] Right-click on [FieldA] Validate all changes made in step 1 are displayed, as expected Close the grid On [FormA], click [FieldA] Validate the selection list contains the expected values Scenario 2: Dictionary Update (Form) - Field Validations Steps Open form "Dictionary Update" in any application. For this test "PM" is used Click the "File" file filed and select a file, for example "Payor" In the "Data Element" field, search for a dictionary field to update. For this example "Financial Class" is used In the "Dictionary Code" field, select any existing code In the "Dictionary Value" field, insert a less than sign "<" anywhere in the value Validate an error is displayed "Can Not Contain '<'" Click [OK] In the "Dictionary Code" field, enter a new code, for example "999" In the "Dictionary Value" field, enter a value that contains a less than sign "<" Validate an error is displayed "Can Not Contain '<' " Click [OK] In the "Dictionary Value" field, enter a value that does not contain a less than sign "<" Validate the value is accepted If applicable, select an extended dictionary from the "Extended Dictionary Data Element" field Select a dictionary value from the "Extended Dictionary Value (Single Dictionary)" field Click [Apply Changes] At the "Filed" dialog, click [OK] Scenario 3: Dictionary Import - Data import validations Specific Setup: Have a form [FormA] that contains a "Dictionary" type field [FieldA] Have access to form "Dictionary Update" Have a "Dictionary Import" file created [FileA] created for [FieldA], that contains dictionary codes configured with the following type characters in their dictionary values: [Code1] includes a dictionary value containing a less than sign (<) [Code2] includes a dictionary value containing a caret symbol (^) [Code3] includes a dictionary value containing an equal sign (=) [Code4] includes a dictionary value containing a tilde symbol (~) Have a "Dictionary Import" file created [FileB] created for [FieldA], that does not contain, a less than sign, caret symbol, equal sign or tilde symbol in any of the dictionary values to be imported Steps Open form "Dictionary Import" Click [Select File] Navigate the location of [FileA] and select it Click "Scan Import File" Validate the scan results indicate Error in row 1: Caret(s) found in dictionary value. Error in row 2: Equal sign(s) found in dictionary value. Error in row 3: Tilde(s) found in dictionary value. Error in row 4: Less than sign(s) found in dictionary value. Import file cannot be processed due to critical errors. Navigate the location of [FileB] and select it Click "Scan Import File" Validate the scan results indicate "No errors or warnings found in file." Click "Begin Import" At the "Dictionary Import Complete" dialog, click [OK] Open [FormA] Navigate to [FieldA] and click on the field Validate the fields imported in [FileB] in step 1, are present in the selection list as expected Close the form	Topics • Dictionary • NX
Update 112 Summary \| Details Envelope and Report Definition Forms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Envelope Export (PM) Report Definition (PM) Report Definition Export Scenario 1: Envelope Export - validations Specific Setup: Have an existing Modeled form [FormA] that exists in [EnvelopeA] Steps Open form "Envelope Definition" Select [EnvelopeA] Note the value in the "Envelope Version Number" field, for example "1.01" Close the form Open form "Envelope Export" Select [EnvelopeA] Click [Begin Export] In the "File Explorer" dialog, select a folder location in the "Save In" field to save the export file. In the "File_Name" field, validate that the file name populated includes the name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and the file extension. For example "NetsmartExportModeledFormV1_01.TXT" Click [Save] Close the form Open file "Envelope Import" Click [Select Envelope Import File] In the "File Explorer" dialog, navigate to the location of the export file Select the file and click [Open] Select the "Overwrite Existing" radio button Click [Begin Import Scan] Click [Begin Import] At the "Import Complete" dialog, click [OK] Close the form At the Home View, search for [FormA] and open the form Populate the desired fields on the form Submit the form Validate the form files successfully Scenario 2: Report Definition Export - validations Specific Setup: In form "Report Definition", have an existing report definition report [ReportA] created. For example, report "Admits By Program, Zip Code, Ethnicity" can be used Steps Open form "Report Definition" Select [ReportA] Note the value in the "Report Version Number" field, for example "1" Close the form Open form "Report Definition Export" Click [Begin Export] Select [ReportA] and in the "File Explorer" dialog: In the "Save In" field, Select a folder location to save the export file. In the "File_Name" field, validate the file name populated includes: The name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and then the file extension. For example "CSMReportExportAdmitsByProgramZipCodeEthnicityV1.TXT" Click [Save] Close the form Open file "Report Definition Import" Click [Select Report Import File] Navigate to the location of the export file saved in step 2, and select the file. Select the "Overwrite Existing" radio button Click [Begin Import Scan] Click [Begin Import] Click [OK], in the "Import Complete" dialog Close the form At the home view, search for [ReportA] and click to open the form Populate the desired fields on the form Submit the form and vlidate the report is displayed as expected Close the report and the form	Topics • Envelope Definition • Envelope Import • NX • Envelope Export
Update 113 Summary \| Details Client Search - results Scenario 1: Validate client search results using "Alternate" lookups Specific Setup: Have the "My Clients Widget" on the home view Have a client [ClientA], that has their "Date of Birth", "Social Security Number" populated in their client record along with an "Alias" name. For this test, [ClientA] is "Mary Jones" and she has an alias of "Jane Doe" Have the "Client Lookup/Header Configuration Manager" form, have "Alias" configured as an "Alternate" search Have any form [FormA], that includes a client search field within the form [FormA]. For example "Progress Notes Group and Individual" Have access to any client based form [FormB], for example "Update Client Data" Steps Open [FormA], the form that includes a search client field In the "Select Client" search field, search for [ClientA] using their "Date of Birth" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their "Social Security Number" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their name Validate [ClientA] is found in the search results In the search field, enter the first name of their "Alias" name. For this example, "Jane" is entered Validate [ClientA] is found in the search results Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]", as expected. (For this example, MARY JONES (0000003) [Alias: Jane Doe] is displayed) Navigate to the "Search Clients" field of the "My Clients" widget In the search field, search for [ClientA] using their "Date of Birth" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their "Social Security Number" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their name Validate [ClientA] is found in the search results In the search field, enter the first name of their "Alias" name. For this test, "Jane" is entered based on the setup steps Validate [ClientA] is found in the search results Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]" For this test, MARY JONES (0000003) [Alias: Jane Doe] would be displayed Click the "Advanced" button next to the "Search Clients" search field In the "Last Name" field, enter any letter In the "Sex" field, select a value In the "Alias" field, enter the "Alias" for [ClientA] Open [FormB], the client based form In the "Select Client" search field, search for [ClientA] using their "Date of Birth" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their "Social Security Number" Validate [ClientA] is found in the search results In the search field, search for [ClientA] using their name Validate [ClientA] is found in the search results In the search field, enter the first name of their "Alias" name. For this test, "Jane" is entered based on the setup Validate [ClientA] is found in the search results Validate the format of the results are displayed as: "Clients Name, (PatID#) [Alias: Alias Name]" For this test, MARY JONES (0000003) [Alias: Jane Doe] would be displayed	Topics • Client Search • NX
Update 114 Summary \| Details Form Designer Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Form Designer (PM) Form Designer (CWS) Modeled form with Default Dictionary Values Scenario 1: Form Designer - Submit and validate form designer changes Specific Setup: Have access to a form [FormA] in the PM namespace, for example the "Admission" form Have access to a form [FormB] in the child namespace, for example a "CWS" modeled form Have access to the "Form Designer" form in "PM" and in the child namespace Steps Access the 'Form Designer' form in the "PM" namespace. Select [FormA] from the 'Forms' field. Select the desired section [SectionA] from the 'Sections' field. Click [Show Section]. Select any field [FieldA] and move/re-size it as desired. Click [Cancel] and [Yes]. Click [Show Section]. Validate nothing has changed. Select any field [FieldA] and move/re-size it as desired. Click [Save], [OK], and [Submit]. Access [FormA] Navigate to [SectionA] Validate [FieldA] is displayed in the location set in step 1 Validate the size of [FieldA] is as expected based on the change make in step 1 Click [Discard]. Access the 'Form Designer' form in the child namespace Select [FormB] from the 'Forms' field. Select the desired section [SectionA] from the 'Sections' field. Click [Show Section]. Select any field [FieldA] and move/re-size it as desired. Click [Cancel] and [Yes]. Click [Show Section]. Validate nothing has changed. Select any field [FieldA] and move/re-size it as desired. Click [Save], [OK], and [Submit]. Access [FormB] Navigate to [SectionA] Validate [FieldA] is displayed in the location set in step 1 Validate the size of [FieldA] is as expected based on the change make in step 1 Click [Discard].	Topics • Forms Designer • NX
Update 117 Summary \| Details User File Import Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: User File Import Scenario 1: Verify 'User File Import' Specific Setup: Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality” configured. An "(ODIC) Identity Provider" solution is configured with Netsmart's (NIAM) functionality to provide external login authentication. [UserA] has been assigned an external login ID [NaimID] and password that can be used to login using the '(ODIC) Identity Provider' solution The system also has the "Identity Manager" module installed In form "User Definition", [UserA] has prompt "Associate User to Network ID Through Avatar Identity Manager" set to "Yes". Have registry setting "Enable Avatar Identity Manager" set to "No" Have a "User File Import" file created [FileA], that includes a row for [UserA], set with: Field "Associate User to Network ID Through Avatar Identity Manager" set to "No" Field "User Description" set to a desired description Field "Use External Login" set to "Yes" Field "External Login ID" set to the user external ID [NaimID] Have a second "User File Import" file created [FileB], that includes a row for [UserA], set with: Field "Associate User to Network ID Through Avatar Identity Manager" set to "Yes" Field "User Description" set to blank Field "Use External Login" set to "No" Field "External Login ID" set to blank Steps Open the 'User File Import' form. Click [Select User Import File] Navigate to the location of [FileA] and select the file Click [Open]. Validate the scan results display messages, "Warning: Row 1 contains an existing User ID which will be edited on import (UserA)" and "Warnings but no errors detected in import file. Import may proceed" Click [Process User Import File] Validate there are no errors Click [OK]. Validate the import completes successfully Close the form Open form "User Definition" Select [UserA] in the "Select User" field Validate field "Associate User to Network ID Through Avatar Identity Manager" set to "No" Validate field "User Description" is populated Validate field "Use External Login" set to "Yes" Validate field "External Login ID" set to the user external ID [NaimID] Open the 'User File Import' form. Click [Select User Import File] Navigate to the location of [FileB] and select the file Click [Open]. Validate the scan results display messages, "Warning: Row 1 contains an existing User ID which will be edited on import (UserA)" and "Warnings but no errors detected in import file. Import may proceed" Click [Process User Import File] Validate there are no errors Click [OK]. Validate the import completes successfully Close the form Open form "User Definition" Select [UserA] in the "Select User" field Validate field "Associate User to Network ID Through Avatar Identity Manager" set to "Yes" Validate field "User Description" is blank Validate field "Use External Login" set to "No" Validate field "External Login ID" set to blank	Topics • File Import • NX
Update 119 Summary \| Details Site Specific Section Modeling - Form 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) Form Designer (CWS) Scenario 1: (GA ASO) enabled "Progress Notes (Group and Individual)" forms - Validate "Site Specific Section Modeling" & "Import/Export" functionality Steps Internal Testing Only Scenario 2: "Create New Progress Note" form - Validate functionality in (GA-ASO) enabled environments Steps Internal Testing Only Scenario 3: Form Designer - Adding/Moving/Deleting Subsections(Bookmarks) Specific Setup: Have access to form "Form Designer" in any application Have a form [FormA] that can be used to make form designer changes that already contains one or more sections. For this example the "Progress Notes (Group & Individual)" form is used Steps Open "Form Designer" Select [FormA] in the "Forms" field Select a [SectionA] from the "Tabs" field Click [Show Tab] Locate a blank section of the form to create the bookmark for the new subsection Right click along the left edge of layout in the black shaded area Validate red stop sign shaped object displays and a grey section divider is created that is labeled "Sub-Section New" If desired click on the label and change the name of the subsection Drag field to the new subsection or move any existing fields already present in the subsection Validate the change is successful Holding the "Ctrl" key, click on the red stop sign symbol and move the section either up or down Validate the change is successful Click [Save] Click [Submit] Open [FormA] On the upper left side of the form click [SectionA] Validate under the name of [SectionA], the subsection created is displayed and name is as expected. Click on the subsection name Validate the user is taken directly to the new subsection Validate fields in that subsection are displayed as expected Close the form Open "Form Designer" Select [FormA] in the "Forms" field Select a [SectionA] from the "Tabs" field Click [Show Tab] Locate the new subsection added in step 1 Right-Click on the red stop sign icon and click "Delete" Validate the subsections is removed Click [Save] Click [Submit] Open [FormA] On the upper left side of the form click [SectionA] Validate under the name of [SectionA] the subsection added in step 1 is no longer present, Scenario 4: Site Specific Section Modeling Form - prompt and value validations Steps Open form "Site Specific Section Modeling". Select any form from the "Site Specific Section" drop down list. For example the "Progress Notes Group and Individual " form. Click [OK] to edit the form. Validate the "Site Specific Section Description" field is populated, as expected Validate the "Form Description" field is populate as expected Validate prompt 'Generate Bookmark for First Page of Section' is not present Validate prompt "Include Page Number Within Bookmark" is not present Validate the "Menu Location" field is populated with "Progress Notes" Select the "Prompt Definition" section In the "Prompt Definition" grid, select a prompt that contains a "Product" field. For example the "Select Client" prompt. Click [Delete Selected Item]. Validate message "Prompt cannot be deleted. To exclude this prompt, set "Exclude from Data Collection Instrument" to "Yes". Click [OK]. Validate the prompt is not removed from the "Prompt Definition" grid. Select a prompt that does not contain a "Product" field. For example, a "SS Note Integer" type field. Click [Delete Selected Item]. Validate message "Are Your Sure?" is displayed. Click [OK]. Validate the prompt is removed from the "Prompt Definition" grid. Click [Add New Item]. From the "Site Specific Field" drop down list, select a "Dictionary" type field that is not already in grid. Validate the prompt is added to the "Prompt Definition" grid. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is set to "No". Select the prompt just added. Click [Edit]. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is still set to "No". Select any other prompt in the "Prompt Definition" grid. Click [Edit]. Make a change to any of the field's property values. For example, the name of the prompt in the "Label" field. Validate the "Label" column for that prompt row in the "Prompt Definition" grid, reflects the new value. Click [Submit]. Validate the form files successfully.	Topics • Site Specific Section Modeling • NX • Progress Notes • Form Designer
Update 119.1 Summary \| Details Site Specific Section Modeling - Form 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) Form Designer (CWS) Scenario 1: (GA ASO) enabled "Progress Notes (Group and Individual)" forms - Validate "Site Specific Section Modeling" & "Import/Export" functionality Steps Internal Testing Only Scenario 2: "Create New Progress Note" form - Validate functionality in (GA-ASO) enabled environments Steps Internal Testing Only Scenario 3: Form Designer - Adding/Moving/Deleting Subsections(Bookmarks) Specific Setup: Have access to form "Form Designer" in any application Have a form [FormA] that can be used to make form designer changes that already contains one or more sections. For this example the "Progress Notes (Group & Individual)" form is used Steps Open "Form Designer" Select [FormA] in the "Forms" field Select a [SectionA] from the "Tabs" field Click [Show Tab] Locate a blank section of the form to create the bookmark for the new subsection Right click along the left edge of layout in the black shaded area Validate red stop sign shaped object displays and a grey section divider is created that is labeled "Sub-Section New" If desired click on the label and change the name of the subsection Drag field to the new subsection or move any existing fields already present in the subsection Validate the change is successful Holding the "Ctrl" key, click on the red stop sign symbol and move the section either up or down Validate the change is successful Click [Save] Click [Submit] Open [FormA] On the upper left side of the form click [SectionA] Validate under the name of [SectionA], the subsection created is displayed and name is as expected. Click on the subsection name Validate the user is taken directly to the new subsection Validate fields in that subsection are displayed as expected Close the form Open "Form Designer" Select [FormA] in the "Forms" field Select a [SectionA] from the "Tabs" field Click [Show Tab] Locate the new subsection added in step 1 Right-Click on the red stop sign icon and click "Delete" Validate the subsections is removed Click [Save] Click [Submit] Open [FormA] On the upper left side of the form click [SectionA] Validate under the name of [SectionA] the subsection added in step 1 is no longer present, Scenario 4: Site Specific Section Modeling Form - prompt and value validations Steps Open form "Site Specific Section Modeling". Select any form from the "Site Specific Section" drop down list. For example the "Progress Notes Group and Individual " form. Click [OK] to edit the form. Validate the "Site Specific Section Description" field is populated, as expected Validate the "Form Description" field is populate as expected Validate prompt 'Generate Bookmark for First Page of Section' is not present Validate prompt "Include Page Number Within Bookmark" is not present Validate the "Menu Location" field is populated with "Progress Notes" Select the "Prompt Definition" section In the "Prompt Definition" grid, select a prompt that contains a "Product" field. For example the "Select Client" prompt. Click [Delete Selected Item]. Validate message "Prompt cannot be deleted. To exclude this prompt, set "Exclude from Data Collection Instrument" to "Yes". Click [OK]. Validate the prompt is not removed from the "Prompt Definition" grid. Select a prompt that does not contain a "Product" field. For example, a "SS Note Integer" type field. Click [Delete Selected Item]. Validate message "Are Your Sure?" is displayed. Click [OK]. Validate the prompt is removed from the "Prompt Definition" grid. Click [Add New Item]. From the "Site Specific Field" drop down list, select a "Dictionary" type field that is not already in grid. Validate the prompt is added to the "Prompt Definition" grid. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is set to "No". Select the prompt just added. Click [Edit]. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is still set to "No". Select any other prompt in the "Prompt Definition" grid. Click [Edit]. Make a change to any of the field's property values. For example, the name of the prompt in the "Label" field. Validate the "Label" column for that prompt row in the "Prompt Definition" grid, reflects the new value. Click [Submit]. Validate the form files successfully.	Topics • Site Specific Section Modeling • NX • Form Designer
Update 120 Summary \| Details RADplus is enhanced to support future functionality. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Charge Input Program Maintenance Scenario 1: Validate the 'Time Zone Determination for UTC Service Entry' registry setting Steps Access the 'Registry Settings' form. Enter "Time Zone Determination for UTC Service Entry" in the 'Limit Registry Settings to the Following Search Criteria' field. Select "Yes" in the 'Include Hidden Registry Settings' field. Click [View Registry Settings]. Validate the 'Registry Setting' field contains: "RADplus->General->Facility->->->Time Zone Determination for UTC Service Entry". Validate the 'Registry Setting Details' field contains: "Define the priority order by which Time Zone should be assigned for populating the Service UTC time at time of filing a service record in a UTC enabled system. Enter the corresponding number(s) separated by an '&' to determine the time zone for Service Entry: 1:'User/User Role' 2:'Location' 3:'Program'. Example: '3&2' would define the priority to check the Program level for a Time Zone and if one is not configured then look at the associated Location for the Service Entry. If the Service is generated by an Appointment, the Appointment Site Time Zone will take precedence over this registry setting. If nothing is entered in this registry setting or the specified option(s) do not have a Time Zone defined, Service Record UTC values will not be stored. Enter the desired value(s) in the 'Registry Setting Value' field. Click [Submit]. Validate a message is displayed stating: "Successful filing". Click [OK] and close the form.	Topics • Registry Settings
Update 122 Summary \| Details My To Do's - Results to Review Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Review Results Results To Review - Review Results Scenario 1: Avatar NX - "Results to Review" To Do validations Specific Setup: A user is logged in and has the 'My To Do's' widget on their home view (User A). A client has a result (Result A) submitted in the 'Results Entry' form (Client A). In the 'Review Results' form, "Result A" has been submitted with field 'Send Results Notification To' set to "User A", to generate a "To Do". Steps Click to open the 'My To Do's' widget. In the 'Results to Review' field, locate the 'To Do' generated for "Client A". Click [Review Results]. Click the 'Client Reviewed' checkbox. Click [Save]. Click [Review Results] again. Validate 'Client Reviewed' checkbox is checked. Click the 'Client Reviewed' checkbox to uncheck it. Click [Save]. Click [Review Results] again. Validate 'Client Reviewed' checkbox is unchecked. Click the 'Client Reviewed' checkbox. Click [Marked Reviewed]. Populate the 'Notes' field if desired. Click [Save]. Validate the 'To Do' is removed from the 'Results to Review' field. 'All Documents' Widget Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Console Widget Viewer Scenario 1: Validate the 'Allow Users Access To All Forms on NX 'All Documents' Widget' registry setting Specific Setup: A client must be enrolled in an existing episode and has 'Progress Notes (Group and Individual)' and 'Treatment Plan' records on file (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 user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User A). Please note: this scenario is for Avatar NX systems. Steps Log in as "User A". Access the 'Registry Settings' form. Enter "allow users access to all" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Validate the "Allow Users Access To All Forms on NX 'All Documents' Widget" registry setting is present. Select the registry setting and click [OK]. Validate the 'Registry Setting Details' field contains "When set to 'Y', the user may view all forms on the Documentation View and 'All Documents' widget per the configuration of the 'All Documents' widget displayed, regardless of individual form access permissions configured in 'User Definition' or 'User Role Definition'. When set to 'N', the user's form access permissions will apply to the list of forms on the Documentation View, suppressing the forms to which the user does not have either read or read/write permission." Validate the 'Registry Setting Value' field contains "N". Click [Submit], [OK], and [No]. Select "Client A" and navigate to the 'All Documents' view. Select 'All Forms'. Validate "Progress Notes (Group and Individual)" and "Treatment Plan" and not present in the 'Form Description' field. Access the 'Registry Settings' form. Enter "allow users access to all" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select the "Allow Users Access To All Forms on NX 'All Documents' Widget" registry setting and click [OK]. Enter "Y" in the 'Registry Setting Value' field. Click [Submit]. Validate a 'Registry Editor Filing' dialog. Click [OK] and [No]. Navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Select 'All Forms'. Select "Progress Notes (Group and Individual)" in the 'Form Description' field. Select a progress note and validate the note displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are disabled. Click [Clear Filters]. Select "Treatment Plan" in the 'Form Description' field. Select a treatment plan and validate the plan displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are disabled. My To Do's - Reassign Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Approver Override HomeView - My To Do's widget Reassign To Do Item Review To Do Item TO DO'S Scenario 1: Validate the 'Allow Users to Reassign To Do List Items' registry setting Specific Setup: The 'Allow Users to Reassign To Do List Items' registry setting must be disabled. There must be two users: A user must have the 'My To Do's' widget configured on a view with various To Do's awaiting approval (User A). "User A" must be logged in. A user must have the 'My To Do's' widget configured on a view (User B). Various To Do's must include: Approve Document (To Do A) Review Results (To Do B) Review To Do Item (To Do C) Steps Navigate to the 'My To Do's' widget. Validate "To Do A", "To Do B", and "To Do C" display. Validate the 'Ellipsis' displays. Click this and validate 'Reassign To Do' is disabled. Select "Create Note to Self" from the menu. Validate a 'Note to Self' dialog and type any value in the 'Create a new note' field. Click [OK]. Verify the icon is a check box. Mouse over the icon and validate the note displays. Access the 'Registry Settings' form. Enter "allow users to reassign to do" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "Y" in the 'Registry Setting Value' field. Click [Submit]. Validate a 'Registry Editor Filing' dialog and click [OK], and [No]. Navigate to the 'My To Do's' widget. For "To Do A", click the 'Ellipsis' and select "Reassign To Do" from the menu. Validate a 'Continue?' dialog stating: "This to-do cannot be re-assigned with the "Reassign To-Do Item" form, continuing will open "Approver Override" and click [OK]. Validate the 'Approver Override' form displays. Click [Update Approvers]. In the 'Route Document To' dialog, deselect "User A" as an approver in the approver list. In the 'Add Approver' field search for "User B" and then click [Add] to add the user to approver list. Click [Submit]. Close the form. Validate "To Do A" no longer displays. For "To Do B", click the 'Ellipsis' and select "Reassign To Do" from the menu. Validate the 'Reassign To Do Item' form launches. Enter "User B" in the 'Select User to Reassign To Do Item to' field. Click [Submit]. Validate "To Do B" no longer displays. For "To Do C", click the 'Ellipsis' and select "Reassign To Do" from the menu. Validate the 'Reassign To Do Item' form launches. Enter "User B" in the 'Select User to Reassign To Do Item to' field. Click [Submit]. Validate "To Do B" no longer displays. Log out and log in as "User B". Navigate to the 'My To Do's' widget. Validate "To Do A", "To Do B", and "To Do C" display. Click [Review] for "To Do A". Validate the to do displays as expected in the 'Document Preview'. Click [Accept] and [Sign]. Enter the password and click [Verify]. Validate "To Do A" no longer displays. Click [Review Results] for "To Do B". Validate the results display as expected in the 'Results to Review'. Click the 'Client Reviewed' checkbox. Click [Mark Reviewed]. Enter any value in the 'Notes' field. Click [Save]. Validate "To Do B" no longer displays. Click [Review To Do Item] for "To Do C". Validate the 'Review To Do Item' form opens and displays as expected. Click [Reviewed] and [Submit]. Validate "To Do C" no longer displays. Close the To Do's.	Topics • NX • My To Do's • Registry Settings • All Documents Widget • ToDo's
Update 123 Summary \| Details Update - background processing Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Move Selected Data (CWS) Scenario 1: Move Selected Data - Table data validations Specific Setup: Have a progress note form [FormA], which is enabled for document routing. For example, the "Inpatient Progress Note" form [ClientA] is admitted in two episodes [Episode1] and [Episode2] [ClientA] has a row filed [RowA] in [FormA] in [Episode1], as "Final", with the document routing document routed and approved. [ClientA] has a row filed [RowB] in [FormA] in [Episode2] as "Draft" [ClentB] is admitted in [Episode1] Have a report or query created to display data in the "DocR.document" table [ReportA] Have a report or query created to display data in the "DocR.document_history" table [ReportB] Have [FormA] added to the logged in users "Chart View" Steps Run [ReportA], to display data in the "DocR.document" table Validate [RowA] is present for [ClientA] in [Episode1] Make a note of the "DocID". For example "789" Make a note of the value in "JOIN_TO_UNIQUE_ID" field. For example: "NOTxxxxx.001" Open form "Move Selected Data" Select [ClientA] in the "Entity Database" field Select [FormA] in the "Form" field Select [ClientA] in the "Old Entity" field Select [Episode1] in the "Old Episode" field Click [Select Row to be Moved] Select [RowA] Select [ClientA] in the "New Entity" field Select [Episode2] in the "New Episode" field Populate the "Reason for Moving Data" field Click [Submit] At the "Confirm Document" screen, click [Sign] Populate the "Verify Password" dialog and click [Verify] Validate the form files successfully Run [ReportA], to display data in the "DocR.document" table Validate [RowA] is present for [ClientA] in [Episode1], with the "DocID" noted in step 1 Make a note of the value in "JOIN_TO_UNIQUE_ID" field. For example: "NOTxxxxx.001" Validate the same value exists in the "JOIN_TO_UNIQUE_ID" field but has incremented by 1 after the decimal point. For example "NOTxxxxx.002". Run [ReportB], to display data in the "DocR.document_history" table Validate [RowA] is present for [ClientA] in [Episode1] Locate the "doc_id" field (Note: the value in "doc_id" contains several values separated by pipe (\|) symbols) Validate the field value contains the same value "JOIN_TO_UNIQUE_ID" value noted in step 3. For this example "NOTxxxxx.002". Select [ClientA] Right-click on the clients name to open the clients "Chart" On the left side panel, choose [FormA] Click the "Episode 1" tab in the main window Validate [RowA] is not present Click the "Episode 2" tab in the main window Validate [RowA] is displayed, as expected Open form "Move Selected Data" Select [ClientA] in the "Entity Database" field Select [FormA] in the "Form" field Select [ClientA] in the "Old Entity" field Select [Episode2] in the "Old Episode" field Click [Select Row to be Moved] Select [RowB] Select [ClientB] in the "New Entity" field Select [Episode1] in the "New Episode" field Populate the "Reason for Moving Data" field Validate the form files successfully Select [ClientA] Right-click on the clients name to open the clients "Chart" On the left side panel, choose [FormA] Click the "Episode 2" tab in the main window Validate [RowB] is not present Select [ClientB] Right-click on the clients name to open the clients "Chart" On the left side panel, choose [FormA] Click the "Episode 1" tab in the main window Validate [RowB] is present, as expected	Topics • Move Selected Data • NX
Update 125 Summary \| Details Form Designer - ScriptLink Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Form Designer (PM) Envelope Export (PM) Scenario 1: Envelope Import/Export - Validate "ScriptLink" script settings and functionality are retained Specific Setup: Have a "ScriptLink" script [ScriptA] created. [EnvelopeA] contains [FormA] [FormA] contains a "ScriptLink" script [ScriptA], imported into the form via "Form Designer" and is configured on [FieldA]. For example, the script that will trigger a test error message when the field is populated. Steps Open "Form Designer" Select [FormA] In the "Tab" field, select the section containing [FieldA] Navigate to [FieldA] and click in the field to highlight it On the left side panel under "General", validate the name in the "ScriptLink" field, contains [ScriptA] Click [Edit] Validate [ScriptA] is populated in the "Available Scripts" field and the "Script Parameter" field is populated (if applicable), as expected Click [Cancel] and exit the form Open form "Envelope Export" Select [EnvelopeA] In the "Include Form Design Changes" prompt, select "Yes" Click "Begin Export" Select a folder location to save the text file Populate a name for the file [ExportA] Click [Save] Close the form Open file "Envelope Import" Click "Select Envelope Import File" Navigate to the saved location of [ExportA] Select [ExportA] Click "Overwrite Existing" radio button Click the "Yes" radio button in the "Include Form Design Changes" field Click [Begin Import Scan] Click "Begin Import" Validate the "Import Complete" dialog is displayed Click [OK] Repeat step 1 Validate the script and script settings are still present, as expected Open [FormA] Navigate to [FieldA] and populate the field Validate the script is triggered and results are as expected Repeat step 3, this time selecting "No" in field "Include Form Design Changes" Repeat step 1 Validate the "ScriptLink" settings are still present and set in [FieldA], as expected Repeat step 5 Validate the script is still triggered and results are as expected	Topics • Form Designer • NX
Update 126 Summary \| Details Client Middle Name is expanded to 25 characters including spaces. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Chart View (Client Header) Scenario 1: Update Client Data - Validate client name allows spaces and client middle name displays up to 25 characters. Specific Setup: Avatar RADplus 2022 Update 126 is required for full functionality. Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form. Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms. Steps Open 'Update Client Data' form for an existing client. Set the 'Client Last Name' field to a last name which includes spaces in the name i.e.: 'FRANKLIN MILLER MOTT' Set the 'Client First Name' field to a first name which includes spaces in the name i.e: 'BENJAMIN WALLY' Set the 'Client Middle Name' field to a middle name which includes spaces and is maximum of 25 characters i.e: 'BILL ED MIDDLE NAME LONG' Click [Submit]. Right click on the client name in the 'Recent Clients' list. Select 'Display Chart'. Verify the name displays in the client banner, including all spaces and a maximum of 25 characters for the middle name. Close the client chart. Client name fields are enhanced to allow spaces in the names. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Scheduling Calendar - Appointment Grid Group Registration Chart View (Client Header) Scenario 1: Appointment Scheduling: Scheduling Calendar - support expanded client name field up to 100 characters and the name contains spaces. Specific Setup: A client (Client A) is admitted with a name where the first name, middle name, and last name combined is up to 100 characters. Access to Crystal Reports or other SQL reporting tool. Avatar PM 2022 Update 118 is required for full functionality. RADplus 2022 Update 126 is required for full functionality. Steps Open the 'Scheduling Calendar'. Click on any time slot. Right mouse and select 'Add Appointment'. Populate all required fields. Select 'Client A' in the 'Client' field. Validate that the client name displays all characters, up to 100. Submit the appointment. Validate that the client name displays the entire name in the time slot. Note: if the client name is not displayed, check the 'Show Name' box on the bottom left of the screen. Click 'Show MR#' box on the bottom left of the screen. Validate that the Client name as well as the MR# are displayed in the time slot. Right click on the appointment and select 'Check In'. Verify the entire client name displays in the 'Client' field. The user may need to scroll to the right to see the entire name. Click [View Client Data]. Verify the 'Client Name' displays the entire client name. Click [Submit]. Select one or more items from the 'Services to Check In' combo box. Click [Submit]. Right click on the appointment and select 'Check Out'. Validate that the client name displays the entire name in the time slot. Note: if the client name is not displayed, check the 'Show Name' box on the bottom left of the screen. Complete additional fields as needed. Click [Submit]. Open Crystal reports or other SQL Reporting tool. Create a report against SYSTEM.check_in_clients. Include, at a minimum, the following fields PATID patient_name data_entry_date Run the report for Client A. Verify the 'patient_name' field contains the entire client name, up to 100 characters. This field may need to be set to 'Can Grow' if using Crystal reports. Close the report. Open Crystal reports or other SQL Reporting tool. Create a report against SYSTEM.check_out_client_history. Include, at a minimum, the following fields PATID patient_name data_entry_date Run the report for Client A. Verify the 'patient_name' field contains the entire client name, up to 100 characters. This field may need to be set to 'Can Grow' if using Crystal reports. Close the report. Scenario 2: 'Group Registration' - support client names with up to 100 characters. Specific Setup: Avatar PM 2022 Update 118 and RADplus 2022 Update 126 are required for full functionality. Registry Setting 'Allow Spaces in Client Name' is set to 'Y'. Registry Setting 'Client Demographics - Additional Fields' include a value of '3' to add the client name detail fields. A client (Client A) has been admitted where the client name is greater than 40 characters, up to 100 characters. Steps Open 'Group Registration' form. Select any group in the 'Select Group' field. Click the group to be selected. Click [Select]. Click [Group Member Assignment]. Click [Add New Item]. Set the 'Client' field to Client A. Verify the 'Client' field is populated with the entire client name. The user may need to scroll to the right to view the entire name. Select any episode in the 'Episode Number' field. Set the 'Group Assignment Start Date' to any date. Click [Submit]. Using Crystal Reports or any reporting tool, create a report against SYSTEM.appt_group_member_data table. Include, at a minimum, the following fields: PATID patient_name group_name. Run the report for Client A. Verify the 'patient_name' field is populated with the full client name, up to 100 characters. The user may need to set the field to 'Can Grow' if using Crystal Reports. Close the report. Open 'Scheduling Calendar'. Add a group appointment for a group where Client A is a member. Click 'Group Members' section. Verify that Client A displays the full client name. This name may wrap to a second line in order to display all characters. Click [Submit]. Scenario 3: Admission - validate Registry setting 'Allow spaces in Client Name'. Specific Setup: Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form. Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms. Steps Open 'Admission (Outpatient)' form. Set the 'Last Name' on the 'Select Client' popup window to any name value. Set the 'First Name' on the 'Select Client' popup window to any name value. Select the gender in the 'Sex' drop down list. Click [Search]. Click [OK] on the 'Search Results' popup window: 'No matches found'. Click [New Client]. Click [Yes] on the 'Auto Assign Next ID Number' popup window. Click on the 'Demographics' section. Set the 'Client Last Name' to any name including one or more spaces. i.e.: 'Last Name'. Set the 'Client First Name' to any name including one or more spaces. i.e.: 'First Name' Set the 'Client Middle Name' to any name including one or more spaces. i.e.: 'Middle Name'. Complete any required fields. Click the 'Admission' section. Verify the 'Client Name' field contains the full name, including spaces. Click [Submit]. Right click on the client name in the 'Recent Clients' section. Click 'Display Chart'. Verify the client name displays all characters entered in the 'Admission' form. Note that the user may need to place the cursor over the client name and review the 'hover help' as it will display the client name. Scenario 4: Update Client Data - Validate client name allows spaces and client middle name displays up to 25 characters. Specific Setup: Avatar RADplus 2022 Update 126 is required for full functionality. Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form. Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms. Steps Open 'Update Client Data' form for an existing client. Set the 'Client Last Name' field to a last name which includes spaces in the name i.e.: 'FRANKLIN MILLER MOTT' Set the 'Client First Name' field to a first name which includes spaces in the name i.e: 'BENJAMIN WALLY' Set the 'Client Middle Name' field to a middle name which includes spaces and is maximum of 25 characters i.e: 'BILL ED MIDDLE NAME LONG' Click [Submit]. Right click on the client name in the 'Recent Clients' list. Select 'Display Chart'. Verify the name displays in the client banner, including all spaces and a maximum of 25 characters for the middle name. Close the client chart.	Topics • Registry Settings • Update Client Data • NX • Scheduling Calendar • Group Member Assignment • Group Appointment • Admission (Outpatient)
Update 127 Summary \| Details Envelope Import Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Modeled_Service_Doc_Form ModeledFormAlias ModeledFormAliasTwo Scenario 1: Envelope Import - Import scan results validation Specific Setup: Have an envelope [EnvelopeA] that contains one or more modeled forms which, in total, comprise a large amount of fields, sections, tables, and columns. Steps Open form "Envelope Import" Click [Select Envelope Import File] In Windows Explorer, navigate to the location of [EnvelopeA] Select the file Click [Save] Click [Create New] Click [Begin Import Scan] Validate the import scan is successful Click [Begin Import] Validate the envelope imports successfully Open a form contained in [EnvelopeA] Validate the form opens successfully Populate fields on the form Submit the form Validate the form files successfully Repeat step 2 for any other forms contained in [EnvelopeA] Validate results are as expected	Topics • Envelope Import
Update 130 Summary \| Details Export Crystal Report File - Avatar PM form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Export Crystal Report File (CWS) Export Crystal Report File (PM) Scenario 1: Validate the 'Export Crystal Report File' PM form Specific Setup: SAP Crystal Report Viewer must be installed. Steps Access the 'Export Crystal Report File' PM form. In the 'Report Type' field, select the "Command Button Report". Select any desired report in the 'Select Report' field [ReportA] (Note: A system may not have any reports for export). Click [Export Report]. In the "Save" dialog, click the "Save In" field and navigate to a desired folder location [FolderA], Click [Save]. Open "File Explorer" and navigate to [FolderA]. In the 'File Name' column, double click on [ReportA] to open the report. Validate the report opens successfully. Close the report. In the 'Report Type' field, select the "Disclosure Management Report". Repeat steps 2 and 3. Validate results are as expected. In the 'Report Type' field, select "Menu Report". Repeat steps 2 and 3. Validate results are as expected. In the 'Report Type' field, select "Document Routing Report". Repeat steps 2 and 3. Validate results are as expected. In the 'Report Type' field, select "Report Definition Report". Repeat steps 2 and 3. Validate results are as expected. In the 'Report Type' field, select "RADplus Report". Repeat steps 2 and 3. Validate results are as expected. Close the form.	Topics • RADplus Utilities • Report Viewer
Update 132 Summary \| Details Routing Admin Dashboard - GSI Size Limit Exceeded Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Routing Admin Dashboard Ambulatory Progress Notes Scenario 1: Routing Admin Dashboard - Search results validations Specific Setup: The system is set up for "Rule Based Routing" The system has over a "1000" documents filed in a single rule based routing queue.[QueueA] Steps Open a progress note form that is configured to work with Rule Based Routing. Create and finalize a progress note. Open the 'Routing Admin Dashboard' form. Select [QueueA] in the 'Queue' field and leave all other search criteria fields unpopulated. Click [Search]. Validate up to "1000" rows of data are displayed in the grid. (The system maximum number of rows that can be displayed in the grid). In the "Queue Search Criteria" section, use any of the search fields to narrow down the results, for example the "Select Programs" field. Click [Search]. Validate the results are displayed as expected based on the search criteria. Scenario 2: Routing Admin Dashboard - Re-Assign Specific Setup: The system is set up for Rule based routing. Steps Open a progress note form that is configured to work with Rule Based Routing. Create and finalize a progress note. Open the "Routing Admin Dashboard" form. Select a "Queue". Click "Search" button. Click the "Select" column on any row in the Results table. Click "Re-Assign" button. Select the desired row in the table. Click the "Direct Assignment" radio button in the "Assignment Type" field. Select the "New Queue" to be assigned to from the drop down. Set the "New Status" for the document to be assigned to. Set the "New User" the document is to be assigned to. Click "File" button. Validate the reassigned row is removed from the results table. Set the "Queue" to the queue the document was reassigned to. Click "Search" button. Validate the row that was reassigned is now showing up in the results table with changed data in the status and user columns. Click the "Exit Form" button. Scenario 3: Routing Admin Dashboard - Guidelines Definition Specific Setup: The system is set up for "Rule Based Routing" Steps Using the progress note form configured for Rule Based Routing, create and finalize a progress note. Open the "Routing Admin Dashboard" form. Enter any desired filters and click [Search]. Select a row in the "Results" table. Click [Guidelines Definition]. Add a row of data. Click [File]. Click [Guidelines Definition]. Validate form redisplays as it was entered. Click [Cancel]. Click [Exit Form].	Topics • Rule Based Routing • NX
Update 134 Summary \| Details Client Header 'Gender Identity' Display Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Lookup/Header Configuration Manager Scenario 1: Client Header - Verification of 'Gender Identity' Display (Avatar Cal-PM) Specific Setup: Avatar Cal-PM 2022 Update 80 must be installed for support of conditional Client Header 'Gender Identity' display 'Gender Identity' must be included in Client Header display fields (via 'Client Lookup/Header Configuration' Manager form) Client Demographic record(s) where 'Gender Identity' field contains value 'Additional gender category or other, please specify', and 'Gender Identity (Please Describe)' field value is defined Steps Open myAvatar/myAvatar NX Client Header display (via active client selection/chart view or Avatar client-based form). In Client Header display, ensure that 'Gender Identity' field is included (as specified in 'Client Lookup/Header Configuration' Manager form). Ensure that Client Header 'Gender Identity' field displays value from Client Demographic information for selected/active client. In case where 'Gender Identity' value in Client Demographic record for selected/active client is filed as 'Additional gender category or other, please specify', ensure that Client header 'Gender Identity' field displays value from 'Gender Identity (Please Describe)' field in Client Demographic information. Note - this conditional display of 'Gender Identity' value in Client Header is only supported in Avatar Cal-PM instances where Avatar Cal-PM 2022 Update 80 is also installed; Avatar PM instances will display 'Gender Identity' value regardless of value if included in Client Header. Ensure that updates to 'Gender Identity' and/or 'Gender Identity (Please Describe)' fields in Client Demographic information are accurately reflected in Client Header 'Gender Identity' field display.	Topics • Client Management • NX • Header Customization
Update 136 Summary \| Details Modeling - Single-Select Dictionary fields Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Table Definition (PM) Modeled Client Scenario 1: Modeling - Add additional fields to an existing modeled form Specific Setup: A client must be enrolled in an existing episode (Client A). A modeled form (Form A) must be defined using a table (Table A) Steps Access the 'Table Definition' form. Select "Table A". Select the "Column Definition" section. Click [Add New Item]. Enter the desired value in the 'Column Name' field. Enter the desired value in the 'Column Description' field. Select "Dictionary - Single Response" in the 'Type of Column' field. Select "Yes" in the 'Lock Dictionary Values' field. Click [Submit] and close the form. Access the 'Dictionary Update' form. Select "User Defined Client" in the 'File' field. Select the Data Element created in the previous steps. Enter the desired value in the 'Dictionary Code' field. Enter the desired value in the 'Dictionary Value' field. Click [Apply Changes] and close the form. Access the 'Form Definition' form. Select "Form A". Select the "Section Def." section. Select any desired section. Select the "Object Def." section. Click [Add New Item]. Select the table column added in the previous steps in the 'Table Column' field. Select "No" in the 'Default to Specific Value on Addition of a New Table Row' field. Click [Submit]. Select "Client A" and access "Form A". Validate the new single-select dictionary field is displayed with the dictionary value defined. Validate the dictionary value is NOT selected. Close the form.	Topics • Modeling
Update 143 Summary \| Details Registry Setting - form 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) Form Designer (CWS) Progress Notes (Group and Individual) Scenario 1: Registry Settings - submission of a registry setting Specific Setup: A client must be enrolled in an existing episode (Client A). A modeled form (Form A) must be defined using a table (Table A) Steps Access the 'Registry Settings' form. In the "Limit Registry Settings to the Following Search Criteria" field, enter any keyword to find a desired registry setting Click [View Registry Settings]. Validate the registry setting is displayed as expected and in a timely manner Note the current value of the setting and change it to a new value Click [Submit]. Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing. Click [OK] Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form? Click [Yes].to return to the form In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1 Validate the value changed in step 1b is present, as expected Click [Submit]. Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing. Click [OK] Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form? Click [Yes].to return to the form In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1 Validate the value submitted in step 2b is present, as expected Close the form	Topics • Registry Settings