Bill Commons

CA SB 503

withdrawn

Health care services: artificial intelligence.

California · 2025-2026 Regular Session · upper

Quick answers

Did CA SB 503 pass?

No. CA SB 503 was withdrawn on 2026-08-30 and is no longer under consideration. Latest recorded action (2026-08-30): Enrolled and presented to the Governor at 6 p.m.

What is CA SB 503 about?

Existing law requires a health facility, clinic, physician's office, or office of a group practice that uses generative artificial intelligence to generate written or verbal patient communications pertaining to patient clinical information, as defined, to ensure that those communications include both (1) a disclaimer that indicates to the patient that a communication was generated by generative artificial intelligence, as specified, and (2) clear instructions describing how a patient may contact a human health care provider, employee, or other appropriate person. Existing law exempts from this requirement a communication read and reviewed by a human licensed or certified health care provider. This bill would require developers and deployers, as defined, of an artificial intelligence system that produces a prediction, classification, recommendation, evaluation, or analysis that aids decisionmaking related to diagnosis or treatment, known as a clinical decision support system, to make reasonable efforts to identify clinical decision support systems developed for use by deployers that are known or have a reasonably foreseeable risk for biased impacts resulting from deployment of the system in health programs or activities. The bill would require developers to make a statement describing the intended uses and known or reasonably foreseeable risks associated with the use of the clinical decision support system and certain documentation available to deployers, as specified. The bill would require developers to make reasonable efforts to mitigate known or reasonably foreseeable risk for biased impacts resulting from use of the clinical decision support system in health programs or activities. The bill would require deployers to regularly monitor clinical decision support systems and take reasonable and proportionate steps to mitigate known or reasonably foreseeable risk of biased impacts. The bill would specify that a person, partnership, state or local governmental agency, or corporation may be both a developer and a deployer.

Who sponsors CA SB 503?

Weber Pierson is the primary sponsor of CA SB 503, joined by 11 cosponsors.

Description

Existing law requires a health facility, clinic, physician's office, or office of a group practice that uses generative artificial intelligence to generate written or verbal patient communications pertaining to patient clinical information, as defined, to ensure that those communications include both (1) a disclaimer that indicates to the patient that a communication was generated by generative artificial intelligence, as specified, and (2) clear instructions describing how a patient may contact a human health care provider, employee, or other appropriate person. Existing law exempts from this requirement a communication read and reviewed by a human licensed or certified health care provider. This bill would require developers and deployers, as defined, of an artificial intelligence system that produces a prediction, classification, recommendation, evaluation, or analysis that aids decisionmaking related to diagnosis or treatment, known as a clinical decision support system, to make reasonable efforts to identify clinical decision support systems developed for use by deployers that are known or have a reasonably foreseeable risk for biased impacts resulting from deployment of the system in health programs or activities. The bill would require developers to make a statement describing the intended uses and known or reasonably foreseeable risks associated with the use of the clinical decision support system and certain documentation available to deployers, as specified. The bill would require developers to make reasonable efforts to mitigate known or reasonably foreseeable risk for biased impacts resulting from use of the clinical decision support system in health programs or activities. The bill would require deployers to regularly monitor clinical decision support systems and take reasonable and proportionate steps to mitigate known or reasonably foreseeable risk of biased impacts. The bill would specify that a person, partnership, state or local governmental agency, or corporation may be both a developer and a deployer.

Introduced
2025-02-19
Latest action
2026-08-30 — Enrolled and presented to the Governor at 6 p.m.
Bill type
bill
Last updated

Subjects

Sponsors

  • Weber Piersonauthor
  • Richardsoncoauthor
  • Bontacoauthor
  • Bryancoauthor
  • Elhawarycoauthor
  • Gipsoncoauthor
  • Jacksoncoauthor
  • McKinnorcoauthor
  • Ransomcoauthor
  • Sharp-Collinscoauthor
  • Smallwood-Cuevascoauthor
  • Wilsoncoauthor

Committees

Not provided by source.

Action timeline

  1. 2025-02-19

    Introduced. Read first time. To Com. on RLS. for assignment. To print.

    introduction,reading-1,referral-committee

  2. 2025-02-20

    From printer. May be acted upon on or after March 22.

  3. 2025-02-26

    Referred to Com. on RLS.

    referral-committee

  4. 2025-03-25

    From committee with author's amendments. Read second time and amended. Re-referred to Com. on RLS.

    amendment-passage,committee-passage,reading-1,reading-2,referral-committee

  5. 2025-04-02

    Set for hearing April 9.

  6. 2025-04-02

    Re-referred to Coms. on HEALTH and G.O.

    referral-committee

  7. 2025-04-10

    Read second time and amended. Re-referred to Com. on G.O.

    amendment-passage,reading-1,reading-2,referral-committee

  8. 2025-04-10

    From committee: Do pass as amended and re-refer to Com. on G.O. (Ayes 10. Noes 0. Page 737.) (April 9).

    amendment-passage,committee-passage,committee-passage-favorable,referral-committee

  9. 2025-04-10

    Withdrawn from committee.

    withdrawal

  10. 2025-04-10

    Re-referred to Com. on RLS.

    referral-committee

  11. 2025-04-22

    Set for hearing April 29 in JUD. pending receipt.

  12. 2025-04-23

    Re-referred to Com. on JUD.

    referral-committee

  13. 2025-04-30

    From committee: Do pass and re-refer to Com. on APPR. (Ayes 13. Noes 0. Page 941.) (April 29). Re-referred to Com. on APPR.

    committee-passage,committee-passage-favorable,referral-committee

  14. 2025-05-02

    Set for hearing May 12.

  15. 2025-05-12

    May 12 hearing: Placed on APPR. suspense file.

  16. 2025-05-16

    Set for hearing May 23.

  17. 2025-05-23

    From committee: Do pass. (Ayes 6. Noes 0. Page 1202.) (May 23).

    committee-passage,committee-passage-favorable

  18. 2025-05-23

    Read second time. Ordered to third reading.

    reading-1,reading-2,reading-3

  19. 2025-05-27

    Ordered to special consent calendar.

  20. 2025-05-29

    Read third time. Passed. (Ayes 38. Noes 0. Page 1327.) Ordered to the Assembly.

    passage,reading-1,reading-3

  21. 2025-05-29

    In Assembly. Read first time. Held at Desk.

    reading-1

  22. 2025-06-05

    Referred to Coms. on HEALTH and P. & C.P.

    referral-committee

  23. 2025-06-24

    July 1 hearing postponed by committee.

  24. 2025-06-30

    From committee with author's amendments. Read second time and amended. Re-referred to Com. on HEALTH.

    amendment-passage,committee-passage,reading-1,reading-2,referral-committee

  25. 2025-07-09

    From committee: Do pass as amended and re-refer to Com. on P. & C.P. (Ayes 16. Noes 0.) (July 8).

    amendment-passage,committee-passage,committee-passage-favorable,referral-committee

  26. 2025-07-10

    Read second time and amended. Re-referred to Com. on P. & C.P.

    amendment-passage,reading-1,reading-2,referral-committee

  27. 2025-07-17

    Assembly Rule 63 suspended. (Ayes 49. Noes 15. Page 2578.)

  28. 2025-07-17

    From committee: Do pass as amended and re-refer to Com. on APPR. (Ayes 13. Noes 0.) (July 16).

    amendment-passage,committee-passage,committee-passage-favorable,referral-committee

  29. 2025-07-17

    Read second time and amended. Re-referred to Com. on APPR.

    amendment-passage,reading-1,reading-2,referral-committee

  30. 2025-08-20

    August 20 set for first hearing. Placed on APPR. suspense file.

  31. 2025-08-29

    From committee: Do pass. (Ayes 15. Noes 0.) (August 29).

    committee-passage,committee-passage-favorable

  32. 2025-09-02

    Read second time. Ordered to third reading.

    reading-1,reading-2,reading-3

  33. 2025-09-04

    Read third time and amended.

    amendment-passage,reading-1,reading-3

  34. 2025-09-04

    Ordered to third reading.

    reading-1,reading-3

  35. 2025-09-10

    Ordered to inactive file on request of Assembly Member Aguiar-Curry.

  36. 2026-08-11

    Notice of intention to remove from inactive file given by Assembly Member Wilson.

  37. 2026-08-12

    Ordered to third reading.

    reading-1,reading-3

  38. 2026-08-12

    From inactive file.

  39. 2026-08-19

    Read third time and amended.

    amendment-passage,reading-1,reading-3

  40. 2026-08-19

    Ordered to third reading.

    reading-1,reading-3

  41. 2026-08-24

    Read third time. Passed. Ordered to the Senate.

    passage,reading-1,reading-3

  42. 2026-08-24

    In Senate. Concurrence in Assembly amendments pending.

  43. 2026-08-25

    Assembly amendments concurred in. (Ayes 39. Noes 0.) Ordered to engrossing and enrolling.

  44. 2026-08-30

    Enrolled and presented to the Governor at 6 p.m.

  45. 2026-08-24

    Read third time. Passed. (Ayes 70. Noes 1. Page 6384.) Ordered to the Senate.

    passage,reading-1,reading-3

Versions

  • 02/19/25 - Introduced — 2025-02-19Compare
  • 03/25/25 - Amended Senate — 2025-03-25Compare
  • 04/10/25 - Amended Senate — 2025-04-10Compare
  • 06/30/25 - Amended Assembly — 2025-06-30Compare
  • 07/10/25 - Amended Assembly — 2025-07-10Compare
  • 07/17/25 - Amended Assembly — 2025-07-17Compare
  • 09/04/25 - Amended Assembly — 2025-09-04Compare
  • 08/19/26 - Amended Assembly — 2026-08-19Compare
  • 08/27/26 - Enrolled — 2026-08-27Compare
  • SB503Compare
  • (document, no version)Compare

Documents

Votes

  • Do pass as amended, but first amend, and re-refer to the Committee on [Governmental Organization]

    2025-04-09 · pass · 10-0

    Member-level votes (11)
    • Menjivar: yes
    • Richardson: yes
    • Rubio: yes
    • Gonzalez: yes
    • Limón: yes
    • Grove: yes
    • Weber Pierson: yes
    • Wiener: yes
    • Durazo: yes
    • Padilla: yes
    • Valladares: other
  • Do pass, but first be re-referred to the Committee on [Appropriations]

    2025-04-29 · pass · 13-0

    Member-level votes (13)
    • Arreguín: yes
    • Niello: yes
    • Allen: yes
    • Durazo: yes
    • Laird: yes
    • Valladares: yes
    • Wahab: yes
    • Stern: yes
    • Caballero: yes
    • Weber Pierson: yes
    • Ashby: yes
    • Umberg: yes
    • Wiener: yes
  • Placed on suspense file

    2025-05-12 · pass · 7-0

    Member-level votes (7)
    • Wahab: yes
    • Seyarto: yes
    • Grayson: yes
    • Richardson: yes
    • Cabaldon: yes
    • Dahle: yes
    • Caballero: yes
  • Do pass

    2025-05-23 · pass · 6-0

    Member-level votes (7)
    • Caballero: yes
    • Seyarto: yes
    • Wahab: yes
    • Cabaldon: yes
    • Richardson: yes
    • Grayson: yes
    • Dahle: other
  • Special Consent SB503 Weber Pierson et al.

    2025-05-29 · pass · 38-0

    Member-level votes (40)
    • Smallwood-Cuevas: yes
    • Grayson: yes
    • Grove: yes
    • Dahle: yes
    • Rubio: yes
    • Jones: yes
    • Umberg: yes
    • Weber Pierson: yes
    • Wiener: yes
    • Stern: yes
    • Padilla: yes
    • Arreguín: yes
    • Caballero: yes
    • Pérez: yes
    • McNerney: yes
    • Gonzalez: yes
    • Durazo: yes
    • Cortese: yes
    • Archuleta: yes
    • Blakespear: yes
    • Laird: yes
    • Strickland: yes
    • Choi: yes
    • Valladares: yes
    • McGuire: yes
    • Niello: yes
    • Allen: yes
    • Richardson: yes
    • Hurtado: yes
    • Cervantes: yes
    • Seyarto: yes
    • Menjivar: yes
    • Wahab: yes
    • Becker: yes
    • Alvarado-Gil: yes
    • Ochoa Bogh: yes
    • Ashby: yes
    • Cabaldon: yes
    • Limón: other
    • Reyes: other
  • Do pass as amended and be re-referred to the Committee on [Privacy and Consumer Protection]

    2025-07-08 · pass · 16-0

    Member-level votes (16)
    • Rogers: yes
    • Caloza: yes
    • Mark González: yes
    • Elhawary: yes
    • Patel: yes
    • Aguiar-Curry: yes
    • Schiavo: yes
    • Bonta: yes
    • Ellis: yes
    • Flora: yes
    • Celeste Rodriguez: yes
    • Stefani: yes
    • Addis: yes
    • Sharp-Collins: yes
    • Chen: yes
    • Sanchez: yes
  • Do pass as amended and be re-referred to the Committee on [Appropriations]

    2025-07-16 · pass · 13-0

    Member-level votes (15)
    • Bryan: yes
    • Wicks: yes
    • Irwin: yes
    • Wilson: yes
    • Dixon: yes
    • Petrie-Norris: yes
    • Pellerin: yes
    • Lowenthal: yes
    • Ward: yes
    • Patterson: yes
    • Bauer-Kahan: yes
    • Ortega: yes
    • McKinnor: yes
    • Macedo: other
    • DeMaio: other
  • Do pass.

    2025-08-29 · pass · 15-0

    Member-level votes (15)
    • Ta: yes
    • Elhawary: yes
    • Pellerin: yes
    • Fong: yes
    • Pacheco: yes
    • Tangipa: yes
    • Calderon: yes
    • Arambula: yes
    • Dixon: yes
    • Mark González: yes
    • Sanchez: yes
    • Wicks: yes
    • Caloza: yes
    • Ahrens: yes
    • Solache: yes

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_api_sync, retrieved 2026-09-13T06:31:56.940426Z

Inspect retained evidence for changes recorded after evidence tracking began:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=CA&identifier=SB 503. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.
  • Some documents have no extracted text yet, so version comparison may be limited.

See the methodology page for data sources and limitations.