indice-co / indice-co/EDI.Net

834 Sample interchange ONLY parsing INS segment into MemberDetail

Open
#269 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
490
Forks
173
PR merge metrics
No merged PRs in 30d

Description

When using the BenefitEnrollmentAndMaintenance_834 class in X12_834.cs, the Headers' MemberDetails List DOES get a single entry for every single INS segment, but the only data getting parsed into each MemberDetail object is what's in the INS segment:
![image](https://github.com/user-attachments/assets/578f21c0-af0b-4c4d-a071-c13e0bee6f81)

Sample file used (sourced from [here](https://www.emedny.org/hipaa/5010/transactions/834_sample_files/)):
[x12.834.txt](https://github.com/user-attachments/files/16980087/x12.834.txt)

I managed to get it working by changing the [EdiSegment, EdiPath()] attributes on the "multi-segment" classes into [EdiSegmentGroup] attributes. For MemberDetails, I'm doing `[EdiSegmentGroup("INS", SequenceEnd = "INS")]` since it's meant to include all segments from one INS segment til the next encountered (until the end of the set). Similar need to be done for the other "multi-segment" classes, like `Benefit`, `ProviderInformation`, `AdditionalReportingCategories`, and `MemberReportingCategory`

Additionally, there is nothing to handle COB or LUI segments.

As a sidenote, this is the only sample interchange that has `Hashtable` properties, but they don't seem to work. I assume it's to allow referencing the Lists by their first element in a Dictionary-like way; is that true?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with X12_834.cs and reproduce the parsing behavior using the attached x12.834.txt sample. Inspect MemberDetails and the other multi-segment classes named in the issue, along with their EdiSegment, EdiPath(), and EdiSegmentGroup attributes. Done means the sample's segments populate the intended objects, COB and LUI are accounted for, and the Hashtable behavior is clarified or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.