Search results

Can't Parse Multiple Transactions in Single 837

Status: Open.

#25 In Inteligenz/X12Parser;

· Mythran101 opened on May 23, 2025

856 conversion error

Status: Open.

#24 In Inteligenz/X12Parser;

· juancxt opened on Aug 26, 2021

Parse X12 835 and other documents?

Status: Open.

#21 In Inteligenz/X12Parser;

· JeffreyZolaVisibilEdi opened on Jan 13, 2021

5010 specifications injection?

Status: Open.

#19 In Inteligenz/X12Parser;

· mamohanma opened on Sep 1, 2020

Segment 'NM1*QD*1*CLAY*MARTONN*C' in segment position 26 within transaction '681560001' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2010BB. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

Status: Open.

#18 In Inteligenz/X12Parser;

· mamohanma opened on Aug 31, 2020

Importing into the database but..

Status: Open.

#16 In Inteligenz/X12Parser;

· denissedonnelly opened on Apr 13, 2020

What is last version that this parser is supporting?

Status: Open.

#14 In Inteligenz/X12Parser;

· moumenmosa opened on Jan 11, 2020

Available as Nuget package?

Status: Open.

#13 In Inteligenz/X12Parser;

· JeffreyZolaVisibilEdi opened on Jul 17, 2019

EDI Claim 837 Mandatory Feild Details

Status: Open.

#12 In Inteligenz/X12Parser;

· nigamabhay671 opened on Dec 1, 2018

Edi Claim 837 Required Field

Status: Open.

#11 In Inteligenz/X12Parser;

· nigamabhay671 opened on Dec 1, 2018

837P Specification Does Not Include PER Segment For Loop 2010CA

Status: Open.

#10 In Inteligenz/X12Parser;

· JeffFerguson opened on Oct 2, 2018

EligibilityTransformationService throws exceptions during parsing of responses

Status: Open.

#9 In Inteligenz/X12Parser;

· tmccurdy opened on Jun 14, 2018