STATE OF IDAHO

THE DEPARTMENT OF HEALTH AND WELFARE

REQUEST FOR PROPOSAL (RFP)

Technology Assessment - RHTP Rural Health Transformation Plan and Program (RHTP) Grant

RHRFP2606 / IPRO RFP1375

Issue Date 07/10/2026 Amended 07/31/2026

TABLE OF CONTENTS

Page

1RFP ADMINISTRATIVE INFORMATION

OVERVIEW

QUESTIONS

INSTRUCTIONS FOR SUBMISSION OF PROPOSALS

PROPOSAL FORMAT

PROPOSAL REVIEW, EVALUATION, AND AWARD

MANDATORY SUBMISSION REQUIREMENTS

Business Information Organization and Staffing

SCOPE OF WORK

APPENDIX A -- COST PROPOSAL AND BILLING PROCEDURE

APPENDIX B -- REPORTS

APPENDIX C -- STATE OF IDAHO CONTRACT TERMS AND CONDITIONS WITH ARTICLE 6

APPENDIX D -- RIDERS

APPENDIX E -- IDAHO TERMS AND CONDITIONS BACKGROUND AND LIMITATIONS

ATTACHMENT 1 -- OFFEROR QUESTIONS

ATTACHMENT 2 -- MODIFICATION AND EXCEPTION FORM

ATTACHMENT 3 -- PRE-PROPOSAL CONFERENCE REGISTRATION FORM

ATTACHMENT 4 -- STATE SIGNATURE PAGE

ATTACHMENT 5 -- COVER FORM

ATTACHMENT 6 -- IDAHO GOVERNOR’S RHTP TASK FORCE

ATTACHMENT 7 -- LEGISLATIVE OVERSIGHT COMMITTEE

ATTACHMENT 8 -- Idaho RHTP Abstract ATTACHMENT 9 -- Idaho RHTP Eligibility Map ATTACHMENT 10 -- Rural Cities within Partially Urban Counties in Idaho

ATTACHMENT 11 -- MAP OF DEPARTMENT REGIONS

RFP ADMINISTRATIVE INFORMATION TC "RFP ADMINISTRATIVE INFORMATION" \f C \l "1"

Supervisory Lead Grants/Contracts Officer Patricia.Thomas@dhw.idaho.gov

Submit Proposal to:

Submit electronically via IPRO Electronic Submission:

IPRO LOGIN

Pre-Proposal Conference Date/Time:

Pre-Proposal Conference Location:

Friday, 07/17/2026, 10:00 a.m. Mountain Time By Microsoft Teams only You must email the RFP Lead by the Pre-Proposal Registration Deadline to receive conference details. Late registrations will not be guaranteed to receive conferencing information. There will not be an in-person conference.

Microsoft Team Meeting ID: 274 696 067 905 139

Passcode: KP22Tb9y

OVERVIEW TC "1

OVERVIEW" \f C \l "1" 1.1 Purpose The Department, through the RHTP grant, funded under Centers for Medicare & Medicaid Services (CMS) cooperative agreement CMS-RHT-26-001, seeks a qualified contractor to conduct comprehensive healthcare facility technology assessments for healthcare organizations statewide, including rural and underserved communities. The assessments must evaluate current-state technology infrastructure, operational capabilities, technology maturity, interoperability readiness, workforce readiness, and future technology needs with long-term sustainability as the core focus.

The objectives of the assessments include to:

· Identify healthcare technology gaps and unmet needs;

· Assess facility readiness for healthcare technology modernization;

· Evaluate interoperability and data-sharing capabilities;

· Evaluate telehealth and virtual care infrastructure;

· Assess healthcare workforce technology readiness and training needs;

· Identify opportunities to improve patient access and care coordination through the use of technology;

· Assess infrastructure required for Artificial Intelligence (AI), analytics, automation, and population health technologies; and

· Identify rural-specific technology barriers.

The Contractor must produce actionable findings and implementation-ready recommendations that support statewide healthcare transformation, access improvement, care coordination, operational sustainability, emergency preparedness, and population health improvement. This work falls under Idaho’s RHTP Initiative 1: Improving rural access to care through technology.

1.2 Background Information The Department will serve as the lead agency for administering the RHTP grant funding award for the state of Idaho. As such, the Department is committed to removing barriers to treatment, improving health outcomes, and promoting patient-centered care. The Idaho RHTP website address is: https://healthandwelfare.idaho.gov/providers/rural-health-transformation-program-grant/about-rural-health-transformation-program-grant

As the grant recipient, the Department manages the entire grant award and is responsible for distributing funding to other Idaho state agencies, contractors, and subgrantees in alignment with the projects awarded by CMS. This distribution will be carried out in accordance with both state and federal regulations, specifically procurement rules, to facilitate the execution of RHTP work. The state’s RHTP is a critical mechanism to advance a sustainable, data-driven model of care that enhances access, quality, and outcomes.

Idaho’s RHTP https://publicdocuments.dhw.idaho.gov/WebLink/DocView.aspx?id=35081&dbid=0&repo=PUBLIC-DOCUMENTS is a multi-year strategic plan including five (5) major initiatives designed to strengthen rural health systems, increase access to care, enhance quality outcomes, expand workforce capacity, and promote financial sustainability. These initiatives address CMS’ strategic goals for this grant to transform healthcare for residents in the state’s rural areas.

The five (5) initiatives are:

Initiative 1. Improving rural access to care through technology

· Facility technology assessments and shared infrastructure

· Telehealth expansion

· Digital health

· Cybersecurity modernization and AI tools

· Emergency communication systems implementation and enrollment

· Health management and data analytics tools

· Electronic Health Record (EHR) software and upgrades

Initiative 2. Ensuring accessible, quality care through innovative models

· Diagnostic and care access innovations

· Health extenders

· Emergency Medical Services (EMS) expansion and workforce stabilization

· Understand opportunities to leverage health extenders and optimize service delivery

Initiative 3. Sustaining rural workforce with training, recruitment, and retention

· Ladder payments based on priority positions and rural presence

· Healthcare career exploration and advancement programs

· Work-based learning

· Graduate medical education (GME) programs

Initiative 4. Implementing population specific, evidence-based projects to Make America Healthy Again

· Chronic disease prevention and treatment

· Behavioral health prevention and treatment

· Maternal and child health efforts

Initiative 5. Investing in rural health infrastructure and partnerships

· Healthcare facility renovations

· Pharmacy solutions

· Clinical equipment purchases

· Vehicles for patient transport and rural mobile health units

· Healthcare facilities federal, state, and local safety code compliance

· Tribal RHTP support

Idaho’s RHTP leverages partnerships with state and local agencies, tribal partners, healthcare providers and community organizations to ensure locally responsive solutions.

Idaho’s RHTP is designed to improve chronic disease prevention and management, expand healthcare access, address workforce training, recruitment and retention, and strengthen the long-term health of rural residents through sustainable solutions. Idaho’s RHTP will work to modernize electronic and logistical infrastructure, strengthen community-to-clinician connections, and further integrate healthcare and community-based services across settings and types of care.

Idaho’s rural healthcare network includes twenty-six (26) Critical Access Hospitals (CAHs), one (1) Rural Emergency Hospital (REH), fifty-seven (57) Rural Health Clinics (RHCs), fifteen (15) Federally Qualified Health Centers (FQHCs), and additional provider facilities serving six hundred fifty-five thousand seventy (655,070) residents in eligible rural census tracts—approximately thirty-six percent (36%) of the state’s population across ninety-six percent (96%) of its land area. Many of these facilities face technology gaps, aging infrastructure, and insufficient interoperability capabilities that hinder care delivery.

The assessments conducted under the Contract resulting from this RFP will inform downstream RHTP procurements including, but not limited to telehealth expansion, AI-enabled tools, digital health applications, EHR/interoperability investments. The Contractor’s findings will serve as the foundational evidence base for technology investment decisions across Idaho RHTP’s five (5)-year period of performance.

The Contractor must perform the following tasks across two (2) major work streams: (A) Statewide and Regional Healthcare Facility Technology Assessments, and (B) Shared Infrastructure Strategy and Framework Development.

QUESTIONS TC "2

QUESTIONS" \f C \l "1" 2.1 Restrictions on Communications

From the issue date of this RFP, until a Contract is awarded, or the RFP is cancelled, vendors are prohibited from communications regarding this RFP with Department staff, evaluation committee members, or other associated individuals, except the Department’s RFP Lead.

2.2 Pre-Proposal Conference

A non-mandatory pre-proposal conference will be held at the time indicated in the RFP Administrative Information Section, page 1 of this RFP. This will be your opportunity to ask questions of Department staff. All interested parties are invited to participate by an established call in number. To receive conference details, participants must register for the Pre-Proposal Conference no later than Thursday, 07/16/2026, 3:00 p.m. Mountain Time by submitting the completed Attachment 3 -- Pre-Proposal Conference Registration Form via e-mail to the RFP Lead at Patricia.Thomas@dhw.idaho.gov. Late registrations will not be guaranteed to receive conferencing information. Vendors are strongly encouraged to submit questions to the RFP Lead prior to the pre-proposal conference. Any oral answers given by the Department during the pre-proposal conference are unofficial and will not be binding on the State. Conference attendance is at the vendor’s own expense.

2.3 Questions and Vendor Proposed Modifications and Exceptions to Requirements, Terms, or Conditions

Questions must be submitted, by email, to the RFP Lead by the date and time indicated in the RFP Administrative Information Section, page 1 of this RFP in order to be considered. Vendors are strongly encouraged to submit any proposed questions, and or modifications to the requirements, terms, or conditions at this time. Written questions must be submitted using Attachment 1 -- Offeror Questions and requested modifications and or exceptions, must be submitted using Attachment 2 -- Modification and Exception Form. The RFP Lead is the only contact for this Solicitation. All correspondence must be in writing. Official answers to all written questions will be posted on the State’s eProcurement system (IPRO) as an amendment to this RFP.

2.3.1 Proposed modifications and exceptions to requirements, terms or conditions must contain the following:

a.

The rationale for the specific requirement being unacceptable to the party submitting the question (define the deficiency).

b.

Recommended verbiage for the State’s consideration that is consistent in content, context, and form with the State’s requirement that is being questioned.

c.

Explanation of how the State’s acceptance of the recommended verbiage is fair and equitable to both the State and to the party submitting the question.

2.3.2 The State will not consider any modifications or exceptions that are not identified specifically on Attachment 2 and that are submitted after the Question deadline.

2.3.3 The State has sole discretion to determine if the modifications or exceptions submitted by an Offeror would result in a material change or otherwise threaten the integrity of the procurement process. Pursuant to IDAPA 38.05.01.084, the State may only negotiate non-material modifications or exceptions. Modifications or exceptions which the State determines to be material, or which otherwise threaten the integrity of the procurement process, will not be accepted or negotiated.

2.3.4 Except as otherwise provided in the Solicitation document, including the State of Idaho Standard Contract Terms and Conditions with Article 6 (updated May 2026) the State will not consider modifications or exceptions to the requirements, terms, or conditions which are proposed after the Question deadline.

2.3.5 Proposals which condition the Proposal based upon the State accepting other terms and conditions not found in the RFP, or which take exception to the State’s terms and conditions, will be found non-responsive, and no further consideration of the Proposal will be given.

INSTRUCTIONS FOR SUBMISSION OF PROPOSALS TC "3

INSTRUCTIONS FOR SUBMISSION OF PROPOSALS" \f C \l "1" 3.1 General Instructions

3.1.1 Proposals must be submitted as detailed in 3.1.6 below. Except as otherwise addressed in this Solicitation, all submission materials must be submitted at the same time. If multiple submissions are received, only the latest timely submission will be considered.

3.1.2 Alternate proposals are not allowed.

3.1.3 All files must be in Microsoft Word, Excel or searchable PDF format. The only exceptions are Attachment 1 – Offeror Questions and Attachment 2 -- Modification and Exception Form which must be submitted in Word format. The electronic version must NOT be password protected or locked in any way.

3.1.4 All Offerors participating in this Solicitation must establish an account in the IPRO system as it is necessary in order to submit your response and award the resulting Contract(s). Establishing an account is free and only takes a few minutes.

3.1.5 Vendors are strongly encouraged to begin the process of submitting the response far enough in advance of the Closing Date to allow for resolution of technical difficulties. Be advised that the State is not responsible for a Vendor’s failure to timely submit a responsive submission due to any technical or technological difficulties. See IDAPA 38.05.01.61.

3.1.6 Both the Technical Proposal and the Appendix A - Cost Proposal and Billing Procedure must be submitted electronically through IPRO. Failure to input this data in IPRO will result in the Proposal being found non-responsive. Download the Excel spreadsheet titled “Appendix A – Cost Proposal and Billing Procedure” found in the Question Section of IPRO. Complete the spreadsheet, upload it back into IPRO in an Excel spreadsheet format. Upload your Technical Proposal into the appropriate Question Section in IPRO. Technical proposals are limited to not more than fifteen (15) pages.

3.1.7 The current version of the Solicitation Instructions to Vendors is incorporated by reference into this Solicitation, and attached or referenced in any resulting Contract, as if set forth in their entirety. This document can be downloaded at https://purchasing.idaho.gov/vendor-resources/; or copies obtained by contacting the Division of Purchasing at 208-327-7465 or purchasing@adm.idaho.gov. Failure by any Offeror to obtain a copy of this document or the State of Idaho Contract Terms and Conditions with Article 6 - Appendix C shall in no way constitute or be deemed a waiver by the State of any term, condition or requirement contained in the referenced documents; and no liability will be assumed by the Department for an Offeror’s failure to consider the State of Idaho Standard Contract Terms and Conditions with Article 6 and Solicitation Instructions to Vendors in preparing its response to the solicitation.

SPECIAL TERMS PRECEDENCE: The State of Idaho Contract Terms and Conditions with Article 6 have been adapted for use by the Department of Health and Welfare and are included with this Solicitation as Appendix C. It also includes the Rural Health Transformation Program Additional Contract Terms and Conditions.

3.2 Trade Secrets

Paragraph 28 of the Solicitation Instructions to Vendors describes trade secrets to “include a formula, pattern, compilation, program, computer program, device, method, technique or process that derives economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by other persons and is subject to the efforts that are reasonable under the circumstances to maintain its secrecy.” In addition to marking each page of the document with a trade secret notation (as applicable; and as provided in Paragraph 28 of the Solicitation Instructions to Vendors), Offerors must also:

3.2.1 Identify with particularity the precise text, illustration, or other information contained within each page marked “trade secret” (it is not sufficient to simply mark the entire page). The specific information you deem “trade secret” within each noted page must be highlighted, italicized, identified by asterisks, contained within a text border, or otherwise clearly delineated from other text/information and specifically identified as a “trade secret.”

3.2.2 Provide a separate document entitled “List of Redacted Trade Secret Information” which provides a succinct list of all trade secret information noted in your Proposal; listed in the order it appears in your submittal documents, identified by Page #, Section #/Paragraph #, Title of Section/Paragraph, specific portions of text/illustrations; or in a manner otherwise sufficient to allow the State’s procurement personnel to determine the precise text/material subject to the notation. Additionally, this list must identify with each notation the specific basis for your position that the materials be treated as exempt from disclosure and how material complies with the Public Records Law.

3.2.3 If your Technical Proposal contains trade secret information, you must also upload a redacted copy with all trade secret information removed or blacked out. The redacted copy must be uploaded into IPRO into the appropriate Question Section in IPRO with the word “redacted” in the file name.

3.3 Electronic Submission of Proposals 3.3.1 Proposals must be submitted through IPRO, at https://sms-idaho-prd.tam.inforgov.com/fsm/SupplyManagementSupplier/page/XiSupplyManagementSupplierPage?csk.SupplierGroup=LUMA. When submitting through IPRO, upload your Technical Proposal and Appendix A - Cost Proposal and Billing Procedure, and all other required submittal items in the appropriate Question Sections. Remember to submit an additional redacted version of the TECHNICAL PROPOSAL if you have identified trade secrets.

3.3.2 The Technical Proposal and Appendix A - Cost Proposal and Billing Procedure must be separate files submitted at the same time.

3.3.3 Offerors are further advised to upload response materials with descriptive file names, organized and consolidated in a manner which allows evaluators to efficiently navigate the Offeror’s response.

PROPOSAL FORMAT TC "4

PROPOSAL FORMAT" \f C \l "1" These instructions describe the format to be used when submitting a Proposal. The format is designed to ensure a complete submission of information necessary for an equitable analysis and evaluation of submitted Proposals.

4.1 Table of Contents

Include a table of contents in the Technical Proposal identifying the contents of each Section, including page numbers of major subsections.

4.2 Format Proposals shall follow the numerical order of this RFP starting at the beginning and continuing through the end of the RFP. Proposal Sections and subsections must be identified with the corresponding numbers and headings used in this RFP. Respond to RFP Sections marked with an evaluation code. In your response, restate the RFP Section and follow with your response.

Offerors are encouraged to use a different color font, bold text, italics, or other indicator to clearly distinguish the RFP Section from the Offeror’s response.

4.3 Evaluation Codes

(M) Mandatory Response - failure to respond to any (M) Section, or to comply with any mandatory specification or requirement, will render Offeror’s Proposal non-responsive and no further evaluation will occur.

(ME)

Mandatory and Evaluated Response - failure to respond to any (ME) Section, or to comply with any mandatory specification or requirement in an (ME) Section, will render Offeror’s Proposal non-responsive and no further evaluation will occur. Offeror must respond to these sections as directed; points will be awarded based on predetermined criteria.

(E) Evaluated Response - a response is desired and will be evaluated. If Offeror cannot meet the requirement, or chooses not to respond for any reason, zero (0) points will be awarded for the Section. If Offeror responds, points will be awarded based on predetermined criteria.

Note: Offerors are directed to IDAPA 38.05.01.074.02.a, which allow the designated State official to waive minor informalities. The State also reserves the right to seek clarification on any M, ME or E requirement.

PROPOSAL REVIEW, EVALUATION, AND AWARD TC "5

PROPOSAL REVIEW, EVALUATION, AND AWARD" \f C \l "1" 5.1 Overview

The objective of the State in soliciting and evaluating Proposals is to ensure the selection of a firm or individual that will produce the best possible results for the funds expended.

5.1.1 All Proposals will be reviewed first to ensure that they meet the Mandatory Submission Requirements of the RFP as addressed in Sections noted with an (M) or (ME). Any Proposal(s) not meeting the Mandatory Submission Requirements may be found non-responsive.

5.1.2 Evaluation Criteria

Technical Proposal:

Mandatory Submission Requirements Met Pass/Fail

Business Information (Section 7) 100 points

Organization and Staffing (Section 8) 100 points

Scope of Work (Section 9) 400 points

Cost Proposal:

Cost Proposal and Billing Procedure (Appendix A) 400 points

Total Points 1000 points

5.2 Technical Proposal

5.2.1 The Technical Proposal will be reviewed first on a “pass” or “fail” basis to determine compliance with those requirements listed in the RFP with an (M) or (ME). All Proposals which are determined by the Department, in its sole discretion, to be responsive in this regard will continue in the evaluation process outlined in this Section.

5.2.2 The Technical Proposal will be reviewed, evaluated, and scored by one (1) or more Technical Proposal Evaluation Committee(s).

5.2.3 The scores for the Technical Proposal will be normalized as follows: The Technical Proposal with the highest overall total technical score will receive a score of six hundred (600) points. Other Technical Proposals will be assigned a portion of the maximum score using the formula:

X raw score of Technical Proposal being evaluated highest raw technical score

5.3 Oral Presentations/Demonstrations 5.3.1 Oral demonstrations will not be conducted for this RFP.

5.4 Appendix A - Cost Proposal and Billing Procedure 5.4.1 The Appendix A - Cost Proposal and Billing Procedure will be reviewed first to determine if it meets the mandatory requirements of the RFP. All Proposals which are determined by the Department, in its sole discretion, to be responsive in this regard will continue in the evaluation process outlined in this Section.

5.4.2 The Appendix A - Cost Proposal and Billing Procedure will only be evaluated for Offerors who receive the top three (3) technical scores

5.4.3 The scores for the Appendix A - Cost Proposal and Billing Procedure will be normalized as follows: The cost evaluation will be based on the total cost proposed for required services as itemized in Appendix A. The Proposal with the lowest TWO (2)-YEAR TOTAL will receive a score of four hundred (400). Other Proposals will be assigned a portion of the maximum score using the formula:

X lowest Cost Proposal and Billing Procedure Cost Proposal and Billing Procedure being evaluated

5.5 Responsibility

Pursuant to IDAPA 38.05.01.081, the RFP Lead may, in the State’s sole discretion, conduct a review to determine if the apparent high point Offeror is responsible. As part of the responsibility review, the RFP Lead may:

5.5.1 Require the apparent high point Offeror to provide credit or financial reports to the satisfaction of the Department.

5.5.2 Require the apparent high point Offeror to provide a reference list and contact the Offeror’s references, which may include sending references a reference questionnaire.

5.5.3 Conduct other responsibility reviews at the discretion of the RFP Lead.

Failure to provide requested documentation may result in the Offeror being deemed non-responsible. Nothing herein shall prevent the State from using other means to determine Offeror’s responsibility.

5.6 Award

Award of Contract will be made to the responsive, responsible Offeror whose Proposal receives the highest number of total normalized points.

MANDATORY SUBMISSION REQUIREMENTS TC "6

MANDATORY SUBMISSION REQUIREMENTS" \f C \l "1" A complete response begins with the mandatory items identified in this list and the following Sections. NOTE: THIS CHECKLIST IS PROVIDED AS A COURTESY ONLY; OFFERORS ARE RESPONSIBLE FOR SUBMITTING ALL MANDATORY SECTIONS, ATTACHMENTS, SUBMITTAL ITEMS, ETC., REGARDLESS OF WHETHER THEY ARE IDENTIFIED IN THIS LIST.

(M) State Signature Page: Upload a completed, signed, Attachment 4 -- State Signature Page in the appropriate Question Section of IPRO.

(M) Cover Form: Upload a completed, signed, Attachment 5, Cover Form in the appropriate Question Section of IPRO

(M) Acknowledgement of Amendments: If the RFP is amended, the Offeror must acknowledge each amendment with a signature on the acknowledgement form provided with each amendment. Failure to return a signed copy of each amendment acknowledgement form with the Proposal may result in the Proposal being found non-responsive. See IDAPA 38.05.01.52. Upload a completed, signed, Acknowledgement of Amendments form in the appropriate Question Section of IPRO.

Section 7: Provide a response to all (E) (M) and (ME) Sections, and any other required submittal items.

Section 8: Provide a response to all (E) (M) and (ME) Sections, and any other required submittal items.

Section 9: Provide a response to all (E) (M) and (ME) Sections, and any other required submittal items.

(ME) Appendix A - Cost Proposal and Billing Procedure: Offerors are required to upload their Appendix A – Cost Proposal and Billing Procedure in the Question Section in IPRO in an Excel spreadsheet format.

Technical Proposal: Offerors are required to upload their Technical Proposal in the Question Section in IPRO.

Trade Secret Redactions: If applicable, the Offeror must upload a redacted copy of Technical Proposal and list of Trade Secret redactions, as detailed in Section 3.2.2.

Insurance: Review the required types and levels of insurance—these are mandatory requirements. If you do not already have the required types and levels of insurance, you are strongly encouraged to contact your insurance representative to find out if you will be able to obtain the required insurance. (The Offeror should not purchase additional insurance in reliance of being awarded a Contract). If you are awarded a Contract, failure to provide proof of the required insurance will be grounds for termination of the Contract. DO NOT SUBMIT WITH PROPOSAL.

Business Information TC "7 Business Information" \f C \l "1" 7.1

(E) Business Profile

Provide a profile of your business including Offeror’s business history, description of current service area, and customer base.

7.2

(E) Experience

Describe in detail your knowledge and experience in providing services similar to those required in this RFP.

7.3 Faith-based Organization

If you are a faith-based organization describe how you will:

7.3.1 Segregate Contract funds in a separate account if federal funds;

7.3.2 Serve all participants without regard to religion, religious belief, refusal to hold a religious belief, or refusal to actively participate in a religious practice;

7.3.3 Ensure that State-referred clients’ participation in religious activities, including worship, scripture study, prayer or proselytization, is only on a voluntary basis;

7.3.4 Notify participants of the religious nature of the organization, their right to be served without religious discrimination, their right not to take part in inherently religious activities, their right to request an alternative provider and the process for doing so;

7.3.5 Ensure that Contract funds are not expended on inherently religious activities; and

7.3.6 Comply with applicable terms of 42 CFR Parts 54 and 54a, and 45 CFR 260 and 1050.

Organization and Staffing TC "8 Organization and Staffing" \f C \l "1" Describe your qualifications to successfully complete the requirements of the RFP by providing a detailed response to the following:

8.1

(E) Project Lead

Identify the person who will be the dedicated Project Lead if Offeror is awarded a Contract. Provide a description of the proposed Project Lead’s experience and qualifications. You may submit a resume in response to this Section.

8.2

(E) Key Personnel and Qualifications

Provide a list of key management, customer service and other roles to be used in the fulfillment of the Contract (in addition to the Project Lead). Provide role descriptions, including requisite qualifications and experience of the person(s)/role(s) identified, as well as an explanation of how the person in that role will contribute to the project. Your response should demonstrate the extent to which you have the expertise to accomplish the Scope of Work.

8.3 Subcontractors

If the Offeror utilizes any entity other than the entity submitting the Proposal to provide any of the services required by this RFP, the relationship between the two (2) entities is considered that of a contractor-subcontractor for the purpose of this Section, regardless of whether a relationship is based on an actual written Contract between the two (2).

8.3.1 If you intend to utilize subcontractors, describe the extent to which subcontractors will be used to comply with Contract requirements.

8.3.2 Include each position providing service and provide a detailed description of how the subcontractors are anticipated to be involved under the Contract (including requisite qualifications/experience).

8.3.3 If applicable, provide resumes for those subcontractors who will be managing and or directly providing services under the Contract.

8.3.4 Include a description of how the Offeror will ensure that all subcontractors and their employees will meet all requirements.

8.3.5 Offerors must disclose the location of the subcontractor’s business office and the location(s) of where the actual work will be performed.

8.3.6 If you do not intend to utilize subcontractors, provide a statement to that effect.

Note: The information provided for subcontractors, if any, will be evaluated as part of the Key Personnel and Qualifications section 8.2 above.

SCOPE OF WORK (SOW) TC "9

SCOPE OF WORK" \f C \l "1" All Sections of the SOW are required Contract services. Use this Proposal outline as part of your response to the RFP by restating each Section number and then providing your response. Keep in mind, the evaluators will be scoring your Proposal based on the methodologies proposed and the completeness of the response to each item listed below. Describe how you will meet each requirement marked (ME) Mandatory Evaluated and (E) Evaluated by describing, in detail, your organization’s qualification and experience (rather than simply restating the question or confirming compliance without additional supporting information); as well as how your organization plans to meet SOW requirements detailed in this RFP. The Proposal should address methodologies, pertinent timelines, personnel, activities, and other pertinent information in order to implement the SOW successfully to achieve full compliance with all tasks and deliverables. Offerors must identify any information or resources needed from the Department in order to perform any of the work. By providing a response to this Solicitation, you affirm you agree to and will comply with the following requirements.

I. General Requirements

A. The Contractor must:

1. Comply with all applicable federal statutes, regulations, executive orders, and award conditions, including but not limited to 2 Code of Federal Regulations (CFR) Part 200 and 2 CFR 300, U.S. Department of Health and Human Services (HHS) Grants Policy Statement effective October 1, 2025, and HHS Administrative and National Policy Requirements.

2. Provide services to the Department and must not exercise programmatic, regulatory, or policy authority. The Contractor must not represent itself as an agent of Department or the state of Idaho.

3. Comply with all program-specific rules, mandatory spending caps, and clinical workforce service commitments set forth in the Centers for Medicare & Medicaid Services (CMS) Rural Health Transformation Plan and Program (RHTP) overview https://www.cms.gov/priorities/rural-health-transformation-rht-program/overview, and Notice of Funding Opportunity https://apply07.grants.gov/apply/opportunities/instructions/PKG00291485-instructions.pdf; Terms and Conditions start on page 59.

4. Comply with subaward and executive compensation reporting requirements as required by the Federal Funding Accountability and Transparency Act (FFATA). 2 CFR part 170.

5. Designate a Project Lead responsible for Contract acceptance, amendments, and oversight. The Contract Administrator/Manager must be the primary contact for the Department and must cooperate fully with respect to the direction and performance of the Contract.

6. Designate staff responsible for development and submission of invoices on or before the due date.

7. Notify the Department in writing within three (3) business days of any changes to Contract management or service staff. Key personnel must serve the full Contract term; however, if a key staff member leaves, the Contractor must provide a Department-approved replacement with equal or better qualifications within thirty (30) calendar days of the key staff member’s notification of departure. Key personnel must have a trained backup available to step in during temporary absences.

8. Within fifteen (15) calendar days of the Contract effective date, attend a Contract implementation meeting (in-person or virtual) facilitated by the Department to review Contract requirements and timelines. All costs associated with attendance and participation in the meeting are the sole responsibility of the Contractor.

9. Allow sixty (60) calendar days for CMS review of each submission or re-submission of each deliverable prior to the deliverable due date.

10. Submit a complete budget proposal ninety (90) calendar days before the start of the second fiscal year. The budget must be approved by the Department and CMS.

11. Receive prior written approval from the Department for any deviations from the budgeted services/activities. The Contractor must be financially responsible for costs deemed unallowable or unapproved by the Contract Monitor.

12. As requested by the Department, coordinate with Department staff, other RHTP-funded entities, and key stakeholders in conducting assessments, data collection, evaluation, reporting, and development of deliverables, as applicable to the scope of work, to prevent duplication or overlap of services.

13. In accordance with the “Steven’s Amendment” (https://www.congress.gov/101/statute/STATUTE-103/STATUTE-103-Pg1159.pdf) in the Department of Labor, HHS, and Education and Related Agencies Appropriations Act, the Contractor must not issue any statements, press release, request for proposals, bid solicitations, and other documents describing projects or programs funded in whole or in part with federal money unless it clearly states the following:

a. “This document was supported by the Centers for Medicare & Medicaid Services (CMS) of the U.S. Department of Health and Human Services (HHS) as part of a financial assistance award totaling one hundred eighty-five million nine hundred seventy-four thousand three hundred sixty-seven dollars and eighty-one cents ($185,974,367.81) with one hundred percent (100%) funded by CMS/HHS. The contents are those of the author(s) and do not necessarily represent the official views of, nor an endorsement, by CMS/HHS, or the U.S. Government.”

II. Project Management

A. The Contractor must:

1. Work closely and collaboratively with the Department throughout all phases of the project, ensuring that departmental considerations, priorities, and feedback are fully integrated. In partnership with the Department, the Contractor must develop a comprehensive Project Management Plan to demonstrate how they will meet the Contract deliverables and complete all items within the Scope of Work.

2. Conduct project kickoff meetings and coordinate regularly with the Department and key stakeholders to ensure a unified and informed approach, as requested by the Department.

3. Maintain an up-to-date project timeline and detailed risk logs, incorporating input to proactively identify, assess, and address emerging risks. Status update meetings will be conducted twice a month by the Department, during which the Contractor must present progress, solicit feedback, and adjust project activities as needed and based on the Department’s guidance.

4. Maintain Department-approved robust stakeholder communication plans, developed and executed in close coordination with the Department to ensure consistent and accurate messaging. The Contractor must also coordinate regional engagement activities, ensuring that these efforts reflect priorities and meet the needs of local partners.

III. (E) Statewide and Regional Healthcare Facility Technology Assessments Describe your experience providing services of a similar size and scope in this section. Draft documents can be provided but if they are, they must be included in the technical proposal fifteen (15)-page limit.

A. Assessment Planning and Tool Development – The Contractor must:

1. Design Department-approved assessment instruments for both onsite and remote administration. The assessment instruments must identify at a minimum all items in SOW III.A.3, what and how they are being used in the healthcare facilities.

2. Develop a prioritization methodology for facility sequencing based on factors including but not limited to geographic region, facility type, patient volume, and known risk indicators.

3. Develop a Department-reviewed and approved standardized technology assessment framework including but not limited to surveys, interviews, executive leadership reviews, clinical workflow reviews, etc., that assesses healthcare facilities across the following domains. Required technology categories include:

a. Clinical Technology

i. Electronic Health Records (EHRs)

ii. Electronic Medical Records (EMRs)

iii. Clinical documentation systems

iv. E-Prescribing systems

v. Clinical decision support systems

vi. Computerized provider order entry (CPOE)

vii. Telehealth platforms

viii. Telepsychiatry systems

ix. Telepharmacy systems

x. Remote patient monitoring systems

xi. Virtual nursing platforms

xii. Digital imaging/Picture Archiving and Communication System (PACS)

xiii. Laboratory information systems

xiv. Radiology systems

xv. Pharmacy management systems

xvi. Medication dispensing technology

xvii. Smart infusion pumps

xviii. Bedside monitoring systems

xix. Biomedical equipment interfaces

xx. Intensive Care Unit (ICU) monitoring technology

xxi. Patient portal systems

xxii. Care coordination platforms

xxiii. Referral management systems

xxiv. Artificial Intelligence (AI) Readiness

b. Interoperability and Data Exchange

i. Health Information Exchange (HIE) connectivity

ii. Health Leven Seven/Fast Healthcare Interoperability Readiness (HL7/FHIR)

iii. Application Programming Interface (API) capabilities

iv. Cross-system data sharing

v. Public health reporting integration

vi. Data governance structures

vii. Master patient index capabilities

c. Population Health and Analytics

i. Population health platforms

ii. Data warehouses

iii. Analytics platforms

iv. Dashboards

v. Predictive analytics

vi. Quality reporting systems

vii. Chronic disease management tools

viii. Risk stratification tools

ix. AI readiness

x. Machine learning capabilities

d. Operational and Administrative Technology

i. Revenue cycle management (RCM) systems

ii. AI-enabled revenue cycle management tools: front-end, mid-cycle, and back-end RCM automation

iii. Scheduling systems

iv. Workforce management systems

v. Human resources systems

vi. Enterprise Resource Planning (ERP) systems

vii. Financial management systems

viii. Supply chain systems

ix. Inventory systems

x. Credentialing systems

xi. Contract management systems

e. Emergency Preparedness and Public Health Technology

i. Health Alert Network connectivity

ii. Emergency communications systems

iii. Syndromic surveillance integration

iv. Public health reporting systems

v. Emergency operations coordination technology

vi. Next Generation 911 integration readiness

vii. Disaster recovery capabilities

f. Patient Access and Consumer Technology

i. Mobile health applications

ii. Community digital literacy levels and patient technology adoption barriers

iii. Digital registration/check-in

iv. Self-scheduling platforms

v. Translation technology

vi. Accessibility technology

vii. Remote access tools

viii. Patient communication systems

ix. Texting and notification systems

g. Workforce and Training Technology

i. Learning management systems

ii. Simulation technology

iii. Workforce training platforms

iv. Tele-education systems

v. Remote workforce capabilities

vi. Technology support staffing models

vii. Provider/facility technical assistance capacity and training absorption gaps

viii. Hardware lifecycle, equipment sustainability, and vendor support timelines beyond the five (5)-year project period

ix. EHR data migration readiness: legacy system condition, data quality, and estimated migration complexity

x. CMS Interoperability Framework current compliance status and readiness gaps per facility

xi. Payer contracting readiness and revenue sustainability maturity: analytics tools, risk stratification, and care coordination capabilities

h. Other proposed technologies and technology supports must be reviewed and approved by the Department before proceeding.

B. Assessment Execution – The Contractor must:

1. Execute assessments at eligible rural healthcare facilities statewide. Where a facility has been subject to a prior technology or needs assessment, the Contractor must obtain and review that assessment and, where findings remain current and applicable, must incorporate those findings in lieu of conducting a duplicative full assessment.

2. Document, and provide to the Department, the basis for any determination that existing assessment data is not sufficient to satisfy assessment requirements.

3. Assess an estimated minimum of two hundred (200) facilities, prioritizing Critical Access Hospitals (CAHs), Rural Health Clinics (RHCs), Rural Emergency Hospitals, Federally Qualified Health Centers (FQHCs), tribal health organizations, pharmacies, EMS agencies, long-term care facilities and dialysis centers in rural areas as defined by the Attachment 9 -- Idaho RHTP Eligibility Map. Other healthcare facilities may be assessed with prior Department approval.

a. The Contractor must engage facility leadership, Information technology staff, clinical staff, and administrative personnel during each assessment.

4. Document findings using the Department-approved standardized tools and scoring methodology.

5. Define and identify critical, high, medium, and low priority gaps for each facility.

IV. (E) Shared Infrastructure Strategy and Framework Development Describe your experience providing services of a similar size and scope in this section. Draft documents can be provided but if they are, they must be included in the technical proposal fifteen (15)-page limit.

A. Based on assessment findings, the Contractor must develop a shared technology infrastructure strategy enabling smaller facilities to pool resources, reduce Information Technology (IT) costs, and build sustainable, cooperative technology capacity.

1. Shared IT Service Model – The Contractor must:

a. Design a shared IT service model that identifies opportunities for regional collaboration, including shared telehealth hubs, regional data centers, and pooled IT support.

b. Evaluate hub-and-spoke telehealth deployment configurations: identify facilities suited to serve as regional hubs and recommend spoke arrangements for connected satellite sites.

c. Develop a provider-specific outreach and engagement strategy to maximize facility participation rates, identifying communication channels and messages rural providers are most responsive to.

d. Develop governance recommendations for shared service arrangements, including cost-sharing frameworks, service-level agreements, and decision-making structures.

e. Identify existing regional partnerships (e.g., Northwest Hospital Alliance, Idaho Healthcare Coalitions, CAH integrated networks, etc.) and recommend how they can serve as anchors for shared infrastructure.

f. Analyze cost-benefit scenarios for shared versus facility-level infrastructure investments.

B. Interoperability Standards Documentation – The Contractor must:

1. Develop interoperability specifications for shared infrastructure components, aligned with CMS Interoperability Framework, Assistant Secretary for Technology Policy/Office of the National Coordinator (ASTP/ONC) criteria, and Trusted Exchange Framework and Common Agreement (TEFCA) https://healthit.gov/policy/tefca/ requirements.

2. Provide the Department Contractor-recommended technology standards and minimum specifications for network infrastructure, endpoints, EHR configurations, and telehealth platforms.

V. Deliverables

A. The Contractor must deliver, at a minimum:

1. The Project Management Plan, due within thirty (30) calendar days after the Contract effective date, and monthly updates thereafter.

2. A stakeholder engagement plan and communication and engagement strategy, to include how the Contractor must engage stakeholders and the healthcare facilities the Contractor must assess within forty-five (45) calendar days after the Contract effective date.

3. The assessment methodology and detailed assessment framework and tools, to include the process the Contractor must use to complete the assessments, within sixty (60) calendar days after the Contract effective date.

4. A technology inventory database and statewide inventory of technology systems and assets, to include all types of technology available to be utilized by facilities, and what is currently being used statewide, within ninety (90) calendar days after the Contract effective date.

5. Data files and dashboard, to include all of the data the Contractor collects through the assessments conducted.

6. Raw and summarized assessment data, to include all raw assessment results and all summarized assessment results.

VI. (E) Quality Assurance Submit a draft of the Quality Assurance Plan with your proposal.

A. The Contractor must provide and maintain a Quality Assurance Plan that documents the processes to be used in ensuring the quality of contracted services.

1. The Quality Assurance Plan must address all activities outlined in the scope of work and include methods for monitoring internal systems and processes and utilizing quality assurance information to improve services.

2. The Quality Assurance Plan must be finalized in conjunction with the Department within thirty (30) calendar days after the Contract effective date.

VII. Data Privacy, Security (does not include cybersecurity), and Health Insurance Portability and Accountability Act (HIPAA) Compliance

A. The Contractor must assess facility-level technology inventories and interact with healthcare information systems that may involve protected health information (PHI). The Contractor must:

1. Execute a Business Associate Agreement (BAA) with the Department each facility prior to commencing any assessment activities involving access to facility systems or PHI.

2. Comply with all applicable HIPAA Privacy and Security Rule requirements and document data handling obligations for all facility-level information collected during assessment activities.

3. Implement and maintain administrative, physical, and technical safeguards to protect all assessment data from unauthorized access, use, or disclosure. Data must be stored in encrypted format and destroyed or returned to the Department upon Contract expiration.

4. Notify the Department within twenty-four (24) hours of any confirmed or suspected breach of assessment data or unauthorized access to facility systems.

VIII. Transition Plan

A. The Contractor must:

1.

Complete all project authorizations signed and initiated prior to the expiration of the Contract. No new project authorizations will be developed within sixty (60) calendar days of the Contract expiration without written approval of the Contract Monitor.

2.

Complete all project-related documentation and deliver it to the Department no later than thirty (30) calendar days prior to Contract expiration.

3.

Participate in a minimum of two (2) structured knowledge transfer meetings with the incoming contractor or Department staff during the final ninety (90) calendar days of the Contract, if applicable. Knowledge transfer must include known issues, vendor relationships, and reporting obligations.

4.

Provide and maintain a Transition Plan that complies with the requirements of the Contract. The objectives of the Transition Plan are to minimize disruption of services provided to the Department and to provide for orderly and controlled transition of the Contractor's responsibilities to a successor if the Contractor cannot complete the responsibilities of the Contract. The final Transition Plan must be negotiated with Department prior to Contract expiration.

5.

Submit final invoices to the Department no later…