STATE OF IDAHO - BidNet · Web viewPricing will be evaluated using a cost model that offers the State the best possible value over a three (3) year contract period. The total term

STATE OF IDAHO

THE DEPARTMENT OF HEALTH AND WELFARE

REQUEST FOR PROPOSAL (RFP)ARFP1507 / IPRO RFP16000146

STATEWIDE HEALTHCARE INNOVATION PLAN (SHIP) DATA ANALYTICS

AMENDMENT 1

Issue Date 10-07-15 11-04-15

TABLE OF CONTENTS

Page

1. RFP ADMINISTRATIVE INFORMATION...............................................................................................1

2. INSTRUCTIONS FOR SUBMISSION OF PROPOSALS.......................................................................8

3. PROPOSAL FORMAT........................................................................................................................... 9

4. SCOPE OF WORK............................................................................................................................... 16

5. COST PROPOSAL............................................................................................................................... 33

6. PROPOSAL REVIEW AND EVALUATION.........................................................................................33

APPENDIX A--COST PROPOSAL AND BILLING PROCEDURE............................................................37

APPENDIX B--PERFORMANCE METRICS.............................................................................................44

APPENDIX C--REPORTS......................................................................................................................... 46

APPENDIX D--SPECIAL TERMS AND CONDITIONS.............................................................................48

APPENDIX E--RIDERS............................................................................................................................. 54

ATTACHMENT 1—OFFEROR QUESTIONS............................................................................................57

ATTACHMENT 2—REFERENCES...........................................................................................................59

ATTACHMENT 3—RE-PROPOSAL CONFERENCE REGISTRATION FORM.......................................63

ATTACHMENT 4—FINANCIAL INFORMATION......................................................................................64

ATTACHMENT 5—LIST OF ACRONYMS USED.....................................................................................65

ATTACHMENT 6—IDAHO’S INITIAL PERFORMANCE MEASURE CATALOG....................................67

ATTACHMENT 7—OFFEROR’S REQUEST FOR PROPOSAL (RFP) CHECKLIST...............................71

i

1. RFP ADMINISTRATIVE INFORMATION

RFP Title: Statewide Healthcare Innovation Plan (SHIP) Data Analytics

RFP Project Description: The Idaho Department of Health and Welfare is seeking proposals for the Data Analytics portion of the Idaho SHIP project.

RFP Lead: Bev BerendsGrants/Contracts OfficerEmail address: [email protected]: 208-639-5715

Deliver Sealed Proposal Package to: Bev BerendsIdaho Department of Health and Welfare450 West State StreetBoise, ID 83702

Pre-Proposal Conference Registration Deadline:

Wednesday, October 14, 2015, 3:00 p.m. Mountain Time

Pre-Proposal Conference:

Location:

Thursday, October 15, 2015, 10:30 a.m. Mountain Time

Pete T. Cenarrusa Building450 West State Street9A Conference RoomBoise, ID 83702

Please allow additional time for check-in at the security desk on the 1st floor.

Deadline To Receive Questions: Friday, October 23, 2015, 11:59:59 p.m. Mountain Time

RFP Closing Date: Tuesday, November 24, 2015, 5:00 p.m. Mountain Time

Proposal Opening Date: Wednesday, November 25, 2015, 8:30 a.m. Mountain Time

Oral Presentations December 17, 2015; December 21, 2015; December 28 through December 31, 2015

Initial Term of Contract and Renewals: The term of the contract is anticipated to be three (3) years but, upon mutual agreement, may be extended up to four (4) years.

TAKE NOTE OF THE 1.25% ADMINISTRATIVE FEE DETAILED IN PARAGRAPH 5 OF THE STATE’S STANDARD CONTRACT TERMS AND CONDITIONS.

ARFP1507 / IPRO RFP16000146 Page 1 of 71 10/07/1511/04/15

1.1 PurposeThe purpose of this solicitation is to obtain proposals for the data analytics portion of the Idaho SHIP project. The data analytics system shall have the capacity to provide output on identified performance measures using healthcare data from clinics throughout the state of Idaho.

1.2 Pre-Proposal ConferenceA non-mandatory pre-proposal conference will be held at the location and time as indicated in Section 1, page 1 of this RFP. This will be your opportunity to ask questions, in person, with the Department of Health and Welfare (Department) staff. All interested parties are invited to participate either by attending the conference or by an established call in number. Those choosing to participate in the pre-proposal conference by phone or in-person must pre-register to receive meeting details by submitting the completed Pre-Proposal Conference Registration Form (Attachment 1) via e-mail to the RFP Lead’s designee Kristin Perry at [email protected] no later than 3:00 p.m. Mountain Time on Wednesday, October 14, 2015. Offerors are strongly encouraged to submit questions to the RFP Lead prior to the pre-proposal conference. Any oral answers given by the State during the pre-proposal conference are unofficial, and will not be binding on the State. Conference attendance is at the participant’s own expense. Offerors are limited to three (3) in-person representatives from each vendor as space is limited. The Department will provide a maximum of three (3) conference call-in lines per vendor for registered vendors who choose to join by phone.

1.3 QuestionsQuestions must be submitted, in writing, to the RFP Lead, by the date and time indicated in Section 1, page 1, of this RFP in order to be considered. Written questions must be submitted using Attachment 1, Offeror Questions, and sent via e-mail to the RFP Lead. Official answers to all written questions will be posted on the state’s eProcurement System as an amendment to this RFP.

Any questions regarding the State of Idaho Standard Contract Terms and Conditions found at http://purchasing.idaho.gov/pdf/terms/standard_terms_and_conditions.pdf and/or Special Terms and Conditions (See Appendix D) must ALSO be submitted in writing, using Attachment 1, Offeror Questions, by the deadline to receive questions. The State will not consider proposed modifications to these requirements after the date and time set for receiving questions.

Proposals which qualify the offer 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.

1.4 Background Information

Healthcare reform and redesign started in Idaho long before the passage of the Affordable Care Act. Dating back to 2007, Idaho identified the need to transform the volume-based


http://purchasing.idaho.gov/pdf/terms/standard_terms_and_conditions.pdf

healthcare system to a value-based system, incentivizing quality of care instead of quantity of care. Since then, Idaho stakeholders from across professions and across the state have started transforming the healthcare system. Major milestones include those identified in Figure 1:

Figure 1 - Major Milestones

1.4.1 Statewide Healthcare Innovation Plan

In 2013, the state of Idaho received a planning grant from the Center for Medicare and Medicaid Innovation (CMMI) to create an innovative healthcare strategy for the entire state, known as the Statewide Healthcare Innovation Plan (SHIP). The Department is the Idaho agency responsible for the SHIP. The SHIP is the blueprint for Idaho’s new approach to healthcare guiding the Department as it works to implement the processes, practices, and features necessary to transform the statewide healthcare system. In 2014, the Idaho Healthcare Coalition (IHC) was established to guide the statewide healthcare transformation and Idaho was awarded a thirty-nine million six hundred thousand dollar ($39.6 million) grant from CMMI to test the model outlined in the SHIP.

The SHIP will achieve the triple aim of improved health outcomes, improved healthcare, and lower costs for Idahoans by reaching the following goals:

1. Transform primary care practices across the state into Patient-Centered Medical Homes (PCMHs).

2. Improve care coordination through the use of Electronic Health Records (EHRs) and health data connections among PCMHs and across the medical neighborhood.

3. Establish seven (7) Regional Collaboratives (RCs) to support the integration of each PCMH into the broader medical neighborhood.

4. Improve rural patient access to PCMHs by developing virtual PCMHs.


5. Build a statewide data analytics system that tracks progress on selected quality measures at the individual patient, regional, and statewide levels.

6. Align payment mechanisms across payers to transform payment methodology from volume to value.

7. Reduce overall healthcare costs.

Patient-Centered Medical Home The PCMH is the cornerstone of Idaho’s new model. Idaho builds upon in-state experience and that of other states to deliver primary care through a PCMH for all individuals regardless of health status. The PCMH is a team of providers working to provide effective and coordinated healthcare by integrating primary care providers, specialists, hospitals, behavioral health professionals, long term care providers, and ancillary care services. The PCMH team-based care model includes a comprehensive care plan based on assessment of patient needs, a screening for behavioral health needs, engagement of patients in wellness and self-management activities, and provision of evidence-based clinical care.

The PCMHs enhance patient care through shared patient information via the Idaho Health Data Exchange (IHDE), coordination of care across delivery settings, communication with patients across multiple formats, and by utilization of EHRs and patient portals. The PCMHs are linked to the broader medical neighborhood by RCs.

Regional Collaboratives Idaho’s seven (7) Public Health Districts listed in Figure 2 serve as the RCs. The RCs facilitate development of the medical neighborhoods to strengthen patient care coordination. The RCs assist local PCMHs by establishing formal referral and communication protocols within the broader medical neighborhood to facilitate coordinated care, support local innovation, and expand evidence-based practices. Comprised of local stakeholders, the RC Advisory Boards advise the IHC on regional issues and provide feedback on progress within each region.


Figure 2 - Regional Collaboratives

Idaho Health Data Exchange The IHDE was established to govern the development and implementation of a Health Information Exchange (HIE) in Idaho. The IHDE is governed by a board of directors that includes representatives from both the public and private healthcare sectors. The IHDE offers connected providers the use of clinical results and e-prescribing, clinical messaging, results delivery, and a data repository through a clinical portal. Through the clinical portal, providers are able to view patient summaries for their patients. Current connections to the IHDE include sixteen (16) hospitals, seven (7) laboratories, three (3) payers, and two thousand four hundred sixty-five (2,465) provider-group users. All participating PCMHs will be connected with the IHDE.

Idaho Healthcare Coalition Established by Governor Otter through Executive Order 2014-02 and composed of key stakeholders from throughout the state, the IHC guides Idaho’s healthcare system transformation efforts into an integrated model focused on patient health outcomes. The IHC focuses on continued expansion of Idaho’s PCMH capacity and oversees the provision of resources and assistance necessary to support practice transformation, while facilitating migration to new payment methodologies. The IHC also monitors the collection and analysis of statewide data, development of baseline performance measures, and establishment of reporting requirements across multiple payers to evaluate, monitor, and improve population health.


This broader care coordination is essential to improving quality of care, reducing errors and duplication of services, and ultimately, controlling costs. Figure 3 illustrates the new model of care for the statewide healthcare system envisioned in Idaho.

Figure 3 - Idaho Patient-Centered Model of Care

1.4.2 Health Information Technology

Health Information Technology (HIT) plays a key component in the statewide healthcare system transformation. Planned, statewide, and interoperable HIT will integrate PCMHs into the greater healthcare system, empowering them to transform care by improving their care coordination with individual patients and the medical neighborhood. It will also enable the systematic and statewide measurement of population health targets, and the payers’ ability to reward outcomes through new payment methodologies.

The HIT activities outlined in the SHIP call for the development and/or expansion of EHR and enhancement of IHDE technology to support:

1. Patient portals to increase patient-provider communication and patient self-management.

2. Shared data to facilitate coordinated care.

3. Statewide data collection and performance analysis needed to improve quality and establish value-based payments.

The Department, with the advice of the IHC, will support and oversee the statewide implementation of the HIT activities. Increased adoption of EHRs will be critical to the exchange of clinical and other information between primary care providers and other providers. The Department has contracted with IHDE to expand the current IHDE


infrastructure and support the integration of remote provider groups who are not yet connected or who have marginal capacity to connect. There will be additional financial incentives offered to PCMHs participating in the SHIP such as paying the IHDE vendor and connection fees as well as the first year IHDE annual fee.

Statewide Healthcare Data Analytics System Use of data has proven critical at the practice level to improve individual patient care and is also essential at the regional and state levels to guide broader population health policy decisions. A critical first step in developing a reporting structure for individual practice feedback as well as regional and state-level population health management functions is the implementation of a statewide healthcare data analytics system. The statewide healthcare data analytics system is an essential component in monitoring the implementation of the SHIP and the transformation of the statewide healthcare system in Idaho. Approximately sixteen point three percent (16.3%) of the thirty-nine million six hundred thousand dollar ($39.6 million) CMMI grant is dedicated to the statewide healthcare data analytics.

The statewide healthcare data analytics system shall have the capacity to provide analytics output on the performance measures identified in Attachment 6 - Idaho’s Initial Performance Measure Catalog using healthcare data within the IHDE from clinics throughout the state. The system shall provide analytics output for those measures at the participating clinic level, county level, regional collaborative level, and statewide. During year one (1) of the contract, the system shall provide analytics output for the following four (4) performance measures:

1. Tobacco Cessation Intervention,

2. Weight Assessment and Counseling for Children and Adolescents,

3. Comprehensive Diabetes Care, and

4. Still to be identified from Idaho’s Initial Performance Measure Catalog.

Table 1 displays, by contract year, the anticipated number of clinics from which data will be used as well as the minimum number of performance measures that the system shall provide during the contract period. Year 2 is inclusive of Year 1 numbers; Year 3 is inclusive of both Year 1 and Year 2 numbers.

Table 1 - Data Analytics Input and Output

Contract Year Clinics Minimum Performance Measures

Year 1 55 minimum 4

Year 2 110 minimum 10

Year 3 165 maximum 16


2. INSTRUCTIONS FOR SUBMISSION OF PROPOSALS

2.1 The current versions of the State of Idaho Standard Contract Terms and Conditions and Solicitation Instructions to Vendors are incorporated by reference into this solicitation, and attached or referenced in any resulting contract, as if set forth in their entirety. Both documents can be downloaded at http://purchasing.idaho.gov/terms_and_conditions.html; or copies obtained by contacting the Division of Purchasing at 208-327-7465 or [email protected]. Failure by any submitting vendor to obtain a copy of these documents 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 a submitting vendor's failure to consider the State of Idaho Standard Contract Terms and Conditions and Solicitation Instructions to Vendors in preparing its response to the solicitation.

SPECIAL TERMS PRECEDENCE: The Department’s Special Terms and Conditions take precedence in this RFP. The Department’s Special Terms and Conditions are included with this solicitation as Appendix D.

2.2 Proposals must be submitted manually. The Department will accept hardcopy (manual) proposals ONLY. No electronic submissions through IPRO will be accepted. Due to the reduction in mail delivery services per day to the Department, it is recommended that proposals be submitted via FedEx, UPS, or hand carried.

2.3 The proposal must be submitted with a state supplied signature page, located on the IPRO solicitation page as an attachment, which must contain an ORIGINAL HANDWRITTEN signature executed in INK OR AN ELECTRONIC SIGNATURE, and be returned with the relevant Solicitation documents. PHOTOCOPIED SIGNATURES or FACSIMILE SIGNATURES are NOT ACCEPTABLE (and will result in a finding that your proposal is non-responsive). Your Signature Page should be included at the FRONT of your Technical Proposal.

2.3.1 The following information must be placed in the lower left corner of your proposal package:

SEALED PROPOSALRFP LEAD: Bev Berends SEALED PROPOSAL FOR: SHIP Data AnalyticsRFP NUMBER: ARFP1507 / IPRO RFP16000146CLOSES: 11/24/15

The offeror’s name should appear on the outside of the package.

2.3.2 Each proposal must be submitted in one (1) original with five (5) copies of the Technical Proposal and one (1) original of the Cost Proposal.


mailto:[email protected]

http://purchasing.idaho.gov/terms_and_conditions.html

2.3.3 Offerors must also submit one (1) electronic copy of the full proposal, including the Cost Proposal and any attachments, on CD or USB device. Word or Excel format is required (the only exception is for financials or brochures). The format and content must be the same as the manually submitted proposal. The electronic version must NOT be password protected or locked in any way. If your proposal contains trade secret information which you have identified, submit an electronic redacted copy of the Technical Proposal with all trade secret information removed or blacked out. Do not seal the electronic copy with your sealed Technical Proposal or your sealed Cost Proposal. The electronic copy should be labeled with the offeror’s name.

2.3.4 The Technical Proposal must be sealed and identified as “Technical Proposal – ARFP1507 / IPRO RFP16000146 SHIP Data Analytics” and include the required cover letter (See Section 3.3). The offeror’s name should appear on the outside of the package.

2.3.5 The Cost Proposal must be separately sealed and identified as “Cost Proposal – ARFP1507 / IPRO RFP16000146 SHIP Data Analytics.” The offeror’s name should appear on the outside of the package.

2.4 Proposals should be submitted on the most favorable terms from both a price and technical standpoint which offerors can propose as negotiations, discussions and best and final offers cannot be guaranteed to occur.

3. PROPOSAL FORMAT

3.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. There is no intent to limit the content of proposals.

3.2 Evaluation Codes

3.2.1 (M) Mandatory Specification or Requirement - failure to comply with any mandatory specification or requirement will render offeror’s proposal non-responsive and no further evaluation will occur.

3.2.2 (ME) Mandatory and Evaluated Specification - failure to comply will render offeror’s proposal non-responsive and no further evaluation will occur. Offeror is required to respond to this specification with a statement outlining its understanding and how it will comply. Points will be awarded based on predetermined criteria. The State reserves the right to seek clarification on any M or ME requirement.

3.2.3 (E) Evaluated Specification - a response is desired. If not available, respond with “Not Available” or other response that identifies offeror’s ability or inability to supply the item or service. Failure to respond will result in zero (0) points awarded for the specification.


3.3 (M) Cover LetterThe Technical Proposal must include a cover letter on official letterhead of the offeror; with the offeror’s name, mailing address, telephone number, facsimile number, e-mail address, and name of offeror’s authorized signer. The cover letter must identify the RFP Title and number, and must be signed, in ink, by an individual authorized to commit the offeror to the work proposed. In addition, the cover letter must include:

3.3.1 Identification of the offeror’s corporate or other legal entity status. Offerors must include their tax identification number. The offeror must be a legal entity with the legal right to contract.

3.3.2 A statement indicating the offeror’s acceptance of and willingness to comply with the requirements of the RFP and attachments, including but not limited to the State of Idaho Standard Contract Terms and Conditions (http://purchasing.idaho.gov/pdf/terms/standard_terms_and_conditions.pdf), any Special Terms and Conditions included in Appendix D, and Riders in Appendix E.

3.3.3. A statement of the offeror’s compliance with affirmative action and equal employment regulations.

3.3.4 A statement that offeror has not employed any company or person other than a bona fide employee working solely for the offeror or a company regularly employed as its marketing agent, to solicit or secure this contract, and that it has not paid or agreed to pay any company or person, other than a bona fide employee working solely for the contractor or a company regularly employed by the contractor as its marketing agent, any fee, commission, percentage, brokerage fee, gifts or any other consideration contingent upon or resulting from the award of this contract. The offeror must affirm its understanding and agreement that for breach or violation of this term, the State has the right to annul the contract without liability or, in its discretion, to deduct from the contract price the amount of any such fee, commission, percentage, brokerage fee, gifts or contingencies.

3.3.5 A statement naming the firms and/or staff responsible for writing the proposal.

3.3.6 A statement that offeror is not currently suspended, debarred or otherwise excluded from federal or state procurement and nonprocurement programs. Vendor information is available on the Internet at: https://www.sam.gov

3.3.7 A statement affirming the proposal will be firm and binding for one hundred twenty (120) calendar days from the proposal opening date.

3.3.8 A statement, by submitting its proposal, that the offeror warrants that any contract resulting from this Solicitation is subject to Executive Order 2009-10 [http://gov.idaho.gov/mediacenter/execorders/eo09/eo_2009_10.html]; it does not knowingly hire or engage any illegal aliens or persons not authorized to work in the


http://gov.idaho.gov/mediacenter/execorders/eo09/eo_2009_10.html

https://www.sam.gov/

http://purchasing.idaho.gov/pdf/terms/standard_terms_and_conditions.pdf

United States; it takes steps to verify that it does not hire or engage any illegal aliens or persons not authorized to work in the United States; and that any misrepresentation in this regard or any employment of persons not authorized to work in the United States constitutes a material breach and will be cause for the imposition of monetary penalties up to five percent (5%) of the contract price, per violation, and/or termination of its contract.

3.4 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. IDAPA 38.05.01.52

3.5 Trade SecretsIdentify each page of the proposal that you believe contains a “trade secret” (See Paragraph 28, Solicitation Instructions to Vendors,http://purchasing.idaho.gov/pdf/terms/solicitation_instructions.pdf).

3.6 Table of ContentsInclude a table of contents in the Technical Proposal identifying the contents of each section, including page numbers of major subsections.

3.7 Executive SummaryInclude an executive summary in the Technical Proposal providing a condensed overview of the Technical Proposal demonstrating an understanding of the services to be performed.

To submit a proposal, you must use this document and, for each requirement listed below, provide your response in the “Response” box directly below the requirement(s). If your response requires charts, tables, pictures, resumes, or other graphics to clarify your text response, include them as clearly marked attachments and reference the attachment(s) in the applicable “Response” box.

DO NOT SUBMIT PROPOSALS OUTSIDE OF THIS FORMAT.

3.8 Business Information(E) This section identifies the critical expertise and qualifications the Department is seeking. The offeror must demonstrate their ability to successfully implement and operate a statewide healthcare data analytics system that tracks, analyzes, and reports on individual and population health in order to monitor health outcomes and measure performance. The offeror should also demonstrate their experience providing healthcare analytics services for an organization of similar size, enabling data-driven decision making, and improving performance.

Provide your general Business Information response here:


http://purchasing.idaho.gov/pdf/terms/solicitation_instructions.pdf

3.8.1 (ME) Mandatory ExperienceThe offeror must have, through its own organization or its subcontractors, experience in the areas listed below. If the proposal includes the experience of a subcontractor to meet a mandatory experience requirement, the subcontractor must be proposed to perform the services. For all areas below, the offeror must have a minimum of three (3) years’ experience within the last seven (7) years. Describe in detail your knowledge and experience which clearly demonstrates your company or proposed subcontractors meet the stated requirement in the following areas:

3.8.1.1 Data Warehouse Experience: Experience building, operating, and maintaining a data warehouse that uses a scalable and open architecture supporting relational database implementations such as DB2, SQL Server, and Oracle to integrate data from a variety of diverse data sources, including external sources such as agencies, exchanges, or other government and non-governmental entities.

3.8.1.2 Data Analytics Experience: Experience developing and applying sophisticated data analytics for performance evaluation of complex programs. This shall include retrospective and prospective analysis, including the use of predictive models.

3.8.1.3 Healthcare Data Experience: Experience collecting, aggregating, analyzing, and reporting on healthcare clinical and claims data in the private sector or working for government agencies that administer healthcare programs.

Provide your Mandatory Experience response here.

3.8.2 (E) Additional ExperienceThis section provides the additional experience preferred by the Department. Describe in detail your knowledge and experience which clearly demonstrates your company or proposed subcontractors have the following qualifications.

3.8.2.1 Health Outcomes Experience: Experience in the healthcare industry helping a business entity achieve improved performance in health outcomes, health cost management, and patient and provider experience.

3.8.2.2 User Accessibility Experience: Experience in developing and hosting a system providing analytic reporting, dashboards, scorecards, and other information to designated stakeholders, as well as experience providing ongoing help desk support for end-users.

Provide your Additional Experience response here.


3.8.2 (E) ReferencesOfferors are allowed three (3) completed Reference Questionnaires. Please see Attachment 2. The Department of Health and Welfare cannot be used as a reference for this project and references must be from two (2) or more separate projects.

3.8.3 (E) Financials Offerors are required to provide financial information as detailed on Attachment 4.

3.9 (E) Organization and StaffingThis section identifies the organizational and personnel qualifications the Department is seeking from a company to successfully implement and operate the statewide data analytics system as described in this RFP. For each section below, describe how you will meet the stated requirements, demonstrating your resources, structure, and proposed staffing to meet the qualifications desired by the Department. Clearly demonstrate you have the organizational and staffing capability to successfully implement and operate the statewide data analytics system as described in this RFP. The offeror shall include a strategy for when staff will be utilized throughout the contract period.

3.9.1 Organizational StructureThe offeror shall have an internal organizational structure of sufficient size to perform or direct the performance of the services described in this RFP. The organizational structure shall clearly define lines of responsibility, authority, communication, and coordination within and between various program components and activities.

Provide a detailed description of your organizational structure, including a delineated management structure, which demonstrates you can meet the Organizational Structure requirements. An organizational chart shall be included with information showing the number and types of employees.

Provide your Organizational Structure response here. In addition to your written response, attach your organizational chart separately and label it as Attachment 3.9.1.

3.9.2 Professional Staffing QualificationsFor each of the positions and functions described in this section, include names, titles, resumes, and a description of relevant experience. Provide evidence of a sufficient number of qualified staff to manage all requirements described in this RFP.

3.9.2.1 (ME) Key Personnel: The key personnel shall be located in Idaho or at a minimum be available in Idaho as requested by the Department for key meetings. Key personnel proposed by the offeror shall serve in the positions for which they were proposed. Any new key personnel appointed during contract performance period shall have at least the same qualifications as the individual proposed for that position in the offeror’s proposal and subject to discussion with the Department.


Project Manager or Similar Title: The Project Manager shall act as the primary point of contact for the Department for contract and performance issues and responsibilities, conduct day-to-day project management, and ensure high quality services. All communications shall go through the Project Manager. The Project Manager shall have experience managing a project of similar size and scope, preferably in healthcare.

Operations Manager or Similar Title: The Operations Manager shall have the primary responsibility for coordinating and executing the tasks needed to ensure operational performance throughout the contract term. The Operations Manager ensures that data analytics and reporting services are compliant with federal, state, Health Insurance Portability and Accountability Act (HIPAA), and other regulations. The Operations Manager oversees all training activities for end-users. The Operations Manager shall have experience with database and business intelligence projects of similar size and scope.

Provide your response to the Key Personnel requirements here. In addition to your written response, attach supporting resumes as needed and label them as Attachment 3.9.2.1.

3.9.2.2 (E) Other Staff Functions: In addition to providing key personnel, the offeror shall ensure the following functions are performed by a qualified staff member employed by the offeror or a subcontractor. Subcontractors shall be subject to approval by the Department.

Analytics Management: The Analytics Management function includes the overall responsibility of performing some combination of accounting, finance, analytical, business process, and information technology knowledge to assist the Department, the IHC, and the RCs with analyzing and enhancing the quality, usability, and availability of data. The Analytics Management function shall focus on transforming data into usable information to improve program performance and decision-making.

User Accessibility: The User Accessibility function (e.g., web portal) has responsibility for ensuring authorized users have appropriate access to the statewide healthcare data analytics system while ensuring the protection of private health information, and working with the Operations Manager to fix problems with access to the statewide healthcare data analytics system. This function is responsible for receiving and responding to user needs and requests, and troubleshooting problems with access to the statewide healthcare data analytics system.


Database Administration Management: The Database Administration Management function includes the overall oversight and responsibility for database development and operations along with data transmission and translation services and health information exchange activities and interactions.

Provide your response to the Other Staff Functions requirements here. In addition to your written response, attach supporting resumes as needed and label them as Attachment 3.9.2.2.

3.9.3 (E) SubcontractorsDescribe the extent to which subcontractors will be used to comply with contract requirements. Include each position providing service, and provide a detailed description of how the subcontractors are anticipated to be involved under the contract. Include a description of how the offeror will ensure that all subcontractors and their employees meet all requirements.

Provide a detailed subcontracting plan, listing names and addresses of the subcontractors, and include resumes for all subcontractor key staff. Describe your past experience in using and managing subcontractors and include your history with the proposed subcontractors.

Offerors must disclose the location of the subcontractor’s business office and the location(s) of where the actual work will be performed. 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 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.

All subcontractors are subject to approval by the Department.

Provide your response to the Subcontractors requirements here. In addition to your written response, attach your detailed subcontracting plan along with subcontractor(s) organizational charts, and subcontractor resumes and label them as Attachment 3.9.3.


4. SCOPE OF WORK

This section provides an overview of the work to be performed and the specific requirements that must be met to successfully implement and operate the statewide data analytics system the Department is seeking.

Scope of Work Section (SOW) I and IX are mandatory requirements and will be included in the resulting contract but do not require a response, except to affirmatively indicate offeror’s willing to comply with each mandatory requirement.

I. General RequirementsA. The Contractor shall:

1. Provide analytics services for evaluating outcomes specific to Attachment 6 - Idaho’s Initial Performance Measure Catalog. The analytics services shall be designed to meet the needs of the Department.

2. Provide services including: hosting, data transfer, analytics design and development, testing, display of analytics output, and user interfacing as required by the Scope of Work.

3. Have significant experience in the healthcare industry and information technology.

4. Possess the capability to extract data based on key performance measures, and develop analytic outputs in a variety of display formats.

5. Possess experience and expertise in architecting and building a statewide healthcare analytics system to track, analyze, and report feedback to individual providers on selected performance and outcome measures to improve their practice. The Contractor shall also possess the capacity to expand the number of analytics measures, analytics outputs, and users served to meet future capacity requirements.

6. During the first year, provide analytics output for a minimum of four (4) performance measures. This will include tobacco cessation intervention, weight assessment and counseling for children and adolescents, comprehensive diabetes care, and a fourth measure still to be determined by the Department from Attachment 6 - Idaho’s Initial Performance Measure Catalog. The second year minimum number of performance measures provided by the analytics system is ten (10). The third year minimum number of performance measures provided by the analytics system is sixteen (16). The system shall provide output for those measures at the participating clinic level, county level, regional collaborative level, and statewide level. Table 2 displays (by year) the approximate number of clinics from which data will be used as well as the minimum number of performance measures that the system shall provide. Year 2 is inclusive of Year 1 numbers; Year 3 is inclusive of both Year 1 and Year 2 numbers.

Table 2- Data Analytics Input and Output


Year 1 55 minimum 4





Affirmatively indicate your willingness to comply with the mandatory requirements in SOW I. General Requirements:

For each requirement listed below, provide your response in the “Response” box directly below the requirement(s). If your response requires charts, tables, pictures, or other graphics to clarify your text response, include them as clearly marked attachments and reference the attachment(s) in the applicable “Response” box. 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. The proposal should address methodologies, pertinent timelines, personnel, activities, and other pertinent information in order to implement the Scope of Work 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.

All sections of the Scope of Work are required contract services. Failure to provide a response to a requirement may result in receiving a score of zero (0) for that portion of the proposal.

II. (ME) Clinical and Claims Based Analytics Describe how you will meet the requirements for Clinical and Claims Based Analytics.A. The Contractor shall provide a Contractor-hosted solution wherein the Contractor

configures an existing analytics system to accommodate the needs of the Department. System configuration requires the Contractor possess a fully developed analytics system that is configurable to meet the needs of the Department prior to contract award. The Contractor’s system shall:1. Support the retrieval of data from a variety of data storage methods including but not

limited to: relational databases, data warehouses, analytic databases, distributed database systems, distributed file systems, and text files in a variety of formats.

a. The Contractor shall create and maintain a data dictionary describing each data element and its associated metadata. The dictionary shall also contain quality measures, performance measures, aggregate values, and any other data elements.

b. The Contractor shall implement system controls to ensure data integrity.

c. The system shall provide consistent results for the same data inquiries regardless of delivery mechanism. A dashboard, a standard report, a self-service report, and


any other delivery mechanism must be consistent in the results provided for the same data request. The results of all delivery mechanisms must also be validated by a direct query of the underlying data.

d. The Contractor’s system shall provide analytics results that are free of errors that meet the following criteria:i. Where the error is caused by factors within the Contractor’s control.

ii. Where what constitutes an error is defined by objective, measurable criteria, and

iii. Based upon a percentage that is consistent with industry standards, where analytic systems of the type requested are typically measured at a ninety-five percent (95%) level measured monthly.

Response to SOW II.A.1:

2. Provide analytics based on data from a minimum of fifty-five (55) clinics in Year 1; a minimum of one hundred ten (110) clinics in Year 2; and, a maximum of one hundred sixty-five (165) clinics in Year 3.


3. Refresh data used in analytics every night after 7:00 p.m. Mountain Time (MT) and complete the nightly data refresh process by 7:00 a.m. MT on the morning following the initiation of the refresh process.

4. Utilize a back-up copy of data from the IHDE database.

Response to SOW II.A.3 & 4:

5. Provide statistical, predictive, and decision analytics capabilities. The system shall have the ability to:a. Provide results of statistical, predictive, and decision analytics including measures

of variance and statistical significance related to the analysis.

b. Provide a full range inferential and descriptive statistics.

c. Provide visual depictions of the results of analytics processes.



6. Support delivery platforms that include at least one (1) of the following: desktop, web, and mobile.


7. Allow an authorized user access to the data analytics system to run standard reports, dashboards, and scorecards. Users shall be able to customize reports, dashboards, and scorecards and save the settings and parameters (filters, report selection criteria, etc.). The system shall have the capability to limit access to reports, dashboards, and scorecards at a group, role, or individual level.


8. Provide standard, ad hoc, and custom reporting, dashboards, and scorecards at the participating clinic level, the county level, the regional collaborative level, and the statewide level.

a. “Standard” means a report written by the Contractor or Department with settings that can be saved, but the report structure remains common to all.

b. “Ad Hoc” means a report that is built once and not re-used.

c. “Custom” means a report that is built and saved to rerun or share with other users.


9. Provide predictive modeling to provide future utilization and projected outcomes.


10. Support a variety of formats and output options (e.g. Word, Excel, pdf, HTML, CSV, and text only).


III. Hosting, Hardware, and Software Describe how you will meet the requirements for Hosting, Hardware, and Software.


A. (E) The Contractor shall:

1. Provide all physical and virtual hardware and software used.

Response to SOW III.A.1:

2. Provide a back-up system.


3. Work with the Department to provide a disaster recovery plan that includes information about plan testing and frequency of testing and ensures the system will be back in production status within seventy-two (72) hours of when the system went down. The final version of the plan must be submitted to and approved by the Department within thirty (30) calendar days of the contract effective date.

4. Ensure the system disaster recovery procedures are stored separately from the production site.

In addition to your written response, provide a draft Disaster Recovery Plan with your proposal and identify it as Attachment III.A.3. Response to SOW III.A.3 & 4:

5. Have the capability to support failover options such as use of a local copy of the data, database replication, mirroring, or snapshot provisions, that allows the system to operate in a degraded service mode until normal operations are restored.


6. Design promotion and rollback plans for development, testing, and production environments.


7. Provide information to the Department for solution scalability options to accommodate capacity and growth.



8. Provide complete system infrastructure, application, and database architectural diagrams. Diagrams shall include all components and processes along with descriptions of the items contained at each layer.

In addition to your written response, provide actual diagrams with your proposal and identify them as Attachment III.A.8. Response to SOW III.A.8:

9. Provide an architectural diagram and description of all data flows and transformations.

In addition to your written response, provide actual diagrams with your proposal and identify them as Attachment III.A.9. Response to SOW III.A.9:

10. Provide a description of databases and data sources the solution supports and the method to connect to each.


11. Host the analytics system in a Tier 2 or greater data center.


12. Maintain written descriptions of operation and maintenance activities, including the types of maintenance (e.g., scheduled, emergency, etc.) and notification methods to users.


13. Provide a separate training environment in the system for end users.



B. (E) The Contractor’s system shall:

1. Automatically reconnect to resources, services and/or applications that were temporarily unavailable once the resource, service, and/or application become available.

Response to SOW III.B.1:

2. Support prioritized functionality regardless of localized failure, capacity issues, or other external obstacles.


3. Provide the users the ability to conduct business from a remote location (alternative processing sites).


4. Include a development environment, a production environment, and a testing environment.


5. Provide a fully developed analytics system that is configurable to meet the needs of the Department.


6. Conduct all analytics processing at the hosted site.


C. (M) Identify the version, version number, and release date of the proposed system and validate it is in production. The version named must be the version demonstrated during


oral presentations, the version included in the proposed costs, and the version implemented for the project.

A response is mandatory but will not be evaluated. Response to SOW III.C:

IV. (E) Project Management Describe how you will meet the requirements for Project Management.A. The Contractor shall:

1. Develop and execute a Project Management Plan (PMP) that follows Project Management Body of Knowledge (PMBOK) guidance and has the final version approved by the Department within thirty (30) calendar days of the contract effective date. http://www.pmi.org/PMBOK-Guide-and-Standards.aspx

In addition to your written response below, include a draft of your proposed PMP with your proposal and label it as Attachment IV.A.1 Response to SOW IV.A.1:

2. Ensure their project team is available to the Department as requested for any meetings related to the project tasks associated with the scope of the contract. This shall include:

a. Attendance by key personnel onsite when requested by the Department.

b. Status update meetings regarding the project tasks on a quarterly basis at the Department’s designated offices.

c. Status update meetings during the planning and implementation phases of the project (as defined by the approved PMP on a weekly basis via phone and web-based meetings.

Response to SOW IV.A.2:

3. Develop and maintain a Project Work Plan that includes each phase of the project. The work plan shall adhere to industry best practices and standards for project management, and be broken down into Work Breakdown Structures (WBS), including key tasks, milestones, resources, deliverables, and task dependencies. The final version of the work plan must be submitted to and approved by the Department within thirty (30) calendar days of the contract effective date.

In addition to your written response below, include a draft of your proposed Project Work Plan with your proposal and label it as Attachment IV.A.3. Response to SOW IV.A.3:


http://www.pmi.org/PMBOK-Guide-and-Standards.aspx

4. Develop and maintain a Requirements Traceability Matrix to associate finalized requirements with the work products that satisfy them. At a minimum this matrix must identify where each of the approved requirements will be addressed in subsequent design, development, and testing deliverables. The final version of the matrix must be submitted to and approved by the Department within sixty (60) calendar days of the contract effective date.

In addition to your written response below, include a draft of your proposed Requirements Traceability Matrix with your proposal and label it as Attachment IV.A.4. Response to SOW IV.A.4:

5. Work with other Department contractors on tasks and activities related to the analytics solution.

Response to SOW IV.A.5:

V. Support Services Describe how you will meet the requirements for Support Services.A. (E) The Contractor shall:

1. Have a Service Level Agreement (SLA) that ensures technical and non-technical support throughout the course of the project.

a. The SLA shall include support coverage Monday – Friday from 7:00 a.m. – 7:00 p.m. MT.

b. The SLA shall include details for support including the type of support (technical, non-technical), support levels (tier 1, tier 2, tier 3, etc.), response time parameters, and issue escalation procedures.

In addition to your written response below, with your proposal provide a copy of your proposed SLA for the Department to consider and label it as Attachment V.A.1. The version of the SLA provided should take into consideration previous experience with government entities and certain clauses not allowable by most governmental entities. Response to SOW V.A.1:

2. Provide a dedicated toll-free call center telephone number(s) within the continental United States that is staffed for the agreed upon support level.

Response to SOW V.A.2:


3. Provide a Training Plan with curriculum that describes new user training, ongoing training for users as system enhancements are released, and subsequent training for added clinics in Year 2 and Year 3. The Training Plan shall:

a. Address the training needs of all stakeholders using the data analytics system.

b. Address all security roles in the data analytics system.

c. Include a person-to-person training option after the initial training is completed.

c. Address conducting a training satisfaction survey.

d. Be submitted and receive Department approval within sixty (60) calendar days of the contract effective date.

4. Conduct training as identified in the approved Training Plan.

In addition to your written response below, provide a draft of your Training Plan and curriculum and label it as Attachment V.A.3. Response to SOW V.A.3 & 4:

5. Provide warranty information on the analytics system.

Response to SOW V.A.5:

B. (M) If customized code is used, describe how you would escrow the customized code.

Providing this information is mandatory but the response will not be evaluated. Response to SOW V.B:

C. (M) Submit information for the Department to consider regarding software licensing requirements, including information per user, enterprise wide, site licensing, etc. Provide general information in the “Response” box below and attach any supporting documents, such as a copy of any licensing agreement and label it as Attachment V.C.

Providing this information is mandatory but the response will not be evaluated. Response to SOW V.C:


VI. (E) Solution Programming Language and Browser Support Describe how you will meet the requirements for Solution Programming Language and Browser Support.A. The system shall:

1. Support graphical user interface data upload functionality for providers.

2. Pass tests for common web vulnerabilities as described in the Open Web Application Security Project (OWASP) Top 10 vulnerabilities. (e.g. https://www.owasp.org/index.php/Top10#OWASP_Top_10_for_2013 )

3. Support notifications of system outages or other unusual circumstances.

4. Include online help accessible from the user interface.

5. Include a comprehensive test plan for analytics output that describes for each test:

a. The type of testing and details;

b. Traceability of test scenarios, test cases and test results to requirements;

c. The processes, procedures, and tools for problem identification and resolution;

d. How the system will maintain accurate test data while protecting privacy;

e. Regression testing at all levels when errors are corrected; and

f. The security tests to ensure the controls appropriately prevent unauthorized access to the system.

6. Validate all input to ensure numeric items with definitive upper and or lower bounds are within the proper range.

7. Include coding that ensures all input fields are validated with expected input, for example, alphabetic fields contain only alphabetic data; numeric fields contain only numeric data; date ranges are valid; URL input is as expected.

8. Support standard system size, color, font, resolution, and input settings.

9. Provide system documentation detailing data workflows from the IHDE system to the data analytics system.

10. Support accepting data from the IHDE system.

11. Include testing to validate the accuracy of the data transmitted from the IHDE system to the data analytics system.

12. Support preparation and distribution of reports specified by the Department.

13. Possess the capability to create new interfaces using the established application architecture.

14. Include the configuration process.

15. Be browser version neutral, i.e., cannot mandate a particular version of a supported browser.

16. Return presentations of analytic outputs within three (3) seconds of user input (excluding delays resulting from network issues beyond the system’s control).


https://www.owasp.org/index.php/Top10#OWASP_Top_10_for_2013

In addition to responding to each item above, provide detailed descriptions of the methods used and your experience in validating analytics results, minimizing response times, resolving errors in analytics outputs, and disclosing the discovery of a failure to meet a Performance Metric. Response to SOW VI.A.1-16:

B. The Contractor shall:

1. Provide a list of all programming languages used.

2. Provide logical and physical diagrams of the database(s) used.

3. Provide name node and job tracker metadata for distributed file system(s) used.

4. Develop a test results report that documents the disposition of all test cases, including expected and actual results; and identifies and classifies all defects, including the status of defect resolution as of the date of the report.

5. Perform volume and stress tests to demonstrate the ability to process expected workloads.

6. Ensure that the system mimics the production environment in training, testing, and development areas.

7. Provide architectural design models for the system within sixty (60) calendar days after the contract effective date.

8. Use a defect tracking tool to ensure all defects are mitigated prior to production implementation.

9. Ensure production data used in testing and training has been appropriately de-identified.

10. Provide database and systems administration.

11. Transfer all existing data to the system in the initial upload from a back-up copy from IHDE.

12. Work with identified stakeholders to extract data from additional sources as needed.

13. Ensure all development is executed in the development environment, all production is executed in the production environment, and all testing is executed in the testing environment.

Response to SOW VI.B:

VII. (E) Privacy, Security, and Audit Describe how you will meet the requirements for Privacy, Security, and Audit.A. The system shall:


1. Provide a means of secure identification and authentication to ensure only authorized users are allowed access to the system.

2. Use a unique User ID for each user to login to the system or application.

3. Have the capability to support users to create a password of their own choice.

4. Include a self-service capability that allows users to retrieve their User ID and reset their password after ensuring the requestor is entitled to the information.

5. Have the capability to enforce administratively determined password formatting rules including requiring the use of upper and lower case, special characters, numbers, and minimum/maximum lengths.

6. Ensure stored passwords are always encrypted.

7. Prevent the creation of duplicate user accounts.

8. Provide the capability to require users to change their password after an administratively configurable time limit.

9. Provide the capability to allow administrators to reset a user’s password.

10. Provide the capability for administrators to suspend or deactivate a user’s account for a specified time period.

11. Use Roles Based Access Control (RBAC) to allow users access to the system/application.

12. Have RBAC capability with a strong security role for administering security-related functions.

13. Allow only authorized individuals to create roles and assign users to specific roles.

14. Base default RBAC roles (if/when used) on the principle of least privilege (e.g. limiting individual access to specific applications, screens, databases, fields, and files based on a need-to-know basis).

15. Include the capability to lock user accounts based on user configurable parameters (such as days of inactivity, number of consecutive failed logon attempts in set period of time, etc.).

16. Provide mechanisms to ensure access to data and reports is based on user's role and specific security clearance; e.g., display fields are "grayed out" or not displayed if users do not have sufficient security clearance to access or view the data.

17. Provide the capability for a user to be attached to more than one (1) role except when roles cannot co-exist.

Response to SOW VII.A 1-17:

18. Include a fully HIPAA-compliant audit capability.

19. Include monitoring to detect abnormal usage (large data transfers, unusual login activity etc.).


20. Be capable of logging all security-related access control events. Security-related access control events include:

a. Addition, deletion/removal of users,

b. Changes to user rights, and

c. Failed logon attempts.

21. Ensure providers are allowed to view/use their own data and not allowed to view any other data unless the data has been sufficiently de-identified or aggregated in such a way as to prevent identification of other provider’s data.

22. Include with all reports containing sensitive or classified data (PII, ePHI, etc.), a disclaimer stating that the report (or dashboard) may contain confidential information intended for a specific individual and purpose, is protected by law, and the receiver should contact the sender and delete the message if received in error. The disclaimer should also indicate that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.

23. Support a data classification schema with data items flagged to link them to a classification category.

24. Reside in a network that uses industry best practices, evidenced by certification, to provide internet security functionality such as the use of firewalls, intrusion detection/intrusion prevention (IDS/IPS) and encrypted networks.

a. (M) The Contractor shall engage and pay for an independent certified public accounting firm to perform an attestation of the Contractor’s internal controls in accordance with the American Institute of Certified Public Accountants Statement Standards for Attestation Engagements (SSAE) No. 16, Reporting on Controls at a Service Organization. The audit shall be performed annually and the Contractor shall submit a copy of the audit report to the Department upon the completion of each audit.

25. Support Secure Sockets Layer (SSL) 3.0, Transport Layer Security (TLS) 1.2 and higher, and Internet Protocol Security (IPSEC) protocols.

26. Include or support procedures for guarding, monitoring, and detecting malicious software (e.g., viruses, worms, malicious code, etc.) in a proactive manner. (For example, use of state of the art anti-virus solutions, intrusion prevention, heuristic analysis, sandbox containment, etc.)

27. Prevent untrusted systems from accessing trusted zone systems.

28. Provide the capability to configure session inactivity "timeout" parameters.

29. Ensure all web services handling sensitive data are delivered using a secure method (https, secure File Transfer Protocol (sFTP), etc.)

30. Support the display of a banner screen as part of the logon process.

31. Implement a patch management process that ensures only tested patches are deployed into production.


32. Provide the capability to generate alerts for conditions that violate security rules.

37. Encrypt data using Federal Information Processing Standards (FIPS) 140-2 compliant encryption.

33. Store data at rest in encrypted format.

34. Have the capability to encrypt and store backed up data.

35. Include an incident alerting and notification system to track potential intrusions.

36. Adhere to all federal and state data security standards including all data sharing agreements necessary to view and receive confidential data.

In addition to your written response to this section, provide an affirmative response to your willingness to provide an annual SSAE 16 audit report and a copy of your most recent SSAE 16 audit report, if available. Response to SOW VII.A 18-36:

B. The Contractor shall:

1. Provide a network infrastructure solution that is self-contained and in its own security perimeter.

2. Provide documentation to ensure the system is compliant with security policies, standards, requirements and audits described in the National Institute of Standards and Technology (NIST) 800-53, “Recommended Security Controls for Federal Information Systems and Organizations”. http://www.nist.gov/

3. Provide an Incident Reporting Plan incorporating a reliable and timely process for identifying and communicating the occurrence of adverse events, security incidents, or data breach involving ePHI or PII as defined in Idaho Statues Title 28, Chapter 51, Section 105 “Disclosure of breach of security of computerized personal information by an agency, individual, or commercial entity.http://www.legislature.idaho.gov/idstat/Title28/T28CH51SECT28-51-105.htm

4. Provide a System Security Plan (SSP) documenting all security controls and features implemented for the system and application.

5. Place the data analytics system on hardware specifically dedicated to the Idaho data analytics system.

6. Ensure all software and data is stored on servers or storage solutions that are secured and not shared or co-mingled with other clients or vendors.

In addition to your written response, provide a draft of your Incident Reporting Plan as an attachment and label it Attachment VII.B.3. In addition to your written response, provide a draft of your System Security Plan as an attachment and label it Attachment VII.B.4. Response to SOW VII.B:


http://www.legislature.idaho.gov/idstat/Title28/T28CH51SECT28-51-105.htm

http://www.nist.gov/

VIII. (E) Reports/Records/Documentation Describe how you will meet the requirements for Reports/Records/Documentation.A. The Contractor shall:

1. Provide all reports as outlined in the Reports section.

2. Provide standard reports, self-service reports, and dashboards. The system shall have the ability to:a. Provide standard, ad hoc, and custom reporting, dashboards, and scorecards for

a minimum of four (4) performance measures identified in Attachment 6 - Idaho's Initial Performance Measure Catalog in Year 1. The system shall provide reporting for those measures at the participating clinic level, county level, regional collaborative level, and statewide level.

b. Have the capacity and flexibility to provide analytics output for performance measures to be defined in the future and added to Attachment 6 - Idaho's Initial Performance Measure Catalog.

c. Provide standard, ad hoc, and custom reporting, dashboards, and scorecards for the remaining twelve (12) performance measures identified in Attachment 6 - Idaho's Initial Performance Measure Catalog for contract Year 2 and contract Year 3, according to the established minimum. The system shall provide reporting for those measures at the participating clinic level, county level, regional collaborative level, and statewide level.

d. Maintain a catalog of all standard reports, dashboards, and scorecard that is searchable by intended use, business area supported, and will allow the user to then access authorized reports.

e. Provide reports, dashboards, and scorecards with the capability to drill-down to a single record, when available.

f. For all standard reports, dashboards, and scorecards, provide authorized users the ability to modify date ranges, as well as filter entities and attributes (including by Regional Collaborative) to display.

g. Support the creation of self-service (i.e.ad hoc and custom) reports allowing the user to define custom content.

Response to SOW VIII:

IX. Transition PlanA. The Contractor shall work with the Department to develop a transition plan which will

ensure a smooth transition of contracted services and transfer of contract-related materials and documentation either to the Department or to another contractor upon expiration or termination of the contract.


a. The draft transition plan shall be due to the Department within three (3) months after the contract effective date.

b. The Contractor and the Department will review and finalize the transition plan, and update if necessary, within three (3) months prior to the expected contract expiration date.

Affirmatively indicate your willingness to comply with the mandatory requirements in SOW IX. Transition Plan:

IX. Faith-based Organization: If you are a faith-based organization describe how you will: A. Segregate contract funds in a separate account;

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

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

D. 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;

E. Ensure that contract funds are not expended on inherently religious activities, and

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

Response to SOW IX., if applicable:

X. Identification of Risks and Constraints: Based on the Scope of Work detailed in this RFP, identify any risks or constraints that you will need to address prior to or during the performance of the work; as well as a description of how you will address each one. For example an incomplete Scope of Work can be both a risk and a constraint. How would you mitigate, or overcome this? Provide your response to this section on no more than two (2) type-written pages.

Response to SOW X. (optional & not evaluated):


5. COST PROPOSAL

Pricing will be evaluated using a cost model that offers the State the best possible value over a three (3) year contract period. The total term is not anticipated to exceed four (4) years.

5.1 (ME) Use the format established in Appendix A when completing your Cost Proposal, and identify it as Appendix A - Cost Proposal and Billing Procedure. Altering the format will cause the Cost Proposal to be found non-responsive.

5.2 The offeror must provide a fully-burdened rate which must include, but not be limited to, all operating and personnel expenses, such as: overhead, salaries, administrative expenses, profit, supplies, travel, quality assurance, etc.

6. PROPOSAL REVIEW AND EVALUATION

6.1 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.

6.2 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). Any proposal(s) not meeting the Mandatory Submission Requirements may be found non-responsive. IDAPA 38.05.01.074.03.a, as well as IDAPA 38.05.01.091.05, allows the designated State official to waive minor informalities as well as minor deviations. The State also reserves the right to seek clarification on any (M) or (ME) requirements.

6.3 The Technical Proposal will be evaluated first as either “pass” or “fail,” based on the compliance with those requirements listed in the RFP with an (M) or (ME). All proposals that meet the requirements will continue in the evaluation process outlined in this section.

6.4 The proposals will be reviewed and evaluated by a Proposal Evaluation Committee.

6.5 The scores for the Technical Proposal will be normalized as follows: The proposal with the highest overall total technical score will receive a score of 600. Other proposals will be assigned a portion of the maximum score using the formula: 600 X technical proposal being evaluated/highest technical proposal

6.6 The four (4) offerors with the highest raw scores after the evaluation of the Technical Proposal is complete will be asked to conduct an onsite presentation of their proposal and demonstration of their proposed system for the system scenarios identified below. Offerors may use their own data set or may use the data set provided by the Department. Offerors who choose to use the data set provided by the Department may be awarded additional points.


The oral demonstration will be conducted for the Proposal Evaluation Committee. Responses become an official part of the proposal and will be evaluated and scored. Each offeror will be allowed up to ninety (90) minutes to present. The offeror’s costs associated with oral presentations are the responsibility of the offeror.

6.6.1 (E) Proposal Presentation: Offerors may receive up to one hundred (100) points on the presentation of their proposal. Offerors shall include the following items during the presentation of their proposal:

Provide a brief overview of the company, including information about company size and experience.

Explain how the proposed system best meets the requirements in the RFP and the needs and goals of the SHIP.

Introduce proposed team members.

Review of proposed schedule for management of the project

6.6.2 (E) System Scenarios: Offers may receive up to two hundred fifty (250) points on the demonstration of their proposed system using their own data set and an optional data set supplied by the Department for the system scenarios identified below. The offeror shall provide their data set and solution during the presentation. Offerors opting to also use the data set provided by the Department to conduct the demonstration of their proposed system may receive up to an additional fifty (50) points. The data set will be provided to the vendors on notification that they are invited to conduct oral presentations upon notification 6.6.2.1 Create a User Role

Demonstrate how a user role is created and how a user is assigned to that role.

6.6.2.2 Create a DashboardCreate and display a dashboard of data analytics output at the regional collaborative level for a day, a week, and a quarter.

6.6.2.3 Create a Standard ReportCreate and display a standard report of data analytics output at the statewide level using parameters selected by the Department.

6.6.2.4 Create a Self-Service ReportCreate a self-service environment and allow one (1) of the members of the evaluation team to create a self-service report of data analytics output at the county level that allows the user to select data, date ranges, and output format.

6.6.2.5 Modify the Data Set and Demonstrate Impact to Dashboard ResultAllow one (1) of the members of the evaluation team to change records within the data set. The offeror shall create and display a dashboard of data analytics output at the regional collaborative level for a day, a week, and a quarter showing the differences between data sets.


6.7 The Cost Proposal will be opened and evaluated for the top three (3) scoring offerors after the Oral Demonstration scores are combined with the scores for the Technical Proposal.

6.8 The scores for the Cost Proposal 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 overall total cost proposed will receive a score of 400. Other proposals will be assigned a portion of the maximum score using the formula: 400 X lowest cost proposal/cost proposal being evaluated.


EVALUATION CRITERIA

Mandatory Submission Requirements Met Pass/Fail

Technical Proposal: Business Information (3.8) 60 points

Organization and Staffing (3.9) 40 points

Scope of Work (4) 500 points

Subtotal 600 points

Oral Demonstrations (6.6) 400 points

Cost Proposal (Appendix A) 400 points

Total Points 1400 points

6.9 Best and Final Offers (BAFO) and other Proposal DiscussionsProposal discussions with individual offerors (including the utilization of one or more BAFOs) may be conducted in accordance with IDAPA 38.05.01.083 and .084, as determined by the State to be in its best interest. Note: Offerors should submit their best proposals initially as there is no guarantee that the State will conduct any discussions.


APPENDIX A

Cost Proposal and Billing Procedure(ME)

Part 1. Cost:

The contract resulting from this RFP shall be a FIRM FIXED FEE / INDEFINITE QUANTITY contract. The Department will pay and the Contractor shall receive up to the total sum proposed by the successful offeror for all goods and services satisfactorily delivered and authorized under the contract. The term of the contract is anticipated to be three (3) years but, upon mutual agreement, may be extended up to a total of four (4) years.

Costs shall remain firm throughout the life of the contract.

This section includes cost matrices that provide a consistent, fair, and equitable format for all offerors to submit cost proposals that include all costs associated with the provision of data analytics services that meets the needs of the State.

The cost matrices are designed to accommodate any and all qualified offerors and the design of the cost matrices do not prohibit any qualified offeror from submitting a cost response. The cost matrices enable a consistent comparison of cost along the same dimensions for all offerors.

The cost matrices are designed to accommodate costs for a vendor-hosted solution wherein the offeror configures an existing analytics system to accommodate the needs of the State. The offeror shall provide analytics output for a minimum of four (4) measures in the first year with the capability to expand to provide analytics output for additional measures in future years.

The offeror shall complete either the Itemized Cost Matrices OR the Milestones Cost Matrix. With either option, the total amount proposed shall be a fully burdened cost proposal and include all costs associated with the completion of the RFP requirements.

The minimum performance measures provided by the analytics system within the first year is four (4). This will include tobacco cessation intervention, weight assessment and counseling for children and adolescents, comprehensive diabetes care, and a fourth measure still to be identified by the State from Attachment 6 - Idaho’s Initial Performance Measure Catalog. The second year minimum number of performance measures provided by the analytics system is ten (10). The third year minimum number of performance measures provided by the analytics system is sixteen (16). Table 3 displays (by year) the anticipated number of clinics from which data will be used as well as the minimum number of performance measures that the system shall provide. Year 2 is inclusive of Year 1 numbers; Year 3 is inclusive of both Year 1 and Year 2 numbers.


Table 3 - Data Analytics Input and Output


Year 1 55 minimum 4



System configuration as used in the cost matrices requires that the offeror possess a fully developed analytics system that is configurable to meet the needs of the State.

Software license types under consideration for this RFP are defined in Table 4. Initially, there will be an estimated three hundred fifteen (315) users and seventy-seven (77) sites using the analytics system.

Table 4 - Software License Types

Software License Type Definition

Concurrent The analytics system can be accessed by a specific number of authorized users at the same time.

Named User The analytics system can be accessed by specific authorized users.

Site The analytics system can be accessed by all authorized users at a specific site.

Enterprise Subscription

The analytics system can be accessed by all authorized users at all sites.

Award will be ALL-OR-None based on the grand total of extended unit prices bid.


ITEMIZED COST MATRICES

Do not complete these cost matrices if you have chosen to submit your proposed costs using the Milestones Cost Matrix below. The Itemized Cost Matrices for Software, Hosting Services, Configuration, and Analytics Output ensure that all costs associated with this RFP are included in the offeror’s response. The structure of the itemized cost matrices are displayed in the tables below. The offeror may add rows to the cost matrices (above the Grand Total row) as needed. Base your cost projections on an estimated three hundred fifteen (315) users and seventy-seven (77) sites using the analytics system. Offerors shall complete all cost matrices in this section “Itemized Cost Matrices.” Sum each column and enter the amount in the appropriate column on the Grand Total line. Transfer the amounts on the Grand Total line from each cost to the applicable cell in the cost matrix for Total Costs. Do not include the cost of the Incremental Annual Fee for 1 More Unit in your overall cost. This is informational only.

Software Cost Matrix

Software

Software (Itemized) License Type(Concurrent, Named User, Site, Enterprise Subscription)

Number of Users or Sites Covered Under a Single

License

Costs Year 1 Costs Year 2 Costs Year 3 Incremental Annual Fee for 1 More Unit (i.e. license [depending on type])

$ $ $ $

$ $ $ $

$ $ $ $

Grand Total $ $ $

Hosting Services Cost Matrix

Hosting Services (including hardware, virtual ware, and maintenance and operations fees)

Service (Itemized) Costs Year 1 Costs Year 2 Costs Year 3

$ $ $

$ $ $

Grand Total $ $ $


Configuration Cost Matrix

Configure Existing Analytics System

Configurations (Itemized) Costs Year 1 Costs Year 2 Costs Year 3

$ $ $

$ $ $

$ $ $

Grand Total $ $ $

Analytics Output Cost Matrix

Analytics Output Development and Testing

Activity Costs Year 1 Costs Year 2 Costs Year 3

$ $ $

$ $ $

$ $ $

Grand Total $ $ $


The “Total Costs Matrix” below allows for the summation of the four (4) Itemized Cost Matrices above. Unlike the itemized matrices, the number of rows is fixed (no rows may be added), thus ensuring a fair comparison of total costs. All amounts on Grand Total lines from each cost matrix above shall be transferred to the applicable cell in the Total Costs matrix. After all numbers are transferred, sum each Total Itemized Costs column and enter the total on the Grand Total line for each column. Sum each row (Software, Hosting Services, Configuration, and Analytics Output) and enter the total on the applicable row under Total Costs. Add the Grand Total for each year together. Add the Total Costs for each line item together. These amounts should be the same. Enter that amount in the shaded cell. This is the amount you are proposing to complete all contract requirements for the entire contract period using this costing model.

Total Costs Matrix

Total Costs

Itemized Total Itemized CostsYear 1

Total Itemized CostsYear 2

Total Itemized CostsYear 3

TOTAL COSTS

Software $ $ $ $

Hosting Services $ $ $ $

Configuration $ $ $ $

Analytics Output $ $ $ $

Grand Total $ $ $ $


MILESTONES COST MATRIXDo not complete this cost matrix if you have chosen to submit your costs using the Itemized Cost Matrices above. The Milestones Cost Matrix below allows for the evaluation of cost on a “by milestone” basis. Milestones are the same for all offeror’s responses. Unlike the itemized matrices, the number of rows is fixed (no rows may be added), thus ensuring a fair comparison by fixed milestones. Enter your cost for each line item, then sum the costs and enter the amount on the Grand Total line. This is the amount you are proposing to complete all contract requirements for the entire contract period using this costing model.

Milestone Cost Matrix

Milestone Costs

Approved Project Management Plan $Approved Training Plan $Data input from a minimum of 55 clinics is ready for use (production) for analytics output. Ready is defined as “without any further transfer, transformation, modification, or manipulation, analytics output can be immediately produced from the data”.

$

Analytics output is in production for a minimum of four performance measures. $Data input from a minimum of 110 clinics is ready for use (production) for analytics output. Ready is defined as “without any further transfer, transformation, modification, or manipulation, analytics output can be immediately produced from the data”.

$

Analytics output is in production for a minimum of 10 performance measures. $Data input from 165 clinics is ready for use (production) for analytics output. Ready is defined as “without any further transfer, transformation, modification, or manipulation, analytics output can be immediately produced from the data”.

$

Analytics output is in production for a minimum of 16 performance measures. $

Grand Total $


Part 2. Billing Procedure:

The Contractor must provide the following information with each invoice:

1 Contract Number

2 Identification of Billing Period

3 Total amount billed for the billing period

4 Detailed description of services provided and associated amounts per the Cost Matrix line items

5 Contractor name, address, phone number, and email address

6. Unique identifier such as an invoice number

Invoices and reports are to be submitted to:Casey MoyerDepartment of Health and Welfare450 West State StreetBoise, ID 83702


APPENDIX B

Performance Metrics

Metric Description: Consistent Analytic Results: (SOW II.A.1.b&c) The Contractor shall implement system controls to ensure data integrity. The system shall provide consistent results for the same data inquiries regardless of delivery mechanism. A dashboard, a standard report, a self-service report, and any other delivery mechanism must be consistent in the results provided for the same data request. The results of all delivery mechanisms must also be validated by a direct query of the underlying data.

Required Level of Expectation: 100% The Contractor shall report to the Department immediately any discovery of a failure to meet the Required Level of Expectation.Method of Monitoring: Review of report data to ensure consistency.Strategy for Correcting Non-Compliance: The Department will document deficiencies and notify the Contractor when the Required Level of Expectation is not met. The Department may meet with the Contractor to discuss the issues and potential resolutions. The Contractor shall be responsible for correcting inconsistent results within seven (7) calendar days of discovery and at no additional cost to the Department. The Contractor shall also follow their standard process for erroneous output resolution to ensure the output is consistent and correct at no additional cost to the Department. The Department may also require the Contractor to submit a corrective action plan which meets Department approval. The corrective action plan shall be submitted within ten (10) business days after the Contractor has been notified in writing of the need for a corrective action plan. Continued non-compliance may result in additional remedies outlined in the Special Terms and Conditions, up to and including termination of the contract.

Metric Description: Erroneous Output: (SOW II.A.1.d) The Contractor’s system shall provide analytics results that are free of errors that meet the stated criteria.

Required Level of Expectation: 100% 95% The Contractor shall report to the Department immediately any discovery of a failure to meet the Required Level of Expectation.Method of Monitoring: Random Quality Assurance against source data (IHDE)Strategy for Correcting Non-Compliance: The Department will document deficiencies and notify the Contractor when the Required Level of Expectation is not met. The Department may meet with the Contractor to discuss the issues and potential resolutions. If the analytics system is found to contain an error in analytics output, the Contractor shall correct the error within seven (7) calendar days of discovery at no additional cost to the Department. The Contractor shall plainly post a description of the error on all output presentation formats impacted by the error along with an estimated time for resolutions at no additional cost to the Department. The Department may also require the Contractor to submit a corrective action plan which meets Department approval. The corrective action plan shall be submitted within ten (10) business days after the Contractor has been notified in writing of the need for a corrective action plan. Continued non-compliance may result in additional remedies outlined in the Special Terms and Conditions, up to and including termination of the contract.


Metric Description: Response Time: (SOW VI.A.16) The Contractor’s system shall return presentations of analytics outputs within three (3) seconds of user input (excluding any delays resulting from network issues beyond the systems’ control).

Required Level of Expectation: 100% The Contractor shall report to the Department immediately any discovery of a failure to meet the Required Level of Expectation.Method of Monitoring: Reports from Department network hardware (i.e. Wireshark) capable of measuring transmission speeds.Strategy for Correcting Non-Compliance: The Department will document deficiencies and notify the Contractor when the Required Level of Expectation is not met. The Department may meet with the Contractor to discuss the issues and potential resolutions. The Contractor shall be responsible to resolve any instance of slow response time within seven (7) calendar days of discovery of the issue at no additional cost to the Department. The Department may also require the Contractor to submit a corrective action plan which meets Department approval. The corrective action plan shall be submitted within ten (10) business days after the Contractor has been notified in writing of the need for a corrective action plan. Continued non-compliance may result in additional remedies outlined in the Special Terms and Conditions, up to and including termination of the contract.

Metric Description: Security Breach Notification: (SOW VII.B.3) The Contractor shall immediately report, via the designated process, any data breach involving ePHI or PII. Notification shall include all relevant details and a contact number of the individual who can provide additional relevant details of the incident.

Required Level of Expectation: 100% The Contractor shall report to the Department immediately any discovery of a failure to meet the Required Level of Expectation.Method of Monitoring: QA Audits, post-breach investigations Strategy for Correcting Non-Compliance: The Department will document deficiencies and notify the Contractor when the Required Level of Expectation is not met. The Department may meet with the Contractor to discuss the issues and potential resolutions. The Department may also require the Contractor to submit a corrective action plan which meets Department approval. The corrective action plan shall be submitted within ten (10) business days after the Contractor has been notified in writing of the need for a corrective action plan. Continued non-compliance may result in additional remedies outlined in the Special Terms and Conditions, up to and including termination of the contract.


APPENDIX C

Reports

This section identifies the monthly reports that will be required of the successful offeror during the contract period. Additional reports may be requested by the Department if the need arises.

Report Description: Project Management Report: The report shall include progress on tasks, milestones, resources, and deliverables; actual time to complete versus scheduled time; issues and risks; change requests by new, status, and completed; and open action items and shall require both a weekly status and a monthly summary.Report Format: As agreed upon between the Department and the ContractorReport Due: Weekly Status Report on a mutually agreed upon day each week; Monthly Summary Report within ten (10) calendar days after the end of each month

Report Description: Training Report: The report shall include the number and type of trainings conducted, number of users trained, new training modules introduced (when appropriate), future training module development progress (when appropriate), and training satisfaction survey results.Report Format: As agreed upon between the Department and the ContractorReport Due: Monthly, within ten (10) calendar days after the end of each month

Report Description: Support Services Report: The report shall include the number of user accounts added, deleted, and disabled; number of user support assistance requests and number resolved; type of support provided; level of support provided; support response time; number of issues escalated; and type of issues escalated.Report Format: As agreed upon between the Department and the ContractorReport Due: Monthly, within ten (10) calendar days after the end of each month

Report Description: System Usage Report: The report shall include the total number of reports produced, total number of reports produced by performance metric, total number of standard reports produced, total number of self-service reports produced, number of report failures, and number of records obtained or refreshed daily.Report Format: As agreed upon between the Department and the ContractorReport Due: Quarterly, within ten (10) calendar days after the end of each quarter

Report Description: System Security Report: The report shall include the number of security incidents (data breaches, successful malicious code infections, etc.) and implemented mitigation strategies; results from any vulnerability assessments or penetrations testing conducted; and security recommendations to the Department to ensure continued protection of provider and other sensitive data.Report Format: As agreed upon between the Department and the ContractorReport Due: Quarterly, within ten (10) calendar days after the end of each quarter


Report Description: System Audit Report: The report shall include a standard audit trail (i.e. system status) reporting using requirements in the contract as requested by the Department.Report Format: As agreed upon between the Department and the ContractorReport Due: As requested by the Department


APPENDIX D

Special Terms And Conditions

I. DEFINITIONS . As used in the Contract, the following terms shall have the meanings set forth below:

A. Contract Manager shall mean that person appointed by the Department to administer the Contract on behalf of the Department. "Contract Manager" includes, except as otherwise provided in the Contract, an authorized representative of the Contract Manager acting within the scope of his or her authority. The Department may change the designated Contract Manager from time to time by providing notice to Contractor as provided in the Contract.

B. Department shall mean the State of Idaho, Department of Health and Welfare, its divisions, sections, offices, units, or other subdivisions, and its officers, employees, and agents.

II. CONTRACT EFFECTIVENESS . It is understood that this Contract or any Amendment is effective when it is signed by all parties, or at a later date if specified in the Contract or Amendment. The Contractor shall not render services to the Department until the Contract or Amendment has become effective. The Department will not pay for any services rendered prior to the effective date of the Contract or Amendment.

III. REASSIGNMENT OF CONTRACTOR EMPLOYEES The Department shall have the right, after having consulted with the Contractor, to require the Contractor to reassign or otherwise remove from the contract any Contractor employee or subcontractor found in good faith to be unacceptable to the Department.

IV. RECORDS AND DATA .

A. Fiscal Records The Contractor shall maintain fiscal records, including its books, audit papers, documents, and any other evidence of accounting procedures and practices, which sufficiently and properly reflect all direct and indirect costs of any nature expended in the performance of the Contract.

B. Records Maintenance The Contractor shall maintain all records and documents relevant to the Contract for three (3) years from the date of final payment to Contractor. If an audit, litigation or other action involving records is initiated before the three (3) year period has expired, the Contractor shall maintain records until all issues arising out of such actions are resolved, or until an additional three (3) year period has passed, whichever is later.

C. Termination of Contract If the existence of the Contractor is terminated by bankruptcy or any other cause, all program and fiscal records related to the Contract in the Contractor's possession shall become the property of the Department and the Contractor shall immediately deliver such records to the Contract Manager.


D. Records Review All records and documents relevant to the Contract, including but not limited to fiscal records, shall be available for and subject to inspection, review or audit, and copying by the Department and other personnel duly authorized by the Department, and by federal inspectors or auditors. The Contractor shall make its records available to such parties at all reasonable times, at either the Contractor's principal place of business or upon premises designated by the Department.

V. CUSTOMER SERVICE .

A. Telephone Contractors who have direct contact with the public in fulfilling this contract shall have their main, published telephone numbers answered by a person during normal business hours. Voice mail for contractor staff shall provide an option for the caller to obtain immediate assistance if necessary. The Contractor shall endeavor to return telephone calls the same day, and shall respond to phone calls and e-mails not later than forty-eight (48) hours or two (2) business days after the initial contact, whichever is later.

B. Correspondence The Contractor shall respond to written correspondence within ten (10) business days. The Contractor shall provide clear, understandable, timely and accurate written information to Department customers as required by this Contract.

C. Policies The Contractor shall treat Department staff and customers with respect and dignity, and shall demonstrate a caring attitude to all who ask for assistance. Contractors shall have a written customer service policy that describes how customer service will be incorporated into policies and training.

VI. BINDING EFFECT OF FEDERAL PURCHASE OF SERVICE REGULATIONS . The Contract is subject to the provisions of any relevant federal regulations and any relevant provisions of agreements between the State of Idaho and the United States, including but not limited to State Plans, in effect at the time the Contract is executed, or which thereafter become effective. Such regulations and agreements are on file in the Central Office of the Department and are available for inspection by the Contractor during regular business hours.

VII. FEDERAL AND STATE AUDIT EXCEPTIONS . If a federal or state audit indicates that payments to the Contractor fail to comply with applicable federal or state laws, rules or regulations, the Contractor shall refund and pay to the Department any compensation paid to Contractor arising from such noncompliance, plus costs, including audit costs.

VIII.COMPLIANCE WITH CERTAIN LAWS .

A. HIPAA The Contractor acknowledges that it may have an obligation, independent of this contract, to comply with the Health Insurance Portability and Accountability Act (HIPAA), Sections 262 and 264 of Public Law 104-191, 42 USC Section 1320d, and federal regulations at 45 CFR Parts 160, 162 and 164. If applicable, the Contractor shall comply with all amendments to the law and federal regulations made during the term of the Contract.


B. Lobbying

1. The Contractor certifies that none of the compensation under the Contract has been paid or will be paid by or on behalf of the Contractor to any person for influencing or attempting to influence an officer or employee of any governmental agency, a member, officer or employee of Congress or the Idaho Legislature in connection with the awarding, continuation, renewal, amendment, or modification of any contract, grant, loan, or cooperative agreement.

2. If any funds, other than funds provided by the Contract, have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any governmental agency, a member, officer or employee of Congress or the State Legislature in connection with the Contract, the Contractor shall complete and submit Standard Form LLL, "Disclosure Form to Report Lobbying," in accordance with its instructions, and submit a copy of such form to the Department.

3. The Contractor shall require that the language of this certification be included in any subcontract, at all tiers, (including grants, subgrants, loans, and cooperative agreements) entered into as a result of the Contract, and that all sub-recipients shall certify and disclose as provided herein.

4. The Contractor acknowledges that a false certification may be cause for rejection or termination of the Contract, subject the Contractor to a civil penalty, under 31 U.S.C. § 1352, of not less than $10,000.00 and not more than $100,000.00 for each such false statement, and that the Contractor's execution of the Contract is a material representation of fact upon which the Department relied in entering the Contract.

C. Qualification The Contractor certifies to the best of its knowledge and belief that it and its principals:

1. Are not presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from performing the terms of the Contract by a government entity (federal, state or local);

2. Have not, within a three (3) year period preceding the Contract, been convicted of or had a civil judgment rendered against them for commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (federal, state, or local) transaction or contract under a public transaction; violation of federal or state antitrust statutes or commission of embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements, or receiving stolen property;

3. Are not presently indicted for or otherwise criminally or civilly charged by a government entity (federal, state or local) with commission of any of the offenses enumerated in paragraph 2 of this certification; and


4. Have not within a three (3) year period preceding the Contract had one or more public transactions (federal, state, or local) terminated for cause or default.

5. The Contractor acknowledges that a false statement of this certification may be cause for rejection or termination of the Contract and subject the Contractor, under 18 U.S.C. § 1001, to a fine of up to $10,000.00 or imprisonment for up to five (5) years, or both.

D. Faith-Based Organization If the Contractor is a faith-based organization, the Contractor and all approved subcontractors shall:

1. Segregate contract funds in a separate account.

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.

3. Ensure that Department-referred clients' participation in religious activities, including worship, scripture study, prayer or proselytization, is only on a voluntary basis.

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 religious activities, their right to request an alternative provider and the process for doing so.

5. Ensure that contract funds are not expended on inherently religious activities.

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

E. Tribes If the Contractor is a Tribe, the Contractor and Department recognize that services performed pursuant to this Contract by the Contractor and all approved subcontractors within reservation boundaries are subject to applicable laws, ordinances and regulations of the Tribe. Nothing in this Contract should be construed as a waiver of sovereign immunity.

F. Single Audit Act The Contractor acknowledges that it may have an obligation; independent of this contract, to comply with the terms of the "Single Audit Act" of 1984. Funds provided under the Contract may be used to pay for compliance with this act in proportion to other funding sources available to the Contractor for the services provided pursuant to the Contract.

G. Local Contribution To Funding If funding for the Contract is tied to a local contribution or match: (1) The Contractor certifies that none of the local contribution or match funds are federal funds, are derived from or are in lieu of federal funds, and none of said funds have been used, or have been substituted for funds used, to earn other federal funds. (2) The Contractor further certifies that any costs incurred by the Contractor prior to the Contract will not be allowable to or included as a cost of any other state or federally financed program in either the current period or any prior period.


IX. CONFLICT OF INTEREST .

A. Public Official No official or employee of the Department and no other public official of the State of Idaho or the United States government who exercises any functions or responsibilities in the review or approval of the undertaking or carrying out of the Contract shall, prior to the termination of the Contract, voluntarily acquire any personal interest, direct or indirect, in the Contract or proposed Contract.

B. Contractor The Contractor covenants that it presently has no interest and shall not acquire any interest, direct or indirect, that would conflict in any manner or degree with the performance of its services hereunder. The Contractor further covenants that in the performance of the Contract, no person who has any such known interests shall be employed.

X. REMEDIES .

A. Remedial Action If any of the Contractor’s responsibilities do not conform to Contract requirements, the Department shall consult with the Contractor and may at its sole discretion require any of the following remedial actions, taking into account the nature of the deficiency: (1) require the Contractor to take corrective action to ensure that performance conforms to Contract requirements; (2) reduce payment to reflect the reduced value of services received; (3) require the Contractor to subcontract all or part of the service at no additional cost to the Department; or (4) terminate the Contract.

B. Termination for Convenience The Department or the Contractor may cancel the Contract at any time, with or without cause, upon thirty (30) ninety (90) calendar days written notice to the other party specifying the date of termination.

C. Termination for Cause Either party may terminate the Contract immediately upon written notice, or upon such notice as such party, in its sole discretion, deems appropriate, if at any time: (a) the other party is in material breach of any warranty, term, condition, covenant or obligation under the Contract; (b) judicial interpretation of federal or state laws, regulations, or rules renders fulfillment of the Contract infeasible or impossible; (c) Contractor's license or certification required by law is suspended, not renewed, or is otherwise not in effect at the time service is provided; or (d) Contractor fails to comply with any applicable law, regulation, or rule.

D. Effect of Termination Upon termination by the Department, the Contractor shall: (a) promptly discontinue all work, unless the termination notice directs otherwise; (b) promptly return to the Department any property provided by the Department pursuant to the Contract; and, (c) deliver or otherwise make available to the Department all data, reports, estimates, summaries and such other information and materials as may have been accumulated by Contractor in performing the Contract, whether completed or in process. Upon termination by the Department, the Department may take over the services and may award another party a contract to complete the services contemplated by the Contract.


Upon termination for cause, the Department shall be entitled to reimbursement from Contractor for losses incurred as a result of the Contractor's breach.

E. Survival of Terms Any termination, cancellation, or expiration of the Contract notwithstanding, provisions which are intended to survive and continue shall survive and continue, including, but not limited to, the provisions of these Special Terms and Conditions, Sections IV (Records and Data), VII (Federal and State Audit Exceptions), VIII (Compliance with Certain Laws), and the State of Idaho Standard Contract Terms and Conditions, Sections 9 (Contract Relationship) and 12 (Indemnification).

XI. MISCELLANEOUS .

A. Disposition of Property At the termination of the Contract, the Contractor shall comply with relevant federal and state laws, rules and regulations and, as applicable, 2 CFR §§ 200.310-316 concerning the disposition of property purchased wholly or in part with funds provided under the Contract.

B. Time of Performance Time is of the essence with respect to the obligations to be performed under the Contract; therefore, the parties shall strictly comply with all times for performance.

C. Headings The captions and headings contained herein are for convenience and reference and are not intended to define or limit the scope of any provision of the Contract.


APPENDIX E

Riders

Insurance

For the term of the Contract and until all services specified in the Contract are completed, the Contractor shall maintain in force, at its own expense, the following insurance.

Commercial General Liability Insurance and, if necessary, Commercial Umbrella Liability Insurance with a limit of not less than one million dollars ($1,000,000) each occurrence. Insurance required by this section shall name the State of Idaho, Department of Health and Welfare as an additional insured.

Automobile Liability Insurance and, if necessary, Umbrella Liability Insurance with a limit of not less than one million dollars ($1,000,000) each accident. Insurance required by this section shall name the State of Idaho, Department of Health and Welfare as an additional insured.

Professional Liability Insurance with a limit of not less than one million dollars ($1,000,000) each occurrence.

Workers' Compensation Insurance which includes Employer Liability Insurance and shall comply with Idaho Statutes regarding Workers' Compensation in the amount of: $100,000 per accident; $500,000 disease policy limit; and $100,000 disease, each employee.

If any of the liability insurance required for this contract is arranged on a "claims-made" basis, "tail coverage" will be required at the completion or termination of this contract for a duration of twenty-four (24) months thereafter. Continuous "claims-made" coverage will be acceptable in lieu of "tail-coverage" provided the retroactive date is on or before the effective date of this contract, or twenty-four (24) months "prior acts" coverage is provided. Contractor will be responsible for furnishing certification of "tail coverage" or continuous "claims-made" coverage.

Prior to performing any services, the Contractor shall provide certificates of insurance to the Department. The Contractor is also required to maintain current certificates on file with the Department and to provide updated certificates upon request. Failure to provide the required certificates of insurance shall constitute a default under this Contract and upon such failure the Department may, at its option, terminate the Contract. Insurance required by this section shall be policies or contracts of insurance issued by insurers approved by the Department. Should any of above described policies be cancelled before the expiration date thereof, notice shall be delivered in accordance with the policy provision.

The Contractor shall further ensure that all policies of insurance are endorsed to read that any failure to comply with the reporting provisions of this insurance, except for the potential exhaustion of aggregate limits, shall not affect the coverage(s) provided to the State of Idaho, Department of Health and Welfare.


Please send updated certificates to:

Idaho Department of Health and WelfareContracting & Procurement Services Unit -- 9th Floor450 West State StreetBoise, ID 83702

Business AssociateSpecific obligations and activities of Contractor to protect confidential information in accord with HIPAA privacy and security requirements in compliance with 45 CFR § 164.504(e).

Contractor agrees to not use or disclose confidential information other than as permitted or required by the contract or as required by law.

Contractor agrees to use appropriate safeguards, and to comply with Subpart C of 45 CFR Part 164 with respect to electronic confidential information, to prevent use or disclosure of confidential information other than as provided for by this contract.

Contractor agrees to report to the Department any use or disclosure of confidential information not provided for by this contract of which it becomes aware, including breaches of unsecured confidential information as required at 45 CFR § 164.410, and any security incident of which it becomes aware. Reporting to the Department will be done no later than 10 business days after discovery of breach.

Contractor agrees to ensure that any agent, including any subcontractors, that create, receive, maintain, or transmit confidential information on behalf of the Contractor agree to the same restrictions, conditions, and requirements that apply through this contract to Contractor with respect to such information.

Contractor agrees to provide access to confidential information, at the request of Department, and in the time and manner as directed by Department, to an individual in order to meet the requirements under 45 CFR § 164.524.

Contractor agrees to make any amendment(s) to confidential information that the Department directs or agrees to pursuant to 45 CFR § 164.526 at the request of Department or an individual.

Contractor agrees to make internal practices, books, and records, including policies and procedures relating to the use and disclosure of confidential information received from, or created or received by Contractor on behalf of the Department available to the Secretary of Health and Human Services, in a time and manner designated by the Secretary, for purposes of the Secretary determining Department's compliance with the Privacy Rule.

Contractor agrees to document any disclosures of confidential information and information related to such disclosures as would be required for Department to respond to a request by an individual for an accounting of disclosures of confidential information in accordance with 45 CFR § 164.528.

Contractor agrees to provide to Department or an individual information collected in accordance with this contract, to permit Department to respond to a request by an individual for an accounting of disclosures of confidential information in accordance with 45


CFR § 164.528.

Permitted Uses and Disclosures by Contractor

a. Except as otherwise limited in this contract, Contractor may use or disclose confidential information to perform functions, activities, or services for, or on behalf of, Department as specified in the scope of work provided that such use or disclosure would not violate the privacy, breach notification or security rule if done by Department or the minimum necessary policies and procedures of the Department.

b. Contractor may also use or disclose confidential information as required by law or other arrangement pursuant to 45 CFR § 164.504(e)

c. Contractor may use confidential information to report violations of law consistent with 45 CFR § 164.502(J)(1).

Obligations of Department

a. Department shall notify Contractor of any limitation(s) in its notice of privacy practices of Department in accordance with 45 CFR § 164.520, to the extent that such limitation may affect Contractor's use or disclosure of confidential information.

b. Department shall notify Contractor of any changes in, or revocation of, permission by an individual to use or disclose confidential information, to the extent that such changes may affect Contractor's use or disclosure of confidential information.

c. Department shall notify Contractor of any restriction to the use or disclosure of confidential information that Department has agreed to in accordance with 45 CFR § 164.522, to the extent that such restriction may affect Contractor's use or disclosure of confidential information.

Permissible Requests by Department

Department shall not request Contractor to use or disclose confidential information in any manner that would not be permissible under the privacy or security rule if done by Department.

a. Action upon Termination of the Contract

Upon termination of this contract, for any reason, Contractor shall return or destroy all confidential information received from Department, or created, maintained or received by Contractor on behalf of Department.

In the event that Contractor determines that returning or destroying the confidential information is infeasible, Contractor shall notify the Department of the conditions that make return or destruction infeasible. If the Department agrees that return or destruction of confidential information is infeasible, Contractor shall extend the protections of this contract to such confidential information and limit further uses and disclosures of such confidential information to those purposes that make the return or destruction infeasible, for so long as Contractor maintains such confidential information. Contractor shall also continue to use appropriate safeguards and comply with Subpart C of 45 CFR Part 164 with respect to electronic confidential information if return or destruction is infeasible.


ATTACHMENT 1OFFEROR QUESTIONS

PLEASE DO NOT IDENTIFY YOUR NAME OR YOUR COMPANY’S NAME OR PRODUCT NAMES OF INTELLECTUAL PROPERTY IN YOUR QUESTIONS.

ADD ROWS BY HITTING THE TAB KEY WHILE WITHIN THE TABLE AND WITHIN THE FINAL ROW.

The following instructions must be followed when submitting questions using the question format on the following page.

1. DO NOT CHANGE THE FORMAT OR FONT. Do not bold your questions or change the color of the font.

2. Enter the RFP section number that the question is for in the “RFP Section” field (column 2). If the question is a general question not related to a specific RFP section, enter “General” in column 2. If the question is in regards to a State Term and Condition or a Special Term and Condition, state the clause number in column 2. If the question is in regard to an attachment, enter the attachment identifier (example “Attachment A”) in the “RFP Section” (column 2), and the attachment page number in the “RFP page” field (column 3).

3. Do not enter text in column 5 (Response). This is for the State’s use only.4. Once completed, this form is to be e-mailed per the instructions in the RFP. The e-mail

subject line is to state the RFP number followed by “Questions.”


ARFP1507 / IPRO RFP16000146 Statewide Healthcare Innovation Plan (SHIP) Data Analytics

Question RFP Section RFP Page

Question Response

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20


ATTACHMENT 2REFERENCES

(E)

INSTRUCTIONS TO THE OFFEROR:

Offerors are allowed three (3) completed reference questionnaires. The completed references questionnaires must be from individuals, companies, or agencies with knowledge of the offeror’s experience that is similar in nature to the products or services being requested by this RFP, and are within the last three (3) years from the date this RFP was posted to IPRO.

References not received prior to the RFP closing date and time will receive a score of zero (0) for that reference. References outside the designated number of years (see paragraph above), and references determined to be not of a similar nature to the products or services requested by this RFP will also receive a score of zero (0) points. Determination of similar will be made by using the information provided by the reference in Section II of the Reference Questionnaire, General Information and any additional information provided by the reference.

If more than three (3) qualifying references are received, only the first three (3) fully completed references received will be used for evaluation purposes.

1. Offerors must complete the following information on page 2 of the “Reference’s Response To” document before sending it to the Reference for response.

a. Print the name of your reference (company/organization) on the “REFERENCE NAME” line.

b. Print the name of your company/organization on the “OFFEROR NAME” line.

2. Send the “Reference’s Response To” document to your references to complete.

NOTE: It is the offeror’s responsibility to follow up with their references to ensure timely receipt of all questionnaires. Offerors may e-mail the RFP Lead prior to the RFP closing date to verify receipt of references.


REFERENCE QUESTIONNAIREREFERENCE’S RESPONSE TO:

RFP Number: ARFP1507 / IPRO RFP16000146RFP Title: Statewide Healthcare Innovation Plan (SHIP) Data Analytics

REFERENCE NAME (Company/Organization): ______________________________________

OFFEROR (Vendor) NAME (Company/Organization): _________________________________ has submitted a proposal to the State of Idaho, Department of Health and Welfare, to provide the following services: Data Analytics services for the Idaho Statewide Healthcare Innovation Plan project. We’ve chosen you as one of our references.

INSTRUCTIONS 1. Complete Section I. RATING using the Rating Scale provided.

2. Complete Section II. GENERAL INFORMATION (This section is for information only and will not be scored.)

3. Complete Section III. ACKNOWLEDGEMENT by manually signing and dating the document. (Reference documents must include an actual signature.)

4. E-mail or fax THIS PAGE and your completed reference document, SECTIONS I through III to:

RFP Lead: Bev BerendsGrants/Contracts Officer

E-mail: [email protected]

Fax: 208-639-5715

5. This completed document MUST be received no later than November 24, 2015 at 5:00 p.m. Mountain Time. Reference documents received after this time will not be considered. References received without an actual signature will not be accepted.

6. DO NOT return this document to the Offeror (Vendor).

7. In addition to this document, the State may contact references for further clarification if necessary.


Section I. RATING

Using the Rating Scale provided below, rate the following numbered items by circling the appropriate number for each item:

Rating Scale Category Score

Poor or Inadequate Performance 0

Below Average 1 – 3

Average 4 – 6

Above Average 7 - 9

Excellent 10

Circle ONE number for each of the following numbered items:

1. Rate the overall quality of the vendor’s services:

10 9 8 7 6 5 4 3 2 1 0

2. Rate the response time of this vendor:

10 9 8 7 6 5 4 3 2 1 0

3. Rate how well the agreed upon, planned schedule was consistently met and deliverables provided on time. (This pertains to delays under the control of the vendor):

10 9 8 7 6 5 4 3 2 1 0

4. Rate the overall customer service and timeliness in responding to customer service inquiries, issues and resolutions:

10 9 8 7 6 5 4 3 2 1 0

5. Rate the knowledge of the vendor’s assigned staff and their ability to accomplish duties as contracted:

10 9 8 7 6 5 4 3 2 1 0

6. Rate the accuracy and timeliness of the vendor’s billing and/or invoices:

10 9 8 7 6 5 4 3 2 1 0


7. Rate the vendor’s ability to quickly and thoroughly resolve a problem related to the services provided:

10 9 8 7 6 5 4 3 2 1 0

8. Rate the vendor’s flexibility in meeting business requirements:

10 9 8 7 6 5 4 3 2 1 0

9. Rate the likelihood of your company/organization recommending this vendor to others in the future:

10 9 8 7 6 5 4 3 2 1 0

Section II. GENERAL INFORMATION

1. Please include a brief description of the services provided by this vendor for your business:

2. During what time period did the vendor provide these services for your business?

Month:_________ Year:_________ to Month:_________ Year:_________

Section III. ACKNOWLEDGEMENT

I affirm to the best of my knowledge that the information I have provided is true, correct, and factual:

____________________________________ ________________________________Signature of Reference Date

____________________________________ ________________________________Print Name Title

____________________________________Phone Number ____________________________________E-mail address


ATTACHMENT 3PRE-PROPOSAL CONFERENCE REGISTRATION FORM

PRE-PROPOSAL CONFERENCE Date: Thursday, October 15, 2015, 10:30 a.m. Mountain Time

Agency: Idaho Department of Health and Welfare

RFP #: ARFP1507 / IPRO RFP16000146Title: Statewide Healthcare Innovation Plan (SHIP) Data Analytics

Verbal Information: Questions concerning an RFP must be directed in writing to the designated purchasing official in the period of time prescribed in the RFP document. Bids, Proposals, or Quotations deviating from the specifications by any means other than an authorized written addendum will be subject to rejection. The State will not be responsible for any verbal information given to Vendors by anyone other than an authorized purchasing official. Reliance on any verbal representation is at the Vendor’s sole risk.

Potential offerors choosing to participate in the pre-proposal conference must pre-register by submitting this completed form, via e-mail, to the RFP Lead’s designee at [email protected]. Once the RFP Lead receives your completed form, you will be provided with phone conferencing and meeting details. Please indicate in the appropriate column if your attendance will be by phone. The deadline to register for the Pre-Proposal Conference is 3:00 p.m. Mountain Time on Wednesday, October 14, 2015.

PLEASE PRINT:

Name Company Email Address Phone Number

By Phone


mailto:[email protected]

ATTACHMENT 4FINANCIAL INFORMATION

(E)

Offerors are required to provide a current D&B Comprehensive Insight Plus credit report or current Experian ProfilePlus report, and the appropriate NAICS code or SIC code (http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2007.) Credit report must be current and have been established within thirty (30) calendar days of the proposal closing date.

1 The offeror should stamp “Trade Secret” or “Confidential” on each page of the Credit report information that it does not want released. The information will be held in confidence to the extent that law allows.

2 State agencies will be exempt from submitting Credit report information and the score assigned will be zero (0.)

3 Credit reports must be for the exact organization submitting the proposal. The credit report cannot be combined or consolidated with the information from any entity other than the company submitting the proposal. If the offeror’s name on the proposal does not match the name on the credit report, the proposal will receive a score of zero (no points) for the credit score. Also, not submitting a credit report will result in a score of zero (no points).

4 The State will evaluate the credit information provided to answer the following question:

4.1 How well does management control expenses and manage resources? Credit Report Score


http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2007

ATTACHMENT 5LIST OF ACRONYMS USED

Acronyms DefinitionCMMI Center for Medicare and Medicaid Innovation

CSV Comma Separated Values

EHR Electronic Health Record

ePHI Electronic Protected Health Information

FIPS Federal Information Processing Standards

FTP File Transfer Protocol

HIE Health Information Exchange

HIPAA Health Insurance Portability and Accountability Act

HIT Health Information Technology

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

HTTPS Secure Hypertext Transfer Protocol

IDS/IPS Intrusion Detection/Intrusion Prevention

IHC Idaho Healthcare Coalition

IHDE Idaho Health Data Exchange

IPSEC Internet Protocol Security

NIST National Institute of Standards and Technology

OWASP Open Web Application Security Project

PCMH Patient-Centered Medical Home

PII Personally Identifiable Information

PMBOK Project Management Body of Knowledge

PMP Project Management Plan

RBAC Roles Based Access Control

RC Regional Collaboratives

RFP Request for Proposal

sFTP Secure File Transfer Protocol

SHIP Statewide Healthcare Innovation Plan

SLA Service Level Agreement

SQL Structured Query Language

SS Support Services (requirement category)


Acronyms DefinitionSSAE Statement on Standards for Attestation Engagements

SSL Secure Sockets Layer

SSP System Security Plan

TLS Transport Layer Security

URL Uniform Resource Locator

WBS Work Breakdown Structure


ATTACHMENT 6IDAHO’S INITIAL PERFORMANCE MEASURE CATALOG

Measure Name (and Source) Measure Description Rationale for the Measure

Screening for clinical depression.

Percentage of patients aged 12 years and older screened for clinical depression using a standardized tool and follow up plan documented.

In Idaho, 22.5% of persons aged 18 or older had a mental illness and 5.8% had SMI in 2008–2009 while 7.5% of persons aged 18 or older had a major depressive episode (MDE). During the period 2005–2009, 9% of persons aged 12-17 had a past MDE.

Suicide is the second leading cause of death for Idahoans aged 15–34 and for males aged 10–14.This measure aligns with Healthy People 2020.

Measure pair: (a.) Tobacco use assessment.

(b.) Tobacco cessation intervention (SIM)

Percentage of patients who were queried about tobacco use one or more times during the two-year measurement period.Percentage of patients identified as tobacco users who received cessation intervention during the two-year measurement period.

In Idaho, 16.9% of the adult population were smokers in 2010 (>187,000 individuals).Idaho ranks fifteenth in the country in prevalence of adult smokers and its smoking-attributable mortality rate is ranked eighth in the country.

Asthma ED visits. Percentage of patients with asthma who have greater than or equal to one visit to the ED for asthma during the measurement period.

While asthma prevalence (those with current asthma) in Idaho was 8.8% in 2010, reduction of emergency treatment for uncontrolled asthma is a reflection of high quality patient care and patient engagement.

Acute care hospitalization (risk-adjusted).

Percentage of patients who had to be admitted to the hospital.

While Idaho has one of the country’s lowest hospital admission rates (81/1000 in 2011), this measure is held as one of the standards for evaluation of utilization and appropriate use of hospital services as part of an integrated network.

Readmission rate within 30 days.

Percentage of patients who were readmitted to the hospital within 30 days of discharge from the hospital.

Data currently unavailable. Metric will be used to establish baseline.


Measure Name (and Source) Measure Description Rationale for the MeasureAvoidable emergency care without hospitalization (risk-adjusted).

Percentage of patients who had avoidable use of a hospital ED.

While Idaho has one of the country’s lowest hospital ED utilization rates (327/1000, 2011), this measure is still held as one of the standards for evaluation of utilization and appropriate use of emergency services, as well as a reflection of quality and patient engagement in primary care related to avoidable treatment.

Elective delivery. Rate of babies electively delivered before full-term.

Data currently unavailable. Metric will be used to establish baseline.

Low birth weight rate (PQI 9).

This measure is used to assess the number of low birth weight infants per 100 births.

While Idaho’s percentage of low birth weight babies is low compared to the national average, the opportunity to improve prenatal care across settings is an indicator of system quality.1,355 babies in Idaho had low birth weights in 2011, compared to 1,160 in 1997.

Adherence to antipsychotics for individuals with psychotic diagnoses.

The percentage of individuals 18–64 years of age during the measurement year with a psychotic diagnosis who were dispensed and remained on an antipsychotic medication for at least 80% of their treatment period.

Idaho has a 100% shortage of mental health providers statewide. Without these critical providers, there is little or no support for patient engagement and medication adherence.Improved adherence may be a reflection of improved access to care and patient engagement.

Weight assessment and counseling for children and adolescents (SIM).

Percentage of children, two through 17 years of age, whose weight is classified based on Body Mass Index (BMI), who receive counseling for nutrition and physical activity.

In 2011, 13.4% of children were overweight as defined by being above the 85th percentile, but below the 95th percentile for BMI by age and sex, while 9.2% were obese, i.e., at or above the 95th percentile for BMI by age and sex.


Measure Name (and Source) Measure Description Rationale for the MeasureComprehensive diabetes care (SIM).

The percentage of patients 18-75 with a diagnosis of diabetes, who have optimally managed modifiable risk factors (A1c<8.0%, LDL<100 mg/dL, blood pressure<140/90 mm Hg, tobacco non-use, and daily aspirin usage for patients with diagnosis of IVD) with the intent of preventing or reducing future complications associated with poorly managed diabetes.

Adult diabetes prevalence in 2010 was 8.0%. Overall, this represented one in 12 people in Idaho had diabetes.

Access to care. Members report adequate and timely access to PCPs, BEHAVIORAL HEALTH, and dentistry (measure adjusted to reflect shortages in Idaho).

Idaho has a critical access shortage of primary care providers, behavioral health providers, and dentists across the State which impedes access to the appropriate level of care.

Childhood immunization status.

Percentage of children two years of age who had four DtaP/DT, three IPV, one MMR, three H influenza type B, three hepatitis B, one chicken pox vaccine, and four pneumococcal conjugate vaccines by their second birthday. The measure calculates a rate for each vaccine and two separate combination rates.

While there have been significant improvements in immunization rates, Idaho ranks 43rd in the nation with an immunization rate of 87.33% in 2012.This measure aligns with Healthy People 2020.

Adult BMI Assessment. The percentage of members 18 to 74 years of age who had an outpatient visit and who’s BMI was documented during the measurement year or the year prior to the measurement year.

In 2010, 62.9% of adults in Idaho were overweight, and 26.9% of adults in Idaho were obese.


Measure Name (and Source) Measure Description Rationale for the MeasureNon-malignant opioid use.

Percent of patients chronically prescribed an opioid medication for non-cancer pain (defined as three consecutive months of prescriptions) that have a controlled substance agreement in force (updated annually).

From 2010–2011, Idaho had the fourth highest non-medical use of prescription pain relievers in the country among persons aged 12 or older at 5.73%.


ATTACHMENT 7OFFEROR’S REQUEST FOR PROPOSAL (RFP) CHECKLIST

It is the responsibility of the offeror to review all instructions on IPRO’s Request for Proposal solicitation, download attachments, including amendments, and complete all required RFP responses and submittals. The following is a checklist for offerors to consider as they complete and submit their response to the RFP. The checklist provided below is NOT intended as an exhaustive checklist of all items, but rather a list of items for offerors to consider as they complete their proposal response.

RFP Ref. # or section

Description Yes No

IPRO RFP solicitation & Section 2.3

State of Idaho RFP signature page signed with original handwritten signature executed in ink OR an electronic signature.

Section 2.3.2 & 2.3.4

Technical Proposal (1 original and 5 copies) clearly marked as required and sealed with the offerors name on the outside of the package.

Section 2.3.5 One (1) original of the Cost Proposal clearly marked as required and sealed with the offeror’s name on the outside of the package.

Section 2.3.3 One (1) electronic copy of the full proposal, including the Cost Proposal and any attachments, and one (1) electronic copy of the redacted proposal (if applicable) on CD or USB device (Word format).

Section 3.3 Cover letter completed and signed with original handwritten signature, executed in ink, and included in the Technical Proposal.

Section 3.4 Acknowledgement of AmendmentsSection 3.6 Table of contents included in the Technical Proposal.Section 3.7 Executive Summary included in the Technical Proposal.Section 3.8 Business information – description of experience included in

the Technical Proposal.Section 3.8.2 Attachment 2 – References: Confirmed three (3) references’

responses submitted.Section 3.8.3 Attachment 4 – Financial information completed and included

in the Technical Proposal.Section 3.9 Organization and staffing information included in the Technical

Proposal.

Section 4 Completed responses to Section 4 Scope of Work

Section 5 & Appendix A

Completed Cost Proposal and Billing Procedure – Appendix A

WE RECOMMEND YOU SUBMIT YOUR PROPOSAL THROUGH FEDEX, UPS OR HAND CARRY. THE DEPARTMENT ONLY RECEIVES USPS DELIVERY ONCE EACH MORNING AND PROPOSALS THAT DO NOT ARRIVE BY THE DESIGNATED DATE & TIME AT THE LOCATION STATED ON PAGE 1 OF THE RFP WILL NOT BE ACCEPTED.


Documents

STATE OF IDAHO - BidNet · Web viewPricing will be evaluated using a cost model that offers the State the best possible value over a three (3) year contract period. The total term