AB MAC JH MASTER RFP Offeror Questions second set of answers.xlsx

XLSX spreadsheet 48 KB Posted

Attached to
Juristiction H Part A and Part B Medicare Claims Administrator
Solicitation number
RFP-CMS-2011-0005
Issued by

About this file

All remaining answers to potential bidder questions

View the file

Other files

File Type Posted
SF-30 Amendment 000004.pdf PDF
Three Clarifications Amendment 000004.docx DOCX document
Amendment 3 Updated Section J Attachments.zip ZIP file
AB MAC Jurisdiction H RFP 3.22.11 Clean.docx DOCX document
SF-30 Amendment 000003.pdf PDF
SF-30 Amendment 000002.pdf PDF
SF-30 Amendment 000001.pdf PDF
AB MAC JH Offeror Questions First Set Answered.xlsx XLSX spreadsheet
AB MAC Jurisdiction H RFP Final Clean Copy 3.4.11.docx DOCX document
J01 Statement of Work 3.4.11.docx DOCX document
RFP-CMS-2011-0005 —
AB MAC Jurisdiction H RFP Final.docx DOCX document
SF-33 for RFP-CMS-2011-0005.pdf PDF
Show all 13

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Section C

IDSectionQuestionAnswer/Action
2Statement of Work C.5.3.1.1.3 Part B Non-HIGLAS Workload Merge, page 75This section references Jurisdiction F states. Please confirm that all references to Jurisdiction F in the Statement of Work will be amended to reflect Jurisdiction H states.
CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
3Statement of Work C.5.7.2.2.1 IHS Provider Inquiries, page 198Please clarify whether it is a requirement to have a dedicated toll-free number for IHS or whether these calls can come into the normal provider services toll-free line as long as there is a mechanism to route IHS calls directly to Provider Assistance Liaisons.
CMS Response: There is no requirement that there be a dedicated toll-free number for IHS calls, however the offeror must provide a mechanism for IHS provider inquiries to be routed directly to the IHS Provider Assistance Liaisons for handling.

4 22. Section C.5.5 – Provider Enrollment Question/Comment: This section of the SOW states “…For providers who are participating in the Medicare program but do not have an established record in PECOS, the Contractor shall require these providers to complete and submit a complete Medicare enrollment application ( the Internet-based PECOS enrollment application or applicable paper CMS-855, to establish such a record.”

a. Please indicate if this revalidation workload is part of the revalidation workload noted in the workload assumption section of the final RFP.

b. Please provide the volume of providers who don’t have an established PECOS record by CLIN. CMS Response: Providers that began participating in Medicare before the PECOS system was implemented, that do not yet have an established record in PECOS, must file an initial enrollment application. New providers must also file an initial enrollment application in order to receive Medicare billing privileges. Providers file a revalidation enrollment application when required, to enable the MAC to revalidate their credentials. Estimates for both types of provider enrollment workload (initial applications and revalidations) are included in the workload estimates. In PECOS workload reports, there is no differentiation between initial and revalidation enrollments, and CMS does not assume any productivity difference between initial and revalidation enrollments. CMS has been tracking the number of Medicare providers enrolled in PECOS vs. the overall number of providers enrolled within local contractor systems. The discrepancy is trending down and should be minimal by the end of 2011. These numbers are also incorporated into the overall total initial enrollment estimates provided with the workload assumptions in Section L.10.e.

523. Section C.5.10.1.2 – Document Imaging and Indexing
Question/Comment:

a. Is it CMS’ intent to index images only for those Appeals that are being requested by the QIC? Requiring this indexing of all appeals may not have a positive return on investment.

b. Please confirm the date required in the index is the scan date and not the Julian date.

CMS Response: CMS requires A/B MAC Contractors to scan and index all redeterminations in accordance with the requirements listed in C.5.10.1.2. This indexing and scanning requirement is not limited to those redeterminations elevated to the QIC level of appeals. CMS also confirms that one of the dates required in the index is the Julian date.
624. Section C.7.2 Indian Health ServicesQuestion/Comment: C.7.2 Indian Health Services are included in this jurisdiction. Is there reimbursement and audit work related to the Indian Health Services? Have the provider count and workload been included in the RFP?

CMS Response: For the Indian Health Services workload, the incumbent Jurisdiction 4 A/B MAC services approximately 59 Part A providers (including 43 hospitals and 11 federally-qualified health care centers) and 8700 Part B providers. The IHS facility/provider claims workloads for February 2010 through January 2011 were: Part A claims- 730,920 and Part B claims- 557,190 The IHS facilities do file cost reports and are subject to Medicare cost reporting review and reimbursement requirements. The applicable volume of IHS claims, audit, and other workloads are reported in the current J4 workload and are included within the workload estimates provided in Section L.10.e of the solicitation.

725. Section C.7.4 Rural Community Hospital DemonstrationQuestion/Comment: This SOW has a requirement for on-site field audits. Are these audits included in the RFP workload?
CMS Response: CMS confirms that both on-site/"field" audits and "in house" audits are both considered "audits," and both types of audits are embedded in the audit workload estimates provided in Section L.10.e of this solicitation. CMS has revised the audit workload estimates somewhat. Offerors shall use the revised audit workloads presented in Section L.10.e of the solicitation (Amendment 0003). While CMS has presented only a total audit workload value in the workload tables, CMS estimates that approximately 35% of audits performed should be on-site/"field" audits and approximately 65% of audits performed should be "in house" audits.
8C.5.3.1.1 Local Hardware and Software RequirementsQuestion/Comment

This section of the JH SOW states “The Contractor shall provide hardware and software identified in Attachment J-22, Contractor Furnished Property (CFP)……”, This appears to be an incorrect Attachment reference. Please clarify that the Contractor Furnished Property reference should be Attachment J-05.

CMS Response: The correct reference for Contractor Furnished Property is J-24. The SOW has been updated to reflect this correction. (Amendment 0003)
9C.5.3.1.1.3 Part B Non-HIGLAS Workload MergeQuestion/Comment

The JH SOW states, “The Contractor shall provide project management, testing, and other services to successfully merge the Idaho Part B Customer Information Control System (CICS) region with the combined Alaska, Oregon, and Washington Part B CICS region at the CDS EDC. Please clarify that this section of the JH SOW should state that the Arkansas, Louisiana, and Mississippi Part B CICS regions will be merged into one CICS Region at the CDS EDC.

CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
10C.5.3.1.1.3.3 Mappings, Duplicate PINs, and TestingQuestion/Comment

The JH SOW states that the Contractor shall perform work on Alaska, Oregon, and Washington mappings, duplicate provider identification numbers and testing. Please clarify that this section of the SOW should state the Contractor shall perform work on Arkansas, Louisiana, and Mississippi mappings, duplicate provider identification numbers, and testing.

CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
11C.5.3.2.1 Telecommunications for Electronic Data InterchangeQuestion/Comment

This JH SOW requirement states the Contractor shall interact with the Individual Authorized Access to the CMS computer services (IACs) to ensure the EDI submitter/receiver is an authorized EDI submitter for each transaction. The use of IACs to validate each EDI transaction could add significant overhead to the EDI framework. If the offeror is an existing A/B MAC, could they use their existing translator, which has a built-in trading partner validation, instead of adding the IAC’s loop?

CMS Response: CMS confirms that the A/B MAC contractors may use their existing translator authenticator.
12C.5.3.2.6 CMS Certification/Recertification Testing ProgramQuestion/Comment

This JH SOW section states that the Initial Certification of the MAC Front End Certification must be completed prior to exchanging transactions (ASC X12 or other standard transaction) with the MAC’s trading partner community. Should the contractor assume that the JOA and certification must be completed prior to any transaction being exchanged, in both the test and production environments?

CMS Response: CMS confirms that the Initial Certification of the MAC Front End Certification applies to both test and production environments.

13 C.5.4.1.11 Contractor Medical Director (CMD) Question/Comment C.5.4.1.11 states that the offeror must employ a “minimum of one (1) FTE CMD for each line of Medicare business per contract” and “one CMD will be in an executive management role”. We assume that CMS is looking for offerors to propose the “one (1) FTE CMD” as the key personnel. Please confirm.

CMS Response: CMS clarifies that according to SOW C.5.4.1.11 the contractor shall employ a minimum of 2.0 full-time-equivalent (FTE) Contractor Medical Directors (CMDs) for this A/B MAC contract. At least one of the CMDs assigned to the contract will serve in an independent executive leadership role to provide an overall leadership role. The executive CMD shall serve as key personnel under this Statement of Work.

Offerors should review amended SOW C.5.4.1.11 in its entirety (Amendment 0003).

14 7. C.5.4.8.1 Review and Comment on Draft Change Requests Question/Comment C.5.4.8.1 states “No response is required if the Contractor concurs with the Change Request (CR).” Please confirm this requirement as it is a change in CMS’ current A/B MAC requirement covered in JSM/TDL-08436, 08-06-1850.

CMS Response: Contractors are required to comment on all CRs. If contractors do not have any comments, they shall respond in eChimp accordingly.
158. C.5.10.1.2 Document Imaging and IndexingQuestion/Comment

C.5.10.1.2 states, “All redetermination requests be scanned, including documentation and incoming correspondence supplied in support of the request. Document imaging shall include scanning a claim in its entirety when it reaches the MAC, performing Quality Assurance (QA) on scanned images, indexing the scanned images, and using these scanned images to make a decision on the claim. At a minimum, all images shall be indexed by date scanned, MAC contract number, claim number and beneficiary HICN. The Contractor shall electronically image and index all redetermination correspondence upon receipt in the corporate mailroom.” Please clarify that using a single, reliable index to accomplish retrieval meets the requirements of C.5.10.1.2, versus using multiple indexing references (e.g., HIC, claim number).

CMS Response: Using a single index to accomplish retrieval does not meet the requirements of C.5.10.1.2. The requirements listed in C.5.10.1.2 allow retrieval of documents by many different criteria and are not limited to retrieval of a single case file.

16 9. C.5.10.1.3.1 Acknowledgement of Redetermination Requests Question/Comment This requirement states the Contractor is required to acknowledge the request for redetermination within 14 calendar days of receipt of the request in the Contractor’s mailroom. At a minimum, the acknowledgement shall identify the date the request was received, the items/services/claims at issue and verbiage indicating the appeal shall be completed within 60 days of receipt. Requiring the inclusion of the item/services/claims at issue is currently not required in the acknowledgement of redetermination requests. Requiring this information for JH will be labor intensive because this information will be difficult to identify without doing significant manual research, thereby taking resources away from processing the redetermination. Providers often submit multiple claims in large volumes as a single redetermination request. Would this requirement mean that all claims included in the redetermination request need to be acknowledged? Would CMS consider requiring only the Health Insurance Claim Number (HIC) for this requirement?

CMS Response: Similar to instructions contained in IOM 100-6, Chapter 6, Section 460.1, related to counting cases, CMS expects an acknowledgement letter to be sent for each redetermination request. CMS, however, is agreeable to the approach suggested in the Offeror's question regarding use of the Health Insurance Claim (HIC) Number as a means of consolidating redetermination acknowledgements, as long as the acknowledgement letters reference every claim involved in each request for redetermination.

17 10. C.5.11.3.2.5.2 Audit Plan Question/Comment This JH SOW requirement states that “The audit plan shall include any cost report in which the Contractor will start audit during the year”. Should this statement more appropriately be worded “the audit plan shall include any cost report in which the Contractor will start and complete audit during the year”?

CMS Response: CMS confirms that the audit plan should include those cost reports started during the year. There may be cases when a limited number of cost report audits have been started but not completed by the end of the year. Historically, the number of open cost report audits in the Jurisdiction H workload at the end of each federal fiscal year is very low (fewer than 10 open audits for the past several years).

18 11. C.5.11.4.3 Description Question/Comment This SOW section states that the RAC will send out the first demand letter and all other letters pertaining to the RAC overpayment will be sent by the Medicare Contractor. Please confirm for RAC overpayments that the only follow-up demand is the Intent to Refer Letter (IRL), and that there is no requirement for the MAC to send out a second demand letter prior to the IRL.

CMS Response: Second demand letters are not required to be sent by the MAC for RAC overpayments, except in the following situation: if the providers, physicians, or other suppliers appeal and receive a partially favorable decision that results in a revised overpayment amount, the contractor (MAC or Legacy) shall be required to send a 2nd demand letter with the revised amount. (See amended SOW)
1912. C.5.15.1 Review of Provider Billing RecordsQuestion/Comment

Are “billing records” synonymous with “claims?” Please clarify how this activity differs from Medical Review data analysis. If the same, should the Contractor notify CMS regarding each probe review that is conducted, (e.g., the provider has “aberrant billing”)? If different, please clarify what is meant by aberrant billing in this scenario. Clarify if this same definition applies in SOW requirement C.5.15.2 (Review of Comprehensive Outpatient Rehabilitation Facility Billing Records).

CMS Response: Billing Records are not synonymous with “claims.” Billing records are defined as “the information that is passed between the provider and the medical review staff as evidence to ensure that billings are in line with the services provided.”
2013. C.6.1 Successful Collaboration with Entities Requiring Joint Operating AgreementsQuestion/Comment

Section C.6.1 of the SOW requires the MAC to execute a JOA with various business partners, including the EDC and MSPRC. Historically, we have found that the EDCs and MSPRC have not had similar requirements in their contracts with CMS to have JOAs with the MACs. Does CMS intend to require these business partners to have JOAs with the MACs?

CMS Response: CMS is not adding requirements to the MSPRC contract at this time. For proposal purposes, Offerors should assume that the MSPRC will enter into a JOA with the MAC.
2114. C.6.1.2.1 Supply of Appeals Case FilesQuestion/Comment

This SOW section states: “The Contractor shall supply to the QIC all appeals case file information, within five (5) calendar days of request.” The IOM states in Pub.4, Chapter 29, Section 320.4 that “Contractors shall send/transmit the case file within seven (7) calendar days of the date of the QIC's request”. Please clarify the timeframe requirement for supplying case files to the QIC.

CMS Response: For A/B MAC Jurisdiction H, the MAC is required to supply case files to the QIC within five calendar days of the date of the QIC's request.
2215. C.7.9.1 Frontier Extended Stay Clinic Demonstration: Medical ReviewQuestion/Comment

Please provide an estimated workload for this activity.

CMS Response: CMS estimates the combined Medicare claims medical review for the two tribal clinics in Alaska to be 100 annually for each of OYs 1-4. This claims medical review workload is in the overall claims estimates.
2316. C.7.10 Pay for Performance Check-WritingQuestion/Comment

Will the incentive and bonus payments for Medicare demonstration projects be made via EFT or check, or both?

CMS Response: The incentive and bonus payments for this demonstration will be made via EFT.
24SOW C.5.1 Workload Implementation Requirements Table Number XXXX6.1It is presumed the reference to Alaska is intended to be Arkansas. Is this a correct presumption?CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
25SOW C.5.1 Workload Implementation Requirements TableIt is believed that the table of business requirements (pgs. 29 through 64) should refer to Pinnacle & Cahaba, rather than NAS and CGS. Please confirmCMS Response: CMS confirms that all references to the legacy contractors for Jurisdiction F (JF), i.e. NAS and CGS, in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH legacy contractors, Pinnacle and Cahaba. See the Amended Statement of Work -- Amendment 0003.
26SOW C.5.1 Workload Implementation Requirements Table Number XXXX6.1It is presumed the reference to Alaska is intended to be Arkansas. Is this a correct presumption?CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
27C.5.1.8 Consolidation of Part A and Part B EditsThis section (page 66) discusses shared system edits and mentions LCDs and FISS Reason Codes as well as other FISS edits. Edits the MAC has put in place for LCDs in FISS are classified as FISS Reason Codes. Can you provide examples of the FISS Reason Codes (and their definitions/specifications) being referred to in this section?CMS Response: FISS Reason Codes are the hard-coded edits which number approximately 100 codes and are based upon NCDs. An example of a FISS Reason Code is: DIAGNOSIS 4275: CARDIAC ARREST is hardcoded for the following: Reason Code 31157: Modifier, Q0 must be present if HCPC codes are equal to G0297, G0300, or 33240, the charges for those codes are greater than zero, and Diagnosis Code 427.1,427.41,427.42,427.5, 427., 996.04, or V53.32 are not present.
28C.5.1.8.2 Consolidation of Local Coverage DeterminationsThis section (page 67) includes a requirement that the narratives written for each consolidated LCD be “sent” to providers along with the final policy. Is posting this information on the MAC’s LCD page sufficient? If not, is inclusion of this information in a Listserv Notice sufficient? If actually mailing the documents to each “provider” (physician and facility etc.) is the requirement, can it be presumed that the associated cost will be a funded implementation expense?CMS Response: CMS confirms that MACs may satisfy Section C.5.1.8.2 of the SOW (consolidated LCDs notice requirement to providers) by posting the consolidated LCDs written narrative and final policy on the MAC’s LCD web page as well as including this information on a Listserv Notice.
29SOW C.5.3.1.1.3 Part B Non-HIGLAS Workload MergeIt is presumed that the reference to Alaska, Idaho, Oregon and Washington is intended to be Arkansas, Louisiana and Mississippi. Is this a correct presumption?CMS Response: CMS confirms that all references to Jurisdiction F (JF) states in the Jurisdiction H (JH) Statement of Work are amended to reflect the JH states. See the Amended Statement of Work -- Amendment 0003.
30SOW C.5.3.1.1.3.3 Mappings, Duplicate PINs, and TestingIt is presumed that the reference to Alaska, Idaho, Oregon and Washington is intended to be Arkansas, Louisiana and Mississippi. Is this a correct presumption?CMS Response: The reference to Alaska, Idaho, Oregon, and Washington has been corrected. The Statement of Work has been updated and can be found in Amendment # 0003 of this solicitation.
31C.5.4.1.11 Contractor Medical DirectorThis section (page 91) has a requirement to have “structured review and analysis of medical evidence” for inclusion in each LCD. Do you have examples or a template of what is expected of this new requirement?CMS Response: CMS does not have an example/template for this requirement at this time. Offerors may propose/describe an approach to this issue in their technical proposal.
32SOW Section C.5.4.1.11 Contractor Medical DirectorThis section of the SOW indicates that the Contractor must employ a minimum of 1 FTE CMD for "each line of business per contract". What does CMS mean by "line of business" in this context? Does this refer to Parts A and B as separate lines of business? Or does this refer to the single A/B MAC as a single line of business?CMS Response: CMS confirms that according to SOW C.5.4.1.11 the contractor shall employ a minimum of 2.0 full-time-equivalent (FTE) Contractor Medical Directors (CMDs) for this A/B MAC contract. At least one of the CMDs assigned to the contract will serve in an independent executive leadership role to provide an overall leadership role. The executive CMD shall serve as key personnel under this Statement of Work.

Offerors should review amended SOW C.5.4.1.11 in its entirety (Amendment 0003).

33SOW Section C.5.4.6 Congressional InquiriesIs the new Congressional SOW code C.5.4.6 only intended for congressional inquiries initiated by beneficiaries? Will the provider-initiated Congressional inquiries workload remain under the Provider Contact Center C.5.7.2 SOW responsibility? Does the RFP workload count for A and B Congressional include both provider and beneficiary congressional inquiries?CMS Response: SOW section C.5.4.6 is not under the Provider Customer Service Program. MACs should forward BCC-related Congressional inquiries to the BCC. All other Congressional inquiries should be handled by the MACs in accordance with C.5.7.2., which references IOM 100-9, Chapter 6. Sections 30.3.9 and 60.3.2.4 in Chapter 6 detail how contractors are to handle Congressional inquiries. (All provider inquiries are handled by the MAC).
34SOW Section C.5.5.1 Process Initial Enrollment and Revalidation ApplicationsIt is our understanding that C.5.5.1 Standards (Attachment J-01 C: JH A/B MAC STATEMENT OF WORK STANDARDS) 1 - 11 pertain to paper applications only. However, the JH SOW standards do not specify "paper only." Please confirm.CMS Response: CMS confirms that Standards 1-11 pertain to paper applications only. CMS has added Standards 12 and 13 into the SOW Standards Matrix to clarify the processing timeliness and accuracy requirements for initial web-based applications. See amended Attachment J-01 C (SOW Standards Matrix), Amendment 0003 to this solicitation.
35SOW Section C.5.5.2 Process Changes, Updates, Reassignments or CorrectionsDoes standard C.5.5.2 (Attachment J-01 C: JH A/B MAC STATEMENT OF WORK STANDARDS) #2 pertain to all Web applications (including Initials)? This standard doesn't reference "initials," and there is no other Web standard noted.CMS Response: The processing timeliness and accuracy requirements for initial web-based applications are incorporated under C.5.5.1, standards 12 and 13. See amended Attachment J-01 C (SOW Standards Matrix), Amendment 0003 to this solicitation.
36SOW Section C.5.11.2 Banking RelationsC.5.11.2 includes extensive information regarding the August 2010 banking implementation. Should this information be removed since the implementation has been completed?CMS Response: CMS confirms that section C.5.11.2 of the SOW has been revised to remove this language. See Amendment 0003 to this solicitation.
37SOW Section C.5.11.2.3.2 Estimated Allowance for Uncollectable AccountsC.5.11.2.3.2 deliverables states the Allowance matrix is due monthly and 4 days after quarter end. IOM 100-06 Chapter 6 states that an allowance matrix is to be submitted semiannually on April 21st and October 21st. Please clarify if this is a change in requirements.CMS Response: HIGLAS contractors are required to submit an Allowance Matrix monthly. This deliverable is part of the Monthly HIGLAS Certification package (this requirement issued to contractors post HIGLAS cutover). Non-HIGLAS contractors (CAFM) are instructed/required to submit an Allowance Matrix in accordance to the IOM Pub. 100-6, Chapter 5, Section 400.14.
38SOW Section C.5.11.4 Non-Medicare Secondary Payer OverpaymentC.5.11.4 states that 2nd demand letters are to be sent by the MAC. This contradicts current direction from CMS. 2nd demand letters are not required to be sent by the MAC for RAC Overpayments. Please clarify if this is a change in requirements.CMS Response: CMS confirms that 2nd demand letters are not required to be sent by the MAC for RAC overpayments, except in the following situation: if the providers, physicians, or other suppliers appeal and receive a partially favorable decision that results in a revised overpayment amount, the contractor (MAC or Legacy) shall be required to send a 2nd demand letter with the revised amount. (The SOW has been amended; see Amendment 0003 of this solicitation.)
39SOW Section C.5.11.9 Financial Reporting and AccountingC.5.11.9 states: CFO reporting certification will remain in effect for HIGLAS generated financial submissions. To accomplish this, a tailored certification statement must be signed and faxed to the Director, Division of Financial Reporting and Policy (fax 410-786-3027). Is it acceptable to submit the HIGLAS certification electronically using PDF files e-mailed to the Director, Division of Financial Reporting and Policy?CMS Response: CMS confirms that the HIGLAS certification can be submitted electronically using PDF files emailed to Lataysheia Lance at lataysheia.lance@cms.hhs.gov, with a cc to kenneth.wilkins@cms.hhs.gov.
40SOW Section C.5.11.9 Financial Reporting and AccountingC.5.11.9 deliverables does not include the HIGLAS reports which are due monthly on the 5th business day. Please clarify if this is a change in requirements.CMS Response: CMS confirms that this is not a change in requirements. The HIGLAS reports referenced in the question are not treated as a formal deliverable, however, these reports are still required.
41SOW Section C.5.12.1 Development of Medical Review StrategyThe SOW states "The Contractor shall consider ... reports, findings, and recommendations related to the Medicare DMEPOS benefit when developing and updating its MR strategy.” Does this DME terminology apply to the MAC?CMS Response: The correct statement is as follows: "the Contractor shall consider reports, findings, and recommendations related to the Medicare Part A and Medicare part B benefits when developing and updating its MR strategy." See the amended Section C.5.12.1 of the SOW (Amendment 0003 to this solicitation).
42SOW Section C.5.24 Medicare Contractor Provider Satisfaction Survey (MCPSS)C.5.24, MCPSS, is currently only reflected on the cost templates under Part A, SLIN AA. Should this SOW item also be included in Part B, SLIN AC?CMS Response: Yes, C.5.24 applies to both Part A SLIN AA and Part B SLIN AC. For proposal purposes, Offerors shall adhere to the instructions under L.15 of this solicitation when submitting its CLIN templates. Specifically, this section states:

All CLINs (CLINs 0001-0008) are required to be submitted at the CLIN level only. Any information submitted beyond that required herein or in attachment J-9 will not be evaluated as part of this procurement.

For proposal purposes, Offerors shall also adhere to the instructions provided in Attachment J-07 of this solicitation which state:

The offeror shall provide a crosswalk to the CLIN templates for the FTEs identified for each workload category using Column I. This crosswalk shall identify each labor category by SLIN and by the lowest WBS level. Each WBS element shall be displayed using a separate row.

Offerors should document any assumptions concerning labor or other expense categories in their submission of the Basis of Estimate forms (Attachment J-07) for the BY and OYs 1-4 in accordance with section L.15 of the solicitation and the instructions provided under Attachment J-07.

43SOW C.7.5 Veterans Affairs Medicare Equivalent Remittance Advice ProjectThe C.7 Jurisdiction-Specific Requirements are all shown on the cost templates as lower level SOW requirements except for C.7.5 Veteran Affairs Equivalent Remittance Advice Project. Should CMS add C.7.5 to the C.7 cost template or add SLINs to collect this cost?CMS Response: CMS confirms that C.7.5 is reported as a separate SLIN for each operational year. (SLIN 0003AE and SLIN 0003AF).
44SOW C.7.10 Pay for Performance Check-WritingC.7.10 does not list the specific demonstration projects to be included in the JH workload, rather it references a CMS website, www.cms.hhs.gov/DemoProjects, where numerous demonstration projects are listed. Are all demonstration projects listed on the website to be included in the proposal?CMS Response: CMS confirms that the successful offeror in JH will not be responsible for all demonstrations listed on the CMS website. The successful offeror will be responsible for all demonstrations listed in SOW section C.1.4.3.2, Jurisdiction Specific Requirements.

&D A/B MAC Jurisdiction H

RFP-CMS-2011-0005 &9&A &9&P

http://www.cms.hhs.gov/DemoProjects Section J

IDSectionQuestionAnswer/Action
51Section J List of Attachments, page 64, J-07 Basis of EstimateIn Column J of the Instructions section of Attachment J-07, Basis of Estimate, CMS indicates: “In addition, if the basis of the Offeror's proposed productivity is its history, which includes an implemented innovation and/or process improvement referenced in another section of its Proposal, the Offeror shall also crosswalk this to the page, tab, and Volume of its Proposal that contains the applicable narrative to support this implemented innovation and/or process improvement.” Please clarify CMS’ expectation for completing this instruction.
CMS Response: If the Offeror has proposed innovations and/or process improvements that are part of its current operations, the Offeror shall provide evidence that the proposed innovation and/or process improvement resulted in the stated benefit to the Government. The Offeror shall identify the date it implemented the innovation and/or process improvement and the result of that implementation to its operations. The Offeror shall disclose the source of this result, which may include reporting systems and customer satisfaction surveys.

The Attachment J-07 instruction for Column J requires the Offeror to crosswalk the productivity and/or level of effort proposed for each labor category to an Offeror’s proposed innovation in its Technical Proposal. For the particular question referenced above, if the Offeror has referenced historic productivity that is the direct result of an innovation and/or process improvement currently in place within its operations and referenced in its Technical Proposal, the Offeror shall provide a crosswalk in Column J to the detailed section in its Technical Proposal as identified in the instruction. Offerors are reminded that an innovation may be part of the Offeror’s current operations, a new innovation not yet implemented that is proposed to be put in place on this contract, or a new innovation not yet implemented that is proposed to be put in place between the date of the Offeror’s proposal submission date and the contract award date.

52 17. Section C.6.1 Initial Joint Operating Agreement Deliverable Question/Comment The list of parties with whom the JH MAC is required to initiate a JOA is not consistent with the list of required JOAs in Section C.6.1 of Attachment J-01, Successful Collaboration with Entities Requiring Joint Operating Agreements. Attachment J-02, Deliverables Schedule, lists the following parties: Program Safeguard Contractors (PSCs) with Benefit Integrity (BI) task orders; other specialty PSCs, if applicable; Qualified Independent Contractors (QICs); Administrative Qualified Independent Contractors (AdQICs); Quality Improvement Organizations (QIOs); Recovery Audit Contractors (RACs); Beneficiary Contact Center (BCC); and Enterprise Data Center (EDC). Attachment J-01, Section C.6.1., lists the following parties: AdQIC, Appeals Support Contractor, BCC, EDC, PSC/ZPIC, QIC, QIO, RAC, and MSPRC. Please clarify which Attachment represents the appropriate reference for the required initial JOAs for the JH MAC.

CMS Response: CMS confirms Section C.6.1 of Attachment J-01 contains a comprehensive list of parties subject to a JOA with the MAC. Attachment J-02 has been updated.
5318. Section C.6.1 Updated Joint Operating Agreement DeliverableQuestion/Comment

The list of parties with whom the JH MAC is required to update JOAs is not consistent with the list of required JOAs in Section C.6.1 of Attachment J-01, Successful Collaboration with Entities Requiring Joint Operating Agreements. Attachment J-02, Deliverables Schedule, lists the following parties: PSCs with BI task orders; other specialty PSCs, if applicable; QICs; AdQICs; QIOs; RACs; and BCC. Attachment J-01, Section C.6.1, lists the following parties: AdQIC, Appeals Support Contractor, BCC, EDC, PSC/ZPIC, QIC, QIO, RAC, and MSPRC. Please clarify which attachment represents the appropriate reference for the required updated JOAs for the JH MAC.

CMS Response: CMS confirms Section C.6.1 of Attachment J-01 contains a comprehensive list of parties subject to a JOA with the MAC. Attachment J-02 has been updated.

&D A/B MAC Jurisdiction H

RFP-CMS-2011-0005 &9&A &9&P

Section L

IDSectionQuestionAnswer/Action
6410. Section L.9.m Proposal Instructions – Documentation, page 85Please identify all systems, including any contractor-developed systems, used for the Indian Health Service (IHS) program and whether they are or will be available to all contractors.
CMS Response: The same shared systems (FISS, MCS, CWF, PECOS, etc.) used by A/B MACs for processing non-IHS claims are used for IHS claims, provider enrollment applications, inquiries handling, and all claims processing-related transactions. There are no separate contractor-developed IHS processing systems in current use.
6511. Section L.10.e Proposal Assumptions - Workloads, page 88This section does not provide IHS workloads. Please clarify the workloads and provider counts for the IHS and whether CMS included them with the other workloads.
CMS Response: For the Indian Health Services workload, the incumbent Jurisdiction 4 A/B MAC services approximately 59 Part A providers (including 43 hospitals and 11 federally-qualified health care centers) and 8700 Part B providers. The IHS facility/provider claims workloads for February 2010 through January 2011 were: Part A claims- 730,920 and Part B claims- 557,190

The IHS facilities do file cost reports and are subject to Medicare cost reporting review and reimbursement requirements. The applicable volume of IHS claims, audit, and other workloads are reported in the current Jurisdiction 4 workload and are embedded within the workload estimates provided in Section L.10.e of the solicitation.

66 12. Section L.10.e Proposal Assumptions - Workloads, page 90-91 Does CMS contemplate an expected level of Provider Education and Outreach support for IHS providers other than that provided to the rest of the provider customer base?

CMS Response: In its provider inquiries tracking systems, CMS does not separately track the complexity, duration, and productivity of IHS provider inquiries relative to those received from other non-IHS providers of similar Part A and Part B provider types. Aside from the requirement for Provider Assistance Liaisons called for in the SOW, CMS does not have any unique provider outreach and education requirements for servicing this provider community. Offerors shall document their technical approach to provider outreach and education, and their overall Provider Customer Service Program, in keeping with the Technical Proposal submission requirements; this may include elaborating on the Offeror's approach to this community. Offerors shall document any cost estimation assumptions relating to provider outreach and education to this community in their Business Proposal, in keeping with the completion requirements for the Basis of Estimate (Attachment J-07).
6713. Section L.10.e Proposal Assumptions - Provider Reimbursement and Audit Workloads, page 91For the "Audits" category, please clarify what the two sets of workload numbers (140 and 307) for Option Year 1 represent. All other workload numbers for Provider Reimbursement and Audit only include one workload number.
CMS Response: Within the Jurisdiction H workload assumptions provided in Section L of this solicitation, CMS has revised many of the workload estimates within the audit and reimbursement category, including the estimate for number of audits for the base year and the option years. Only one audit volume figure is provided for each operating period. Of the total audits to be performed, CMS anticipates that approximately 35% will be "field audits" and 65% will be "in house" audits. Offerors shall document their specific approach to estimating audit-related costs in their Basis of Estimate forms (Attachment J-07), in keeping with the Business Proposal submission requirements.
6814. Section L.10.e Proposal Assumptions - Provider Reimbursement and Audit Workloads, page 91Please provide the desk review workloads broken down between full desk reviews and limited desk reviews.
CMS Response: CMS has provided specific estimates for the number of "limited desk reviews" and "full desk reviews" by revising the audit and reimbursement workload estimates in Section L of the solicitation. The estimates for both types of workload (limited desk reviews and full desk reviews) have been substantially revised upwards. Historically, approximately 13% of desk reviews performed in this Jurisdiction have been full desk reviews and 87% of the desk reviews performed have been limited desk reviews.
6915. Section L.10.e Proposal Assumptions - Provider Reimbursement and Audit Workloads, page 91CMS' workload for Cost Report Settlements for Option Year 1 is 216. The total number of hospitals and other facilities reflects 6,074 in Option Year 1. The workload number for cost report settlements (216) appears to be significantly understated compared to the total number of hospitals and other facilities (6,074). Almost all hospitals and other facilities file cost reports, which will need a Cost Report Settlement as described in the SOW C .11.3.2.6 Final Settlement Section. Please clarify the workload for cost report settlements.
CMS Response: CMS confirms that many of the audit and reimbursement workload values, including those related to cost report tentative and final settlements, were misstated. For proposal purposes, Offerors shall use the revised audit and reimbursement workload values presented in a revised Section L.10.e. of the solicitation. See Amendment 0003.
7016. Section L.10.e Proposal Assumptions - Provider Reimbursement and Audit Workloads, page 91CMS' workload for Desk Reviews for Option Year 1 is 704. The total number of hospitals and other facilities reflects 6,074 in Option Year 1. The workload number for cost report Desk Reviews (704) appears to be significantly understated compared to the total number of hospitals and other facilities (6,074). The Contractor is responsible for performing desk reviews of institutional providers filing cost reports (except Hospice and no/low Medicare utilization cost reports) as described in the SOW C .11.3.2.3 Desk Reviews Section. Please clarify the desk review workload.
CMS Response: CMS confirms that many of the audit and reimbursement workload values, including those related to desk review of cost reports, were misstated. For proposal purposes, Offerors shall use the revised audit and reimbursement workload values presented in a revised Section L. The revised workload tables provide CMS's estimate of the number of limited desk reviews and full desk reviews to be performed, for each operating period of the Jurisdiction H MAC contract. See Amendment 0003.
7117. Section L.10.e Proposal Assumptions - Workloads, page 93What are the IHS telephone and written inquiry workloads?

CMS Response: The IHS telephone and written workload for the 12 month period of February 2010 thru January 2011 were:

Part A inquiries = 1,654 Part B inquiries = 2,681

7218. Section L.10.e Proposal Assumptions - Workloads, page 93Please describe and compare the level of complexity for Indian Health Services provider or patient inquiries relative to other call center workload.
CMS Response: CMS confirms that a few IHS inquiries may represent a higher level of complexity than non-IHS inquiries due to unique billing requirements. Otherwise, IHS inquiries are similar in complexity level to non-IHS inquiries. In its provider inquiries tracking systems, CMS does not separately identify or track the complexity, duration, and productivity of IHS provider inquiries relative to those received from other non-IHS providers of similar Part A and Part B provider types. Aside from the requirement for Provider Assistance Liaisons and other requirements expressly stated in this SOW, CMS does not have any unique provider inquiries or provider outreach and education requirements for servicing this provider community. Offerors shall document their technical approach to provider inquiries as well as provider outreach and education, and their overall Provider Customer Service Program, in keeping with the Technical Proposal submission requirements, which may include elaborating on the Offeror's approach to this community. Offerors shall document any cost estimation assumptions relating to provider inquiries and provider outreach and education to this community in their Business Proposal, in keeping with the completion requirements for the Basis of Estimate (Attachment J-07).
7319. Section L.10 Proposal Assumptions – Workloads, page 93In this section, CMS provides Provider Telephone and Written Inquiry workloads. Please clarify and confirm the definition of these workloads includes both IVR and portal workloads.
CMS Response: The provider telephone workload assumptions include calls handled by the IVR and customer service representatives. Internet portal transactions are not included. Written inquiry workload is written correspondence handled by the MAC and does not include portal workloads. Providers in this jurisdiction are not currently serviced by portal technology.
7420. Section L.10.p Proposal Assumptions, Postage and Printing Costs, page 103Please clarify whether the 3% escalation should be applied only to postage costs or to postage and materials.
CMS Response: For this particular assumption, the 3% escalation factor should be applied only to postage costs.
7521. Section L.13 Tab C.2: Innovations, page 107 thru 108 & Section L.15.b Tab F.1: Business Proposal Assumptions, page 116Please clarify whether the Offerors should only include the cost of implementing innovations in Tab F.1 (Business Proposal) or whether the Offerors should also include the expected cost savings of innovations in Tab F.1 (Business Proposal)?
CMS Response: At a minimum, the Offeror shall identify any associated costs for an innovation in Tab F.1 of its Business Proposal. Further, at a minimum, any expected cost savings for an innovation shall be stated clearly in the Offerors Technical Proposal, Tab C.2.2. Where applicable, the Offeror shall also identify under column J of its Attachment J-07 submission proposed innovations highlighted in the Technical Proposal that have resulted in the proposed productivity for a labor category in accordance with the instructions provided in the Attachment J-07 template.
792. Section L.10 Proposal assumptionsQuestion/Comment: f.1.i states “Assuming a 12-month base year volume of 500 draft CRs issued for review and comment, for base year estimations Offerors shall use a 7 month total (292 draft CRs). For all Option Years estimations, please bid annual increases of five percent (5%) on Draft CRs per the following table.”, however, SOW Section C.5.4.8 Participation in Change Management Process states “The contractor shall provide a level of effort up to 46,200 hours per contract year … There will be an estimated ten (10) percent increase in hours for each contract year.” Please clarify the percentage increase the offeror should propose.
CMS Response: The offeror should propose to an estimated five (5) percent increase in hours for each contract year, instead of ten (10) percent. SOW Section C.5.4.8 Participation in the Change Management Process will correctly state, "The contractor shall provide a level of effort up to 46,200 hours per contract year … There will be an estimated five (5) percent increase in hours for each contract year.” See revised SOW, Amendment 0003.
803. Section L.10 Proposal assumptionsQuestion/Comment: AR, LA and MS workload (old J7 workload) has an implementation and base period but CO, NM, OK and TX (old J4 workload) just has an implementation period and no base period. Operations per page 87 start 11/1/11 and 7/23/12 but per page 98 the old J4 workload implementation period ends 8/4/12. Can CMS please clarify? Will there be a base period for the old J4 workload?
CMS Response: The Jurisdiction 4 workload does not become incorporated into the Jurisdiction H MAC contract until after the 1st option year of the Jurisdiction H contract (OY1) begins on June 1, 2012. CMS projects that the operational cutovers of the Jurisdiction 4 workload will occur during mid-June 2012 and mid-July 2012 in order to accommodate the CMS HIGLAS program requirement of the cutover occurring mid-month. See the Table in Section L.10.a. of the RFP. CMS currently projects that August 4, 2012, will be the end date of the existing Jurisdiction 4 MAC contract as well as the second Implementation CLIN (CLIN 0008) of the Jurisdiction H MAC contract, enabling the Jurisdiction 4 MAC and Jurisdiction H MAC to conduct appropriate post-cutover coordination prior to the end of the Jurisdiction 4 MAC contract.
814. Section L.10.e. – Annual Workload AssumptionsQuestion/Comment: Can CMS define “backlog- pending” workload noted throughout the workload table?
CMS Response: These workloads represent CMS’s estimate of the volume of pending workload (work in progress), by workload category, that the awardee will receive from the respective incumbent (outgoing) contractors, at the time each operational workload segment is cutover to the Jurisdiction H MAC. Part A “backlog-pending” values (inclusive of Part B of A) during the Base Year represent the projected workload in progress that will be received by the Jurisdiction H MAC from the fiscal intermediary for Arkansas, Louisiana, and Mississippi (Pinnacle). Part B “backlog-pending” values during the Base Year represent the projected workload in progress that will be received by the Jurisdiction H MAC from the incumbent carriers for Arkansas, Louisiana, and Mississippi. Finally, the Part A and Part B “backlog-pending” workloads during Option Year 1 represent the projected workload in progress that will be received by the Jurisdiction H MAC from the current Jurisdiction 4 MAC (TrailBlazer).
825. Section L.10.e. – Annual Workload AssumptionsQuestion/Comment: The workload assumptions included under MIP Medical Review (MR) Part A and Part B include two workload items that are not described in the MAC JH SOW or the Program Integrity Manual and they are not reportable workloads in CMS’ MR Strategy Web portal. These include “Medical Review Data Requests” and “Medical Review Limited Education.” Is there a description of the activities represented by these two workload targets?
CMS Response: The workload for Medical Review Data Requests references the actual number of requests the contractor receives from internal (within the organization) or external (GAO, OIG) sources asking for data the contractor possesses. Medical Review Limited Education is basic education that the Contractor's MR unit may provide to the supplier (documentation, results of probe) and assist the provider outreach and education (POE) staff as the subject matter expert. In-depth education is provided by provider outreach and education (POE) staff. POE is responsible for providing education as a result of referrals from Medical Review. This education would not be an MR activity. See the Program Integrity Manual (PIM) 3.11.1.6, last paragraph to further address this question. Data requests were meant to capture the number of data reports anticipated to be run for medical review prioritization and analysis purposes.

CMS expects education to be performed through the ADR findings letter and probe findings letter. For purposes of this solicitation, Offerors should indicate the number of activities outside POE or the letters that they define as part of medical review.

836. Section L.10.e. – Annual Workload AssumptionsQuestion/Comment: Does the workload “Non-MSP collections” – demands (offset/recoupment/withhold)” only include debt that has been satisfied in full and is closed?CMS Response; CMS confirms that this workload also includes open AR’s (still under the collection process).

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .