Release 2.16.05 Notes

Issue#

Application Module

Primary Function

Detail

Reported Issues

DFDD-120

Clinic

Certification Guided Script and Assign Certification Risk Factors

Issue: The DFDD is unclear on the functionality of the High Risk check boxes on the Certification Guided Script and Assign Certification Risk Factors screens.

Resolution: The DFDD has been updated to add additional clarification on the High Risk check boxes.

DFDD-134

Clinic

Button Labels

Issue: The DFDD still contains references to the Issue to Household, Issue to Member Only, Print for Household, and Print for Member Only buttons.

Resolution: The DFDD has been updated to remove references to these buttons and replace them with the Issue Benefits to Selected Members button.

DFDD-135

Clinic

Identify Benefits to Void

Issue: The DFDD incorrectly documents the names of some controls on the Identify Benefits to Void screen. These controls use the term "Check" rather than "Benefit".

Resolution: The DFDD has been updated for the Identify Benefits to Void screen topic to correctly document the names of the controls. There are other instances in the DFDD where this issue may still exist.

SUG-110

Clinic

Infant Information

Issue: On the Infant Information screen, after not entering a weight or length for the infant, if the screen is displayed again, the Height In, Height 8ths, Weight Lbs, and Weight Ozs masked edit boxes are populated with zeros. When the infant is linked to the mother and no weight or length values are entered, the masked edit boxes are not populated with zeros. However, Risk Factor 312 is assigned to the mother when it should not be.

Resolution: The height or weight of a participant can be recorded as zero (0) when it is an unknown height or weight. The system was incorrectly assigning Risk Factor 312 because the weight of zero (0) is below the low birth weight threshold. The code has been modified to not assign Risk Factor 312 when the weight is zero (0).

SUG-955

Clinic

Child Health Information

Issue: The Diabetes Mellitus check box and Hypertension or Prehypertension check box are enabled on the Child Health Information screen. When selected, the check boxes become disabled, but the associated risk factor is not assigned. The check boxes cannot be unchecked.

Resolution: The code has been modified so the Diabetes Mellitus check box and Hypertension or Prehypertension check box are enabled in both a Certification Guided Script and the Participant Folder when the participant is in an active certification. If either check box was selected during a previous certification, it carries forward to all subsequent certifications. If Risk Factor 343 no longer applies to the participant, the check box can be unchecked and the risk factor unassigned.

SUG-1194

Clinic

Benefits (Issue Benefits)

Issue: An infant who was previously issued formula had the prescription changed to soy formula. The system created a prescription dated for the current date and changed the prescription for the issuance, but it did not change the future food prescriptions.

Resolution: The code has been modified to include the new formula added to all future prescriptions.

SUG-1250

Clinic

Benefits (Issue Benefits) and Identify Benefits to Void

Issue: A user from a different clinic can void benefits on the Identify Benefits to Void screen for a participant assigned to a different clinic.

Resolution: The Void Benefits Issued at Other Clinic menu option has been removed. The Void Benefits Issued at This Clinic menu option has been renamed the Void Benefits menu option.

SUG-1348

DFDD

Business Rules

Issue: The DFDD incorrectly documents the date range for package size issuance for some business rules.

Resolution: The DFDD has been updated to clarify the business rules for package size issuance. The number of days have been modified to be exact calculations of the date range (for example, August 8 through August 29 is now documented as 21 days). The following business rules have been updated:

• B_MAX_DAYS_HALF_PACKAGE

• B_MAX_DAYS_QUARTER_PACKAGE

• B_MAX_DAYS_THREE_QUARTER_PACKAGE

• C_MAX_DAYS_HALF_PACKAGE

• C_MAX_DAYS_QUARTER_PACKAGE

• C_MAX_DAYS_THREE_QUARTER_PACKAGE

• I_MAX_DAYS_HALF_PACKAGE

• I_MAX_DAYS_THREE_QUARTER_PACKAGE

• N_MAX_DAYS_HALF_PACKAGE

• N_MAX_DAYS_QUARTER_PACKAGE

• N_MAX_DAYS_THREE_QUARTER_PACKAGE

• P_MAX_DAYS_HALF_PACKAGE

• P_MAX_DAYS_QUARTER_PACKAGE

• P_MAX_DAYS_THREE_QUARTER_PACKAGE

SUG-1617

Clinic

Add SOAP Note

Issue: The height and weight of the participant is not being included in the SOAP note information on the Add SOAP Note screen.

Resolution: The code has been modified to automatically populate the SOAP note with a measurement that was up to 60 days prior to the certification start date. Additionally, code has been added to find blood work information that was entered up to 60 days prior to the certification start date.

SUG-1646

Clinic

Issue Benefits

Issue: A standard warning message is not displayed when the seventh set of benefits is issued on the Benefits (Issue Benefits) screen because it must be added using the Add or Replace functionality. However, when a participant is recertified and has received all six sets of benefits but not the seventh set of benefits, the system is suggesting late issuance for the seventh set.

When a participant has completed a certification and a new one is started, the system is attempting to move the benefit cycle forward to the new certification. As a result, there is a gap between the certifications that results in a late issuance for the first set. The system is incorrectly setting the printed FDTU on the previous issuance. This results in a printed FDTU that is before the certification start date. The code was previously modified to set the benefit's start date and the printed FDTU as the current date. However, the system does not always maintain the same cycle even when the last set of benefits LDTU does not overlap the new certification start date. As a result, the participant only received two (2) months of benefits rather than three (3). The system does not continue the issuance cycle when the participant is recertified before their previous certification end date.

Resolution: The system was maintaining the benefit cycle dates when the last certification end date was prior to the current system date and the last certification ended within thirty-seven (37) days from the current system date. If the old certification end date is equal to the current system date, the last certification end date is not before the current system date and the benefit cycle dates are reset. The code has been modified to remove the first date check so any new certifications completed within thirty-seven (37) days of the last certification keep their benefit cycle dates.

SUG-1720

Clinic

Benefits (Issue Benefits)

Issue: A new certification was started for a participant, but the system displayed a standard information message that there were benefits to be printed first. The benefits were printed, and they had a PFDTU of 6/13 and a LDTU of 7/12. The certification was completed for the participant and the remainder of the benefits were printed, but the PFDTU on the new benefits was 7/28. There is a gap in the benefit issuance.

Resolution: If a participant has a late pickup of benefits on 3/13, and those benefits were voided, the FDTU of the last set of benefits is set at 3/13. As a result, the LDTU is 3/29. When benefits are issued again, the PFDTU is 5/13 with a LDTU of 6/12. The system is retrieving the 3/13 date to adjust the cycle.

The FDTU is being adjusted because there is more than a 1-month gap between the last benefit and the new benefit. The system is verifying if the last benefit's LDTU + 29 days is prior to the current date. If this is true, the system is using the FDTU of the last benefit and adding a month to it to use on the new benefit which results in the LDTU being adjusted. This causes issues when the last benefit was a late pickup because it is looking at the FDTU rather than the PFDTU. However, if the last benefit's LDTU + 29 days is after the current date, the system is correctly looking at the late pickup and using the correct date for cycle adjustment.

The code has been modified to remove the 29-day logic and add a check for whether the last benefit was a late pickup. If it is a late pickup, the system accounts for that and does not use the last benefit's FDTU to determine the cycle of the next benefits.

SUG-1814

State Office

Participation by Priority/Category/Ethnicity Group Report CLD020 (Output)

Issue: The Participation by Priority/Category/Ethnicity Group Report CLD020 (Output) does not include the run date or page numbers.

Resolution: The code has been modified to move the run date, run time, and the page number to the left so it displays on the report.

SUG-1858

Clinic

Benefits (Issue Benefits)

Issue: A household whose LDTU has always been the first of the month was changed by the system to be the 15th of the month. The set of benefits issued before this was a late pickup with a FDTU of the 16th.

Resolution: If a participant has a late pickup of benefits on 3/13, and those benefits were voided, the FDTU of the last set of benefits is set at 3/13. As a result, the LDTU is 3/29. When benefits are issued again, the PFDTU is 5/13 with a LDTU of 6/12. The system is retrieving the 3/13 date to adjust the cycle.

The FDTU is being adjusted because there is more than a 1-month gap between the last benefit and the new benefit. The system is verifying if the last benefit's LDTU + 29 days is prior to the current date. If this is true, the system is using the FDTU of the last benefit and adding a month to it to use on the new benefit which results in the LDTU being adjusted. This causes issues when the last benefit was a late pickup because it is looking at the FDTU rather than the PFDTU. However, if the last benefit's LDTU + 29 days is after the current date, the system is correctly looking at the late pickup and using the correct date for cycle adjustment.

The code has been modified to remove the 29-day logic and add a check for whether the last benefit was a late pickup. If it is a late pickup, the system accounts for that and does not use the last benefit's FDTU to determine the cycle of the next benefits.

SUG-1874

Clinic

Participant List

Issue: On the Participant List screen, the Details pane does not correctly display the default clinic issuance frequency. If the CPA-determined Follow-up screen is completed, the Details pane correctly displays the information.

Resolution: All new household members are automatically set to the issuance frequency set at the clinic level. The user can modify this information using the CPA-determined Follow-up screen. The code has been modified to change the issuance frequency in the Details pane when the issuance frequency is modified.

SUG-1911

Clinic

Issue Benefits

Issue: The system does not consistently suggest the last set of benefits on the Benefits (Issue Benefits) screen for participants becoming categorically ineligible.

Resolution: This issue could be replicated for infants, but not breastfeeding women. In a previous release, the code added was allowing the extra benefit to be suggested when the month of the benefit was the same month as the categorically ineligible date. As a result, an infant who is turning 1 year old on the month of issuance and has a categorically ineligible date four (4) years in the future was not receiving the extra benefit because the categorically ineligible date is in the future.

The code has been modified to not include the categorical ineligible date for infants or pregnant women when determining benefit issuance.

SUG-1942

Clinic

Benefits (Issue Benefits)

Issue: After a late pickup, the system seems to be using the participant's FDTU rather than the LDTU of the late pickup issuance.

Resolution: If a participant has a late pickup of benefits on 3/13, and those benefits were voided, the FDTU of the last set of benefits is set at 3/13. As a result, the LDTU is 3/29. When benefits are issued again, the PFDTU is 5/13 with a LDTU of 6/12. The system is retrieving the 3/13 date to adjust the cycle.

The FDTU is being adjusted because there is more than a 1-month gap between the last benefit and the new benefit. The system is verifying if the last benefit's LDTU + 29 days is prior to the current date. If this is true, the system is using the FDTU of the last benefit and adding a month to it to use on the new benefit which results in the LDTU being adjusted. This causes issues when the last benefit was a late pickup because it is looking at the FDTU rather than the PFDTU. However, if the last benefit's LDTU + 29 days is after the current date, the system is correctly looking at the late pickup and using the correct date for cycle adjustment.

The code has been modified to remove the 29-day logic and add a check for whether the last benefit was a late pickup. If it is a late pickup, the system accounts for that and does not use the last benefit's FDTU to determine the cycle of the next benefits.

SUG-1948

Clinic

Schedule Appointments for Household

Issue: When scheduling an appointment on the Schedule Appointments for Household screen, the WIC category selected in the WIC Category drop-down list box is not being saved.

Resolution: The code has been modified to change the WIC Category drop-down list box to a text and value label. There is no place to store the WIC category in the Appointment table.

SUG-1950

Clinic

Issue Benefits

Issue: When benefits are replaced for a breastfeeding infant and the FIS.AmountBreastfed table is queried, the initially issued benefits have a correct value indicating the infant is breastfeeding; however, the replaced benefits have an incorrect value indicating the infant is not breastfeeding.

Resolution: The issue is caused by the AmountBreastfed property defaulting to 4 when a value other than 1-5 is entered. When the FoodInstrumentSet is created, it defaults to 4 and does not change unless the code changes it somewhere else. The code is not saving the replacement benefit set for the infant, and it does not retrieve the breastfeeding amount from the Child record. As a result, the value never changes from 4 to 2.

The code has been modified to retrieve the breastfeeding amount for the infant and save it to the FoodInstrumentSet record. Additionally, the code has been modified to retrieve the breastfeeding amount for children, pregnant women, breastfeeding women, and non-breastfeeding women.

TOF-45

State Office

Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report CLD035 (Output)

Issue: When a grantee number is selected for generation on the Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report CLD035 (Output), if that number is included as part of another grantee's number, both grantees display on the report. For example, if grantee 10 is selected, the output include all grantees that have "10" in their number (for example, grantee 10 is included as well as grantee 710 and 810).

The title of the report displays "Calendar Year" rather than the actual year.

At the end of each section, the text should be bold and all capital letters. Currently, it is not capitalized.

The last page total appropriately indicates how the report was run, but they are not displayed in all capital letters.

Resolution: The code has been modified to correctly retrieve the grantee number for a single grantee rather than including all grantees with a similar number.

The title of the report has not been modified as the report is for a calendar year.

The text at the end of each section has been modified to be displayed in all capital letters.

The last page total is using mixed case, which is the report standard.

TOF-61

Vendor Online Price Survey

Price List and New Price List

Issue: When a terminated vendor is entered on the Price List screen and the OK button is clicked on the New Price List screen, a 404 server error displays.

Resolution: The code has been modified to add validation to the Vendor ID masked edit box. When the New Price List button is clicked on the Price List screen, the system verifies the status of the vendor. If the vendor is not an Applicant, Enrolled, or on Probation, the system displays a standard error message (E0361) with the text, "You cannot create a price list for a vendor with a status of {status}."

TOF-78

Clinic

Food Prescription

Issue: When an infant over 6 months of age is receiving Food Package III and the solid food items are being removed and replaced with formula for the 4-5 month age range on the Food Prescription screen, the system deletes the cereal and infant food, but the formula does not change. Instead, it retains the 6-12 month amount and does not change to the 4-5 month amount.

Resolution: The code has been modified so that when the user chooses to maximize the formula, it initializes with the new higher maximum. However, if the initial quantity is one (1), then it remains at one (1).

TOF-79

Reference Utility

Base Food Category Limits

Issue: On the Base Food Category Limits screen, when the Active check box is selected in the Active column, it deactivates the food item. When the Search button is clicked, all the deselected items no longer display in the editable data grid. When another record is selected to be deactivated in the Active column, it immediately disappears from the editable data grid.

Resolution: This issue occurs when there are no inactive rows in the results if the search had been for "ALL" food categories. The code has been modified to no longer hide rows when the Active column check box is deselected. This change also affects the editable data grid on the Risk Factor Associations screen.

TOF-85

Clinic

Participant List

Issue: When the Details pane is displayed for a participant selected in the data grid on the Participant List screen, if a new participant is prescreened and the user returns to the Participant List screen, the participant listed above the newly added participant has their details displaying in the Details pane. The Details pane is not refreshing and displaying the newly selected record.

Resolution: The code has been modified to call the RefreshDetailsPanel so the system now refreshes the Details pane after prescreening an applicant.

TOF-86

Reference Utility

Violation Types

Issue: When adding values to the Days to Apply column for new rows on the Violation Types screen, the system displays a standard error message with the text, "Column 'ViolationTypeID, Category' is constrained to be unique. Value ',' is already present."

Resolution: The data set object associated with the editable data grid did not allow duplicated primary keys, and the primary key was not created until the user chose a category in the Federal/State column. The code has been modified to assign a unique ID whenever a new record does not have a primary key. The system still informs the user if a category is not chosen in the Federal/State column when the screen is processed.

TOF-89

Clinic

Certification Notice (Output)

Issue: When the Certification Notice (Output) is generated during a Certification Guided Script with an adjunct eligibility of medicaid, the adjunctive eligibility is blank on the notice.

Resolution: The system was using the income contact record properties to retrieve the adjunctive details. The code has been modified to retrieve the adjunctive details from the income contact adjunctive item record.

TOF-90

Vendor

Generate Vendor Benefits Redeemed Report

Issue: When a four-digit vendor ID is entered in the Stamp Number masked edit box on the Generate Vendor Benefits Redeemed Report screen, the system generates the Vendor Benefits Redeemed Report VND068 (Output) for the vendor, but it displays a standard error message with the text, "No vendor could be found with the stamp number provided. Please enter a different stamp number." If the leading zero is entered with the stamp number, the standard error message does not display and the report generates correctly.

Resolution: The code has been modified to automatically add the leading zero to a 4-digit stamp number. The standard error message no longer displays when a 4-digit stamp number is entered.

TOF-93

Reference Utility

Reference Utility

Issue: On the Reference Utility screen, when a column header is double-clicked, the selected row is activated and displays the calling screen.

Resolution: The code has been modified to only open the selected row when it is double-clicked.

TOF-94

Clinic

Benefits (Issue Benefits) and Food Prescription (Issue Benefits)

Issue: When editing food prescriptions on the Food Prescription (Issue Benefits) screen and returning to the Benefits (Issue Benefits) screen, the check boxes for the suggested issuance are unchecked.

Resolution: The code has been modified to call a function to refresh the checked state of the check boxes when the Benefits (Issue Benefits) screen displays.

TOF-96

Vendor Online Price Survey

New Price List

Issue: When the New Price List screen displays, it has a transparent background and is difficult to read.

Resolution: The CSS has been changed to correct the opacity of the New Price List screen.

TOF-97

Vendor

Page2 (Demographics)

Issue: When changes are made on the Page2 (Demographics) screen and the user is asked to save, a standard error message displays with the text, "An entry is required for the Store Type." The Store Type drop-down list box was already populated.

Resolution: The code has been modified to track changes in the Store Type drop-down list box. When the Store Type drop-down list box is populated, the standard error message no longer displays.

TOF-100

Vendor Online Application

Business Information

Issue: When multiple Authorized Agent Information tabs are added on the Business Information screen so that there are multiple rows, if the user attempts to delete a tab in a row above the last row, the system displays a standard error message with the text, "Errors on this webpage might cause it to work incorrectly".

Resolution: There is an internal tab counter that was using string values and not integer values. This caused the tabs to be handled in the wrong order. This issue occurs when there are more than nine (9) tabs added. The code has been modified to use an integer value for counting the total number of tabs.

TOF-102

Vendor

Event Log

Issue: When the Total Outstanding Sanction Points text and value label is double-clicked on the Event Log screen, a new screen is displayed.

Resolution: There was leftover debugging code that would reload the tree view object and present the user with the timing of how long the process took to complete. The code has been modified to remove the debugging code.

TOF-103

Clinic

Error Messages

Issue: The Food Item ID is displayed in front of the item description on some standard error messages.

Resolution: The standard error messages related to ENH-119 (MN-78) have been modified to move the Food Item ID. Additionally, four (4) other messages were modified to display the food item ID after the food item description.

TOF-104

Vendor

Corporate Owner

Issue: The DFDD incorrectly states that the Percent Owned masked edit box on the Corporate Owner screen can be left blank. However, an entry is required.

Resolution: The code has been modified to allow the Percent Owned masked edit box to hold a value of zero (0). The DFDD has been updated to reflect this functionality.

TOF-105

Clinic

Benefits (Issue Benefits)

Issue: On the Benefits (Issue Benefits) screen, the user is unable to select additional check boxes for a participant for additional months.

Resolution: When the check box is selected, the system was refreshing all the check boxes to display as they did when the Benefits (Issue Benefits) screen first displayed. The code has been modified to not refresh the check boxes when one check box is selected.

TOF-106

Clinic

Child Health Information

Issue: When an infant is changed from fully breastfeeding to non-breastfeeding on the Child Health Information screen, the Select Formula screen no longer displays.

Resolution: The function to modify the prescription contains a check for the certification before calling the default prescription code. The code was incorrectly checking that the certification did not exist before creating the default prescription. The code has been modified to check that the certification does exist before creating the default prescription.

TOF-110

Vendor Online Price Survey

New Price List

Issue: When the OK button is clicked on the New Price List screen, the system displays a standard error message with the text, "There is no row at position 0." This occurs regardless of whether the All Distribution Items radio button or the Select Template radio button is selected.

Resolution: The code has been modified to add validation to the Vendor ID masked edit box. When the New Price List button is clicked on the Price List screen, the system verifies the status of the vendor. If the vendor is not an Applicant, Enrolled, or on Probation, the system displays a standard error message (E0361) with the text, "You cannot create a price list for a vendor with a status of {status}."

TOF-113

State Office

Weight Status of Women and Children Greater than 2 Years (BMI) Report OPR032 (Output)

Issue: The names of the files created when the Weight Status of Women and Children Greater than 2 Years (BMI) Report OPR032 (Output) is run during the End of Month Processing are "BMI". This should be changed to "Weight Status" to match the report title.

Resolution: The constant used for the file names for the report have been changed from "BMI" to "Weight Status".

TOF-117

Vendor

Compliance Buy Returned

Issue: When a benefit number is entered on the Compliance Buy Returned screen, the only way to activate the other controls on the screen is to press the Tab key. The Enter key does not process the benefit number.

Resolution: The code has been modified so the Enter key functions the same as the Tab key. When Enter is pressed, the benefit number is processed and the controls become enabled.

TOF-120

Vendor

Compliance Buy Meeting Letter

Issue: The leading zeros are being removed on the Compliance Buy Meeting Letter.

The last name of the contact on the Compliance Buy Meeting Letter displays after "Dear" rather than the first name.

Resolution: The code has been modified to populate the benefit number from the ReturnedComplianceBuyFI.FoodInstrumentID column rather than the ReturnedComplianceBuyFI.SerialNo column.

Additionally, the LastName merge field is functioning as designed for the letter template.

TOF-122

Vendor

Compliance Buy Benefits

Issue: A value of zero (0) can be entered in the Qty column in the Benefit Set editable data grids on the Compliance Buy Benefits screen. The screen can be processed with a value of zero for the quantity.

Resolution: The code has been modified to make changes to the Compliance Buy Benefits screen and include additional validation of the controls. The following changes have been made to the screen:

• Each editable data grid has been labeled as Benefit 1, Benefit 2, and Benefit 3.

• The Qty column has been renamed the Quantity column, and the values for each record are right-aligned.

• The Quantity column allows input from 0.0 to 9,999.99.

• The Quantity column has been changed to a numeric data type to match the FoodItemQty table. All values above 9,999.99 are updated to 9,999.99.

• When the screen is processed, the data validation highlights each cell that did not pass validation.

• The background color of the editable data grids and buttons have been corrected.

• The Compliance Buy Benefits screen can now be resized.

• The security messages for the button clicks have been updated.

The following validations have been added:

• When no rows have been added to the Benefit 1 editable data grid, the system displays the standard error message (E0362) with the text, "Benefit 1 must include at least one item."

• When a single Quantity value is blank, the system displays the standard error message (E0001) with the text, "An entry is required for the Quantity on Benefit {1/2/3}."

• When multiple Quantity values are blank, the system displays the standard error message (E0001) with the text, "An entry is required for multiple Quantities on Benefit {1/2/3}."

• When a single Quantity value is equal to zero (0), the system displays the standard error message (E0363) with the text, "Quantity must be greater than zero on Benefit {1/2/3}."

• When multiple Quantity values are equal to zero (0), the system displays the standard error message (E0363) with the text, "Quantity must be greater than zero on Benefit {1/2/3} for multiple entries."

• When a single Food Distribution Item value is blank, the system displays the standard error message (E0002) with the text, "A selection is required for the Food Distribution Item on Benefit {1/2/3}."

• When multiple Quantity values are blank, the system displays the standard error message (E0002) with the text, "A selection is required for multiple Food Distribution Items on Benefit {1/2/3}."

• When multiple Food Distribution Items are selected multiple times in the same editable data grid, the system displays the standard error message (E0364) with the text, "Food Distribution Item cannot be selected more than once for Benefit {1/2/3}."

TOF-125

Management Console

Role Profile

Issue: On the Role Profile screen, the Role Name text box allows the entry of a duplicate role name. If the role name has already been created, a user can create a new role with the same name.

Resolution: The code has been modified to validate the role name. If it is a duplicate value, the system displays the standard error message (E0060) with the text, "The Role Name already exists."

TOF-131

Vendor

Page2 (Demographics)

Issue: When no changes are made on the Page2 (Demographics) screen, the user is asked to save. A standard error message displays with the text, "An entry is required for the Store Type." The Store Type drop-down list box was already populated and no changes were made to the screen.

Resolution: The Store Type drop-down list box properties were being changed whenever the Page2 (Demographics) screen was displayed. This resulted in the standard confirmation message for saving the data. The code has been modified to not change the properties of the Store Type drop-down list box when no changes have been made to it.

TOF-134

Clinic

Benefits (Issue Benefits)

Issue: When a food item is issued along with an alternative food item of the same type, if the Preview Benefits button is clicked on the Benefits (Issue Benefits) screen, the system displays a standard error message with the text, "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index".

Resolution: The system was combining the food items when the alternate food item created two of the same food items on the benefit. As a result, the system deletes one of the duplicate lines which caused the error. The code has been modified to combine the duplicate food items.

TOF-135

Clinic

Benefits (Issue Benefits)

Issue: When the Issue Benefits toolbar button is clicked to issue benefits for a participant who will be categorically ineligible for the month the benefits are issued, the system displays a standard error message with the text, "Unable to locate month". This does not always occur for every participant who has benefits issued for the month in which the participant becomes categorically ineligible. Instead, it occurs when the categorically ineligible date is equal to the PFDTU of the benefits, and when the system suggests the month to issue benefits. The issuance frequency can be changed from tri-monthly to bi-monthly, but the system then states that there are still benefits available to be issued.

Resolution: The system, when distributing the food instruments across the benefits, first calculated the number of months between the FDTU of the first set of benefits and the categorically ineligible date. In the case of a participant whose categorically ineligible date is 9/30/2012 and the LDTU of their last set of benefits is 7/29/2012, the system was calculating the range to be two (2) months. Next, the system went through the three (3) months of benefits for tri-monthly issuance and added the distributed item quantity to each month. When the system reaches the third month, it is unable to find the quantities for month 3 as the above calculation only returned two (2) months. As a result, the standard error message is displayed.

The code has been modified to ensure the system calculates three (3) months between 7/30 and 9/30. When the system calculates the benefit dates for September, it wants to set the LDTU as 9/31. Because September only has 30 days, the system adjusts the date to 9/30, which causes the calculation to return the number of months between 7/30 and 9/30 as 2 months.

TOF-150

Clinic

Benefits (Issue Benefits)

Issue: A participant had benefits issued on 6/7 and then later voided those benefits on 6/12 and reissued the benefits. When the next set of benefits was issued on 8/6, the system should have suggested the benefits range of 7/7-8/6; instead, the system used the previous month's issuance date of 6/12 and set the PFTU to 7/12. When the next set is issued, August is skipped by the system.

Resolution: If a participant has a late pickup of benefits on 3/13, and those benefits were voided, the FDTU of the last set of benefits is set at 3/13. As a result, the LDTU is 3/29. When benefits are issued again, the PFDTU is 5/13 with a LDTU of 6/12. The system is retrieving the 3/13 date to adjust the cycle.

The FDTU is being adjusted because there is more than a 1-month gap between the last benefit and the new benefit. The system is verifying if the last benefit's LDTU + 29 days is prior to the current date. If this is true, the system is using the FDTU of the last benefit and adding a month to it to use on the new benefit which results in the LDTU being adjusted. This causes issues when the last benefit was a late pickup because it is looking at the FDTU rather than the PFDTU. However, if the last benefit's LDTU + 29 days is after the current date, the system is correctly looking at the late pickup and using the correct date for cycle adjustment.

The code has been modified to remove the 29-day logic and add a check for whether the last benefit was a late pickup. If it is a late pickup, the system accounts for that and does not use the last benefit's FDTU to determine the cycle of the next benefits.

The system was maintaining the benefit cycle dates when the last certification end date was prior to the current system date and the last certification ended within thirty-seven (37) days from the current system date. If the old certification end date is equal to the current system date, the last certification end date is not before the current system date and the benefit cycle dates are reset. The code has been modified to remove the first date check so any new certifications completed within thirty-seven (37) days of the last certification keep their benefit cycle dates

TOF-161

Financial Management

Year-to-date Participation and Outlays Report FIN017 (Output)

Issue: When generating the Year-to-date Participation and Outlays Report FIN017 (Output) to any report destination or report by selection for the month of July, the system displays a standard error message with the text, "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated."

Resolution: The code has been modified to add four new indexes to improve the performance of the report query. The following indices have been added:

• IX_CASELOADCOUNT_3

• IX_FOODINSTRUMENTSET_7

• IX_FOODINSTRUMENTSET_8

• IX_FOODINSTRUMENTSET_9

These indices were run in the Arkansas production environment due to an immediate need of the finance department. The database script changes have been included with this release.

TOF-165

Vendor

Peer Group Average

Issue: When recalculating the peer group average on the Peer Group Average screen, the averages are not being calculated correctly.

Resolution: The code has been modified to retrieve the maximum price list for a vendor when doing the recalculation.

TOS-1

Clinic

Schedule Appointments for Household

Issue: When appointments are still available for a day on the Schedule Appointments for Household screen, the day is being colored teal, which means there are no available times.

Resolution: The code added for an earlier release was removed. The code has been added back to the stored procedure.

TOS-2

Clinic

Participant List

Issue: The Details pane on the Participant List screen is displaying a LDTU when there is no PFDTU. Additionally, no issuance frequency displays for the participant.

Resolution: The code has been modified to return a PFDTU when there is no issuance frequency.

TOS-3

Clinic

Participant List

Issue: When benefits are marked as lost or stolen, the PFDTU and LDTU text and value labels display a status of "Issued".

Resolution: The system is functioning as designed. The DFDD has been updated to clarify the statuses of the benefits. When the benefit has been issued, the status is "Issued". When the benefit has been marked as lost or stolen, the status is "Issued". When a benefit has been voided, the status is "Voided".

TOS-4

Clinic

Participant List

Issue: The DFDD incorrectly states that the PFDTU text and value label in the Details pane on the Participant List screen displays the "last" date on which the printed benefits can be used.

Resolution: The DFDD has been updated to document the PFDTU text and value label as the first date on which the benefits can be used as printed on the benefits issued to the participant.

TOS-6

DFDD

Business Rule

Issue: The USETWOMOSTRECENTMESUREMENTSRF131P business rule is not documented in the DFDD.

Resolution: The USETWOMOSTRECENTMESUREMENTSRF131P business rule has been added to the DFDD.

TOS-7

Clinic

Missed Appointments Follow-up

Issue: When a missed appointment follow-up is added to a household on the Missed Appointments Follow-up screen, the screen refreshes and resorts the data grid.

Resolution: The system reloads the Missed Appointments Follow-up screen with the initial sort order every time it is displayed. The code has been modified to set the focus on the item that invoked the screen.

TOS-8

Clinic

VOC Certification

Issue: When a priority is entered in the Priority text box on the VOC Certification screen, a system-assigned risk factor with a higher priority is not overriding it.

Resolution: The code has been modified to check if any system-assigned risk factors have been created, calculate the risk factor priority, and assign the highest priority among the risk factors for the current certification.

TOS-9

Clinic

Height/Weight Measurement

Issue: When a new measurement is added on the Height/Weight Measurement screen for a participant who has risk factors related to height or weight, all risk factors for the current certification are removed and a pseudo-certification is created.

Resolution: The issue was caused by applying extra filters such as Age Category and Amount Breastfeeding to CPA or nutrition assessment assigned risk factors during a pseudo-certification process. As a result, the CPA and nutrition assessment assigned risk factors were being excluded from the next certification. The code has been modified to add an extra parameter to control the utilization of the extra filters.

Additionally, the code added as part of SUG-1665 has been removed.

TOS-10

Clinic

Participant Folder and Certification Guided Script

Issue: The Hypertension or Prehypertension check box is enabled in the Participant Folder but disabled during a Certification Guided Script

Resolution: The code has been modified so the Diabetes Mellitus check box and Hypertension or Prehypertension check box are enabled in both a Certification Guided Script and the Participant Folder when the participant is in an active certification. If either check box was selected during a previous certification, it carries forward to all subsequent certifications. If Risk Factor 343 no longer applies to the participant, the check box can be unchecked and the risk factor unassigned.

TOS-14

Clinic

Schedule Appointments for Household

Issue: When the Close button is clicked on the Schedule Appointments for Household screen, the Participant List screen displays on top of all other screens. This occurs when the Schedule Appointments for Household screen is called from the Participant Folder.

Resolution: The code has been modified to display the last active screen from which the Schedule Appointments for Household screen was invoked.

TOS-15

Vendor

New Price List

Issue:When the OK button is clicked on the New Price List screen, the system displays a standard error message with the text, "There is no row at position 0." This occurs regardless of whether the All Distribution Items radio button or the Select Template radio button is selected. This occurs for an enrolled vendor.

Resolution: The code has been modified to add validation to the Vendor ID masked edit box. When the New Price List button is clicked on the Price List screen, the system verifies the status of the vendor. If the vendor is not an Applicant, Enrolled, or on Probation, the system displays a standard error message (E0361) with the text, "You cannot create a price list for a vendor with a status of {status}."

TOS-17

Clinic

Infants Born from This Pregnancy

Issue: The columns on the Infants Born from This Pregnancy screen are not in the correct order. The Breastfeeding Amount column and Date Breastfeeding Ended column need to be moved.

Resolution: The columns have been re-ordered. Additionally, the columns have been shrunk as much as possible to allow the user to view more of the contents of the data grid without scrolling.

TOS-19

Vendor Online Price Survey

E-mail

Issue: If the vendor name contains an ampersand (&), in the invitation e-mail containing the mail merge field {vendor.tradename}, the ampersand is displayed as "&".

Resolution: The code has been modified to display the ampersand (&) correctly when sending the invitation e-mail to the vendor.

TOS-20

Clinic

Height/Weight Measurement and Risk Factors

Issue: When a child greater than or equal to 2 years of age has a height measurement added on the Height/Weight Measurement screen and is measured recumbently, the child was assigned an anthropometric risk factor. The measurement is correctly plotted on the Growth Grids.

Resolution: The code has been modified for the child risk factor assignment for children older than 2 years of age whose latest height and weight measurement is measured recumbently. All risk factors related to height and weight are no longer assigned when the most recent measurement is recumbent. The following risk factors have been modified:

• Risk Factor 103

• Risk Factor 121

• Risk Factor 135

Risk Factor 113 was not modified as the recumbent measurement must be used to compare against the weight for height percentile to check if the risk factor should be assigned for children 2-3 years of age.

TOS-21

Clinic

Benefits (Issue Benefits)

Issue: A participant with monthly issuance has three months of benefits suggested on the Benefits (Issue Benefits) screen.

Resolution: When a new member is created and the user does not set the issuance frequency, the issuance frequency is not automatically set for the participant. The benefits issuance code was checking that value to determine how many benefit sets the participant was to receive. The code was set to use tri-monthly issuance if it could not find an issuance frequency value for the member.

The code has been modified to automatically set the issuance frequency for each participant to the issuance frequency set at the clinic level.

Additionally, the 2.16.05 SQL script has been modified to update all ServiceSite records with a NULL IssuanceFrequency value to T (tri-monthly). All Member records with a NULL IssuanceFrequency value are to be updated with the clinic's IssuanceFrequency value.

TOS-23

Clinic

Follow-up Information

Issue: When no date is entered on the Follow-up Information screen, a date of 1/1/1900 is displayed on the Missed Appointments Follow-up screen and is printed on the notice.

The DFDD incorrectly states the Follow-up Information screen displays when the OK button is clicked on the Generate Missed Appointment Notice screen.

Resolution: When no valid date is entered, SQL Server inserts a default value of 1/1/1900. The code has been modified to pass a SQL Server null type, which inserts a null value in the Follow-up Date column on the Missed Appointments Follow-up screen when no valid date is supplied.

The DFDD has been updated to correctly document that the Missed Appointments Follow-up screen displays when either the OK or Cancel button is clicked on the Generate Missed Appointment Notice screen.

TOS-24

Vendor Online Price Survey

Price Survey

Issue: When the Export button is clicked on the Price Survey screen, the file that is exported incorrectly spells "Survey" (PriceSuveyXXXX.csv)

Resolution: The code has been modified to change the file name to PriceSurveyXXXX.csv.

TOS-27

Clinic

Risk Factors

Issue: If Risk Factor 201 is added to a participant for a low Hemoglobin level, adding a valid Hematocrit value on the Blood screen does not remove the risk factor.

Resolution: The code has been modified to use the most recent Hemoglobin or Hematocrit measurement for determining the risk factor.

TOS-28

Financial Management

Generate Reports

Issue: When the FNS-798 Statement list item is double-clicked on the Generate Reports screen, the system displays a standard error message with the text, "Could not find a part of the path {file path}."

Resolution: This issue is caused by the system attempting to access the report templates in multiple Windows environments. The Statement table stores the report template source and destination paths. If a clinic uses different Windows environments, the system cannot find the file path to the template.

The code has been modified to access the report template paths automatically without looking in the Statement table. The code now accesses the templates in the Reports folder of the application path and stores the output in the Output folder of the application path. The source and destination paths have been removed from the Statement table.

The Financial Statements List screen has been modified. The Template Path/File column has been removed from the Financial Statements List data grid. Additionally, the Edit button and Details button have been removed.

TOS-31

Clinic

Demographics

Issue: When the CLN_AllowPendingProof_ID, CLN_AllowPendingProof_Residency, and CLN_AllowPendingProof_Income business rules are set to "N", the blank entry in the drop-down list boxes can be selected and saved by the system on the Demographics screen.

Resolution: The blank entry in the ID Proof and Residency Proof drop-down list boxes was for participants who had "Pending Proof" selected prior to the 2.16 release. If the state chose to not allow pending proofs based on the new business rules, the drop-down list boxes needed some value selected.

The code has been modified for the Participant Folder to require an entry in the ID Proof and Residency Proof drop-down list boxes when the blank entry is selected. Additionally, the code has been modified for the Certification Guided Script to not include the blank entry in the drop-down list boxes.

TOS-34

Reference Utility

Risk Factors

Issue: For mothers of multiples, risk factors, aside from Risk Factor 335, cannot be assigned. When attempting to add a new risk factor on the Risk Factors screen, the system displays an object reference error.

Resolution: The code has been modified to correct the object reference error when the Add button is clicked on the Risk Factors screen. Additional insert SQL statements were added to the SQL script to add the breastfeeding risk factors so that mothers of multiples can have risk factors assigned. A new SQL script has been created to move risk factors from UAT to production. This script generates the SQL code needed to copy all RiskFactorReference records from the UAT database to the client's production database.

TOS-35

Clinic

Participant List

Issue: When a search is performed on the Participant List screen and errors are encountered with a specific control, the control receives the orange halo. If the Clear button is clicked, focus is returned to the State WIC ID text box, but the control that received the orange halo still displays the halo even when it is disabled.

Resolution: The code has been modified to remove the orange halo when the Clear button is clicked.