EDI formats

Feature Requests
, ,
1

The idea is:

Utilizing EDI as an API is a software toolkit to translate between the two. Useful for an organization familiar with API that wants to connect to another organization via EDI.

My use case:

interchanging EDI ( EDI, X12, HIPAA, EDIFACT, HL7, NCPDP, EANCOM, VDA, PNRGOV, IATA, IAIABC, Flat Files, EDIGAS) files to convert them into JSON payloads

I think it would be beneficial to add this because:

Extremely beneficial for organizations including healthcare to interchange data between API and EDI. An EDI node may be used as an adapter.

Any resources to support this?

various EDI formats (X12, EDIFACT, HL7, etc.) and their corresponding JSON representation

2

Hey @physx911,

Solid request there, EDI can be a pain. Don’t forget to hit the vote button to make it count.

3

Unfortunately, I’m out of ballots

4

Any news about this requirement from 2022? :smiley:

5

Hey @Fortian,

No real updates on this one, It doesn’t have that many votes compared to other requests so is fairly low down on the list.

6

Very important feature, I use EDI for so many bug projects.

1 Like
7

Hey @avi,

Welcome to the community :raised_hands:

Which EDI format do you use is it EDIFACT or one of the others?

8

From what I can tell, there are very few or no open source libraries that translate EDI formats to standards like JSON or XML and back. The reliable libraries can be licensed but it’s pricey. One of those companies could make a closed-source module for N8N, but doesn’t seem likely until N8N gets a lot bigger.

Anyone doing EDI with relatively few trading partners should look at AWS’ new service B2B Data Interchange. You pay $8/mo per trading partner, plus a fraction of a cent per transformation.

Lee