Skip to main content

RADplus 2023 Update 20

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Recommended Update Level

RADplus 2019 Update 35

Product Update Form Description

The following issues are resolved: An instance of NOTOPEN EDIT+8^GUIPRE which occurs in User Modeled forms with Service Documentation for a Draft row associated to an Appointment which was subsequently deleted. User File Import may not associate a Staff Member ID to a User ID, resulting in the User not appearing in Order Entry searches. Table Alias validation does not show an error which submission is blocked because a prompt required for the Table Alias is hidden with Form Designer edits and left unanswered.

Included Updates

None

Required Updates

None

Details
NEW0 CHANGED0 FIXED4
Fixed (4)
Team File Import
An issue is resolved to ensure that a team file imported in form "Team File Import" which does not a value in the "Team Finalizer" field, displays no value when querying the "RADplusTeams" table
Topics
• NX
 
Modeled Form - service documentation
An issue is resolved to ensure a row filed for an appointment as "Draft" in a modeled form with service documentation, can be edited successfully if the appointment submitted in the form had been subsequently deleted
Topics
• NX • Service Documentation
 
User File Import - form
"User File Import" is updated to ensure that a user contained in the import file who is associated to a staff member, can successfully be found when searching in an "Order Entry" user search field KB0072117 v0.01
Topics
• NX • User Definition
 
Modeling - Table Alias fields
An issue is resolved to ensure when filing a form as "Final" that contains "Table Alias" fields that have any required fields which are hidden via "Form Designer", the user will be alerted and prevented from submitting the form
Topics
• Modeling • NX
 
Acceptance Tests
AV-82292 Summary | Details
Team File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Team Definition
  • Team File Import
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
  1. Open form "Team File Import"
  2. Click [Select Import File]
  3. Navigate to the location of [ImportA] and select the file
  4. Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
  5. Close the form
  6. Open form "Team Definition"
  7. Click [Select Team]
  8. Validate [TeamA] is present in the list and select the team
  9. Validate the "Team ID" is populated. Note the value
  10. Validate "Team Description" is populated as expected based on the set up
  11. Validate the "Team Finalizer" field is populated as expected based on the setup
  12. Validate any other fields set in the import file are displayed as expected
  13. Close the form
  14. Open form "Team File Import"
  15. Click [Select Import File]
  16. Navigate to the location of [ImportB] and select the file
  17. Validate the "Team Import File Scan Results" field indicates "No errors detected in import file."
  18. Close the form
  19. Open form "Team Definition"
  20. Click [Select Team]
  21. Validate [TeamB] is present in the list and select the team
  22. Validate the "Team ID" is populated. Note the value
  23. Validate "Team Description" is populated as expected based on the set up
  24. Validate the "Team Finalizer" field is blank, as expected based on the setup
  25. Validate any other fields set in the import file are displayed as expected
  26. Close the form
  27. Run the report created to display data in the "SYSTEM.RADPlus_teams" table
  28. Validate a row for [TeamA] imported via [ImportA], is displayed
  29. Validate the "Team ID" is populated.with value noted in step 2a
  30. Validate "Team Description" is populated as expected based on the set up
  31. Validate the "Team Finalizer" field is populated as expected based on the setup
  32. Validate the other fields set in the import file are displayed as expected
  33. Validate a row for [TeamB] imported via [ImportB], is displayed
  34. Validate the "Team ID" is populated.with value noted in step 5a
  35. Validate "Team Description" is populated as expected based on the set up
  36. Validate the "Team Finalizer" field is blank, as expected
  37. Validate the other fields set in the import file are displayed as expected
Topics
• NX
AV-83794 Summary | Details
Modeled Form - service documentation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Appointment Move/Delete
  • Modeled Form With Service Documentation
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
  1. Access the modeled form.
  2. Select [TestClient] in the 'Select Client' dialog.
  3. Select "Existing Appointment" in the 'Data Row For' field.
  4. Select [TestAppt] in the 'Addresses Which Service/Appointment' field.
  5. Populate any other desired field
  6. Select "Draft" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate the form files successfully
  9. Access form "Appointment Move/Delete form"
  10. Select the practitioner for [TestAppt]
  11. Populate the "Appointment Start Time" and "Appointment End Time" fields s
  12. Select [TestClient] in the "Client ID" field
  13. Click the [Appointment Select] button
  14. Select the row for [TestAppt] in the "Appointment Move/Delete" selection dialog
  15. Click [OK]
  16. Click [Delete/Move Appointment] button
  17. Click [OK]
  18. Access the modeled form.
  19. Search for and select "Client A" in the 'Select Client' dialog.
  20. Select the row submitted in step 1 for edit
  21. Validate the "Draft/Final" field has "Draft" selected
  22. Validate 'Addresses Which Service/Appointment' field., no longer has [TestApptA] selected, as expected
  23. Click 'Addresses Which Service/Appointment' field
  24. Select [TestApptB]
  25. Validate the other data fields are now populated as expected, based on data filed for [TestApptB]
  26. Populate any other desired fields
  27. Submit the form
  28. Validate the form files successfully
  29. Return to the modeled form and select [TestClient]
  30. Select the row just submitted in step 3
  31. Validate all fields are populated as expected
  32. Close the form
Topics
• NX • Service Documentation
AV-84188 Summary | Details
User File Import - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry User Definition
  • User Definition
  • User File Import
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
  1. Open the 'User File Import' form.
  2. Click [Select User Import File].
  3. Select [ImportA]
  4. Click [Open].
  5. Validate the "Import File Scan Results" field indicates the file is ready for import
  6. Click [Process User Import File]
  7. Validate message "Import Completed" is displayed
  8. Click [OK].
  9. Close the form
  10. Open form "User Definition"
  11. Select [UserA]
  12. Navigate to the "User Caseload" section
  13. Validate the "Staff Member" field is populated with name of [StaffA] and their "ID#" (noted in the setup)
  14. Close the form
  15. Open form "Order Entry User Definition"
  16. Search for [UserA] in the "Select Order Entry User" field
  17. Validate [UserA] is found, as expected
  18. Validate the "Staff Member" field is populated with [StaffA] and their "ID#", as expected
  19. Close the form
  20. Open the 'User File Import' form.
  21. Click [Select User Import File].
  22. Select [ImportB]
  23. Click [Open].
  24. Validate the "Import File Scan Results" field indicates the file is ready for import
  25. Click [Process User Import File]
  26. Validate message "Import Completed" is displayed
  27. Click [OK].
  28. Open form "User Definition"
  29. Select [UserB]
  30. Navigate to the "User Caseload" section
  31. Validate the "Staff Member" field not populated, as expected
  32. Close the form
  33. Open form "Order Entry User Definition"
  34. Search for [UserB] in the "Select Order Entry User" field
  35. Validate [UserB] is not found, as expected
  36. Close the form
  37. Run the report to display data in the "SYSTEM.RADplus_Users" table
  38. Validate row is present for [UserA]
  39. Validate the "staff_member_ID" field is populated with "ID#" imported for [StaffA] in step 1, as expected
  40. Validate a row is present for [UserB]
  41. Validate the "staff_member_ID" field is blank, as expected
Topics
• NX • User Definition
AV-84427 Summary | Details
Modeling - Table Alias fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (CWS)
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
  1. Open form "Form Designer"
  2. Select form [TestForm]
  3. Select the section containing the table aliased fields.
  4. Highlight the label and text box for "Duration" and uncheck the box
  5. On left side panel, uncheck the box named "Visible"
  6. Click [Save]
  7. Submit the form
  8. Open [TestForm]
  9. Select any client [TestClient]
  10. Complete Date of Service, Service Code, Practitioner, and Program. These are required. Complete any other prompts desired.
  11. Submit the form as "Final".
  12. Validate submission is blocked with an error message "Prompt mapped to Duration (Minutes) is missing."
  13. Close the form
  14. Open form "Form Designer"
  15. Select form [TestForm]
  16. Select the section containing the table aliased fields.
  17. Highlight the label and text box for "Duration"
  18. On the left side panel, check the box named "Visible" to unhide the field on the form
  19. Click [Save]
  20. Submit the form
  21. Open [TestForm]
  22. Select [TestClient]
  23. Complete "Date of Service", "Service Code", "Practitioner", and "Program".
  24. Submit as the form as "Final"
  25. Validate the form files successfully
  26. Generate the report to display the fields in the "SYSTEM.billing_tx_history" table for [TestClient]
  27. Validate a new row is found for the service created by the [TestForm] form in the previous steps
  28. Validate the "Date of Service", "Service Code", "Practitioner, Program", "Duration" and "Join_To_Tx_history" fields are populated as expected
Topics
• Modeling • NX