Fort Bend County, Case Management Enterprise Solution (R26-064)

Recommendation: do not bid. The county is buying a social services benefits and case management platform, not clinical documentation software. Carepatron cannot do the core of what this solicitation asks for.

The portal block from the earlier note is cleared. We now have the county's own solicitation record, so this is a decision on evidence rather than on a four word summary.

What the county is actually buying

The project description, quoted from Fort Bend County's own procurement portal:

Fort Bend County, Texas seeks Sealed Proposals from qualified firms to provide a modern, fully supported Case Management Enterprise System (CMES) to replace, consolidate, and standardize existing legacy systems and manual processes currently used by the Social Services Division. The solution shall be designed with an enterprise architecture to support future scalability and expansion to additional HHS divisions, programs, and service areas, enabling long-term standardization across present and future program needs.

The buying department is Health and Human Services. The first user is the Social Services Division. The commodity code is NIGP 95215, Case Management.

Fort Bend County Social Services runs general assistance, case management for vulnerable residents, and the County Indigent Health Care Program. Its published work is eligibility determination, which reviews a household's composition, residency, income and resources, then rent, utility, food and medication assistance. On indigent health care the county acts as the payer, not as the provider.

Why this is not a Carepatron opportunity

Four independent reasons. Any one of them would be enough.

1. The product category is different. The county wants eligibility determination, benefits issuance, means testing and multi-program administration. Carepatron has no capability in any of those. Our claim library covers clinical documentation, scheduling, telehealth, billing and client portals for people delivering care.
2. The scope is enterprise consolidation, not per-clinician software. The system has to replace several legacy systems and manual processes now, then extend across further HHS divisions and programs. Carepatron is priced and built per staff user for a single practice workspace.
3. The competing bidders confirm the category. Vendors who have already taken the documents include CaseWorthy and AssureCare, which sell human services case management and government care management, and Catalis, which sells court and land records systems. Carepatron's competitive set is SimplePractice and TherapyNotes, and it does not overlap with this list.
4. A county enterprise system brings accessibility conformance into scope. Local government in the United States must meet digital accessibility obligations under Title II of the Americans with Disabilities Act. Carepatron holds no WCAG conformance work and no VPAT, which is recorded in the claim library as a gap.

Writing a response would mean claiming capability we do not have. That is the one thing the drafting rules never allow, so no draft was produced.

Submission facts, for the record

These are from the county portal and supersede the aggregator listings.

One trap worth noting. The aggregators disagreed with the county on the closing time. Two listings said 3:00pm Eastern and 8:00pm Eastern. The portal says 2:00pm Central. Trust the portal.

What we could not read, and whether it matters

The two attached documents, the full RFP and the legal notice, need a free Euna supplier account to download. We did not create one, because registering Carepatron as a county vendor means submitting company legal and tax details, and inventing those is not acceptable.

It does not change the recommendation. The disqualifying facts come from the county's own project description, department, commodity code and bidder list, not from the attachments. If anyone wants the attachments anyway, register on the Euna portal using carepatron@agentmail.to and download from opportunity 250226.

Two reusable findings for the pipeline

1. Fort Bend County mirrors most solicitation PDFs on its own website under /sites/default/files/document-central/document-central/purchasing-documents/current-bids-rfps-rfqs-quotes/, named after the solicitation, for example R26-014.-Dispatching-and-Scheduling-Software.pdf. R26-064 is not there yet, but the pattern is worth trying before treating a Bonfire opportunity as locked.
2. JavaScript portals that defeat server side fetching are often mirrored by smaller aggregators that do render. techbids.com and instantmarkets.com both carried the department name for this solicitation, which was the fact the earlier attempt was missing. Both were reachable through Firecrawl.

Coverage

No requirements were answered, because no response was drafted. Nothing in this note claims a Carepatron capability, so nothing here needs a claim library trace.

The one library reference is the WCAG and VPAT gap, recorded as a known gap and cited in reason 4 above.

Questions for Glen: none. This is a category mismatch rather than a product question.

Recommended next steps

1. Mark R26-064 as skipped in the radar. Done as part of this assessment.
2. Leave the county on the watch list. Fort Bend bought an electronic patient care reporting system for emergency medical services in November 2025 under R26-021, so the county does buy clinical software. A future behavioural health or clinic system RFP from the same buyer would be worth reading.
3. No action before 15 September. There is nothing here to bid on.