Illuminate Rx cut prior authorizations as employers question benefits complexity

A pharmacy executive’s reported reduction sharpened a broader debate over whether benefit design helps people obtain care or asks them to become experts in the system.

Author
HDM Staff
Save
Share
Five participants discuss employer benefit design on the Velocity Stage
The Redesigning the Benefits Blueprint panel examines plan design and employee access on November 17. Photo credit: HLTH USA 2026

    Illuminate Rx removed 20% of its prior authorizations, president Dr. Ritu Malhotra said, arguing that routinely approving a request can be a reason to question the requirement itself. Her account put a concrete operational change behind a broader challenge from employer benefits leaders: health plans should become easier to use while buyers become more demanding about prices and vendor incentives.

    “We took out 20% of prior authorizations,” Malhotra said, asking what a process achieves when approval rates are already extremely high. She described more targeted clinical management, particularly for nonspecialty drugs, rather than indiscriminate barriers. The figure was company-reported; the session did not provide an independent evaluation of the change’s financial or clinical effects.

    Malhotra joined Ali Diab, CEO and co-founder of Collective Health; Nathan Counts, Amtrak’s vice president of total rewards; and Noora Garnett, HelloFresh’s global director of benefits and retirement, for Redesigning the Benefits Blueprint on November 17. Susan Nash, partner and co-chair of health and welfare benefits at Winston Taylor, moderated, connecting plan design with contracting, transparency and the responsibilities of employers purchasing care.

    A clinical program should do more than delay a prescription

    Malhotra, a pharmacist who described a career advising plan sponsors, said pass-through pricing increases the importance of competing on administrative fees and clinical programs. In her account, prior authorization should identify potentially inappropriate treatment or an alternative worth discussing with a prescriber. Its purpose should not be to make a patient wait without knowing what is happening.

    Her argument linked affordability with clinical operations. A less costly alternative can matter to a patient’s ability to continue treatment, but the discussion belongs with the prescriber and must account for the therapy needed. She described a more selective process rather than a claim that every authorization can safely disappear.

    “Transparency is a tool. It's not the outcome,” Malhotra said. She wanted disclosures that buyers could interpret, use to understand who earns money and compare with the way claims actually process. Providing a file, in that framework, is an intermediate step toward a different purchasing or clinical decision.

    She also warned against adding complexity as new pricing arrangements, direct offers and copay programs proliferate. Employers may be able to examine contracts, but a patient facing a prescription cannot be expected to reconstruct the commercial relationships behind it. Her operational test was whether the system makes a needed treatment easier to obtain.

    Free care does not automatically produce engagement

    “We focus a lot on prevention and access to care,” Garnett said of HelloFresh’s approach, including screening support, a free medical plan and free virtual care. She described a specialty cancer partner’s work making screening more visible and approachable. Her examples placed value in helping employees reach care before a problem becomes harder to address.

    Counts questioned whether removing the price alone reliably gets people to use a curated service. “Employers are realizing maybe free isn't enough,” he said. He described employers considering alternative plan designs and stronger incentives because the utilization they expected from free offerings had not necessarily materialized.

    That was a distinction between a benefit’s availability and its use. A company can pay for an offering, remove an employee charge and still find that people do not know how or when to engage. The panel’s debate suggested that the next design question is what work remains for the employee after the financial barrier has been lowered.

    Garnett argued that the burden itself deserves attention. “I feel like it should be my full time job to try to make it easy,” she said, describing how much expertise the system can require from people whose jobs are elsewhere. She proposed considering guided options while preserving more open access for employees who want to do the research themselves.

    More data still needs someone to make it usable

    Nash asked the employer representatives whether they could obtain the information needed to analyze their plans. Counts acknowledged access problems, but also questioned the assumption that simply receiving more data would solve the problem. Employers depend on partners who can turn complex information into something useful for the benefits team and its members.

    Counts’s closing warning was that “the status quo is disruptive,” because incremental changes would not resolve the pressures employers face. His response connected the need for usable information with a willingness to reconsider established designs, rather than assuming that keeping an existing arrangement is always the less disruptive choice.

    Garnett saw potential for AI to combine pricing information with population health history and improve forecasting. She described that as a hope for better tools, not an established result from a deployed system. The distinction kept the discussion focused on the work the technology would have to perform before it could guide investment.

    Diab framed Collective Health’s purpose as giving employers tools to purchase care intelligently. He criticized arrangements that require buyers to reconstruct costs after the fact and argued for addressing pricing problems further upstream. The broader policy proposals were his position, rather than an announcement that a new pricing system had been adopted.

    Follow the vendor’s revenue as well as its fee

    “Challenge all of your vendors and suppliers and understand how they make money,” Diab said. He argued that a quoted administrative fee may not capture the other ways an organization earns revenue through contracting or related services. His closing recommendation was to ask whether the vendor can explain those incentives clearly.

    He contrasted that with Collective Health’s fixed per-employee fee model. “Our job is to faithfully administer the plan the way that the plan sponsor wants it administered,” Diab said. That was the company’s stated rationale for sitting outside incentives tied to more or less care, not independent proof that any fee structure eliminates every conflict.

    The same scrutiny applied to care navigation and primary care. Garnett described the communication advantages of a primary-care-led model, while Counts emphasized employers’ immediate pressure to address unit costs. Diab distinguished independent or onsite primary care from arrangements connected to a broader referral system. They were examining the incentives behind the service, not treating every primary care offering as interchangeable.

    The panel’s most useful design principle connected those purchasing questions with Malhotra’s authorization example. Employers need to know what a vendor is paid to do, whether the work changes care and how much effort it leaves with the employee. A simpler experience requires more deliberate decisions by the purchaser, including removing a process when its routine approvals no longer justify the burden.