Basalt Raises $20M—Its 86% Speed Gain Is Still Customer

Basalt Health announced a $20 million Series A on September 24, 2026, led by NEA, and reported an 86% reduction in median chart-processing time at Lifepoint Health, from 8.5 minutes to 1.2 minutes. Frist Cressey Ventures and 25m Health also participated. The timing figure is a company-reported result from an existing customer, not a measured outcome across the hospitals Basalt plans to reach next.

A MobiHealthNews report published the following day corroborates the financing and describes plans to deploy Basalt across 62 ScionHealth hospitals and 49 additional Lifepoint markets by the end of 2026. Those are separate expansion commitments, expressed in different units. The reported Lifepoint processing result does not establish what either wider rollout will achieve.

Basalt sells software to post-acute care providers receiving referrals from hospitals. The receiving facility must review a patient’s information and decide whether it can provide the appropriate care. Basalt’s product addresses the work between a referral arriving and a clinician making that admissions decision, where finding the relevant details in a packet can take time.

An Axios Pro report dated September 23, 2026 cited Basalt chief executive Ben Hackett on the NEA-led financing before the public announcement. That account independently supports the transaction. It does not independently measure the Lifepoint result, which remains Basalt’s disclosure about a customer implementation.

The funding is intended to extend Basalt’s platform beyond admissions into discharge and payer workflows and to support hiring in sales, marketing, implementation and engineering. Existing product descriptions already include benefits checks and prior-authorization support, so the expansion is a statement about further development, not proof that every planned workflow is fully deployed. That distinction matters because handling a referral and completing a discharge or payer process involve related but different decisions.

From incoming referral to admission decision

Referrals can reach a receiving facility by fax, portal or electronic medical record connection. Basalt reads the incoming material, extracts relevant clinical and payer information, and checks it against the facility’s admission criteria. The aim is to put the findings needed for a decision in front of the admissions team without requiring staff to hunt through the entire packet first.

Basalt’s product walkthrough shows findings flagged and tied to their source in a referral, followed by clinician review and sign-off. Its illustrated patient example is explicitly synthetic; it explains the proposed workflow rather than documenting a patient outcome. The clinician still makes the final admit decision after the software has read and organized the material.

That sequence defines the software’s role. Identifying a clinical concern in a packet can help staff assess whether a facility’s services match the patient’s needs, but the finding does not resolve every operational condition of admission. Bed availability, the facility’s own criteria and any required payer authorization can still affect whether a proposed placement proceeds. A shorter chart review is therefore a narrower result than a faster transfer from the hospital.

The Lifepoint comparison concerns median chart-processing time: the middle processing time among the charts measured, rather than the time taken for every referral. It describes one part of the admissions workflow. It does not measure the full interval from a hospital sending a referral to a receiving facility accepting the patient, arranging a bed and completing a transfer.

The published figures do not specify the number of referrals measured, the observation period, the mix of cases or how much of the change is attributable to the software rather than accompanying workflow changes. They also do not show the slowest cases, which may be the most consequential for staff trying to resolve a difficult placement. Those gaps do not negate the reported result; they limit how far it can be generalized.

ScionHealth’s hospitals may receive different referral packets and apply different admission rules from Lifepoint’s teams. Even within one health system, local staffing, services and document formats can affect processing time. The disclosed comparison supports a claim about Basalt’s Lifepoint implementation, but it is not a universal speed benchmark for post-acute referrals or a forecast for the planned deployments.

Basalt describes Lifepoint as an existing customer and its additional markets as an extension of that relationship. ScionHealth’s commitment is framed as a hospital deployment. A market and a hospital are not interchangeable measures of reach, so adding those counts together would obscure the scale and status of each program.

Implementation also has steps beyond making the software available. Referrals must be routed into the platform, each facility’s criteria must be applied, and clinicians must remain part of the admission decision. The announced plans do not provide a completed-site count or a processing-time result for the additional Lifepoint markets or ScionHealth hospitals.

The financing is confirmed, and Basalt has disclosed a substantial reduction in median chart-processing time at Lifepoint. The next evidence will come from the wider deployments: which locations are live, how their results are measured, and whether faster chart review leads to faster admission decisions or patient placements. For now, those outcomes remain separate from the customer-specific figure in the announcement.