ABA Formal Op. 512 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 ABA Formal Op. 512 requirement to the evidence record for the clinical AI workflow under review.
What you get.
ABA Formal Op. 512 in ATTESTATION.json
Every artifact your clinical AI workflow emits is hashed and named; the ABA Formal Op. 512 control reference sits next to the hash.
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.
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.
Related coverage.
ABA Formal Op. 512 reference · Open the ABA Formal Op. 512 reference · ABA Formal Op. 512 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.