ESRD_Amendment_000001.pdf

(x)

CMS-2016-ESRD-NETWORKS

x x

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT

THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

AGG/KT

CONTRACT SPECIALIST

Kimberly Tatum

ASG - DQC

BALTIMORE MD 21244-1850

7500 SECURITY BLVD., MS: B3-30-03

CMS,OAGM,ASG,DQC

06/25/2015000001

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

06/23/2015

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not, is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See attached.

Period of Performance: 12/01/2015 to 11/30/2016

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

KIMBERLY TATUM

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

NSN 7540-01-152-8070

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

RFP: CMS-2016-ESRD-NETWORKS

Amendment 000001

AMENDMENT 00001 is hereby issued, which incorporates the following:

1. Update Attachment J.2 Style Guide for the ESRD Network Program

2. Update Attachment J.19 Compliance Program Attestation

3. Update Attachment J.22 Business Proposal Form

4. Add Attachment J.22a Business Proposal Form Instructions

5. Update Preproposal Conference Webinar Dial In, as follows:

Meeting Number: 996 201 028 WebEx: 1-877-267-1577

6. Delete Section L.14 in its entirety and replace Section L.14 as follows:

L.14 TECHNICAL PROPOSAL INSTRUCTIONS (Volume I)

The Technical Proposal and attachments shall be divided, tabbed and identified as follows:

Tab 1: Table of Contents (not included in page count) Tab 2: Technical Approach Tab 3: Past Performance and experience Tab 4: Management Plan Tab 5: Staffing Plan and Personnel Tab 6: Appendix (not included in page count)

Tab labels must, at a minimum, contain identification of tab numbers.

The page limitation for the Technical Proposal is 60 single-sided or 30 double-sided pages.

Offerors are cautioned that any pages exceeding the page limit will not be reviewed or evaluated.

The Technical Proposal shall cover the specific plan and approach to all requirements of each task of this project, including the offeror’s proposed technical approach. Proposals shall identify anticipated barriers the offeror feels will be material to the success of the project and strategies likely to be effective in overcoming those barriers. The technical proposal must not contain reference to price/cost; however, resource information such as data concerning labor hours and categories, materials, subcontract(s), etc., must be included in the technical proposal.

CMS has identified specific requirements that the ESRD Networks must address in its written technical proposal. Each ESRD Network shall prepare and submit a document addressing the specific requirements as specified below:

Table 1. AIMS, Domains, and Sub-Domains AIM Domain Sub-Domain

General Requirements

Organizational Structure NC, BOD, MRB, PAC, other committees Network Staff Internal Quality Improvement Performance Improvement Plan

Communication and Meetings

Communications, Data Confidentiality, Reporting to CMS and others, Meetings and Network Collaborations

Emergency Preparedness Emergency and Disaster Responsibilities Data Systems and Security Data Systems, Infrastructure, Hardware/Software and Security

AIM 1: Better Care for the Individual through Patient and Family Centered Care

Patient and Family Engagement

Foster Patient and Family Engagement at the Facility Level and involve Patient Subject Matter Experts in Patient Experience of Care and Healthcare Associated Infection QIAs Involve Patients/Families/Caregivers in CMS Meetings Support the ESRD National Coordinating Center (NCC) Patient and Family Engagement Learning and Action Network (LAN)

Patient Experience of Care

Evaluate and Resolve Grievances Conduct QIA to improve Facility Grievance process Promote Use of In-Center Hemodialysis Consumer Assessment of Healthcare Providers and Systems (ICH CAHPS) and/or Any Similar Survey Identified by CMS Address Issues Identified through Data Analysis Recommend Sanctions

Patient-Appropriate Access to In-Center Dialysis Care

Decrease Involuntary Discharges (IVDs) and Involuntary Transfers (IVTs) Address Patients at Risk for IVD/IVT and Failure to Place Report data on Access to Dialysis Care Monthly

Vascular Access Management

Reduce Catheter Rates for Prevalent Patients Support Facility Vascular Access Reporting

Spread Best Practices Provide Technical Support in the Area of Vascular Access

Patient Safety: Healthcare- Associated Infections (HAIs)

Support National Healthcare Safety Network (NHSN) Establish HAILAN

1) Reduce Rates of Dialysis Events(HAI/bloodstream infection

(BSI)/Sepsis)

2) Increase Hepatitis B (HBV)and Pneumococcal Vaccination Rates

AIM 2: Better Health for the

ESRD

Population

Population Health Innovation Pilot Project

Reduce Identified Disparity through:

Project A: Reducing Hospital Utilization or Project B: Improve Transplant Referrals or Project C: Promote Appropriate Home Dialysis or Project D: Support Improvement in Quality of Life

For Option Year (OY)3 – OY4 all Network will conduct Project A;

additional Network selected project may occur

AIM 3: Reduce Costs of ESRD

Support for ESRD Quality Incentive Program (ESRD

Assist Facilities in Understanding and Complying with ESRD QIP Processes and Requirements

AIM Domain Sub-Domain Care by Improving Care

QIP) and Performance Improvement on ESRD QIP Measures

Conduct Quality Improvement Activities (QIA) to assist Facilities in Improving their Performance on ESRD QIP Measures Assist CMS in Monitoring the Quality of and Access to Dialysis Care Assist Patients and Caregivers in Understanding the ESRD QIP

Support for Facility Data Submission to CROWNWeb, NHSN, and/or Other CMS- Designated Data Collection System(s)

1) Provide support for CROWNWeb (CW) NHSN, other CMS data systems as directed;

2) Conduct Data Quality QIA for NHSN with hospitals and dialysis facilities

3) Provide necessary CW functions as directed by SOW

General Requirements: Indicate how the Network will accomplish the following for each Domain based on the Subdomain activities (see Table 1)

• What efficiencies are you going to incorporate?

• How will you measure and ensure the effectiveness of activities?

• How will collaboration and/or stakeholder engagement be utilized and how will it impact outcomes?

• What challenges are anticipated and what proposed solutions will be implemented?

Aim 1: Better Care for the Individual through Beneficiary and Family Centered Care. Indicate how the Network will accomplish the following for each Domain based on the Subdomain activities (see Table 1)

• How will patient SMEs be integrated into projects and quality improvement activities?

• How will you measure and ensure the effectiveness of interventions? Demonstrate that proposed interventions are:

o evidence-based, efficient and effective.

o appropriate to the ESRD beneficiary population within the participating facilities.

o feasible in the context of the offeror’s Network’s area, considering local practices, geography and other relevant location-specific factors?

• How will collaboration and/or stakeholder engagement be utilized and how will it

Aim 2: Better Health for ESRD Population, including Domains and Sub Domains

• How will patient SMEs be integrated into projects and quality improvement activities?

• How will you measure and ensure the effectiveness of interventions? Demonstrate that proposed interventions are:

o evidence-based, efficient and effective.

o appropriate to the ESRD beneficiary population within the participating facilities.

o feasible in the context of the offeror’s Network’s area, considering local practices, geography and other relevant location-specific factors?

• How will collaboration and/or stakeholder engagement be utilized and how will it impact outcomes?

• What challenges are anticipated and what proposed solutions will be implemented?

• How will the 6 attributes (Innovation, Customer Focus, Rapid Cycle Improvement, Unconditional Teamwork, Boundarilessness and Sustainability) be integrated into projects?

Aim 3: Reduce Cost of ESRD Care by Improving Care, including Domains and Sub Domains

• How will patient SMEs be integrated into projects and quality improvement activities?

• How will you measure and ensure the effectiveness of interventions? Demonstrate that proposed interventions are:

o evidence-based, efficient and effective.

o appropriate to the ESRD beneficiary population within the participating facilities.

o feasible in the context of the offeror’s Network’s area, considering local practices, geography and other relevant location-specific factors?

• How will collaboration and/or stakeholder engagement be utilized and how will it

Description of Technical Proposal Contents

1. Tab 1 shall consist of a “Table of Contents”

2. Tab 2 entitled, “Technical Approach” shall utilize the table below to provide the following for each AIM and Domain:

• What efficiencies are you going to incorporate? (General Requirements and ALL

AIMs)

• How will patient SMEs be integrated into projects and quality improvement activities? (ALL AIMs)

• How will you measure and ensure the effectiveness of interventions? Demonstrate that proposed interventions are:

o evidence-based, efficient and effective.

o appropriate to the ESRD beneficiary population within the participating facilities.

o feasible in the context of the offeror’s Network’s area, considering local practices, geography and other relevant location-specific factors? (ALL AIMs)

• How will collaboration and/or stakeholder engagement be utilized and how will it impact outcomes? (General Requirements and ALL AIMs)

• What challenges are anticipated and what proposed solutions will be implemented?

(General Requirements and ALL AIMs)

• How will the 6 attributes (Innovation, Customer Focus, Rapid Cycle Improvement, Unconditional Teamwork, Boundarilessness and Sustainability) be integrated into projects? (AIM 2 Only)

• Transition:

o Offeror shall describe their transition plan for the period of December 1, 2015 through December 31, 2015 o The Transition Plan shall include a milestone chart detailing the time lines and stages of transition from the effective date of contract performance until the ESRD Network assumes sole responsibility for the ESRD Network Program work. Detailed explanation of the information in the milestone chart must be submitted with your technical proposal. The milestone chart may be included in the Appendix.

• The Offeror must demonstrate a clear understanding of the work to be performed and describe the technical approach that will be utilized to successfully meet the Government’s objectives. The Offeror must submit an explanation of the proposed technical approach in conjunction with the activity to be performed in achieving the project objectives described in the SOW.

3. Tab 3 entitled, Experience and Past Performance shall consist of:

a. Experience

Meeting and Collaborating with Vested Stakeholders:

• The offerer shall describe their experience developing and fostering partnerships to accomplish the services described in the Aims, Domains and Sub Domains in the SOW.

• The offerer must describe how their existing experience supports the proposed approaches used to collaborate with stakeholders to meet the activities outlined in the SOW. The offeror must also demonstrate how the proposed meetings and collaborations with stakeholders will meet the specific major activities proposed.

b. Past Performance

The Offeror shall demonstrate satisfactory performance on current and completed contracts within the last 3 years. For purposes of this section, contracts referenced shall be related to the SOW.

1) Definitions:

Relevant – Relevant past performance information is described in FAR 42.1501, General. For the purposes of this solicitation, ‘relevant’ is also past performance information which is similar in size, scope and complexity to this contract.

Significant Subcontractor – A subcontractor performing major or critical aspects of the requirements relevant to the prospective contract. Significant is defined as those subcontractors who are performing at least 25% of the contract effort.

2) Instructions:

The Offeror and all its significant subcontractor(s) identified in the proposal are required to provide a summary to disclose all of the following for the past performance information with a period of performance end date within the last 3 years of the date of this solicitation:

a) All CMS contracts/task orders greater than the simplified acquisition threshold

b) All relevant contracts/orders entered into with:

o Other Federal Government Agencies, o State Agencies, o Local Governments, and o Commercial Customers

The Offeror’s and proposed significant subcontractor(s) summary shall provide the following information.

• Customer or Agency

• Contract number (if applicable);

• Point of Contact (Contracting Officer or other for Commercial Contract);

• Approximate total contract value;

• Contract period of performance, by base and option year(s);

• Description of contracted services/supplies; and,

• Relevant (Y/N) o If the past performance is relevant, how the disclosed contract’s past performance information is relevant to the subject solicitation.

• Additional Info: If performance was documented as less than satisfactory, the

Offeror shall provide a summary of the identified issues, steps taken to resolve the problem and processes in place to improve future performance.

• Was Offeror prime contractor or subcontractor.

The below table should be used when providing a summary of the past performance information:

Customer (Agency)

Contract

POC Total Contract

Value

Period of Performance

Description of Services

Relevant (Y/N)

Additional Info

CMS utilizes the Contractor Past Performance Retrieval System (CPARS) for recording and storing all CMS Contractor performance evaluations. CMS will access the CPARS for all relevant CMS performance history, if available. However, the Offeror must identify for CMS in its written proposal, which evaluations are being referenced for this solicitation.

Past Performance information will be used for both the responsibility determination and as an evaluation factor against which Offerors’ relative rankings will be compared to assure best value to the Government.

4. Tab 4 entitled, “Management Plan” shall consist of following:

CMS will evaluate the offeror’s description of proposed management plan to the extent that the offeror demonstrates and documents the necessary management structure to successfully perform the contract including:

• Ability to conduct and manage all of the areas described in the Statement of Work

(Section C.)

• The offeror demonstrates and documents the necessary management structure to successfully perform the contract.

• Offeror’s management structure must be consistent with the proposed management plan and with efficient, effective implementation of proposed strategies.

• Offeror must explain in detail the performance management process and system that will be used to continuously monitor progress at meeting desired goals.

5. Tab 5 entitled, “Staffing Plan and Personnel” shall contain the following:

The proposal shall demonstrate:

a. Offeror ability to assemble a team with the appropriate skills to meet the requirements of the SOW;

b. Offeror’s proposed labor mix accurately reflects the offeror’stechnical approach;

and

c. Offeror’s proposal presents and describes its rationale and method for staffing the contract that can be accomplished.

CMS will evaluate the offeror’s description of proposed staff to the extent that the offeror demonstrates and documents the necessary expertise to successfully perform the contract.

Therefore, the offeror shall identify and provide resumes for key personnel and all other essential personnel for each Aim and Domain of the contract. Resumes shall be a maximum of 2 single sided pages each and will not count against the written proposal page limit. Resumes are to be included in the Appendix. Each resume shall contain sufficient detail to clearly demonstrate the candidate is qualified for the position proposed. Each resume shall contain, at a minimum, the following information:

• Name and position.

• Educational background, including academic degrees and the year conferred.

• Technical training, including program year completions.

• Years of applicable experience.

• Citizenship.

• Immediate availability

• History of applicable employment experience and the technical qualifications relevant to the SOW and labor categories.

• History of other experience and professional accomplishments that the offeror may wish to present to demonstrate the qualifications of the proposed candidate.

(Note: Include a Letter of Commitment for each proposed staff who is not currently employed by your organization. Letter of Commitment is not included in the page limit and should be included in the Appendix.)

6. Tab 6 entitled, “Appendix” shall contain the following:

• All items listed within the RFP that should be included in the Appendix, i.e.

resumes, letters of commitment, milestone chart, etc.

• Information Security Attestation. The Offeror shall attest that its Information

Security Plan is in compliance with CMS policies, procedures, and requirements set forth in the Business Partner System Security Manual found at www.cms.hhs.gov/informationsecurity. Specifically, the Offeror shall complete and submit the attestation template provided in J.20.

http://www.cms.hhs.gov/informationsecurity