Medicine · California AI Transparency

California AI Transparency for clinical AI workflows

California AI Transparency in clinical AI workflows: what compliance requires, who asks for evidence, and the records to keep.

Start free Open the Console

Legal forceBinding law

Applies from2 Aug 2026

SectorMedicine

Checked21 Oct 2026

01 / The rule

What California AI Transparency requires

Covered providers: anyone who creates, codes or produces a generative AI system publicly accessible in California with over 1,000,000 monthly visitors or users, plus their licensees.

01Embed a latent disclosure in covered content: provider name, system name and version, creation or alteration time, and a unique identifier.
02Make the latent disclosure detectable by the provider's own tool, consistent with industry standards, and permanent or extremely difficult to remove.
03Offer users the option of a clear, conspicuous manifest disclosure appropriate to the medium.
04Provide a free, publicly accessible detection tool with upload or URL input and an API, without outputting personal provenance data.
05Revoke a licence within 96 hours of discovering a licensee modified the system so it no longer applies the disclosures.

02 / In this sector

In a clinical AI workflow

Written specifically for generative AI systems; the duties attach to content those systems create or alter. The one-million threshold counts users worldwide, measured at the provider, so companies that only call a third-party model through an API are generally not covered providers.

Usually asked by

Clinical committees and health system AI governance.

Named alongside

HHS §1557 · HIPAA · FDA PCCP.

Sector pagePlanisphere for medicine

03 / Records

Records to keep

01Latent disclosure specification and per-release test results
02Logs showing the manifest-disclosure option was offered on each surface
03Detection tool uptime and API availability records
04Licensee monitoring records with discovery and revocation timestamps

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES