Issue# |
Application Module |
Primary Function |
Detail |
Enhancements |
EBT-50 |
Scheduled Job Administration,
Reference Utility |
End of Day |
The
SPIRIT EBT system was originally designed to perform reconciliation,
on issuance and void transactions, during the End of Day (EOD) process
based on the date of the transaction and the recipient ID. However,
SPIRIT and the EBT Processor
record the transactions differently and as such the transactions
became irreconcilable. A modification has been made, changing
the existing functionality to ignore the date and time of transactions
in the opposite system and simply ensure that they exist based
on the recipient ID (HouseHold ID) and Issuance Number.
To find the unmatched records, the system
will filter the records by date. The filtered records will then
be matched against records from the opposite system by their respective
HouseHoldID and Issuance Numbers. Any that do not match will be
collected for later reference when constructing the reconciliation
e-mail.
Once both SPIRIT and the EBT Processor
records have been reconciled, an e-mail
will be generated that contains a listing and description of the
exceptions. The e-mail
will be sent to the addresses specified in the Reference Utility.
Additionally, the WIC Activity File Import
in the SPIRIT Import Files process
has been modified to eliminate further discrepancies. The Quantity
column was changed
to a 2 precision decimal. The process was changed to store the
filename and perform a delete/insert based on the filename for
initial and re-imported files.
The overall reconciliation process was changed
to use the stored procedure, uspGetEBTReconciliationErrors. A
statement can be used to execute it for a given date. |
ENH-181 |
Clinic |
Risk Factor |
Risk Factor 133, High Maternal
Weight Gain, has been revised for pregnant women per the USDAs
updated criteria. This revision adds a new level of "Obese"
(a woman with a BMI of 30.0 or more) to the Pre-pregnancy BMI
Growth Grids.
Previously, these women would have been plotted as "Overweight"
on the Growth Grids.
This revision will now assign Risk Factor 133 in the
2nd or 3rd trimester for a singleton pregnancy as follows:
For Underweight
women, if the weight gain is > 1.3 lbs per week For Normal
Weight women, if the weight gain is > 1 lb per week For Overweight
women, if the weight gain is >.7 lb per week For Obese
women, if the weight gain is >.6 lb per week |
Reported Issues |
CNEBT-32,
CNEBT-119 |
Vendor |
Vendor
Return File |
Issue: When the vendor file was sent to
the EBT Processor
with the End of Day
process, two standard error messages
were associated with the vendor file due to missing data: DT58
- missing vendor contact, and DT54 - Vendor doesn't exist.
Resolution: The
contact name on the rejected records was populated with a value
of "unknown" in lowercase letters when the corporate
authorized agent was null or blank. The EBT Processor
does not accept this as a valid contact name. The accepted value
for null or blank records is "UNKNOWN" in uppercase
letters. A change was added to the database scripts to accommodate
this requirement.
Additionally, there was a problem with the
selection
criteria for the vendor file:
WHERE EBT="Y"
AND vendor is terminated or disqualified
with a future bank termination date that is since last run
OR vendor is active and approved, contract
expired since last run, or expires in the future and record is
modified.
In this situation, the first two conditions
were evaluated as AND, while the third condition was treated as
a separate OR clause, thus causing all modified vendor records
to be sent. A fix was made, changing the criteria to:
WHERE EBT="Y"
AND (vendor is terminated or disqualified
with a future bank termination date that is since last run OR
vendor is active and approved, contract expired since last run,
or expires in the future and record is modified)
This change will force the second and third
conditions to be evaluated together as one criteria, resolving
the issue. |
CNEBT-98 |
Reference Utility |
EBT |
Issue: A comparison of the Ad hoc query
of the SPIRIT redemption data store against the EBT Processor
files produced some conflicts. Certain records were found in the
EBT Processor
files but not in the SPIRIT query.
Resolution: An
issue was identified where the Import National UPC File
was not importing all of the UPC records. A fix was made based
on duplicate matching by filename. Any records from a file with
the same name as the one being imported will now be deleted and
reinserted with the values of the current file. This should resolve
issues with records missing from the import, regardless of matching
date/times, identifiers, category/subcategories, etc. |
CNEBT-102, SUG-938 |
Reference Utility |
Food Items |
Issue: When an infant is certified and issued
benefits at six months old, the quantity of fruits and vegetables
issued is more than that configured in the Food Items screen. A NBF infant at
six months is issued 128 jars instead of 32. A FBF infant at six
months is issued 256 jars instead of 64.
Resolution: This
issue affected infant fruits and vegetables when a max exception
existed. The Max Exception quantity (in ounces) was not being
divided by the container formulation units defined in the Food Item Wizard (1 of 3).
A fix was made to correct this issue. |
CNEBT-105 |
Clinic |
Add/Replace Set of Benefits |
Issue: Users would like to be able to extended
a certification by 30 days as per regulations, providing a 7th
month of benefits in certain cases. This functionality exists
for checks, but is not available in the EBT system.
Resolution: The
Add/Replace Set of Benefits
screen has
been modified for EBT. The new EBT functionality calculates the
additional set's FDTU = Expected Cert End Date + 1 day.
This may be different from the certification
end date that is displayed for the participant if the State business rule allowing certifications
to the end of the month is enabled. The Expected Cert End Date
can be described as the Last Expected LDTU, or 6 months from the
First FDTU of the current certification. Note that this change
is per the customer's request and is slightly different from the
process used for adding a set of checks. This change affects only
EBT; adding a set of checks will not be changed.
Additionally, code was added to calculate
a "LastLDTUBeforeEndOfCert" value from the LDTU of the
last set of benefits issued after the certification effective
date.
In some instances, pseudo certs affected
the ability to issue an additional set of checks as they were
using the certification effective date instead of the certification
start date. The code was changed to use the CertStartDate to fix
this issue.
The two following scenarios help describe
these changes:
Scenario 1: If
there are no outstanding or future issuances for the household,
only a single EBT issuance will be added. The Add/Replace Set of Benefits
screen will
function in the same manner as it does when adding a set of checks.
When the user clicks
OK,
the Aggregated Issuance for EBT Account
screen will
be displayed, allowing the user to complete the transaction.
Note that no future household LDTUs will
be synced against an issuance that was the result of this process
when the Add Set LDTU is after the participant's Certification
End Date. This is done to minimize the number of partial packages
that are created for a household in an attempt to keep the LDTU
synced. As a result, the next issuance after an Add Set for the
participant may be a partial package in order to sync with the
household. Since this would only occur with a recertification,
this was determined to be an acceptable result.
Scenario 2: If
there is at least 1 outstanding or future issuance for the household,
the additional benefit will need to be split in order to give
a full 30 day period and still meet the EBT LDTU syncing requirements.
The first issuance cannot be modified. This is the system determined
minimum issuance that can occur. The second issuance is optional
and will allow the user to adjust the remaining package size and/or
the LDTU for the second issuance. When the user clicks OK,
the Aggregated Issuance for EBT Account
screen will
be displayed, allowing the user to complete the transaction.
Note that this scenario does not address
situations where there is more than one future benefit outstanding
for the household. In those situations, the additional set of
benefit's second issuance LDTU may not sync with the other future
benefits' LDTU. Since the combination of both issuances could
allow for a full 30 days to redeem, and since the next possible
FDTU will not be affected for the participant, this was determined
to be an acceptable result. |
CNEBT-107 |
Reference Utility |
Notification List |
Issue: The Notification List
screen allows
only 10 people to be notified.
Resolution: This
was caused by using a string data type in the dataset. This was
changed to an integer, resolving the issue. There is no longer
a limit on the amount of Notification List
entries that can be added. |
CNEBT-108,
CNEBT-121 |
Reference Utility,
Clinic |
Food Item Wizard (3 of 3),
Aggregated Issuance for EBT Account |
Issue: Users are required to link Category/Sub-category
to food distribution items in the Food Item Wizard (3 of 3);
however, there are no available Category/Sub-category designations
for quarts when linking milk food items.
When attempting to issue and print benefits
for the milk sub-category, users receive the following standard error messages
from the Aggregated Issuance for EBT Account
screen: Invalid/Missing
Category (Not on J.P. Morgan EFS host Category/Sub-category file),
and EBT Category not established for Distribution ID: 1022.
Resolution: The
check was relaxed for Category/Sub-category mapping when adding
or editing a distribution item with a base food category of milk
in the Food Item Wizard (3 of 3).
A blank Category/Sub-category is now allowed for milk food items.
A code change was made for EBT, suppressing
the "EBT Category not established for Distribution ID"
standard error message
when the base food category is milk. This allows for the distribution
item to be linked to the food item, while avoiding issues when
the distribution item does not have a category and sub-category
already mapped. |
CNEBT-111 |
EBT |
Timeout |
Issue: The 'timeout' message is unclear.
Users would like for it to be more intuitive.
Resolution: The
'timeout' message was changed to: "Cannot Connect to EBT
Processor - Connection Timed Out". |
CNEBT-112 |
Clinic |
Issue Benefits |
Issue: Some benefits were recorded as issued
in SPIRIT but not in the EBT Processor.
Resolution: The
code used to generate issuance numbers failed to create unique
numbers when two users requested an issuance from the web service
at exactly the same time, while logged in with the same user name.
The code has been modified to ensure unique issuance numbers,
and has been wrapped in a SQL transaction to further reduce the
chance of this happening again. Additionally, another check will
be performed on the issuance number from the client side. |
CNEBT-113 |
Clinic |
Certification Guided Script |
Issue: Users receive the following standard error message
when attempting to access the Health Information
screen in
the Certification Guided Script:
"Conversion from string "" to type 'Double' is
not valid".
Resolution: The
code was modified to check for a valid value before it is assigned
to a variable. |
CNEBT-124 |
Vendor |
Approve New MAR Prices |
Issue: When purchases have been made, the
system is not calculating the prices correctly. Quarts of milk
are being calculated as gallons. The price for a quart should
be a quart price, not a gallon price.
Resolution: In
this issue, MAR prices were being calculated at the whole unit
of the given sub-category. Instead, they should be calculated
at the UPC unit in order to work with the EBT Processor
system. Calculations were modified to claimamount / upcpackagesizeunits
so that the UPC price is per item instead of per whole unit of
the given sub-category. When the MAR is calculated at the sub-category
level, the calculation will remain as claimamount / redeemedquantity
/ upcpackagesizeunits. The result is then multiplied by the UPC
quantity. |
CNEBT-125 |
Vendor |
Approve New MAR Prices |
Issue: When approving new MARs in the Approve New MAR Prices
screen, it
is inefficient to select
each item individually in order to mark them as approved.
Resolution: Two
Select All
and Deselect All
buttons were added
to the Approve New MAR Prices
screen, allowing
users to select
all foods at once and approve them, deselect
all foods at once, or individually select
or deselect
items as before. |
CNEBT-128 |
Clinic |
Participant Folder |
Issue: The Nutrition Education Contact
tab of the Participant Folder
is not displaying group education topics for participants on-site.
Resolution: The
TopicCode was not being retrieved for WorkOnSiteEducationTopics,
which was disallowing topics from being saved. This was corrected. |
CNEBT-129 |
Clinic |
EBT Transaction History Detail |
Issue: Users receive the following standard error message
when attempting to view the EBT Transaction History Detail
screen: "Index
0 is either negative or above rows count".
Resolution: This
was caused by Category/Sub-categories that were not defined in
SPIRIT, but were being returned from the EBT Processor
(possibly from previous testing). This should no longer cause
a standard error message
and instead will display "unknown" in the description
of the Category/Sub-category of the EBT Transaction History Detail
screen. |
MN-308, ENH-37 |
Clinic |
Benefits History |
Issue: The FDTU on the printed check does
not match the one displayed on the Benefits History
tab of the Participant Folder,
or on the Benefit Details
screen.
ENH-37 changed benefit printing so that the
FDTU (First Date to Use) always prints the Expected FDTU on the
first set of benefits instead of the Actual FDTU when issued late.
The system should display the FDTU printed on the benefits anywhere
the FDTU is displayed in the system. However, the system should
continue to maintain and display the actual issue date as appropriate.
Resolution: When
participants pick checks up late, the actual FDTU differs from
the printed FDTU. The existing FDTU and LDTU dates will appear
as they did previously on both the Benefits History
and Benefit Details
screens.
A new "Printed FDTU" column
will be added to both locations to show the different FDTU in
these situations.
When a Printed FDTU is not available (the
database field is NULL), the Benefits History
tree view will display the Agency and Clinic values immediately
after the "Printed FDTU" label as a placeholder. |
MN-412 |
State Office |
Manufacturer Brand Type List |
Issue: Users receive the following standard error message
when adding a Manufacturer Brand Type List
record: "Brand Type Root element is missing".
Resolution: This
standard error message
occurred when converting the string to xml using a translator
object. The code was corrected to resolve this standard error message. |
MN-431 |
Clinic, State Office, Central Administrative Site |
BMI Growth Grids |
Issue: The plot points on the BMI Growth Grids do not appear
to match the percentile lines. Additionally, recumbent measurements
(length) should not be included on the BMI Growth Grids. Only standing
height measurements should be used. BMI should not be plotted
until a child is measured while standing.
Resolution: Two
new views have been created to provide the required data for the
Growth Grids:
V_LENGTHWEIGHTAGE and V_WEIGHTLENGTH. These views pull in the
percentile data from LGTHAGE, HTAGE, WTHEIGHT, and WTLENGTH tables
which have been confirmed as matching the CDC data files. The
views convert CM to INCHES and KILOGRAMS to POUNDS since the CDC
data is provided in metric units only.
Code was added to limit the rows that appear
on some of the data grids below the Growth Grids
graphs. The new code limits the data to the same range as the
graph.
Additional limits were placed on which data
points will be plotted. If the child is less than 2 years old
and standing, that point is not shown. If the child is more than
3 years old and recumbent, that data point is not shown.
Note: When compared
to the CDC printed Growth Grids,
there are small differences since the CDC Growth Grids
have their own accuracy issues due to scaling and how grids are
combined. When checking data points, compare the SPIRIT Growth Grids to the converted
values from the CDC data sheets. |
MN-433 |
Clinic |
Food Prescription |
Issue: Uses are unable to issue the maximum
amount of formula to an infant receiving Food Package III and
no supplemental foods.
Resolution: Code
has been added to set the WicStatus+BFAmount quantity of a food
item, as entered in the Food Item Wizard (1 of 3).
If a max exception entry exists, it will override the quantity
later in the code logic. This should provide the desired functionality
for those environments that may not be using a standard max exception
table.
Changes have been made specifically for Food
Package III when adding food items to an infant 6 months or older.
If the user attempts to add the maximum 4-5 month quantity of
formula to the Food Prescription,
and there are solids present, the user will be given the option
to have the system remove those non-formula items. If the user
selects
"No", the system will add the formula at the standard
6 month quantity. If the maximum 4-5 month quantity of formula
is already prescribed and the user attempts to add non-formula
items, the user will be prompted to let the system decrease the
amount of formula to the 6 month quantity. If the user selects No,
the system will disallow the user from adding the selected food
item.
The code was also changed to use the Initial
Quantity value of the food item when the system automatically
adds a formula item or automatically adjusts the formula amount.
This matches the way in which the code currently uses the Initial
Quantity when a user manually adds a food item. |
MN-444 |
Vendor |
Compliance Buy (Participant Information) |
Issue: Users receive an Object Reference
standard error message
when attempting to add a Compliance Buy (Food Prescription).
Resolution: The
breastfeeding amount was missing when retrieving the Basefoodcombinationmaximum,
thus causing the object reference standard error message.
The code was modified to set the breastfeeding amount to "non
applicable" if it is missing.
Compliance buys using default food packages
are now functioning properly. When the Use Default
button is selected, the
database will attempt to match the food package ID and age category
ID of the participant to the default food package in the risk
factor reference folder. If the match is successful, the default
food package will be added. If no match is found, the user will
have the opportunity to manually add a food prescription or adjust
the participant's age in order to find a match.
Note: This is
a short term solution within the constraints of the current business rules which limit flexibility
with age and breastfeeding amount. Larger issues will be addressed
in the near future by Vendor Change Order #9. The goal for this
solution is to prevent standard error messages
and allow users to complete a compliance buy. |
MN-461 |
Scheduled Job Administration |
End of Day |
Issue: NoteSubject standard error messages
are occurring whenever the system auto-generates a note due to
the fact that the notes have not been mapped to a particular Note
Subject.
Resolution: Code
was added to map the newly added NOTETYPE and following NoteSubjects
for auto generated "SystemNotes" in the application:
Benefits Mailed
to Participant Ineligibility
Letter Provided Benefits Replaced Appointments
Reminder Sent via E-mail Official Notification
Printed VOC Document
Produced
Code was added to retrieve the EXTERNALID
values for the "SystemNote" type and for the respective
subject depending on the function. These values were assigned
to the notes object.
Additionally, the Manage Notes screen has been modified
to show system generated notes. These will be controlled by the
newly assigned NOTETYPE value. |
MN-463, SUG-955, SUG-959, SUG-964 |
Clinic, State Office, Central Administrative Site |
Woman Health Information |
Issue: There should not be a Diabetes Mellitus
check box in
the Any History section of the Postpartum Information
screen. It
should be removed.
The Diabetes Mellitus
check box in
the Postpartum Information
section of the Postpartum Information
screen is
not being selected
as desired to indicate if there is any history of Diabetes Mellitus.
If the participant has a history of Diabetes
Mellitus, the condition should be saved to the Woman table and
the Diabetes Mellitus
check box should
be disabled. This is not happening as desired.
Risk Factor
343 is not consistently being assigned when the Diabetes Mellitus
check box is
selected
and disabled.
Resolution: Changes
were made to remove the Diabetes Mellitus
check box from
the Any History section. If the Diabetes Mellitus
check box is
selected
in the Postpartum Information
section as a result of Diabetes Mellitus in the participant's
history, the check box
will be disabled. Additionally, a fix was made for Risk Factors that were
not consistently being assigned. |
MN-464, SUG-928, SUG-929, SUG-931,
SUG-972 |
Clinic, State Office, Central Administrative Site |
Woman Health Information |
Issue: When the Gestational Diabetes
check box is
selected
in the Current Pregnancy Information
section of the Pregnancy Information
screen, the
system is auto-selecting
the Gestational Diabetes
check box in
the Any Pregnancy History
(this is as intended). However, it is then assigning both Risk Factor 302 and Risk Factor 303 incorrectly
based on its selection.
Instead, for participants with no previous history of gestational
diabetes, the system should assign Risk Factor
302 and save the indicator for Risk Factor
303, but not actually assign 303 to the participant at the end
of the certification process.
Resolution: Previously,
whenever adding Risk Factor
302 (Gestational Diabetes), the system was also flagging the Woman
record for history of gestational diabetes (Risk Factor
303). Now, Risk Factor
303 will only be assigned when starting a certification attempt
if one of the following conditions is true:
There is a
previous certification where Risk Factor
302 was assigned There is a
previous certification where Risk Factor
303 was assigned There is a
previous certification where Pregnancy.GestationalDiabetes
was set to "Y" There is a
previous certification where Woman.HasHistoryGestationalDiabetes
was set to "Y"
Note: It is possible
that the customer database has many participants with Risk Factor 302/303 already
assigned. If one of these participants is in an active certification,
these Risk Factors
will not be picked up and automatically assigned by the system.
This means that if the user assigns Risk Factors
in the Assign Certification Risk Factors
screen, Risk Factor 302/303 will
be present in the list of available Risk Factors
to select.
Because of the new implementation and the fact that the database
columns to support
these Risk Factors
didn't exist prior to release 2.09, there is no way to handle
this situation. The next time the user recertifies these participants,
Risk Factor
303 will be assigned and the Woman record will be flagged. |
MN-468, SUG-925 |
Clinic |
Pre-pregnancy BMI
Growth Grids |
Issue: Risk Factor
131 (Low Maternal Weight Gain) is not being assigned correctly
when the participant's weight plots below the bottom line of the
Pre-pregnancy BMI
Growth Grids.
Resolution: Code
was added to check if the pregnant participant's weight was being
plotted below the "Low" weight gain line on the Growth Grids after the
13th week. |
MN-485 |
Clinic |
Demographic Information |
Issue: Pseudo Certs are being inappropriately
created when Demographic Information
is saved in the Participant Folder.
Resolution: A
fix was made, correcting problems where Pseudo Certs were being
created any time Demographic Information
was saved. |
SUG-681 |
Clinic |
Issue Benefits |
Issue: The default printer tray selection is
being ignored when issuing benefits. Benefits are always being
printed to tray 1.
Resolution: This
was an issue with the overlay. Source Technologies hard-coded
the tray to which checks were printed in the overlay. That part
of the overlay has been removed. Changes were made to PCI commands
to map and print from the selected
tray in the Default Printers screen.
To correctly map the tray values selected in
the Default Printers screen with Source Technologies'
internal tray value, a State business rule
has been added: CHEQUE_PRINTERNAME_TRAY_OVERRIDE.
This business rule
is used to override the default printer tray configuration in
the overlay.
If the business rule
is set to "Y", then the system will retrieve the tray
configuration from the printerconfig and printertrayconfig tables and use that value
to print checks. Values must be seeded in these tables before issuing checks.
This is a manual step as there is no interface provided for seeding
values.
If the business rule
is set to "N", then the system uses the default printer
settings tray value (as configured in the overlay) to print checks.
Note: This resolution
was tested against the Minnesota and Chickasaw environments. It
passed all scenarios tested in these environments for benefits,
documents, and reports. Note that changing the business rule requires the PC to
be restarted in the Chickasaw environment, but not in the Minnesota
environment. |
SUG-895 |
State Office |
List of Dual Reported Participation Cases Report ENR002 (Output) |
Issue: When printing the List of Dual Reported Participation Cases Report ENR002 (Output),
the Clinic number is being truncated.
Resolution: This
issue occurred only when the report was displayed on screen, displayed
on screen and then printed, or sent directly to the printer. It
did not occur when saved to PDF or when the PDF was printed. A
fix was made to correct this issue on printed reports. |
SUG-922 |
State Office |
PC20XX File (Output) |
Issue: Field Name: Participation in Medicaid
(10c). This field appears to be generated at the household level
rather than at the individual level.
Resolution: The
code will now correctly flag an individual if their IncomeContact
record has a "Y" in the Medicaid flag, or if anyone
in their household is an infant or a pregnant woman and that person
has a current certification and their IncomeContact has a "Y"
in the Medicaid flag. |
SUG-930 |
Clinic |
Certification Guided Script |
Issue: When certifying or recertifying a
child participant, users cannot proceed past the Health Information
screen and
cannot complete the certification process. This issue occurs when
users select
No
in the "Ever Breastfed" section, but are still required
to enter breastfeeding dates.
Resolution: Code
was added to correctly handle No
and Unknown
radio button
selections
for "Ever Breastfed" in the Health Information
screen. This
code existed for a selection
of Yes
but was missing for No
and Unknown.
Controls in the "Feeding Information" group will now
be enabled or disabled correctly. |
SUG-953 |
State Office |
PC20XX File (Output) |
Issue: Fields 15a and 15b. Many children
on file have no blood data reported; however, many of their records
do have a value, just not from the current certification. PC20XX
guidance suggests that the most recent certification data should
be used.
Resolution: The
most recent measurement data will now be used if there is no value
for the current certification. |
Recertification |
CLD-005 |
State Office |
Report |
The
Enrollment Monthly Report CLD005 (Output)
has been through a recertification process to correct format,
data, DFDD content, and add minor clarifications as necessary. |
CLD-009 |
State Office |
Report |
The
Monthly Redemption Unduplicated Report CLD009 (Output)
has been through a recertification process to correct format,
data, DFDD content, and add minor clarifications as necessary. |
CLD-029 |
Clinic, State Office |
Report |
The
Participation vs. Enrollment Monthly Report CLD029 (Output)
has been through a recertification process to correct format,
data, DFDD content, and add minor clarifications as necessary. |
OPR-002 |
State Office |
Report |
The
Non-participation Reason by Category Report OPR002 (Output)
has been through a recertification process to correct format,
data, DFDD content, and add minor clarifications as necessary. |