RADplus 2022 Monthly Release 2022.03.00 Acceptance Tests

Last updated
Save as PDF

Update 24 Summary \| Details State Form Task Scheduler - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form Definition State Form Task Scheduler System Task Scheduler Scenario 1: System Task Scheduler - Validate a "State Form Definition" file task sent to an "FTP/SFTP" server Specific Setup: Have a state form definition file [DefA], created in form "State Form Definition" Have an "FTP Server" set up to receive files Have the following "FTP Server" information available in order to populate the "State Form Task Scheduler" form during testing: The "Service Directory" location The "Server Host Name" The "Server Port Number" The "Server Username" field The "Server Password" field The "Public Key File" and the folder location of the file The "Private Key File" and the folder location of the file Steps Open form "State Form Definition" Select [DefA] Populate the "File Path" field with directory that exists on the logged in users server; [LocationA] Submit the form Validate the form files successfully Open the 'State Form Task Scheduler' form Select [DefA] Select "Yes" in the "Create File" field Select "Yes" in "Send File To FTP Server" field In the "FTP Type" field, select "SFTP - Key Pair" Populate the "Server Host Name" field Populate the "Server Port Number" field Populate the "Server Username" field Populate the "Server Password" field Populate the "Service Directory" field, this is folder location [FTPfolderA] on the FTP server where the file will be sent Populate the "Public Key File Location" field Populate the "Private Key File Location" field Click [Test FTP Connection] Validate test is successful Submit the form Validate the form files successfully Open form "System Task Scheduler" Select the task set up for [DefA] in step 2 from the "Schedule(s)" field Populate the "Recurrence Pattern" field with desired value Populate the "Task Occurrence" field with the desired value Populate the "Start By" field with the desired date for the task to start Populate the "Start Time" field with the desired time for the task to start Select "No" in the "Inactive Task" field Click [Schedule Task] Close the form When the scheduled start by date and time for task filed in step 3 has passed: Validate the state form file [DefA] exist in the folder [LocationA] on the logged in users server, set in step1 Validate the state form file [DefA] exists in the folder [FTPfolderA] on the "FTP" server, set in step 2 State Form Task Files - ECP servers Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form Task Scheduler System Task Scheduler Scenario 1: System Task Scheduler - Validate "State Form Definition" file task when compiled on an ECP server Specific Setup: Have an environment that contains an Avatar "Database" server and also an "ECP" server configured by Netsmart with the database server as its "Remote" database server Have a state form definition file created in form "State Form Definition" [DefA] In form "State Form Definition", select [DefA] and note the definition ID# [IDNum], in parentheses next to the file name Have a report or query that can display data in the "SYSTEM.RADplus_sf_audit_record" table [ReportA] Steps Open form "State Form Definition" Select [DefA] Populate the "File Path" field with directory that exists on the users local server Submit the form Open the 'State Form Task Scheduler' form Select [DefA] Select "Yes" for Create File Populate any other required fields Submit the form Validate the form files successful pen form "System Task Scheduler" Select the task set up for [DefA] in step 2 from the "Schedule(s)" field Populate the "Recurrence Pattern" field with desired value Populate the "Task Occurrence" field with the desired value Populate the "Start By" field with the desired date for the task to start Populate the "Start Time" field with the desired time for the task to start Select "No" in the "Inactive Task" field Click [Schedule Task] Close the form When the scheduled date and time for task filed in step 2 has passed Run [ReportA] to display data in the "SYSTEM.RADplus_sf_audit_record" table Validate a row is present for the state form definition file, [DefA] Validate the "FileID" column is populated with definitions ID number [IDNum], noted in the setup Validate the "Server" field is populated with expected "FTP" server name, indicating that the file compiled on that server as expected State Form Definition Files - sub records Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form File Generation Scenario 1: Validate the output of a "State Form Definition" file containing multiple sub-records Specific Setup: Have an "XML" type "State Form Definition" file created that contains a main record and multiple sub-records. [Def1] Steps Open form "State Form File Generation" Select the [Def1] definition in field "State Form" In the "File Generation Options" field, select "Compile" Click [Process] Validate the process completes successfully In the "File Generation Options" field, select "Create File on Server" Click [Process] Click the "Compile Complete", [OK] button Click [Process] to create a file on the server In the "Windows Explorer" window, navigate to a folder location and save the file In the "Save In" drop down list of File Explorer, select a directory and populate the "File Name" Click [Save] In "File Explorer", go to the directory where the file was saved Click to open the file Validate the contents are as expected State Form File Generation - Compiles Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form File Generation Scenario 1: State Form File Generation - Validations Specific Setup: Have user [UserA] that has "Double Quotes" populated in the "User Description" field of their "User Definition" form record Have user [UserB] that has an "Apostrophe" populated in the "User Description" field of their "User Definition" form record Have user [UserC] that has any other special character populated in the "User Description" field of their "User Definition" form record Have user [UserD] that has no special characters in their name Have a "State Form Definition" file defined [DefinitionA], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "GROUP BY" command with the statement Log in as [UserA] Steps Open form "State Form File Generation". Select definition [DefinitionA] in field "State Form". Populate the "File Description" field. In the "File Generation Options" field, select "Compile". Click [Process]. Validate the process completes successfully. In the "File Generation Options" field, select "Dump File". Click [Process]. Validate the data output of the file is as expected Log out as [UserA] Log in as [UserB] Repeat step 1 Validate results are as expected Log out as [UserB] Log in as [UserC] Repeat step 1 Validate results are as expected	Topics • NX • State Form Task Scheduler • State Form Tools
Update 51 Summary \| Details Block Client Chart Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Block Client Chart Scenario 1: Block Client Chart - Emergency Access Specific Setup: Have a user role defined in form "User Role Definition" with prompt "User Role For Emergency Access Only" set to "Y". Have a user who is assigned to the emergency access role [UserA] Have a client that can be used to test the user's blocked client access. [ClientA] Prompt "Emergency Access" has been enabled in form "Emergency Access" Steps Open form "Block Client Chart" Click the "Blocked Clients" tab Click [Add New Item] In the "Select Client" field select [ClientA] In the "Allow Emergency Access for User/User Role", select "Yes" In the "Block Users" field, select "Yes-Selected" In the "Selected Users" field, select [UserA] Click [Submit] Validate the form files successfully Open the "Block Client Chart" form Click the List Blocked Clients button Validate [ClientA] is present on the report Click the Close Report button At the home view, search and select [ClientA] Validate the Block Client Dialog - Message text contains "[ClientA] chart is blocked." Click 'Cancel' Validate the user is returned to the client search prompt Select [ClientA] again Validate the Block Client Dialog - Message text contains "[ClientA] chart is blocked." is displayed again, as expected In the "Why are you accessing [ClientA]", text box, populate a reason Click [OK] Open any client based form, for example "Update Client Data" Validate the form opens Validate [ClientA] is displayed in the form Close the form	Topics • Block Client Chart
Update 65 Summary \| Details View Definition - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: View Definition Scenario 1: View Definition - Validate Addition of a Widget Specific Setup: Have a view defined in form "View Definition" [TestViewA] with one or more widgets assigned to the view Have two existing widgets [WidgetA] and [WidgetB] hat have the same widget name, that are not assigned yet to [TestViewA]. For this test: [WidgetA] is the Netsmart product widget "Financial Eligibility (NTST_FINANCIAL ELIG)" [WidgetB] is the console widget "Financial Eligibility [PATIENT500]". This widget can be created using the "Console Widget Configuration" form and selecting "Financial Eligibility [PATIENT500]" from the prompt "Form to Create Widget For" and then submitting the form [ClientA] has data filed in form "Financial Eligibility" Have two users [UserA] and [UserB] [UserA] has access to form "View Definition" [TestViewA] is assigned to a [UserB] as their home view Log in as [UserA] Steps Access the 'View Definition' form. Click [Select View]. Select [TestViewA] from the "Select Views" list box Click [OK]. Click [Launch View Designer] Validate [WidgetA] is present on the layout as expected In the "Available" widgets list, search for [WidgetA] Validate [WidgetA] is found and select the widget Click the right arrow icon to add it to the "Assigned" widget list Click and drag [WidgetA] to the layout section In the "Available" widgets list, search for [WidgetB] Validate [WidgetB] is found and select the widget Click the right arrow icon to add it to the "Assigned" widget list Click and drag [WidgetB] to the layout section Click [Submit] to return to exit the view designer and return to the main form and click [Submit]. Validate that a 'Form Return' message is displayed stating: "Submitting has completed. Do you wish to return to form?" Click [No]. Log out as [UserA] and login as [UserB] At the home view, click [Preferences] on the menu bar Select 'Widgets' from the tab selection. Click [Reload Home View]. Validate that a 'Confirm Reload' message appears stating: "Are you sure you want to discard current changes and reload layout from server?" Click [Yes]. Validate that [WidgetA] and [WidgetB] are no present on the view Click [Apply]. At the home view Validate that [WidgetA] and [WidgetB] are now present on the home view Select [ClientA] Validate data is displayed in the widget, as expected "SQL" table field name display Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Form Designer (PM) Form and Table Documentation (PM) Scenario 1: "Form Designer - Validate the "SQL Info" table information Specific Setup: Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information" Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined Have access to form "Form Designer" Steps Open form "Form Designer" Select the product form [FormA], from the "Forms" drop down list Select a section from the "Tabs" drop down list Click on [FieldA] in the form layout section. Click the "SQL Info" on the left side panel to display field and table name information Validate "Table Name" for the [TableA] reflects current SQL table name for example "SYSTEM.user_emergency_contact_information" Validate "Field Name" for the [FieldA] reflects current SQL table name, for example "Emergency_contact_name" Close the form Open form "Form Designer" Select the modeled form [FormB] from the "Forms" drop down list Select a section from the "Tabs" drop down list Click on [FieldB] in the form layout section. Click the "SQL Info" on the left side panel to display field and table name information Validate "Table Name" for the [TableB] reflects current SQL table name for example "SYSTEM.modeled_form" Validate "Field Name" for the [FieldB] reflects current SQL table name, for example "Clients_full_name" Close the form Scenario 2: "Form and Table Documentation" - validate SQL table field names Specific Setup: Have a product form [FormA] that contains an SQL Table [TableA] with one or more fields defined in the table. For example product form "Emergency Contact Information" containing table "SYSTEM.user_emergency_contact_information" Have a modeled form [FormB] that contains an SQL Table [TableB] with one or more fields defined Steps Open 'Form and Table Documentation'. Set 'Type of Documentation' to 'Form'. Select "Individual" in the "Individual or All Forms" field Select [FormA] from the 'Form to be Documented' field Click [Process] Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected Click the "Page" field and go to the last page of the report Validate all field names and their associated SQL table names are listed, as expected Click [Close] Set 'Type of Documentation' to 'Form'. Locate and select [TableA] in field "Table(s) to be Documented" Click [Process] Validate the "Form and Table Documentation" report, displays all field names and their associated SQL table names, as expected Click [Close] Repeat step 1 for modeled [FormB] and [TableB] Validate results are as expected Display User Role - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: User Role Definition Display User Role Display User Role (Report) Scenario 1: Display User Role - Include "Deactivated" Roles - Yes Specific Setup: Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA] Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA] Steps Open form "Display User Role" Select "All" in the Individual or All User Roles" field Set field "Include Deactivated User Roles" to "Yes" Click [Process] Validate the "Display User Role" report is displayed Search for the active ole [ActiveRoleA] Validate the role is found Search for the deactivated role [DeactiveRoleA] Validate the role is found, as expected Close the report Select "Individual" in the Individual or All User Roles" field Click the "User Role" field Validate the drop down list contains [ActiveRoleA] Validate the drop down list also contains [DeactiveRoleA], as expected Scenario 2: Display User Role - Include "Deactivated" Roles - No Specific Setup: Have a role defined in form "User Role Definition" with field "Deactivated" set to "No" [ActiveRoleA] Have a role defined in form "User Role Definition" with field "Deactivated" set to "Yes" [DeactiveRoleA] Steps Open form "Display User Role" Select "All" in the Individual or All User Roles" field Set field "Include Deactivated User Roles" to "No" Click [Process] Validate the "Display User Role" report is displayed Search for the "Active" role [ActiveRoleA] Validate the role is found Search for the "Active" role [DeactiveRoleA] Validate the role is not found, as expected Close the report Select "Individual" in the Individual or All User Roles" field Click the "User Role" field Validate the drop down list contains [ActiveRoleA] Validate the drop down list does not contain [DeactiveRoleA], as expected Client Triggers - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Triggers (PM) Dynamic Form - Client Alert - Client Scenario 1: Client Triggers (Form) - Field Validations Specific Setup: Have an "Alert" defined in form "Client Alerts" [AlertA] Steps Open form "Client Triggers" Select [TableA] in the "Table" field Click to the "Table Based Triggers" section Click to "Add New Item" Select [AlertA] in the "Client Alert Type" field Select the desired value from the "Trigger On" field Select a value if desired from the "Offset Trigger Based On The Following Date Field" Populate the "Number of Days Alert Should be Active" field Populate the "Days Before/After Date Field to Offset Trigger" field Click to the "Field Based Triggers" section and Click to "Add New Item" Select [AlertA] in the "Client Alert Type" field Select the desired value in the "Trigger Alert for All Episodes" field Populate the "Number of Days Alert Should be Active" field Click the "Field" prompt Validate all the expected field valued for [TableA] are listed for selection Select a desired value Select the desired value in the "Type of Comparison" field Populate the "Comparison Value" field with the desired value Select a value if desired from the "Offset Trigger Based On The Following Date Field" Populate the "Days Before/After Date Field to Offset Trigger" field Submit the form Return to form "Client Triggers" Select [TableA] in the "Table" field Click to the "Table Based Triggers" section Validate all fields are populated as expected based on the value filed in step 1 Click to the "Field Based Triggers" section Validate all fields are populated as expected based on the value filed in step 1	Topics • Console Widget • Form Designer • Forms • NX • User Role Definition • My Clients
Update 79 Summary \| Details Notify Attending Practitioner Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Home Medications Scenario 1: OE NX - Home Medication - Notify Attending Practitioner Specific Setup: Avatar OE 2022 Update 47, RADplus 2022 Update 79, and Avatar NX Release 2022.09.00 are required in order to utilize full functionality. The 'Avatar Order Entry->Facility Defaults->Medication Reconciliation->->->Prevent Admission Med Reconciliation if med history not completed on Home Meds' registry setting must be set to "Y". The 'Default to Client Reported in Home Medications' field in the 'Order Entry User Definition' form or the 'Order Entry User Role' form must have "Client Reported" checked. Please log out of the application and log back in after completing the above configuration. A pharmacy type order code must exist. (Order Code A) A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Make note of the 'Attending Practitioner' associated with "Client A". Steps Select "Client A" and access the Order Entry Console. Select the 'Home Medications' tab. Create an order for "Order Code A". Populate all required fields and click [Save]. Validate the 'Order grid' contains an order for "Order Code A". Check the 'Medication history reviewed and completed for Episode #' checkbox. Click [Notify Attending Practitioner]. Validate the 'Notify Attending Practitioner' dialog is displayed. Validate "Client A" and the episode number is displayed. Validate the 'Practitioner' field contains the 'Attending Practitioner'. Validate the 'Communication Note' field contains "Medication history complete for "Client A" Episode # [Episode Number] - Please complete Admission Med Reconciliation." Set the 'Communication Note' field to "Medication history complete for "Client A" Episode # [Episode Number] - Please complete Admission Med Reconciliation. Testing" Click [Send Notification]. Access the 'Home View'. Access the 'To do's' and select 'Days in Queue' from the 'To do's' sort by field. Validate "Client A" is displayed at the top for the current date. Click 'Review To Do Item'. Validate the 'To do information' field contains "Medication history complete for "Client A" Episode # [Episode Number] - Please complete Admission Med Reconciliation. Testing". Check the 'Reviewed' checkbox. Click [Submit].	Topics • NX • Order Entry Console
Update 89 Summary \| Details Compliance Rule - Notifications Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Compliance Rule Definition (CWS) Compliance Rule Definition (PM) Scenario 1: Compliance Rule Definition - Validate 'Team to Send Notification To Do' functionality Specific Setup: Have two users who are practitioners, [StaffA] and [StaffB] [TeamA] has been created in form "Team Definition" and both [StaffA] and [StaffB] have been assigned to the team In form "Compliance Rule Definition" : Create a rule that will set a client out of compliance if a diagnosis has not been submitted for the client, within five days after their admission date In field "Team To Send Notification To", have [TeamA] selected, which will send a To Do to staff members on the team when a client is out of compliance Have a client [ClientA] who already has had a diagnosis filed within five days after of their admission date Have a client [ClientB] who has not had a diagnosis filed within five days after of their admission date [StaffA] and [StaffB] have both clients on their caseload [StaffA] and [StaffB] have the "My Clients" and the "My To Do's" widgets on their home view Log in as [StaffA] Steps At the home view Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup Click to refresh the "My To Do's" widget Validate the To Do list for [StaffA] does not contain a To Do compliance notification for [ClientA], as expected Validate the To Do list for [StaffA] does contains a To Do compliance notification for [ClientB] Click [Review To Do Item] Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA] notification has been received. Click the "Reviewed" check box Click [Submit] Validate the submission is successful and the To Do is removed from the To Do's list Log out as [StaffA] Log in as [StaffB] At the home view Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup Click to refresh the "My To Do's" widget Validate the To Do list for [StaffB] does not contain a To Do compliance notification for [ClientA] Validate the To Do list for [StaffB] does contains a To Do compliance notification for [ClientB] Click [Review To Do Item] Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA] notification has been received. Click the "Reviewed" check box Click [Submit] Validate the submission is successful and the To Do is removed from the To Do's list Scenario 2: Compliance Rule Definition - Validate 'Team to Send Notification To Do' filtered by 'Provider Categories for Coverage' Specific Setup: Have two users who are practitioners, [StaffA] and [StaffB] In form "Practitioner Enrollment", [StaffA] has [CatagoryA] selected in the 'Practitioner Categories for Coverage Filter' field In form "Practitioner Enrollment", [StaffB] does not have [CatagoryA] selected in the "Practitioner Categories for Coverage Filter" field [TeamA] has been created in form "Team Definition" and both staff members have been assigned to the team In form "Compliance Rule Definition" : Create a rule that will set a client out of compliance if a diagnosis has not been submitted for the client, within five days after their admission date In field "Team To Send Notification To", have [TeamA] selected, which will send a To Do to staff members on the team when a client is out of compliance In the field "Notification Provider Categories for Coverage Filter" select [CategoryA]. [Please Note: This field has been renamed from 'Notification Practitioner Category Filter', in order to accurately reflect the contents of the field] Have a client [ClientA] who already has had a diagnosis filed within five days of their admission date Have a client [ClientB] who has not had a diagnosis filed within five days after of their admission date [StaffA] and [StaffB] have both clients on their caseload [StaffA] and [StaffB] have the "My Clients" and the "My To Do's" widgets on their home view Log in as [StaffA] Steps At the home view Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup Click to refresh the "My To Do's" widget Validate the To Do list for [StaffA] does not contain a To Do notification for [ClientA], as expected Validate the To Do list for [StaffA] does contains a compliance To Do for [ClientB] Click [Review To Do Item] Validate the "To Do Information" field indicates "A COMPLIANCE: [RuleA]" notification has been received. Click the "Reviewed" check box Click [Submit] Validate the submission is successful and the To Do is removed from the To Do's list Log out as [StaffA] Log in as [StaffB] At the home view Validate the "My Clients" widget contains [ClientA] with a "Black" arrow next to their name as expected, indicating the client is in compliance with [RuleA] configured in the setup Validate the "My Clients" widget contains [ClientB] with a "Red" arrow next to their name as expected, indicating the client is 'not' in compliance with [RuleA] configured in the setup Click to refresh the "My To Do's" widget Validate there is no compliance To Do present for either [ClientA] or [ClientB] as expected, since [StaffB] does not have [CatagoryA] selected in the "Practitioner Categories for Coverage Filter" field of form "Practitioner Enrollment"	Topics • My To Do's • NX • Practitioner • Team Definition
Update 91 Summary \| Details Document Routing -'Default From Last Filing Scenario 1: Document Routing - Default Notification User from Last Filing Specific Setup: Have a form [FormA] set up in form "Document Routing Setup" with following prompts set: 'Enable Document Routing' se to 'Yes'. 'Allow Notifications When Final' set to 'Yes'. 'Notification List Defaults' set to 'Default From List Filing' [UserA] has access to [FormA] [UserB] is a Staff member and has the "My To Do's" widget on their home view Log in as [UserA] Steps Access [FormA] and select any client [ClientA] Populate all desired fields on the form. Select "Final" in the 'Draft/Final' field. Click [Accept and Route/Notify] Enter the user's password in the 'Password' field. Click [OK]. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box Search for User. [UserB], Click [Add] to have [UserB] receive a To do notification Validate that [UserB] is added and the "Notify' check box is populated Click [Submit] Validate the form files successfully Repeat step 1 a thru e On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box Validate the [UserB] is automatically added to the approver list and the "Notify" check box is populated Click [Submit] Validate the form files successfully Log in as [UserB] Navigate to the "My To Do's" widget Click to refresh the widget Click the "New" tab Validate there are two new To Do's in the list for [ClientA], for [FormA] Click to open each To Do Validate the "To Do Information" box contains the expected data Click the "Reviewed" check box Click [Submit] Validate submission is successful and each To Do has been removed form the To Do's list Document Routing - 'Create Document Only' Scenario 1: Document Routing - 'Create Document Only' - Yes with 'Skip Display of Document Image' - Yes Specific Setup: Have a form enabled for "Document Routing" [FormA] In form "Document Routing Setup", have prompt "Create Document Only" set to "Yes" for [FormA] In "Document Routing Setup", have 'Skip Display Of Image' set to "Yes" for [FormA] The 'My To Do's' widget is on the user's home screen Have a client [ClientA] enrolled in an active episode [EpisodeA] Steps Open [FormA] Select [ClientA] Select [EpisodeA] Complete the desired fields Set the "Draft/Final" prompt to "Final" Click [Submit] Validate no document image or route to document screen(s) are displayed Validate a quick "Confirm Document", "Saving Image Data" screen displays and the form files successfully Navigate to form "Clinical Document Viewer" In the "Search Clients" field, select [ClientA] Select [EpisodeA] in the "Episodes" field Click [Process] In the document "Results" list, validate there is a document row present for [ClientA] for the submission of [FormA] in step 1 Double-click the row to view the document Validate the data is displayed as expected Scenario 2: Document Routing - 'Create Document Only' - Yes with 'Skip Display of Document Image' - No Specific Setup: Have a form enabled for "Document Routing" [FormA] In form "Document Routing Setup", have prompt "Create Document Only"' set to "Yes" for [FormA] In "Document Routing Setup", have 'Skip Display Of Image' set to "No" for [FormA] The 'My To Do's' widget is on the user's home screen Have a client [ClientA] enrolled in an active episode [EpisodeA] Steps Open [FormA] Select [ClientA] Select [EpisodeA] Complete the desired fields Set the "Draft/Final" prompt to "Final" Click [Submit] At the "Confirm Document" screen, validate the document is displayed as expected Click [Accept] At the "Verify Password" prompt, populate the "Password" field Click [OK] Validate the user is not presented with the "Route To Document" screen, as expected Validate the form submits successfully Navigate to form "Clinical Document Viewer" In the "Search Clients" field, select [ClientA] Select [EpisodeA] in the "Episodes" field Click [Process] In the document "Results" list, validate there is a document row present for [ClientA] for the submission of [FormA] in step 1 Double-click the row to view the document Validate the data is displayed as expected Document Routing - Co-signer Scenario 1: Progress Notes (Document Routing) requiring co-signer - 'Create Document Only' - No with 'Skip Display of Document Image' - Yes Specific Setup: Have a progress note form [FormA] enabled for "Document Routing" In form "Document Routing Setup": Have prompt 'Skip Display Of Image' set to "No" for [FormA] Have prompt "Create Document Only" set to "No" for [FormA] Have a 'Note Type' requiring a co-signature defined on the system [NotetypeA] Have a client [ClientA] enrolled in an active episode [EpisodeA] [UserA] has access to [FormA] [UserB] is a staff member and has the "My To Do's" widget on their home view Log in as [UserA] Steps Open [FormA] Select [ClientA] Select [EpisodeA] Complete the progress note, selecting [NotetypeA], which requires a co-signer Set the "Draft/Final" prompt to "Final" Click [Submit] At the "Route To Document" screen Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer In the 'Add Approver' field, select [UserB] Validate the [Submit] button is now enabled Click [Cancel] Validate user is returned to [FormA] and form is set to "Final" Click [Submit] At the "Route To Document" screen Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer In the 'Add Approver' field, select [UserB] Validate the [Submit] button is now enabled Click [Submit] Validate the form submits successfully Log out as [UserA] and log in as [UserB] Navigate to the 'My To Do's' widget Locate the To Do routed in step 1 for [FormA] Click 'Approve Document' Validate the document is displayed as expected Click [Sign] Enter the user's password Click [OK] Validate the To Do is removed from the 'My To Do's' widget Scenario 2: Progress Notes (Document Routing) requiring co-signer - 'Create Document Only' - No with 'Skip Display of Document Image' - No Specific Setup: Have a progress note form [FormA] enabled for "Document Routing" In form "Document Routing Setup": Have prompt 'Skip Display Of Image' set to "No" for [FormA] Have prompt "Create Document Only" set to "No" for [FormA] Have a 'Note Type' requiring a co-signature defined on the system [NotetypeA] Have a client [ClientA] enrolled in an active episode [EpisodeA] [UserA] has access to [FormA] [UserB] is a staff member and has the "My To Do's" widget on their home view Log in as [UserA] Steps Open [FormA] Select [ClientA] Select [EpisodeA] Complete the progress note, selecting [NotetypeA], which requires a co-signer Set the "Draft/Final" prompt to "Final" Click [Submit] At the "Confirm Document" screen, validate the document is displayed as expected Click [Accept/Route] At the "Verify Password" prompt, populate the "Password" field Click [OK] At the "Route To Document" screen Validate the [Submit] button is not enabled, as expected since [FormA] requires a co-signer In the 'Add Approver' field, select [UserB] Validate the [Submit] button is now enabled Click [Cancel] Validate user is returned to "Confirm Document" screen Click [Accept/Route] At the "Verify Password" prompt, populate the "Password" field Click [OK] At the "Route To Document" screen Validate the [Submit] button is not enabled again as expected, since [FormA] requires a co-signer In the 'Add Approver' field, select [UserB] Validate the [Submit] button is now enabled Click [Submit] Validate the form submits successfully Log out as [UserA] and log in as [UserB] Navigate to the 'My To Do's' widget Locate the To Do routed in step 1 for [FormA] Click 'Approve Document' Validate the document is displayed as expected Click [Sign] Enter the user's password Click [OK] Validate the To Do is removed from the 'My To Do's' widget	Topics • Document Routing • NX
Update 104 Summary \| Details Team Definition - Team Finalizer Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Team Definition Crystal Reports or other SQL Reporting tool (ReportA) Scenario 1: Team Definition - "SYSTEM.radplus_teams" table field and widget data validation Specific Setup: Have two users who are staff members. [UserA] and [UserB] [UserA] has a UserID that includes a period, for example "John.Smith" and a user description [DescriptionA] [UserB] has a UserID that does not include a period and a user description [DescriptionB] Have a widget [WidgetA] that displays data in the "SYSTEM_RADplus_teams" table, and includes the "team_finalizer_userID" and "team_finalizer_user_desc" columns in its data output Have two teams set up in form "Team Definition", [TeamA] and [TeamB] Both teams have [UserA] and [UserB] added to the teams as user's Have a report [ReportA] to display data in the "SYSTEM_RADplus_teams" table that includes the "team_finalizer_userID" and "team_finalizer_user_desc" columns in its data output [UserC] has access to "Team Definition" and has [WidgetA] on their home view Log in as [UserC] Steps Open form "Team Definition" Select [TeamA] Click the "Team Finalizer" field Validate both [UserA] and [UserB] are present Select [UserA] Submit the form Validate submission is successful Return to the form Select [TeamA] Validate the "Team Finalizer" field is populated with [UserA] [DecriptionA] Exit the form Select [TeamB] Click the "Team Finalizer" field Validate both [UserA] and [UserB] are present Select [UserB] Submit the form Validate submission is successful Return to the form Select [TeamB] Validate the "Team Finalizer" field is populate with [UserB] [DescriptionB] Exit the form At the home view, click the refresh button in [WidgetA] Locate the row for [TeamA] Validate the UserID for [UserA] is displayed in the "team_finalizer_userID" column, as expected and includes the period in ID Validate [DescriptionA] is displayed in the "team_finalizer_user_desc column", as expected Locate the row for [TeamB] Validate the UserID for [UserB] is displayed in the "team_finalizer_userID" column, as expected Validate [DescriptionB] is displayed in the "team_finalizer_user_desc" column, as expected Launch [ReportA] Click to preview the report Locate the row for [TeamA] Validate the UserID for [UserA] is displayed in the "team_finalizer_userID" column, as expected and includes the period in ID Validate [DescriptionA] is displayed in the "team_finalizer_user_desc column", as expected Locate the row for [TeamB] Validate the UserID for [UserB] is displayed in the "team_finalizer_userID" column, as expected Validate [DescriptionB] is displayed in the "team_finalizer_user_desc" column, as expected	Topics • NX • Team Definition
Update 107 Summary \| Details Widgets Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Diagnosis Treatment Plan All Documents Widget Scenario 1: 'Progress Notes (Group and Individual)' - File a progress note that includes signatures with document routing enabled Specific Setup: Document routing must be enabled on the 'Progress Notes (Group and Individual)' form. The 'Progress Notes (Group and Individual)' form must have a signature field (SS Signature Pad 2). This can be done in the 'Site Specific Section Modeling' form. A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Select "Episode 1" in the 'Select Episode' field. Select "New Service" in the 'Progress Notes For' field. Select any value in the 'Note Type' field. Enter any value in the 'Notes Field' field. Enter any value in the 'Date Of Service' field. Enter any value in the 'Service Charge Code' field. Click [Sign] in the 'SS Signature Pad 2' signature field. Validate the 'Please Sign' dialog is displayed and sign in it. Click [OK]. Validate the signature displays as expected. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate a "Progress Notes" document is displayed. Click [Sign]. Validate the 'Verify Password' dialog is displayed and enter the password associated to the logged in user. Click [OK]. Validate a "Progress Notes" message is displayed stating: Note Filed. Click [OK] and close the form. Scenario 2: Avatar NX - Views configured with associated views and workflow items Specific Setup: A client must be admitted to an existing episode and have a 'Review To Do Item' routed to the logged in user. (Client A). User's 'myDay' view must have an associated view that contains CC Inbox POV (View A). User's 'myDay' view must have an associated view that contains Medical Note POV and the 'My To-Do's' widget (View B). User's 'myDay' view must have several associated views that do not contain POV's (View C). "View C" must have a workflow item that contains a POV (Item A) and a workflow item that does not contain a POV (Item B). User's 'myDay' view must have an associated view that contains the 'Client Acuity', 'Client's Care Team', and 'Rule Based Routing' widgets (View D). Document routing must be enabled for the 'Progress Notes (Group & Individual)' form. A client must be admitted to an existing episode (Client A). Please note: this scenario is for Avatar NX systems. Steps Select "Client A" and select "View A". Validate the view opens and displays as expected. Select "View B". Validate the view opens and displays as expected. Open the 'My To-Do's' widget. Click [Review To Do Item]. Validate the form displays as expected. Click [Discard]. Validate user is taken back to the 'My To-Do's'. Switch between "View A" and "View B" a dozen times and then select the 'View Menu'. Validate the 'View Menu' opens and displays as expected. Close the 'View Menu'. Select "View C". Validate the view opens and displays as expected. Select "Item A" and validate the workflow item opens and displays as expected. Select "Item B" and validate the workflow item opens and displays as expected. Continue selecting the desired views and workflow items and validate they open and display as expected. Access the 'Progress Notes' (Group and Individual)' form. Select "View A". Validate the view displays as expected and the 'Progress Notes (Group and Individual)' form tab is present. Scroll down and validate the form tab is anchored to the top of the page. Select the form tab. Validate the 'Progress Notes (Group and Individual)' form displays as expected. Select "View C". Validate the view displays as expected and the 'Progress Notes (Group and Individual)' form tab is present. Scroll down and validate the form tab is anchored to the top of the page. Select the form tab. Validate the 'Progress Notes (Group and Individual)' form displays as expected. Select "View D". Validate the view displays as expected and the 'Progress Notes (Group and Individual)' form tab is present. Scroll down and validate the form tab is anchored to the top of the page. Access the 'Diagnosis' form. Click [Add]. Validate the 'Diagnosis' form opens and displays as expected and the 'Progress Notes (Group and Individual)' form tab is present. Select the 'Progress Notes (Group and Individual)' form tab. Validate the 'Progress Notes (Group and Individual)' form displays as expected. Select "myDay". Validate the view displays as expected and the 'Progress Notes (Group and Individual)' form tab is present. Scroll down and validate the form tab is anchored to the top of the page. Select the 'Progress Notes (Group and Individual)' form tab. Validate the 'Progress Notes (Group and Individual)' form displays as expected. Populate the desired and required fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate a 'Confirm Document' dialog containing the note and click [Sign]. Enter the password of the logged in user and click [Verify]. Validate a 'Progress Notes' dialog stating "Note filed." and click [OK]. Close the form. Select the 'Diagnosis' form tab. Validate the 'Diagnosis' form displays as expected. Close the form. Validate the user is taken back to the "myDay" view. Access the desired form. Validate the form displays as expected. Continue opening and closing the desired forms. Validate they display and close as expected. Scenario 3: 'All Documents' Widget - validate filtering when navigating between views Specific Setup: Must have a view that contains the 'All Documents' widget ('All Documents' View). A client with documents and/or data filed in various forms (ex. 'Vitals Entry', 'Problem List', 'Diagnosis', 'Progress Notes (Group and Individual)') (Client A). Please note: this scenario is for Avatar NX systems. Steps Select "Client A" and navigate to the 'All Documents' view. Select any value in the 'Form Description' field. Validate the filter works as expected. Navigate to the another view and back to the 'All Documents' view. Validate the filter is retained. Deselect the value in the 'Form Description' field. Validate the 'Form Description' field contains "ALL". Click [Clear Filters]. Select any value in the 'Form Description' field. Validate the filter works as expected. Navigate to the another view and back to the 'All Documents' view. Validate the filter is retained. Select another value from the 'Form Description' field. Validate the filters work as expected. Click [Clear Filters]. Select any value in the 'Date' field. Validate the filter works as expected. Navigate to the another view and back to the 'All Documents' view. Validate the same records are displayed. Deselect the value in the 'Date' field. Validate the 'Date' field contains "ALL". Click [Clear Filters]. Scenario 4: 'All Documents' widget - Validate user access levels Specific Setup: A client must be enrolled in an existing episode (Client A). There must be three users: A user who has full access to forms and is logged in (User A) A user who has read-only access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User B). A user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User C). 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). Document routing must be enabled for the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms. The 'Allow Users Access To All Forms on NX 'All Documents' Widget' registry setting must be set to "N". Please note: this scenario is for Avatar NX systems. Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Select any value in the 'Progress Note For' field. Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign]. Enter the password associated with the logged in user and click [Verify]. Close the form. Navigate to the 'All Documents' view. Select 'All Forms'. Select "Progress Notes (Group and Individual)" in the 'Form Description' field. Validate the time and staff credentials display. Validate the progress note from the previous steps is present and select it. Validate the note displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are enabled. Access the 'Treatment Plan' form. Enter the desired date in the 'Plan Date' field. Populate all required and desired fields. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Populate all required and desired fields. Click [Return to Plan] and [OK]. Select "Final" in the 'Treatment Plan Status' field. Click [Submit]. Validate a 'Confirm Document' dialog displays the progress note from the previous steps and click [Sign]. Enter the password associated with the logged in user and click [Verify]. Navigate to the 'All Documents' view. Select 'All Forms'. Select "Treatment Plan" in the 'Form Description' field. Validate the treatment plan from the previous steps is present and select it. Validate the plan displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are enabled. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays with the information filed in the previous steps. Close the report. Log out. Login as "User B". Select "Client A" and navigate to the 'All Documents' view. Select 'All Forms'. Select "Progress Notes (Group and Individual)" in the 'Form Description' field. Validate the progress note from the previous steps is present and select it. Validate the note displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are disabled. Select "Treatment Plan" in the 'Form Description' field. Validate the treatment plan from the previous steps is present and select it. Validate the plan displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are disabled. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays with the information filed in the previous steps. Close the report. Log out. Login as "User C". Select "Client A" and navigate to the 'All Documents' view. 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 "Allow Users Access to All Forms on NX 'All Documents' Widget Registry Setting" from the 'Registry Settings' field. 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. Validate the progress note from the previous steps is present and select it. 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. Validate the treatment plan from the previous steps is present and select it. Validate the plan displays in the 'Console Widget Viewer'. Validate the 'Open' and 'Open Record' buttons are disabled. Scenario 5: Clinical Document Viewer - Validate user access levels Specific Setup: A client has finalized documents for 'Progress Notes (Group and Individual)' (Client A). There must be two users: A user who has full access to forms and is logged in (User A). A user who doesn't have access to the 'Progress Notes (Group and Individual)' form (User B). Steps Access the 'Clinical Document Viewer' form. Select "Individual" in the 'Select All or Individual Client' field. Enter "Client A" in the 'Select Client' field. Select "All" in the 'Episode' field. Click [Process]. Select the desired document in the 'Search Results' field. Click to view the document. Validate document data is displayed. Click [Close All Documents]. Navigate back to the "Search" section. Click [Close]. Log out. Log in as "User B". Access the 'Clinical Document Viewer' form. Select "Individual" in the 'Select All or Individual Client' field. Enter "Client A" in the 'Select Client' field. Select "All" in the 'Episode' field. Click [Process]. Validate the desired document has a lock next to it in the 'Search Results' field. Validate the user is unable to select and view the document. Navigate back to the "Search" section. Click [Close]. Scenario 6: 'All Documents' Widget - Validate filtering when switching between clients Specific Setup: A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view). Two clients are admitted into two active episodes with documents on file in the 'All Documents' Widget. The 'Default Value for Console View Episodes Registry Setting' must be set to "1". Steps Select "Client A" and navigate to the 'All Documents' view. Validate the 'Episode Header' field contains "All Episodes". Select "Treatment Plan" from the side menu. Validate the 'All Documents' widget only displays treatment plan records. Select a 'Treatment Plan' record and validate the 'Console Widget Viewer' displays the selected plan. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays. Close the report. Select "Episode 2" in the 'Episode Header' field. Validate the 'Console Widget Viewer' still displays the selected 'Treatment Plan' but the filters are cleared in the 'All Documents' widget. Continue selecting various filters and validate the expected result displays. Select "Client B". Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'. Access the 'Registry Settings' form. Enter "Default Value for Console View Episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Select "Yes" in the 'Include Hidden Registry Settings' field. Click [View Registry Settings]. Select the registry setting and click [OK]. Enter "2" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Select "Client A" and navigate to the 'All Documents' view. Validate the 'Episode Header' field contains "Episode 2". Click [Close All]. Select 'Continuity of Care Document' from the side menu. Validate only Continuity of Care Documents display in the 'All Documents' widget. Select a record and validate it is displayed in the 'Console Widget Viewer'. Select "Episode 1" in the 'Episode Header' field. Validate the 'Console Widget Viewer' still displays the record but the filters are cleared in the 'All Documents' widget. Continue selecting various filters and validate the expected result displays. Select "Client B". Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'.	Topics • All Documents Widget • NX • Progress Notes (Group And Individual) • To-Do's • Widgets
Update 108 Summary \| Details 'All Documents' Widget Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan Scenario 1: Validate the 'Filter NX Documentation View Sidebar Document List by Client' registry setting Specific Setup: A client must be enrolled in an existing episode with no documents filed (Client A). A client must be enrolled in an existing episode and have numerous routed documents on file (Client B). 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). Document routing must be enabled for the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms. Each form must have a different document types associated within the 'Document Routing Setup' form. There must be 2 users: A user who is logged in and has access to all document types in 'User Definition' (User A). A user who does not have access to the document types in 'User Definition' (User B). The 'Filter NX Documentation View Sidebar Document List by Client' registry setting will be enabled. If you would like this disabled, please contact a Netsmart Representative. Please note: this scenario is for Avatar NX systems. Steps Select "Client A" and navigate to the 'All Documents' view. Validate no document types display under the 'Doc Widget:Progress Note Documents' field on the sidebar. Access the 'Progress Notes (Group and Individual)' form. Select any value in the 'Progress Note For' field. Select any value in the 'Note Type' field. Enter any value in the 'Notes' field. Populate any desired and required fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate a ' Confirm Document' dialog is displayed with the progress note data. Click [Sign]. Enter the password and click [Verify]. Validate a 'Progress Notes' dialog stating: "Note Filed". Click [OK] and close the form. Navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Validate a document type displays under the 'Doc Widget:Progress Note Documents' field on the sidebar. Access the 'Treatment Plan' form. Enter the current date in the 'Plan Date' field. Select any value in the 'Plan Type' field. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Click [Add New Problem]. Populate all required fields. Click [Add New Goal]. Populate all required fields. Click [Add New Objective]. Populate all required fields. Click [Add New Intervention]. Populate all required fields. Click [Return to Plan]. Select "Final" in the 'Draft/Final' field. Click [Submit]. Validate the treatment plan data displays as expected in the 'Confirm Document' dialog. Click [Sign]. Enter the password and click [Verify]. Navigate to the 'All Documents' view. Refresh the 'All Documents' widget. Validate an additional document type displays under the 'Doc Widget:Progress Note Documents' field on the sidebar. Select "Client B". Validate the sidebar updates. Log out. Log in as "User B". Select "Client A" and navigate to the 'All Documents' view. Validate no document types display under the 'Doc Widget:Progress Note Documents' field on the sidebar. Select "Client B". Validate no document types display under the 'Doc Widget:Progress Note Documents' field on the sidebar. 'Console Widget Viewer' - Append Documents Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: HomeView - Console Widget Viewer Append Progress Notes HomeView - Progress Notes Widget Scenario 1: Validate appending to a Document via "Console Widget Viewer" (Append Security Level Override -Enabled) Specific Setup: Registry Setting "Append Security Level Override" is set to "3". (Note: This setting will override the 'Limit Append To Original Author' registry setting) One user (User1), has "User Security Level" set to "3" in the 'User Definition' form A second user (User2), has "User Security Level" also set to "3" in the 'User Definition' form A third user (User3), has "User Security Level" set to higher than level "3" in 'User Definition' form A fourth user (User4), has "User Security Level" set to lower than level "3" in the 'User Definition' form Have modeled form with document routing enabled. Have console widget created for the modeled form using form "Console Widget Configuration" Have the modeled form console widget added to all the users home view Have the "Console Widget Viewer" widget added to all the users home view Have the "My To Do's" widget added to all the users home view Have a desired client [ClientA], that will be used for testing Steps Log in as "User1" Open the modeled form Select [ClientA] Populate all the desired fields on the form Click [Final] Click [Submit] Route the document In the "My To Do's Widget", click to approve the document just submitted Select [ClientA] in the 'Search Clients' box of the home screen Select "All Episodes" in the 'Episode' list at the top of the home screen Validate the console widget created for the modeled form, displays a row for the document created by "User1" Click the [View] button in that row Validate the document details are populated to the 'Console Widget Viewer', as expected Click the 'Append' button Validate the 'Append Documents' form is loaded. Validate all the fields are populated in the form, as expected data Validate the field 'New Comments to Be Appended to the Original Document' field is enabled Add desired comments in the field In the "Confirm Document" screen, validate all the document data is populated and the comments just added, are appended to the end of document as expected Click [Accept] Populate the "Verify Password" prompt and click [OK] Validate the form is filed successfully Click the [View] button in the row again in the modeled forms console widget Validate all the document data is populated and the comments just added, are appended to the end of document as expected Log out as "User1" Log in as "User2", Select [ClientA] in the 'Search Clients' box of the home screen Select "All Episodes" in the 'Episode' list at the top of the home screen Validate the console widget created for the modeled form, displays a row for the document created by "User1" Click the [View] button in that row Validate the document details are populated to the 'Console Widget Viewer', as expected Validate the "Append" button is present since User2 has the same security level as "User1" Repeat steps 14 thru 24 to append the document Validate results are as expected Log out as "User2" Log in as "User3" Select [ClientA] in the 'Search Clients' box of the home screen Select "All Episodes" in the 'Episode' list at the top of the home screen Validate the console widget created for the modeled form, displays a row for the document created by "User1" Click the [View] button in that row Validate the document details are populated to the 'Console Widget Viewer', as expected Validate the "Append" button is present since User3 has higher security level than "User1" Repeat steps 14 thru 24 to append the document Validate results are as expected Log out as "User3" Log in as "User4" Select [ClientA] in the 'Search Clients' box of the home screen Select "All Episodes" in the 'Episode' list at the top of the home screen Validate the console widget created for the modeled form, displays a row for the document created by "User1" Click the [View] button in that row Validate the document details are populated to the 'Console Widget Viewer', as expected Validate the "Append" button is not present since User4 has a lower security level than "User1" Scenario 2: Validate appending to a Progress Note via the "Console Widget Viewer" (Append Security Level Override -Enabled) Specific Setup: A client must be enrolled in an existing episode (Client A). Have console widget created for the progress note form using the 'Console Widget Configuration' form ('Progress Notes' Console Widget). Document routing must be enabled for the 'Progress Notes (Group and Individual)' form. The 'Append Progress Notes: Limit Append to Original Author' registry setting must be enabled. The 'Append Security Level Override' registry setting must be set to "3". (Note: This setting will override the 'Limit Append To Original Author' registry setting) There must be 4 users: A user with an associated practitioner (Practitioner A) that's logged in (User A). "User A" has the 'My To Do's' widget configured to a view and has a 'User Security Level' of "3" in the 'User Definition' form. A user that has a 'User Security Level' of "3" in the 'User Definition' form (User B). A user that has a 'User Security Level' higher than "3" in the 'User Definition' form (User C). A user that has a 'User Security Level' lower than "3" in the 'User Definition' form (User D). Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate the note displays as expected in the 'Confirm Document' dialog and click [Sign and Route]. Enter the password and click [Verify]. In the 'Route Document to' dialog select "Practitioner A" and click [Submit]. Close the form. Navigate to the 'My To Do's' widget. Validate the document for "Client A" is present and click [Review]. Validate the document displays as expected. Click [Accept] and [Sign]. Enter the password and click [Verify]. Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note displays as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to the 'Progress Notes' console widget. Refresh the widget. Click [View]. Validate the note and appended comment display as expected in the 'Console Widget Viewer'. Log out. Login as "User B". Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note and appended comment display as expected in the 'Console Widget Viewer'. Validate 'Append' is present since "User B" has the same security level as "User A". Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Log out. Login as "User C". Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note and appended comments display as expected in the 'Console Widget Viewer'. Validate 'Append' is present since "User C" has a higher security level than "User A". Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Log out. Log in as "User D". Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note and appended comments display as expected in the 'Console Widget Viewer'. Validate 'Append' is not present since "User D" has a lower security level than "User A". Scenario 3: Validate the 'Limit Append to Original Author' registry setting - Progress Note via the "Console Widget Viewer" Specific Setup: A client must be enrolled in an existing episode (Client A). Have console widget created for the progress note form using the 'Console Widget Configuration' form ('Progress Notes' Console Widget). There must have two users: A user that's logged in and has a practitioner associated (Practitioner A) (User A). Another user (User B) Have the "Progress Notes" Console Widget, the "Console Widget Viewer" and the "My To Do's" widget added to both of the user's home view. Document routing must be enabled for the 'Progress Notes (Group and Individual)' form. The 'Append Progress Notes: Limit Append to Original Author' registry setting must be enabled. Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Populate all required and desired fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate the note displays as expected in the 'Confirm Document' dialog and click [Sign and Route]. Enter the password and click [Verify]. In the 'Route Document to' dialog select "Practitioner A" and click [Submit]. Close the form. Navigate to the 'My To Do's' widget. Validate the document for "Client A" is present and click [Review]. Validate the document displays as expected. Click [Accept] and [Sign]. Enter the password and click [Verify]. Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note displays as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to the 'Progress Notes' console widget. Refresh the widget. Click [View]. Validate the note and appended comment display as expected in the 'Console Widget Viewer'. Log out. Login as "User B". Select "Client A" and navigate to the 'Progress Notes' console widget. Validate an entry displays for "Client A" and click [View]. Validate the note and appended comment display as expected in the 'Console Widget Viewer'. Validate 'Append' does not display in the 'Console Widget Viewer'. Access the 'Registry Settings' form. Enter "Limit Append To Original Author" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Append Progress Notes: Limit Append to Original Author" and click [OK]. Enter "N" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Navigate to the 'Progress Notes' console widget. Refresh the widget. Validate an entry displays for "Client A" and click [View]. Validate the note and appended comment display as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to the 'Progress Notes' console widget. Refresh the widget. Click [View]. Validate the note and appended comments display as expected in the 'Console Widget Viewer'. Scenario 4: Validate appending to a Document via the "Console Widget Viewer" Specific Setup: Have a Modeled form with document routing enabled (Form A). Have console widget created for the modeled form using the 'Console Widget Configuration' form. Have the modeled form console widget (Widget A), the 'Console Widget Viewer' and the 'My To Do's' widget, added to all of the user's home view. The Append Documents 'Limit Append to Original Author' registry setting must be enabled. There must be three users: A user that's logged in and has a practitioner associated (Practitioner A) and has access to "Form A" and the 'Append Documents' form (User A). A user has to access "Form A" and the 'Append Documents' form (User B). A user who has access to "Form A" but does not have access to the 'Append Documents' form (User C). A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access "Form A". Populate all the desired fields on the form. Select "Final" in the 'Draft/Final' field. Click [Submit]. Validate the 'Confirm Document' dialog contains the expected data. Click [Sign and Route]. Enter the password and click [Verify]. In the 'Route Document to' dialog select "Practitioner A" and click [Submit]. Navigate to the 'My To Do's' widget. Validate the document for "Client A" is present and click [Review]. Validate the document displays as expected. Click [Accept] and [Sign]. Enter the password and click [Verify]. Navigate to "Widget A". Validate an entry displays for "Client A" and click [View]. Validate the document displays as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Documents' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the document's data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Refresh "Widget A". Click [View] in the row again in "Widget A". Validate the document and appended comment display as expected in the 'Console Widget Viewer'. Log out. Log in as "User B". Select "Client A" and navigate to "Widget A". Validate an entry displays for "Client A" and click [View]. Validate the document and appended comment display as expected in the 'Console Widget Viewer'. Validate 'Append' does not display in the 'Console Widget Viewer'. Log out. Login as "User C". Select "Client A" and navigate to "Widget A". Validate an entry displays for "Client A" and click [View]. Validate the document and appended comment display as expected in the 'Console Widget Viewer'. Validate 'Append' does not display in the 'Console Widget Viewer'. Access the 'Registry Settings' form. Enter "Limit Append To Original Author" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Limit Append To Original Author" and click [OK]. Enter "N" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Navigate to "Widget A." Refresh the widget. Validate an entry displays for "Client A" and click [View]. Validate the document and appended comment display as expected in the 'Console Widget Viewer'. Validate 'Append' does not display in the 'Console Widget Viewer'. Log out. Login as "User B". Select "Client A" and navigate to "Widget A". Validate an entry displays for "Client A" and click [View]. Validate the document and appended comment display as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Documents' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the document's data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to "Widget A". Refresh the widget. Click [View] in the row again in "Widget A". Validate the document and appended comments display as expected in the 'Console Widget Viewer'. Scenario 5: Validate CCDs display in the All Documents widget Specific Setup: This scenario is for Avatar NX systems only. A client must be defined and have a CCD 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). Steps Select "Client A" and access the 'All Documents' view. Validate the 'Client Information' header is aligned with the widgets. Close the sidebar. Validate the view resizes and the 'Client Information' header aligns with the widgets. Close the 'All Docs' menu Validate the view resizes and the 'Client Information' header aligns with the widgets. Open the sidebar. Validate the view resizes and the 'Client Information' header aligns with the widgets. Select the 'My Activity' menu. Validate the view resizes and the 'Client Information' header aligns with the widgets. Select the "Documents" section. Validate a 'Continuity of Care Document' record is displayed and select it. Validate the CCD displays in the 'Console Widget Viewer'. Click [Close All]. Select the 'My Activity' menu. Validate the view resizes and the 'Client Information' header aligns with the widgets. Scenario 6: 'All Documents' widget - Validate the 'Limit Append to Original Author' registry setting for a Progress Note Specific Setup: A client must be enrolled in an existing episode (Client A). A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' for both users. ('All Documents' view). The 'My To-Do's' widget must be configured to a view for both users. A Category (Category A) must be created in 'Document Management Definition' with the desired document types "Category A" must be selected in 'All Documents Widget Definition - Multi-Document Tab'. Document routing must be enabled for the 'Progress Notes (Group and Individual)' form. Both of the 'Limit Append To Original Author' registry settings must be enabled. There must be two users: A user must have an associated Practitioner (Practitioner A) and be logged in (User A). Another defined user. Please note: This is for Avatar NX systems. Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Fill out all required fields. Select "Final" in the 'Draft/Final' field. Click [Submit Note]. Validate the note displays in the 'Confirm Document' dialog and click [Sign and Route]. Enter the password and click [Verify]. Select "Practitioner A" and click [Add]. Click [Submit]. Validate a 'Progress Notes' dialog stating: "Note Filed." and click [OK]. Close the form. Navigate to the 'My To-Do's' widget. Validate the note for "Client A" and click [Review]. Validate the note displays as expected. Click [Accept] and [Sign]. Enter the password and click [Verify]. Validate the To Do no longer displays. Click [Close]. Select "Client A" and navigate to the 'All Documents' view. Validate the 'Multi-Document Tab' is selected. Validate the note is present and select it. Validate the note displays as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Documents' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to the 'All Documents' view. Click [Close All]. Refresh the 'All Documents' widget. Select 'All Forms'. Validate the note displays and click [View]. Validate the note displays as expected in the 'Console Widget Viewer'. Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Log out. Log in as "User B". Select "Client A" and navigate to the 'All Documents' view. Validate the 'Multi-Document Tab' is selected. Validate the note is present and select it. Validate the note displays as expected in the 'Console Widget Viewer'. Validate 'Append' is not present in the 'Console Widget Viewer'. Click [Close All]. Select 'All Forms'. Validate the note displays and click [View]. Validate the note displays as expected in the 'Console Widget Viewer'. Validate 'Append' is not present in the 'Console Widget Viewer'. Click [Close All]. Access the 'Registry Settings' form. Enter "Limit Append To Original Author" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Append Progress Notes: Limit Append to Original Author" and click [OK]. Enter "N" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Select "Client A" and navigate to the 'All Documents' view. Repeat steps 5a-5h Click [Append]. Validate the 'Append Progress Notes' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Click [Close All]. Access the 'Registry Settings' form. Enter "Limit Append To Original Author" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Append Documents: Limit Append to Original Author" and click [OK]. Enter "N" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Select "Client A" and navigate to the 'All Documents' view. Repeat steps 5a-5c. Click [Append]. Validate the 'Append Documents' form launches. Validate all the fields are populated in the form, as expected. Enter the desired value in the 'New Comments to Be Appended to the Original Document' field. Click [Submit]. Validate the 'Confirm Document' dialog contains all the notes' data including the comments added. Click [Accept]. Enter the password and click [Verify]. Validate the form is filed successfully. Navigate to the 'All Documents' view. Click [Close All]. Refresh the 'All Documents' widget. Validate the note displays and click [View]. Validate the note and all the comments display as expected in the 'Console Widget Viewer'.	Topics • All Documents Widget • NX • Progress Notes (Group And Individual) • Treatment Plan • Console Widget • Document Routing • My To Do's • Registry Settings • Widgets
Update 109 Summary \| Details Personal Pronouns are added to 'Client Lookup/Header Configuration Manager' form. 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 Lookup/Header Configuration Manager' validate added fields display in the 'Client Header' Specific Setup: Avatar PM 2022 Update 100 or Cal-PM 2022 Update 65 is required for full functionality. Steps Open 'Client Lookup/Header Configuration Manager' form. Click 'Client Header' tab. Click [Add New Item] Select 'Personal Pronouns' from the 'Field to Include in Client Header' drop down list. Select any available field order from the 'Field Order' drop down list. Click 'Client Header Override' tab. Click [Add New Item] Select 'Personal Pronouns' from the 'Field to Include in Client Header' drop down list. Select any program from the 'Program' drop down list. Select any available location from the 'Field Order' drop down list. Note: When a client is assigned to the selected program(s), that client's Personal Pronouns will display in the location indicated for the program, not in the location indicated in the 'Client Header' tab. Click [Submit].	Topics • Client Lookup
Update 115 Summary \| Details PM UTC functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Practitioner Enrollment Client Charge Input Client Ledger Scenario 1: Validating Practitioner Enrollment with UTC Enabled - data entry time after midnight Specific Setup: The system must be configured to use UTC. Data entry needs to occur after midnight. A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update their enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset (e.g -4), data_entry_time_j (e.g. 0:02:12), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g EDT), data_entry_utc (e.g. 9/21/2022 4:02). Scenario 2: Validating Practitioner Enrollment with UTC disabled - data entry time after midnight Specific Setup: Data entry needs to occur after midnight. A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update their enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns do not exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset, data_entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short, data_entry_utc. Using the preferred method to validate SQL tables, validate the value in the data_entry_time column in the SYSTEM.staff_category_history table appropriately reflects the time of data entry, which would be after midnight. Scenario 3: Validating Client Charge Input with UTC enabled - data entry after midnight Specific Setup: The system must be configured to use UTC. Data entry needs to occur after midnight. Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns in the SYSTEM.billing_tx_history table: data_entry_offset (e.g. -4), data _entry_time_j (e.g. 0:02:04), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g. EDT), data_entry_utc (e.g. 9/21/2022 4:02). Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry after midnight. Scenario 4: Validating Client Charge Input with UTC disabled - data entry after midnight Specific Setup: Data entry needs to occur after midnight. Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns don't exist in the SYSTEM.billing_tx_history table: data_entry_offset, data _entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short, data_entry_utc. Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry after midnight. Scenario 5: Validating Practitioner Enrollment with UTC Enabled Specific Setup: The system must be configured to use UTC. A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update their enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset (e.g -4), data_entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g EDT), data_entry_utc (e.g. 9/21/2022 16:26). Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry. Scenario 6: Validating Practitioner Enrollment with UTC disabled Specific Setup: A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update their enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns don't exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset, data_entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short), data_entry_utc. Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry. Scenario 7: Validating Client Charge Input with UTC enabled Specific Setup: The system must be configured to use UTC. Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns in the SYSTEM.billing_tx_history table: data_entry_offset (e.g. -4), data _entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g. EDT), data_entry_utc (e.g. 09/20/2022 16:26) Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry. Scenario 8: Validating Client Charge Input with UTC disabled Specific Setup: Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns don't exist in the SYSTEM.billing_tx_history table: data_entry_offset, data _entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short, data_entry_utc. Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry.	Topics • Client Charge Input • NX • Practitioner
Update 118 Summary \| Details Avatar NX - eMAR Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: All Documents Widget Avatar eMAR Scenario 1: Validate the 'Default Value for Console View Episodes' registry setting Specific Setup: The 'Enable Console Widgets/Views' registry setting must be enabled. Have a client that is currently admitted in multiple episodes which include active and inactive (discharged) inpatient and outpatient episodes (Client A). Have a client that is currently admitted in multiple episodes but all the episodes are inactive (discharged) (Client B). Steps Access the 'Registry Settings' form. Select "Yes" in the 'Include Hidden Registry Settings' field. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "0" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" In the "Search Clients" field on the home view, select "Client A". Validate the "Episodes" field on the home view defaults to the client's highest numbered "active or inactive" episode number. On the home view, select [ClientB] Validate the "Episodes" selection box on the home view defaults to the clients highest numbered episode number In the "Registry Settings" form, search for registry setting 'Default Value for Console View Episodes' Set the "Registry Setting Value" field to "1" Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" In the "Search Clients" field on the home view, select [ClientA] Validate the "Episodes" selection box on the home view displays the text "All Episodes' Click "All Episodes" Validate all the clients episodes are displayed, as expected In the "Search Clients" field on the home view, select [ClientB] Validate the "Episodes" selection box on the home view displays the text "All Episodes' Click "All Episodes" Validate all the clients episodes are displayed, as expected In the "Registry Settings" form, search for registry setting 'Default Value for Console View Episodes' Set the "Registry Setting Value" field to "2" Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" On the home view, select [ClientA] Validate the "Episodes" selection box on the home view defaults to the clients latest 'active' episode (by Episode Number) On the home view, select [ClientB] Validate the "Episodes" selection box on the home view defaults to the clients highest numbered episode. In the "Registry Settings" form, search for registry setting 'Default Value for Console View Episodes' Set the "Registry Setting Value" field to "3" Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" On the home view, select [ClientA] Validate the "Episodes" selection box on the home view defaults to the clients latest 'active' episode (by Admission Date). On the home view, select [ClientB] Validate the "Episodes" selection box on the home view defaults to the clients highest numbered episode. In the "Registry Settings" form, search for registry setting 'Default Value for Console View Episodes' Set the "Registry Setting Value" field to "4" Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" On the home view, select [ClientA] Validate the "Episodes" selection box on the home view defaults to the clients latest 'active' inpatient client episode (by Admission Date) On the home view, select [ClientB] Validate the "Episodes" selection box on the home view defaults to the clients highest numbered episode. In the "Registry Settings" form, search for registry setting 'Default Value for Console View Episodes' Set the "Registry Setting Value" field to "5" Click [Submit] and click [No] to message "Submitting has completed. Do you wish to return to the form?" On the home view, select [ClientA] Validate the "Episodes" selection box on the home view defaults to the clients latest 'active' episode (by Admission Date) but always default the latest active Inpatient episode when one exists On the home view, select [ClientB] Validate the "Episodes" selection box on the home view defaults to the clients highest numbered episode. Scenario 2: 'All Documents' Widget - Validate filtering when switching between clients Specific Setup: A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view). Two clients are admitted into two active episodes with documents on file in the 'All Documents' Widget. The 'Default Value for Console View Episodes Registry Setting' must be set to "1". Steps Select "Client A" and navigate to the 'All Documents' view. Validate the 'Episode Header' field contains "All Episodes". Select "Treatment Plan" from the side menu. Validate the 'All Documents' widget only displays treatment plan records. Select a 'Treatment Plan' record and validate the 'Console Widget Viewer' displays the selected plan. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays. Close the report. Select "Episode 2" in the 'Episode Header' field. Validate the 'Console Widget Viewer' still displays the selected 'Treatment Plan' but the filters are cleared in the 'All Documents' widget. Continue selecting various filters and validate the expected result displays. Select "Client B". Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'. Access the 'Registry Settings' form. Enter "Default Value for Console View Episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Select "Yes" in the 'Include Hidden Registry Settings' field. Click [View Registry Settings]. Select the registry setting and click [OK]. Enter "2" in the 'Registry Setting Value' field. Click [Submit], [OK], and [No]. Select "Client A" and navigate to the 'All Documents' view. Validate the 'Episode Header' field contains "Episode 2". Click [Close All]. Select 'Continuity of Care Document' from the side menu. Validate only Continuity of Care Documents display in the 'All Documents' widget. Select a record and validate it is displayed in the 'Console Widget Viewer'. Select "Episode 1" in the 'Episode Header' field. Validate the 'Console Widget Viewer' still displays the record but the filters are cleared in the 'All Documents' widget. Continue selecting various filters and validate the expected result displays. Select "Client B". Validate the filters clear in the 'All Documents' widget and no records display in the 'Console Widget Viewer'. Scenario 3: eMAR - Validate the 'Default Value for Console View Episodes' registry setting Specific Setup: The 'Enable Console Widgets/Views' registry setting must be enabled. Have a client that is currently admitted in multiple episodes which include active and inactive (discharged) inpatient and outpatient episodes (Client A). Have a client that is currently admitted in multiple episodes but all the episodes are inactive (discharged) (Client B). The 'eMAR' widget must be configured to a view. Please note: This scenario is for Avatar NX systems only. Steps Access the 'Registry Settings' form. Select "Yes" in the 'Include Hidden Registry Settings' field. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "0" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the highest numbered episode displays in the 'Episode' field. Select "Client B". Validate the highest numbered episode displays in the 'Episode' field. Access the 'Registry Settings' form. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "1" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the most recent inpatient episode displays in the 'Episode' field. (Please note: "All" will display in myAvatar) Select "Client B". Validate "All" displays in the 'Episode' field. Access the 'Registry Settings' form. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "2" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the latest active episode (by Episode number) displays in the 'Episode' field. Select "Client B". Validate the latest active episode (by Episode number) displays in the 'Episode' field. Access the 'Registry Settings' form. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "3" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the latest/current active episode (by Admission Date) displays in the 'Episode' field. Select "Client B". Validate the latest/current active episode (by Admission Date) displays in the 'Episode' field. Access the 'Registry Settings' form. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "4" in the 'Registry Setting Value' field. Click [Submit] and click [Yes] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the most recent inpatient episode displays in the 'Episode' field. Select "Client B". Validate the most recent inpatient episode displays in the 'Episode' field. Access the 'Registry Settings' form. Enter "default value for console view episodes" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Enter "5" in the 'Registry Setting Value' field. Click [Submit] and click [No] to message "Submitting has completed. Do you wish to return to the form?" Select "Client A" and navigate to the 'eMAR' widget. Validate the most recent inpatient episode displays in the 'Episode' field. Select "Client B". Validate the most recent inpatient episode displays in the 'Episode' field.	Topics • NX • Registry Settings
Update 24.1 Summary \| Details State Form File Generation - Compiles Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form File Generation Scenario 1: State Form File Generation - Validations Specific Setup: Have user [UserA] that has "Double Quotes" populated in the "User Description" field of their "User Definition" form record Have user [UserB] that has an "Apostrophe" populated in the "User Description" field of their "User Definition" form record Have user [UserC] that has any other special character populated in the "User Description" field of their "User Definition" form record Have user [UserD] that has no special characters in their name Have a "State Form Definition" file defined [DefinitionA], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "GROUP BY" command within the statement Have a "State Form Definition" file defined [DefinitionB], whose record has an SQL statement populated in the "Additional SQL Selection" column that includes the "ORDER BY" command within the statement Log in as [UserA] Steps Open form "State Form File Generation". Select definition [DefinitionA] in field "State Form". Populate the "File Description" field. In the "File Generation Options" field, select "Compile". Click [Process]. Validate the process completes successfully. In the "File Generation Options" field, select "Dump File". Click [Process]. Validate the data output of the file is as expected Close the form Open form "State Form File Generation". Select definition [DefinitionB] in field "State Form". Populate the "File Description" field. In the "File Generation Options" field, select "Compile". Click [Process]. Validate the process completes successfully. In the "File Generation Options" field, select "Dump File". Click [Process]. Validate the data output of the file is as expected Close the form Log out as [UserA] Log in as [UserB] Repeat step 1 Validate results are as expected Repeat step 2 Validate results are as expected Log out as [UserB] Log in as [UserC] Repeat step 1 Validate results are as expected Repeat step 2 Validate results are as expected State Form Task Scheduler - Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form Definition State Form Task Scheduler System Task Scheduler Scenario 1: System Task Scheduler - Validate a "State Form Definition" file task sent to an "FTP/SFTP" server Specific Setup: Have a state form definition file [DefA], created in form "State Form Definition" Have an "FTP Server" set up to receive files Have the following "FTP Server" information available in order to populate the "State Form Task Scheduler" form during testing: The "Service Directory" location The "Server Host Name" The "Server Port Number" The "Server Username" field The "Server Password" field The "Public Key File" and the folder location of the file The "Private Key File" and the folder location of the file Steps Open form "State Form Definition" Select [DefA] Populate the "File Path" field with directory that exists on the logged in users server; [LocationA] Submit the form Validate the form files successfully Open the 'State Form Task Scheduler' form Select [DefA] Select "Yes" in the "Create File" field Select "Yes" in "Send File To FTP Server" field In the "FTP Type" field, select "SFTP - Key Pair" Populate the "Server Host Name" field Populate the "Server Port Number" field Populate the "Server Username" field Populate the "Server Password" field Populate the "Service Directory" field, this is folder location [FTPfolderA] on the FTP server where the file will be sent Populate the "Public Key File Location" field Populate the "Private Key File Location" field Click [Test FTP Connection] Validate test is successful Submit the form Validate the form files successfully Open form "System Task Scheduler" Select the task set up for [DefA] in step 2 from the "Schedule(s)" field Populate the "Recurrence Pattern" field with desired value Populate the "Task Occurrence" field with the desired value Populate the "Start By" field with the desired date for the task to start Populate the "Start Time" field with the desired time for the task to start Select "No" in the "Inactive Task" field Click [Schedule Task] Close the form When the scheduled start by date and time for task filed in step 3 has passed: Validate the state form file [DefA] exist in the folder [LocationA] on the logged in users server, set in step1 Validate the state form file [DefA] exists in the folder [FTPfolderA] on the "FTP" server, set in step 2 State Form Task Files - ECP servers Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form Task Scheduler System Task Scheduler Scenario 1: System Task Scheduler - Validate "State Form Definition" file task when compiled on an ECP server Specific Setup: Have an environment that contains an Avatar "Database" server and also an "ECP" server configured by Netsmart with the database server as its "Remote" database server Have a state form definition file created in form "State Form Definition" [DefA] In form "State Form Definition", select [DefA] and note the definition ID# [IDNum], in parentheses next to the file name Have a report or query that can display data in the "SYSTEM.RADplus_sf_audit_record" table [ReportA] Steps Open form "State Form Definition" Select [DefA] Populate the "File Path" field with directory that exists on the users local server Submit the form Open the 'State Form Task Scheduler' form Select [DefA] Select "Yes" for Create File Populate any other required fields Submit the form Validate the form files successful Open form "System Task Scheduler" Select the task set up for [DefA] in step 2 from the "Schedule(s)" field Populate the "Recurrence Pattern" field with desired value Populate the "Task Occurrence" field with the desired value Populate the "Start By" field with the desired date for the task to start Populate the "Start Time" field with the desired time for the task to start Select "No" in the "Inactive Task" field Click [Schedule Task] Close the form When the scheduled date and time for task filed in step 2 has passed Run [ReportA] to display data in the "SYSTEM.RADplus_sf_audit_record" table Validate a row is present for the state form definition file, [DefA] Validate the "FileID" column is populated with definitions ID number [IDNum], noted in the setup Validate the "Server" field is populated with expected "FTP" server name, indicating that the file compiled on that server as expected State Form Definition Files - sub records Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: State Form File Generation Scenario 1: Validate the output of a "State Form Definition" file containing multiple sub-records Specific Setup: Have an "XML" type "State Form Definition" file created that contains a main record and multiple sub-records. [Def1] Steps Open form "State Form File Generation" Select the [Def1] definition in field "State Form" In the "File Generation Options" field, select "Compile" Click [Process] Validate the process completes successfully In the "File Generation Options" field, select "Create File on Server" Click [Process] Click the "Compile Complete", [OK] button Click [Process] to create a file on the server In the "Windows Explorer" window, navigate to a folder location and save the file In the "Save In" drop down list of File Explorer, select a directory and populate the "File Name" Click [Save] In "File Explorer", go to the directory where the file was saved Click to open the file Validate the contents are as expected	Topics • NX • State Form Tools • State Form Task Scheduler