Stedi @stedi

More details in the changelog: stedi.com/changelog/intr…

You can now look up a payer ID by uploading a photo of an insurance member ID card to the Stedi Agent. Eligibility checks – and other healthcare billing transactions – fail if you use the wrong payer ID, even if you provide the right patient data. Many member ID cards don't list the payer ID, so matching a card to the right payer previously required a manual search. If your workflow starts with a physical or digital insurance card, you can now get the payer ID without searching Stedi's payer list. It's as simple as dragging and dropping in a photo of the card. There are more details in our changelog. Link below.

@ay_o You can watch the full episode here: youtube.com/watch?v=TQ3qvy… Subscribe to the podcast: - YouTube: youtube.com/playlist?list=… - Spotify: open.spotify.com/show/6cyz5JaAo… - Apple Podcasts: podcasts.apple.com/podcast/unders… - RSS feed: feeds.transistor.fm/understanding-…

We just released a new episode of our Understanding Healthcare podcast. This time Zack, our CEO, chatted with @ay_o, co-founder and CEO of Substrate AI, about using AI agents to automate the revenue cycle. Before Substrate, Ayo ran product at Carbon Health, an urgent care provider. He joined in early 2020, right as COVID hit. Over the next year and a half, Carbon grew from a handful of clinics to 150+ and ran one of the largest vaccination programs in California. Ayo repeatedly saw how difficult revenue collection was for providers, and that ultimately led him to create Substrate. In this clip, Ayo explains why he thinks getting paid in healthcare is so hard: payers are incentivized not to pay providers. Later in the conversation, Zack and Ayo talk about payer anti-patterns, why they both think healthcare billing could be 5x faster and cheaper, and what they'd change about the revenue cycle.

Read the changelog: stedi.com/changelog/in-a…

You can now get in-app notifications right in the Stedi portal. The new notifications cover things like enrollment status changes, event destination delivery failures, and account invitations and requests. Previously, Stedi only sent these notifications through email. Now, you can see them as soon as you log in. To learn more, check out our changelog (linked below) – or just sign in to your Stedi account. A bell in the nav bar shows your unread notifications.

Read the changelog: stedi.com/changelog/clai…

Stedi now has a claim edit for provider taxonomy codes that aren't in the NUCC code set. A taxonomy code identifies a provider's classification and specialization, such as cardiology or orthodontics. The National Uniform Claim Committee (NUCC) maintains and publishes the list of valid codes. If a claim includes a taxonomy code that isn't on the NUCC list, the payer may reject it. Payer rejections are slow to resolve and often delay payment for the provider. Our new claim edit catches the issue before the claim reaches the payer. If you're using our API, the error comes back in real time. If you're using SFTP, Stedi rejects the claim directly instead of the payer. Either way, billers can fix the code and resubmit right away. More details in the changelog. Link below.

Read the guide: stedi.com/blog/claims-an…

Medicare's new ACCESS Model launched July 5, 2026. ACCESS is an alternative payment model for tech-enabled chronic care. With ACCESS, patients with chronic conditions like high blood pressure or depression can get care through apps, devices, and telehealth, covered by Medicare. Many providers and billers have asked us how eligibility and billing work with ACCESS. Our latest blog post answers those questions, including whether an eligibility check can confirm ACCESS eligibility and which procedure codes you use for ACCESS claims. Link below.

You can read the full case study on our site: stedi.com/customers/vinta Watch Vinta's demo from Vinta's Health Builders Jam: youtube.com/watch?v=fL8fSW…

@vintasoftware is a development shop for healthcare providers and health tech teams. They've built everything from patient-facing apps to custom EHRs and EMRs – for everyone from digital health startups to the United Nations. One problematic workflow kept coming up across their projects: patient intake. When someone sees a new provider, they often have to fill out forms first: contact details, medical history, insurance, and consent. That's patient intake. Even when digitized, those forms are often a source of errors. A misspelled name or a transposed digit in a member ID is all it takes. The mistakes only surface in a failed eligibility check or – worse – weeks later, in a denied claim. To fix it, Vinta built a paperless intake flow they can reuse across clients. Patients import their records through a SMART Health Link, a shareable package of their health history, then review and correct them. Because the data is imported rather than re-typed, providers can run the eligibility check – in real time – on trusted data. Vinta powers those checks with @stedi 's Real-Time Eligibility API. "Instead of rebuilding intake for every client, we start from a validated flow and customize only what's unique to their care. Stedi handles eligibility, so we're not building clearinghouse plumbing on every project," says Lais Varejão, Vinta's CPO. Full case study and Vinta's demo video are linked below.

Read the guide: stedi.com/blog/quick-sta…

Many billing teams check a claim's status by calling the payer or logging into a payer portal. Both methods take minutes per claim and often require extra staff. Neither scales across payers. In contrast, a real-time claim status (RTCS) check returns results in seconds, costs pennies per check, and is designed to run at scale. Claim status checks are standardized. Every payer uses the same request and response format, which makes them easier to automate. If you're building an AI agent or automated workflow, our latest guide covers the basics in under 15 minutes: what claim status checks are, when to use them, how to run them, and how to handle common responses. Link below.

Read the guide: stedi.com/blog/managing-…

Switching to Stedi from another clearinghouse won't affect your transaction enrollments for most transaction types. You can run eligibility checks, claim submissions, and claim status checks through several clearinghouses at once. Most payers don't require enrollment for these transactions. The ones that do usually let you enroll through multiple clearinghouses. ERAs are the exception. Every payer requires enrollment for them. And each one routes your ERAs to a single clearinghouse at a time. When you enroll for ERAs through Stedi, the payer stops sending them to your old clearinghouse. That sounds risky, but there's no gap: the payer keeps sending to the old clearinghouse until the switch goes live. Nothing locks you in either. You can always move your ERAs back later. Our latest guide covers which enrollments are exclusive, which aren't, and how to manage them across clearinghouses. Link below.

You can read the full changelog here: stedi.com/changelog/intr…

You can now see how many claims or ERAs match your filters in the Stedi portal. Before, you could filter the claims and ERA lists but couldn't tell how many records matched. Now a result count appears as soon as you apply a filter. You can see how many claims from last week are still rejected, or how many ERAs Aetna sent you last month. More details in the changelog. Link below.

The My Payers view is free on all production accounts. More details in the changelog: stedi.com/changelog/intr…

You can now see every payer you've sent claims to or received ERAs from through Stedi in one place: the My Payers view in the Stedi portal. Before, finding which payers you'd worked with meant combing through your claims and ERAs lists separately. Now they're in a single, filterable list. Each payer row links to its profile in the Stedi Payer Network, its claims, its ERAs, and its enrollments. More details in the changelog. Link below.