Stedi reposted this
new post - a write up of what electronic data interchange is, X12, and how Stedi works: https://lnkd.in/ekAm-cQv if you've ever wondered why prior authorizations or eligibility checks are so painful in healthcare, understand X12 and its limitations are part of that we walk through what Stedi does to turn X12 in JSON-based APIs, a walkthrough of the product, and some of my thoughts on what's cool and what they might struggle with down the line [This one is a sponsored post, but it was really cool to learn from Zack Kanter and the team around EDI, something that was on my list to-do for a while]
Nikhil Krishnan checking benefits pre-visit is the on ramp to the entire revenue cycle and is the differentiator for well run practices. There is ZERO difference whether you are a brick and mortar business or a digital/telemed model. We all need to get paid, have the tools to accurately calculate (in advance) what any member needs to pay at the point of care. B&M practices that don’t do this but ‘send claims/wait/mail statements’ are a set up for failure.
Zack Kanter has Stedi built more than the API/EDI provider<-> payer, ie: An embedded UI in the EHR/PM for -real time and batch scheduled 270/271 -daily/twice daily 837 batch claim submission -835 push These are fundamental features that keep most of us tied to (insert clearinghouse name). EDI can’t just be a backend process. **what is the current state of things for EDI advanced EOB /predetermination of benefits/GFE?
Favorite lines: “Ever since I’ve been in healthcare, I’ve heard the engineering teams talk in passing about “EDI,” “X12,” and “wait how does our company make money?” But for a long time, I simply ignored this topic because I thought knowing something about this niche might actually lower my chances of finding love.”
We made the switch over to Stedi and were live in a day. We had built our logic around the Change API, so switching to Stedi was seamless. Thanks Zack Kanter and Sean O'Donnell
👏 Stedi. Let’s take down the clearinghouse cartel. You left out EDI 837, the actual claim file fyi
I have chatted with Zack and Dave (as collogues) and have reviewed their offerings. When feasible in my subject matter expertise projects or to augment my existing development solutions with technology teams, I will suggest Stedi as a reputable, efficient processing platform.
The Stedi x Out-Of-Pocket collab that I have been waiting years for
Building healthcare's digital assistant.
2moHow is Stedi different from Inovalon, Availity, Wave HDC - Healthcare Data Curation, or any other host of clearinghouse/data companies that already provide JSON APIs and convert to X12/HL7 to integrate with payers and providers? I'm not quite seeing the value add to pour $70m into this company.