Old dudes like me might have a strong negative reaction to something called "EDI."
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.
> 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
For the record the term is still thrown around left and right in enterprise settings.
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.
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
I am still waiting for people to join in (write parsers) and customers to be convinced and use it :-)