Step 3 Create Batch Individual Route

This route batches the 277 responses and the 276 requests that do not have a corresponding 277 response.

Route Structure

Step 3 Create Batch Individual Route

Route Components Description

Component Name Component Type Description
Create Batch Individual JMS Inbound Receives a trigger message from the queue Create_Batch_Response to initiate the route processing.
Get Response (277) Data Storage Inbound Extracts the validated 277 responses from the XEServer Data Storage and sends them through the data output. Also, the component sends the original trigger message through the output original to pick up those 276 requests that do not have an associated 277 response.
Get Requests (276) Data Storage Inbound Extracts the remaining 276 requests from the data storage. At this point, the data storage contains only those 276 requests that do not have a corresponding 277 response generated.
Generate AAA XE Translator Generates acknowledgements for "non-responded" 276 requests.
AAA Generation Errors FS Outbound Stores the acknowledgement generation error reports, if any.
Merge Aggregation

Merges the validated 276 responses and the "non-responded" 276 requests.

Note The merging is implemented by using a pluggable HIPAA merger strategy. To make the merge work, be sure to copy the file merger_hipaa277x212cs.properties from the folder ${XESProfileConfig}/artifacts/Merger to the folder ${XESRoot}/features/route-engine/components/aggregator-hipaa/config.
BatchedResponse FS Outbound Stores the batched response on the file system.