13-RFP 26-07045FinalDocument.pdf

Request for Proposal Rev. 01-13-2026

Request for Proposal # 26-07045

Electronic Health Record System

10801 6th Street Rancho Cucamonga, CA 91730

This RFP and any ensuing Addenda are available at the following link:

http://iehp.bonfirehub.com

NOTE: BIDDERS ARE RESPONSIBLE TO READ ALL INFORMATION THAT IS STATED IN THIS

REQUEST FOR PROPOSAL AND PROVIDE A RESPONSE AS REQUIRED

http://iehp.bonfirehub.com/

Timeline

1. The following timeline is based on IEHP’s requirements and will be strictly adhered to unless modified by written addendum:

Date: Description:

5/6/2026 RFP release date 6/3/2026 Bidder Questions Due (5:00 p.m. PT) 6/19/2026 Bidder’s Proposals Due (2:00 p.m. PT) TBD Bidder Demonstrations

IEHP anticipates holding Bidder Presentations/Demonstrations as indicated in the RFP Timeline above. IEHP may choose to hold presentations/demonstrations with all, some or no Bidders, at its sole discretion, pursuant to this RFP.

2. The period of performance anticipated for this RFP shall be for an initial term of one

(1) year. At the end of the initial term, IEHP shall have the option to renew the Agreement for up to four (4) additional consecutive one (1) year period(s), upon written notice. This RFP does not commit IEHP to award a contract, and there is no obligation by IEHP to purchase any specified amount of goods or services. IEHP will award a contract, if any, in its best interest and based on a proposal that best meets its needs as set forth herein.

3. IEHP reserves the right to award to multiple bidders, based on IEHP’s needs, at IEHP’s sole discretion.

TABLE OF CONTENTS

A. SOLICITATION INTRODUCTION

1. Background of IEHP

2. Key Principles

3. Primary Goals

4. Program Objectives

5. Key Selection Criteria

6. Program Outcomes

7. Target Population/Historical Information

B. PROPOSAL COMPONENTS

Instructions Proposal Guidelines Bidder Acknowledgements Required Documents Required Data Company Profile Company Evaluation Criteria Scope of Services Demonstration Cost Proposal/Pricing Narrative Financial Documents Security Questionnaires Exhibit A: RFP Bidder Terms and Conditions Exhibit B: IEHP Standard Contract Terms Exhibit C: IT Security Documents

1. Background of IEHP

Inland Empire Health Plan (IEHP) is a local public entity of the State of California and is a rapidly growing Medi-Cal and IEHP DualChoice (HMO D-SNP [Dual Eligible Special Needs Plans]) health plan in California. Since September of 1996, IEHP has consistently focused on our mission: “We heal and inspire the human spirit”. As a result of the Healthcare Reform and participation in the California Coordinated Care Initiatives, IEHP grew to over 1 million members. With a provider network of over 7,500 providers and more than 3,200 employees, we now serve more than 1.4 million residents of the Riverside and San Bernardino counties who are enrolled in Medi-Cal, D-SNP, or Covered California.

IEHP’s Membership totals as of March 2026 are listed in the table below:

Line of Business Member Count Medi-Cal 1,367,174

D-SNP 38,766

Covered California 40,202 Total Membership 1,446,142

2. Key Principles

This RFP contains a list of requirements for RFP # IEHP-RFP-26-07045 Electronic Health Record System on behalf of IEHP. IEHP’s Procurement Department is soliciting responses from qualified vendors to address the stated requirements of this RFP. A “Qualified Bidder”, for the purpose of this RFP, is one that can reliably and independently provide the required services to IEHP for the entire term of the agreement.

3. Primary Goals

The primary goals of the (EHR solution) are to contract with a vendor to implement a fully integrated, cloud-based ambulatory electronic health record (EHR) solution that will support its envisioned scope of care as it expands over the coming years.

4. Program Objectives

The objectives of contracting with a vendor for EHR Solution are to implement a system that includes full range of support for Electronic Medical Records, Practice Management, Revenue Cycle, Telehealth, Mobile and Patient Portal functionality, all within an integrated ambulatory ecosystem. Vendor must also have an integrated, effective and transparent RCM (Billing & Collections) service offering

A. Solicitation Introduction

5. Key Selection Criteria

At the discretion of the Evaluation Team, 65 points will be allocated between the scope and company scores, 30 points will be assigned to price, and 5 points will be given for local preference. If demonstrations or interviews are conducted, an additional 10 points will be allocated to demo scores.

IEHP reserves the right, at its sole discretion, to award the contract to the responsive and responsible bidder whose proposal offers the best value to IEHP. Best value will be determined through a comprehensive evaluation of both price and non-price factors, including technical approach, experience, methodology, and other criteria specified in this RFP.

Additional details on evaluation criteria can be found in Exhibit A: RFP Bidder Terms and Conditions.

6. Program Outcomes

The outcome expectation of the successful program/project is upon successful implementation of the Care Division Electronic Health Record (EHR) Program, Care Division will have established the digital infrastructure necessary to support efficient clinical workflows, streamlined documentation, and robust data reporting. The program will position Care Division to deliver coordinated, high-quality care across its physical, mobile, and virtual care settings, while enabling proactive population health management, SDOH screening, and complex care coordination. Ultimately, the EHR implementation will lay the foundation for a scalable, integrated care delivery model capable of growing alongside Care Division's expanding member population and operational footprint.

7. Target Population/Historical Information

This initiative marks a new operational direction for IEHP, which has not previously operated its own medical clinics. The Care Division’s ambulatory clinic model introduces new workflows, data requirements, and internal processes, and is expected to scale across physical sites, mobile units, and virtual care to serve a growing population.

8. FDR Status –NO

The services outlined in this RFP are classified as non-delegated administrative or healthcare services. The contractor will not be recognized as a first-tier, downstream, and related entity (FDR) vendor, and therefore is not subject to the associated requirements. However, if the status changes, as determined by IEHP, the contractor will be required to comply with all relevant FDR requirements.

9. Piggyback Provision

Other public agencies, municipalities, and government entities within the State of California may, at their discretion and with the awarded vendor’s consent, utilize this Request for Proposal (RFP) and any resulting agreement. Any such use shall be arranged directly between the vendor and the participating entity, independent of IEHP. IEHP does not assume any responsibility or liability for contracts entered into by other entities under this provision.

B. Proposal Guidelines

Instructions:

1. This document is provided to Bidders as a reference. Bidders are not required to enter answers to Bidder questions in this document. All required questions will be found under the associated solicitation number on the Bonfire portal at http://iehp.bonfirehub.com.

a. All requested documents from each section shall be uploaded to their corresponding document slot at http://iehp.bonfirehub.com.

b. All questions from each section shall be answered by bidders in the corresponding questionnaire and/or bid table located at http://iehp.bonfirehub.com.

2. Follow the instructions in each section of this RFP.

3. All Proposals must include a detailed description of each proposed service to be provided.

4. Responses that do not comply with submission instructions may be delayed or not accepted for review.

5. Bidders that do not follow the bid instructions found in the Bidder Terms and Conditions document, attached hereto as Exhibit A, may be found to be “non-responsive” and disqualified from the bid process, at the sole discretion of IEHP.

6. A duly authorized officer of the organization must sign your RFP response.

7. IEHP reserves the right to modify or terminate the RFP process at any time. IEHP may amend or modify the project scope of services prior to the award of a contract(s), as necessity may dictate, reject any and all proposals submitted (and rebid, if necessary), accept any or all proposals submitted, negotiate with any qualified source, or cancel, in part or in its entirety, this RFP if it is in the best interest of IEHP, at IEHP’s sole discretion.

8. IEHP may keep submissions and negotiations confidential until the Governing Board approves the final contract and/or a contract is issued. Proposals may contain financial statements or other information which constitute a trade secret. In order to protect such data from disclosure, please identify the pages by clearly marking the applicable pages as confidential.

9. Upon receipt of this RFP, recipients are expected to read and understand the service priorities and requirements that have been defined by IEHP. Opportunity will be http://iehp.bonfirehub.com/ https://iehp.bonfirehub.com/ given to ask questions and receive clarification. The character and operating principles of the successful vendor are important to IEHP. The following sections ask questions about the history and purpose of the vendor’s company. Please answer the specific questions. If additional information would be informative to IEHP, please add it to the last question in each question set.

10. Each proposal will be reviewed by IEHP’s Procurement team to determine if the proposal is responsive to the submission requirements outlined in the RFP. A responsive proposal, for the purpose of this RFP, is one which follows the requirements of this RFP, includes all documentation, is submitted in the format specified in this RFP document, is submitted on time, and has the appropriate signatures required on each document. Failure to comply with these requirements may result in the proposal being deemed non-responsive and, therefore, rejected, at the sole discretion of IEHP.

11. An Evaluation Committee comprised of IEHP stakeholders will review each bidder’s responses to the questions contained in this RFP. If the respondent cannot represent and warrant the business requirements listed herein, the proposal may be rejected, at the sole discretion of IEHP.

12. The Evaluation Committee will review, evaluate, and score the proposals. The best response(s) may be recommended for another round of evaluation at IEHP’s sole discretion. IEHP reserves the right to conduct as many rounds of evaluations as it deems to be reasonable or necessary in the public interest. Each round of evaluation may result in modification of scores, further clarification or addenda being issued, and changes in the RFP process.

13. Upon evaluation of the criteria and the rating and ranking, the Evaluation Committee may choose to conduct an oral presentation/demonstration with any bidder(s). Upon completion of the oral presentations/demonstrations, the Evaluation Committee members may re-evaluate, re-score and/or re-rank the proposals remaining in consideration.

14. The price proposal will be evaluated relative to the combination of the technical proposal, including an evaluation of how well it matches the bidder’s understanding of IEHP’s needs described in this Solicitation, the bidder’s assumptions, and the value of the proposed solution and/or services. The pricing evaluation is used as part of the evaluation process to determine the bidder that will provide the best overall value to IEHP.

15. IEHP may direct negotiations with its first-choice bidder, negotiations with multiple bidders, and/or may request for best and final offers. The discussions may include price and conditions attendant to price. This RFP includes IEHP’s standard, required contract terms, attached hereto as Exhibit B, which IEHP expects to be incorporated into a final contract form together with other terms and conditions. Failure to accept IEHP’s standard terms may result in the bidder being removed from consideration.

16. Notwithstanding the foregoing, if IEHP believes IEHP and the said bidder(s) cannot reach agreement on a contract, IEHP shall exercise its right to terminate or suspend negotiations and may begin negotiations with the other bidder(s). This process may continue until a contract acceptable to IEHP has been executed or all proposals are rejected. No bidder shall have any rights against the IEHP arising from such negotiations or termination thereof.

17. A bidder’s protest of any IEHP decision to eliminate the bidder from further consideration for an award, or to award a contract to another bidder, shall be made in writing and submitted to IEHP by 5:00 p.m. PT on the fifth (5th) day following posting of Notice of Intent to Award, or posting Notice of Award of the contract, whichever occurs first. The written protest shall be submitted to procurement@iehp.org. The written protest shall fully describe each and every basis for protest and shall describe the manner in which IEHP failed to act within its discretion or abused its discretion.

For avoidance of doubt, IEHP’s intent is to reserve its discretion under this RFP to maximum amount allowed by law, and this RFP shall be construed in favor of reserving IEHP’s discretion in all circumstances. Failure to timely and completely submit a protest shall constitute a final and conclusive waiver of any and all rights to bring a legal action to challenge an award of a contract under this RFP. IEHP will not consider untimely protests or protests where the bidder failed to timely object under Section 1 of the Bidder Acknowledgements below. All bidders expressly acknowledge that IEHP may proceed with awarding and implementing a contract under this RFP while any protest, or legal action related to a protest, is pending.

mailto:procurement@iehp.org

1. Clarifications, Exceptions, or Deviations

a. All bidders must describe any exceptions or deviations from the requirements of this RFP in Question Set 1 of Questionnaire Q-59CH Each clarification, exception, or deviation must be clearly identified. If your firm has no clarifications, exceptions, or deviations, include a statement to that effect.

IEHP’s standard contract terms are outlined in the RFP Bidder Terms and Conditions document incorporated herein by reference, and attached as Exhibit A.

b. Any objection to the prescribed procedures, terms, conditions, or requirements set forth in this RFP or any component document must be submitted to IEHP as part of, or contemporaneously with, the bidder’s proposal. Failure to timely submit an objection, or failure to submit a proposal, constitutes a final and conclusive waiver of any and all rights to raise such objection for any purpose, including, without limitation, any protest or legal action challenging an award of a contract under this RFP.

c. All bidders must specify any additional documents that IEHP will need to sign along with the standard Agreement (e.g., appendices, requirements documents, third-party agreements, service level agreements, compliance certifications) in Question Set 1 of Questionnaire Q-59CH. These documents must also be uploaded to the “Bidder Attachments” document slot.

d. All Bidders must specify any additional costs that IEHP will be required to pay outside of the standard agreement (e.g., third-party fees) in Question Set 1 of Questionnaire Q-59CH. These costs should also be included in Bid Table BT-

09AL.

2. Evidence of Insurability/Business Licenses

a. All bidders must submit evidence of required insurance in the corresponding document slot on the Bonfire portal. An Acord cover page will suffice for submission. If awarded the contract, the bidder will have ten (10) calendar days to provide all required insurance documentation, including a certified endorsement naming IEHP as additionally insured.

b. Bidders must also certify possession of all current required licenses or certifications. Do not purchase additional insurance until this RFP has been awarded. Provide a copy of your current business license or other applicable licenses. Failure to provide the required document may be grounds for disqualification of bidder from the RFP process, at IEHP's sole discretion.

Bidder Acknowledgements

3. IEHP General Compliance Requirements for Contractors

a. If the services provided under this RFP are designated as delegated administrative or healthcare services, the contractor will be considered a First-Tier, Downstream, and Related Entity (FDR) vendor. IEHP requires all temporary FDR staff and contractors to participate in General Compliance Training as mandated by State and Federal regulations.

b. The training includes a quiz to assess knowledge of compliance topics and covers the following objectives:

• Understand the purpose and functions of a Compliance Program

• Learn the 7 Elements of an Effective Compliance Program

• Understand IEHP’s Fraud, Waste, and Abuse and HIPAA Programs, including reporting requirements and procedures for suspected non-compliance.

4. IEHP Background Check Requirements for Bidders

IEHP may require all individuals assigned to provide services under this RFP to undergo a background check prior to commencement of work, at the contractor’s expense, including any checks required by law.

5. Out of Country Services Notice

a. IEHP will only consider service offerings within the continental United States, defined as the 49 States including Alaska and the District of Columbia; excluding Hawaii.

b. Proposed solutions that create, transmit, receive and/or maintain IEHP data must always reside within the United States.

c. IEHP’s data must always remain in the United States.

d. All persons, electronic processes, information systems, and devices accessing

IEHP systems or data must be physically located in the United States.

6. Executive Order N-6-22 – Russia Sanctions

On March 4, 2022, California Governor Gavin Newsom issued Executive Order N-6- 22 (the EO) regarding Economic Sanctions against Russia and Russian entities and individuals. “Economic Sanctions” refers to sanctions imposed by the U.S.

government in response to Russia’s actions in Ukraine, as well as any sanctions imposed under state law. The EO directs all California state agencies and departments to terminate contracts with, and to refrain from entering any new contracts with, individuals or entities that are determined to be a target of Economic Sanctions. All contractors and grantees are obligated to comply with the Economic

Sanctions. Accordingly, should the State of California (the State) or IEHP determine Contractor is a target of Economic Sanctions or is conducting prohibited transactions with sanctioned individuals or entities, that shall be grounds for termination of this Agreement. Contractor shall be provided with advance written notice of such termination, allowing Contractor at least thirty (30) calendar days to provide a written response. Termination shall be at the sole discretion of the State or

IEHP.

7. Registration with California Agencies

All bidders must comply with California business registration and standing requirements including:

a. Secretary of State (SOS): Register and maintain active status for your business entity (corporation, LLC, partnership) to legally operate and contract in California.

b. Franchise Tax Board (FTB): Register with the FTB, ensure good standing (i.e., no outstanding state tax liabilities), and complete any required filings to participate in public procurement.

c. IEHP Procurement Compliance: Review and adhere to IEHP’s procurement procedures as documented in the IEHP Purchasing Policies & Procedures Manual, available here: IEHP Purchasing Policy & Procedures Manual PDF

This requirement ensures bidders are authorized and fully compliant with statutory and IEHP-specific procurement rules.

https://www.iehp.org/content/dam/iehp-org/en/documents/procurement/2025/Purchasing%20Policy%20and%20Procedure%20Manual.pdf

All required documents listed below shall be uploaded to their corresponding document slot in the Requested Information section at http://iehp.bonfirehub.com.

Note: Failure to provide the required documents listed below at time of bid may be grounds for disqualification of bidder from the RFP process, at IEHP's sole discretion.

1. Principal Certification Binding Bidder’s Response (IEHP-provided form)

2. Certification of Non-Debarment (IEHP-provided form)

3. Non-Collusion Declaration (IEHP-provided form)

4. Local Preference Affidavit (If applicable – IEHP-provided form)

5. Contractor’s Certificate Regarding Workers’ Compensation (IEHP-Provided form)

6. Acknowledgment of Non-Negotiable Contract Terms (IEHP-Provided form)

7. Company W-9 Form listing company’s Tax Identification Number (TIN)

8. Evidence of Insurability (ACORD Certificate of Insurance)

9. Business License(s)

10. Proof of Registration: Documentation verifying corporate registration with the

California Secretary of State or if not a corporation, proof of tax registration with the California Franchise Tax Board.

11. Credentials/Certifications/Licenses Document

12. Account Management Narrative

13. List of three (3) contracts of similar value awarded to your company in the past three

(3) years. Include the year, type of services, dollar amounts, services provided, location, contracting company, contact name, and phone number.

14. Policy and Procedures document detailing Bidder’s background checking procedures and the name of any external company utilized to perform this service.

15. Pricing Narrative

16. Redacted Pricing Narrative

17. Financial Statements

18. IEHP Security Risk Assessment

19. Data Sharing Assessment

20. Vendor Security Documents Checklist

21. Bidder’s Security Documents

22. Sample Standard Reports

23. Sample Proposed Document

24. Annual Report for publicly traded companies, or if privately held, details of financial stability.

25. Bidder’s Standard Agreement Template, including detailed pricing and Scope of

Work (for consideration). If not available, include a detailed proposal on Bidder’s letterhead including detailed pricing and Scope of Work (for consideration).

26. References (Questionnaire Q-78MP)

27. Cost Proposal (Bid Table BT-09AL) and (BT-68AJ)

28. Company Profile and Evaluation Criteria (Questionnaire Q-59CH)

29. Bidder Response Questions (Questionnaire Q-15QV)

Required Documents

All required information listed below must be provided in the Requested Information section at http://iehp.bonfirehub.com.

Note: Failure to provide the required information at the time of bid submission may result in disqualification from the RFP process at IEHP's sole discretion.

1. Ownership and Campaign Contributions

IEHP is a public agency with a Board of Directors composed of elected officials and public members. Under applicable law, elected officials are restricted from voting on any action concerning a contract if the contractor’s owners have made campaign contributions of $250 or more within the previous 12 months. To assist in compliance, please provide:

a. The names of all company owners

b. Disclosure of any campaign contributions made to IEHP Board members or elected officials within the past 12 months

2. Exclusions from State and Federal Programs

a. In accordance with 42 C.F.R. §§ 438.610, 422.503 (b)(4)(vi)(F), 423.504 (b)(4)(vi)(F) and California Welfare and Institutions Code §§ 14043.6 and 14123, IEHP is prohibited from employing, contracting, or issuing payments to an individual or entity that is excluded, ineligible, or terminated from participation in State and Federal health care programs.

b. Contract awards are contingent upon the bidder, its principals’ and subcontractors’, eligibility to participate in State and Federal health care programs.

c. Bidders must certify that it or any of its subcontractors do not appear on State and Federal exclusionary lists in the Requested Data section of their response on the Bonfire portal.

3. DUNS Number Provide your company’s DUNS (Data Universal Numbering System) number.

Required Data

This section of the proposal is designed to establish the bidder as an entity with the ability and experience to operate the program or provide goods and/or services as specified in the RFP. The Company Profile should be concise and clear, including descriptive information regarding service delivery. All Bidders shall answer these questions in Question Set 2 of Questionnaire Q-59CH, unless specifically stated otherwise below. Questions that also require the upload of a (Required Document) to the associated document slot are noted.

Questions that require an answer in the form of (Required Data) are also noted.

2.1 Company Name and Corporate Structure:

2.1.1 Business name and legal business status (i.e., partnership, corporation, etc.).

2.2 Company overview related to RFP services or activities performed, including:

2.2.1 IEHP is a public agency with a Board of Directors composed of elected officials and public members. The elected officials are restricted from voting on any action concerning a contract whose owners have made a campaign contribution of $250 or more in the previous 12 months. To assist them in their decision-making process, please indicate the owners of the company, and if any contributions were made to the Elected Officials.

2.2.2 Company hierarchy (President, Vice President, Company Officers, etc.) and an organizational chart. The organizational chart shall clearly identify all staff members that will provide services under this contract. Upload this document to the corresponding document slot on Bonfire. (Required Document)

2.2.3 Number of years in business under the present business name, as well as prior business names, and the number of years of experience providing the proposed, equivalent, or related services.

2.2.4 Location of the office from which the work under this contract will be provided, and the staff allocation at that office.

2.3 Provision of Services:

2.3.1 Please provide a detailed response discussing how bidder plans on providing the services requested in this RFP; specifically, whether services will be provided by bidder’s own forces, subcontractors.

2.4 Financial Interests:

2.4.1 Please indicate whether the Bidder holds controlling or interests in any other organization or is owned or controlled by any other person or organization. If none, please state N/A. Governmental agencies are exempt from this requirement.

Company Profile

2.4.2 Provide any financial interests in any other business. Individuals who are personally performing the contracted services and governmental agencies are exempt from this requirement.

2.4.3 Please indicate if the Bidder is privately or publicly held. If private, please provide details of financial stability. If public, please provide ticker symbol and copy of your most recent annual report.

2.5 Company Structure/Staffing:

2.5.1 Please describe any organizational changes (mergers, acquisitions, divestitures) that have occurred in the past five (5) years.

2.5.2 Please indicate whether Bidder has organizational changes (mergers, acquisitions, divestitures) planned within the next five (5) years.

2.5.3 Please indicate whether Bidder has any layoffs, or personnel expansions planned within the next five (5) years.

2.6 Legal:

2.6.1 Provide a detailed explanation of any litigation involving the Bidder or any principal officers thereof in connection with any contract within the last five (5) years. Is your firm, or the principals corresponding with your firm, under investigation, being sued, suing, or affiliated in any lawsuit or alternative dispute resolution with any governmental agency? If none, state N/A.

2.6.2 Has your company ever been or are you currently subject to any federal or state regulatory enforcement action including but not limited to exclusion and/or suspension from participation in a federal program?

2.6.3 List the officers of your organization who are authorized to negotiate the agreement with IEHP if awarded, and their positions within your organization.

2.6.4 Provide details of any failure or refusal to complete a contract. If none, that must be stated.

2.6.5 State whether your company, or the principals corresponding with your company, are under investigation, being sued, suing, or affiliated in any lawsuit or alternative dispute resolution with any governmental agency. If so, please provide details.

2.7 Certification of Non-Debarment: (Required Document)

2.7.1 IEHP receives Federal and State funds. All Bidders must sign and submit the Certification of Non-Debarment document provided by IEHP in Bonfire that verifies that the bidder is not listed on any of the exclusion lists notated in the section below.

If awarded a contract, awarded vendor must notify IEHP immediately if debarred at any time during the contract period.

a. The Department of Health & Human Services (DHHS), Office of Inspector General (OIG), and List of Excluded Individuals and Entities (LEIE). Please visit https://exclusions.oig.hhs.gov.

b. General Services Administration (GSA), and the System for Award Management (SAM.gov). Please visit https://www.sam.gov.

c. California Department of Health Care Services (DHCS), and Medi-Cal Suspended and Ineligible Provider List (S&I List). Please visit https://mcweb.apps.prd.cammis.medi-cal.ca.gov/references/sandi.

d. Medicare Opt-Out List. Please visit https://data.cms.gov/tools/provider-opt-out-affidavits-look-up-tool.

2.7.2 In accordance with 42 C.F.R. 438.610, 422.503 (b)(4)(vi)(F), 423.504 (b)(4)(vi)(F) and California Welfare and Institutions Code, Section 14043.6 and 14123, IEHP is prohibited from employing, contracting, or issuing payments to an individual or entity that is excluded, ineligible, or terminated from participation in State and Federal health care programs. Contract awards are contingent upon the bidder, its principals’ and subcontractors’, eligibility to participate in State and Federal health care programs.

2.7.3 Bidders must certify that it or any of its subcontractors do not appear on State and Federal exclusionary lists in the Requested Data section of their response on Bonfire.

2.8 Financial Stability:

2.8.1 Please detail your insurance coverage, including the name of the carrier and coverage level for General Liability.

2.8.2 Please detail your insurance coverage, including the name of the carrier and coverage level for Tech Errors & Omissions (E&O).

2.8.3 Please detail your insurance coverage, including the name of the carrier and coverage level for Cyber Crime Insurance

2.8.4 Please provide your revenue for last five (5) fiscal years.

2.8.5 Please provide your profit/(loss) for last five (5) fiscal years.

https://exclusions.oig.hhs.gov/ https://www.sam.gov/ https://mcweb.apps.prd.cammis.medi-cal.ca.gov/references/sandi https://data.cms.gov/tools/provider-opt-out-affidavits-look-up-tool https://data.cms.gov/tools/provider-opt-out-affidavits-look-up-tool

2.8.6 Please provide your company ratings (i.e., A.M. Best, Better Business Bureau, etc.).

2.8.7 Please provide your annual R&D budget for the last five (5) fiscal years (break out by product offerings).

2.8.8 Explain how your company is planning to meet the increase in demand for your product (including implementation, training, and support) over the next five (5) years.

2.9 Eligibility to Participate in Federal and State Health Care Programs (Required Data)

2.9.1 In accordance with 42 C.F.R. 438.610, 422.503 (b)(4)(vi)(F), 423.504 (b)(4)(vi)(F) and California Welfare and Institutions Code, §§ 14043.6 and 14123, IEHP is prohibited from employing, contracting, or issuing payments to an individual or entity that is excluded, ineligible, or terminated from participation in State and Federal health care programs. Contract awards are contingent upon the bidder, its principals’ and subcontractors’, eligibility to participate in State and Federal health care programs.

Bidders must certify that they or any of its subcontractors do not appear on State and Federal exclusionary lists in the Requested Data section of their response on Bonfire.

Company Evaluation Criteria

This section of the proposal is designed to further establish the Bidder as an entity with the ability and experience to operate the program or provide goods and/or services as specified in the RFP. The Company Profile should be concise and clear, including descriptive information regarding service delivery. All Bidders shall answer these questions in Question Set 3 of Questionnaire Q-59CH, unless specifically stated otherwise below. Questions that also require the upload of a (Required Document) to the associated document slot are noted.

3.1 Differentiators

3.1.1 What do you consider to be your company’s strengths, and how do you see your company as differentiated from other Bidders?

3.1.2 Is there any other information you would like IEHP to know about your company including value-added services?

3.2. Account Management Team (Required Document)

3.2.1 In the corresponding document slot on Bonfire, please provide the name(s) and general background(s) of each member of your account management team that will be assigned to IEHP. Include the information below:

• Functional area to which each person reports

• Years of service with your organization

• Total years of experience with commercial product implementation and operations

• Number of public entity accounts currently handled

• General size of the accounts (in terms of number of employees)

3.3 Organizational Information:

3.3.1 Provide a summary of the work plan and/or methodology and physical resources (staff and equipment) your company will commit to ensure successful services are provided under this RFP.

3.3.2 Will IEHP have a dedicated team assigned throughout the implementation? If so, who? Provide the organizational structure and experience for each team member, if not outlined above.

3.3.3 How would the account service team be structured after the implementation?

3.3.4 What is your company’s Mission Statement?

3.3.5 Summarize your company’s billing procedures.

3.3.6 What office will support IEHP?

3.3.7 Please indicate your company’s total number of employees this year and last year.

3.3.8 Please indicate your company’s total number of contractors this year and last year.

3.4 Administration:

3.4.1 Describe any customer and/or member services available on-line.

3.4.2 Do you have a customer service department? If so, what is the phone number, and the hours of operation?

3.4.3 Please describe how your customer service department is organized. Would IEHP receive a dedicated team?

3.5 Experience:

3.5.1 Describe your company’s experience/history with providing the services requested in this RFP.

3.5.2 Describe your company’s experience with Health Maintenance Organizations.

3.5.3 Describe your company’s relationship/experience with governmental regulators (e.g., Department of Health Services, Department of Managed Healthcare, and the Centers for Medicare and Medicaid Services).

3.6 Awarded Contracts: (Required Document)

3.6.1 In the corresponding document slot, provide a list of three (3) contracts of similar value awarded to your company in the past three (3) years. Include the year, type of services, dollar amounts, services provided, location, contracting company, contact name, and phone number.

Scope of Services

Summary of Services The following criteria will be required of the awarded vendor(s):

Project overview:

Care Division EHR Platform Requirements

Care Division, the care delivery arm of Inland Empire Health Plan (IEHP), is seeking a fully integrated, cloud-based ambulatory platform that unifies Electronic Health Records (EHR), Practice Management, Revenue Cycle Management (RCM), Telehealth, Mobile capabilities, Patient Portal functionality, and population health tools into a single enterprise ecosystem.

The selected solution must be proven to operate at scale in large, multisite ambulatory environments and must support day one operational readiness as well as long term growth.

Operational Scale and Complexity

The platform must reliably support an enterprise level care model that includes:

• 10+ ambulatory clinic locations across a large geographic region

• Multiple mobile and telehealth diagnostic units serving dispersed communities

• A robust virtual care service line for scheduled and on-demand encounters

Workforce and Care Model Support

The solution must accommodate:

• 150+ licensed providers

• Several hundred interdisciplinary care team members (RNs, LVNs, MAs, social workers, behavioral health staff, pharmacists, community health workers, care coordinators, etc.)

• Centralized operational, access, and population health teams (call center, referral management, care coordination, chronic disease management, quality operations)

Population Health and Care Management

The platform must include advanced capabilities such as:

• Decision support, care gap identification, registries, and risk stratification

• Quality measurement and reporting

• Automated outreach

• Integrated care planning tools

Revenue Cycle Management

Vendors must provide a scalable, integrated RCM solution capable of supporting high volume, multisite ambulatory operations with centralized billing and transparent reporting.

Interoperability Requirements

The solution must support:

• Seamless data exchange at scale

• FHIR-based integration

• Connectivity with hospitals, specialty partners, and community organizations

Bidder Response Questions (Questions in this section must be answered in Questionnaire Q-15QV, unless specifically stated otherwise)

1.0 General and Technical

1.1.1 Is your organization the original developer and principal owner of the EHR platform being proposed (i.e., not a reseller, VAR, or third‑party implementer)?

Note: A “No” response will result in disqualification from further evaluation.

1.1.2 Does your organization currently have at least one active client operating an ambulatory care practice with 25 or more clinical providers on the EHR platform?

1.1.3 Specify the number of active clients that are operating an ambulatory care practice with 25 or more clinical providers on the EHR platform.

1.1.4 Describe the proposed system's fully integrated cloud-based platform for ambulatory practices, including all service modules provided (EMR, Practice Management, Care Management, Population Health, Revenue Cycle, Telehealth, Mobile, Patient Portal). Identify any modules that require third-party solutions or additional licensing.

1.1.5 Does the proposed system have the ability to operate on a cloud hosting platform (e.g., AWS, Azure, GCP) with data centers located in the United States and geographic redundancy?

1.1.6 Does the proposed system have the ability to provide data isolation between customers with logical or physical separation of PHI in a multi-tenant or single-tenant architecture?

1.1.7 Does the proposed system have the ability to maintain compliance with HIPAA, HITECH, CURES Act, CMS Interoperability and Patient Access final rule, and ADA standards?

1.1.8 Does the proposed system have the ability to meet Federal reporting requirements and supports the Continuity of Care Document, Continuity of Care Record, HITSP standard?

1.1.9 Does the proposed system have the ability to allow remote access from any authorized computer with Internet connection without loading special software?

1.1.10 Does the proposed system have the ability to support the use of portable devices (e.g., tablets and smartphones)?

1.1.11 Provide the minimum and recommended workstation hardware specifications (CPU, RAM, display resolution, storage) and supported operating system versions (e.g., Windows 11, macOS) required for optimal system performance.

1.1.12 Does the proposed system have the ability to support rapid user switching at shared clinical workstations via proximity badge or tap-to-login solutions (e.g., Imprivata, RFID badge readers) to enable fast provider authentication without full logout/login cycles?

1.1.13 Describe the system's compatibility with virtual desktop infrastructure (VDI) and thin client environments (e.g., Citrix, VMware Horizon, Azure Virtual Desktop, Windows 365).

1.1.14 List all clinical peripheral devices supported at the workstation level (e.g., barcode scanners, signature pads, smart card readers, document scanners, microphones, clinical imaging devices). Provide a detailed description of any device-specific configuration requirements.

1.1.15 Describe the system's behavior under degraded or intermittent network conditions.

Does the system support offline capabilities? If so, describe data synchronization upon reconnection and any functional limitations while offline.

1.1.16 Provide a comprehensive list of all required firewall rules, ports, protocols, and domains/IP ranges that must be permitted for system operation, including any outbound connections to cloud services, third-party integrations, and update servers.

1.1.17 Describe how the system operates within a segmented network architecture (e.g., dedicated clinical VLAN, DMZ), behind enterprise proxy servers/web filters/SSL inspection, and over site-to-site VPN or dedicated connectivity.

1.1.18 Provide estimated bandwidth consumption per concurrent user session to support network capacity planning for each clinic site, including baseline and peak utilization figures.

1.1.19 Does the proposed system have the ability for multiple users to be in the patient record at the same time and at multiple sites?

1.1.20 Provide the guaranteed minimum uptime SLA percentage and historical uptime performance data for the past 12 months, including any outage incidents and their duration.

1.1.21 Describe the vendor's support SLA structure, including severity-tiered response and resolution times (P1/P2/P3), 24/7 support availability for critical issues, escalation procedures, and whether a dedicated account manager is provided.

1.1.22 Does the proposed system have the ability to support multiple environments (e.g., production, staging, UAT, training, sandbox) with defined management and refresh processes?

1.1.23 Specify all client-side software or browser extension requirements (if any), including supported deployment methods (e.g., MSI, SCCM, Intune, silent install) and compatibility with enterprise endpoint management tools.

1.1.24 Does the proposed system have the ability to automatically apply a date, time, and user stamp to all data entered into the system, including comments and/or notes entered into all system modules, with an audit trail of all data entered?

1.1.25 Does the proposed system have the ability to use locally installed printers at each workstation as well as network printers?

1.1.26 Does the proposed system have the ability to auto-fax documents directly from the software (e.g., without printing it out on paper and then putting it through a fax machine), based on established security and permissions?

1.1.27 Does the proposed system have the ability to provide an inbox for managing secure messages related to a patient, to a practice, provider, or other system user?

1.1.28 Describe the platform's white-labeling capabilities, including whether the EMR, patient portal, and mobile app can be rebranded with the organization's name, logo and identity. For the mobile app, specify whether patients use the vendor's standard app or whether the organization can publish its own branded app via SDK.

1.1.29 Describe the industry-standard interfaces supported (e.g., HL7, CCR, CCD, CDA, LOINC).

1.1.30 Describe HL7v2 messaging capabilities, including supported message types (ADT, ORM, ORU, SIU, DFT), transport protocols, and any custom message profiles available.

1.1.31 Describe FHIR R4 API capabilities, including compliance with the CMS Interoperability and Patient Access final rule (CMS-9115-F). Provide a list of supported FHIR resources and operations.

1.1.32 Does the proposed system have the ability to support a modern API architecture (REST, SOAP, and/or GraphQL) with API versioning, rate limiting, deprecation policies, and real-time event-driven integrations (e.g., webhooks, pub/sub messaging)?

1.1.33 Does the proposed system have the ability to utilize an integration engine or middleware platform for managing interfaces (e.g., Mirth Connect, Rhapsody, Cloverleaf)?

1.1.34 Does the proposed system have the ability to support the Direct Messaging protocol for secure clinical document exchange with external providers?

1.1.35 Describe current connectivity with Health Information Exchanges (HIEs) operating in the Riverside and San Bernardino County service area (e.g., Manifest MedEx). If not currently connected, describe the implementation timeline and approach.

1.1.36 Does the proposed system have the ability to interface diagnostics reports (lab, radiology, etc.) from hospitals, public health entities, labs and outside systems into the EMR?

1.1.37 Does the proposed system have the ability to interface Emergency Room notes, discharge summaries, and history and physicals from hospital systems into the

EMR?

1.1.38 Describe bulk data export and import capabilities, including support for FHIR Bulk Data Access, flat file exports, and ETL integration for data warehousing. What export formats are available?

1.1.39 Describe the integration SDK/toolkit and developer documentation available, including whether a developer sandbox/testing environment is provided. What programming languages and frameworks are supported?

1.1.40 Describe the platform's approach to third-party application integration. Is the system open or closed to external applications connecting to the platform? Describe any restrictions, certification requirements, or approval processes imposed on third-party integrations, and provide examples of third-party applications currently integrated by existing clients.

1.1.41 Does the proposed system have the ability to provide an application marketplace or app store with pre-built extensions, a third-party app certification process, and a user community for sharing best practices and configurations.

1.1.42 Describe how the system's patient facing tools (patient portal, self-scheduling, chat, etc.) can be embedded into or integrated with an organization's existing public website, including supported integration methods (SSO, iframe, API, widgets, white labeling), branding/customization capabilities, and any CMS or web platform requirements.

1.1.43 Does the proposed system have the ability to allow a system administrator to add/change permissions for system access, maintain a directory of all personnel, and support role-based administration delegation (e.g., super admin, site admin, report admin)?

1.1.44 Describe the functional security model, including how user permissions control view

vs. edit access, how specific patient record sections can be restricted, and how security permissions apply across web and mobile interfaces.

1.1.45 Does the proposed system have the ability to support external provider access via federated identity or guest accounts?

1.1.46 Describe how referring or affiliated providers are granted restricted access to patient charts, and how external access differs from internal clinical staff.

1.1.47 Does the proposed system have the ability to support PHI data masking and de-identification for non-production environments?

1.1.48 Does the proposed system have the ability to support Multi-Factor Authentication (MFA) for all user types including administrators, clinical staff, and patients?

1.1.49 Does the proposed system have the ability to support SAML 2.0 and/or OAuth 2.0/OpenID Connect for Single Sign-On (SSO) integration with enterprise identity providers (e.g., Okta, Azure AD)?

1.1.50 Does the proposed system have the ability to terminate user sessions remotely if a breach is suspected and lock out users for upgrades, security breaches, or employee terminations?

1.1.51 Does the proposed system have the ability to provide a "break the glass", or similar, functionality for confidential programs, patient(s) or selected sensitive patient information?

1.1.52 Does the proposed system have the ability to encrypt data at rest (e.g., AES-256) and data in transit (TLS 1.2 or higher) ?

1.1.53 Describe the system's cybersecurity capabilities, including data loss prevention (DLP) controls, endpoint security requirements, and protocols for protecting against digital attacks on the database and patient information.

1.1.54 Does the proposed system have the ability to maintain an incident response plan with defined customer notification timelines in the event of a security breach, in compliance with the HIPAA Breach Notification Rule?

1.1.55 Describe audit trail reporting capabilities, including what system activities are logged, available report formats, retention periods, and how audit reports can be generated and exported.

1.1.56 Does the proposed system have the ability to provide security logging and monitoring capabilities including SIEM integration, real-time alerting, and configurable log retention policies?

1.1.57 Provide evidence of current SOC 2 Type II certification and/or HITRUST CSF certification, including certification dates and scope. Describe the approach to regular security risk assessments per HIPAA Security Rule.

1.1.58 Provide the system's current ONC Health IT Certification status, including CHPL listing number, HTI-1 compliance, USCDI v3 support, and anticipated timeline for HTI-2 compliance.

1.1.59 Does the proposed system have the ability to comply with California Consumer Privacy Act (CCPA) and California Confidentiality of Medical Information Act (CMIA) requirements?

1.1.60 Describe how third-party vendor security risks are managed for subprocessors that handle PHI, including vendor assessment processes, BAA requirements, and ongoing monitoring procedures.

1.1.61 Describe the change management and release management process, including typical release frequency, how release notes are communicated, customer notification timelines, and the ability to defer or opt out of updates.

1.1.62 Does the proposed system…