THE SIGNAL

The 2024 Section 1557 final rule from the U.S. Department of Health and Human Services added 45 CFR 92.210. It says a covered entity "must not discriminate on the basis of race, color, national origin, sex, age, or disability in its health programs or activities through the use of patient care decision support tools." The rule defines those tools broadly: "any automated or non-automated tool, mechanism, method, technology, or combination thereof used by a covered entity to support clinical decision-making."

Two duties follow. A covered entity has "an ongoing duty to make reasonable efforts to identify" tools that use input variables measuring race, color, national origin, sex, age, or disability. For each tool it identifies, it "must make reasonable efforts to mitigate the risk of discrimination." The compliance date for both duties was 300 days after July 5, 2024, which was May 1, 2025.

On June 1, 2026, after a federal court vacated parts of the rule, HHS said its Office for Civil Rights "will continue to enforce the Rule's protections against discrimination based on race, color, national origin, age, disability, and aspects of sex discrimination not impacted by the court's order."

BEFORE

Hypothetical: a community hospital's clinical informatics team updates its inventory of decision support tools. One entry is an inpatient deterioration score that uses age as an input. The team drafts a mitigation plan: check the score's alert performance by age group each quarter, and give nurses written guidance on when to escalate despite a low score.

The plan needs sign-off from the chief medical officer, and it sits on the agenda of the quarterly clinical decision support committee, seven weeks out.

The file is ready. The person who can release it is not.

WHAT THE WAIT COSTS

The score runs unchanged for another quarter, and the reasonable efforts the rule asks for exist only as a draft. Meanwhile a vendor update adds new inputs and joins the same queue, so the inventory is stale the day it is approved.

AFTER

Every flagged tool in the inventory has a named owner and a named approver. The mitigation plan arrives as one decision packet: the tool's input variables, the developer's documentation, local performance by group, the proposed monitoring and the clinical guidance.

The chief medical officer approves it with one change that week. The decision and the reasoning are recorded against the tool, which is the record you want when someone asks what your reasonable efforts looked like.

HOW WISDOMTWIN FITS

WisdomTwin.ai is building a Judgment Platform for regulated enterprises. It is designed to give each named approver a role-specific judgment twin that prepares the decision packet the way that person reviews, with the evidence attached, so the decision moves faster and leaves an auditable record. It is designed to run on-premises or in your private cloud, and the named person still makes the call.

We don't replace judgment. We remove the wait.

TRY THIS THIS WEEK

  • Pull your decision support tool inventory and count the tools flagged under 92.210(b).

  • For each flagged tool, write down the mitigation status and the person who approves it.

  • Note how long the oldest open mitigation plan has been waiting for that approval.

SOURCES

Examples in this issue are hypothetical, and nothing here describes a customer result.

Roman Bodnarchuk

Co-Founder and CEO, WisdomTwin.ai