Open the Console Prepare evidence for clinical AI review

Is the HHS §1557 patient-care-decision-support-tools rule still in effect in 2026?

The 2024 §1557 rule includes a provision (effective 2025) barring discrimination through patient-care decision-support tools, requiring covered entities to make reasonable efforts to identify and mitigate discrimination risk from such tools — and that…

register 09 · Compliance pins· HHS §1557
01 ·

Answer.

Healthcare regulation · HHS §1557.

The 2024 §1557 rule includes a provision (effective 2025) barring discrimination through patient-care decision-support tools, requiring covered entities to make reasonable efforts to identify and mitigate discrimination risk from such tools — and that provision is the operative one for AI. Parts of the broader rule have faced litigation, so confirm current status for your situation, but the decision-support-tool nondiscrimination duty is what governs clinical AI. Planisphere supplies cohort-comparison evidence to support the mitigation effort; it does not provide legal advice on the rule's status.

02 ·

The mark behind the answer.

HHS §1557 can require evidence around clinical workflows, ePHI boundaries, change control, or patient-impacting decision…

ACA non-discrimination in patient-care AI.

→ Full reference for HHS §1557

03 ·

More on HHS §1557.

Other questions this mark answers.
How do I audit a clinical algorithm for §1557 nondiscrimination? What's the difference between §1557's algorithm provision and its gender-identity provisions?

Try HHS §1557 with a free test key.

Start with the free sandbox. Planisphere measures model behaviour and emits a reproducible, sha-pinned record — it does not certify, file, or give legal advice.

Open the Console Prepare evidence for clinical AI review HHS §1557 reference
API ·

When HHS §1557 asks for proof, hand over records — not assurances.

record the duty · seal the receipt · verify offline

Planisphere records each duty event — an output marked, a disclosure shown, a review made — and seals it into a receipt that verifies offline against our published keys. You send hashes, never content. A record is evidence a third party can check; it is not a certification and not a legal determination.

Open the Console Read the Docs Read the capability briefing

See how a record is checked