Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / How Vertical SaaS Is Solving Healthcare Interoperability
Transcript
- Lucas: So here's a number that still kind of bothers me. The US healthcare system spends somewhere around $5 billion a year just on fax machines. We're in 2026 and critical patient data is still traveling over telephone lines as images on paper. Luna: And yet we keep hearing that healthcare is finally digitizing. I mean, electronic medical records are everywhere now. Lucas: They are. But having a digital record on one system and being able to share it with the system across the street are two very different things. That gap is where vertical SaaS has gotten interesting over the last, say, five years. Luna: You know, I get that a lot of people listening work in or with healthcare. And if this episode helps clarify why your clinic's software still doesn't talk to the hospital down the road — that's exactly the kind of insight we try to deliver here. If today was worth a coffee to you, the link is super simple: buy me a coffee dot com slash fexingo. No pressure, just a way to keep the show ad-free. Lucas: Yeah, and we appreciate that. So, where does the problem start? Interoperability. It's the technical term for systems that don't talk to each other. And for decades, the standard for healthcare data exchange was something called HL7 version 2. Luna: Right, which is from the late eighties. It's not even xml based. It's a pipe-delimited text format. Lucas: Exactly. And it worked as long as both ends agreed on what each field meant. But in practice? Every implementation was a little different. So you'd get 'patient name' in one system and 'name' in another, and the mapping broke. The result is that hospitals and clinics spend huge money on integration middleware just to get basic lab results or medication lists to flow. Luna: Enter FHIR. The Fast Healthcare Interoperability Resources standard. It's modern, RESTful, uses JSON. It was designed from the ground up to be web-friendly. Lucas: And the government put some serious money behind it. The 21st Century Cures Act, back in 2016, mandated that EHR vendors offer FHIR APIs. The Office of the National Coordinator for Health IT has been enforcing information blocking rules since 2021. But adoption has been slow. Why? Because the incumbents — Epic, Cerner, Meditech — they built their moats on proprietary data. Luna: Epic especially. They have something like 40 percent of the large hospital market. And their system is incredibly sticky. Once a hospital goes Epic, it's hard to leave because all their clinical workflows are tied to it. Lucas: But here's where vertical SaaS comes in. A lot of the newer software for specific specialties — dermatology, ophthalmology, behavioral health — they're being built on FHIR from day one. They don't have to retrofit. So they can offer a practice management system for a small clinic that talks to the big hospital's Epic system via FHIR and actually works. Luna: Give me a concrete example. Who's doing this well? Lucas: Take a company called DrChrono. They started as a tablet-based EHR for small practices. But they've built on FHIR and have a marketplace of integrations. A dermatologist can use DrChrono for scheduling, billing, notes, and then send a referral to a hospital with a fhir based document. The data doesn't get lost in a fax queue. Luna: What about revenue cycle management? That's another area where data exchange is critical. Lucas: Huge. A claim goes from the practice management system to a clearinghouse, then to the payer. If any format mismatch happens, the claim gets rejected. A vertical SaaS company like Athenahealth claims its integrated network reduces denial rates by matching payer-specific rules. They're not just an EHR; they're a data translator. Luna: And the federal government has been pushing real. The CMS interoperability rule, finalized in 2020, requires payers to share patient data via FHIR. So now the insurance companies have to build APIs. That opens up a whole new set of integrations for vertical SaaS providers. Lucas: That's the key insight. Interoperability isn't just about hospitals talking to clinics anymore. It's about payers, labs, pharmacies, public health registries — all consuming and producing data. A vertical SaaS company that can thread that needle for a specific provider type has a defensible product. Luna: But is it actually happening at scale? Or are we still in pilot phase? Lucas: It's happening, but unevenly. The big academic medical centers are pretty wired. Community hospitals less so. And small private practices are the most behind. That's where the opportunity is. There are roughly 200,000 independent physician practices in the US. Most use legacy systems or even paper. A vertical SaaS product that offers a cloud-based EHR with built-in FHIR exchange can land in a week. Luna: What about cost? Is it cheaper than the old fax-based workflows? Lucas: It can be, but the upfront switch is painful. You have to migrate years of patient data. The old system's data might be in a proprietary format. So there's often a data conversion cost. But once you're on a fhir native system, the ongoing cost of exchanging data drops dramatically. No per-fax charges, no manual data entry errors. Luna: And the security angle? FHIR uses OAuth and HTTPS, so it's more secure than fax in terms of encryption. Lucas: Right. The old HL7 v2 often ran over unencrypted sockets. So FHIR is a win for privacy. And the ONC requires certified APIs to support patient access, so patients can download their own records via smartphone apps. That's a consumer-driven pull that forces provider adoption. Luna: We're also seeing some interesting vertical plays in areas like dental and veterinary. Those are smaller markets but have terrible interoperability with human health systems. Lucas: And there's a big push around social determinants of health. Community health centers that serve low-income populations need to share data with social services. A vertical SaaS company that can integrate with a housing agency's system via FHIR? That's a value-add that's hard to replicate. Luna: One challenge I hear about is versioning. FHIR has multiple versions — STU3, R4, R5. Not all are backward compatible. Lucas: It's a mess. R4 is the current standard that CMS mandates, but some vendors lag. And as FHIR evolves, you have to update your API endpoints. But that's a software problem, not a fundamental barrier. Compare it to having to redo point to point integration every time you partner with a new hospital. FHIR reduces the combinatorial complexity. Luna: So where does this go in the next three to five years? Lucas: I think we'll see more vertical SaaS companies pivoting to become data platforms. The EHR becomes a commodity; the real value is in the network effects of data exchange. If you're a practice and all your referring providers, labs, and payers are on your platform's network, switching costs become enormous. That's the moat. Luna: It's almost like the Stripe model for healthcare. Stripe doesn't just process payments; it provides a whole infrastructure. The vertical SaaS companies that can offer not just software but a data utility will win. Lucas: Exactly. And we're already seeing it with companies like Health Gorilla. They're a kind of interoperability backbone as a service. But the vertical SaaS players might build that in themselves for their niche. Luna: What about the role of AI? Could that accelerate interoperability? Lucas: Yes, but cautiously. AI can help map legacy data formats to FHIR. Natural language processing can extract information from unstructured doctor's notes. But you have to be careful about hallucinations. A mis-mapped medication could kill someone. So AI will assist, but validation loops are essential. Luna: That's a sobering thought. But also an opportunity for vertical SaaS to provide that validation layer. Lucas: Right. And the incumbents are not standing still. Epic has its own interoperability suite, Care Everywhere. But they're still a large enterprise product. The advantage of vertical SaaS is nimbleness and focus on a specific workflow. A small orthopedics practice doesn't need the full Epic system; they need something that talks to Epic. Luna: So the big takeaway: vertical SaaS in healthcare isn't about replacing Epic. It's about being the glue that makes Epic talk to everything else. Lucas: Exactly. And that's a multi-billion dollar opportunity. We'll keep watching how it evolves.