SHB 1706
SignedHouse
Prior auth. APIs/health
Aligning the implementation of application programming interfaces for prior authorization with federal guidelines.
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 standardizes how health plans in Washington handle prior authorization—especially through electronic systems—to speed up decisions, reduce administrative burden on providers, and ensure fairness and equity. It requires health plans to use modern digital tools (APIs) to connect with providers’ electronic health records, and sets strict deadlines for responding to requests. It also strengthens transparency and appeal rights when services or drugs are denied or altered.
- Requires health plans (insurers, public employee plans, and managed care organizations) to respond to prior authorization requests within strict time frames: 3 days for standard electronic requests, 1 day for expedited electronic requests, and longer (up to 5 days) for non-electronic requests.
- Mandates that health plans use application programming interfaces (APIs)—secure digital connections—to let providers automatically check if prior authorization is needed, submit requests, and receive decisions directly from their electronic health records systems.
- Requires APIs for health services to be operational by January 1, 2025, and for prescription drugs by January 1, 2027, aligned with federal rules from the Centers for Medicare & Medicaid Services (CMS).
- Requires clinical review criteria used for prior authorization to be evidence-based, updated at least annually, and inclusive of considerations for racial equity, gender, and underserved populations.
- Clarifies that denials or downgrades of prior authorization requests (e.g., approving a less intensive service or drug than requested) count as adverse benefit determinations, triggering the plan’s formal grievance and appeal process for patients and providers.
Who is affected
- Health insurers and managed care organizations — Health plans (insurance companies) must now meet stricter time limits for responding to prior authorization requests and use standardized electronic systems to communicate with providers.
- Health care providers and facilities — Providers (doctors, clinics, hospitals) gain faster, more consistent access to prior authorization decisions and requirements through automated electronic systems, reducing paperwork and delays.
- Health plan enrollees (patients) — Patients may experience shorter wait times for care decisions—especially for urgent needs—and more transparent, consistent rules about what services or drugs require approval before treatment.
- State government agencies — State agencies (like the Office of the Insurance Commissioner and Health Care Authority) gain new reporting and oversight responsibilities to ensure compliance with federal and state requirements.
Pro/Con Analysis
Stronger case for benefits
Potential Benefits (5)
Mandating 3-day (electronic) and 1-day (expedited) decision windows for prior authorization significantly reduces administrative delays in care, enabling timely treatment — especially for patients with chronic or acute conditions — and reduces provider burnout from paperwork backlogs.
HealthcarePeopleRef: Sec. 1(1)(a)(i), Sec. 2(1)(a)(i), Sec. 3(1)(a)(i)Classifying denials or downgrades (e.g., approving a less intensive service) as adverse benefit determinations triggers formal appeal rights, empowering patients and providers to challenge unjust denials — a major improvement in patient agency and due process in the prior auth process.
HealthcarePeopleRef: Sec. 1(2)(a)(v), Sec. 2(2)(a)(v), Sec. 3(2)(a)(v)API-based integration between EHRs and health plans reduces manual data entry, faxing, and phone calls — lowering administrative burden for providers (especially small clinics) and reducing no-show rates due to prior auth delays.
HealthcarePeopleRef: Sec. 1(2)(a), Sec. 2(2)(a), Sec. 3(2)(a)Requiring clinical review criteria to be evidence-based, updated annually, and inclusive of racial/gender/underserved population considerations creates a structural pathway to reduce bias in coverage decisions — though enforcement remains a concern.
HealthcarePeopleRef: Sec. 1(1)(d), Sec. 2(1)(d), Sec. 3(1)(d)Standardizing prescription drug prior authorization APIs by 2027 (aligned with CMS) will reduce fragmentation in drug coverage decisions — helping patients avoid last-minute formulary changes and ensuring smoother transitions between therapies.
HealthcarePeopleRef: Sec. 1(2)(b), Sec. 2(2)(b), Sec. 3(2)(b)
Potential Concerns (5)
Expedited prior authorization decisions (within 1 day) for urgent cases may improve access to time-sensitive care, but the requirement only applies to *electronic* requests — many rural, low-income, or elderly patients lack reliable access to EHR-integrated systems, potentially excluding them from the fastest review timelines and worsening disparities in urgent care access.
HealthcarePeopleRef: Sec. 1(1)(a)(ii), Sec. 2(1)(a)(ii), Sec. 3(1)(a)(ii)Mandating APIs for prior authorization creates significant one-time and ongoing technology costs for health plans — especially smaller insurers and MCOs — which may pass these costs to employers and enrollees via higher premiums or reduced network coverage, disproportionately affecting small businesses and working families.
HealthcarePeopleRef: Sec. 1(2)(a), Sec. 2(2)(a), Sec. 3(2)(a)While clinical review criteria must be updated annually and consider equity, the bill does not mandate independent oversight or enforceable standards for *implementation* — health plans retain broad discretion in defining criteria, which may still reflect implicit bias or fail to meaningfully incorporate social determinants of health.
HealthcarePeopleRef: Sec. 1(1)(d), Sec. 2(1)(d), Sec. 3(1)(d)The bill allows health plans to request one-year delays in API implementation if they claim “good faith effort” — a subjective standard that could be exploited by large insurers to delay compliance, undermining the bill’s goal of timely, standardized digital access for providers and patients.
HealthcareLean peopleRef: Sec. 1(2)(d)(i), Sec. 2(2)(d)(i), Sec. 3(2)(d)(i)The bill explicitly excludes prior authorizations under RCW 48.43.761 (certain mental health and substance use disorder services), creating a carve-out that may perpetuate unequal administrative scrutiny and delays for behavioral health care compared to physical health services.
HealthcareLean peopleRef: Sec. 1(3), Sec. 2(3), Sec. 3(3)
Who Is Most Affected
Patients — especially those with chronic conditions, low income, or in rural areas — benefit from faster, more transparent prior auth decisions and reduced administrative barriers to care. However, those without reliable EHR access or digital literacy may not fully benefit from the API requirements.
Providers (especially small clinics and solo practices) benefit from reduced paperwork, faster decisions, and automated workflows — but may face costs in adapting EHR systems to meet API requirements, especially if health plans do not share implementation costs.
Health insurers and MCOs face new technology and compliance costs, but may benefit from long-term operational efficiencies and reduced appeals litigation. Large national plans are better positioned to absorb costs than smaller regional insurers.