UW-Madison UHS, enterprise-wide EMR (2027-UWMSN-01430-RFP), third arrival

Recommendation: do not bid. Two new facts settle what the earlier notes left open. The question window closed on 5 October, so nobody can ask the buyer anything now. The incumbent is Point and Click Solutions, confirmed from the university's own patient portal.

This is the same solicitation as UW-Madison University Health Services, enterprise-wide EMR (2027-UWMS… and UW-Madison University Health Services, enterprise-wide EMR (duplicate…, found a third time under a third source id. Both earlier notes are now marked superseded and point here.

What the buyer is buying, in their own words

University Health Services (UHS), the student health center for UW-Madison, is requesting proposals for the purchase of an enterprise-wide electronic medical record (EMR).

The title on the aggregator mirror is fuller than the one the radar stored, and it adds a second organisation:

Enterprise-wide Electronic Medical Record (EMR) for University Health Services and Environmental and Occupational Health

So the scope is two bodies, not one. UHS covers medical care, mental health and counselling, prevention, survivor services and recovery support. EOH is occupational health for staff. The cost form carries a separate pricing section for standing up and supporting the EOH instance.

The answer to the check

The check was: open UHS_EMR_RFP_FINAL_9.23.26_(1).docx on ShopUW+ and see whether lab, eRx, SIS or HL7 are mandatory.

I could not open that file. It renders only to a logged-in JAGGAER supplier, and creating that account is your call, not mine. But the requirement set is no longer a blank. A bid aggregator, publicbidsearch.com, has run all five attachments through its own analysis and publishes the summary free. Treat the next paragraph as strong secondary evidence, not as the buyer's words.

On that analysis, these are stated as mandatory:

• WCAG 2.1 AA accessibility conformance.
• Bi-directional integration with university systems, naming Workday and PeopleSoft.
• Orders and results management, inside the core capability list.
• Separate logical instances for UHS and EOH, with full data ownership and portability.
• Cloud hosting with sub-second response times.
• HIPAA and HITECH compliance.

Against the check as asked:

eRx is the one part of the check I cannot answer, and it is the only one where we would have had a good answer.

Two further mandatory items hit gaps the check did not ask about. WCAG 2.1 AA conformance is a gap, and we hold no VPAT (known-gap-no-wcag-conformance). Sub-second response time reads as an availability commitment, and we publish no uptime figure (known-gap-no-published-uptime).

A fifth gap is visible without any document. The MyUHS patient portal authenticates with a UW-Madison NetID, which is campus single sign-on. We support neither SAML nor OIDC (sso-no-saml-scim). An enterprise-wide campus EMR that cannot accept NetID is a hard sell on its own.

The rubric caps an item at REVIEW once two mandatory gap frictions are stated. Four are.

Two new facts that decide it

The question window shut on 5 October. The event document gives proposers five business days from the 28 September issue date to raise any ambiguity or error, and the aggregator independently records questions as due 5 October 2026, 2:00 pm Central. Those agree. The RFP also forbids contacting any university employee outside the Sourcing Module, on pain of disqualification. So there is now no legitimate way to ask UW-Madison a single clarifying question. We would be answering a specification we have not read, with no right of reply.

The incumbent is Point and Click Solutions. The MyUHS portal footer says so plainly:

Powered by Point and Click Solutions

That is the buyer's own system, not an inference from a vendor list. The rubric already flags college health as incumbent-held and tells us to score winnability lower until Carepatron holds a HECVAT and a VPAT. We hold neither, and this RFP makes accessibility conformance mandatory.

Score

48, REVIEW. Down from 58, and the verdict does not move.

I have moved the number this time, where the two earlier notes held at 58. The reason is that the earlier notes had no requirement evidence of any kind. This one has a structured analysis of the real attachment set, and it points the same way on four separate counts. The score stays above 45 because the underlying document is still secondary evidence, and I will not call a hard no-bid on an AI summary of a file I have not opened.

The practical effect is the same either way. At 48 it cannot become PURSUE, and the gap count alone forbids it.

Routes I tried for the requirements document

• ShopUW+ public bid board. Served the 9-page event document as a PDF with no login, via a presigned S3 link. That is the primary source for everything in the logistics section.
• The ShopUW+ event detail page, the tokenised JAGGAER link. Returns the supplier login wall. Registering submits Carepatron's legal and tax details, so I stopped.
• The attachment store directly, without the presigned token. Returns AccessDenied.
• publicbidsearch.com. Carries the analysis quoted above free. The files themselves sit behind a $20 per month subscription, which is a purchase, so I did not take it.
• cleat.ai. Carries the metadata, states "No documents available".
• InstantMarkets, with our account. Returns a JavaScript shell with no matching record.
• Wisconsin VendorNet. No record under this solicitation number.
• Web search for a wisc.edu mirror of the docx. Nothing.

One caution for whoever picks this up next. A general web search for this solicitation returns details that belong to a different RFP, including a three-year term, a $150,000 budget and Epic interoperability via HL7 and FHIR. None of that matches the buyer's own document, which gives two years plus eight one-year renewals. I have discarded it, and so should you.

The one next action

Close it. Record the no bid and let the radar stop surfacing it.

If you would rather not, the alternative is unchanged from 30 September: open a JAGGAER Supplier Network account and read the document yourself. I would not spend the time. With the question window shut, four mandatory requirements sitting on verified gaps, no campus single sign-on and the incumbent already in the building, reading the file would most likely confirm the no bid rather than overturn it.

There is no email route. The RFP prohibits contact outside the Sourcing Module, so I have not drafted a request email. Sending one would risk a submission rather than help it.

Submission logistics, for the record

Sources

• ShopUW+ public bid board event document for 2027-UWMSN-01430-RFP, retrieved 12 October
• Buyer, dates, forms, question set, attachment list, contract extension clause.
• MyUHS patient portal, myuhs.uhs.wisc.edu, retrieved 12 October 2026. Incumbent vendor and NetID authentication.
• uhs.wisc.edu service menu, retrieved 12 October 2026. Service lines.
• publicbidsearch.com record for this solicitation, retrieved 12 October 2026. Requirement analysis across all five attachments, question deadline, contract term. Secondary.
• library/claims.json: known-gap-no-lab-integration, known-gap-no-hl7-fhir, known-gap-no-sis-integration, known-gap-no-wcag-conformance, known-gap-no-published-uptime, sso-no-saml-scim, integrations-eprescribing.
• UW-Madison University Health Services, enterprise-wide EMR (2027-UWMS… for the clinical volume table and the original logistics trail.