NYC Local Law 144 · for Clinical AI evidence workflow

NYC Local Law 144 evidence for clinical AI workflows.

For clinical committees and health system AI governance: use the self-serve API to gate the workflow and link the NYC Local Law 144 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 NYC Local Law 144 lands in the record.
Named control

NYC Local Law 144 in ATTESTATION.json

Every artifact your clinical AI workflow emits is hashed and named; the NYC Local Law 144 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.

See the Clinical AI evidence workflow path in the Console.

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

API ·

When NYC Local Law 144 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.

See how a record is checked