Procurement Language That Actually Works in Healthcare

Your organization mostly buys rather than builds. The signature moment is the only leverage you get.

The patient portal, the EHR's patient-facing modules, the telehealth platform — almost none of your digital surface was built in-house, and every piece of it is a vendor contract that's going to renew eventually. That renewal is a chance to fix the problem permanently instead of patching it forever, and it only happens once per contract: the moment of signature. A clause costs nothing to ask for before that moment. After it, you're negotiating from nothing.

Here are the five clauses that do the actual work.

The standards representation

The product, as configured for your organization — not the vendor's marketing site, not the demo — meets WCAG 2.1 AA (opens in new window) or later, warranted, with a current conformance report per interface. Push specifically for the patient-facing modules to be named, not just "the platform" generally. A vendor's beautiful accessibility statement about their product overall means very little if the specific modules your patients actually touch were never tested.

The remediation commitment

Defects get fixed at the vendor's expense, on a stated timeline by severity, and that commitment survives future upgrades — otherwise you'll fix something, the vendor pushes an update, and you're paying for a change order instead of enforcing a warranty.

Acceptance testing

Test the final, actually-configured deliverable before sign-off — not a sales demo, not a generic sandbox. The instance your patients will actually use.

Remedies with actual teeth

Cure period, cost deduction, non-renewal, termination, and indemnification if the vendor misrepresented what they sold you. A clause with no consequence attached is marketing copy with a signature block.

The silence default

One sentence, borrowed from Texas administrative code: if a vendor can't produce credible accessibility documentation, the product is treated as non-conforming. It turns "we'll get back to you on that" from a shrug into a finding.

None of this is legal advice — bring these concepts to your counsel before anything goes into a contract, and let them draft the actual language for your specific deal.

The renewal calendar, and where to start it

Clauses only fire at signature, so the second artifact you need is a calendar: every digital contract, its renewal date, its notice window, and whether it already carries these terms. Ninety days before each renewal, the vendor gets the accessibility documentation request and the clause language together, before the renewal conversation starts.

Start with three vendors, in this order: your patient portal, the patient-facing modules of your EHR, and your telehealth platform. Request their Accessibility Conformance Reports (opens in new window) now, at your next quarterly business review, regardless of where you are in the contract cycle — the next piece in this series covers how to actually read what comes back.

If you want a second opinion on a report before you bring it to your compliance committee, ask Luke to check it against what the vendor actually promised. Our methodology covers how we verify claims like these.

Previous: document inventory and triage · Next: how to read a VPAT

---

Sources: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · How to Create an ACR Using a VPAT (opens in new window) · HHS Guidance on Section 1557 (opens in new window)