HuBERT Logo - Mama Loon with Baby Loon on Back

Benefit Issuance

HuBERT Cross-Reference

MN WIC Program

Binoculars Use Ctrl + F to search page for keywords or phrases.

6 month, 19 kcal, add/replace, beans, benefit, benefit pickup report, breastfeeding, cash-value, categorically ineligible, cereal, certification, child food package, count, cycle, definitions, early issuance, fruit/vegetable, food package, formula, fully BF, infants turning one, last set, late issuance, LDTU, locked household, March, maximum, message, non-breastfeeding, partial packages, previous month, print, printed first date to use, prorated, questions to ask, redeemed, supplemental foods, SQL, sync, terminated, void reason

Early Issuance and Issuing 6-Month Set of Benefits to Fully BF Infants

When issuing benefits to a fully breastfed infant, in some instances, the system will not suggest the 6-month benefits. This doesn’t occur consistently since it is based on meeting specific criteria relative to when the infant was first certified and the dates of their cycle. However, the following is a general explanation why this may occur.

The benefit issuance cycle hasn’t yet been set when issuing to a fully bf infant who is currently less than 6 months old. This means they don’t have a Last Date to Use (LDTU) associated with their record. In order to set their cycle, the system must sync them to another household member, usually the mom.

If mom were to come in early for her next set of tri-monthly benefits the system will attempt to sync the baby to mom’s cycle. Since baby doesn’t have a LDTU, the system will set her cycle as if issuing late benefits for baby. If baby is turning 6 months old at the end of that tri-monthly period, you might expect her to receive benefits for the last set that mom receives. In most cases, this may be true but in some cases, baby won’t be issued any benefits.

Here is a specific example to help with the general explanation of when a baby won’t be suggested benefits:

Baby was born on 12/11/2014. Her 6-month birthday is 6/11/215.

Mom has received benefits up through April, 2015 and has come in to clinic to receive May, June and July benefits early on April 30.

Mom’s cycle is the 6th to the 5th. Mom is issued benefits for:

  • 5/6-6/5 (May)
  • 6/6-7/5 (June)
  • 7/6-8/5 (July)

Baby is eligible to receive benefits for infant foods in July (not June because her birthday, June 11, is not before the PFDTU of the cycle).

When issuing the system sees that the baby doesn’t have a LDTU and since this is early issuance for mom, it attempts to provide late issuance for the baby. It syncs baby up with a late partial package and her issuance cycles are:

  • 4/30-5/5 (April)
  • 5/6-6/5 (May)
  • 6/6-7/5 (June) - Baby doesn’t receive any benefits at this pick-up

In order for baby to receive July benefits, mom would have to pick up benefits on or after the First Date to Use of her cycle; in this case, on or after May 6th. If she were to pick them up on or after May 6th, the system cannot issue late benefits to baby and when syncing the cycle will start her cycle on 5/6 so that it can provide the July food package.

  • 5/6-6/5 (May)
  • 6/6-7/5 (June)
  • 7/6-8/5 (July) - Baby receives July benefits

NOTE! The next time mom comes in, as long as she picks up even one day before her typical cycle, the system will suggest July benefits for baby. If she doesn’t come in until her actual August cycle starts or later, then baby will not receive July benefits.

May 2015 HuBERT Hints #2

Back to Top

Children Are Counted as Infants if Sets of Benefits with PFDTU after First Birthday Issued Before First Birthday (TMP-220)

Description: When benefits are issued to a participant the system records their WIC Type at the time of issuance based on their current WIC Type (or the WIC Type stored in the MEMBER table). The WIC Type stored at the time of issuance is used to count the type of participant in the participation counts.

If an infant is recertified prior to their first birthday and issued tri-monthly benefits, the system will count the participant as an infant for all three months even if the second and third sets of benefits are for child food packages and the PFDTU of the benefits is after the first birthday.

This can result in over-counting infants in the participation counts and could have a larger impact after Release 2.22 in which infants can be certified within 30 days of the first birthday.

Please note that infants should only be recertified early in instances where it is absolutely necessary to sync the infant's appointment with other household members. (Reference: 2.22 Release Document, page 10.)

What You Should Do: In general, infants should be recertified after their first birthday. If trying to sync the infant to other household members, ascertain if it is possible to sync all of the appointments after the infant's first birth date (by extending other certification periods by 30 or less days). If the infant must be recertified early, benefits could be issued for only one month and subsequent benefits issued after the infant's first birthday. If doing this were to cause hardship then issue tri-monthly; the system will count the participant incorrectly as an infant for the subsequent sets of benefits.

Resolution: This has been added to the issue queue.

Posted to Issues Page on 5/20/15 and May 2015 HuBERT Hints #2

Back to Top

Participants Certified on 29th – 31st of Month - Benefit Issuance Cycles Start on First of Next Month

In Release 2.20, February benefit issuance issues were corrected by ensuring that issuance cycles do not have a LDTU after the 27th of any month. For participants certified on the 29th, 30th, or 31st who don’t have an established cycle, or a household member who has an established cycle to cycle-adjust to, the system will issues a partial set starting on the current date and ending on the last date of the month. This may result in a benefit for one day. Their cycle will then start on the first of the next month.

For more detailed information about this functionality, and how to change the cycle to a date later in the month if necessary, please refer to pages 6 and 7 of the 2.20 Release Document.

April 2015 HuBERT Hints #1

Back to Top

Changes to Benefit Maximums and Descriptions for 19 Kcal Powder Formula

The following formulas will be affected by these changes:

  • Similac Sensitive (12.6 OR 12.0 oz pwd)
  • Similac Spit Up (12.3 OR 12.0 oz pwd)
  • Similac Total Comfort (12.6 or 12.0 oz pwd)

Change to Benefit Maximum
In July 2014, the maximum number of cans that would print on a benefit for the 19 Kcal powder formulas was changed to 5 cans due to their limited availability in stores. Since these formulas should now be readily available, the maximum number of cans that will print on a benefit has been changed back to the maximum allowed based on the participant’s age category and breastfeeding amounts.

Change to Descriptions
During the transition to the 19 Kcal formulas, the formula descriptions included the larger can size. Since the 12.0 ounce cans of powdered formula are now readily available, the larger size will be removed from the formula description so that after February 21, 2015, they will print as:

  • can(s) 12.0 oz powder Similac Sensitive
  • can(s) 12.0 oz powder Similac Spit Up
  • can(s) 12.0 oz powder Similac Total Comfort

February 2015 HuBERT Hints #1

Back to Top

Small Change to Issue Benefits Screen

On 12/1/14, a small change will be made to the Issue Benefits screen so that categorically ineligible participants will no longer be processed for benefit issuance. This change will have the largest impact on the processing speed for households with a large number of categorically ineligible members (children who are over 5 years old and women who are no longer eligible). Households with no categorically ineligible people will see no difference in processing speed.

For example, the household shown below has 4 categorically ineligible household members. When tested prior to the processing change, the Issue Benefits screen took 25.3 seconds to open and displayed all members of the household regardless of eligibility.

Isse Benefits with categorical ineligible participants displayed

Once the processing change had been made, the Issue Benefits screen took 15.7 seconds to open and displayed only those members potentially eligible for benefits.

November 2014 HuBERT Hints #2

Back to Top

SQL-Adjusted Last Date to use (LDTU) Will Revert Back to Original LDTU if Issue Benefits Screen is Opened and Closed without Issuing Benefits

For more detailed information, including print screens, please see the November 2011 HuBERT Hints #1.

As part of Release 2.20 installed on Production on November 1, 2014, a SQL query was run on the back-end that adjusted any established issuance cycles with a LDTU on the last days of the month back to the 27th to help resolve the issues seen with February issuance.

If a participant’s LDTU was adjusted by the SQL query, and the Issue Benefits screen is opened while in their Participant Folder, and then subsequently closed without issuing benefits, the adjusted LDTU will revert back to its original date for that household member.

This is because the SQL only resets the LDTU in one place. When the Issue Benefits screen is opened, closed and again re-opened, the system re-evaluates the LDTU and resets it back to the LDTU of the last set of benefits issued. Since this only occurs for the member from whose Participant Folder Issue Benefits is opened from, the other members retain their adjusted LDTU.

However, if there are other members in the household, the cycle automatically syncs to the other members and the new cycle of the 28th to the 27th will be maintained for future issuances.

NOTE! You Must Cycle-Adjust to Correct the Benefit Cycle if Only One Household Member

If there aren’t any other members to sync to and the Issue Benefits screen is opened and closed without issuing benefits, when re-opened, incorrect benefits will be suggested for the participant. In this instance, you will need to select the cycle-adjust radio button and select the 27th from the drop-down calendar.

This will correct the participant's cycle with the new cycle of the 28th to the 27th.

November 2014 HuBERT Hints #1

Back to Top

Some-Breastfeeding Women More than 6 Months Postpartum Incorrectly Suggested Benefits when Second Unlinked Infant Record in Infants Born from This Pregnancy (TWY-18)

Description: Although Some-Breastfeeding women more than 6 months postpartum are not eligible to receive food benefits, HuBERT is incorrectly suggesting benefits to these women when a second unlinked infant record exists in the Infants Born from This Pregnancy window in Health Information.

Infants Born from This Pregnancy with two records

What You Should Do: If a second record was incorrectly added to the Infants Born from This Pregnancy window instead of editing the initial record, you can delete the incorrectly added record simply by highlighting it in the window and clicking the Delete button. This should resolve the incorrectly suggested issuance.

If, however, the second record is appropriate because a second infant was born but is not on WIC due to neonatal death or other circumstances, you should simply remove the checkmark from in front of the participant's name in the Issue Benefits screen so that no benefits are issued.

Resolution: This issue has been added to the issue's queue.

Identified Issues - Posted 9/4/14

Back to Top

Move Cereal so that It Always Prints on Second Benefit

Currently, participants receiving two dozen eggs often receive a benefit with just one dozen eggs on it. By changing the cereal from always printing on the first benefit to always printing on the second benefit, the eggs will be distributed onto the first two benefits for the majority of participants, which should greatly decrease the number of benefits printed with only one dozen eggs on them.

Update Document - Food, Formula, & Materials Given Changes - 07/01/14

Back to Top

Alternating Beans - 8 Cans of Beans Will Print on One Benefit

In Release 2.18.06, the ability to alternate canned beans with other bean options was corrected.

However, if the participant receives two dry beans, peas and lentil options and one of those options is canned beans while the other option is alternating canned beans, the system will print all 8 cans of beans on one benefit.

Although there is a maximum of 4 cans per benefit, this maximum is set by individual food item. When alternating, it is considered a different food item so the maximum does not apply for both the single and alternating food items.

From the 2.18.06 Release Document

Back to Top

Explaining Prorated Food Packages to Participants

When issuing benefits "late" to women and children, HuBERT prorates the food package, indicating a "three-quarters", "half" or "one-quarter" food package. However, only the amount of milk is reduced; the other food items are not. CPAs should specifically mention this to participants, informing them of the amount of milk they will receive, and that the amount of other food items is not less.

We suggest not using the terms "half" or "three-quarters" food package with participants since such terms are inaccurate and likely to be confusing. If you have questions, please contact your Nutrition Consultant.

March 2013 HuBERT Hints #3

Back to Top

Purpose of "Valid benefits are still available…" Message that Displays before Certification

This pertains to the message "Valid benefits are still available for this participant through Issue Benefits. Would you like to abort the certification process?" that sometimes displays before starting a certification.

When a certification is first started, HuBERT assesses whether there are benefits that can still be auto-suggested in the Issue Benefits screen for the participant's current certification period. If there are, this message will display.

The message has two options:

  • Yes – abort the cert process (so that you can go to the Issue Benefits screen and issue benefits before starting the cert)
  • No – continue with the certification

This allows you to decide whether benefits should be issued before certifying. There are two different scenarios that have caused some confusion:

NOTE: For the following we will use 6-month certs for ease of examples.

Scenario #1: Participant Certified in Month Cert Ends and Hasn’t Received Benefits for Previous Month
  • CHILD's current certification began on: 8/26/12
  • Received benefits for August, Sept, Oct, Nov and Dec (for some reason, haven’t received January)
  • Cert End Date = 2/28/13
  • Cycle = 26th to 25th
  • Last Printed First Date to Use (PFDTU) = 12/26/12
  • Last Check Last Date to Use (LDTU) = 1/25/13
  • Recertifying participant on 2/7/13

Since the January benefits are the 6th set for the participant's current cert period and the participant is eligible to receive late issuance for January, the system is still able to auto-suggest this set in Issue Benefits and the message will display. If you click Yes on the message and go to Issue Benefits, the following set will be suggested:

  • <1/26/2013>2/7/2013-2/25/2013 Three Fourth

The PFDTU is in January and these benefits are counted for that month.

If you click No on the message, the system begins the cert process. When you open the Issue Benefits screen once the cert is completed, the system now suggests a syncing partial package for February and a full set for February, March and April; it will no longer auto-suggest late issuance for January once the cert is completed.

  • 2/7/2013-2/25/2013 Three Fourth
  • 2/26/2013-3/27/2013 Full
  • 3/26/2013-4/25/2013 Full
  • 4/26/2013-5/25/2013 Full

NOTE: Remember, this message displays regardless of whether the issuance would be considered a "late issuance"; it simply displays if benefits can still be auto-suggested by the system in the Issue Benefits screen.

Scenario #2: Participant Certified Month AFTER Cert Ends and Hasn't Received Benefits for Previous Month

  • CHILD's current certification began on: 8/26/12
  • Received benefits for August, Sept, Oct, Nov, Dec and Jan
  • Cert End Date = 2/28/13
  • Missed original appointment scheduled in February
  • Cycle = 26th to 25th
  • Last Printed First Date to Use (PFDTU) = 1/26/13
  • Last Check Last Date to Use (LDTU) = 2/25/13
  • Recertifying participant on 3/7/13

In this case, the participant has received all sets of benefits for their certification period. But, since they missed an appointment last month (February) they didn't receive benefits for that month (February) and they are still eligible to receive late issuance for the month their cert ended (February). (Reference - Participation: Issuing Late Benefits before Recertifying Children, Wednesday Update Memo from 2/6/13).

For children who are not turning 5 years old, the system will NOT auto-suggest the set with a PFDTU in the month their cert ends (for all other participants, who technically become categorically ineligible, the system will suggest this last set).

In this case, the system does not have any other benefits it can auto-suggest in the Issue Benefits screen and the message will NOT display. You need to remember to use Add Set to issue the February benefits.

NOTE: In Release 2.18, a prompt will display that allows you to choose whether to issue the late benefits once the cert has been completed.

February 2013 HuBERT Hints #2

Back to Top

Issuing Last Set if No Longer Breastfeeding and More than 6 Months Postpartum

Question from 2.17.07 WebEx Review: If mom is more than 6 months postpartum and is no longer breastfeeding, should she receive a last set of benefits before being terminated for Categorical Ineligibility? If so, do those benefits need to be issued before changes are made to the infant's Health Information screen?

Answer: According to MOM 5.2-3, under Certification Periods: For a BF Woman, "If her infant is six (6) months or older, she is given 15 days notification of pending ineligibility. If she is due to receive vouchers within the 15 days, CPAs may issue one-month's vouchers."

As explained on pages 33-34 of the 2.17.07 Release Document, after Release 2.17.07 is implemented, the system will auto-terminate mom if her infant is more than 6 months old and she is no longer breastfeeding (the checkmark is removed from the Breastfeeding Now checkbox in the infant's Health Information screen).

The following steps should be taken in order to insure mom receives her last set of benefits and policy guidelines are met:

  • Issue Benefits to Mom:

1. Open mom's Participant Folder

2. Issue one last set of benefits to mom for her current food package (remove the checkmarks from all but the first set auto-suggested and, to keep it simple, from any other household members being suggested at this time)

3. Once the set of benefits is issued, close mom's Participant Folder (it must be closed for the system to auto-terminate)

  • Change Infant's Breastfeeding Status, Auto-Terminate Mom's Cert, and Issue Benefits to Infant:

4. Open the infant's Participant Folder

5. Click on the Health Information tab

6. Click on the Breastfeeding Now checkbox to remove the checkmark

7. Click Yes on the message indicating mom's cert will be terminated

8. Click on another tab and save the changes to Health Information

9. The Select Formula screen opens; complete it

10. Issue benefits to the infant and other members of the household

  • Issue Ineligibility Letter to Mom:

11. Open mom's Participant Folder again

12. Click on Participant Activities on the menu bar

13. Select Generate Official Notification

This is specific to a breastfeeding woman who has an infant more than 6 months old and has completely stopped breastfeeding. As long as she is breastfeeding at least one time per day, she should continue as a Some-BF woman.

February 2013 HuBERT Hints #1

Back to Top

Able to Issue Formula Benefits to Infant Who Already Received Benefits for 6 Month Fully BF Food Package

This is a reminder that you are now able to issue benefits for formula to an infant who used to be fully-breastfeeding and had already received benefits with the 6-month supplemental foods on them.

Example: On 1/5/13, Fully-BF infant received benefits for March 2013 with supplemental foods. On 2/6/13, mom returns requesting supplemental formula (baby is now Mostly-BF); you void the March benefits with Fully-BF supplemental foods on them and update the food package as appropriate.

  • When benefits are voided, the system resets the last set's LDTU to the participant's last non-voided LDTU (LastCheckLDTU in the MEMBER table is set back to last non-voided issued set, if only voided benefits exist, the LastCheckLDTU is set to NULL)
  • System suggests benefits for February, March and April in the Issue Benefits screen

NOTE! Since benefits for February were never issued or voided, they will not display in the Replace screen. Benefits have to be issued via Issue Benefits.

February 2013 HuBERT Hints #1

Back to Top

Using Issue Benefits Versus Add/Replace to Re-Issue Voided Benefits

When ALL future sets of benefits have been VOIDED, the system will automatically set the LastCheckLDTU in the MEMBER table back to the LDTU of the last issued set. This means you are now able to re-issue these benefits using Issue Benefits.

However, if you void a set of benefits and the participant still has a future set of benefits that have been issued, you must use the Replace function to re-issue the voided set of benefits.

Example #1: Using Issue Benefits to Re-Issue

  • Participant's cycle is the 5th to 4th – last set issued 12/5/12-1/4/13
  • Benefits issued for 1/5/13-2/4/13 (Jan), 2/5/13-3/6/13 (Feb) and 3/5/13-4/4/13 (March)
  • Benefits for all three months are voided
  • System sets LastCheckLDTU in MEMBER table back to LDTU of last issued set – 1/4/133
  • System auto-suggests 1/5/13-2/4/13 (Jan), 2/5/13-3/6/13 (Feb) and 3/5/13-4/4/13 (March) in the Issue Benefits screen

Example #2: Using Add/Replace Function to Re-Issue

  • Participant's cycle is the 5th to 4th – last set issued 12/5/12-1/4/13
  • Benefits issued for 1/5/13-2/4/13 (Jan), 2/5/13-3/6/13 (Feb) and 3/5/13-4/4/13 (March)
  • Benefits for February are voided
  • System doesn't change the LastCheckLDTU in MEMBER table; it maintains the LDTU of the last issued set, which in this example if for March (LDTU = 4/4/13)
  • Use Add/Replace to re-issue benefits for February

February 2013 HuBERT Hints #1

Back to Top

System Won't Allow Issuance if Participant Is No Longer Categorically Eligible

Add Set functions so that participants can be issued additional benefits within 30 days of their Cert End Date as long as they are still categorically eligible. This allows states that certify to the exact date (instead of the last date of the month) to be able to issue.

NOTE: Users will be unable to issue late benefits to a participant that has been terminated by the system for categorical ineligibility.

For example, if a participant comes in on 5/6/13 to receive April benefits and their:

  • Last Check LDTU = 4/22/13
  • Categorical Ineligibility Date = 4/30/13
  • Termination Date = 4/30/13

The user will be unable to issue April benefits because the participant has been terminated by the system and is no longer categorically eligible to receive benefits.

Also, if the Printed First Date to Use (PFDTU) is after the Cert End Date or the Categorical Ineligibility Date, Add Set will no longer allow benefits to be issued for that month.

From the 2.17.07 Release Document

Back to Top

Unable to Issue Last Set to Participants Becoming Categorically Ineligible in 4 Months

Although participants should only receive 3 sets of benefits at a time, we understand that some agencies may have issued the last set via Add Set when a single child without any other household members was turning 5 years old so that the participant would not have to return for one last set of benefits.

In Release 2.15.06 changes were made to insure that a last set of benefits is auto-suggested in the Benefit Issuance screen for participants becoming categorically ineligible. One of the results of this is that participants turning 5 that are issued 3 sets of benefits and are still eligible for one more set before becoming categorically ineligible will not be able to receive another set via Add Set at the time that the 3 sets are issued. The system now determines that another set can still be issued via Benefit Issuance and Add Set will display a message indicating this. The participant will have to return for the last set of benefits (or they can be mailed as policy allows, ref: MOM, Section 8.4).

NOTE: See above - System Won't Allow Issuance if Participant Is No Longer Categorically Eligible.

July 2012 HuBERT Hints #2

Back to Top

Selecting the Correct Void Reason: "Printed in Error" versus "Printer Error"

It is important that the correct Reason for Voiding is selected from the drop-down list when benefits are voided. After running a query to assess why benefits are being voided, we found a high number of benefits that were voided due to "Printer Error" and yet, have had relatively few printer problems called into the Help Desk.

Printer Error should be selected when you have to void benefits due to the printer causing the benefit to be unusable, such as when the printing is out of alignment on the benefit, or it is sent to the printer and doesn't print.

Printed in Error should be selected when you've printed benefits and shouldn't have, such as if you were to print benefits for 3 months when the participant needs to return for a High Risk visit or MidCert appointment the next month.

Remember, if benefits are voided because the food package is incorrect, you should choose Food Prescription Change.

June 2012 HuBERT Hints #1

Back to Top

Benefit Issuance Definitions

Issued Date

  • The date a benefit is physically sent to the printer
  • This date is not on the benefit

Printed First Date to Use (PFDTU)

  • The date printed on the benefit that indicates the first date it can be redeemed at a store
  • The month and year of the PFDTU are used for participation count

Last Date to Use (LDTU): The date printed on the benefit that indicates the last date it can be redeemed at a store

First Date to Use (FDTU)

  • The first date the participant is able to use the benefit
  • If benefits are issued early/on time: Equal to the printed first date to use (PFDTU)
  • If issued late: Equal to the date the participant receives the benefit
  • This date is not on the benefit

Syncing Package: A set of benefits issued at a cert appointment with a printed first date to use on the certification date and a last date to use the same as the other family members

Benefit Issuance Definitions - May 2012

Back to Top

The Top 5 Questions to Ask Yourself Before Clicking the Issue Benefits Icon

Description/Explanation: During a Nutrition Education contact, it is easy to overlook information that must be modified or entered into HuBERT in order for the system to be able to suggest benefits in the Issue Benefits screen, especially when serving multi-member households. Although the system will remind you with alerts prior to opening the Issue Benefits screen, it can affect your ability to serve the participant efficiently when you have to wait for the screen to open so that you can close it again and complete the necessary activities.

What You Should Do: Best practice is to review the participants' records prior to interacting with them. This will allow you to use your time more constructively and to use the system more efficiently. When reviewing the records, ask yourself:

  • Is mom or baby breastfeeding? You will need to verify the Breastfeeding Amount and select the Date Breastfeeding Verified in the infant's Health Information; adjust the Food Packages as appropriate.
  • Is anyone receiving a special formula? You will need to verify when the prescription expires in the Food Prescription tab and select the Date Food Package III Verified in Health Information.
  • Is anyone turning 1 year old? You will need to assess whether an infant or child food package should be provided and delete the Child food package in the Food Prescription tab if appropriate.
  • Is anyone turning 3 years old? You will need to create a food prescription with an Effective Date on the third birthday.

March 2012 HuBERT Hints #2

Back to Top

Infants Turning One in Next Benefit Issuance - Issuing an Infant vs. Child Food Package

Description: A child's food package will automatically be suggested by the system for the last set of benefits issued to an infant if the following two criteria are met:

  • A child's food package exists in the Food Prescription screen with an Effective Date of the infant's first birthday (or between the Printed First Date to Use (PFDTU) and the Last Date to Use)
  • The infant's one-year birthday falls between the PFDTU and the LDTU of a set of benefits being issued

Explanation: The system will automatically create a child's food package during the certification process when an infant has a Risk Factor assigned that is applicable to both infants and children. It is up to you, the CPA, to determine whether the child's food package is appropriate to provide at this time. Some examples of when it might not be appropriate include, if the infant:

  • Had a low hemoglobin at the Midcert
  • Doesn't consume protein or high-iron foods well
  • Has special needs
  • Just turned 11 months old

What You Should Do: The process for changing a suggested child's food package to an infant's food package, or vice-versa, is relatively simple:

If a CHILD Food Package is suggested and you want to provide an INFANT food package:

  • Delete the Child Food Package in the Food Prescription tab
  • Issue benefits

If an INFANT Food Package is suggested and you want to provide a CHILD food package:

  • Verify the participant has a Risk Factor appropriate for a Child (if not, assign Risk Factor 428)
  • Create a Food Package with an Effective Date of the infant's first birthday
  • Issue benefits

February 2012 HuBERT Hints #3

Back to Top

Can we replace benefits that have already been redeemed?

Yes. The Add/Replace Set functionality allows you to replace benefits even if they have already been redeemed. This allows agencies to provide benefits for different formula if it has been purchased for an infant but needs to be changed to another formula. Benefits do not have to be voided to replace them. A new food package should be created before the Add/Replace screen is opened and a descriptive note written in the Note field in the Replace section of the screen. The only caveat is benefits cannot be replaced once it is past the Last Date to Use.

January 2012 HuBERT Hints #2

Back to Top

Always Close Issue Benefits Window When Returning to Participant Folder to Avoid Household Lock

Description: In Release 2.12.05, a Lock Household function was added to ensure that the Issue Benefits screen could only be opened for one member of a household at a time.

Explanation: When you click on the Issue Benefits icon, the system will verify whether another Issue Benefits screen has already been opened for the household. If not, HuBERT allows the Issue Benefits screen to be opened but places a temporary lock on the household so that the screen cannot be opened again for the same household until the screen is closed.

If the Issue Benefits screen is already opened and you try to open it again for the same household, a warning message displays indicating the household is temporarily . Both the initial user who opened the screen and the State WIC ID of the participant folder from which the Issue Benefits screen was opened is displayed in the message.

Message:  This household is temporarily loked because user (MALLBS1) is in the process of issuing benefits to member 42563

What You Should Do: Once the Issue Benefits screen is closed either by issuing benefits or exiting the screen, the system will automatically unlock the household. To avoid receiving the message, always exit the Issue Benefits screen if you have to return to a household member's Participant Folder before issuing the benefits (for example, to update the food prescription).

If you receive the message, click the Cancel button. Then, determine which household member already has the Issue Benefits screen open and re-maximize/use that screen. If another user has the Issue Benefits screen open, let them know that they must close it in order for you to be able to issue benefits.

If the household is even once the Issue Benefits screen is closed (due to a workstation locking up or loss of connectivity), you can manually unlock it by going to: File…System Tools…Unlock Household.

For more information, please see pages 15-16 in the Release 2.12.05 Document.

NOTE: All households are automatically unlocked during the End-of-Day processes.

August 2011 HuBERT Hints #2

Back to Top

Always Issue Both Partial and Full Packages if Printed First Date to Use (PFDTU) Is in Same Month

Description: If two sets of benefits are suggested in the Issue Benefits screen for the same month (the PFDTU is in the same month), then both sets should be printed.

Explanation: Partial packages are suggested to close the gap between two different cycles within a household. When we set a participant's issuance frequency to Monthly, Bi-Monthly or Tri-Monthly, we are establishing the number of unique participation months for which the benefits should be suggested. Based on this definition, the system will suggest two sets of benefits for one month, a partial and a full package, and treat them as one month's issuance as long as the PFDTU is in the same month.

Example: The system suggests:

Benefit suggested by system

What You Should Do: If two sets of benefits are suggested with the PFDTU in the same month, you should issue both sets at the same time.

August 2011 HuBERT Hints #1

Back to Top

Fully-Breastfed Infants Must be 6 Months Old On or Before the Printed First Date to Use to Receive Supplemental Foods

Description: The system will not suggest benefits for fully-breastfeeding infants until the Printed First Date to Use (PFDTU) is greater than the infant's 6-month birthday.

Example #1

  • Fully BF Infant
  • DOB = 10/27/2010
  • Cycle = 23rd - 22nd
  • Issuance Date = 4/28/2011

System Suggests for Tri-Monthly Issuance:

  • Set 1: 5/23/2011-6/22/2011 (May)
  • Set 2: 6/23/2011-7/22/2011 (June)

Even though the infant may be older than 6 months on the date the benefits are issued, the PFDTU of the April set is 4/23/2011. Since 4/23 is before 4/27, which is her 6-month birthday, April benefits will not be suggested for this fully-breastfed infant.

Example #2

  • Fully BF Infant
  • DOB = 10/20
  • Cycle = 23rd to 22nd
  • Issuance Date = 4/18/2011

System Suggests for Tri-Monthly Issuance:

  • Set 1: 4/23/2011-5/22/2011
  • Set 2: 5/23/2011-6/22/2011
  • Set 3: 6/23/2011-7/22/2011

Even though the infant isn't quite 6-months old when the benefits are printed on 4/18 she will be 6-months old by the time the benefits can be used on 4/23/2011. Since the PFDTU of the first set is on 4/23, which is after her 6-month birthday, April benefits will be suggested for this fully-breastfed infant.

April 2011 HuBERT Hints #2

Back to Top