Palm Beach County, Digital Client Engagement and Care Coordination SaaS Platform (26-081/BW)

Recommendation: do not bid. The contract requires Carepatron to warrant accessibility conformance it does not hold, and failure is defined as material breach. The product category is also wrong. The county wants a layer that sits across many provider organisations and integrates with their EHRs. Carepatron is the EHR for one practice.

The full RFP was read. No question to the county was needed.

The answer to the check

The check asked whether HL7 and FHIR and WCAG 2.1 AA are pass or fail, or scored, and suggested asking Bridget Williams before questions close on 29 October. The document answers both, so the question does not need to be asked.

WCAG 2.1 Level AA is neither scored nor optional. It is a contract warranty. It sits in Attachment 1, the sample standard contract, at Article 14:

CONTRACTOR represents and warrants that all websites, web-based applications, digital services, electronic documents, multimedia, and other electronic content created, developed, provided, submitted, maintained, or delivered under this Agreement that may be electronically displayed, accessed, distributed, or made available to the public by the County shall conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, or any successor standard adopted by the U.S. Department of Justice.

And the enforcement line:

Failure to comply with this subsection shall constitute a material breach of this Agreement.

The article also requires remediation at no cost on county demand, and requires that any third-party platform used either complies or has an accessible alternative the county accepts. Carepatron's position is recorded as known-gap-no-wcag-conformance: Carepatron is a modern responsive web application, but WCAG conformance has not specifically been implemented in the product. Signing Article 14 would mean warranting something that is not true today. That is the end of the analysis.

HL7 and FHIR are mandatory scope, inside the heaviest non-capability criterion. Section 4.5 opens "The platform shall provide or support the following", and 4.5.1 reads:

Integration using applicable healthcare and data interoperability standards, including HL7 and FHIR.

Section 4.5 feeds evaluation criterion 3, "Interoperability, Data, Security & Technology Readiness", weighted 30 per cent. Carepatron's position is known-gap-no-hl7-fhir: no HL7 or FHIR interfaces, no ADT feeds, no lab interfaces. Data exchange is the public API for client endpoints, file import and CSV export.

Two stated-mandatory gap frictions appear together, which the rubric treats as barring a pursue on its own, before anything else is weighed.

What the county is buying, in their own words

This is the part that makes the call easy, separately from the two gaps.

Palm Beach County Community Services Department is seeking an existing, commercially available Software-as-a-Service (SaaS) digital client engagement and care coordination platform to support County residents and service providers serving individuals with behavioral health needs, co-occurring conditions, substance use disorders, and other serious or chronic medical conditions.

The platform is not the system of record. It sits above the systems of record. Section 4.5.3 asks for "The ability to integrate with Electronic Health Record (EHR) systems and other clinical systems, where required". Section 4.5.6 asks it to "support data from multiple provider organizations while maintaining appropriate security, access controls, confidentiality, and organizational separation". Section 4.10.1 repeats that as a multi-provider environment requirement.

So the buyer already has EHRs across its funded provider network. It is buying the connective tissue between them, for county-wide oversight and evaluation. Carepatron would be one of the systems this platform integrates with, not the platform.

The remaining scope reinforces it. Risk stratification (4.6.2), social determinants of health capture (4.3.8), resource navigation (4.3.6), moderated peer support and community features (4.3.7), consent management across organisations (4.7.4), and population-level dashboards spanning provider organisations (4.4.6). None of these trace to a claim in the library.

Why this is not a Carepatron opportunity

Four reasons. The first alone is enough.

1. Article 14 cannot be signed honestly. Carepatron holds no WCAG conformance work and no VPAT. The clause is a warranty, not a scoring line, and breach is material.
2. HL7 and FHIR are named as mandatory, inside the 30 per cent criterion where we would score near zero on the central requirement.
3. The product category is different. The county buys a cross-organisation engagement and care coordination layer that integrates with EHRs. Carepatron is a single-practice EHR and practice management system.
4. The scale is wrong and open-ended. The programme is county-wide across an unbounded set of county-funded provider organisations, with explicit requirements to scale participants, users and programmes. Carepatron is priced per staff user for one practice workspace, and the rubric's sweet spot is 3 to 150 staff users.

Writing a response would mean claiming capability we do not have, which the drafting rules never allow. No draft was produced.

Submission facts, for the record

From the RFP itself. These correct the aggregator listing.

Two corrections worth noting. The contact email in the queue, [email protected], does not appear anywhere in the RFP. Section 1.10 prints team addresses instead. And a cone of silence applies from release until award, so all contact must route through the Procurement Department.

The evaluation weights are Experience and demonstrated outcomes 15, Platform capabilities and project approach 35, Interoperability, data, security and technology readiness 30, Implementation, scalability, training and support 10, Price 10. Local proposers who file a Palm Beach County Business Tax Receipt get five additional points, which Carepatron cannot earn.

Score

1. Under the 45 threshold, so this is recorded as a skip.

Coverage

No requirements were answered, because no response was drafted. Nothing in this note claims a Carepatron capability.

Two library references are used, both gaps:

• Article 14, WCAG 2.1 Level AA warranty: known-gap-no-wcag-conformance
• Section 4.5.1, HL7 and FHIR: known-gap-no-hl7-fhir

Questions for Glen: none. The two decisive requirements are both already answered in the claim library, and both answers are no.

Sources

• RFP 26-081/BW, 75 pages, downloaded from the BidScope mirror and read in full. Sections 1.2 to 1.10, 2.17, 3.4, 4.1 to 4.11, and Attachment 1 Article 14.
• The county's own Vendor Self Service portal is named in the RFP as the authoritative source for the package and any amendments.

Recommended next steps

1. Carlos: no action. Recorded as a skip in the radar.
2. Worth keeping the buyer in mind rather than the solicitation. Palm Beach County Community Services funds a provider network delivering outpatient behavioural health and substance use services. The individual funded providers in that network are the right size for Carepatron, even though the county's own platform purchase is not.
3. If Carepatron ever authors WCAG conformance work and a VPAT, this buyer and this clause are a good test of whether that unlocks US local government work. Article 14 is becoming standard in Title II entities, and it blocked Fort Bend County in August as well.