Stedi

716 posts

Stedi banner
Stedi

Stedi

@stedi

The only programmable healthcare clearinghouse | https://t.co/EIG41pbRBm

Distributed Katılım Aralık 2016
0 Takip Edilen1.9K Takipçiler
Stedi
Stedi@stedi·
We've finalized the lineup for our first Stedi Platform Partner Demo Day on Jun 2 at 3pm ET/12pm PT. These Stedi Platform Partners and others will demo what they've built: - Cair Health – AI agents for scheduling and denials - Substrate AI – Real-time claim status agent - Tennr – Referral management - Veribrance (formerly Aarogram) – Patient cost estimates Each demo runs five minutes, followed by a short Q&A. You can register to watch at the link below. The event is free.
Stedi tweet media
English
1
0
1
56
Stedi
Stedi@stedi·
We now have a claim edit for negative service unit counts. In a claim, a service line represents billing for a specific service, such as an office visit, lab test, or therapy session. A service unit count is the number of units for a service line. The meaning of a unit depends on the procedure code. For example, four units of a 15-minute therapy code equal one hour. X12 standards require these counts to be zero or higher. Submit a claim with a negative count and the payer rejects it. That slows down payment for the provider. This claim edit catches the issue before the claim leaves Stedi. More details in the changelog. Link below.
Stedi tweet media
English
1
0
2
72
Stedi
Stedi@stedi·
Stedi now supports CMS-1500 Claim Form PDF downloads directly from the claims view in the Stedi portal. The CMS-1500 Health Insurance Claim Form, also called the HCFA, is the standard paper form for professional medical claims. You can auto-generate a PDF that mirrors the CMS-1500 form's layout for any claim submitted through Stedi. Previously, these PDFs were only available through our API or from each claim's transaction details page in the Stedi portal. Teams use CMS-1500 PDFs for record keeping, mailing claims to payers, or reviewing claim information in a familiar format. More details in the changelog. Link below.
Stedi tweet media
English
1
0
2
72
Stedi
Stedi@stedi·
Stedi now has a claim edit for invalid state and province codes. X12 standards require US addresses in claims to use the USPS two-letter state abbreviation, like 'FL' for Florida. Canadian addresses in claims must use the Canada Post province or territory symbol, like 'ON' for Ontario. Submit a claim with the wrong state or province code format, and the payer may reject the claim. That ultimately delays payment for the provider. This claim edit catches the issue before the claim ever reaches the payer. More details in the changelog. Link in the replies.
Stedi tweet media
English
1
0
1
64
Stedi
Stedi@stedi·
Healthcare voice AI agents fall into three categories: inbound, outbound, and ambient. If you're building an inbound or outbound voice agent, Stedi's APIs can replace or supplement most phone calls with standard healthcare transactions. These transactions are faster, cheaper, and more reliable than relying on voice alone. Our latest guide covers the different types of voice agents and where Stedi fits in.
Stedi tweet media
English
1
0
2
62
Stedi
Stedi@stedi·
You can now view Electronic Remittance Advice (ERAs) in the Stedi portal's claims view. Features include: - A filterable list of all ERAs received through Stedi. - A detail page for each ERA showing payer and payee info, payment date and method, total paid, and claim-level adjustments. - A click-through from a claim's timeline to any ERAs that match its Patient Control Number (PCN). - Download options for the full ERA PDF, per-claim PDFs, or the PDF for a single claim. More details are in our announcement blog. Link in the replies.
English
1
0
2
73
Stedi retweetledi
Nikhil Krishnan
Nikhil Krishnan@nikillinit·
if you're trying to see whether a service is covered, you need to do an eligibility check with the insurance company. This is typically done through something called a 270/271 response. A lot of people don't know what data is actually included in that transaction + make some common mistakes We put together a report with @stedi to answer those questions
Nikhil Krishnan tweet media
English
1
1
3
875
Stedi
Stedi@stedi·
Stedi now has a claim edit for phone numbers with invalid area or exchange codes. For 10-digit North American phone numbers, the area code is the first 3 digits. The exchange code is the next 3. To be a valid phone number, neither the area code nor exchange code can begin with '0' or '1'. If you submit a claim that contains a phone number with an invalid area or exchange code, the payer may reject the claim. This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider. More details in our changelog. Link in the replies.
Stedi tweet media
English
1
0
3
70
Stedi
Stedi@stedi·
You can now include information for a patient's secondary or tertiary insurance plan in professional claims submitted using the Stedi portal's CMS-1500 claim form. Coordination of benefits (COB) is how payers divide responsibility for payment when a patient is covered by more than one insurance plan, such as a child covered under both parents' health plans. In a COB scenario, the primary payer processes the claim first, then passes any remaining balance to the secondary payer, and so on. The information in the Other Insured's Information section lets the primary payer see the patient's other plans so payment can be coordinated downstream. For more info, check out our changelog. Link below.
Stedi tweet media
English
1
0
3
75
Stedi
Stedi@stedi·
When you need insurance information, making a phone call to the payer seems like an easy win. The catch is that calls are slow and labor-intensive, which makes them expensive. Most of what you pay for is hold time. At any real volume, the math stops working. Stedi's APIs replace most payer phone calls with standard healthcare transactions. In most cases, you get the same information as a call in a few seconds, for pennies each. Our latest guide walks through the most common questions providers ask payers and how Stedi answers each. Link in the replies.
Stedi tweet media
English
1
0
2
74
Stedi retweetledi
Nikhil Krishnan
Nikhil Krishnan@nikillinit·
Excited to launch something we've been working on...the "must know" guide to eligibility checks! We worked with @stedi to go through eligibility checks that come back from 1200+ payers to understand trends - What is in and not in the eligibility check? - What are common mistakes people make when submitting an eligibility check that leads to errors? - What are some interesting ways AI agents are being used to help with eligibility checks? And obvi some good memes to get you through it, you can see the full report in the next tweet
Nikhil Krishnan tweet media
English
1
2
13
1.4K