Stedi

If you’re using Stedi’s List Enrollments API, you can now control how returned enrollment records are sorted. Before, enrollment records were always sorted by descending creation date. That’s still the default. Now you can also sort by last status update, last update, or ID. You can choose the sort direction (ascending or descending) and combine sort fields to get stable, deterministic ordering.

Our technical product managers, Nick Radov and Arna Meyer, just wrapped up their week at the X12 Winter 2026 meeting in Portland. Most electronic healthcare billing transactions — like claims and eligibility checks — are required to use X12 EDI. It’s what Stedi uses under the hood. These meetings are where X12 standards are settled and evolve. And it's where Nick and Arna – with decades of shared experience – get to learn and weigh in. We’re proud of the work Arna and Nick are doing – alongside the community – to move X12 forward.

Reposting a somewhat old post. For all you RCM nerds, this is probably the most comprehensive map I've seen of the RCM space.

Thanks, Jordan Haisley. We love seeing folks take advantage of our changelog RSS feed! If you're curious, you can check out our changelog here: https://lnkd.in/ebx7yvda The RSS feed is here: https://lnkd.in/eETwsCfj

We're proud to have Winspire RCM as a Stedi Platform Partner. Winspire is a fully transparent, outcome-driven revenue cycle management (RCM) platform and service for healthcare organizations.

We're proud to have Winspire RCM as a Stedi Platform Partner. Winspire is a fully transparent, outcome-driven revenue cycle management (RCM) platform and service for healthcare organizations.

Insurers – called payers in healthcare – almost never pay what’s billed on a claim. That’s by design. The billed amount is just a starting point. What actually gets paid is the allowed amount – a price negotiated in advance between the payer and the provider. In this clip from our podcast, Eric Bricker, MD of AHealthcareZ breaks down how this works, with a simple example.

Today, we're putting a spotlight on ✨ Joel Fenelon, ✨ co-founder and CEO of Pangaea Healthcare. 𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝗣𝗮𝗻𝗴𝗮𝗲𝗮 𝗛𝗲𝗮𝗹𝘁𝗵𝗰𝗮𝗿𝗲 𝗱𝗼? Pangaea Healthcare is building a revenue intelligence platform on a clear conviction: the future of RCM is payers being present by proxy at every step of healthcare operations. Instead of EHR-centered billing workflows that apply payer logic too late or not at all, we embed payer-aware intelligence directly into clinical and operational workflows so that care, documentation, and claims are shaped with reimbursement in mind from the start. 𝗛𝗼𝘄 𝗱𝗶𝗱 𝘆𝗼𝘂 𝗲𝗻𝗱 𝘂𝗽 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗶𝗻 𝗵𝗲𝗮𝗹𝘁𝗵 𝘁𝗲𝗰𝗵? My path into health tech started with my father’s own painful experience navigating the healthcare system. Watching someone you love suffer needlessly because people and systems failed to coordinate properly leaves a mark, and it creates a kind of fire that never dies. When I later met my cofounder Levinski, we recognized that same failure pattern at scale. Value isn’t being lost because providers don’t care; it's being lost because the systems around them are brittle and disconnected. Billing teams work hard, but are trapped in workflows that force them to manually reconstruct reality from incomplete data. Once you see that clearly, it’s hard to look away. Health tech became the arena where building better systems could meaningfully improve both financial sustainability for providers and ultimately, patient care. 𝗛𝗼𝘄 𝗱𝗼𝗲𝘀 𝘆𝗼𝘂𝗿 𝗿𝗼𝗹𝗲 𝗶𝗻𝘁𝗲𝗿𝘀𝗲𝗰𝘁 𝘄𝗶𝘁𝗵 𝗿𝗲𝘃𝗲𝗻𝘂𝗲 𝗰𝘆𝗰𝗹𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 (𝗥𝗖𝗠)? My role sits at the intersection of product, operations, and revenue reality. I spend time with billing teams, operators, and executives to see exactly where RCM breaks down in day-to-day execution. That perspective directly shapes what we build. We design around the precise moments where claims slow, denials occur, or critical data goes missing. 𝗪𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗥𝗖𝗠 𝘄𝗶𝗹𝗹 𝗹𝗼𝗼𝗸 𝗹𝗶𝗸𝗲 𝘁𝘄𝗼 𝘆𝗲𝗮𝗿𝘀 𝗳𝗿𝗼𝗺 𝗻𝗼𝘄? RCM will no longer be a downstream, reactive function. It will be embedded directly into how care is delivered and managed. Payer requirements, risk signals, and reimbursement logic will be present by proxy throughout patient management, shaping documentation, workflows, and claims before revenue ever has a chance to break. Instead of applying payer rules after the fact, health systems will design encounters with those constraints in mind from the start. Most routine billing work will be automated end-to-end, driven by intelligence that understands payer behavior and learns continuously from outcomes. Human teams will (potentially) be smaller, more specialized, and focused on oversight, exceptions, and optimization rather than manual reconstruction and cleanup. The organizations that win won’t treat RCM as a back-office necessity. They’ll treat it as core infrastructure and a natural output of care.