Avatar PM 2023 is Installed
Scenario 1: Validate Upgrading RADplus 2022 to 2023 is successful when 2022.04.00 is loaded
Specific Setup:
- Latest Monthly Release is installed.
Steps
- Open the "Product Updates" form.
- Select the appropriate [Namespace] from the Application dropdown list
- Click [Select Update/Customization Pack].
- Browse to the location for the updates and select the Update 1.
- Click [OK] on the "File Upload Complete" window.
- Click [Review Update/Customization Pack Contents].
- Verify Update 1 is included.
- Click [Install Update/Customization Pack].
- Click [OK] when the install completes.
- Click [Close Form].
|
Topics
• Upgrade
|
Append Document
Scenario 1: Append Documents - Validate user permissions to append documents
Specific Setup:
- Have a system with a [Root] system code and sub system code defined [TestSub]
- Sub system code [TestSub] has been assigned a specific program [ProgramA]
- [TestClient] is admitted in two episodes:
- [Episode1] to [ProgramA]
- [Episode2] to [ProgramB]
- [UserA] has access to both the [Root] system code and sub system code [TestSub]
- [UserB] has access only to the sub system code [TestSub]
- [FormA] has been submitted for [TestClient] in [Episode1] and a document has been generated [DocA]
- [FormB] has been submitted for [TestClient] in [Episode2] and a document has been generated [DocB]
- Log in as [UserB] into the [TestSub] sub system code
Steps
- Open form "Append Documents"
- Select the applicable form type in the "Form Type" field
- Select [TestClient] in the "Entity" field
- Enter the applicable date range in the "From Date" and "To Date" fields
- Click the "List of Documents" field
- Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
- Validate the drop down list does not display [Doc2] filed for [FormB] in [Episode2, ProgramB], as expected
- Select the row for [Doc1]
- Add any desired comments in the "New Comments to be Appended to Original Document" field
- Submit the form
- Validate the 'Confirm Document' dialog displays the appended comments
- Validate the document contains the appended signature of the logged in user [UserB] at the end of the document.
- Click [Accept].
- Validate the form files successfully.
- Log out as [UserB]
- Log in as [UserA] into the sub system code [SubCode]
- Repeat step1
- Validate the results are the same, as the sub code is restricted to only [ProgramA]
- Log out as [UserA]
- Log in as [UserA] into the [Root] system code
- Repeat step 1
- Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
- Validate the drop down list also displays [Doc2] filed for [FormB] in [Episode2, ProgramB], as [UserA] has access to both the root and sub system code.
My To Do's Widget - Sign Tab
Scenario 1: 'My To Do's Widget - Validate user permissions to access documents
Specific Setup:
- Have a system with a root and a sub system code
- The sub system is code is assigned to only [ProgramA]
- [UserA] is a staff member that can cosign for other staff members and has access to log into both the root and the sub code
- [UserB] is a staff member and cannot cosign for other staff members and has access to log both the root and the sub code
- [TestClient] has been admitted in two episodes:
- "Episode1" in [ProgramA]
- "Episode2" in [ProgramB]
- Two documents have been routed for [TestForm] for [TestClient]
- [DocA] - was routed to [UserA] for an [Epsiode1]
- [DocB] - was routed to [UserB] for [Episode2]
- [UserA] and [UserB] have the "My To Do's" widget on their home view
Steps
- Log in to the sub code as [UserA]
- Navigate to the "My To Do's" widget
- Click the [Sign] tab
- Search for [UserA] in the "Staff" search field
- Validate [DocA] is found
- Search for [UserB] in the Staff field
- Validate [DocB] is not found, as [DocB] was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
- Log out as [UserA] from sub code
- Log in as [UserA] to the root system code
- Navigate to the "My To Do's" widget
- Click the [Sign] tab
- Search for [UserA] in the "Staff" search field
- Validate [DocA] is found
- Search for [UserB] in the "Staff" search field
- Validate [DocB] is found, as [UserA] can co-sign for other staff members is logged into the root system code, which has access to all programs
- Log out as [UserA]
- Log in as [UserB] into the sub code
- Navigate to the "My To Do's" widget
- Click the [Sign] tab
- Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
- Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
- Validate [DocB] is not listed in the "Search Documents" list, as that document was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
- Log out as [UserB] from sub code
- Log in as [UserB] to the root system code
- Navigate to the "My To Do's" widget
- Click the [Sign] tab
- Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
- Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
- Validate [DocB] is listed in the "Search Documents" list, as the document was routed to [UserB] and is logged into the root system code, which has access to all programs
My To Do's Widget - Sign Tab
Scenario 1: 'My To Do's Widget (Sign Tab) - Validate approving documents as as Co-Signer
Specific Setup:
- [UserA] is a staff member
- [UserB] is a staff member
- [UserC] is a staff member that can co-sign To Do's for other staff members
- Two documents have been routed in form [TestForm], for [TestClient]
- [DocA] - was routed to [UserA] in [Episode1]
- [DocB] - was routed to [UserB] in [Episode2]
- [UserC] has the "My To Do's" widget on their home view
- Log in as [UserC]
Steps
- Navigate to the "My To Do's" widget
- Click the [Sign] tab
- In the "Staff" search filed, search for [UserA]
- Validate the row for [DocA] is the "Search Documents" list, and select the row
- Validate the "Document" preview pane displays data as expected for the document
- Navigate to the end of the document
- Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
- Click [Accept], to move the document to the "Accepted Documents" section
- Select the document
- Click [Sign All]
- Validate the document is removed from the "Sign Tab"
- In the "Staff" search filed, search for [UserB]
- Validate the row for [DocB] is the "Search Documents" list, and select the row
- Validate the "Document" preview pane displays data as expected for the document
- Navigate to the end of the document
- Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
- Click [Accept], to move the document to the "Accepted Documents" section
- Select the document
- Click [Sign All]
- Validate the document is removed from the "Sign Tab"
- Open form "Clinical Document Viewer"
- Select [TestClient] in the "Select Client" field
- Click [Process]
- Click the [Results] tab
- Locate the row for the [DocA] signed in step 1b and select the "View" check box
- Click the [View] button
- Validate the "Document" preview pane displays data as expected for the document
- Navigate to the end of the document
- Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
- Click [Close All Documents]
- Locate the row for the [DocB] signed in step 1b and select the "View" check box
- Click the [View] button
- Validate the "Document" preview pane displays data as expected for the document
- Navigate to the end of the document
- Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
- Click [Close All Documents]
- Click the [Search] tab
- Click [Close]
Document Archiving
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Document Archiving - Form field validations
Specific Setup:
- A "Form" type [FormtypeA], is defined in form "Document Management Definition" and includes restrictions selected in field "Document Restrictions'
- [FormA] is set up in form "Document Routing Setup" with [FormtypeA]
- A document [DocumentA] generated with [FormA] exists for [TestClient], that was created over "180" days ago
- A "Form" type [FormtypeB], is defined in form "Document Management Definition" and does "not" include any restrictions selected in field "Document Restrictions'
- [FormB] is set up in form "Document Routing Setup" with [FormtypeB]
- A document [DocumentB] that was generated with [FormB] exists for [TestClient], that was created over "180" days ago
Steps
- Open form "Clinical Document Viewer"
- Select [TestClient]
- Click [Process]
- Validate [DocumentA] generated by [FormA], is displayed as expected date
- Validate [DocumentB] generated by [FormB], is displayed as expected date
- Close the form
- Open form "Document Archiving"
- Select "Client" the entity type in the "Entity Type" field
- Select "Individual" in the "Include" field
- Select [TestClient] in the "Entity" field
- Select the applicable episode in the "Episode" field
- In the "Archive Documents Older Than" enter the desired date greater than "180" days
- Click the "View Form Types Included"
- Validate row is displayed for [FormTypeA] for [FormA]
- Validate row is displayed for [FormTypeB] for [FormB]
- Click [Archive]
- At the "Are you sure you want to Archive these Documents" dialog, click [Yes]
- Close the form
- Open form "Clinical Document Viewer"
- Select [TestClient]
- Click [Process]
- Validate [DocumentA] generated by [FormA] is no longer displayed, as expected
- Validate [DocumentB] generated by [FormB] is no longer displayed, as expected
|
Topics
• Document Routing • NX • My To Do's • Document Management
|
Modeled Forms - 'Decimal' and 'Integer' fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Table Definition (PM)
- Dictionary Update (PM)
- Modeled Client
Scenario 1: Modeled Form - 'Decimal' and 'Integer' field validations
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
- Have a modeled form with "Decimal" and "Integer" field types (Form A).
- "Form A" must be accessible from the Chart View.
Steps
- Select "Client A" and access "Form A".
- Enter a negative decimal value in the 'Decimal' field (Ex: -1.24).
- Validate the value is accepted.
- Enter a negative integer value in the 'Integer' field (Ex: -1212).
- Validate the value is accepted.
- Click [Submit].
- Double click on "Client A" in the 'My Clients' widget.
- Validate that the 'Chart View' is displayed.
- Select "Form A" from the left-hand side.
- Validate the record filed in the previous steps is displayed.
- Validate the 'Decimal' field contains the value filed in the previous steps (Ex: -1.24).
- Validate the 'Integer' field contains the value filed in the previous steps (Ex: -1212).
- Close the Chart.
- Select "Client A" and access "Form A".
- Click [Edit] to edit the previous filed record.
- Enter a positive decimal value in the 'Decimal' field (Ex: 2.41).
- Validate the value is accepted.
- Enter a positive integer value in the 'Integer' field (Ex: 1212).
- Validate the value is accepted.
- Click [Submit].
- Double-click on "Client A" in the 'My Clients' widget.
- Validate that the 'Chart View' is displayed.
- Select "Form A" from the left-hand side.
- Validate the record updated in the previous steps is displayed.
- Validate the 'Decimal' field contains the value filed in the previous steps (Ex: 2.41).
- Validate the 'Integer' field contains the value filed in the previous steps (Ex: 1212).
- Close the Chart.
|
Topics
• Modeling
|
Avatar Data Warehouse - IRIS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Data Warehouse Processing (IRIS)- Table row validations
Specific Setup:
- Have Avatar database server set up that is running on "IRIS" based system that's configured with the parent namespace and one or more child namespaces
- Have a server installed with the latest released version of "Avatar Data Warehouse Middleware" for "IRIS".
- Netsmart has been configured the middleware to initiate the data warehouse process
- Have a "Microsoft SQL Server" where table data processed by the data warehouse process will be stored
- Have a database program that can query the data in the tables stored on the data warehouse server. For example program "DBeaver Universal Database Manager" or "Crystal Reports"
- In form "User Definition", a user had been created [AvatarDW] as the designated data warehouse user.
- [AvatarDW] has been assigned permissions to tables determined to be included in the data warehouse process, that includes tables selected in parent namespace and in any child namespaces
- In form "Data Warehouse Transient Comparison Configuration", the designated data warehouse user [AvatarDW] has the designated tables selected in previous selected in "Mark Tables for Full Load" section
- Have a report or query that will display data in the "SYSTEM.dss_inc_error_log" table
- Have a report or query that will display data in the "SYSTEM.dss_inc_full_load_history" table
- Netsmart has run "Data Warehouse Middleware" process on the middleware server, in the parent namespace and each child namespace
Steps
- Generate the report to display data in the "SYSTEM.dss_inc_error_log" table
- Validate there are no results indicating the data warehouse middleware process has completed successfully
- Generate the report to display data in the "SYSTEM.dss_inc_full_load_history" table
- Validate the expected data rows are present on the report for the parent and child namespace tables selected for data warehouse processing in the setup
- Validate each row has "Insert" populated in the "Type" field
- Open the program to query data on the 'SQL' database server and connect to the database
- Run at query to display rows filed the "dss_completion_flag" table.
- Validate the expected tables are present on the results, for the parent and child namespace tables selected for data warehouse processing, in the setup
- Validate the "dss_status" field for each row is set to "1", indicating the table was loaded successfully
- From the database "Table" tree list, select tables form the parent and child namespaces
- Click to display the rows in the table
- Validate all data rows are displayed, as expected
|
Topics
• Data Warehouse
|
|
Topics
• Progress Notes (Group And Individual) • RADplus Utilities • NX • Allergies and Hypersensitivities • myAvatar NX Only • View Definition
|
User Modeled Forms - Multiple Iterations Sections
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Table Definition (PM)
- Dictionary Update (PM)
Scenario 1: Validate modeled forms that have various multiple iterations sections when document routing is enabled
Specific Setup:
- A user-modeled form (Form A) is defined with the following:
- 10+ multiple iterations sections
- Document routing enabled
- Accessible from the Chart View
Steps
- Select "Client A" and access the "Form A".
- Populate all sections in the form.
- Select "Final" in the 'Draft/Final' field.
- Click [Submit].
- Validate the 'Confirm Document' dialog is displayed.
- Validate the TIFF image contains the form sections in proper order.
- Click [Accept].
- Enter the password associated to the logged in user and click [OK].
- Double click on "Client A" in the 'My Clients' widget.
- Validate that the 'Chart View' is displayed.
- Select "Form A" from the left-hand side.
- Validate all previously filed data is displayed.
- Validate the form sections appear in the proper order.
- Close the Chart.
|
Topics
• Modeling • Document Routing
|
Progress Notes and User Modeled Form - Default Author for Transcribing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission
- Practitioner Enrollment
- User Role Definition
- Envelope Definition (CWS)
- Table Definition (CWS)
- Form Definition (CWS)
- Routing Test Form w/Doc Routing Crystal Report
- Progress Notes (Group and Individual)
- Attending Practitioner
- Treatment Plan (Non-Episodic)
Scenario 1: User Modeled Forms - Transcriber Default Author
Specific Setup:
- Using the "Practitioner Enrollment" form, create 8 practitioners.
- Admit a client into an outpatient episode, populate the "Attending Practitioner" field with the staff designated as "Practitioner 1" and designate this "Client A".
- Admit a client into an outpatient episode, do not populate the "Attending Practitioner" field and designate this "Client B".
- Using user modeling, create a user modeled form that contains a Draft/Final field so it can be routed.
- Using "User Role Definition" add or edit a user role to give users access to the form being tested, to not allow customization and to designate the user role as a transcriber and set the "Default Author" to "Practitioner 3". Designate this "User Role A".
- Set up a user for each of the 8 practitioners using "User Definition".
- User 1 must be "Practitioner 1" and should not be a transcriber on the "Document Routing" section.
- User 2 must be "Practitioner 2" and should not be a transcriber on the "Document Routing" section.
- User 3 must be "Practitioner 3" and should not be a transcriber on the "Document Routing" section.
- User 4 must be "Practitioner 4" and should be designated a transcriber on the "Document Routing" section and should have "Practitioner 2" assigned as "Default Author" on the "Document Routing" section.
- User 5 must be "Practitioner 5" and should be assigned to "User Role A" and designated a transcriber on the "Document Routing" section.
- User 6 must be "Practitioner 6" and must be designated a transcriber but should have no "Default Author" defined on the "Document Routing" section.
- User 7 must be "Practitioner 7", should be assigned to "User Role A" and should be designated a transcriber and should have the "Default Author" set to "Practitioner 3" on the "Document Routing" section.
- User 8 must be "Practitioner 8", should be assigned to "User Role A" and should be designated a transcriber, the "Default Author" should be set to "Practitioner 2" on the "Document Routing" section.
- All users must be given access to the form being tested on the "Forms and Table" section of the "User Definition" form.
- All users must be set up to have a home view that contains the "MyToDo's" widget.
- Using the "Document Routing Setup" form, enable document routing and allow transcriber for the form being tested.
Steps
- Test 1: User who is a transcriber, but has no default author assigned, client who has no attending practitioner. The result is the Select Author field will be blank.
- Login as "User 6".
- Using the user modeled form, generate a progress note for "Client B" and set it to final.
- Validate the "Select Author" field is blank.
- Set "Select Author" to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the author column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 2: User who is a transcriber, and has a default author assigned in the "User Definition" form, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" in the "User Definition".
- Login as "User 4".
- Using the user modeled form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 3: User who is a transcriber, is assigned to a default author assigned in the "User Definition" form, is also assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's default author from "User Definition".
- Login as "User 8".
- Using the user modeled form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 4: User who is a transcriber, is assigned to a user role that has default author assigned, and has the same default author assigned on the user definition form and client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Definition" form.
- Login as "User 7".
- Using the user modeled form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 5: User who is a transcriber, is assigned to a user role that has default author assigned, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Role Definition".
- Login as "User 5".
- Using the user modeled form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 6: User who is a transcriber, is assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's user role default author from "User Role Definition".
- Login as "User 5".
- Using the user modeled form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 7: User who is a transcriber, has no "Default Author" in "User Definition" and a client who does not have an attending practitioner. The result is the Select Author field will default to blank.
- Login as "User 6".
- Using the user modeled form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 8: User who is a transcriber, has no "Default Author" defined client who has an attending practitioner. Author rejected the initial note and returned to transcriber for corrections.
- Login as "User 6".
- Using the user modeled form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Reject the note to send it back to the transcriber.
- Log off and login as "User 6".
- Navigate to the "myToDo's" widget.
- Open the user modeled form from the myToDo's item.
- Correct and finalize the note.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User 2".
- Finalize the progress note.
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the progress note.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
Scenario 2: Progress Notes (Group and Individual) - Transcriber Default Author
Specific Setup:
- Using the "Practitioner Enrollment" form, create 8 practitioners.
- Admit a client into an outpatient episode, populate the "Attending Practitioner" field with the staff designated as "Practitioner 1" and designate this "Client A".
- Admit a client into an outpatient episode, do not populate the "Attending Practitioner" field and designate this "Client B".
- Using "User Role Definition" add or edit a user role to give users access to the form being tested, to not allow customization and to designate the user role as a transcriber and set the "Default Author" to "Practitioner 3". Designate this "User Role A".
- Set up a user for each of the 8 practitioners using "User Definition".
- User 1 must be "Practitioner 1" and should not be a transcriber on the "Document Routing" section.
- User 2 must be "Practitioner 2" and should not be a transcriber on the "Document Routing" section.
- User 3 must be "Practitioner 3" and should not be a transcriber on the "Document Routing" section.
- User 4 must be "Practitioner 4" and should be designated a transcriber on the "Document Routing" section and should have "Practitioner 2" assigned as "Default Author" on the "Document Routing" section.
- User 5 must be "Practitioner 5" and should be assigned to "User Role A" and designated a transcriber on the "Document Routing" section.
- User 6 must be "Practitioner 6" and must be designated a transcriber but should have no "Default Author" defined on the "Document Routing" section.
- User 7 must be "Practitioner 7", should be assigned to "User Role A" and should be designated a transcriber and should have the "Default Author" set to "Practitioner 3" on the "Document Routing" section.
- User 8 must be "Practitioner 8", should be assigned to "User Role A" and should be designated a transcriber, the "Default Author" should be set to "Practitioner 2" on the "Document Routing" section.
- All users must be given access to the form being tested on the "Forms and Table" section of the "User Definition" form.
- All users must be set up to have a home view that contains the "MyToDo's" widget.
- Using the "Document Routing Setup" form, enable document routing and allow transcriber for the form being tested.
Steps
- Test 1: User who is a transcriber, but has no default author assigned, client who has no attending practitioner. The result is the Select Author field will be blank.
- Login as "User 6".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client B" and set it to final.
- Validate the "Select Author" field is blank.
- Set "Select Author" to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the author column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 2: User who is a transcriber, but has no default author assigned, client who has an attending practitioner. The result is the Select Author will default to the client's attending practitioner.
- Login as "User 6".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note and for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 1".
- Log off and login as "User/Practitioner 1".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 3: User who is a transcriber, and has a default author assigned in the "User Definition" form, client who has an attending practitioner. The result is the Select Author field will default to the client's attending practitioner.
- Login as "User 4".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 4: User who is a transcriber, is assigned to a user role that has default author assigned, client who has an attending practitioner. The result is the Select Author field will default to the client's attending practitioner.
- Login as "User 5".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 5: User who is a transcriber, is assigned to a user role that has default author assigned, and has the same default author assigned on the user definition form and client who has an attending practitioner. The result is the Select Author field will default to the client's attending practitioner.
- Login as "User 7".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 6: User who is a transcriber, and has a default author assigned in the "User Definition" form, client who does not have an attending practitioner. The result is the Select Author field will default to the user's default author from "User Definition".
- Login as "User 4".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 7: User who is a transcriber, is assigned to a default author assigned in the "User Definition" form, is also assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's default author from "User Definition".
- Login as "User 8".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 8: User who is a transcriber, is assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's user role default author from "User Role Definition".
- Login as "User 8".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 9: User who is a transcriber, is assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is that no matter the default value, if you change the "Select Author" to someone else, the note will be routed to them.
- Login as "User 8".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Change the "Select Author" to "User/Transcriber 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 10: User who is a transcriber, is assigned to a user role that has default author assigned, and has the same default author assigned on the user definition form, client who has an attending practitioner. Author rejected the initial note and returned to transcriber for corrections.
- Login as "User 7".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 1".
- Log off and login as "User/Practitioner 1".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Reject the note to send it back to the transcriber.
- Log off and login as "User 7".
- Navigate to the "myToDo's" widget.
- Open the "Progress Notes (Group and Individual)" form from the myToDo's item.
- Correct and finalize the note.
- Validate "Select Author" defaults to "User/Practitioner 1".
- Log off and login as "User 1".
- Finalize the progress note.
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the progress note.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 11: User who is a transcriber, has no default author assigned, is not assigned to a user role., client who has an attending practitioner. After note is transcribed, the client's attending practitioner is changed to another practitioner. Note remains with the original author and doesn't transfer to the new attending practitioner for the client.
- Login as "User 8".
- Using the "Progress Notes (Group and Individual)" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 1".
- Open the "Attending Practitioner" form and change the practitioner to "Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- This user won't get a To Do for this item because the To do will stay with the original author.
- Log off and log in as "User/Practitioner 1".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the progress note.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
Scenario 3: Episodic Treatment Plans - Transcriber Default Author
Specific Setup:
- Using the "Practitioner Enrollment" form, create 8 practitioners.
- Admit a client into an outpatient episode, populate the "Attending Practitioner" field with the staff designated as "Practitioner 1" and designate this "Client A".
- Admit a client into an outpatient episode, do not populate the "Attending Practitioner" field and designate this "Client B".
- Using "User Role Definition" add or edit a user role to give users access to the form being tested, to not allow customization and to designate the user role as a transcriber and set the "Default Author" to "Practitioner 3". Designate this "User Role A".
- Set up a user for each of the 8 practitioners using "User Definition".
- User 1 must be "Practitioner 1" and should not be a transcriber on the "Document Routing" section.
- User 2 must be "Practitioner 2" and should not be a transcriber on the "Document Routing" section.
- User 3 must be "Practitioner 3" and should not be a transcriber on the "Document Routing" section.
- User 4 must be "Practitioner 4" and should be designated a transcriber on the "Document Routing" section and should have "Practitioner 2" assigned as "Default Author" on the "Document Routing" section.
- User 5 must be "Practitioner 5" and should be assigned to "User Role A" and designated a transcriber on the "Document Routing" section.
- User 6 must be "Practitioner 6" and must be designated a transcriber but should have no "Default Author" defined on the "Document Routing" section.
- User 7 must be "Practitioner 7", should be assigned to "User Role A" and should be designated a transcriber and should have the "Default Author" set to "Practitioner 3" on the "Document Routing" section.
- User 8 must be "Practitioner 8", should be assigned to "User Role A" and should be designated a transcriber, the "Default Author" should be set to "Practitioner 2" on the "Document Routing" section.
- All users must be given access to the form being tested on the "Forms and Table" section of the "User Definition" form.
- All users must be set up to have a home view that contains the "MyToDo's" widget.
- Using the "Document Routing Setup" form, enable document routing and allow transcriber for the form being tested.
Steps
- Test 1: User who is a transcriber, but has no default author assigned, client who has no attending practitioner. The result is the Select Author field will be blank.
- Login as "User 6".
- Using the "Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate the "Select Author" field is blank.
- Set "Select Author" to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the author column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 2: User who is a transcriber, and has a default author assigned in the "User Definition" form, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" in the "User Definition".
- Login as "User 4".
- Using the "Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 3: User who is a transcriber, is assigned to a default author assigned in the "User Definition" form, is also assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's default author from "User Definition".
- Login as "User 8".
- Using the "Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 4: User who is a transcriber, is assigned to a user role that has default author assigned, and has the same default author assigned on the user definition form and client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Definition" form.
- Login as "User 7".
- Using the "Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 5: User who is a transcriber, is assigned to a user role that has default author assigned, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Role Definition".
- Login as "User 5".
- Using the "Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 6: User who is a transcriber, is assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's user role default author from "User Role Definition".
- Login as "User 5".
- Using the "Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 7: User who is a transcriber, has no "Default Author" in "User Definition" and a client who does not have an attending practitioner. The result is the Select Author field will default to blank.
- Login as "User 6".
- Using the "Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 8: User who is a transcriber, has no "Default Author" defined client who has an attending practitioner. Author rejected the initial note and returned to transcriber for corrections.
- Login as "User 6".
- Using the "Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Reject the note to send it back to the transcriber.
- Log off and login as "User 6".
- Navigate to the "myToDo's" widget.
- Open the "Treatment Plan" form from the myToDo's item.
- Correct and finalize the note.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User 2".
- Finalize the progress note.
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the progress note.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
Scenario 4: Non Episodic Treatment Plan - Transcriber Default Author
Specific Setup:
- Using the "Practitioner Enrollment" form, create 8 practitioners.
- Admit a client into an outpatient episode, populate the "Attending Practitioner" field with the staff designated as "Practitioner 1" and designate this "Client A".
- Admit a client into an outpatient episode, do not populate the "Attending Practitioner" field and designate this "Client B".
- Using "User Role Definition" add or edit a user role to give users access to the form being tested, to not allow customization and to designate the user role as a transcriber and set the "Default Author" to "Practitioner 3". Designate this "User Role A".
- Set up a user for each of the 8 practitioners using "User Definition".
- User 1 must be "Practitioner 1" and should not be a transcriber on the "Document Routing" section.
- User 2 must be "Practitioner 2" and should not be a transcriber on the "Document Routing" section.
- User 3 must be "Practitioner 3" and should not be a transcriber on the "Document Routing" section.
- User 4 must be "Practitioner 4" and should be designated a transcriber on the "Document Routing" section and should have "Practitioner 2" assigned as "Default Author" on the "Document Routing" section.
- User 5 must be "Practitioner 5" and should be assigned to "User Role A" and designated a transcriber on the "Document Routing" section.
- User 6 must be "Practitioner 6" and must be designated a transcriber but should have no "Default Author" defined on the "Document Routing" section.
- User 7 must be "Practitioner 7", should be assigned to "User Role A" and should be designated a transcriber and should have the "Default Author" set to "Practitioner 3" on the "Document Routing" section.
- User 8 must be "Practitioner 8", should be assigned to "User Role A" and should be designated a transcriber, the "Default Author" should be set to "Practitioner 2" on the "Document Routing" section.
- All users must be given access to the form being tested on the "Forms and Table" section of the "User Definition" form.
- All users must be set up to have a home view that contains the "MyToDo's" widget.
- Using the "Document Routing Setup" form, enable document routing and allow transcriber for the form being tested.
Steps
- Test 1: User who is a transcriber, but has no default author assigned, client who has no attending practitioner. The result is the Select Author field will be blank.
- Login as "User 6".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate the "Select Author" field is blank.
- Set "Select Author" to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the author column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 2: User who is a transcriber, and has a default author assigned in the "User Definition" form, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" in the "User Definition".
- Login as "User 4".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 3: User who is a transcriber, is assigned to a default author assigned in the "User Definition" form, is also assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's default author from "User Definition".
- Login as "User 8".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 4: User who is a transcriber, is assigned to a user role that has default author assigned, and has the same default author assigned on the user definition form and client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Definition" form.
- Login as "User 7".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 5: User who is a transcriber, is assigned to a user role that has default author assigned, client who has an attending practitioner. The result is the Select Author field will default to the "Default Author" from the "User Role Definition".
- Login as "User 5".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 6: User who is a transcriber, is assigned to a user role that has a default author assigned and a client who does not have an attending practitioner. The result is the Select Author field will default to the user's user role default author from "User Role Definition".
- Login as "User 5".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 3".
- Log off and login as "User/Practitioner 3".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 7: User who is a transcriber, has no "Default Author" in "User Definition" and a client who does not have an attending practitioner. The result is the Select Author field will default to blank.
- Login as "User 6".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client B" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the note and sign it.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
- Test 8: User who is a transcriber, has no "Default Author" defined client who has an attending practitioner. Author rejected the initial note and returned to transcriber for corrections.
- Login as "User 6".
- Using the "Non Episodic Treatment Plan" form, generate a progress note for "Client A" and set it to final.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User/Practitioner 2".
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Reject the note to send it back to the transcriber.
- Log off and login as "User 6".
- Navigate to the "myToDo's" widget.
- Open the "Non Episodic Treatment Plan" form from the myToDo's item.
- Correct and finalize the note.
- Validate "Select Author" defaults to "User/Practitioner 2".
- Log off and login as "User 2".
- Finalize the progress note.
- Navigate to the "myToDo's" widget.
- Select the transcription note that has transferred to this practitioner.
- Finalize the progress note.
- Open the "Clinical Document Viewer" form.
- Validate the form displays and prints.
- Validate the "author" column is correctly populated with the author in the SQL table "DocR.transcriber".
|
Topics
• NX • Non-episodic CWS user modeled form • Progress Notes (Group And Individual) • Treatment Plan
|
Console Widgets - Military Time
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission
- Console Widget Configuration (PM)
- Console Widget Configuration (CWS)
- Patient/Family Teaching
Scenario 1: Console Widgets - Validate the 'Enable Military Time' registry setting for user modeled forms
Specific Setup:
- The 'Enable Military Time' registry setting must be enabled. Please note: this must be done by a Netsmart Associate.
- A user modeled form is defined with a 'Time' field (Form A).
- A console widget must be configured for "Form A" in the 'Console Widget Configuration' form (Widget A).
- A view must be defined with "Widget A" and the 'Console Widget Viewer' (View A).
- A client must be enrolled in an existing episode (Client A).
Steps
- Select "Client A" and access "Form A".
- Enter the desired time in the 'Time' field.
- Validate the time displays in military time format.
- Populate all other required and desired fields.
- Click [Submit] and close the form.
- Select "Client A" and navigate to "View A".
- Validate "Widget A" contains the record filed in the previous steps.
- Validate the 'Time' field displays in military time.
- Click [View].
- Validate the 'Console Widget Viewer' displays the data filed in the previous steps.
- Validate the 'Time' field displays in military time.
- Click [Close All].
|
Topics
• Console Widget • Modeling • Console Widget Configuration
|
Document Management - Perceptive 2022.01 Release
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Batch Capture and Indexing
- Client Document Capture
- Document Capture
- Staff Document Capture
- Entity-Based Document Capture
- Document Management Definition
- Family Registration
- Delete Document
Scenario 1: Perceptive Batch Capture and Indexing - JxBrowser enabled
Specific Setup:
- Perceptive storage method must be utilized.
Steps
- Open the "Batch Capture and Indexing" form.
- Click "Capture" to create a new batch.
- Choose "Scanner" for the "Source".
- Click "Open Batch".
- Scan a document
- If Batch Verify is utilized, then click "Send To".
- If Batch Verify is not utilized, then click "Submit".
- If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
- Select the batch that was sent to this queue.
- Open the batch and click "Submit".
- Close form.
- Open the "Batch Capture and Indexing" form.
- Click "Capture" to create a new batch.
- Choose "File" for the "Source".
- Click "Browse" and browse to the location of where the file is stored on the server.
- Click "Open".
- Click "Open Batch".
- If Batch Verify is utilized, then click "Send To".
- If Batch Verify is not utilized, then click "Submit".
- If Batch Verify is utilized, select Avatar Batch Validate in the left-hand pane.
- Select the batch that was sent to this queue.
- Open the batch and click "Submit".
- Close form.
- Open "Chart Review" form for the client and episode that the documents were just scanned and imported for.
- Navigate to the form/category that you want to validate.
- Select a document that was scanned in.
- Validate that the document displays.
- Click the "Print" button.
- Print the document.
- Validate that the printed document matches what displayed on the viewer.
- Select a document that was imported in.
- Validate that the document displays.
- Click the "Print" button.
- Print the document.
- Validate that the printed document matches what displayed on the viewer.
- Open "Clinical Document Viewer".
- Validate you can view and print both the scanned and imported document.
Scenario 2: Perceptive Individual Scanning/Importing/Viewing/Printing through Chart Review
Specific Setup:
- Perceptive storage method must be utilized.
Steps
- Open the "Chart Review" form.
- Select the desired client and episode.
- Open the "Document Capture" form within Chart.
- Scan a document.
- Assign the document to a particular "Document Type".
- Save the document.
- Import a document.
- Assign the document to a particular "Document Type".
- Save the document.
- Navigate to the section designated by the "Document Type" the document was saved under.
- Navigate to the "Episode" tab.
- Open the document(s).
- Validate the document(s) can be viewed and display as scanned.
- Validate the document(s) can be printed and display as scanned.
- Close the document.
- Open the "Clinical Document Viewer".
- Select the desired client and episode.
- Locate the document(s) that were just scanned in or imported.
- Validate the document(s) can be viewed and display as scanned.
- Validate the document(s) can be printed and display as scanned.
- Close the form.
Scenario 3: Client Document Capture - Validation
Specific Setup:
- Perceptive storage method must be utilized.
- A client must be enrolled in an existing episode (Client A).
- A document must exist for import.
Steps
- Access the 'Client Document Capture' form.
- Enter "Client A" in the 'Client ID' field.
- Select any episode for the 'Episode Number' field.
- Click [Launch POS Capture].
- Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
- Click [Import].
- Validate the 'Document Capture' opens in a new window.
- Select any value in the 'Document Type' field.
- Enter any value in the 'Document Description' field.
- Click [Capture] and [Browse].
- Locate the file to be imported and click [Open] and [Done].
- Validate the image displays.
- Click [Save].
- Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
- Close the form.
- Access the undocked 'Clinical Document Viewer' form.
- Validate the form opens in a new window.
- Select "Client" in the 'Select Type' field.
- Select "Individual" in the 'Select All or Individual Client' field.
- Enter "Client A" in the 'Select Client' field.
- Select the episode from the previous steps in the 'Episode' field.
- Click [Process].
- Locate and select the document that was saved in the previous steps.
- Validate the image displays.
- Click [Close All Documents], [Search] and [Close].
Scenario 4: Staff Document Capture - Validation
Specific Setup:
- Perceptive storage method must be utilized.
- There must be a practitioner defined (Practitioner A).
- A document must exist for import.
Steps
- Access the 'Staff Document Capture' form.
- Enter "Practitioner A" in the 'Staff ID' field.
- Click [Launch POS Capture].
- Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
- Click [Import].
- Validate the 'Document Capture' opens in a new window.
- Select any value in the 'Document Type' field.
- Enter any value in the 'Document Description' field.
- Click [Capture] and [Browse].
- Locate the file to be imported and click [Open] and [Done].
- Validate the image displays.
- Click [Save].
- Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
- Access the 'Clinical Document Viewer' form.
- Select "Staff" in the 'Select Type' field.
- Select "Individual" in the 'Select All or Individual Staff' field.
- Select "Practitioner A" in the 'Select Staff' field.
- Click [Process].
- Locate and select the document that was saved in the previous steps.
- Validate the image displays.
- Click [Close All Documents], [Search] and [Close].
- Navigate back to the open 'Staff Document Capture' form.
- Click [Launch POS Capture].
- Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
- Click [Import].
- Validate a second document capture window opens.
- Navigate back to the open 'Staff Document Capture' form.
- Click [Discard].
- Validate the document capture windows close and the form discards.
Scenario 5: Entity-Based Document Capture - Validation
Specific Setup:
- Perceptive storage method must be utilized.
- Select a client, staff, provider, family and performing provider for the tests.
Steps
- Open the "Entity-Based Document Capture" form.
- Select "Client" in the "Entity Type" dropdown.
- Select "Non-episodic" in the "Episode Number" dropdown.
- Click "Launch POS Capture" button.
- Import in a document saved as a file on the server.
- Validate the document renders on screen.
- Select a "Document Type".
- Optionally, set the "Document Description" to desired text.
- Click the "Save" button.
- Validate that messages display indicating the document was successfully saved.
- Click the "Close" button.
- Close the form.
- Open the "Clinical Document Viewer".
- Select the "Client" Entity.
- Select the client from the document capture above.
- Validate a row was added for the document that was just saved.
- View the document to validate it displays as it was captured.
- Print the document to ensure it prints as it was captured.
- Open the "Entity-Based Document Capture" form.
- Select "Staff" in the "Entity Type" dropdown.
- Click "Launch POS Capture" button.
- Import in a document saved as a file on the server.
- Validate the document renders on screen.
- Select a "Document Type".
- Optionally, set the "Document Description" to desired text.
- Click the "Save" button.
- Validate that messages display indicating the document was successfully saved.
- Click the "Close" button.
- Close the form.
- Open the "Clinical Document Viewer".
- Set "Select Type" to "Staff".
- Select the staff from the document capture above.
- Validate a row was added for the document that was just saved.
- View the document to validate it displays as it was captured.
- Print the document to ensure it prints as it was captured.
- Open the "Entity-Based Document Capture" form.
- Select "Performing Provider" in the "Entity Type" dropdown.
- Click "Launch POS Capture" button.
- Import in a document saved as a file on the server.
- Validate the document renders on screen.
- Select a "Document Type".
- Optionally, set the "Document Description" to desired text.
- Click the "Save" button.
- Validate that messages display indicating the document was successfully saved.
- Click the "Close" button.
- Close the form.
- Open the "Clinical Document Viewer".
- Set "Select Type to "Performing Provider".
- Select the client from the document capture above.
- Validate a row was added for the document that was just saved.
- View the document to validate it displays as it was captured.
- Print the document to ensure it prints as it was captured.
- Open the "Entity-Based Document Capture" form.
- Select "Provider" in the "Entity Type" dropdown.
- Click "Launch POS Capture" button.
- Import in a document saved as a file on the server.
- Validate the document renders on screen.
- Select a "Document Type".
- Optionally, set the "Document Description" to desired text.
- Click the "Save" button.
- Validate that messages display indicating the document was successfully saved.
- Click the "Close" button.
- Close the form.
- Open the "Clinical Document Viewer".
- Set "Select Type" to "Provider".
- Select the client from the document capture above.
- Validate a row was added for the document that was just saved.
- View the document to validate it displays as it was captured.
- Print the document to ensure it prints as it was captured.
- Open the "Entity-Based Document Capture" form.
- Select "Family" in the "Entity Type" dropdown.
- Click "Launch POS Capture" button.
- Import in a document saved as a file on the server.
- Validate the document renders on screen.
- Select a "Document Type".
- Optionally, set the "Document Description" to desired text.
- Click the "Save" button.
- Validate that messages display indicating the document was successfully saved.
- Click the "Close" button.
- Close the form.
- Open the "Clinical Document Viewer".
- Set "Select Type" to "Family".
- Select the client from the document capture above.
- Validate a row was added for the document that was just saved.
- View the document to validate it displays as it was captured.
- Print the document to ensure it prints as it was captured.
- Close all forms.
Scenario 6: Chart Review - Document Capture - Scan Nonepisodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Scan a document and identify it was non-episodic.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was scanned.
- Print the document and validate it prints as it was scanned.
- Close the forms.
Scenario 7: Chart Review - Document Capture - Import Non Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Navigate to the "Chart".
- Click "Document Capture".
- Import a non-episodic document.
- Assign a "Document Type" to the document.
- Optionally, add a "Document Description".
- Save the document.
- Validate messages display that indicate the document was successfully saved.
- Select the document type from the list that the document was just saved under.
- Select the document that was just saved from the document list.
- Validate the document displays and prints as it was rendered upon import.
- Close all forms.
Scenario 8: Chart Review - Document Capture - Import Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Import a document and select an episode.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was imported.
- Print the document and validate it prints as it was imported.
- Close the forms.
Scenario 9: Chart Review - Document Capture - Scan Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Scan a document and identify an episode.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was scanned.
- Print the document and validate it prints as it was scanned.
- Close the forms.
Scenario 10: Client Document Capture - Scan Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Scan a document and identify an episode.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was scanned.
- Print the document and validate it prints as it was scanned.
- Close the forms.
Scenario 11: Family Entity - Validation
Specific Setup:
- Perceptive must be installed and configured.
- Family entity must be configured on the perceptive server.
- Using the "Document Management Defaults" form:
- Select "Family" in the "Select Entity Types Allowed" checklist.
- Using the "Document Management Definition" form
- Add new document type(s) for the Family entity documents.
- Using "Family Registration", create a family and add family members.
Steps
- Open the "Entity-Based Document Capture" form.
- Select "Family" in the "Entity Type" field.
- Select the Family created in setup.
- Scan a document.
- Save the document and validate messages are received saying it was saved successfully and added to Avatar.
- Open the "Clinical Document Viewer".
- Retrieve the family document that was scanned in.
- Validate the document displays as it was captured.
- Print the document and validate it prints as it displays.
- Open the "Entity-Based Document Capture" form.
- Select "Family" in the "Entity Type" field.
- Select the Family created in setup.
- Import a document.
- Save the document and validate messages are received saying it was saved successfully and added to Avatar.
- Open the "Clinical Document Viewer".
- Retrieve the family document that was imported in.
- Validate the document displays as it was captured.
- Print the document and validate it prints as it displays.
Scenario 12: Clinical Document Viewer - "Void & Copy" documents
Specific Setup:
- Perceptive is enabled.
- In "User Definition", validate user has permissions to void documents.
- The entity being tested must have imported or scanned documents on file.
Steps
- Access the 'Clinical Document Viewer' form.
- Select the desired entity in the "Entity Type field".
- Select "Individual" in the 'Select All or Individual' entity field.
- Select the desired entity (Client ID, Staff ID, Family ID, etc).
- Click [Process].
- Select a document and view it.
- Click [Void] and then [Void & Copy]
- Select a target entity to copy the document to.
- If the entity is a client, select the desired episode in the 'Select Episode' field.
- Click [Void].
- Validate the document list now has a Status of "Void" for the original document.
- Select the "Search" section.
- Select the target entity.
- Click [Process].
- Validate the copied document is now in the document list for this entity.
- View the copied document and validate it displays as expected.
- Click [Close All Documents].
- Select the "Search" section.
- Click [Close].
Scenario 13: Clinical Document Viewer - "Void" documents
Specific Setup:
- Perceptive is enabled.
- User has permissions to void documents.
- A client must have non-routed documents on file in the 'Clinical Document Viewer' (Client A).
- A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer'.
Steps
- Access the 'Clinical Document Viewer' form.
- Select "Individual" in the 'Select All or Individual Client' field.
- Select "Client A" in the 'Select Client' field.
- Click [Process].
- Select any non-routed document and view it.
- Click [Void] and [Void] again.
- Select the desired value in the 'Void Reason' field.
- Enter the desired value in the 'Void Comments' field.
- Click [Void] and [Close All Documents].
- Select the "Search" section.
- Click [Close].
- Select "Client A" and navigate to the 'All Documents' view.
- Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void".
- Select the document.
- Validate the document displays with "Voided" in the 'Console Widget Viewer'.
Scenario 14: Clinical Document Viewer - View and Print
Specific Setup:
- Select a client who has documents that have been routed, scanned and imported.
Steps
- Open the "Clinical Document Viewer" form.
- Open a document that was imported from a .bmp file.
- Validate you can view and print this document.
- Open a document that was imported from a .gif file.
- Validate you can view and print this document.
- Open any document that was imported from a .jpg file.
- Validate you can view and print this document.
- Open any document that was imported from a .tif file.
- Validate you can view and print this document.
- Open any document that was imported from a .txt file.
- Validate you can view and print this document.
- Open any document that was imported from a .xls file.
- Validate you can view and print this document.
- Open any document that was imported from a .xml file.
- Validate you can view and print this document.
- Open any document that was imported from a .doc file.
- Validate you can view and print this document.
- Open any document that was imported from a .png file.
- Validate you can view and print this document.
- Open any document that was imported from a .docx file.
- Validate you can view and print this document.
- Open any document that was imported from a .xslx file.
- Validate you can view and print this document.
- Open any routed progress note or treatment plan type of document.
- Validate you can view and print this document.
- Open any documents that were imported from a .pdf file.
- Validate you can view and print this document.
- Select 4 random documents to view.
- Validate that all 4 documents open for display and that all of them display.
- Click "Close All Documents".
- Select the same 4 random documents to print.
- Click "Print All".
- Validate all 4 documents preview and print out as if it's one file.
Scenario 15: Clinical Document Viewer - Undocked
Specific Setup:
- Select a test client who has multiple documents on file.
Steps
- Click the "Undocked" icon on the "Clinical Document Viewer" form.
- Open a random document.
- Validate you can view and print the document.
- Select 4 documents to view.
- Validate you can display all 4 documents.
- Select 4 documents to print.
- Validate all 4 documents print as one document.
|
Topics
• Perceptive • Clinical Document Viewer • NX
|
Results To Review To Do List - Removing ToDos
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Order Entry Console
- Results Entry
- Notifications Setup
- Order Code Setup
- Admission
- Order Entry Console - Interactions dialog
- Results Importing
Scenario 1: Validate results in the Lab Results widget
Steps
- Open the "Results Entry" form.
- File a header and then file details to enter a lab order for CBC.
- Validate you can see the order in the "Lab Results" Widget.
Scenario 2: Lab Result ToDos
Specific Setup:
- Using the "Notifications Setup" form:
- Enter a notification for the "Results" notification type.
- Set the "Notification Text" to "<FULL_NAME><PATID>.
- Enter a notification for the "Results (Abnormal)" notification type.
- Set the "Notification Text" to "<FULL_NAME><PATID> has new lab results (Abnormal)".
- Using the "Order Code Setup" form:
- Set up a lab order code called "Comprehensive Metabolic Panel (CMP)".
- Set up a lab order code called "Lipid Panel".
- Admit or select a test client into any episode.
- "Order Entry Console" must be set up on the user's homeview or associated home view.
Steps
- Using the "Order Entry Console", enter a lab order for CMP.
- Complete the order, add it to the scratchpad and Sign the order.
- Note the order number.
- User the "Order Entry Console", enter a lab order for LIPID.
- Complete the order, add it to the scratchpad and Sign the order.
- Note the order number.
- Using the data from the orders entered into the "Order Entry Console", mockup an HL7 import file.
- Import the file using the "Results Importing" file.
- Results ToDos will be generated for the 2 orders included in the mocked up import file.
- Navigate to the "TodDo's" Widget.
- Mark the Results ToDo's as reviewed.
- Note the ToDo's are removed from the ToDo Widget.
|
Topics
• Widgets • Results • NX
|
Internal Utilities
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Envelope Export/Import
|
Topics
• Forms
|
Team File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Team File Import
- Team Definition
Scenario 1: Team Definition Import - Validations
Specific Setup:
- Have a "Team Definition" import file that contains the "Team Finalizer" field populated [ImportA]. (Make a note of the "Team Description" and the user set in the file as the finalizer)
- Have a "Team Definition" import file that does not contain the "Team Finalizer" field populated [ImportB]. (Make a note of the "Team Description" set in the file)
- Have a report created to display data in the "SYSTEM.RADPlus_teams" table
Steps
- Open form "Team File Import"
- Click [Select Import File]
- Navigate to the location of [ImportA] and select the file
- Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
- Close the form
- Open form "Team Definition"
- Click [Select Team]
- Validate [TeamA] is present in the list and select the team
- Validate the "Team ID" is populated. Note the value
- Validate "Team Description" is populated as expected based on the set up
- Validate the "Team Finalizer" field is populated as expected based on the setup
- Validate any other fields set in the import file are displayed as expected
- Close the form
- Open form "Team File Import"
- Click [Select Import File]
- Navigate to the location of [ImportB] and select the file
- Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
- Close the form
- Open form "Team Definition"
- Click [Select Team]
- Validate [TeamB] is present in the list and select the team
- Validate the "Team ID" is populated. Note the value
- Validate "Team Description" is populated as expected based on the set up
- Validate the "Team Finalizer" field is blank, as expected based on the setup
- Validate any other fields set in the import file are displayed as expected
- Close the form
- Run the report created to display data in the "SYSTEM.RADPlus_teams" table
- Validate a row for [TeamA] imported via [ImportA], is displayed
- Validate the "Team ID" is populated.with value noted in step 2a
- Validate "Team Description" is populated as expected based on the set up
- Validate the "Team Finalizer" field is populated as expected based on the setup
- Validate the other fields set in the import file are displayed as expected
- Validate a row for [TeamB] imported via [ImportB], is displayed
- Validate the "Team ID" is populated.with value noted in step 5a
- Validate "Team Description" is populated as expected based on the set up
- Validate the "Team Finalizer" field is blank, as expected
- Validate the other fields set in the import file are displayed as expected
Modeled Form - service documentation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Modeled Form With Service Documentation
- Appointment Move/Delete
Scenario 1: Modeled Form with service documentation - Submission validations when filing a form as "Draft" for an Appointment
Specific Setup:
- Have a modeled form configured and enabled for service documentation
- [TestClient] is enrolled in an episode and has two existing appointments [TestApptA] and [TestAppB]
- User has access to form "Appointment Move/Delete"
Steps
- Access the modeled form.
- Select [TestClient] in the 'Select Client' dialog.
- Select "Existing Appointment" in the 'Data Row For' field.
- Select [TestAppt] in the 'Addresses Which Service/Appointment' field.
- Populate any other desired field
- Select "Draft" in the 'Draft/Final' field.
- Click [Submit].
- Validate the form files successfully
- Access form "Appointment Move/Delete form"
- Select the practitioner for [TestAppt]
- Populate the "Appointment Start Time" and "Appointment End Time" fields s
- Select [TestClient] in the "Client ID" field
- Click the [Appointment Select] button
- Select the row for [TestAppt] in the "Appointment Move/Delete" selection dialog
- Click [OK]
- Click [Delete/Move Appointment] button
- Click [OK]
- Access the modeled form.
- Search for and select "Client A" in the 'Select Client' dialog.
- Select the row submitted in step 1 for edit
- Validate the "Draft/Final" field has "Draft" selected
- Validate 'Addresses Which Service/Appointment' field., no longer has [TestApptA] selected, as expected
- Click 'Addresses Which Service/Appointment' field
- Select [TestApptB]
- Validate the other data fields are now populated as expected, based on data filed for [TestApptB]
- Populate any other desired fields
- Submit the form
- Validate the form files successfully
- Return to the modeled form and select [TestClient]
- Select the row just submitted in step 3
- Validate all fields are populated as expected
- Close the form
User File Import - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User File Import
- Order Entry User Definition
Scenario 1: 'User File Import' - "Staff" user validations
Specific Setup:
- Have a system with "Avatar Order Entry" installed
- Have an existing practitioner [StaffTest] who has not yet been assigned to any user in form "User Definition".
- In form "Practitioner Enrollment", select [StaffTest] and note the "ID#" assigned to the practitioner
- Create a "User File Import" file [ImportA], for a new user [UserA]
- Have the "Practitioner ID" field in the file populated with the "ID#" noted in the previous step
- Create a "User File Import" file [ImportB], for a new user [UserB]
- Leave the "Practitioner ID" field in file unpopulated
- Have a report created, to display data in the "SYSTEM.RADplus_Users" table
- User has access forms "User Definition" and the "Order Entry User Definition"
Steps
- Open the 'User File Import' form.
- Click [Select User Import File].
- Select [ImportA]
- Click [Open].
- Validate the "Import File Scan Results" field indicates the file is ready for import
- Click [Process User Import File]
- Validate message "Import Completed" is displayed
- Click [OK].
- Close the form
- Open form "User Definition"
- Select [UserA]
- Navigate to the "User Caseload" section
- Validate the "Staff Member" field is populated with name of [StaffA] and their "ID#" (noted in the setup)
- Close the form
- Open form "Order Entry User Definition"
- Search for [UserA] in the "Select Order Entry User" field
- Validate [UserA] is found, as expected
- Validate the "Staff Member" field is populated with [StaffA] and their "ID#", as expected
- Close the form
- Open the 'User File Import' form.
- Click [Select User Import File].
- Select [ImportB]
- Click [Open].
- Validate the "Import File Scan Results" field indicates the file is ready for import
- Click [Process User Import File]
- Validate message "Import Completed" is displayed
- Click [OK].
- Open form "User Definition"
- Select [UserB]
- Navigate to the "User Caseload" section
- Validate the "Staff Member" field not populated, as expected
- Close the form
- Open form "Order Entry User Definition"
- Search for [UserB] in the "Select Order Entry User" field
- Validate [UserB] is not found, as expected
- Close the form
- Run the report to display data in the "SYSTEM.RADplus_Users" table
- Validate row is present for [UserA]
- Validate the "staff_member_ID" field is populated with "ID#" imported for [StaffA] in step 1, as expected
- Validate a row is present for [UserB]
- Validate the "staff_member_ID" field is blank, as expected
Modeling - Table Alias fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Modeled Forms - Validate form submission when hiding fields using "Form Designer"
Specific Setup:
- Have a modeled form that contains mapped "Table" aliased fields on the form
- For this example, a form [TestForm] has the following "Service" alias type fields mapped on the form which are necessary to file a service in the modeled form: "Date of Service", "Service Code", "Practitioner, Program", and "Duration"
- Have access to "Form Designer"
- Have a report created to display data in the "SYSTEM.Billing_tx_history" table
Steps
- Open form "Form Designer"
- Select form [TestForm]
- Select the section containing the table aliased fields.
- Highlight the label and text box for "Duration" and uncheck the box
- On left side panel, uncheck the box named "Visible"
- Click [Save]
- Submit the form
- Open [TestForm]
- Select any client [TestClient]
- Complete Date of Service, Service Code, Practitioner, and Program. These are required. Complete any other prompts desired.
- Submit the form as "Final".
- Validate submission is blocked with an error message "Prompt mapped to Duration (Minutes) is missing."
- Close the form
- Open form "Form Designer"
- Select form [TestForm]
- Select the section containing the table aliased fields.
- Highlight the label and text box for "Duration"
- On the left side panel, check the box named "Visible" to unhide the field on the form
- Click [Save]
- Submit the form
- Open [TestForm]
- Select [TestClient]
- Complete "Date of Service", "Service Code", "Practitioner", and "Program".
- Submit as the form as "Final"
- Validate the form files successfully
- Generate the report to display the fields in the "SYSTEM.billing_tx_history" table for [TestClient]
- Validate a new row is found for the service created by the [TestForm] form in the previous steps
- Validate the "Date of Service", "Service Code", "Practitioner, Program", "Duration" and "Join_To_Tx_history" fields are populated as expected
|
Topics
• NX • Service Documentation • User Definition • Modeling
|
State Form Task Scheduler
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: Scheduling a "State Form Definition" file(s) to be sent to an "FTP" Server (File Type - 'SFTP-Password')
Specific Setup:
- Have two state form definition files created in form "State Form Definition" [DefA] and [DefB]
- In form "State Form Definition", [DefA] and [DefB] have the following fields populate:
- The "File Path" field is populated with a directory location [FileLocation], that exists on the logged in users workstation
- In form "State Form Batch Creation" a batch file [Batchfile], has been created that contains state form definition files [DefA] and [DefB]
- 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
Steps
- 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 - Password"
- Based on the valid FTP values stated in the setup, populate the following required fields:
- "Server Host Name"
- "Server Port Number"
- "Server Username"
- "Server Password"
- "Service Directory"
- Click [Test FTP Connection]
- Validate test is successful
- For each FTP field populated in step 1e, enter an invalid value
- Click [Test FTP Connection]
- Validate the test is not successful
- Set the field back to the valid entry
- 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] exists in the folder [FileLocation] on the logged in users server, set in step1
- Open the file
- Validate data results are as expected
- Validate the state form file [DefA] exists in the [Service Directory] location on the "FTP" server, specified in step 1e
- Open the file
- Validate date results are as expected
- Repeat steps 1 and 2, selecting the batch file [DefB]
- When the scheduled start by date and time for task filed has passed:
- Validate the state form file(s) [DefA] and [DefB] exists in the folder [FileLocation] on the logged in users server, set in step1
- Open each file
- Validate data results are as expected
- Validate the state form file [DefA] and [DefB] exists in the [Service Directory] location on the "FTP" server, specified in step 1e
- Open each file
- Validate date results are as expected
State Form Task Scheduler
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- State Form File Generation
- State Form Task Scheduler
- System Task Scheduler
Scenario 1: "State Form Task Scheduler" - Scheduled a task for a' State Form Definition' file (Create File - No)
Specific Setup:
- Have a state form definition file created in form "State Form Definition" [DefinitionA] with the "File Path" field populated with a valid folder location on the Avatar server. Make note of the folder location
Steps
- Open form "State Form Task Scheduler"
- Select "Single Definition" in the "Type" field
- Select the [DefinitionA] from the "Select Batch or Definition" drop down list
- Set field "Create File" to "No"
- Set the "File Description" field to a desired file name
- Select "Static" in the "Change From Date"
- Set the "Static Date" field to today's date
- Select "Static" in the "Change Through Date"
- Set the "Static Date" field to today's date
- Select "Yes" in the "Create File" field
- Click [Submit]
- At the dialog, "Filed. In order for compiles to be run, the new task must be scheduled using the 'System Task Scheduler' form", click [OK]
- Open the "System Task Scheduler" form
- In the "Schedule(s)" field, select the task created in step for [DefinitionA] in step 1
- Select a desired recurrence type pattern from the "Recurrence Pattern" field. For example "Daily"
- Populate a desired value in the "Task Occurrence Sequence".
- Populate the "Start By" field with today's date
- Populate the "Start Time" field with a time later than the current time
- Click [Schedule Task]
- Close the form
- Wait till the "Start Time" set in step 2 has passed
- Open the "State Form File Generation" form.
- Select [DefinitionA] in the "State Form" field
- Select "Dump File" in the "File Generation Options" field
- In the "Select File" field, select the compiled file for [DefinitionA], generated by the automated task set up in step 2
- Click [Process]
- Validate data displayed on the report is as expected
- On the Avatar server:
- Navigate to the folder location noted in the setup, where the state form file was set to be created
- Validate no file was generated, as expected since field "Create File" was set to "No" in step 1c
|
Topics
• State Form Task Scheduler • NX
|
|
Topics
• Progress Notes • Appointment Management • Diagnosis • Site Registration • Practitioner
|
Envelope definition data
Scenario 1: Validate data in the 'SYSTEM.radplus_envelope_info' SQL Table View
Specific Setup:
- Have one or more modeled "Envelopes" defined in form "Envelope Definition" in the "PM" namespace and in any child namespace's. For this test "CWS" and "MSO" have envelopes defined
- The user has permissions assigned to query table view 'SYSTEM.radplus_envelope_info' in their user definition
- Have a report created to display data in table view 'SYSTEM.radplus_envelope_info', in each namespace
Steps
- Open the report created for table view 'SYSTEM.radplus_envelope_info' in the "PM" namespace
- Click to generate the report
- Validate the report reflects all the expected envelopes, defined in that namespace
- Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
- Build Application (Avatar PM)
- Build Environment
- Envelope ID
- Envelope Name
- Envelope (SQL) Schema
- Envelope Version
- Is Envelope Eligible for Export?
- Always Allow Export
- Open the report created for table view 'SYSTEM.radplus_envelope_info' in the "CWS" namespace
- Click to generate the report
- Validate the report reflects all the expected envelopes, defined in that namespace
- Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
- Build Application (Avatar CWS)
- Build Environment
- Envelope ID
- Envelope Name
- Envelope (SQL) Schema
- Envelope Version
- Is Envelope Eligible for Export?
- Always Allow Export
- CDR (SQL) Schema
- Open the report created for table view 'SYSTEM.radplus_envelope_info' in the " MSO" namespace
- Click to generate the report
- Validate the report reflects all the expected envelopes, defined in that namespace
- Validate the following fields are populated for each envelope, based the field values selected in form "Envelope Definition"
- Build Application (Avatar MSO)
- Build Environment
- Envelope ID
- Envelope Name
- Envelope (SQL) Schema
- Envelope Version
- Is Envelope Eligible for Export?
- Always Allow Export
- CDR (SQL) Schema
|
Topics
• SQL Data Access
|
Document Capture - Upload Notification To Dos
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Document Capture
- Document Capture
- User Role Definition
- User File Import
- Admission
Scenario 1: Client Document Capture - Validation
Specific Setup:
- Perceptive storage method must be utilized.
- A client must be enrolled in an existing episode (Client A).
- A document must exist for import.
Steps
- Access the 'Client Document Capture' form.
- Enter "Client A" in the 'Client ID' field.
- Select any episode for the 'Episode Number' field.
- Click [Launch POS Capture].
- Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
- Click [Import].
- Validate the 'Document Capture' opens in a new window.
- Select any value in the 'Document Type' field.
- Enter any value in the 'Document Description' field.
- Click [Capture] and [Browse].
- Locate the file to be imported and click [Open] and [Done].
- Validate the image displays.
- Click [Save].
- Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
- Close the form.
- Access the undocked 'Clinical Document Viewer' form.
- Validate the form opens in a new window.
- Select "Client" in the 'Select Type' field.
- Select "Individual" in the 'Select All or Individual Client' field.
- Enter "Client A" in the 'Select Client' field.
- Select the episode from the previous steps in the 'Episode' field.
- Click [Process].
- Locate and select the document that was saved in the previous steps.
- Validate the image displays.
- Click [Close All Documents], [Search] and [Close].
Scenario 2: Client Document Capture - Scan Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Scan a document and identify an episode.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was scanned.
- Print the document and validate it prints as it was scanned.
- Close the forms.
Scenario 3: Validate Document Upload Notifications
Specific Setup:
- Using the "User Role Definition" form:
- Select a user role.
- Navigate to the "Document Management" section.
- Click "Specify Forms" in the "Forms to Send Upload Notifications".
- Click "Select Forms".
- Select one of the forms to receive upload notifications.
- Using the "User Definition" form, assign the user signed on to the user role defined above.
- Admit or select a test client.
Steps
- Open the "Client Document Capture" form.
- Import or scan in a document for the test client.
- Set the "Document Type" to a form that is set to receive upload notifications for the user.
- Save the document.
- Navigate to the "myToDo's" widget.
- Validate a To Do was generated for the upload notification.
- Select the upload notification item.
- Set the "Set To Do Item to Reviewed" to "Reviewed".
- Click "Submit".
- Navigate to the "myToDo's" widget.
- Validate the Upload Notification To Do item is removed from the widget.
- Open the "Clinical Document Viewer" form.
- Locate and display the document that was just saved.
- Validate it displays appropriately.
Scenario 4: Validate Delayed Document Upload Notification
Specific Setup:
- Using the "User Role Definition' form:
- Select a user role.
- Navigate to the "Document Management" section.
- Click "Specify Forms" in the "Forms to Send Upload Notifications".
- Click "Select Forms".
- Select one of the forms to receive upload notifications.
- Using the "User Definition" form, assign the user signed on to the user role defined above.
- Admit or select a test client.
Steps
- Open the "Client Document Capture" form.
- Import or scan in a document for the test client.
- Set the "Document Type" to a form that is set to receive upload notifications for the user.
- Save the document.
- Navigate to the "myToDo's" widget.
- Validate a To Do was generated for the delayed upload notification.
- Select the delayed upload notification item.
- Set the "Set To Do Item to Reviewed" to "Reviewed".
- Click "Submit".
- Navigate to the "myToDo's" widget.
- Validate the Delayed Upload Notification To Do item is removed from the widget.
- Open the "Clinical Document Viewer" form.
- Locate and display the document that was just saved.
- Validate it displays appropriately.
Clinical Data Repository (CDR) - Remove DocM and DocR schema tables from the Clinical Data Repository
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Document Capture
- Client Document Capture
Scenario 1: Client Document Capture - Scan Episodic
Specific Setup:
- Perceptive must be configured and enabled.
Steps
- Open the "Chart Review" form.
- Select the desired client.
- Navigate to the "Chart".
- Click "Document Capture".
- Scan a document and identify an episode.
- Note the document type.
- Save the document.
- Click the document type the document was just saved under.
- Locate the document that was just saved.
- Validate the document displays as it was scanned.
- Print the document and validate it prints as it was scanned.
- Close the forms.
Scenario 2: Removing DocR and DocM tables from CDR
Delete/Re-Assign To Do Items - Acknowledgment To Dos no longer displayed
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
- Admission
- Delete/Re-Assign To Do Items
Scenario 1: Progress Note (Group and Individual) - Document Routing - Validate "Acknowledgement" To-Do functionality
Specific Setup:
- A client must be admitted in an existing episode. (Client A)
- Must have two users defined with associated staff members (User A and User B). Must be logged in as "User A".
- Document routing must be enabled for the 'Progress Note (Group and Individual)' form in 'Document Routing Setup' with the following fields set.
- Have the 'Approver Required' field set to "Yes".
- Have the 'Acknowledgment Allowed' field set to "Yes".
- Have the 'Allow Notifications When Final' field set to "No".
- Have the 'Allow Comments During Approval' field set to "No".
Steps
- Select "Client A" and 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.
- Populate any required and desired fields.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note] and [Accept and Route].
- Enter the password associated with "User A" and click [Verify].
- Enter the practitioner associated to "User A" in the 'Add Approver' field and click [Add].
- Verify the 'Add Members to Acknowledge' field is present.
- Search for the practitioner associated to "User B" using only one letter in the 'Add Members to Acknowledge' field.
- Click [Add] and [Submit].
- Close the form.
- Navigate to the 'My To Do's' widget.
- Validate there is a To-Do for the progress note filed in the previous steps.
- Click [Approve Document].
- Validate the 'Document Preview' contains the progress note data filed in the previous steps.
- Click [Accept].
- Enter the password associated with "User A" and click [Verify].
- Validate the To-Do is no longer present.
- Log out.
- Login as "User B" and navigate to the 'My To Do's' widget.
- Validate there is a To-Do for the progress note filed in the previous steps.
- Click [Acknowledge Document] and [Acknowledge].
- Enter the password associated with "User B" and click [Verify].
- Validate the To-Do is no longer present.
Scenario 2: Delete/Re-Assign Ackknowledgement To Dos
Specific Setup:
- Admit or select a test client.
- Using the "Document Routing Setup" form, enable document routing.
- Enable acknowledgments by setting the field "Acknowledgement Allowed" to "Yes".
- Set "Verification Level of Acknowledgment" to "Warn User if Acknowledgement is missing"
- Set "Days after finalized document to alert" to "Y".
- File the form.
- Using "Dictionary Update", print the dictionary for the data element Note Type (10751).
- Locate a note type that says it requires a signature.
Steps
- Open the Progress note form that was used during setup.
- Create a progress note.
- Set the "Note Type" to one the requires a signature.
- Set the "Draft/Final" field to "Final".
- Select "Caseload Practitioners" from the "Add Members to Acknowledge".
- Set "Add Approver" to a valid practitioner.
- Validate the Practitioner chosen in Add Members to Acknowledge" listbox has "Acknowledge" check marked.
- Submit the form to route the document.
- Navigate to the "myToDo's" widget.
- Select the To do that was just generated.
- Click the "Accept" button.
- Click the "Sign" button.
- Close the To Do widget.
- Sign off of Avatar.
- Log back in as the user that you designated as an approver.
- Navigate to the "myToDo's" widget.
- Locate the To do generated for this test.
- Click "Accept".
- Click "Sign".
- Log off of Avatar.
- Log back on as the user who was designated to receive the acknowledgment To Do.
- Navigate to the "myToDo's" widget.
- Validate it contains the "Acknowledgment Document To do.
- Open the " Delete/Re-Assign To Do Items" form.
- Set "Delete/Re-Assign" to "Delete".
- Set "Select User" to the user who received the Acknowledgment To Do".
- Select a To Do to be deleted.
- Add a comment as to why it's being deleted.
- Navigate to the "myToDo's" widget and validate the to do was removed.
Background Notification Task - Infinite Loop when an error is encountered
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Document Capture
- Document Capture
- User Role Definition
- User File Import
- Admission
Scenario 1: Client Document Capture - Validation
Specific Setup:
- Perceptive storage method must be utilized.
- A client must be enrolled in an existing episode (Client A).
- A document must exist for import.
Steps
- Access the 'Client Document Capture' form.
- Enter "Client A" in the 'Client ID' field.
- Select any episode for the 'Episode Number' field.
- Click [Launch POS Capture].
- Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
- Click [Import].
- Validate the 'Document Capture' opens in a new window.
- Select any value in the 'Document Type' field.
- Enter any value in the 'Document Description' field.
- Click [Capture] and [Browse].
- Locate the file to be imported and click [Open] and [Done].
- Validate the image displays.
- Click [Save].
- Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
- Close the form.
- Access the undocked 'Clinical Document Viewer' form.
- Validate the form opens in a new window.
- Select "Client" in the 'Select Type' field.
- Select "Individual" in the 'Select All or Individual Client' field.
- Enter "Client A" in the 'Select Client' field.
- Select the episode from the previous steps in the 'Episode' field.
- Click [Process].
- Locate and select the document that was saved in the previous steps.
- Validate the image displays.
- Click [Close All Documents], [Search] and [Close].
Scenario 2: Validate Document Upload Notifications
Specific Setup:
- Using the "User Role Definition" form:
- Select a user role.
- Navigate to the "Document Management" section.
- Click "Specify Forms" in the "Forms to Send Upload Notifications".
- Click "Select Forms".
- Select one of the forms to receive upload notifications.
- Using the "User Definition" form, assign the user signed on to the user role defined above.
- Admit or select a test client.
Steps
- Open the "Client Document Capture" form.
- Import or scan in a document for the test client.
- Set the "Document Type" to a form that is set to receive upload notifications for the user.
- Save the document.
- Navigate to the "myToDo's" widget.
- Validate a To Do was generated for the upload notification.
- Select the upload notification item.
- Set the "Set To Do Item to Reviewed" to "Reviewed".
- Click "Submit".
- Navigate to the "myToDo's" widget.
- Validate the Upload Notification To Do item is removed from the widget.
- Open the "Clinical Document Viewer" form.
- Locate and display the document that was just saved.
- Validate it displays appropriately.
Scenario 3: Validate Delayed Document Upload Notification
Specific Setup:
- Using the "User Role Definition' form:
- Select a user role.
- Navigate to the "Document Management" section.
- Click "Specify Forms" in the "Forms to Send Upload Notifications".
- Click "Select Forms".
- Select one of the forms to receive upload notifications.
- Using the "User Definition" form, assign the user signed on to the user role defined above.
- Admit or select a test client.
Steps
- Open the "Client Document Capture" form.
- Import or scan in a document for the test client.
- Set the "Document Type" to a form that is set to receive upload notifications for the user.
- Save the document.
- Navigate to the "myToDo's" widget.
- Validate a To Do was generated for the delayed upload notification.
- Select the delayed upload notification item.
- Set the "Set To Do Item to Reviewed" to "Reviewed".
- Click "Submit".
- Navigate to the "myToDo's" widget.
- Validate the Delayed Upload Notification To Do item is removed from the widget.
- Open the "Clinical Document Viewer" form.
- Locate and display the document that was just saved.
- Validate it displays appropriately.
Delete/Re-Assign To Do Items - Notification To Dos no longer displayed
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Delete/Re-Assign Notification To Dos
Specific Setup:
- Select a client for this test.
Steps
- Open the "Send To Do Notification" form.
- Select the test client.
- Enter text into the "To Do Message" field.
- Select the user logged in as in the "Select User" field.
- Click "Add User" button.
- Validate the user was added to the "Send To" text box.
- Click "File To Do" button.
- Navigate to the "myToDo's" widget.
- Validate the To Do that was just generated is contained in the widget.
CareFabric - SendCareConnectClientDocument action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Transfer Queue Configuration
- Document Management Definition
Scenario 1: Disable Transfer Queue - Overwrite existing document
|
Topics
• Document Scan/Import • Document Management • Perceptive
|
RADPlus - Family Entity Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Change MR#
- Family Registration
- Delete Last Movement
- Table Definition (PM)
- Family Entity User Modeled Form
- Delete Family
Scenario 1: Change MR# - "Family" Entity Data validations
Specific Setup:
- Have an active test client on the system [ClientA], note their current PatID# [OrigPatID#]
- In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
- Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
- A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved
- Have a report [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
Steps
- Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is a row displayed for [FamilyA] and [ClientA]
- Open "Change MR#" form in Avatar PM.
- Select [ClientA] in the "Client ID" field and note their current PatID# [OrigPatID#]
- Click [Assign MR#].
- Note the new PatID# assigned, [NewPatID#]
- Click [Submit].
- Validate the form files successfully
- At the home view, search for the [OrigPatID#] noted in step 3a
- Validate there are no results
- Now search for the [NewPatID#] noted in step 3b
- Validate the [NewPatID#] is found and the associated client is [ClientA]
- Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is a row displayed for [FamilyA] and with new PatID# [NewPatID#] displayed for [ClientA]
Scenario 2: Client Delete - "Family" Entity Data validations
Specific Setup:
- Have an active test client on the system [ClientA]
- In form "Family Registration", have a family created [FamilyA] with [ClientA] added as a family member in "Family Members" section of the form.
- Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
- A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved
- Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table
- User has launched [ReportA] and has logged into the system
Steps
- Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is a row displayed for [FamilyA] and [ClientA]
- Open "Client Delete" form.
- Select [ClientA] in the "Client ID" field.
- Validate an error message is received "Client Must Be Removed From All Families Before Client Can Be Deleted."
- Click [OK]
- Close the form
- Open form "Family Registration"
- Select [FamilyA]
- Click the "Family Members" section
- Select the row for [ClientA]
- Click [Delete]
- Validate the client is removed as a family member
- Submit the form
- Open "Client Delete" form.
- Select [ClientA] in the "Client ID" field.
- Validate an error message is received "All Movements must be deleted before Client can be deleted"
- Click [OK]
- Close the form
- Open form "Delete Last Movement"
- Select [ClientA]
- Select the admission episode from the "Episode Number" drop down list
- Click [Submit]
- Click [Yes] to continue
- Validate the form submits successfully
- Open "Client Delete" form.
- Select [ClientA] in the "Client ID" field.
- Click [Submit]
- Validate the form submits successfully
- At the home view, search for [ClientA]
- Validate there are no results
- Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is no longer a row displayed for [FamilyA] and [ClientA]
Scenario 3: "Family" Entity User Modeled Form - Create a new form
Specific Setup:
- In form "Family Registration" have a family created [FamilyA] with one or more clients added as family member's in "Family Members" section of the form.
For this test, [ClientA], [ClientB] and [ClientC] are used
Steps
- Open form "Envelope Definition"
- Click the [New Avatar Envelope]
- Set the "Envelope Description" field to the desired name [EnvelopeA], for the envelope
- Select "Family" in the "Entity Database" field
- Click the "Yes - Is Envelope Eligible for Export" radio button
- Click the "Yes - Always Allow Export" radio button
- Click [Submit]
- Validate the form files successfully
- Open form "Table Definition"
- At the "Select Avatar Table" prompt enter the desired table name [TableA]
- Click the [New Avatar Table] button
- From the "Envelope" dialog drop down list, select [EnvelopeA]
- Populate the "Table Name" field with the desired table name [TableA]
- Populate the "Table Description" field with the desired description of the table
- Select the "Column Definition" section
- Click the [Add New Item] button
- Select "Family Member(s)" column from the "Type of Column" drop down list
- Populate the "Column Name" field
- Populate the "Column Description" field
- Populate the "Column Label" field
- Validate the "Column Definition" grid contains a row with values just populated
- Click the [Add New Item] button
- Select "Draft/Final (Document Routing)" column from the "Type of Column" drop down list
- Populate the "Column Name" field
- Populate the "Column Description" field
- Populate the "Column Label" field
- Validate the "Column Definition" grid contains a row with values just populated
- Repeat step 4 for any other desired prompts to be added from the "Type of Column" drop down list
- Validate results are as expected
- Click [Submit]
- Validate the form files successfully
- Open form "Form Definition"
- At the "Select Avatar Table" prompt enter the desired form name [FormA]
- Click the [New Avatar Form] button
- From the "Envelope" dialog drop down list, select [EnvelopeA]
- Populate the "Table Name" field with the desired table name [TableA]
- Populate the "Table Description" field with the desired description of the table
- Select a menu location for the form from the "Menu to Place Form Under" field
- Populate the "Form Name" field [FormA]
- In the "Primary Table" field, select [TableA]
- Click the "Pre-display" section
- Select one or more pre-display columns from the "Primary Table Pre-display" column prompts
- Click the "Section Definition" section
- Click [Add New Item] and populate the "Section Description" field
- Click the "Object Definition" section
- Click [Add New Item]
- From the "Table Column" field, select the "Family Member's" column
- Validate the "Object Definition" grid reflect the column added
- From the "Table Column" field, select the "Draft/Final" column
- Validate the "Object Definition" grid reflect the column added
- Repeat step b adding any other columns desired from the "Table Column" field
- Validate the "Object Definition" grid reflect the columns added
- Click [Submit]
- Validate the form files successfully
- Open [FormA]
- At the "Select Family" prompt, select [FamilyA]
- Validate the form loads successfully
- Verify the "Family Member's" field is present and contains each client added as a family member in the set up, along with a check box next to their name.
- Verify the "Draft/Final" field is present on the form.
- Verify any other fields added during "Form Definition" are present on the form, as expected.
- Select values for any desired fields on the form
- Submit the form
- Validate the form files successfully.
Scenario 4: "Family" Entity User Modeled Form- Form submission and Doc Routing Validations
Specific Setup:
- The "Document Management Defaults" form has "Family - User Defined Family" selected in the field "Select Entity Types Allowed"
- The "Document Management Definition" form has been submitted with a "Form Name" [FName] associated to the "Family" entity in the "Entity Database" field.
- In form "Family Registration" have a family created [Family] with family members added in "Family Members" section of the form. For the test [ClientA] and [ClientB]
- Have a user modeled form [Form] created based on the "Family - User Defined Family" entity database
- [Form] contains fields from [Table] that include a "Family Member(s)" column type, a field using a "Draft/Final" column type and any other desired field types
- [Form] is enabled for document routing with form name [FName] selected in the "Select Type" field
- [User] is a staff member who has access to [Form] and [Table]
- [User] has the "My To do's" widget on their home view
- Have a report [Report], set to display data in the "SYSTEM.user_modelled_fam_members" table
- Log in as [User]
Steps
- Access [Form]
- In the "Select Family" prompt, select [Family]
- Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB]
- Click "All", to select all members
- Populate any other desired fields on the form
- Select "Draft" in the 'Draft/Final' field.
- Click [Submit]
- Validate the form files successfully
- Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is a row displayed for [Family] and [ClientA]
- Validate there is a row displayed for [Family] and [ClientB]
- Access [Form]
- In the "Select Family" prompt, select [Family]
- In the pre-display screen, click [Edit] to select the row filed in step 1
- Validate all fields are populated, as expected
- Close the form
- Access [Form]
- In the "Select Family" prompt, select [Family]
- In the pre-display screen, select the row filed in step1
- Click [Delete]
- Validate the row is removed from the pre-display
- Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate the row field for [Family] and [ClientA], has been deleted
- Validate the row field for [Family] and [ClientB], has been deleted
- Access [Form]
- In the "Select Family" prompt, select [Family]
- Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB]
- Click "All", to select all members
- Populate any other desired fields on the form
- Select "Final in the 'Draft/Final' field.
- Click [Submit] and then [OK]
- Validate the "Confirm Document" screen displays all data submitted, including clients [ClientA] and [ClientB] listed in the "Family Member's field.
- Click [Accept and Route]
- Enter the password for the user in the 'Password' field and click [OK].
- At the "Route Document to" dialog, add [User] as an approver
- Click [Submit]
- Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table
- Validate there is a row displayed for [Family] and [ClientA]
- Validate there is a row displayed for [Family] and [ClientB]
- Navigate to the "My To Do's" widget
- Click the "New" tab
- Validate the To Do for [Form] is present in the list
- Validate the "Client" column indicates [Family]
- Click [Approve Document]
- Validate the document displays all data submitted, including clients [ClientA] and [ClientB] in the "Family Member's" field.
- Click [Accept]
- Validate the To Do is removed the widget, as expected
- In the "My Clients" widget, select any one of the clients selected as a family member in submission of [Form] in step 1. For example [Client]
- Double click on the client to open their "Chart"
- In the "Documents" section on left side panel, click the form type [Fname], associated with [Form]
- Locate the row listed for the document approved for [Form] in step 2
- Click the "View" check box and then the [View] button to display the document
- Validate the document displays all the data submitted as expected
- Close the chart
Scenario 5: Delete Family - Form (Submission and Validations)
Specific Setup:
- Have an active test client on the system [ClientA]
- In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
- Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing
- File a row for [FamilyA], selecting [ClientA] selected in the "Family Members" field and routing the document to [UserA] to create To do
- [UserA] has the "My To do's" widget on their home view
- Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table
- [UserA] has launched [ReportA] and has logged into the system
Steps
- Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
- Verify a data row is displayed for the row filed in the set up for [FamilyA] that includes [ClientA]
- On the home view, validate a To do exists in the "My To do's" widget for the row filed in [FormA] in the set up
- Open form "Delete Family"
- Select [FamilyA]
- Validate an error message is displayed stating "The Family has members on file. You must delete all family members in the Family Registration form prior to deleting the family"
- Click [OK]
- Open form "Family Registration"
- Select [FamilyA]
- Click the "Family Members" section
- Select each family member row and click delete to remove the row
- Submit the form
- Open form "Delete Family"
- Select [FamilyA]
- Click [Submit]
- At the "Delete Family" dialog, click [Yes]
- Validate the message "Family has been Deleted" displays
- Click [OK]
- Open form "Delete Family"
- Search for [FamilyA]
- Validate [FamilyA] is not found
- Return to the "My To Do's" widget
- Validate a To do is no longer present for [FormA] for [ClientA]
- Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table
- Verify there are no rows displayed for [FamilyA]
|
Topics
• Client Merge • NX • Database Tables
|
Console Widget Viewer - Perceptive enabled
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- HomeView - Documents Widget
- HomeView - Console Widget Viewer
Scenario 1: Console Widget Viewer - validate print preview and print output
Specific Setup:
- User has the 'Primary All Documents Widget' and the 'Console Widget Viewer' on their myDay view.
- "Client A" has data filed in various forms.
Steps
- Select "Client A" and access the 'Primary All Documents Widget'.
- Select the 'All Forms' tab.
- Select the first desired form, for example 'Diagnosis'.
- Click [Print Current].
- In the 'Console Widget Viewer', validate the print preview displays as expected without any truncation.
- Select several other desired forms.
- Click [Print All].
- In the 'Console Widget Viewer', validate the print preview displays as expected for all forms, without any truncation.
- Click [Print].
- Validate the printed forms display as expected, without any truncation.
Scenario 2: Console Widget Viewer - Retrieving and printing documents from Perceptive enabled system
Specific Setup:
- This update is to be tested in a Perceptive enabled system.
- Add the "Documents Widget" and the "Console Widget Viewer" to the user's home view using "View Definition".
Steps
- Generate a progress note document using one of the progress note forms.
- Navigate to the "Documents Widget" on the user's home view.
- Locate the progress note created for this test.
- Highlight that row in the widget.
- Click "View".
- Validate the document is retrieved and displays in the "Console Widget Viewer".
- Click "Print" to print the document to a printer.
- Validate the printed output matches the document displayed in the "Console Widget Viewer".
|
Topics
• Console Widget • Perceptive
|
Support is added for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Final to Draft Override (CWS)
- Final to Draft Override (PM)
Scenario 1: Final to Draft Override - Form Validations
Specific Setup:
- A modeled form is defined with the 'Draft/Final' prompt (Form A).
- A client is enrolled in an existing episode (Client A).
Steps
- Select "Client A" and access "Form A".
- Populate all required and desired fields.
- Select "Final" in the 'Draft/Final' field.
- Click [Submit].
- Access the 'Final to Draft Override' form.
- Select "Form A" in the 'Form' field.
- Select "Client A" in the 'Entity Lookup' field.
- Click [Select Row].
- Select the finalized record filed in the previous steps and click [OK].
- Validate the 'Row Contents' field contains the values entered in the previous steps.
- Enter the desired value in the 'Override Reason' field.
- Click [Submit].
- Select "Client A" and access "Form A".
- Select the record filed in the previous steps and click [Edit].
- Validate "Draft" is now selected in the 'Draft/Final' field.
- Close the form.
|
Topics
• Final to Draft Override
|
Form Definition - Event Logic
Scenario 1: Form Definition - Event Logic setup and validations
Specific Setup:
- Have a "Modeled" form [ModeledForm], that contains three fields that will be used to set up a "Calculation Type" event in "Form Definition". For this test, the following fields are set up:
- [FieldA] - a "Dictionary" field
- [FieldB] - an "Integer" field
- [FieldC]- a "Decimal" field
Steps
- Open "Form Definition" and select the [ModeledForm]
- Click the "Section Def" tab and select the section with fields defined in the setup
- Click the "Object Def" tab
- Select [FieldB]. This will be the field that will trigger the calculation event
- Click to the "Event" section and click the [Add Item] button
- Set the "Type of Event" field to "Result of Input with Value Checking"
- Set the "Compare with for Event" field, select "Specific Value"
- Set the "Specific Value" field to a desired value that will be used to trigger the event. For this test "!0" is used
- Set the "Relationship to Comparison Value to Trigger Event" select "Equal To"
- Set the "Set Value to Specific Table Value on Event" to "Yes"
- Set the "Table Value to Have Value Changed on Event" to [FieldC]. (This will be the field populated with the result of the calculation)
- Set the "Table Column Value To" to "Calculation Result"
- Set the Calculation Type" to "Addition"
- Click the "Left Operand" field
- Validate [FieldC] is present and select that value
- Click "Submit" to file the form
- Validate the form files successfully
- Re-open "Form Definition"
- Click the "Section Def" tab and select the section with fields defined in the setup
- Click the "Object Def" tab
- Select [FieldB]
- Click to the "Event" section
- Validate each field value selected in step 1d is populated as expected
- Close the form
- Open the [ModeledForm]
- Navigate to [FieldA] and enter any value. For this test "4" is used
- Navigate to [FieldB] enter a value other than "10", which was the trigger value set up
- Validate [FieldC] is not populated
- Navigate back to [FieldB] and enter "10"
- Validate [FieldC] is populated with addition result of [FieldA] plus [FieldB], as expected. In this test, "14" was validated
- Submit the form
- Return to the [ModledForm]
- Select the row just submitted in step 3
- Validate all fields are populated as expected
Chart View - Data display
Scenario 1: Chart View - Form data validations
Specific Setup:
- Have a copy of the "Treatment Plan" form [TPlanCopy] created using form "Create New Treatment Plan"
- Have a modeled table[MTable] that includes any desired field types and also includes the "Selection Leaf" field that points to [TPlanCopy]. For this example: "Selection Leaf: TPlanCopy" would be listed for selection.
- Create a "Modeled" form [MForm] that includes all the fields table [MTable]
- Have a treatment plan filed in treatment plan[TPlanCopy] for a client [TestClient], that includes "Problem", "Goal", "Objective" and an "Intervention" tree view items submitted in the form
- Have the user with access to the modeled form [MForm]
- Have the modeled form [MForm] added to the users chart view
Steps
- Select client [TestClient]
- Open modeled form [MForm]
- Click the [Select Treatment Plan Item] button
- Validate a "Tab" is opened named with the name of the treatment plan copy created in the set up [TPlanCopy]
- Validate the data displayed contains the "Problems", "Goals", "Objective", "Interventions" tree view data submitted in the setup
- Validate the data displayed for each tree item is as expected and listed in a readable format
- Select the last tree item, "Interventions", this will bring in all connected tree items
- Click the [Return] button
- In the "Selection Leaf" field text box
- Validate the "Problems", "Goals", "Objective", "Interventions" tree view data is displayed as expected, and in a readable format
- Submit the form
- Validate the form files successfully
- Re-open [MForm] for client [TestClient]
- Select the row just submitted
- Validate all fields are populated, as expected
- Close the form
- Open "Chart" view for client [TestClient]
- Select [MForm] on the left side forms list
- Validate the data under the "Select Leaf:" field includes the "Problems", "Goals", "Objective", "Interventions" tree view data as expected
- Validate the data is in a readable paragraph format, with each item (Problem, Goal, Objective, etc) starting on a separate line.
- Validate data in any other fields are displayed as expected
Envelope Import - Mapped Dictionaries
Scenario 1: Envelope Export/Import - Validate forms that contain "Mapped" dictionary fields
Specific Setup:
- Have a server with two Avatar instances setup [SystemA] and [SystemB]
- [SystemA] has several programs set up in form "Program Maintenance" that include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
- [SystemB] has several programs set up in form "Program Maintenance" but they do not include programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)"
- [SystemA] contains two modeled "Envelopes"
- [EnvelopeA] contains [FormA], it includes a dictionary field [FormA_Dict1] which is mapped to the "(10011) Program" dictionary
- [EnvelopeB] contains [FormB], it contains a dictionary field [FormB_Dict1] that is mapped to the mapped dictionary "[FormADict1]" set up in [FormA]
- Both envelopes have been exported from [SystemA] and the export files have saved on the server
- User has logged in [SystemB]
Steps
- Open form "Envelope Import"
- Click [Select Envelope Import File]
- Navigate to the location of [EnvelopeA] and select the file
- Select "Create New"
- Click "Begin Import Scan"
- Validate there are no errors or warnings in the scan results
- Click [Begin Import]
- Validate the envelope imports successfully
- Repeat steps 1 for [EnvelopeB]
- Validate the results are as expected
- Open [FormA]
- Navigate to field [FormADict1]
- Validate programs "ProgramA(800)", "ProgramB(900) and "ProgramC(950) are not displayed in the field, as expected
- Select any other program
- Submit the form
- Return to [FormA]
- Select the row just submitted
- Validate field [FormADict1] contains the expected value
- Close the form
- Open [FormB]
- Navigate to field [FormBDict1]
- Validate programs, "ProgramA(800)", "ProgramB(900) and "ProgramC(950)" are not displayed in the field, as expected
- Select any other program
- Submit the form
- Return [FormB]
- Select the row just submitted
- Validate field [FormBDict1] contains the expected value
- Close the form
Form "Display User"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Display User
- User Display Report
Scenario 1: "Display User" Form - "User Display" report data validations
Specific Setup:
- Have a user [UserA] who is not assigned to a user role
- Have another user [UserB] who is assigned to a user role [RoleA]
- Have another user [UserC] who is assigned to a user role [RoleB]
- In form "User List Management", have or create a new user list [Userlisttest] with following users submitted in the form
- In the "Workflow Users" section, add [UserA]
- In the "Workflow User Roles" section, add [RoleA] but do not add [RoleB]
- Logged in user has access to form "Display User"
Steps
- Open form "Display User"
- In field "Individual or All Users", click the "Individual" radio button
- In the "Select User" field, select [UserA]
- Click the [Display User(s)] button
- Validate the "User Display" report generates successfully and in a timely manner
- Validate the "User ID" field is populate with [UserA]
- Validate the "User Description" field is populated as expected
- Validate the "Associate With User Role" field is set to "No", as expected
- Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
- Close the report
- In the "Select User" field, select [UserB]
- Click the [Display User(s)] button
- Validate the "User Display" report generates successfully and in a timely manner
- Validate the "User ID" field is populate with [UserB]
- Validate the "User Description" field is populated as expected
- Validate the "Associate With User Role" field is set to "Yes"
- Validate the "User Role" field is populated with [RoleA], as expected
- Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
- Close the report
- In the "Select User" field, select [UserC]
- Click the [Display User(s)] button
- Validate the "User Display" report generates successfully and in a timely manner
- Validate the "User ID" field is populate with [UserC]
- Validate the "User Description" field is populated as expected
- Validate the "Associate With User Role" field is set to "Yes"
- Validate the "User Role" field is populated with [RoleB], as expected
- Validate the "Workflow Notification User Lists" field is populated with the [Userlisttest] user list, as expected
- Close the report
Importing Images in Forms
Scenario 1: Validate Images imported and submitted in a forms
Specific Setup:
- Have a form that contains a "Primary" and a "Multiple Iteration" section, with each section containing a "Picture" field and any other desired fields.
- Have "Autosave" is enabled on the form
- Have three image files(for example ".JPG" images) available for import, [ImageA], [ImageB] and [ImageC]
- A client [TestClient], is admitted in an active episode
Steps
- Open the form
- Select [TestClient] and then select the episode
- Select the primary section of the form
- Navigate to the "Picture" field and import [ImageA]
- Populate any other desired fields in the section
- Navigate to the multiple-iteration section of the form
- Click [Add] to add a row [Row1]
- Navigate to the "Picture" field and import [ImageB]
- Populate any other desired fields
- Click [Add] to add another row [Row2]
- Navigate to the "Picture" field and import [ImageC]
- Populate any other desired fields
- Wait for "Autosave" to automatically trigger or click the [Backup] button
- Validate an "Autosave" message is displayed indicating the time of the backup
- Close the form
- Open the form
- Select [TestClient] and then select the episode
- Validate a message displays: "You have an unsubmitted backup of this data record. Do you wish to restore from the backup?"
- Click [Yes]
- Navigate to primary section of the form
- Validate the "Picture" field is populated with [ImageA]
- Validate all other fields are populates as expected
- Navigate to the multiple-iteration section of the form
- Select [Row1]
- Validate the "Picture" field is populated with [ImageB]
- Validate all other fields are populated as expected
- Select [Row2]
- Validate the "Picture" field is populated with [ImageC]
- Validate all other fields are populated as expected
- Click [Submit]
- Validate the form files successfully
- Return to the form
- Select [TestClient] and then select the episode
- Navigate to primary section of the form
- Validate the "Picture" field is populated with [ImageA]
- Validate all other fields are populates as expected
- Navigate to the multiple-iteration section of the form
- Select [Row1]
- Validate the "Picture" field is populated with [ImageB]
- Validate all other fields are populates as expected
- Select [Row2]
- Validate the "Picture" field is populated with [ImageC]
- Validate all other fields are populates as expected
- Close the form
|
Topics
• Modeling • NX • Chart Review • Forms • Envelope Import • User Definition • User Role Definition • Auto Save
|
State Form Query Logging - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- State Form File Generation
- State Form Query Logging
Scenario 1: 'State Form Query Logging' form - Functionality and validations
Specific Setup:
- Have a system with two state form file definitions created in form "State Form Definition" [SFileA] and [SFileB]
- [SFileA] is a definition that contains one record [Rec]
- [SFileB] is a definition that contains two records [Rec] and [Rec2]
- Have a report to display data in the "RADplus_sf_audit_query" table, sorted by the "ID" field and displaying the fields "ID", "Query" and "Rec"
Steps
- Open form "State Form File Generation"
- Select definition [SFileA] in the "State Form" field. (Make a note of the file "ID" number located next to the state form file name)
- Select "Compile" in the "File Generation Options" field
- Populate the "File Description" field
- Click [Process]
- At the "Compile Complete" dialog, click [OK]
- Open form "State Form Query Logging"
- Select definition [SFileA] in the "State Form" field
- Validate the "Record" filed is automatically populated with the record name [Rec]. (Make a note of the record name)
- Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
- Close the form
- Run the report created to query table "RADplus_sf_audit_query" table
- In the "ID" column, locate the row that contains a value starting with the definition "ID" for [SFileA], noted in step 1a
- Validate the "Record" field value matches the value noted in step 2a
- Validate the "Query" field value matches the value noted in step 2a
- Close the report
- Open form "State Form File Generation"
- Select definition [SFileB] in the "State Form" field. (Make a note of the file "ID" number, located next to the state form file name)
- Select "Compile" in the "File Generation Options" field
- Populate the "File Description" field
- Click [Process]
- At the "Compile Complete" dialog, click [OK]
- Open form "State Form Query Logging"
- Select definition [SFileB] in the "State Form" field
- Click the "Record" field
- Validate there are two records for selection, as expected. [Rec] and [Rec2]
- Select [Rec]
- Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
- Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
- Navigate back to the "Record" field
- Select [Rec2]
- Validate the "Record" field is automatically populated with the record name [Rec]. (Make a note of the record name)
- Validate "Query" field is populated with the expected SQL query based on the table and selection criteria being executed in the record, [Make a note of the query displayed]
- Run the report created to query table "RADplus_sf_audit_query" table
- In the "ID" column, locate the row(s) that contains a value starting with the definition "ID" for [SFileB], noted in step 4a
- Validate a row is found for record name [Rec]
- Validate the "Query" field value for record [Rec] matches the value noted in step 5a
- Validate a row is also found for record name [Rec]
- Validate the "Query" field value for record [Rec2] matches the value noted in step 5a
- Close the report
'State Form Parameters Definition' - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- State Form Parameter Definition
- State Form File Generation
- State Form Definition
Scenario 1: 'State Form Parameters Definition" form - Functionality and validations
Specific Setup:
- In form "Update Client Data", have one or more clients on the system that have any "Date", "Single-Select" field and "Multi-Select" field populated. For this test the following fields will be used:
- "Martial Status", single-select field
- "Date of Birth", date field
- "Other Languages", multi-select field
- Have a state form definition file [StateFile] set up in form "State Form Definition", that extracts "PATID", "Name", "Marital Status", "Date of Birth" and "Other Languages" from the "SYSTEM.patient_current_demographics" table
- In form "State Form Definition", edit file [StateFile]
- Navigate to the "Define Record Table" section of the definition and
- Select the row defined containing the "SYSTEM.patient_current_demographics" table
- Navigate to the "Additional SQL Conditions" column and populate the field with the following SQL parameter "p.marital_status_code={?Param1}"
- Submit the form
Steps
- Open form "State Form Parameter Definition"
- Select [StateFile] in the "State Form Definition" field
- Select "Add New" in the "Select Parameter" field
- Set the "Parameter Description" field to a desired name for the single-select field. For this example, "Marital Status"
- Validate the "Parameter Number" field contains "1"
- Validate the "Parameter Reference" field contains "{?Param1}"
- Select "Single Select Dictionary" in the "Parameter Type" field
- Select "Yes" in the "Required" field
- In the "Entity Database" field, select "Client"
- Search and select "(10) Marital Status" from the "Dictionary" field
- Select "Active" in the "Status" field
- Click the [File] button
- Validate the form submits successfully
- Open form "State Form File Generation" and select [StateFile] in the "State Form" field
- Click the "Compile" radio button in the "File Generation Options" field
- Set the "File Description" field to the desired name. For example, "Married Clients File"
- Click the Process button
- The user is prompted with a "Select Values - Dialog"
- Validate the "Martial Status" dictionary selection list is displayed
- Select the desired marital status and click [OK]
- Click [OK] at the "Compile Complete" message
- In the "File Generation Options" field, select the "Dump File" radio button
- Click [Process]
- Validate the "Data Dump File - Report" contains only clients with a "Martial Status" field equal to the value selected in the previous step
- Close the report
- Open form "State Form Definition", edit the state form file [StateFile]
- Navigate to the "Define Record Table" section of the definition and
- Select the row defined containing the "SYSTEM.patient_current_demographics" table
- Navigate to the "Additional SQL Conditions" column and replace the previous SQL parameter with one for the "Date" field. For this test enter "p.other_lang_code={?Param2}"
- Open form "State Form Parameter Definition"
- Select [StateFile] in the "State Form Definition" field
- Select "Marital Status" in the "Select Parameter" field, entered in step 1
- Click [Delete] to removed it
- Click the "Select Parameter" field and select "Add New"
- Validate the "Parameter Number" field contains "1"
- Validate the "Parameter Reference" field contains "{?Param1}"
- Set the "Parameter Description" field to a desired name for the multi-select field. For this example, "Other Languages"
- Select "Multi-Select Dictionary" in the "Parameter Type" field
- Select "Yes" in the "Required" field
- In the "Entity Database" field, select "Client"
- Search and select the multi-select field, for this test,"(149) Primary Language" is selected
- Select "Active" in the "Status" field
- Click the [File] button
- Validate the form submits successfully
- Open form "State Form File Generation" and select [StateFile] in the "State Form" field
- Click the "Compile" radio button in the "File Generation Options" field
- Set the "File Description" field to the desired name. For example, "Other Languages File"
- Click the [Process] button
- The user is prompted with a "Select Values - Dialog"
- Validate the "Other Languages" dictionary selection list is displayed
- Select the desired values and click the [OK] button
- Click [OK] at the "Compile Complete" message
- In the "File Generation Options" field, select the "Dump File" radio button
- Click [Process]
- Validate the "Data Dump File - Report" contains only clients that have the "Other Languages" field populated with the value(s) selected in the previous step
- Close the report
- Open form "State Form Definition", edit the state form file [StateFile]
- Navigate to the "Define Record Table" section of the definition and
- Select the row defined containing the "SYSTEM.patient_current_demographics" table
- Navigate to the "Additional SQL Conditions" column and replace the previous SQL parameter with one for the "Date" field. For this test enter "p.date_of_birth={?Param1}"
- Submit the form
- Open form "State Form Parameter Definition"
- Select [StateFile] in the "State Form Definition" field
- Select "Other Languages" in the "Select Parameter" field, entered in step 1
- Click [Delete] to removed it
- Click the "Select Parameter" field and select "Add New"
- Validate the "Parameter Number" field contains "1"
- Validate the "Parameter Reference" field contains "{?Param1}"
- Set the "Parameter Description" field to a desired name for the multi-select field. For this example, "Date of Birth"
- Select "Date" in the "Parameter Type" field
- Select "Yes" in the "Required" field
- Select "Active" in the "Status" field
- Click the [File] button
- Validate the form submits successfully
- Open form "State Form File Generation" and select [StateFile] in the "State Form" field
- Click the "Compile" radio button in the "File Generation Options" field
- Set the "File Description" field to the desired name. For example, "Date of Birth File"
- Click the [Process] button
- The user is prompted with a "Select Values - Dialog"
- Validate the "Date of Birth" input field is displayed
- Enter the desired date and click [OK]
- Click [OK] at the "Compile Complete" message
- In the "File Generation Options" field, select the "Dump File" radio button
- Click [Process]
- Validate the "Data Dump File - Report" contains only clients that contain a date of birth equal to value populated in the previous step
- Close the report
'State Form Definition Versioning' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- State Form Definition
- State Form Definition Versioning
- Enter a description of any changes made- Dialog
Scenario 1: State Form Definition - Import/Export
Specific Setup:
- Have a state form definition file created in form "State Form Definition". [SFDefFile]
Steps
- Open form "State Form Definition"
- Click section "State Form Definition File Import/Export"
- Select [SFDefFile] from the "Select State Form For Export" field
- Click [Export State Form]
- Click [Save] to save the file [SFileExp] to a folder
- Close the form
- Open form "State Form Definition"
- Select [SFDefFile] for edit
- Navigate to any field on the form and note its current value. For example the "File Type" field
- Enter or select a new value in the field
- Submit the form
- Open form "State Form Definition"
- Select [SFDefFile] for edit
- Validate the change made to the field in step 2 is present as expected
- Close the form
- Open form "State Form Definition"
- Click section "State Form Definition File Import/Export"
- Click [Select File for Import]
- Navigate to the location of the export file [SFileExp]
- Select the file
- Click [Open]
- Click [Process Import]
- Validate message "Import Complete" is displayed
- Close the form
- Open form "State Form Definition"
- Select [SFDefFile] for edit
- Validate the change made to the field in step 2, has returned to its original value
- Close the form
Scenario 2: "State Form Definition Versioning" form - Functionality and validations
Specific Setup:
- A state form file definition file exists, created in form "State Form Definition" [StateFormFile]
Steps
- Open form "State Form Definition Versioning"
- Select [StateFormFile] from the "State Form Definition" field
- Click "Create New Version" in the "Action" field
- Validate the "Version Number" field is set to "1"
- Click "Create New Subversion"
- Validate a message stating a subversion cannot be created until the initial version is created is displayed
- Click [OK]
- Click "Create New Version"
- Populate the "Version Description" field
- Submit the form
- Return to form "State Form Definition Versioning"
- Select [StateFormFile] from the "State Form Definition" field
- Click "Create New Subversion"
- Validate a message is displayed stating that the current version must be finalized before a subversion can be created
- Click [OK]
- Click "Finalize Version
- Validate a message is displayed stating that once this form is submitted, the definition cannot be modified until a new version is created.
- Click [OK]
- Click [Submit]
- Return to form "State Form Definition Versioning"
- Select [StateFormFile] from the "State Form Definition" field
- Click "Create New Subversion" in the "Action" field
- Validate the "Version Number" field contains "1.01"
- Populate the "Version Description" text field
- Submit the form
- Open form "State Form Definition"
- Select [StateFormFile] from the "State Form Definition" field
- Validate the "Version Number" field contains "1.01"
- Change any field value on the form. For this example the "File Type" was changed from "Delimited" to "XML"
- Click the [File Form] button
- In the "Enter a description of any changes made" dialog, enter a description of the change
- Click the OK button
- Close the form
- Open form "State Form Definition Versioning"
- Select [StateFormFile] from the "State Form Definition" field
- Validate the "Version Number" field has a value of "1.01"
- Validate the "Change Log" text box contains: "Version 1.01", the description of the change, the time/date of the change and name of the user who filed the change
- Click "Restore Version" in the "Action" field
- Select "1" from the "Select Version" field
- Submit the form
- Open form "State Form Definition"
- Select [StateFormFile] from the "State Form Definition" field
- Validate the "Version Number" field has a value of "1"
- Validate the field value change made in step 4, has been reverted back to its original value. (For this test, the "File Type" field value has been reverted back to its original value of "Delimited")
- Close the form
- Open form "State Form Definition Versioning"
- Select [StateFormFile] from the State Form Definition field
- Click "Restore Version" in the "Action" field
- Select "1.01" from the "Select Version" field
- Submit the form
- Open form "State Form Definition"
- Select [StateFormFile] from the "State Form Definition" field
- Validate a warning is displayed "Definition is currently final, editing is not permitted unless a new version is created in the 'State Form Definition Versioning' form.
- Validate the [File Form] and the [Delete Form] buttons are disabled
- Validate the field value change made in step 4 has returned. (For this test, the "File Type" field value has returned to changed value of "XML" made in step 4)
- Close the form
- Open form "State Form Definition Versioning"
- Select [StateFormFile] from the State Form Definition field
- Validate the "Version Number" field is populated with "1"
- Click "Delete Version" in the "Action" field
- Submit the form
- Click "Yes" to return to the form
- Select [StateFormFile] from the State Form Definition field
- Validate the "Version Number" field is populated with "1.01"
- Click "Restore Version" in the "Action" field
- Validate message "No additional versions found for selected definition" is displayed
- Click [OK]
- Close the form
|
Topics
• NX • State Form Tools • State Forms
|
'Client Merge' process
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Service Documentation Form
- Admission
Scenario 1: Validate 'Client Merge' for clients with appointments linked via Service Documentation to CWS modeled forms
Specific Setup:
- A client is enrolled in an existing episode (Client A).
- A second client is enrolled in an existing episode and has the same name as "Client A" (Client B).
- A CWS modeled form configured for service documentation must be defined with a 'Draft/Final' field (Service Documentation Form).
- The 'Attach Selected Appointment To Service Documentation On Draft' registry setting is set to "1" or "2".
Steps
- Access the 'Scheduling Calendar' form.
- Right click in any available time slot and click [Add Appointment].
- Select "Client A" in the 'Client' field.
- Populate any other required and desired fields.
- Click [Submit].
- Validate the appointment for "Client A" is displayed.
- Click [Dismiss].
- Select "Client A" and access the "Service Documentation Form".
- File an existing appointment note for the appointment filed in the previous steps.
- Select "Draft" in the 'Draft/Final' field.
- Click [Submit].
- Access the 'Client Merge' form.
- Select "Client A" in the 'Source Client' field.
- Select "Client B" in the 'Target Client' field.
- Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
- Select "Yes" in the 'Create New Episode On Merge' field.
- Click [File].
- Validate a message is displayed stating: Do you wish to continue with the indicated action?
- Click [Yes].
- Validate a message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
- Click [OK] and close the form.
- Select "Client B" and access the 'Service Documentation Form'.
- Select the new episode created on merge.
- Validate the note filed in the previous steps is displayed in the Pre-Display.
- Click [Edit].
- Validate all previously filed data is displayed.
- Close the form.
|
Topics
• Scheduling Calendar • Client Merge
|
Dynamic Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Dynamic Form - Validations
Specific Setup:
- User has access forms, "Basic Troubleshooting", "Treatment Plan" and "Member Enrollment"
Steps
- Open form "Basic Troubleshooting"
- Click the [Test Dynamic Forms] button
- Validate message "Test Successful", is displayed
- Click the [OK] button
- Set the "Duration (minutes)" field to "1"
- Click the [Submit] button
- Verify the message window "Submitting... Please Wait", is displayed
- Wait "1" Minute
- Verify the message window "Submitting... Please Wait" closes and the user is returned to the home screen
- Open the "Treatment Plan" form and select the desired client in the "Select Client" search field
- Populate the "Plan Date" field
- Populate any other desired fields
- Set the "Draft/Final" to "Draft"
- Click the Launch Plan button
- Click the [Add New Problem] button
- Click the [Return to Plan] button
- Validate the "Plan Saved" message is displayed and click [OK]
- Set the "Draft/Final" field to "Final"
- Click [Submit]
- Validate the message "Cannot finalize plan until the following required fields are completed"
- Click the OK button
- Populate any missing required fields
- Click the [Submit] button
- Validate the form files successfully
- Open the Member Enrollment - Avatar MSO / Membership Management form
- Populate the "Last Name" field with a name that is not on file yet as a member
- Populate the "First Name" field
- Populate the Sex" field
- Click the Search button
- Validate the message "Search Results - No Matches found", is displayed
- Click [OK] button
- Click the New Client button
- Click the Auto Assign ID Number - Yes button
- Validate the "Name" field is populated as expected
- Populate any other desired fields
- Submit the form
- Validate the form files successfully
|
Topics
• Forms • Cache
|
Update installation
Scenario 1: Product Updates: Validate import, view, and install update(s)
Specific Setup:
- Have a system that requires loading an update in the parent namespace and any child namespace
Steps
- Open form "Product Updates"
- Click [Select Application]
- Select the parent application "Avatar PM"
- Click [Select Update/Customization Pack]
- Browse to the location of the ".GSA" file
- Click [OK]
- Click [Review Update/Customization Pack Contents]
- Validate the results in the "Review Update/Customization Pack Contents" text box are as expected for the update being loaded
- Click [Print Update/Customization Pack Contents]
- Validate the print dialog displays the same results as the "Print Update/Customization Pack Contents" text box
- Click [Print]
- Validate the report prints successfully and displays the same results as the "Print Update/Customization Pack Contents" text box
- Click [OK]
- Click [Dismiss] to return to form
- Click [Install Update Customization Pack]
- Validate message "Update Loaded" is displayed
- Click [OK]
- Open form "Current Server" in "Avatar PM"
- Navigate to the "Updates" list section
- Click the search text editor icon
- In the update listing search for the update installed in step 1
- Validate the update is found, as expected
- Close the form
- Repeat steps 1 thru 3 for each child namespace update
- Validate results are as expected
Scenario 2: "Product Updates" form 'Pre-load' functionality - validations
|
Topics
• Cache
|
Console Widget Viewer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Delete Last Movement
- Admission
Scenario 1: "Console" Widgets - View form data in the "Console Widget Viewer"
Specific Setup:
- Have a client already admitted in four active episodes. [Ep1], [Ep2], [Ep3] and [Ep4]
- In form "Console Widget Configuration" create a console widget for an episodic based form [WAdmit]. For this test, an "Admission" form widget is used
- The logged in user has access to form "Delete Last Movement"
- The logged in user has the console widget [WAdmit] and the "Console Widget Viewer" widget on their home view or on an additional view
Steps
- At the home view, select the client
- In the "Episode" selection field on the menu bar, select "All Episodes"
- Refresh the [WAdmit] widget
- Validate rows for all four episodes are displayed
- Click the [View] button for each episode row
- Validate the "Console Widget Viewer" displays the expected data for each episode
- Open form "Delete Last Movement"
- Select [Ep2]
- Complete and submit the form
- Repeat step 2 for [Ep3]
- Refresh the [WAdmit] widget
- Validate only admission rows for [Ep1] and [Ep4] are present
- Click the [View] button for each row
- Validate the "Console Widget Viewer" displays the expected data for each episode
- Select the client and open the "Admission" form
- Populate all the required fields to admit the client to any program to create a new episode [Ep5]
- Submit the form
- Validate the form files successfully
- Repeat step 5, admitting the client to any other program to create another episode [Ep6]
- At the home view, select the client
- In the "Episode" selection field on the menu bar, select "All Episodes"
- Refresh the [WAdmit] widget
- Validate rows for [Ep2] and [Ep3] are not present as expected
- Validate rows for [Ep1], [Ep4] are present
- Validate the two new episode admission for [Ep5] and [Ep6] are also present
- Click the [View] button for each episode row in the widget
- Validate the "Console Widget Viewer" displays the expected data for each episode
Scenario 2: "All Documents" Widget - View form data in the "Console Widget Viewer"
Specific Setup:
- Have a client already admitted in four active episodes. [Ep1], [Ep2], [Ep3] and [Ep4]
- Have an episodic form included in the "All Documents" widget. For this test, the "Admission" form is used
- The logged in user has the "All Documents" widget and the "Console Widget Viewer" widget on their home view or an additional view
- The logged in user has access to the "Delete Last Movement" and the "Admission" forms
Steps
- At the home view, select the client
- In the "Episode" selection field on the menu bar, select "All Episodes"
- Navigate to the "All Documents" Widget
- Select the "Admission" form from the "Form Description" column form list
- Validate rows for all four episodes are displayed
- Click the [View] button for each episode row
- Validate the "Console Widget Viewer" displays the expected data for each episode
- Open form "Delete Last Movement"
- Select [Ep2]
- Complete and submit the form
- Repeat step 2 for [Ep3]
- At the home view, select the client
- In the "Episode" selection field on the menu bar, select "All Episodes"
- Navigate to the "All Documents" Widget
- Select the "Admission" form from the "Form Description" column form list
- Validate only admission rows for [Ep1] and [Ep4] are present
- Click the [View] button for each episode row
- Validate the "Console Widget Viewer" displays the expected data for each episode
- Select the client and open the "Admission" form
- Populate all the required fields to admit the client to any program to create a new episode [Ep5]
- Submit the form
- Validate the form files successfully
- Repeat step 7, admitting the client to any other program to create another episode [Ep6]
- At the home view, select the client
- In the "Episode" selection field on the menu bar, select "All Episodes"
- Navigate to the "All Documents" Widget
- Select the "Admission" form from the "Form Description" column form list
- Validate rows for [Ep2] and [Ep3] are not present as expected
- Validate rows for [Ep1], [Ep4] are present
- Validate the two new episode admission for [Ep5] and [Ep6] are present
- Click the [View] button for each episode row in the widget
- Validate the "Console Widget Viewer" displays the expected data for each episode
|
Topics
• Console Widget • Console Widget Configuration • NX • All Documents Widget
|
Product Updates - form compiles
Scenario 1: "Product Updates" form - Post installation validations
Product Update - On hold
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Product Updates - Validate the "Guardiant" product update check functionality
|
Topics
• Forms • Guardiant
|
Product Updates - form compiles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Product Updates' Form - Installation and post installation validations
Specific Setup:
- Have a system where a product update [TestUpdate] will be installed that compile a form or forms. For example an update that will require compiling "Modeled" forms.
Steps
- Open form "Product Updates"
- Click [Select Application]
- Select the desired application
- Click [Select Update/Customization Pack]
- Browse to the location containing the ".GSA" file for [TestUpdate]
- Click [OK]
- Click [Review Update/Customization Pack Contents]
- Validate the results in the "Review Update/Customization Pack Contents" text box are as expected for the update being loaded
- Click [Install Update Customization Pack]
- Validate message "Update Loaded" is displayed
- Click [OK]
- Close the form
- Open form "Current Server" in application the update was installed in
- Navigate to the "Updates" list section
- Click the search text editor icon
- In the update listing search for the update installed in step 1
- Validate the update is found, as expected
- Close the form
- Open form "Print Error Log"
- Select today's date
- Run the report
- Validate there are no errors
- Locate any form that may have been recompiled by the product update. For example a "Modeled" form
- Populate the fields on the form
- Submit the form
- Validate the form files successfully
- Return to the form
- Select the row just submitted
- Validate all fields are populated, as expected
|
Topics
• Update Install • NX
|
Registry Setting - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Site Specific Section Modeling Import/Export (CWS)
- Form Designer (CWS)
- Progress Notes (Group and Individual)
Scenario 1: Registry Settings - submission of a registry setting
Steps
- Access the 'Registry Settings' form.
- In the "Limit Registry Settings to the Following Search Criteria" field, enter any keyword to find a desired registry setting
- Click [View Registry Settings].
- Validate the registry setting is displayed as expected and in a timely manner
- Note the current value of the setting and change it to a new value
- Click [Submit].
- Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing.
- Click [OK]
- Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
- Click [Yes].to return to the form
- In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1
- Validate the value changed in step 1b is present, as expected
- Click [Submit].
- Validate a "Registry Editor Filing" dialog is displayed stating: Successful filing.
- Click [OK]
- Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
- Click [Yes].to return to the form
- In the "Limit Registry Settings to the Following Search Criteria", select the same registry setting updated in step 1
- Validate the value submitted in step 2b is present, as expected
- Close the form
|
Topics
• Registry Settings • NX
|
| |