A health plan offers its members a ride to the doctor. Good benefit, real need. Then the actuary asks the question that matters now: did it improve anyone’s health, and can we show it? And the honest answer, for most plans, is that the data to answer it does not exist in one place. The rides happened. The proof did not get captured.
That gap used to be tolerable. It is not anymore. The rules have shifted from offering a benefit to evidencing it, and the plans that cannot connect a ride to an outcome are the ones who will struggle to justify the benefit at all.
I am the CMTO at Mindbowser, and the work I care about most is where clinical outcomes meet the systems that have to capture them. Transportation is one of the cleanest examples right now: a benefit that obviously helps, that plans increasingly have to defend with data, and where the software most plans run was never built to produce that data. This is a walk through what the rules now require, why it is a software problem, and what a plan-side build actually has to do.
The transportation benefit plans offer, and the gap underneath it
Start with where the benefit stands, because it is moving. In 2026, a medical transportation benefit was available to 22% of individual Medicare Advantage enrollees, down from 28% in 2025, and to 73% of SNP enrollees, per KFF’s June 2026 analysis. Non-medical transportation, offered as a Special Supplemental Benefit for the Chronically Ill, sat at 5% of individual plans and 36% of SNPs.
Two things stand out in those numbers. The benefit is widespread, especially in the SNP world where the membership is sickest and the need for reliable transportation to care is highest. And on the individual side it is contracting, which is what happens when plans cannot defend a benefit’s cost with evidence of its value. A benefit you cannot measure is a benefit you cut when margins tighten.
The gap underneath the benefit is the data. A plan knows it paid for rides. What it usually cannot show is which members used them, whether those members made their appointments, and whether the benefit changed anything about their care or their cost. That is not a reporting inconvenience. Under the current rules, it is an existential question for the benefit.
What CMS now requires you to prove
The CY2025 Medicare Advantage final rule, CMS-4205-F, with provisions taking effect into 2026, changed the standard for supplemental benefits. Two requirements matter most for transportation.
First, the evidence standard. For Special Supplemental Benefits for the Chronically Ill, a plan must maintain a bibliography of high-quality clinical research, published within ten years of the coverage year, showing the benefit has a reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollees who receive it. You can read the framing in the CMS-4205-F fact sheet. In plain terms, offering a transportation benefit on the belief that it helps is no longer enough. You have to be able to point to the evidence, and increasingly to your own.
Second, the mid-year notice. Beginning January 1, 2026, plans must send each enrollee with unused supplemental benefits a mid-year notification, no sooner than June 30 and no later than July 31, listing the benefits they have not used. For a transportation benefit, that means you have to know, member by member, mid-year, who has and has not used their rides. That is a live utilization-tracking requirement, not an annual report you assemble after the fact.
Put the two together and the message is clear. You must evidence that the benefit works, and you must track its use closely enough to nudge members who are leaving it on the table. Both are data capabilities, and most plans do not have them wired together.
Why this is a software problem, not a policy memo
It is tempting to treat the new requirements as a compliance task, something the regulatory team handles with a binder. But the binder cannot answer the actuary’s question, and it cannot generate the mid-year notice. The requirements decompose into four data capabilities, and every one of them is software.
You need eligibility logic that knows which members qualify for the benefit and under what rules, because SSBCI eligibility is narrower than the general membership. You need utilization tracking that sees each ride as it happens, not in a quarterly broker file, so the mid-year unused-benefit notice is accurate. You need outcome and encounter capture that connects a ride to what it enabled, the appointment kept, the gap in care closed, so the benefit can be tied to a measurable result. And you need member engagement, the reminders and the booking experience, that turns an offered benefit into a used one.
None of those is a transportation feature. They are health-plan data features, and they have to share a spine. The reason this lands as a custom build for serious plans is that the off-the-shelf tools own pieces of it, the broker owns the rides, the benefit-admin system owns eligibility, the analytics team owns outcomes, and nothing connects them into the single thread that proves the benefit worked. The same outcome-capture discipline that runs quality tracking under value-based care is exactly what a transportation benefit now needs, applied to rides.
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.
