3 ms·
My former employer Stedi, an EDI integrations startup, is working on a compatibility layer to help companies who are affected route messages to alternative clea
by tvanhens 3y ago
My former employer Stedi, an EDI integrations startup, is working on a compatibility layer to help companies who are affected route messages to alternative clearing houses.
The founder posted on Twitter to let people know they can also reach out directly for urgent support at change@stedi.com
https://x.com/zackkanter/status/1764057780800094350?s=46 https://x.com/zackkanter/status/1764057780800094350?s=46
- koliber 3y agoI hope the compatibility layer will be self-hosted. Otherwise the compatibility layer could become an even bigger single point of failure.
- vel0city 3y agoThis current failure is already a failure of a hosted compatibility layer. The service in question presents a central JSON API to do healthcare billing so you don't have to deal with the ancient arcane EDI formats to talk to insurers.
- nradov 3y agoThe EDI formats are old, but reasonably well documented and quite easy to implement. The bigger obstacle to interoperability in this space is that the various payers have different rules around handling optional data elements or how certain things should be coded. You have to implement the base X12 EDI format plus a supplementary guide for every payer. And there are changes every year. So, it can be difficult for provider organizations to stay current. CMS could use their regulatory authority to tighten up the specifications and reduce the ability of payers to do their own thing.