4 ms·
I love the excitement coming out of the elixir community.. it really shows. can't wait to see what you're working on.. phoenix app or something else? we do stra
by tmat 9y ago
I love the excitement coming out of the elixir community.. it really shows. can't wait to see what you're working on.. phoenix app or something else? we do straight elixir / plug api with a separate node/react front end.. we also use json-api which has been nice to standardize or json structure.
- jetti 9y agoFor some "quick" money I'm doing a small Phoenix app that is doing CSV processing/formatting and is going to be an adsense page. I'm looking into doing a full blown Elixir/OTP app that handles X12 EDI parsing/validating but we shall see. I'm going to start writing the X12 parser soon and will at least open source that. Edit: I would add I was able to talk a client into allowing me to write their platform in Phoenix and away from the Laravel. So I've been working on that as well.
- tmat 9y agonice! good luck...
- jetti 9y agoThanks, you too!
- mlpinit 9y agoDo you have any tips for where to find open source X12 specifications? Seems like EDIFACT is nicer from this perspective.
- jetti 9y agoUnfortunately ASC X12 is very good at keeping their docs hidden. I'm fortunate to be able to have the docs provided by work but when I didn't I would just search for the file type and spec (e.g "837 Spec") and would go off the companion guides. Companion guides from various companies are not a reliable to create a product though as they can deviate from the standard EDIT: One place I forgot to look is Microsoft's BizTalk HIPAA information[0]. It has information about the various segments and how they are laid out. [0] https://msdn.microsoft.com/en-us/library/cc982631(v=bts.10).aspx https://msdn.microsoft.com/en-us/library/cc982631(v=bts.10)....
- dragonwriter 9y ago> Unfortunately ASC X12 is very good at keeping their docs hidden They aren't hidden, they just aren't free, and the kinds of people paying for them aren't as likely to share them illegally as is the case with some other non-free content. (The 4010 versions of the standards were free [gratis, not libre] because the government paid X12 to make them available without charge to encourage adoption.) > One place I forgot to look is Microsoft's BizTalk HIPAA information[0]. It has information about the various segments and how they are laid out. Unless I'm missing something, it only seems to have info on the common envelope segments, not the segments making up the actual transaction set, and the information it does have is woefully incomplete.
- jetti 9y agoYou're right, they aren't hidden but not free. Hidden was a bad choice of words as they just aren't available without paying. BizTalk and Websphere documenation on X12 is limited and mainly focuses around the envelopes (though I do believe there are other segments covered in BizTalk docs I just can't find them at the moment). If you don't have access to the specificiations then your only real options are BizTalk/Websphere/other tool docs + companion guides. It isn't going to get you far at all
- dragonwriter 9y agoThe full set of HIPAA mandated X12 standards is only $3,100, which isn't all that much. (Though, yeah, it would be much better if they were still gratis; but even when they were it wasn't exactly like the open-source community was jumping all over them.) The bigger problem is that many of the external code sets referenced are also not-free-of-charge, and weren't even when the X12 standards were.
- jetti 9y agoIt isn't that much for a company but that is sure a large amount of money to start an open source project.
- dragonwriter 9y ago> Do you have any tips for where to find open source X12 specifications? They don't exist. X12 specs are proprietary, not open source.