Cross-Reference for HuBERT
|Use Ctrl + F to search page for keywords or phrases.|
|113, 121, cash-value benefits, categorically ineligible, child food package, high risk, infants turning one, recumbent, participant dies, relationship field, risk factor|
System Incorrectly Assigning Risk Factor 113 to Children 3-5 Years Old Measured Recumbent (TMP-169)
Description: The system is incorrectly auto-assigning Risk Factor 113, Obese (Children 2-5 Years of Age), to children who are 3-5 years old and are measured recumbent. These measurements are also not being plotted on the Y2-6 grids as they should be.
What You Should Do: This should affect a very limited number of children since most 3-5 year old children are measured standing. However, if risk factor 113 is incorrectly assigned, document that it should NOT have been assigned in a note.
Resolution: This issue has been added to the issue's queue.
Identified Issues - Posted 5/13/14
Increase in Cash Value Benefit for Children Effective Monday, May 5, 2014
Due to changes in the final Food Package Rule, the fruit and vegetable cash value benefits will increase from $6.00 to $8.00. This change will be implemented on the HuBERT back-end and will be available to users on Monday, May 5. Please be sure to Reset Local Reference Data to ensure this change is made.
The increased cash value benefit will be added to the children’s Default Food Package. In order for children to receive the increased amount, you will need to create a new food prescription (since prescriptions with Effective Dates in the past cannot be edited). Future food prescriptions can be edited (delete current fruit/vegetable food item and add new fruit/vegetable food item).
April 2014 HuBERT Hints #2
System is Incorrectly Assigning Risk Factor 142 to Children between 1-2 Years Old with Weeks Gestation of 37 Weeks (TMP-149)
Description: Risk Factor 142 should be assigned to children 1-2 years of age if their Gestation value in Health Information is 37 Weeks and 0 days. However, the system is incorrectly assigning Risk Factor 142 to children 1-2 years old and 37 weeks gestation regardless of the number of days. This occurs both in the Certification Guided Scripts and when pseudo-certs are generated in the Participant Folder.
What You Should Do: Remove the link between the child's and mom's records since the child is over one year old and the link is unnecessary.
To do this, simply remove the checkmark in the On WIC checkbox in the child's Health Information screen and save the change.
Once the link is removed, the system will remove the incorrectly assigned Risk Factor.
Resolution: This issue has also been added to the issue's queue.
Identified Issues - Posted 3/10/14
For Children over Two Years Old, the System is Not Assigning Risk Factor 121 and if 121 Is Already Assigned It Is Removing it when a Pseudo-Cert is Created (TMP-132)
Description: For children over two years old, whose height is less than the 10th percentile, the system is not auto-assigning Risk Factor 121. If a pseudo-cert is created and Risk Factor 121 has been previously assigned, the system is removing the risk factor even though it may still be applicable.
What You Should Do: When this happens, document that Risk Factor 121 should be assigned in a note.Resolution: This issue has been added to the issue's queue.
Identified Issues - Posted 2/24/14
Using the Authorized Representative's Relationship Field
If users choose to use the Relationship field, they should select the option that best describes the representative's relationship to a child in the household (born or unborn).
For instance, if in mom's participant folder, "Mother" should be selected for the Authorized Representative's Relationship field since she is the mother of the children in the household. Other examples:
- If mom's sister is an Alternate Representative, select "Aunt" since that is her relationship to the child(ren) in the household.
- If mom is pregnant and her mother is an Alternative Representative, select "Grandmother" since she will be the grandmother of the unborn child.
From the 2.17.07 Release Document
Managing a Participant's Record if the Participant Dies
Description: When a participant dies it can be uncomfortable or difficult if staff don't realize it and ask the family about the member.
Explanation: Participants who haven't had any activity on their participant record remain in the Local Agency database for 180 days before being purged to Agency 88. When the household is searched for the participant will continue to display for 6 months. Alerts are helpful but only if the staff asks questions after opening the Participant Folder.
What You Should Do: Change the participant's Household ID so that the participant record no longer displays with the rest of the household. Select Other (explain in notes) from the Reason for ID Change drop-down and document why the participant's household ID was changed.
September 2012 HuBERT Hints #2
Issuing the Last Set of Benefits to Categorically Ineligible Participants
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).
July 2012 HuBERT Hints #2
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