Weber Human Services, AI-Assisted Clinical Note Writing System (09-14-2026)

Recommendation: do not bid. No action needed from you. This is the same solicitation you already decided on 21 September, reaching the radar a second time through a different aggregator. See [[2026-09-21-weber-human-services]].

The radar scored it fresh at 63 because it arrived as a new record. It is not new. Buyer, reference number, close date and scoring table all match.

Both now carry a SKIP verdict, so neither should resurface.

The decision has not changed

Weber Human Services is keeping its EHR and buying a scribe to sit on top of it. The scoring table is explicit about the criterion worth 15 per cent:

EHR Integration & Technical Fit 15% Ability to integrate with WHS's existing EHR and workflow, including API/interface capabilities and implementation requirements.

Carepatron's AI Scribe writes into Carepatron. It drafts a structured note against the client record and the appointment (ai-scribe-ambient-transcription), including for in-person sessions captured on the mobile app (ai-scribe-in-person-mobile-capture) and for sessions held on a non-Carepatron video platform (telehealth-third-party-platforms). In every one of those paths the finished note lands in Carepatron.

There is no supported route out. The public API covers client endpoints only, with appointments, documentation and billing endpoints outside the present scope (known-gap-api-client-endpoints-only). There are no HL7 or FHIR interfaces (known-gap-no-hl7-fhir). Nothing in the library says the Scribe can be licensed on its own, and I have not assumed it.

Bidding would mean answering a scribe procurement with an EHR replacement.

What reading the document added

The 21 September assessment was made from the public opportunity page, because the attachment needed a Euna login. I have now read the attachment itself, retrieved from the mirror on the Bidscope listing rather than through the portal.

It changes nothing about the recommendation. The five-page "Solicitation Document" is a Bonfire Solicitation Builder form containing the project details, the submission instruction and the same six-criterion scoring table already on the public page. Its one numbered section, "1. Untitled Section", is empty. There is no requirement list, no technical specification and no mandatory forms schedule. The scoring table is the whole solicitation.

Two facts on the record do need correcting.

unanswered. WHS has since answered it. Public question #8, lodged 24 September, asks which roles are "included in the 100 clinicians (e.g., individual therapy, group, family, SUD, case management, crisis, prescribers/med management)". The figure comes from a bidder restating an answer WHS gave, so treat it as the buyer's number rather than a published one. It sits inside the 3 to 150 band.

required a Euna Supplier Network account Carepatron does not hold. That was wrong. The solicitation document says "Submit bid to [email protected]", and public question #1 records that "there is no option to submit a response on this record". Bids go by email. The Euna login is needed only to post a public question or download the attachment through the portal.

The score

49 out of 100, up from 43. The whole increase is feasibility, now that email submission is confirmed, plus size fit now that the clinician count is known. Product fit is the binding constraint and it has not moved.

Even scoring 5 on all four criteria Carepatron is strong at, and 1 on EHR integration, the bid would be arguing against the question the buyer asked.

What would change the call

The buyer is right and the product is wrong. Weber Human Services is the local authority for mental health, substance use, prevention and ageing services across two counties. If WHS posts an EHR replacement rather than a scribe bolt-on, it should score well and is worth chasing. That is the thing to watch for, not this RFB.

One note for the radar

The two listings were not deduplicated, so the same solicitation consumed a drafting slot twice. The underlying issue is already staged as a memory proposal, rfp-radar-duplicate-across-sources-not-deduped.

Separately: the Bidscope listing renders a "Comments", "Correspondences" and "Custom Fields" block containing a bid owner, a go or no-go decision, a bonding requirement and the line "Incumbent is up for recompete. Price to win is roughly $420k." None of that belongs to this solicitation. It is Bidscope's own sample interface, and the correspondence thread in it is about a roof replacement addendum. It should not be read as buyer information.