Issues
- 0
.NET Standard 2.0 compliant?
#23 opened by briansboyd - 2
- 2
Error Parsing Certain 837 Claims
#22 opened by larryrshirley - 0
856 conversion error
#24 opened by juancxt - 2
Parse X12 835 and other documents?
#21 opened by JeffreyZolaVisibilEdi - 32
Importing into the database but..
#16 opened by denissedonnelly - 3
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
#18 opened by mamohanma - 0
5010 specifications injection?
#19 opened by mamohanma - 2
FileLoadException
#15 opened by johnweidauer - 1
Adding DMG Segment to NM1 Returns NULL
#5 opened by JeffFerguson - 1
- 1
Edi Claim 837 Required Field
#11 opened by nigamabhay671 - 1
EDI Claim 837 Mandatory Feild Details
#12 opened by nigamabhay671 - 1
- 5
Available as Nuget package?
#13 opened by JeffreyZolaVisibilEdi - 1
- 0
- 0
All Exception Errors cause Crash
#7 opened by martinamw - 0
- 0
X12 Parser Comment
#2 opened by Mythran101