Sample Duplication Check Profile Workflow

The route Duplicate Claims Check in this profile picks up an 837 transaction from the file system. Then the XE Native component splits the transaction by claims and validates the data. Valid claims obtain a set of properties, including the ClaimID property. The route directs the data to the Tracking and Duplication component. If a claim is processed for the first time, the route registers the ClaimID in the Elasticsearch Node Storage and directs the claim to the Good Claims output folder. If a claim was processed before, and the ClaimID already exists in the Elasticsearch Node Storage, the route directs the claim for further processing. An HTML processing report is generated, depending on the processing result.

Note A check for duplication can be performed by any property. This allows you to detect unique and duplicate items not only in the scope of ClaimID, but in the scope of providerID, subscriberID, transactionID and other.

The route Duplicate Claims Check has the following structure:

Component Name	Component Type	Description
Inbound Claims	FS Inbound	Picks up an 837 transaction from the file system.
Validate, Split, Reports	XE Native	Splits the incoming transaction into good and bad claims.
Duplication Check	Tracking and Duplication	Checks claims for uniqueness.
Bad Data	FS Outbound	Stores the invalid claims to the file system.
Reports	FS Outbound	Stores the splitting report in the file system.
Report Footer	Velocity	Translates the incoming data into the report footer based on the velocity template that is available.
Report Header	Velocity	Translates the incoming data into the report header based on the velocity template that is available.
Good Claims	FS Outbound	Stores the valid claims to the file system for reference purposes.
Report Body	Velocity	Translates the incoming data into the report body based on the velocity template that is available.
Final Report	FS Outbound	Stores the final processing report in the file system.