1 Claim Payment Batch Route
The route splits an inbound file into separate claims, submits data to Visualizer Server for visualization on dashboards and tracking, and creates an 835 transaction as a response.
Route structure:
Route Components Description:
| Inbound 837
|
FS Inbound |
Picks up 837 transactions from the file system. |
| Native Processing
|
XE Native |
Splits the inbound file into separate claims, generates reports and acknowledgments. |
| Process Date
|
Groovy |
Extracts the claim service date (can be a period) and saves the data in the form of a message properties file. |
| Visibility - Claim
|
Visualizer Reporter |
Reports the claim data to Visualizer Server for visualization on dashboards and further tracking. |
| Load Ack
|
Subroute |
Send the data for further processing on the subroute Load Ack. |
| Archive Report
|
FS Outbound |
Saves the LDNS reports on the file system. |
| Archive File
|
FS Outbound |
Saves the original files on the file system. |
| 835 Template
|
Velocity |
Transforms the data to emulate 835 transaction generation based on the Velocity template 835-ClaimPayment_OneClaim_Template.dat that is available in the folder ${XESRoot}/profiles/Visual Tracking Sample_1/config/configuration/velocity. |
| Visibility - ClaimReports
|
Visualizer Reporter |
Stores the report data to Visualizer Server for dashboards and further tracking. |
| Validate 835
|
XE Native |
Validates the emulated 835 transactions. |
| Visibility - Payment
|
Visualizer Reporter |
Submits the emulated 835 response file to Visualizer Server for visualization on dashboards and further tracking. |
| Archive 835
|
FS Outbound |
Saves the 835 transactions on the file system. |
| Archive Report 835
|
FS Outbound |
Saves the processing reports on the file system. |
