Section 504 · for Clinical AI evidence workflow

Section 504 evidence for clinical AI workflows.

Open the Console Open the Medicine brief

For clinical committees and health system AI governance: use the self-serve API to gate the workflow and link the Section 504 requirement to the evidence record for the clinical AI workflow under review.

HHS §1557 · HIPAA · FDA PCCP
01 ·

What you get.

Three things a medicine program office gets when Section 504 lands in the record.
Named control

Section 504 in ATTESTATION.json

Every artifact your clinical AI workflow emits is hashed and named; the Section 504 control reference sits next to the hash.

Sector framing

Medicine anchors named alongside

The evidence record names HHS §1557 · HIPAA · FDA PCCP together. Internal or external medicine compliance sees the regime they care about, not a generic list.

Reproducible

Bit-exact on your hardware

The measurement engine runs in-enclave. Medicine evidence rules can permit recompute on customer infrastructure; the record supports that review property by construction.

02 ·

Related coverage.

Other Planisphere surfaces for this combination.

Section 504 reference · Open the Section 504 reference · Section 504 capability brief · Medicine vertical landing

Every medicine-shaped landing for the corpus lives under register 09.

See the Clinical AI evidence workflow path in the Console.

Open the Console to see sealed records; the Docs carry the endpoints.

Open the Console Section 504 reference Medicine vertical
API ·

When Section 504 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