Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EDI parsing does not handle segment groups with an optional first segments #126

Closed
mtruchard opened this issue Apr 19, 2017 · 1 comment
Closed
Assignees
Milestone

Comments

@mtruchard
Copy link

I have EDI x837 data that seems to make use of an optional first segment in the "drug identification 2410" loop. The group starts with an optional LIN segment followed by a CTP segment and can repeat 0 to 25 times. The spec I have says that the LIN segment is optional but I don't see a way to configure the smooks edi mapping to detect a segment group with an optional first segment for a repeated segment. I read up on EDI and 837 and it seems that this is valid. One doc said that a loop will repeat until segments are found that fall outside of the loop. Another doc said that normally a loop is detected when its first segment is hit again. I'm not 100% sure on the EDI rules around this.

Here is some example data:

LIN||N4|00703722102
CTP||||1|ML
LIN||N4|0338954206
CTP||||1|ML
CTP||||1|ME

And here is an extract from the config:

<medi:segmentGroup xmltag="DrugIdentification_2410" minOccurs="0" maxOccurs="25">
	<medi:segment segcode="LIN" xmltag="DrugIdentification" minOccurs="0" maxOccurs="1" truncatable="true">
		<medi:field xmltag="DrugAssignedIdentification" />
	</medi:segment>
	<medi:segment segcode="CTP" xmltag="DrugQuantity" minOccurs="0" maxOccurs="1" truncatable="true">
		<medi:field xmltag="DrugClassOfTradeCode" />
	</medi:segment>
</medi:segmentGroup>
@cjmamo cjmamo self-assigned this Apr 11, 2020
@cjmamo
Copy link
Member

cjmamo commented Apr 11, 2020

The issue is no longer applicable: the next Smooks release replaces MEDI with DFDL.

@cjmamo cjmamo closed this as completed Apr 11, 2020
@cjmamo cjmamo added this to the v2.0.0-M1 milestone Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants