Daren Thayne

Clinicians want to use AI but don’t have the bandwidth to evaluate all the different models. Meet Health Olymp, an AI tool purpose-built for clinicians. Here’s why this matters 👇 1. Health and life science experts gain instant access to frontier models for free. No procurement hoops or IT bottlenecks. Every clinician gets their own sandbox to explore. 2. Clinicians can compare models side by side and pick the one that works best for their use case. That transparency builds trust and sparks ideas for novel AI applications in care delivery, diagnostics, and research. 3. Most AI benchmarks are too generic or disconnected from clinical reality. Health Olymp brings frontline feedback into the loop, helping the industry identify models that perform reliably in real world clinical environments. Congrats to Ruslan Nazarenko and the Lumos team as they put AI model benchmarking directly into the hands of healthcare professionals. ⬇️ (link in comments)

148

53 Comments

Interoperability doesn’t happen on its own. Valere builds it. At Valere Health, we create interoperability by: -Connecting EMRs, third-party vendors, distributors, and manufacturers -Automating workflows across those systems -Eliminating manual handoffs and data chasing -Freeing teams to focus on high-value, strategic work Clean connections lead to cleaner execution. Watch the full episode of The Co-Conspirator Track with CSO Madhan Kris Srinivasan and VP of Brand Marketing Caleb Long- linked in the comments.

7

1 Comment

Bringing a new product to market in MedTech (or any regulated industry) takes more than great engineering. It also takes regulatory strategy built in from day one. Too often, these two tracks run separately -- engineering pushes ahead, while regulatory steps in later to “check the boxes.” The result? Delays, rework, and surprises no one enjoys. When engineering and regulatory work as one team under one roof, the story changes: -Compliance is baked into design decisions -Submissions move faster with fewer surprises -Innovation and safety stay aligned Our latest blog explores how integrated teams accelerate time-to-market and reduce risk -- without compromising on innovation. Read more 👉 https://lnkd.in/gj_v_e5r

6

3 reasons why we build software and service as one team: We don’t build tech *for* operations at Tandem. We build tech *with* operations. Here’s why that matters; 1) Fix friction at the root. If a vet has to click 5 times to do something that should take one, we fix it. Not just because it’s “inefficient”. But because it creates cognitive load, slows care delivery, and compounds under pressure. Less friction = faster throughput, fewer errors, and lower burnout. 2) Close the loop between builders and users. The person who writes the feature talks directly to the person who uses it. That means issues surface faster, fixes are more accurate, and nobody ships something that “technically works” but operationally fails. It’s not just “faster iteration” - it’s tighter alignment with reality. 3) Scale the system, not the sprawl. New clinics, new roles, new workflows. We don’t layer on SaaS duct tape. We evolve a system designed to flex with operational growth. That means fewer integration points, tighter control, and a consistent experience from core to edge. We don’t treat tech like a layer. We treat it like a nervous system. Because when you’re delivering care in the real world, you can’t afford delay, dissonance, or dropped signals. That’s why we built Tandem the way we did: One system. One team. Zero silos. Because when service and software evolve together, the whole organism gets smarter, faster, and stronger over time. ------------- Hi, I’m Doug. I’m the Chief Technology Officer at Tandem. We’re engineering the backbone for modern pet care. Follow me for posts on: * How we build tech with ops, not for them * How we build tech tools that scale cleanly * Scaling hybrid companies without SaaS bloat

27

2 Comments

CMS drops another model (4th one in about 30 days) - LEAD aka Long-term Enhanced ACO Design. This one had my head scratching... Reason...trying to identify what it actually is and material differences from prior ACO models like REACH. Abe's video announcement on the LEAD landing page is very generic...it just sounds like he is explaining ACOs and Value-Based Care. To truly see what is different, you have to go into the weeds of the FAQ. I'll dig in more on the FAQ later but I had to answer my first question...why did CMS come out with this model? If I had to answer for CMS in plain language (because CMS announcements are chalked full of industry jargon and fluffy vocabulary), this is what I think they are saying the point of LEAD is... "We’re committing to value-based care for the long haul, smoothing out some pain points of prior models, and trying to make the model survivable for more organizations." Anyone else agree? What's your take? Up next I'll dive into more of the details to highlight the new model.

22

1 Comment