6 ms·

Old dudes like me might have a strong negative reaction to something called "EDI."

by robterrell 12y ago

peaton 12y ago
For the young dudes like me could you explain why?
- jzawodn 12y ago
  This: http://en.wikipedia.org/wiki/Electronic_data_interchange http://en.wikipedia.org/wiki/Electronic_data_interchange
- ChikkaChiChi 12y ago
  http://en.wikipedia.org/wiki/Electronic_data_interchange http://en.wikipedia.org/wiki/Electronic_data_interchange For the record the term is still thrown around left and right in enterprise settings.
  - daigoba66 12y ago
    US Healthcare Insurance industry relies heavily on this for... everything.
    - kyllo 12y ago
      Yep. And to a somewhat lesser extent, so does international commerce and logistics. Nearly all major importers of goods (think Wal-Mart for example) and their various suppliers and service providers rely on EDI to exchange commercial documents (purchase orders, commercial invoices, packing lists), file customs entries, track their incoming shipments and inventory, etc etc. EDI is probably irrelevant and dead in Silicon Valley (unless maybe you work at Oracle). But in healthcare and commerce it's very much alive.
      - ChikkaChiChi 12y ago
        It exists heavily in my industry (retail channel management) but mostly as design specs. Most companies tend to use XML it seems but they still base their feeds off of the old-school spec.
runevault 12y ago
Not just old dudes, in my job we have to output and ingest various EDI formats (though mostly 820) all the time dealing with financial information.
dchamberlin 12y ago
Please tell me it has a built in EDI parser/linter
kyllo 12y ago
Old dudes as well as young dudes in old-school industries like healthcare or logistics. I work at a logistics company and inter-company integration via EDI messaging is still considered cutting-edge technology in this field. Of course it doesn't just mean pre-internet standards like ANSI X12 and EDIFACT anymore, these days much of the messaging is CSV and XML data pushed over FTP or AS2. But it's almost like no one has even heard of an HTTP REST API or JSON (or even SOAP) yet.
- dragonwriter 12y ago
  > Old dudes as well as young dudes in old-school industries like healthcare or logistics. [...] > Of course it doesn't just mean pre-internet standards like ANSI X12 and EDIFACT anymore, these days much of the messaging is CSV and XML data pushed over FTP or AS2. But it's almost like no one has even heard of an HTTP REST API or JSON (or even SOAP) yet. Given that both an HTTP+Mime and a SOAP transport are mandatory for all payers to support for transactions (which, yes, are still X12) covered under operating rules adopted as national requirements under HIPAA [1], I'm pretty sure that its not the case that no one in the healthcare industry has heard of SOAP. [1] Under the CORE 270 Connectivity Rule, http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf
  - kyllo 12y ago
    Interesting, thanks for sharing. Like I said, I work in logistics. I've never worked in healthcare before so I didn't know they are required to use SOAP, but I was aware that they use lots of X12 and I guess I thought SOAP content was always XML. SOAP is pretty rare in my industry. Almost all FTP & AS2.
satyajitranjeev 12y ago
Thought of it as a succession to ed. And it nicely inverses to IDE.
grimman 12y ago
You just need some new and more pleasant associations! http://masseffect.wikia.com/wiki/EDI http://masseffect.wikia.com/wiki/EDI
mqsiuser 12y ago
Instead of complaining you can just try to fix the situation. Things get better: Open Source, Git Hub and you can have your share, too! My 0.02 Cents here: http://www.use-the-tree.com http://www.use-the-tree.com I am still waiting for people to join in (write parsers) and customers to be convinced and use it :-)

Old dudes like me might have a strong negative reaction to something called "EDI."

peaton 12y ago

For the young dudes like me could you explain why?

jzawodn 12y ago
This: http://en.wikipedia.org/wiki/Electronic_data_interchange http://en.wikipedia.org/wiki/Electronic_data_interchange
ChikkaChiChi 12y ago
http://en.wikipedia.org/wiki/Electronic_data_interchange http://en.wikipedia.org/wiki/Electronic_data_interchange For the record the term is still thrown around left and right in enterprise settings.
- daigoba66 12y ago
  US Healthcare Insurance industry relies heavily on this for... everything.
  - kyllo 12y ago
    Yep. And to a somewhat lesser extent, so does international commerce and logistics. Nearly all major importers of goods (think Wal-Mart for example) and their various suppliers and service providers rely on EDI to exchange commercial documents (purchase orders, commercial invoices, packing lists), file customs entries, track their incoming shipments and inventory, etc etc. EDI is probably irrelevant and dead in Silicon Valley (unless maybe you work at Oracle). But in healthcare and commerce it's very much alive.
    - ChikkaChiChi 12y ago
      It exists heavily in my industry (retail channel management) but mostly as design specs. Most companies tend to use XML it seems but they still base their feeds off of the old-school spec.

runevault 12y ago

Not just old dudes, in my job we have to output and ingest various EDI formats (though mostly 820) all the time dealing with financial information.

dchamberlin 12y ago

Please tell me it has a built in EDI parser/linter

kyllo 12y ago

Old dudes as well as young dudes in old-school industries like healthcare or logistics. I work at a logistics company and inter-company integration via EDI messaging is still considered cutting-edge technology in this field. Of course it doesn't just mean pre-internet standards like ANSI X12 and EDIFACT anymore, these days much of the messaging is CSV and XML data pushed over FTP or AS2. But it's almost like no one has even heard of an HTTP REST API or JSON (or even SOAP) yet.

dragonwriter 12y ago
> Old dudes as well as young dudes in old-school industries like healthcare or logistics. [...] > Of course it doesn't just mean pre-internet standards like ANSI X12 and EDIFACT anymore, these days much of the messaging is CSV and XML data pushed over FTP or AS2. But it's almost like no one has even heard of an HTTP REST API or JSON (or even SOAP) yet. Given that both an HTTP+Mime and a SOAP transport are mandatory for all payers to support for transactions (which, yes, are still X12) covered under operating rules adopted as national requirements under HIPAA [1], I'm pretty sure that its not the case that no one in the healthcare industry has heard of SOAP. [1] Under the CORE 270 Connectivity Rule, http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf
- kyllo 12y ago
  Interesting, thanks for sharing. Like I said, I work in logistics. I've never worked in healthcare before so I didn't know they are required to use SOAP, but I was aware that they use lots of X12 and I guess I thought SOAP content was always XML. SOAP is pretty rare in my industry. Almost all FTP & AS2.

satyajitranjeev 12y ago

Thought of it as a succession to ed. And it nicely inverses to IDE.

grimman 12y ago

You just need some new and more pleasant associations! http://masseffect.wikia.com/wiki/EDI http://masseffect.wikia.com/wiki/EDI

mqsiuser 12y ago

Instead of complaining you can just try to fix the situation. Things get better: Open Source, Git Hub and you can have your share, too! My 0.02 Cents here: http://www.use-the-tree.com http://www.use-the-tree.com I am still waiting for people to join in (write parsers) and customers to be convinced and use it :-)