This edi processor is not generating loops as per the spec http://www.edissweb.com/docs/blue/837Icompanion.pdf.
Accoriding to the spec, billing provider information should be inside it's own loop 2010AA with it's own NM1, N3, N4 and REF segments. But the generated JSON does not contain any loops and has all segments mixed together. This is making it harder for processing the resulting JSON.
Attached are the sample input and output files
Input:
TEST_837P.EDI.txt
Output:
TEST_837P.EDI.JSON.txt
This edi processor is not generating loops as per the spec http://www.edissweb.com/docs/blue/837Icompanion.pdf.
Accoriding to the spec, billing provider information should be inside it's own loop 2010AA with it's own NM1, N3, N4 and REF segments. But the generated JSON does not contain any loops and has all segments mixed together. This is making it harder for processing the resulting JSON.
Attached are the sample input and output files
Input:
TEST_837P.EDI.txt
Output:
TEST_837P.EDI.JSON.txt