SSB 5324
In CommitteeSenate
Prior auth. APIs/health
Aligning the implementation of application programming interfaces for prior authorization with federal guidelines.
This status may be delayed. See Action History below for the latest updates.
How does a bill become law?
- Introduced: The bill is filed and assigned a number.
- Committee: A subject-matter committee holds hearings, takes public testimony, and decides whether to advance the bill.
- Floor Vote: The full chamber (House or Senate) debates and votes on the bill.
- Opposite Chamber: The bill repeats the committee and floor vote process in the other chamber.
- Governor: The Governor reviews the bill and decides whether to sign or veto it.
- Signed: The bill has been signed into law.
AI Analysis
This bill sets strict timing requirements for health plans to respond to prior authorization requests—especially electronic ones—and requires them to use modern technology (APIs) to let providers check and submit authorization requests automatically. It also updates clinical review criteria to be more equitable and ensures denials can be appealed like other benefit decisions.
- Requires health plans (private, public employee, and Medicaid) to respond to electronic prior authorization requests within 3 calendar days for standard requests and 1 calendar day for expedited requests (excluding holidays).
- Requires health plans to respond to non-electronic (e.g., fax or mail) prior authorization requests within 5 calendar days for standard requests and 2 calendar days for expedited requests.
- Mandates that health plans develop and maintain application programming interfaces (APIs) to let providers automatically check if prior authorization is needed and submit requests through their electronic health records—starting with health services on January 1, 2025, and prescription drugs on January 1, 2027.
- Requires prior authorization clinical criteria to be evidence-based, updated at least annually, and specifically address equity for Black and Indigenous people, people of color, gender identities, and underserved populations.
- States that a prior authorization denial or approval of a less intensive service or drug is considered an adverse benefit determination, triggering the plan’s formal grievance and appeal process.
Who is affected
- Health insurance carriers — Health plans (insurance companies) must now meet stricter timing requirements for reviewing and responding to prior authorization requests—especially electronic ones—and must implement new technology interfaces to automate prior authorization checks for services and drugs.
- Public employees, retirees, and their dependents — Public employee health plans must comply with the same prior authorization timing and technology standards as private insurers, including electronic interfaces and updated clinical criteria.
- Medicaid enrollees and their providers — Managed care organizations (like Medicaid HMOs) must meet the same prior authorization rules and technology requirements as other health plans, including electronic interfaces and equity-focused clinical criteria.
- Health care providers and facilities — Doctors, hospitals, and clinics must now receive faster decisions on prior authorization requests and have access to standardized electronic tools to check authorization needs and submit requests directly from their electronic health records.
Pro/Con Analysis
Stronger case for benefits
Potential Benefits (5)
Expedited prior authorization decisions (1-day for electronic requests) and standardized 3-day turnaround for standard requests reduce delays in care, especially for time-sensitive conditions—directly benefiting patients who face denials or long waits for approval.
HealthcarePeopleRef: Sec. 1(1)(a)(i)-(ii), Sec. 2(1)(a)(i)-(ii), Sec. 3(1)(a)(i)-(ii)Mandating equity-focused, annually updated clinical criteria helps reduce biased or outdated clinical standards that have historically disadvantaged Black, Indigenous, and people of color, improving fairness in coverage decisions.
HealthcarePeopleRef: Sec. 1(1)(d), Sec. 2(1)(d), Sec. 3(1)(d)APIs enabling automatic prior authorization checks and submissions through electronic health records reduce administrative burden on providers, freeing clinical staff time and reducing billing errors or delays.
HealthcarePeopleRef: Sec. 1(2)(a), Sec. 2(2)(a), Sec. 3(2)(a)Treating partial approvals (e.g., approving a less intensive service or drug) as adverse benefit determinations triggers formal appeal rights, strengthening patient and provider recourse against unfair coverage denials.
HealthcarePeopleRef: Sec. 1(2)(a)(v), Sec. 2(2)(a)(v), Sec. 3(2)(a)(v)Standardized electronic response timelines (3 days for standard, 1 day for expedited) reduce uncertainty for providers and patients, enabling better care coordination and scheduling—especially important for chronic or acute conditions.
HealthcarePeopleRef: Sec. 1(1)(a)(i), Sec. 2(1)(a)(i), Sec. 3(1)(a)(i)
Potential Concerns (5)
Health plans (including Medicaid HMOs and public employee plans) must invest in new API infrastructure and interoperability systems to comply with federal standards by 2025/2027, which may involve one-time technology costs and ongoing maintenance burdens.
Business & EmploymentRef: Sec. 1(2)(a), Sec. 2(2)(a), Sec. 3(2)(a)Health plans may request one-year delays in API implementation if they cannot meet deadlines, potentially creating inconsistent rollout timelines across plans and administrative complexity for providers who must track multiple compliance schedules.
Business & EmploymentRef: Sec. 1(2)(d), Sec. 2(2)(d), Sec. 3(2)(d)Mandating annual updates to clinical review criteria to address equity for Black and Indigenous people, people of color, gender identities, and underserved populations may require additional clinical review resources and training for health plan staff.
HealthcareRef: Sec. 1(1)(d), Sec. 2(1)(d), Sec. 3(1)(d)The bill does not allocate state funding to support implementation of API infrastructure or prior authorization system upgrades, potentially shifting costs to local governments that operate Medicaid managed care plans or public employee health programs.
Local GovernmentRef: Sec. 1(2)(a), Sec. 2(2)(a), Sec. 3(2)(a)Health plans must submit detailed justifications to the insurance commissioner if they cannot meet API implementation deadlines, creating additional regulatory oversight and reporting burdens for insurers.
Business & EmploymentRef: Sec. 1(2)(d)(i), Sec. 2(2)(d)(i), Sec. 3(2)(d)(i)
Who Is Most Affected
Health plans (insurance companies) must invest in new API infrastructure and comply with stricter timing requirements, increasing operational costs and regulatory oversight, though they retain discretion to request delays.
Public employees, retirees, and dependents benefit from faster, more equitable prior authorization decisions and reduced administrative delays in care, with no direct cost increase to them.
Medicaid enrollees—especially those from historically underserved communities—gain more timely and equitable access to care through standardized, equity-focused review criteria and faster electronic decisions.
Providers (doctors, clinics, hospitals) benefit from reduced administrative burden, faster decisions, and automated tools that integrate with EHRs, improving workflow efficiency and care delivery.