Issue# |
Application Module |
Primary Function |
Detail |
Reported Issues |
DFDD-81 |
Clinic |
Benefits (Issue Benefits) |
Issue: The DFDD does not specify the default
date for the Selected LDTU of
calendar control
when the Selected LDTU of
radio button
is selected
on the Benefits (Issue Benefits)
screen.
Resolution: When
the Selected LDTU of
radio button
is selected,
the calendar control
defaults to the earliest possible cycle adjustment for the household.
This information has been added to DFDD. |
DFDD-82 |
Clinic |
Pregnancy Information |
Issue: The Date Prenatal Care Began
calendar control
on the Pregnancy Information
screen incorrectly
documented the mask to be "##/##/####". The calendar control only allows
the entry of a month and year.
Resolution: The
DFDD has been updated to reflect the application. The Date Prenatal Care Began
calendar control
mask has been changed to "##/####". |
DFDD-83 |
Central Administrative Site,
Clinic,
Direct Distribution,
Financial Management,
State Office,
System Administration,
Vendor |
Generate
Report screens |
Issue: If a default printer has not been
set up, reports from the Generate Reports
screen that
have the Display on Screen
radio button
selected
do not display. The DFDD does not specify that the Display on Screen
radio button
requires a default printer.
Resolution: The
DFDD has been updated for all generate report screens
to include the requirements of the Display on Screen
radio button.
Additionally, the processes of the OK
button on the
generate report screens
have been updated to include the system response if no default
printer is currently selected. |
DFDD-85 |
Clinic |
Pregnancy Information |
Issue: On the Pregnancy Information
screen, the
system allows a user to enter a LMP Start Date that matches the
same month and year as the date entered in Last Pregnancy Ended.
According to the DFDD, a standard error message
should display informing the user that the Last Pregnancy Ended
date must be before the LMP Start Date.
Resolution: The
DFDD has been updated to reflect the application. The DFDD now
states that the value entered in for Last Pregnancy Ended can
be less than or equal to the value of the LMP Start Date. |
DFDD-86 |
Clinic |
Child Health Information |
Issue: The DFDD does not document the SETSTARTDATETODOB
business rule in
the business rule
appendix or on the Child Health Information
screen.
Resolution: The
information is currently in the DFDD, and no change was made. |
DFDD-87 |
Clinic |
Benefits (Issue Benefits) |
Issue: The DFDD states that the system checks
for pending benefits on the Benefits (Issue Benefits)
screen prior
to beginning a recertification. This caused the system to enforce
issuing pending benefits, but this was not the desired system
response. Instead, the system should allow a recertification attempt
even when pending benefits remain.
Resolution: The
DFDD topics for the Participant Folder toolbar
and Participant Activities menu
have been updated to remove the check performed by the system.
The standard confirmation message
that was displayed should pending benefits exist prior to a recertification
has been removed from the DFDD. |
DFDD-88 |
Clinic |
Benefits (Issue Benefits) |
Issue: The initializing the interface section
on the Benefits (Issue Benefits)
screen states,
"The Household Member Information
data grid is
populated with members of the household assigned to the local
clinic."
The data grid
is actually populated with all members of the household, not just
those assigned to the local clinic,
as described under the screen elements for the Household Member Information
data grid.
Resolution: The
DFDD has been updated to reflect the application. The initializing
the interface section now states, "The Household Member Information
data grid is
populated with members of the same household." |
SUG-643 |
State Office |
Add New Inventory |
Issue: When trying to enter new breastpumps
on the Add New Inventory
screen, several
standard error messages
are received about setting the compatibility level for the current
database and SQL server.
Resolution: This
issue is caused by the SQL scripts that were developed for SQL
2000 being run against a SQL 2008 database when the compatibility
level is set to 100. The data views V_Products and V_CertificationNotice
were modified to replace the non-ANSI syntaxt (*=) with the ANSI
standard LEFT OUTER JOIN, and this allows the database to be run
with the compatibility level set to 100. |
SUG-1173 |
Clinic |
Issue Benefits |
Issue: The following standard error message
is received when a user clicks
on the Issue Benefits
toolbar button
in the Participant Folder:
"The conversion of a varchar data type to a datetime data
type resulted in an out-of-range value". The system is creating
records with null as the CertEndDate and CertEffectiveDate. On
occasion, the system is accessing a certification record with
a null value.
Resolution: This
was caused by an old certification record with a null end date
(CertContact records with null values in the CertEndDate column). The data view has been
modified to exclude such records since they are invalid. Additionally,
the code has been modified to exclude null records that are pulled
directly from the table,
which has resolved the issue. The creation of null records will
be addressed in a later release. |
SUG-1193 |
Clinic |
Participant List and
Participant Folder |
Issue: A certified woman's status is changed
from breastfeeding to non-breastfeeding, but the certification
end date did not change in the Participant Folder.
The change in status is not reflected on the Participant List
screen. The
certification is still effective for a year, and the certification
end date does not change.
Resolution: The
certification end date is being changed in the system, but it
is not visible to the user until a search is performed again.
The code has been change to refresh the Participant
List data grid
on the Participant List
screen with
the new WIC status. Additionally, a standard warning message
has been added to the Participant Folder
with the text, "Certification end date will change to {##/##/####}."
This standard warning message
confirms to the user that the WIC category has been changed. |
SUG-1339 |
Clinic |
Benefits (Issue Benefits) |
Issue: An infant participant born on January
30 cannot be issued 1-month benefits on the Benefits (Issue Benefits)
screen when
the benefit issuance date is February 28 of the same year. When
a user attempts to issue benefits to a participant with an end
of month birth date, and the issuance date is February 28, a standard error message
is displayed and the benefits cannot be issued. If the issuance
date is moved to March 1, the benefits can be issued.
Resolution: The
create food prescription functionality uses the AddMonths functionality
to add months to the participant's date of birth to determine
the benefit issuance date. The GetAge category functionality uses
different logic that does not account for the AddMonths functionality.
When a participant has a date of birth of 1/31/11, the benefits
are created for 2/28/11 based on the AddMonths functionality.
However, the GetAge category functionality calculates the age
of the participant on 2/28/11 as being 28 days old. Therefore,
the system does not recognize the participant as being 1-month
old. The GetAge category functionality has been changed to account
for the month of February when a participant has an end of month
birthday. |
SUG-1454 |
Clinic |
Participant Folder |
Issue: When the Print Certification Notice
menu option
is selected
from the Participant Activities menu
of the Participant Folder,
the Spanish Certification Notice that prints is different from
the English Certification Notice.
Resolution: The
Spanish Certification Notice that is generated was specific to
Minnesota.
A new version of the Spanish Certification Notice has been created
for other clients. |
SUG-1465 |
Clinic |
Capture Electronic Signature (for Receipt of the Rights and Responsibilities Statement) |
Issue: When certifying multiple family members
on the same date, the system is requiring a signature for each
participant on the Capture Electronic Signature (for Receipt of the Rights and Responsibilities Statement)
screen. For
participants certifying on the same date, the signature from the
first completed certification should populate the signature box
and be saved for each record.
Resolution: Code
has been added to verify if a signature is captured for a household
on the current day. If a signature was captured on the current
day, it is displayed on the Capture Electronic Signature (for Receipt of the Rights and Responsibilities Statement)
screen. Otherwise,
the screen
is displayed without a signature. |
SUG-1470 |
Clinic |
Certification Guided Script
and Demographics |
Issue: When certifying more than one participant
for the same household, "Pending Proof" is selected from
the Residency Proof
drop-down list box
but it is not being carried over to the other household members
during their certification. Additionally, if the Residency Proof
drop-down list box
value is changed on the Demographics screen of the Participant Folder
for one household member, it is not changed for the other household
members.
Resolution: When
"Pending Proof" is selected
during the Certification Guided Script
and there is another participant in the same household who is
certified on the same date, the "Pending Proof" selection auto-populates.
If the certifications do not occur on the same date, "Pending
Proof" does not auto-populate. Any other selection
from the Residency Proof
drop-down list box
auto-populates during the Certification Guided Script
based on the participant who has the most recent residency verification
date. The "Pending Proof" selection
only transfers during the Certification Guided Script
if the ENABLECOPYRESIDENCY
business rule is
set to "Y".
Any change to Residency Proof in the Participant Folder
transfers to all household members in a valid certification except
"Pending Proof". |
SUG-1471 |
Clinic |
Demographics |
Issue: When a new certification is started,
but not completed, for a participant and then the incomplete certification
is removed, the ID Proof and Residency Proof
drop-down list boxes
are cleared on the Demographics screen of the Participant Folder.
Resolution: The
code has been changed so the ID Proof and Residency Proof
drop-down list boxes
retain their previously saved values when an incomplete certification
is removed. |
SUG-1486 |
Clinic |
Risk Factors |
Issue: A record with a pseudo-cert causes
the Risk Factors Display
tree list on
the Risk Factors screen to display records
out of chronological order.
Resolution: The
Risk Factors Display
tree list was
being sorted by CertificationID, which caused the certifications
to be out of order because the certifications were not assigned
their IDs based on the CertEffectiveDate. The Risk Factors Display
tree list has
been modified to sort the certification records based on both
the CertEffectiveDate and the CertStartDate. This ensures the
certification records are displayed in chronological order. |
SUG-1500 / SUG-1504 / SUG-1593 |
Clinic |
Demographics |
Issue: When certifying a new household with
multiple members, an option is selected
from the Household Smoking
drop-down list box
on the AdditionalInfo1
screen. After
certifying the first participant of the household, the next participant
also required an entry in the Household Smoking
drop-down list box.
The system allows the user to complete the certification when
the Household Smoking
drop-down list box
is blank. This information should be saved and transferred to
all members of the household.
Additionally, Risk
Factor 904 is not assigned to all household members when "Yes"
is selected
from the Household Smoking
drop-down list box.
If every household members' Participant Folder
is open during a certification attempt, the Household Smoking
drop-down list box
selection
is not transferred from one member's Participant Folder
to another.
Resolution: The
code has been change to transfer one participant's selection from
the Household Smoking
drop-down list box
to all other participants within the same household. This transfer
occurs regardless of whether the other household members are present
during certification. Additionally, the selection
is transferred to any household members added at a later date.
If more than one Participant Folder
is open for a household, the selection
made in Household Smoking does not transfer to the other household
participants. There is no automatic refresh that updates the household
changes made in one Participant Folder
so the Household Smoking selection
is not displayed in another participant's Participant Folder
within the same household. The database is updated with the Household
Smoking selection,
but the Participant Folder
for other household participants is not updated with the new information
until the screen
is refreshed by updating data or reopening the Participant Folder.
If the Household Smoking
drop-down list box
is set to "Yes", then Risk Factor 904 is assigned to
all participants who are currently in a valid certification. Risk
Factor 904 is not assigned if "No" or "Unknown"
is selected.
If the Household Smoking selection
changes from "Yes" to "No" or "Unknown",
Risk Factor 904 is removed from all participants who are currently
in a valid certification. |
SUG-1516 |
Clinic |
Food Item Distribution |
Issue: A nine-month old infant with special
formula is shown to receive six cans for the first two benefits,
then five cans for the third benefit on the Food Item Distribution
screen. When
the checks for the benefits are printed, six cans of special formula
are given for each check instead of six cans for two checks and
five cans for the third check.
Resolution: The
code has been changed so the maximum exception logic is used for
special formula. The Food Item Distribution
screen currently
uses the exception logic code, therefore it displays the correct
benefit amounts. When issuing benefits, the exception logic code
is not used due to a prior change in the code to fix the issuance
of cheese benefits. The changes made have been reversed to correct
this issue. |
SUG-1550 |
Clinic |
Risk Factor |
Issue: Risk
Factor 371 was incorrectly removed from a pregnant woman who
smoked three cigarettes per day. For postpartum women, the system
is checking for the standard risk factor assignment of greater
than zero (>0) cigarettes per day. For pregnant women, the
system is checking the high risk threshold to determine if Risk
Factor 371 should be assigned and not just flagged high risk.
Depending on the value defined for the high risk threshold, the
system may remove Risk Factor 371 because the number of cigarettes
the woman smokes does not cross the high risk threshold.
Resolution: The
code was written that if RiskFactorReference.HighRisk is "Y"
in the RISKFACTORTHRESHOLD table,
the participant received the risk factor and then the high risk
flag. The system never checked the high risk criteria. The code
has been changed for Risk Factor 371 to use the standard threshold
for pregnant women when assigning the risk factor. The risk factor
is applied with the high risk flag only if the participant smokes
more than the standard and high risk threshold amounts, and RiskFactorReference.HighRisk
is set to "Y". For the high risk threshold, the system
uses the threshold value on the AssignmentType "H" and
the corresponding ThresholdID. For non-high risk, the system uses
the threshold value on the AssignmentType "S" and the
corresponding ThresholdID. |
SUG-1552 |
System Administration |
Approved Product List (APL) File |
Issue: When the APL file is built in the
System Administration
application using MAR (Maximum Allowable Reimbursement) values,
there are not enough transactions to calculate a new MAR for some
peer groups. As a result, the old subcategory for MAR is displayed
in the APL file.
Resolution: The
code has been changed so the APL file is built from the values
in the UPC table
rather than the MAR table.
The UPC.FOODCATEGORYCD is used as both the category and subcategory
instead of the MAR category and subcategory in Wic.FoodInstruments.JPMAPLFile.LoadAPLFile. |
SUG-1582 |
Clinic |
Food Adjustment Wizard |
Issue: An infant or child participant cannot
have a prescription formula added to their benefits on the Food Adjustment Wizard
screen because
no formula is available for selection.
The Food Adjustment Wizard
screen only
adds the current benefits and ignores previous benefit issuances.
Resolution: The
code has been changed so the FDTU and LDTU dates are taken into
account when deciding to choose the prescription formula or the
existing issuance on the Food Adjustment Wizard
screen. The
system now allows additional quantities of formula for the current
benefit issuance. |
SUG-1639 |
Direct Distribution |
Direct Distribution Redemption |
Issue: On the Direct Distribution Redemption
screen, when
the Print Food List
button is clicked, the
font of CVB items, and all items that follow it, print in a smaller
font. The check printing code has a condition that reduces the
font if the item quantity field is greater than two characters.
This is necessary for printing paper checks.
Resolution: The
code has been changed to add the issuance type to the check printing
code and to include a condition not to reduce the font size for
the printed food list. The check font size is still reduced accordingly. |