Basic Health-Plus (BH-Plus) Case
DSHS Home Page

ACES

  Search   for:   
DSHS HomeACES ManualEAZ ManualSocial Services ManualWork First Manual

Basic Health-Plus (BH-Plus) Case


Revised October 28, 2007



Purpose:

Alerts

Alert 404 - Another CSO Updated Shared AU

Alert 405 - CSO Updated BH-Plus AU

Coordination of Case Action Between MEDS CSO and Non-MEDS CSO

Enhanced Security for Selected MEDS Users

Letters

Maintenance Activity

Processing a Shared Case

Recertification of BH-Plus Assistance Unit

Shared Cases

All Assistance Units Do Have Same Head of Household

All Assistance Units Do Not Have Same Head of Household
 


Alerts

When a user in another office has acted on an AU that is in a shared case, an alert is generated to inform the user in the other office that the case action has been processed.

Alerts generated in this situation are:

Alert 404 - Another CSO Updated Shared AU

Alert 404 - generated when action is taken on an AU which is linked to an active AU in another office.

  • This includes action taken by a non-MEDS office user if the related AU is "owned" by the MEDS office but is a non-BH-Plus AU.

  • This alert is also generated when a MEDS user with enhanced security updates a BH-Plus AU that is "owned" by another CSO.

  • The user should review the case action taken by the other office.

  • This is a user-dispositioned alert.

Alert 405 - CSO Updated BH-Plus AU

Alert 405 - generated when action is taken on an AU which is linked to an active BHP-Plus AU.

  • This alert is sent to the MEDS user assigned to the AU and displays regardless of which office "owns" the AU.
     


Coordination of Case Action Between MEDS CSO and Non-MEDS CSO

  • An AU in which a client is receiving BH-Plus medical can not be its own separate AU in ACES if there are other related AUs. The BH-Plus AU becomes an associated AU with the other AUs in which there are common members.

  • The MEDS office is responsible for maintaining the BH-Plus AUs regardless of the fact that a non-BH-Plus AU exists and regardless of whom "owns" the case.

  • The non-MEDS office is responsible for maintaining all non-BH-Plus AU.

  • MEDS users processing case actions on a BH-Plus AU when a shared case exists must be aware of how the case action being processed will affect eligibility on the non-BH-Plus AU.

  • The case action on the BH-Plus AU can not be completed until coordinated with the user in the other office.

  • If the case action being processed has no effect on the non-BH-Plus AU, the MEDS user will confirm the action on the (DONE). ACES will automatically send Alert 404 - Another CSO Updated Shared AU - to the appropriate CSO user.

  • If the case action being processed has an affect on the non-BH-Plus AU, the MEDS user will hold the case to the SPA and contact the non-MEDS office before finalizing the case action.

  • When the case action is processed, the non-MEDS CSO will receive Alert 404 - Another CSO Updated Shared AU.
     


Enhanced Security for Selected MEDS Users

  • To allow MEDS users to take action on a BH-Plus AU "owned" by a non-MEDS CSO, selected MEDS users have been assigned an enhanced security profile.

  • These MEDS users have an on-line update access to non-MEDS office cases.
     


Letters

  • ACES suppresses all letters that normally would be generated on a MEDS AU in a shared case situation.

  • The MEDS office generates special BH letters instead of ACES generated letters.

  • Review letters normally generated for non-MEDS AU are suppressed on BH-Plus AUs.
     


Maintenance Activity

When a MEDS user with enhanced security accesses an AU that has an associated non-MEDS AU, the MEDS user must determine if the case action being processed will affect the non-BH-Plus AU.

If the case action will affect the non-BH-Plus AU

  1. Do not confirm the case action.

  2. Place the AU on the SPA.

  3. Contact the non-MEDS office to receive approval for updating the non-BH-Plus AU.

  4. After the case is finalized Alert 404 - Another CSO Updated Shared AU - will be sent to the user of record.
     


Processing a Shared Case

  • ACES treats a shared case differently depending on whether the head of household is the same for all AUs.

  • When one or more AUs is shared between offices and the head of household is the same for all AUs, the non-MEDS office "owns" all of the AUs, including the BH-Plus AU.

However, only BH-Plus users have access to work on the BH-Plus AU.

  • Reports showing total AU count will have a separate total for the number of BH-Plus AUs "owned" by a non-MEDS office.
     


Recertification of BH-Plus Assistance Unit

  • ACES automatically extends the review end date for an additional certification period at the end of an existing certification period.  This continues until the AU is closed.

  • Review alerts normally generated for non-MEDS AU are suppressed on BH-Plus AUs.
     


Shared Cases

  • Shared cases must be processed differently based on whether or not all assistance units have the same head of household.

  • In both of the following situations each office can choose to retain ownership of their individual AU depending on the case circumstances.

When working on a shared case that includes a BH-Plus AU:

All Assistance Units Have Same Head of Household

  1. AU is active in a non-MEDS CSO and the MEDS office screens a new application.

    1. MEDS user gets Edit Message 229 - AU and FW Are Not in the Same CSO

    2. This means there is an AU open in another CSO so the user must press <F3> to cancel out of screening.

    3. MEDS user with enhanced security must screen Add a Program and then process case through Options

      • O - Interview,

      • P - Process Appl Months, and

      • Q - Finalize.

    4. In this situation, all AUs are "owned" by the non-MEDS CSO and only a MEDS user with enhanced security can update the case.

  2. AU is active in MEDS CSO - non-MEDs office receives new application.

    1. When the non-MEDS office user tries to screen the new application, Edit Message 229 - AU and FW Are Not in the Same CSO - displays.

    2. This means that there is an active or pending AU in the MEDS office.

    3. Press <F3> to cancel out of screening.

    4. The user in the non-MEDS office must contact the MEDS office and ask that the MEDS AU be transferred to the non-MEDS office.

    5. The non-MEDS office then can do Add a Program and then process case through Options

      • O - Interview,

      • P - Process Appl Months, and

      • Q - Finalize.

    6. The BH-Plus AU stays in the CSO of residence (non-MEDS office) and the case is "owned" by the non-MEDS CSO.

    7. Maintaining the BH-Plus AU is the responsibility of the MEDS office.

    8. Only a MEDS office user with enhanced security can work on the MEDS AU.

All Assistance Units Do Not Have Same Head of Household

  1. AU is active in a non-MEDS CSO - MEDS office receives application.

    The MEDS office user with enhanced security can screen Add a Program and then process, and finalize the application.

  2. AU is active in MEDS CSO - non-MEDS office receives application.

    The non-MEDS office user can screen Add a Program, process, and finalize the application.

Back to top

Modification Date: October 28, 2007
Have comments on the manual? Please e-mail us. You can also use this link to report broken links or content problems.