Skip to main content

Avatar Data Warehouse Update 26

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar Data Warehouse required
Avatar PM required
RADplus required
Avatar Cal-PM

Product Update Description

The following changes are made: 1) The Data Warehouse has been updated to support new functionality within the 2024.1.001 Data Warehouse Incremental Middleware. 2) The Data Warehouse background process has been improved to stay in sync with changes within myAvatar. 3) The error "[UNDEFINED]Compare+21^DssLiabilityUpdate" which can occur when liability is being calculated for a service has been resolved. 4) An issue has been resolved where the 'Data Warehouse Transient Comparison Configuration' form was not displaying all transient fields for selected tables within the 'Compare Columns' field.

Required Updates

None

Included Updates

2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 11.1, 12, 13, 13.1, 14, 15, 16, 17, 18, 19, 20, 21, 23, 24

Details
NEW1 CHANGED1 FIXED3
New (1)
Data Warehouse - Globals
Data Warehouse Globals are reset not include globals ^DssIncCompile and ^DssIncView.
Please Note: "Avatar Data Warehouse Middleware Update 2024.1.001" is needed for full functionality
Value Added: Improves Data Warehouse Global utilization
Topics
• Data Warehouse
 
Changed (1)
Data Warehouse Global
The ^CSMZSTU("GUIZSTU","DssIncJournalFileDump") global is removed permanently . Please Note: "Avatar Data Warehouse Middleware Update 2024.1.001" is needed for full functionality
Value Added: Improves Data Warehouse Global utilization
Topics
• Data Warehouse
 
Fixed (3)
Progress Note - service note
An issue that could occur when a progress note was submitted for a service, is resolved KB0075472 v0.01
Please Note: "Avatar Data Warehouse Middleware Update 2024.1.001" is needed for full functionality
Topics
• Progress Notes
 
Data Warehouse - table validation
An issue is resolved where a data record submitted in the "cw_patient_notes" on the database server, may not be present on the "Data Warehouse" server, after the "Data Warehouse" Middleware process was run KB0069894 v0.01
Please Note: "Avatar Data Warehouse Middleware Update 2024.1.001" is needed for full functionality
Topics
• Data Warehouse
 
Data Warehouse Transient Comparison Configuration' form
An issue has been resolved where the 'Data Warehouse Transient Comparison Configuration' form was not displaying all transient fields for selected tables within the 'Compare Columns' field. KB0076023 v0.01
Please Note: "Avatar Data Warehouse Middleware Update 2024.1.001" is needed for full functionality
Topics
• Data Warehouse
 
Acceptance Tests
AV-80459 Summary | Details
Progress Note - service note
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Charge Input
Scenario 1: Progress Notes- Submit a note for an Existing Service
Specific Setup:
  1. Have a client [TestClient] with a service created that has an existing liability balance
  2. Form "Liability Update" has been submitted for the client
  3. Have access to any progress note form
Steps
  1. Select [TestClient] and access any progress note form. For example the 'Progress Notes (Group and Individual)" form.
  2. Select "Existing Service" in the 'Progress Note For' field.
  3. Select the created service in the 'Note Addresses Which Existing Service/Appointment' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field' field.
  6. Select "Draft" in 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a message is displayed stating: Note Filed.
  9. Click [OK] and remain in the form.
  10. Select the draft note in the 'Select Draft Note To Edit' field.
  11. Validate all previously filed data is displayed.
  12. Select "Final" in the 'Draft/Final' form.
  13. Click [File Note].
  14. Validate a message is displayed stating: Note Filed.
  15. Click [OK] and close the form.
Topics
• Progress Notes
AV-80647 Summary | Details
Data Warehouse - table validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SQL Query/Reporting Tool
Scenario 1: Data Warehouse - 'Background Journal' and 'Middleware' Processing - Table row validations
Specific Setup:
  • Have any desired tables selected for "Data Warehouse" processing in the "Data Warehouse Transient Comparison Configuration form' form that contain data.
  • In addition, have the following table data included for "Data Warehouse" processing:
  • Data submitted in the "SYSTEM.billing_guar_table" that includes data populated in the field "interim_billing_days" field
  • Data that exists in the "SYSTEM.billing_tx_charge_detail" table that contains data in field "remaining_balance"
  • Data in the 'DocR.Document' table that includes signature data in the "signature_stream" field and any other field data
  • Data in table 'SYSTEM.cw_tx_pn_sign_data_audit',and table SYSTEM.cw_tx_pn_sign_data', that includes signature data filed in the 'signaturecontent" field
  • Data submitted in a "Modeled" table [TestTable] that includes a "Decimal" type field.
  • A row of data has been submitted that includes a value populated in the decimal field that contains eight or more digits.
  • Data submitted in table "SYSTEM.cw_patient_notes" for via progress note form for a client, for an existing service that has a liability balance
  • Data submitted from two "View" tables created from existing tables, via form "SQL View Definition".
  • [ViewA], is based on a table that includes as one of its fields, a field name called "Enter By"
  • [ViewB] is based on table that contains one or more fields that include any of following characters in its field name: ' , ( ) [ ] < > & * ! ~ ?
  • Have a report or query that will display data in the following tables on the Cache server
  • "SYSTEM.dss_inc_full_load" table; "SYSTEM.dss_inc_full_load_history" and "SYSTEM.dss_inc_error_log" table
  • Have a program to query data tables on the Middleware SQL Server after "Data Warehouse" processing has completed and also the following tables:
  • "SYSTEM.dss_completion_flag" and the "SYSTEM.dss_inc_full_load_history
Steps
  1. Netsmart has run or set up a background process to run the middleware "Background Journal Process" process to select table rows based on the tables selected for data warehouse in the set up
  2. Validate the process completes successfully
  3. Run the report to display data table rows in the "SYSTEM.dss_inc_full_load" table
  4. Validate the report includes the expected tables queued for data warehouse processing based on the tables selected for data warehouse in the setup
  5. Netsmart has run or set up a background process to run "StartDssIncQueueManager" executable that will start the "Data Warehouse" Middleware to process and move selected data tables to the SQL Server Middleware server
  6. Validate the process completes successfully
  7. Run the report or query to display data in the "SYSTEM.dss_inc_error_log" table
  8. Validate the report indicates that there are no errors
  9. Run the report to display data table rows in the "SYSTEM.dss_inc_full_load_history" table
  10. Validate the report includes the expected data rows for the tables selected for processing in the setup
  11. Validate there are both "Insert" and "Delete" type rows, if applicable as expected
  12. Open the program used to query data on the SQL server
  13. Navigate to and select the folder where the data tables reside
  14. Execute a query to display field data filed in the "dss_completion_flag" table.
  15. Validate all the data rows for all the table(s) selected in the set up are present on the report, as expected.
  16. Validate for each table row. "dss_status" field value is set to"1", indicating success
  17. Execute a query to display data in the 'DW.dss_inc_full_load_history table'
  18. Validate data displays the same rows for the tables displayed in step 2b
  19. Execute a query to display data in the "SYSTEM.billing_guar_table"
  20. Validate data is populated in the field "interim_billing_days" field, as expected
  21. Execute a query to display data in the "SYSTEM.billing_tx_charge_detail" table
  22. Validate data is populated in the field "remaining_balance" field, as expected
  23. Execute a query to display data in the 'DocR.Document' table
  24. Validate signature data in the "signature_stream" field, as expected
  25. Execute a query to display data in the 'SYSTEM.cw_tx_pn_sign_data_audit' table
  26. Validate data is populated in the 'signatureconent" field, as expected
  27. Execute a query to display data in the SYSTEM.cw_tx_pn_sign_data table
  28. Validate data is populated in the 'signatureconent" field, as expected
  29. Execute a query to display data in the "Modeled" table [TestTable]
  30. Validate the data populated in "Decimal" field, as expected. In this example the field was populated with data consisting of eight or more digits
  31. Execute a query to display data in the "SYSTEM.cw_patient_notes" table
  32. Validate the row for progress note form for the existing service submitted in the setup, is displayed as expected
  33. Execute a query to display data in view [ViewA]
  34. Validate the "Entered by" field is populated as expected
  35. Execute a query to display data in view [ViewB]
  36. Validate for each field name that contained and of these special characters: ' , ( ) [ ] < > & * ! ~ ?
  37. The special characters noted have been removed from the field name headers
  38. Validate the data values populated in each field, is as expected
Topics
• Data Warehouse
AV-92894 Summary | Details
Data Warehouse - Globals
Scenario 1: “Data Warehouse” (Internal) - Validate data in "Middleware" processing "Properties", "Log" and "Installation" files
Steps
  1. Internal Testing Only
Topics
• Data Warehouse
AV-94278 Summary | Details
Data Warehouse Global
Scenario 1: “Data Warehouse” (Internal) - Data Warehouse "Globals" - Validations
Steps
  • Internal Testing Only
Topics
• Data Warehouse
AV-95704 Summary | Details
Data Warehouse Transient Comparison Configuration' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Warehouse Transient Comparison Configuration
Scenario 1: Data Warehouse Transient Comparison Configuration form
Specific Setup:
  • Have the data warehouse user [AvatarDW] created in form "User Definition", to be designated as the data warehouse user used in the Data Warehouse process
  • In form "User Definition" assign the [AvatarDW] any desired SQL Tables to be processed during the Data Warehouse process that also includes table, "SYSTEM.billing_835_header". Make note of all tables selected.
Steps
  1. Open form "Data Warehouse Transient Comparison Configuration form"
  2. Select the "Mark Tables For Full Loads" section
  3. In the "Avatar DW User" field, select the designated data warehouse user [AvatarDW]
  4. Validate the "SQL" Tables selection field is populated with the expected tables selected for the data warehouse user in the setup
  5. Click the checkbox next to the desired tables to be marked for a full data load
  6. Click [Mark Selected Tables For a Full Load]
  7. Validate message "Selected Tables are marked for a full load for the next Data Warehouse run
  8. Click [OK]
  9. Select the "Data Warehouse Transient Comparison Configuration" section
  10. In the "Avatar DW User" field, select the designated data warehouse user [AvatarDW]
  11. Click the "SQL Table" fields dropdown list
  12. Select any desired table from the list. For this test, select the "SYSTEM.billing_835_header".table
  13. Validate the "Compare Columns" selection box is populated
  14. Select any desired fields or all of the fields
  15. Submit the form
  16. Validate the form submits successfully
  17. Return to the "Data Warehouse Transient Comparison Configuration form"
  18. Select the "Mark Tables For Full Loads" section
  19. In the "Avatar DW User" field, select the designated data warehouse user [AvatarDW]
  20. Validate all tables selected for full load in step 1a, are selected as expected
  21. Select the "Data Warehouse Transient Comparison Configuration" section
  22. In the "Avatar DW User" field, select the designated data warehouse user [AvatarDW]
  23. Select the "SYSTEM.billing_835_header".table updated in step 1b
  24. Validate the "Compare Columns" selection box is populated
  25. Validate the fields selected in step 1b for the table, are selected as expected
  26. Close the form
Topics
• Data Warehouse