This project has moved and is read-only. For the latest updates, please go here.

Unbundling by CLP01 / Merging 835's

Nov 21, 2012 at 8:53 PM

My current project calls for one 835 file to be broken down into 5 or 6 provider-specifc files, and the value that the records need to be sorted/grouped by is in the CLP01 field.

So my question is - is it possible to unbundle an 835 file by a value in the CLP01 field?  Basically I want to pull out all claims that match a value mask, and store them in their own 835 file.  I can unbundle it by the 2100 loop, but then I get 3,000 separate files, and that seems excessive. 

Or should I take this on from the other direction and try to merge the files that got unbundled, back into 1 file(After sorting into distinct folders) ?

Anyones thoughts on this would be appreciated.

- Thanks

Nov 22, 2012 at 2:42 PM

The problem with merging files is that you have to identify how to merge loops back which can be pretty complicated.  The purpose of the unbundling is to break-up the file into individual units for processing.  I would only attempt a rebundle if you are truely trying to maintain the integrety of the file with all possible segements (even ones you are not concerned with).

The easier method would be to just parse your file into a flattened format and then reproduce files by looping through your parsed data format.  The files you create would only include the elements that you parsed (any extra segments might be lost), but if you are doing this just for internal processing.

The attempt to rebundle would be most valuable if you have downstream processes that might need more segments than what you are immediately concerned with.

Just be careful, there really isn't a single identifier that let's you know two loops were originally the same loop (this only exists at the ISA, FG, and ST segments), so you really need to compare the entire loop header to ensure that it's the same loop that can be merged back.