1_Intake Route

The route picks up an 837P claims batch, validates the batch, splits the batch into individual 837P good claims, and stores the claims in the XEServer Data Storage Save Original with ID = Original. The route uses two XEServer properties to connect the original messages to the responses from the different web services:

• BatchID: Used to group the processing results that relate to the same input file.
• MessageID: Used to group individual claims and their related responses from a web service.

The BCounter Outbound component Set Total tracks the total number of good claims after splitting, and stores this value in Balance Counters as the field Total.

Route Structure

Route Components Description

Component Name	Component Type	Description
FS Inbound	FS Inbound	Picks up an 837 professional claims batch from the file system. Sets the property BatchID = {T_ID} to identify the input batch.
Split	XE Native	Splits the batch into good and bad individual claims.
Checkpoint	Checkpoint	Creates a checkpoint in the processing flow. If there is an error further down the route, the component rolls back the processing to the checkpoint position and attempts a retry.
Save Original	Data Storage Outbound	Stores individual claims using the ID Original.
Set Total	Balance Counter Outbound	Stores the number of total claims received as input in the Balance Counter database.
Drop Body	Velocity	Clears the message body in each XEServer message that carries an individual claim.
Checkpoint_1	Checkpoint	Creates a checkpoint in the processing flow. If there is an error further down the route, the component rolls back the processing to the checkpoint position and attempts a retry.
To Service1	JMS Outbound	Sends the messages to the route Service1.