 |
Identified Issues with Current |
This page will provide up-to-date information about any issues found by Local Agencies once Release 2.17.08 is installed on Production.
It also describes bugs/issues that were introduced by Releases 2.17.07, 2.16.06, 2.15.06, and those identified during testing that were unable to be fixed in time for the Release and are also documented in the 2.17.08 Release Document.
These issues should have minimal impact on the HuBERT clinic application and will be fixed in a future Release.
Information provided about each bug includes a description, "What the User Should Do" or a work-around, and resolution (if known).
- Release 2.18.06 - from Release Document
- Issues Identified Since Release 2.17.08 Installed on Production in MN
- Issues Identified Since Release 2.17.07 Installed on Production in MN
- Release 2.17.07 - from Release Document
- Release 2.16.06
- Release 2.15.06
Release 2.18.06 - from Release Document
* * * * *
Benefit Issuance: System Will Allow Issue of More than One Month of Benefits for Participants with Pending Proof of Residency (EGT-157, SUG-1938)
Description: The system is allowing issuance of more than one month's of benefits when participants are pending Proof of Residency.
What the User Should Do: Issue only one month's of benefits (may be a partial syncing package and a full package). Set an alert to remind the next person that assists the participant that Proof of Residency is required before issuing any more benefits.
Resolution: This is currently assigned to Release 2.19.
Mid-Certification Assessment (MCA): Adding Unknown Ht/Wt in MCA Causes Ht/Wt Node of Most Recent Cert in Certification History Tab to Update with MCA Staff Name and Date/Time (NIN-201)
Description: When an Unknown Birth Height/Weight is added in the MCA, the system is writing a CertStartDate to the ANTHROPCONTACT table. This results in the most recent certification information for Height/Weight to be updated in the Certification History tab once the MCA has been completed.
What the User Should Do: This is a display issue.
Resolution: This is currently assigned to Release 2.19.
Mid-Certification Assessment (MCA) Due Date: If Infant Is Certified via VOC and There Are Fewer than 9 Months Left in the Certification Period, the System is Not Calculating a MCA Due Date (EGT-21)
Description: The system should calculate a MCA Due Date whenever an infant is certified based on the infant's Date of Birth (plus 9 months). If there are fewer than 9 months left in an infant's certification, and that infant was certified via VOC, the system is not calculating the MCA Due Date. Since the MCA icon is enabled based on the MCA Due Date users will be unable to use the MCA Guided Script to perform the infant’s MCA.
What the User Should Do: All infants should have a MCA between 9-11 months. If the system does not calculate a MCA Due Date, write an alert to indicate when the MCA is due. Since the MCA icon will be disabled, the Midcert should be completed in the Participant Folder (same as before Release 2.18.06 was installed on Production).
Resolution: This is currently assigned to Release 2.19.
Output: Risk Factor Descriptions Not Printing in Participant Summary (NIN-238)
Description: The descriptions for assigned risk factors are not printing on the Participant Summary. However, the risk factors IDs are.
What the User Should Do: This is a display issue on the printed document.
Resolution: This is currently assigned to Release 2.19.06
Report: Mid-certification Assessment (MCA) Report Displaying Pseudo-Cert Dates for Cert Effective Date (EGT-21)
Description: If a participant has had a pseudo-cert created during their most recent certification period, the MCA report is displaying the Cert Effective Date associated with the pseudo-cert instead of the start of their certification period.
What the User Should Do: This is a display issue. The MCA Due Date is still displaying correctly. If you need to know the actual Cert Effective Date for some reason, the Cert Effective Date for women and children should always be 6 months to the date before the MCA Due Date. Since the MCA Due Date is 9 months from the date of an infant's birth date, the actual Cert Effective Date would have to be looked up for infants (on the Show Details panel in the Participant Search screen).
Resolution: This has not yet been assigned to a Release.
Report: Reported Participation Monthly Report – CLD007 - Not Sorting Correctly (NIN-232)
Description: The Reported Participation Monthly Report when generated during End-of-Month (EOM) for Grantee, Agency and Clinic is not sorting in top-down order and one of the Grantees appears to be listed more than once.
What the User Should Do: This is a display issue. All information is provided in the report.
Resolution: This is currently assigned to Release 2.19.
Report: Standard Message Does Not Display Indicating EOM Must Be Run to Generate Data when Running Initial and Closeout Participation – FDI013 – Report for Month for which End-of-Month (EOM) Hasn't Yet Been (NIN-237)
Description: If a user runs a report based on data generated during EOM for a month in which EOM hasn't yet been run, the system usually displays a standard message indicating "The Month/Year selected must be less than or equal to the current month/year…". This message is not displaying when generating the Initial and Closeout Participation report for a month in which EOM hasn't been run.
What the User Should Do: Do not run the Initial and Closeout Participation report for a month in which EOM hasn't yet been run. If such a report is run, the system will generate a blank template.
Resolution: This is currently assigned to Release 2.19.06.
SOAP Notes: Age-Adjusted Growth Percentiles Not Displaying in SOAP Note (NIN-209)
Description: For children under 2 who were born premature, the system adjusts their age when displaying the length/age and weight/age percentiles on the Growth Grids. However, in the SOAP Notes, non-age-adjusted percentiles are displaying next to the measurements.
What the User Should Do: This is a display issue in the SOAP Note. The measurements are correct in the SOAP Note and both the measurements and percentiles display correctly in the Growth Grids.
Resolution: This is currently assigned to Release 2.19.
Issues Identified Since Release 2.17.08
Installed on Production in MN
* * * * *
Posted 5/1/2013
Unduplicated Reported Participation by Category/Breastfeeding Amt and Ethnicity/Race (Calendar Year) Report (CLD035) Not Showing Correct C/O Headers when Run for Previous Months (NIN-12)
Description: When running the Unduplicated Reported Participation by Category/Breastfeeding Amt and Ethnicity Race (Calendar Year) Report (CLD035) for a previous month, the 30DY and ISSD headers are not displaying correctly. The headers of the last 2 months in the report always display as 30DY and ISSD even when those months have been closed out and should display "C/O".
In the example below, the August 2012 and December 2012 reports were run May 1, 2013. Since all of these months have been closed out, they should all display C/O as the header under the Month/Year. However, they still display the 30DY and ISSD headers for the last two months listed with data.
What You Should Do: This is a display issue. Although the headers are not displaying correctly, the data is correct. If the month has been closed out, the data in that column provides your closed-out numbers for that month/year.
Resolution: This issue has been assigned to Release 2.19.05.
Posted 4/29/2013
System Is Incorrectly Assigning Risk Factor 121 (Short Stature) for Children with Height/Age Percentile of NA (NIN-257)
Description: Children with a Height/Age above the top line of the Height/Age grid have a percentile of "NA" (as shown below). When this occurs the system is incorrectly assigning Risk Factor 121. Since this risk factor is only system-assigned, it cannot be removed by the CPA.
What You Should Do: Document in a note that RF 121 was incorrectly system-assigned.
Resolution: This is currently being researched by CSC.
Posted 4/4/2013
System is Assigning Risk Factor 334 Incorrectly for Pregnant Women Certified during their First Trimester (NIN-236)
Description: Risk Factor 334 - Lack of or Inadequate Prenatal Care - should only be system-assigned when the Has Not Received Prenatal Care checkbox is selected and the woman is more than 13 weeks gestation. The system is assigning this risk factor regardless of how many weeks gestation the woman is.
What You Should Do: Document in a note if RF 334 was incorrectly assigned. Assignment should be based on the following criteria from the MN WIC Operations Manual, Exhibit 5-T.
|
|
Resolution: This is tentatively scheduled for Release 2.18.06. Also in Release 2.18.06, the CPA will be able to update the Has Not Received Prenatal Care checkbox and Date Prenatal Care Began field in the Participant Folder so that the RF can assign accurately based on when the participant first goes to the doctor for prenatal care.
Posted 4/1/2013
System Calculates Termination Date Incorrectly when Changing Breastfeeding (BF) Woman to Non-Breastfeeding (NBF) during the Month the Infant Turns 6 Months Old when the Change Is Made on or after the Infant's 6-Month Birthday (EGT-27)
Description: When changing a woman's WIC Category from BF to NBF, or an infant's BF status from fully, mostly-, or some-BF to NBF, and:
- The change is made during the month the infant is turning 6 months old
- The change is made on or after the infant's 6-month birthday
The system is incorrectly terminating mom on the date the WIC Category is changed instead of the last date of that month. It also isn't updating the Cert End Date to be the last date of the month.
Example:
- Infant turns 6 months old on 4/03/13.
- Infant's Amount of Breastfeeding is changed from mostly-BF to Non-Breastfeeding on 4/13/13.
- System terminates mom on current date and displays the termination date of 4/13/13.
- Mom's Cert End Date continues to be 10/31/13.
- System changes mom's WIC Category to NBF (as is correct).
- System creates NBF food package for mom with Effective Date of 4/13/13 (as is appropriate).
- User is unable to issue benefits for last month of eligibility (in this case, April 2013) because mom has been terminated.
NOTE: In this example, the issue only occurs if the BF status is changed any time between 4/03/13 and 4/30/13.
What You Should Do: In order to issue benefits, you will need to perform a VOC certification for mom from within her Participant Folder (if VOC Certification is not enabled in the Participant Activities menu, close and re-open the Participant Folder to refresh it).
- WIC Category = Non-Breastfeeding
- Certification End Date = Last date of month infant turns 6 months old
- Actual Delivery Date = Infant's DOB
- Select YES for "Were you on WIC in this state during the pregnancy related to this postpartum certification?"
Since mom will already have a food package with the current date as the Effective Date, you can issue the last set of benefits for the current month.
Resolution: This is currently being researched by CSC.
Issues Identified Since Release 2.17.07
Installed on Production in MN
* * * * *
Posted 3/19/2013
Object Reference Error Occurs when Food Prescription Has Two Formulas and Editing the Second Formula Selected (NIN-99/SVN-105)
Description: When creating a new food prescription with two formula food items, if both formulas are added then edited, when the user attempts to edit the second formula an Object Reference Error displays.
What You Should Do - Contract and Medical Formula: If you are adding a contract and medical formula into a food prescription:
- Add the Contract formula first;
- Immediately edit the quantity of the Contract formula;
- Add the Medical formula second;
- Edit the quantity of the Medical formula (the system will not allow you to over-issue the amount of formula in the same food prescription)
- Issue the benefits via the Issue Benefits screen
What You Should Do - Two Contract Formulas: If you are adding two different contract formulas into a food prescription:
if providing two different types of formula (such as Powder and Concentrate), you may have to use the Formula Amounts Guide: Maximum Amounts by Federal Regulation (66KB/1 page), which provides the maximum amount of reconstituted formula allowed, and the MN WIC Contract Formula Amounts Guide (PDF: 19KB/1 page), which provides the number of cans allowed and how many reconstituted ounces are provided by each can of formula, to ensure you do not provide more than the maximum number of reconstituted ounces allowed based on breastfeeding amount and age category.
- Create a food prescription that provides a half-package for the first contract formula based on the infant's breastfeeding amount and age category;
- Issue benefits for that formula;
- Edit the food prescription to provide a half-package for the second contract formula based on the infant's breastfeeding amount and age category;
- Go to Benefit Management...Add/Replace and replace the set of benefits just issued.
Please remember to document why two formulas were provided.
Resolution: This will be corrected in Release 2.19.05.
Posted 3/13/2013
Certification History Tab Is Displaying Pseudo-Cert Information Resulting in Signatures Not Displaying on Certification Details (EGT-16)
Description: When a pseudo-cert is created, the certification information is being updated in the Certification History tab. The Certification History tab is only supposed to display information completed during the Certification Guided Script (CGS).
In the print screen below, when the pseudo-cert was created, the Risk Factors created by date, time and staff ID were updated to reflect the user at the time the risk factors were updated and the pseudo-cert created.
This issue is also causing the WIC Category to update if the pseudo-cert was caused by a change in WIC Category, such as Breastfeeding to Non-Breastfeeding.
Lastly, since the certification record is now being linked to the pseudo-cert, the Participant/Proxy Signature and the Staff Member Signature associated with the certification no longer display in the Certification Details window
What You Should Do: This is a display issue.
Resolution: This will be corrected in Release 2.18.06.
Posted 3/13/2013
Contact Type Clearing in Initial Contact when Comment Added on Different Date than Initial Contact (EGT-68)
Description: When an Initial Contact has been previously created and the user updates it by adding a comment on a different date than the Initial Contact…
…the Contact Type is cleared and is changing to NULL in the database.
NOTE! The comment is also being truncated to 8 characters. This issue (SVN-89) was documented in the 2.17.07 Release Document and is detailed below.
What You Should Do: This is a display and database issue.
Resolution: This is currently being researched by CSC.
Posted 3/7/2013
When Plotting Measurements on Growth Grids for Age, System is Incorrectly Age-Adjusting Infants and Children Under 2 Years Old when VOC Certification or Unknown Birth Criteria Checkbox Has Been Selected in Health Information (SVN-142)
Description: When the Unknown Birth Criteria checkbox has been selected for infants and children up to 2 years old, the system is incorrectly age-adjusting the measurements when plotting them on the Length/Age and Weight/Age WHO growth grids.
Example of incorrectly age-adjusted grid:
This issue does not affect children over 2 when the Unknown Birth Criteria checkbox is selected because the system does not age-adjust for children over 2 years old.
What You Should Do: Until this issue is resolved do NOT use the Unknown Birth Criteria checkbox for infants and children under 2 years old. If it has been previously selected and you are trying to review the WHO Length/Age or WHO Weight/Age grid, you will need to de-select the checkbox and complete the information as best as possible. If mom really can't remember, ask her to give you her best guess. If it is a foster parent, you may need to enter an educated guess after some probing questions about whether the child was born early, was small when born, etc.
Resolution: This issue is due to the Gestation Weeks and Days not being populated and the system calculating the participant to be 40 weeks premature. This will be corrected in Release 2.18.06.
Posted 2/25/2013
Resource Not Displaying When the Appointment Listing for Date is Printed by Resource (SVN-134)
Description: When printing the schedule on the View Appointments for Date screen by a selected Resource, the Resource is not displaying in the report header.
What You Should Do: This is a display issue. The printed schedule only displays the Resource when an individual resource is selected from the Resource drop-down. Each schedule has to be printed individually. Until fixed, the user will need to write in the staff person's name.
Resolution: This is currently being researched by CSC.
Release 2.17.07 - from Release Document
* * * * *
Benefit Issuance: Food Prescriptions Are Not Validated When Using Add Set (SVN-86)
Description: Users are able to issue benefits via Add Set with invalid food items. For example:
- Benefits can be added with a Printed First Date to Use (PFDTU) after a Special Special Prescription has expired.
- Benefits can be added for a child over 2 years old that print with the "Whole, 2%, 1% or Fat Free/Skim milk" option instead of the Fat Free/Skim or 1% milk" option.
What You Should Do: Verify the food prescription before adding a set of benefits if a child has a special prescription or has recently turned 2 years old.
Resolution: This is currently being researched by CSC.
Demographics: Register to Vote Field in the AdditionalInfo2 Tab Is Clearing (SVN-80)
Description: The selection for the Register to Vote field is clearing after being re-selected. (Please note that when this field is moved from the MEMBER table to the HOUSEHOLD table, if an infant's or child's record is the last record converted for the household, the Register to Vote field will be cleared for that household. This is expected. This issue occurs after NOT APPLICABLE has been re-selected for the household.)
What You Should Do: This field is required in order to complete Demographics for women. Select NOT APPLICABLE from the drop-down.
Resolution: This is currently being researched by CSC.
Height/Weight: Height Measurements Less than 31 Inches Result in Incorrect Message (SVN-122)
Description: When a participant's height measurement is less than 31 inches, a message displays incorrectly indicating the measurement falls below the lowest point of the grid and the asking the user to verify the accuracy of the measurement. This occurs when adding or editing a measurement.
NOTE: The message displays only the full inches value and not the eighths value. This is another issue with this message.
What You Should Do: As long as the measurement is accurate, click the Yes button on the message.
Resolution: This is currently being researched by CSC.
Initial Contact: Comment Field Truncated to 8 Characters after Saving (SVN-89)
Please Note: Not in Release Document
Description: The Comment field in the Initial Contact dialog is only displaying 8 characters once saved.
What You Should Do: This is a display issue.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Nutrition Assessment: Created Staff ID and Date/Time Not Displaying in Certification History Tab for Nutrition Assessment Completed in Certification Guided Script (CGS) (SVN-77)
Description: When a Nutrition Assessment is added during the CGS, the Certification History tab is not displaying the Create/Modify User and the Date/Time.
What You Should Do: This is a display issue.
Resolution: A CERTHISTORY table will be added in Release 2.18.06, tentatively scheduled for April/May, 2013. This should resolve all issues with the Certification History tab.
Nutrition Assessment: Contact Remains after Removal of Incomplete Certification (SVN-108)
Description: If a Nutrition Assessment is added during the Certification Guided Script (CGS) and the incomplete certification is subsequently removed, the Nutrition Assessment contact remains.
What You Should Do: If a new certification is started on that same date, Delete the previous Nutrition Assessment contact.
Resolution: This is currently being researched by CSC.
Nutrition Education: Add Materials Given Button Stays Enabled after Contact Added – Overwrites Current Contact if New Contact Added on Same Date (SVN-98)
Description: The Add Materials Given button stays enabled after a contact is added. If the user adds another Materials Given contact on the same date, the system over-writes the previous contact with the most recent one.
What You Should Do: Once a Materials Given contact is created, use the Edit Contact, Material, or Referral button if more contacts need to be added for that date.
Resolution: This will be corrected in Release 2.18.06.
Release 2.16.06
* * * * *
Holidays Defined for 2013 Are Displaying on the 2012 Calendar Grids in Schedule Appointments for Household (TOS-128)
Description: Holidays defined for 2013 are displaying in red in the calendar grids for 2012 in the Schedule Appointments for Household screen.
Example: If you've already defined November 28-29, 2013 as holidays, the 28th and 29th in the November 2012 calendar are displaying in red along with the 22nd and 23rd.
What You Should Do: The work-around is to undefine any holidays that are more than one year in the future.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Dates with Defined Business Hours and No Scheduled Resources Are Displaying Yellow in the Schedule Appointments for Household and View Appointments Screens (TOS-127)
Description: Dates that don’t have any resource columns scheduled that have been defined as business days with business hours are displaying as yellow instead of dark gray in the Schedule Appointments for Household and View Appointments screen.
Some agencies choose to define these dates so that they are available if additional resource columns need to be added in the future. They display as white in Build Master Calendar and used to display as dark gray in the clinic application.
What You Should Do: In order for these dates to display as gray instead of yellow, you will need to use the Clear Business Days function in Build Master Calendar to remove the define business days/hours. Once the Business Days are cleared, they will no longer display as yellow.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Participant Search/List: The System Does Not Maintain Focus on the Highlighted Participant in the Participant List (TOS-80)
Description: When a participant is highlighted on the Participant List and their Participant Folder is opened, upon returning to the Participant Search screen, the focus is at the top of the list instead of on the highlighted participant.
What the User Should Do: This is a display issue and is only an issue when numerous records are displayed in the list, which may occur when searching by name. However, if the user scrolls down, the previously highlighted record will still be highlighted. This is not an issue when searching by ID number.
Resolution: This issue is currently being researched by CSC.
Benefits - Void: Able to Void Benefits for Household Members Who Belong to Different Agency (TOS-84)
Description: The revised Void Benefits function allows users to void benefits for members of a household who belong to a different Local Agency. They are only supposed to be able to void benefits for household members who belong to a different Clinic.
What the User Should Do: This is a display issue and does not affect the user's ability to void benefits.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Categorical Ineligibility Date: Missing for Some Participant Records (TOS-62)
Description: Some participants in a valid certification who have not been terminated have NULL values in the Categorical Ineligibility Date field instead of dates. If the user tries to print an Official Notification from the Participant Activities menu, they receive an error that reads: "There is insufficient information to generate the Official Notification for the participant."
What the User Should Do: This is a database issue; MN does not use the Official Notification document.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Certification Guided Script (CGS): CPA-determined Follow-up Fields Not Auto-Populating (TOS-70)
Description: The Education Follow-up Frequency and Education Method fields in the CPA-determined Follow-up window are not auto-populating with the clinic defaults in the CGS.
What the User Should Do: These are not required fields. The user can choose to complete them as appropriate.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Food Package: Object Reference Error if Click OK when Adding Food Item without Selecting a Food Category (TOF-136)
Description: If the user clicks the OK button on the Add Food Item window without selecting a Food Category from the drop-down, an "Object Reference not set to an instance of an object" error displays.
What the User Should Do: The user should click the Cancel button to exit the screen without making any selections/changes.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Missed Appointment Follow-up: Follow-up Date Not Applying to Household (TOS-72)
Description: When multiple household members are selected in the Missed Appointment Follow-up (Participant Search…Activities menu) and the Follow-up screen is completed, the Follow-up Date column does not display the date for all household members.
What the User Should Do: The Follow-up will need to be completed individually for each participant.
Resolution: This issue is tentatively scheduled for Release 2.18.06.
Participant Search: Show/Hide Details in Appointments for Today List Causes Values in Appt Columns to Disappear/Error to Occur when Marking Appt as Kept (TOS-52)
Description: When the user toggles the appointment as kept then selects the Show Details button on the Appointments for Today screen and clicks on the screen, the Appointment Time and Appointment Type column clear for the selected participant. The Kept checkmark will also sometimes clear.
If the user selects the Hide Details button and attempts to toggle the appointment as kept, an "unexpected error" occurs.
Once the error displays, it will continue to display until the Participant Search screen is cleared and the Appointments for Today screen is re-opened.
What the User Should Do: These issues do not occur if the user does not use the Show Details function in this screen. If the issues do occur, click the Clear button, re-select the Appointments for Today radio button and click the Search button (or hit the Enter key on the keyboard) to refresh the screen. The checkmark will be maintained if it wasn't cleared as part of the issue. NOTE: The Kept checkmark will also automatically be inserted if benefits are printed for the participant.
Resolution: This is currently being researched by CSC.
VENA: Pseudo-Cert Created if VENA Contact Added in Participant Folder and No Risk Factors Are Assigned (TOS-69)
Description: If a participant is in a current cert and the user creates a VENA contact from within the Participant Folder, a pseudo-cert is being created even though no Risk Factors have changed.
What the User Should Do: This is a display issue.
Resolution: This issue is tentatively scheduled to be corrected in Release 2.19.05.
Release 2.15.06
* * * * *
Benefit Issuance: System is Not Recognizing Benefit Maximums for Milk Products (TOS-5)
Description: The system is still distributing 2 gallons of "regular" milk and 2 gallons of Lactose Free Milk on the same benefits.
What the User Should Do: This is continuing to function as it currently does in HuBERT.
Explanation: Each food item has a maximum quantity that can be issued on one benefit. For example, "Fat Free/Skim or 1% Milk" and "Fat Free or 1% Lactose Free Milk" both have a maximum of 2 gallons that can be distributed onto each benefit.
ENH-119 allows the State to set another maximum benefit limit by base Food Category. This means that Milk products can be limited to a maximum of 2 gallons per benefits, regardless of the different types of milk a participant may have in their food package.
However, the system is not recognizing this limit for the base Food Category limit for Milk. This means that a participant who has more than one milk product in their food package may receive up to 4 gallons of milk on one benefit (2 gallons of "regular" Milk and 2 gallons of Lactose Free Milk).
Resolution: This is currently being researched by CSC.
