Back

State of Oregon

· State

· Oregon

Scheduling Portal for Health Care Interpreters

PROPOSALS DUE

October 15, 2026, 5:00 pm PDT

Closed

Deadline moved · was Oct 1 → now Oct 15 · +14 days

WHAT THEY WANT

(Summarized from the RFP)

The Oregon Health Authority (OHA), through the Department of Administrative Services State Procurement Services, seeks a vendor to design, implement, and operate a cloud-based Software as a Service (SaaS) Scheduling Portal for Health Care Interpreters. The Portal will enable Oregon Health Plan (OHP) members with limited English proficiency or who are deaf or hard of hearing to access credentialed health care interpretation services — including Video Remote Interpretation, Over-the-Phone Interpretation, and In-Person Interpretation — through a centralized, secure online platform.

WHAT OTHERS ASKED

71 questions answered

▶

Please define the minimum required Day 1 functionality for initial Go-Live versus functionality that may be delivered in post-launch phases. For each major capability-including user onboarding, scheduling and matching, interpreter fulfillment and overflow, claims and payer workflows, integrations, reporting, notifications, customer service, and grievance support-please identify whether it must be fully operational at launch, may be phased in, or is optional, together with any required completion dates and acceptance criteria.

Scope/requirements

▶

Please provide a consolidated integration roadmap identifying which external-system integrations are mandatory and fully operational at initial Go-Live, which may be delivered in later phases, and the required timing for each. For every integration, please also identify whether OHA will provide an existing interface specification or companion guide, a development/test environment with test data, and an OHA or third-party technical point of contact during implementation.

Administrative

▶

For CCO-enrolled members, which CCO payment processes must the Portal support at initial go-live? Please clarify whether each CCO uses a different claims or payment-instruction workflow and interface, or whether OHA will provide standardized requirements, data formats, interface specifications, and connectivity for all CCOs. If CCO-specific integrations are required, please identify the CCOs and workflows that must be supported at launch versus those that may be phased in later.

Scope/requirements

▶

You mentioned that the contractor must provide interpreters when the Registry and Recruitment and Retention partner cannot fill an appointment. Can we use a subcontracted language services company for this? Are there specific qualifications or response times that company would need to meet?

Scope/requirements · Award & contract

▶

Thanks for providing the estimated appointment volumes. Do you also have estimates for the number of providers, interpreters, OHA staff, CCO users and people using the system at the same time? Can you provide an estimated monthly text-message volume and annual claim volume?

Administrative

▶

Is the first quarter of 2028 a firm go-live deadline or an estimated target? Would you consider launching the system in phases?

Scope/requirements

All 71 answers open with a free account.

ABOUT THIS RFP

RFP number

S-DASOBO-00016280

Budget

$1,500,000

Published

Entity type

State

State

Oregon

Summarized from the State of Oregon portal.

HOW TO SUBMIT

Proposals must be submitted electronically through the State of Oregon's OregonBuys procurement system at https://oregonbuys.gov/. No other submission method (e.g., email, printed matter) is authorized or permitted. Proposals submitted by any other method will not be accepted or considered.

NAICS CODES & TAGS

541511

541512

541519

Website Development

Information Technology Support Services

Data Analytics and Research Services

ACROSS 539 RFPS

MORE THAN

1 in 5

1 in 5

RFPs changed their terms while active.

A week of proposal work, based on the published terms.

A week of proposal work, based on the published terms.

DAY 1 · PUBLISHED

PUBLISHED

DAY 16 · THE TERMS CHANGE

DAY 16 · TERMS CHANGE

DAY 25 · DUE

DUE

25 days is the median window from publication to due date; day 16 is the median first change for the 113 that changed. 539 RFPs published and due: July 23 - Sept. 30, 2026.

Bid on five RFPs, and the odds are better than two in three that at least one changes its terms before the deadline. Larger firms have staff tracking this. Start free and you’ll have it at your fingertips too.

This RFP has closed

Proposals were due October 15, 2026, 5:00 pm PDT. Leads tracks active RFPs from posting to deadline.

"The efficiency of the Leads platform allows us to determine if an RFP is worth the effort in minutes rather than hours. The results speak for themselves, we recently won our first bid, which we initially found on Leads!"

Kiana Stringfield

Founder, AKOMAKONNECT

"The efficiency of the Leads platform allows us to determine if an RFP is worth the effort in minutes rather than hours. The results speak for themselves, we recently won our first bid, which we initially found on Leads!"

Kiana Stringfield

Founder, AKOMAKONNECT

A week of proposal work, based on the published terms.

A week of proposal work, based on the published terms.

Unlocking access to government contracts

one RFP at a time.

Sign up for RFP Insights

We'll send you RFP insights and relevant updates to help you gain a competitive edge.

© 2026 RFPGo.ai, All rights reserved

Unlocking access to government contracts one RFP at a time.

Sign up for RFP Insights

We'll send you RFP insights and relevant updates to help you gain a competitive edge.

© 2026 RFPGo.ai, All rights reserved

Unlocking access to government

contracts one RFP at a time.

Sign up for RFP Insights

We'll send you RFP insights and relevant updates to help you gain a competitive edge.

© 2026 RFPGo.ai, All rights reserved