Processing an Inbound Message

Prerequisites

The following table lists the prerequisites which you should setup before processing the respective inbound message:

Inbound Message Refer to...
Health Care Inbound Message Prerequisites
Health Product and Plan Inbound Message Prerequisites

Procedure

To process an inbound message:

  1. Search for the inbound message in the Inbound Message screen.
  2. In the Search Results section, click the link in the Inbound Message Information column corresponding to the inbound message that you want to submit for validation and processing.
    The Inbound Message screen appears.
  3. Ensure that the Main tab is selected.
  4. Click the Submit for Processing button in the Inbound Message zone.

    The status of the inbound message is changed to Validation and the algorithms attached to the Validation status are invoked in the specified sequence. If the validation is successful, the status of the inbound message is changed to Processing and the algorithms attached to the Processing status are invoked in the specified sequence. The following table lists how the system behaves when the respective inbound message is processed:

    If the inbound message is a... Then...
    Health Care Inbound Message Creates or updates a person, account and fully-insured group or self-funded policy. It creates or updates a policy plan, membership, and pass-through billable charge for a fully-insured group policy. In addition, if requested, it terminates, reinstates, or renews a fully-insured group policy. Finally, the status of the inbound message is changed to Processed.

    The system uses the C1-PERSTYPE feature configuration to decide whether the person type specified in the health care inbound message represents Parent Customer or Bill Group. If the person type specified in the health care inbound message matches the person type specified in the Bill Group Person Type or Parent Person Type option type of the C1-PERSTYPE feature configuration, the system creates or updates the person, account, policy, policy plan, and address through a customer registration object. Note that the memberships, pass-through billable charges, and pricing rules are created directly and not via customer registration object. However, if the person type specified in the health care inbound message does not match the person type specified in the Bill Group Person Type or Parent Person Type option type, the system creates or updates the person and its other entities directly and not through a customer registration object. In this case, the system only refers the customer registration type for the business objects using which the person, account, policy plan, membership, and address should be created or updated in the system.

    If the derivation and pricing parameters are specified for a bill group, the system automatically creates one sort record for the bill group. Here, the sort ID is set to the bill group ID. The start and end dates of the sort record are set to the bill group and parent customer's relationship start and end dates. Once the sort record is created, the system creates the derivation and pricing parameters for the bill group and sort ID combination.

    Health Product and Plan Inbound Message

    Creates or updates a health product, health plan, and pricing rules for individual memberships. In addition, it also maintains a log of the entities that are either added or updated through the health product and plan inbound message. Note that the system allows to upload the health product, health plan, and pricing rules together in a single inbound message or by creating three separate inbound messages. Finally, the status of the inbound message is changed to Processed.

    The system uses the C1-HLTPRDVAL algorithm to validate the uploaded data through the health product and plan inbound message. Once the data is successfully validated, entities like health product, health plan, and pricing rules are created in the system.

    However, if the validation or processing fails due to any reason, the status of the inbound message is changed to Rejected and the algorithms attached to the Rejected status are invoked in the specified sequence. A To Do is created using the To Do type specified in the C1-TDCRINMSG algorithm and assigned to the users with the To Do role specified in the C1-TDCRINMSG algorithm.

    Note: The Submit for Processing button appears when the inbound message is in the Pending status.

Related Topics

For more information on... See...
How to search for an inbound message Searching for an Inbound Message
Inbound Message screen Inbound Message (Used for Viewing)
Inbound Message zone Inbound Message