Revised_Question_and_Answers_2.20.18.xlsx
XLSX spreadsheet 26 KB Posted
- Attached to
- Pricing, Data Analysis and Coding (PDAC) Contractor Federal contract opportunity
- Solicitation number
- 75FCMC18R0010
View the file
Other files for this federal contract opportunity
Show all 28
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| # | Document | Page | Section | Solicitation Reference | Question | Answer | notes |
| 1 | General Question | NA | NA | NA | Is it the Government's intention that this work will be done by a current Medicare Administrative Contractor? | This procurement is being conducted under FAR 15 procedures with no limiting sources or set-asides. |
2 RFP Section D.2 of the SOW states that the CMS BPSSM is incorporated into the SOW. Although the PDAC contract is not specifically identified as one of the various "business partners" on page 6 of the BPSSM, based on the SOW and level of access to data, the PDAC contract is very similar in access to the DME MACs, which are identified as business partners in the BPSSM. The BPSSM incorporated into the PDAC SOW also includes the CMS Information Security Acceptable Risk Safeguards, which are CMS' Minimum Security Requirements for MACs, in Appendices A, B, and C. In J.09 Security Attestation, it states that the PDAC contract must comply with NIST standards. Based on Section 4 Information and Information Systems Security of the BPSSM, and particularly 4.1.3 - CMS Security Level Designation-HIGH, the similarities with MACs, and the fact MACs must comply with FISMA High standards, does CMS intend PDAC to also comply with FISMA High and the MAC ARS controls in the BPSSM? CMS confirm that the PDAC Contractor shall comply with the security requirements defined in the Business Partner System Security Manual (BPSSM) found at http://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Internet-Only-Manuals-IOMs.html and the MAC specific Information Security (IS) Acceptable Risk Safeguards (ARS) included as Attachment 1 in IOM Publication 100-17 found at http://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Internet-Only-Manuals-IOMs.html.
The Contractor shall comply with the Federal Information Security Management Act of 2002 (FISMA) requirements set forth in section 912 of the Medicare Prescription Drug, Improvement and Modernization Act of 2003 (MMA).
The Contractor shall comply with and utilize standards and guidelines promulgated by the National Institute of Standards and Technology (NIST) in its entity-wide information security program. The Contractor shall comply with the applicable standards, implementation specifications, and requirements of the Health Insurance Portability and Accountability Act (HIPAA) security rule, found at http://www.hhs.gov/ocr/privacy/hipaa/administrative/securityrule/, covering electronically protected health information.
The Contractor shall provide annual certification, in accordance with ATO methodology, that certifies it has examined the management, operational, and technical controls for its systems supporting the Medicare Administrative Contractor (MAC) function and considers these controls adequate to meet CMS security standards and requirements.
Background: The CMS ATO procedures can be found on the CMS web site at www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/InformationSecurity/Information-Security-Library.html
CMS has updated the Statement of Work (SOW) with the above language and is providing an updated SOW (J.01). In addition, CMS will not require submission of a Systems Security Plan with proposals. However, offerors may be asked to furnish their Systems Security Plan upon request.
| 3 | RFP | L.13.B | Business Proposal Instructions | According to the RFP, CMS anticipates awarding a Firm Fixed Price (FFP) contract. Typically on a firm fixed price, only the price is provided. However, in this RFP, cost and pricing data appears to be requested. Please confirm that this is a Firm Fixed Price contract and if so, whether the Government anticipates adequate competition. If the resultant contract is to be FFP and adequate competition is expected, then we would respectfully request an explanation as to why cost and pricing information is being requested. | The RFP has been updated to remove specfic elements based on the anticipated FFP contract type. | |
| 4 | 75FCMC18R0010_PDAC_RFP | 6 | B.4 | Period of Performance | The Total FFP period of performance ending date of 11/30/2023 is not consistent with the CLIN 0007 ending date of 8/31/2023. Please clarify that 8/31/2023 is the end date. | The end date is 8/31/2023. RFP has been updated accordingly. |
| 5 | RFP | 19 | G.7 | Subcontracting Reporting | The RFP states that the reporting periods for the Individual Subcontract Report (ISR) are September 1-February 28 and March 1-August 31; and the Summary Subcontract Report (SSR) shall be submitted annual for the period September 1 through August 31. |
FAR 19.704(a)(10)) states the ISR reporting periods end March 31 and September 30 and the SSR reporting period is October 1 through September 30.
| Which reporting periods are correct for this RFP? | G.7 has been updated in the RFP to reflect the correct dates. | ||||||
| 6 | RFP | 19 | G.6 | Contractor Project Manager | This section of the RFP references a Contractor Project Manager. The term Contractor Project Manager does not coincide with any Key personnel listed in the RFP or SOW. Should the offeror assume that the term Contractor Project Manager means the key labor category Program Director? | The RFP has been updated accordingly. | |
| 7 | RFP | 20 | G.9 | Subcontract/Consultant Consent | Since this is a fixed price contract, is it necessary for government approval if the contractor decides to utilize a subcontractor on a labor hour basis? | Please refer to FAR 52.244-2. | |
| 8 | RFP | 38 | H.5 | CMS Security Clause | For what government systems specifically will the contractor require PIV cards to perform PDAC services. |
CMS confirms, at this time, there are no government systems that will require a PIV card to perform PDAC services. Further, at this time there are no government systems that will require the contractor to have PIV cards.
| 9 | RFP | 43 | H.5.D | Background Invesitgaqtion and Adjudication | What is the time frame for the government to complete a background investigation? | Please refer to H.5 CMS Security Clause of the RFP. |
| 10 | RFP | 43 | H.5.D | Background Invesitgaqtion and Adjudication | For personnel who require access to CMS systems, is interim approval given to employees pending a final approval? | CMS confirms there will be no interm approval give to employees pending final approval of CMS systems. |
| 11 | RFP | 44 | H.5.G | Background Investigation Cost | Should the government require the contractor to reimburse the government, what is the cost of the background investigation? | Please refer to H.5 CMS Security Clause of the RFP. |
| 12 | RFP | 45 | H.5.H | Identification Card Custody and Control | Will personnel under this contract be given/need Identification Cards for access to agency facilities? | The PDAC must be prepared to fully comply with HSPD-12 at the point in time when CMS initiates activity to ensure full HSPD-12 compliance, which could include mandatory us of PIV cards. Upon award of the contract, determinations will be made as to which personnel require access to Agency facilities and subsequently, PIV card requirements will be addressed with the contractor. |
| 13 | RFP | 48-49 | H.7 | Transition from Incumbent to Successor | H.7 describes various requirements for the contractor in the event of termination or non-renewal of the contract. Are the requirements in H.7 included in CLIN 0007, which is not an option, or are should these requirements be included under an additional and separate optional CLIN? If the requirements in H.7 are to be in an option period and not included in CLIN 0007, FAR 17.207 provides that a contracting officer is only authorized to exercise an option to a firm-fixed price contract if the option was evaluated as part of the initial competition and is exercisable at an amount specified in or reasonably determinable from the terms of the basic contract. In that event, does the RFP specify how the Contracting Officer will determine the firm-fixed price for this option at the time the option is exercised in accordance with FAR 17.207? Should the requirements described in Section H.7 be reflected in a CLIN in Section H.7 be reflected in a CLIN in Section B.4 and be evaluated for contract award? In MAC RFPs, CMS has included an instruction that "For proposal purposes, the Offeror shall assume $XXXXXX as its CLIN 0009 outgoing contractor workload transition activities costs." Should CMS direct offerors to use a uniform value for the transition CLIN set by CMS? | H.7 corresponds to CLIN 0007. The RFP has been updated accordingly. |
| 14 | RFP | 49 | H.7.A | TRANSITION FROM INCUMBENT TO SUCCESSOR | The RFP refers to "the ESRD Network Program." Should this reference be to the PDAC program? | Updated accordingly in the RFP |
| 15 | RFP | 50 | L.1 | FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) | The following clauses appear to have been omitted from Section I.1. on page 50 of the RFP: |
52.243-1, Changes - Fixed Price (Alternate I) 52.249-2, Termination for Convenience of the Government (Fixed-Price) 52.249-8, Default (Fixed-Price Supply and Service)
| Do these clauses need to be added to the RFP? | RFP has been updated. | ||||||
| 16 | RFP | 82-83 | L.10 | PROPOSAL DELIVERY | Many corporate and enterprise email systems reject emails larger than an established maximum size (e.g., 15Mb or 25Mb). Does CMS' email system have a message size limit that offerors should take into account when submitting proposals via email? | The maximum file size is 20 MB. The RFP has been updated accordingly. | |
| 17 | RFP | 83 | L.11 | Proposal Organization | CMS requests that Excel document for cost templates be submiited with full functionalty and editting. However, it also states that entire volume should be within one PDF if possible. Should offerors submit all non-Excel files combined into a single file in PDF format? | CMS updated direction in Section L.11, offerors are no longer required to complete and submit cost templates. As stated in section L.11, CMS prefers one PDF per proposal. | |
| 18 | 75FCMC18R0010_PDAC_RFP | 84, 86, 91 | L.11, L.12.Tab B.2, L.13.A | Proposal Organization, Technical Proposal Instructions-Project Management, Business Proposal Instructions-Cover Letter and Table of Contents | The RFP includes two different locations for assumptions. Section L.11 indicates that they should be included on the cover page of each proposal, whereas sections L.12.B.2 and L.13.A indicate that they should be included in a separate document (attached to Cover Letter) as part of Volume II. Please clarify. | CMS removed assumptions direction in section L.11, L.12 Tab B.2, and L.13.A. CMS has updated section L to add direction for Tab B.6: Proposal Assumptions. Tab B.6 is not included as part of the 30-page limit. However, there is a 5-page limit to the Proposal Assumptions. |
| 19 | RFP | 85 | Tab B.1.1 | Work Breakdown Structure | A WBS generally does not contain positions and jog titles, just tasks, milestones, timeframes, and deliverables. Please clarify in what format you would like to see the WBS. | The offeror shall structure the WBS such that it makes certain the position/job titles algin with the SOW. No specific format is required. |
| 20 | RFP | 86 | L.12 | B.2 Project Management | Some elements of the Project Management Plan (Staffing Chart, paragraph 2, Labor Types paragraph 5) appear to be duplicated in Tab B.4 Staffing Plan. Please clarify what information is required in each of these sections, and what the difference is between the two sections. | CMS confirms and acknowledges there is an intentional level of duplication between the two sections. CMS believes it’s important for offerors to address this issue separately in both sections, as these two sections have different functions during the evaluation of the proposal. |
| 21 | RFP | 86 | l.11 - B.3 | Key Personnel | Is CMS directing offerors to include narrative in Tab B.3 Key Personnel regarding a list of names, proposed duties, and labor hours as well as identification of all full-time equivalents (FTEs) segregated by their labor category and also by proposed labor hours? If so, is it correct that all narrative in Tab B.3 is excluded from the 30 page limitation? Or does CMS just intent to exclude the resumes and letters of commitment that are to be included in Tab H? | CMS confirms resumes are limited to 3 pages and letters of commitment to 1 page. All other information requested under B.3 will not be included in the 30-page limit. |
| 22 | RFP | 86 | Tab B.2: | Project Management | In the last sentence of the fourth paragraph of the project management section, the RFP asks offerors to describe their "corporate commitment to providing quality service during the transition to the PDAC contract." Did CMS intend to limit offerors' description of corporate commitment to providing quality service only during the transition to the PDAC contract or did CMS intend for offerors to describe their corporate commitment to providing quality service during ongoing operations of the PDAC contract, as well? |
CMS removed the words "the transition to" from section L Tab B.2.
| 23 | 75FCMC18R0010_PDAC_RFP | 87 | B.3.5 | Resume requirements | Is US citizenship an eligibility criteria for key personnel? | Please refer to H.5 CMS Security Clause |
| 24 | RFP | 89 | L.12 | D.1 Implementation and Project Plan | This section states that “Under this sub-factor, the offeror shall also provide a detailed Implementation Project Plan…”. Should the offeror submit this plan in a particular file format, i.e., Word, Excel, MS Project? If so, which file format is the government directing the offeror to use? |
CMS directs the offeror to submit this plan in Microsoft Word.
| 25 | 75FCMC18R0010_PDAC_RFP | 89 | L.12, Tab C, b. | Past Performance Instructions, Instructions | The example table for past performance information is presented in a landscape orientation. May the offeror change the orientation of the table to portait? This change will result in data that is easier to read/review. | CMS confirms the offeror may change the orientation of the table in section L.12, Tab C. |
| 26 | RFP | 90 | Tab F | Utilization of Small Business (shall not exceed 2 pages) | We intend to complete the CMS-provided Attachment J.10 HHS Subcontract Plan Template, however the instructions state that it not exceed 2 pages. As the blank template is 7 pages, completing this along with including the certification of current business size and type, and including the last 2 years of eSRS reports will greatly exceed the 2 pages. Please clarify the page limitation instructions. | The RFP has been updated. |
| 27 | 75FCMC18R0010_PDAC_RFP | 91 | L.13, Tab G | Section 508 | CMS states "Offeror shall complete a Product Accessibility Template (PAT) [See Attachment J.13]." What product or website is CMS asking the offeror to assess? | Please refer to Attachment J.13, page 4, item #5, GSA Buy Acessible Wizard which provides tools to help determine if acessiblity requirements apply to Information and Communication Technology products and services. Attachment J.13 has been updated. |
| 28 | RFP | 97 | L.14 | Business Ethics, Conflict of Interest and Compliance Proposal Submission Instructions | Section L.14 requires that subcontractor COI information be submitted in Volume III, Appendices. Can CMS confirm that subcontractor information is to be submitted to CMS for review, or is CMS directing the offeror to collect, review and determine whether subcontractor conflicts exist and include that conclusion in the offerors Attachment J.18? | Please refer to H.1 of the RFP. |
29 Attachment J.05 GovtFurnishedMaterials J-05 Government Furnished Property Attachment Attachment J.05 Government Furnished Materials references Web-base Intelligence (WebI), a Web based product that allows CMS and certain other entities access to current and historical data analysis, reports and research articles published by PDAC. The WebI application requires a license for a business intelligence application such as Business Objects. Should offerors include costs in their business proposal for a license for a suitable business intelligence application and annual maintenance fees?
Yes, CMS affirms that offerors should include costs in their business proposals for a license for a suitable business intelligence application for the WebI application, including annual maintenance fees.
30 Attachment J.06 Proposal Assumptions 1 4 Workload Figures What is the average call duration and Total Handle Time of the Telephone Inquiries?
CMS confirms for proposal purposes offerors shall expect an average call duration including handle time of 90-200 seconds. Per SOW section E.2.5.1, PDAC shall respond to calls within 90 seconds of receipt for a mimimum of 85% of incoming calls.
31 Attachment J.06 Proposal Assumptions 2 4. Workload Figures Written/Email Inquiries What is the average response time for written/email inquiries? CMS confirms section E.2.5.2, a telephone or written response shall be developed within 45 calendar days of receipt.
| 32 | Attachement J.05 GovtFurnishedMaterials | 1 | Crosswalks (general) | HCPCS to 855S crosswalk (not listed) | Like all other crosswalks defined, should the HCPCS to 855S crosswalk be considered as government furnished? | CMS confirms the HCPCS to 855S crosswalk is considered government furnished. The Government Furnished Material attachment (J.05) was updated to include this information. |
| 33 | Attachement J.05 GovtFurnishedMaterials | 1 | DMEPOS Claims Data Warehouse | Server Licensing | Is CMS mandating that only an Oracle server can be used to house DMEPOS claims data if there are other viable and cost effective methods for warehousing? |
CMS affirms an Oracle license is not required, and a different relational database that meets CMS requirements is acceptable. Further the Oracle service is not considered government furnished, licenses and maintenance will not transition with this contract.
| 34 | Attachment J.05 GovtFurnishedMaterials | 1 | DMEPOS Claims Data Warehouse | Data Warehouse | Where is the DMEPOS Claims Data Warehouse hosted today? | CMS confirms the DMEPOS Claims Data Warehouse is hosted as VMS (ViPS medicare system). |
| 53 | Attachment J.05 GovtFurnishedMaterials | 1 | DMEPOS Claims Data Warehouse | Data Warehouse | Would CMS look favorably on the offeror moving the DMEPOS Claims Data Warehouse to an existing contractor-owned and contractor-operated Data Warehouse? | CMS confirms the incumbent contractor will be responsible for hosting the DMEPOS Claims Data Warehouse. |
| 35 | Attachment J.06 Proposal Assumptions | 1-4 | 4 | Workload Figures | It appears the Base Year quantities in Section 4 are the same as the quantities in Option Years 1-4, even though Base Year is 9 months and the Option Years are 12 months. Please confirm the Base Year quantities. |
CMS confirms that Base Year workload quantities have been updated. See updated Government Provided Proposal Assumptions (J.06).
36 Attachment J.06 Proposal Assumptions 3 Attach J.06 Proposal Assumptions workload NDC HCPCS Crosswalk file - number of updates All years have a workload of 2,096, except OY1, which has a workload of 209. This appears to be a clerical error. Can CMS please confirm the correct workload for OY1 for the workload NDC HCPCS Crosswalk file - number of updates?
CMS confirms the workload for OY1 should reflect 2096. See updated Government Provided Proposal Assumptions (J.06) .
37 Attachment J.06 Proposal Assumptions 3 4 Workload Figures size of data warehouse Although the number of years of archived data in the warehouse increments with each year of the contract, the size of the archived claims data in the warehouse does not increase year over year even though an additional year's worth of claims volume is expected to be added to it each year. How much additional storage of archived data should offerors assume for each year of the contract? CMS estimates an increase of 15% per contract year for archive claims data will occur.
| 38 | 75FCMC18R0010_PDAC_RFP | 3 and 61 | Table of Contents, J.15 | List of Attachments | Attachment J.15 is referenced on page 3 and page 61 as J.15 Service Center Matrix, but is not discussed anywhere in the solicitation. Is this a required attachment and if so, please clarify the purpose and placement in offeror's proposal. | The RFP has been updated. |
| 39 | Attachment J.09 Security Attestation | In J.09 - Security Attestation, in the second item in table "Information Security Requirements", the text references a "Systems Security Plan that complies with CMS Methodology listed in section C.5.4.3 of the SOW". This appears to be incorrect. Does CMS intend this to refer to Section D.2 of the SOW? |
CMS confirms the section C.5.4.3 reference was incorrect. CMS has updated the Attestation document (J.09).
40 SOW 13 A.4 Additional Constraints Does the contractor require access to the common working file to perform PDAC services?
CMS confirms the contractor will require access to the common working file (CWF) to perform PDAC services. This will be completed through the Data Use Agreement process upon award of the contract.
| 41 | Attachment J.01 Statement of Work | 13-20 | J-01 | Statement of Work Attachment, section B | The Program Director, Medical Director, Special Projects Coordinator, HCPCS Coding Specialist, and Orthotist/Prosthetist are required to be fully dedicated to the PDAC contract. However, the biomedical engineer and the Manager of Reports and Analysis are not specifically identified as being fully dedicated. Please confirm these positions are required to be fully dedicated to the PDAC contract. | CMS affirms that all key personnel identifed in this solicitation must be fully dedicated to the Contract. CMS has update the SOW (J.01). |
| 42 | Attachment J.01 Statement of Work | 18-19 | B. Personnel Requirements | B.6. Biomedical Engineer (Key Personnel) | Given the specificity of medical devices and technology, would CMS consider for this position, the proposal of a Biomedical collective intelligence with an identified lead, rather than a single Biomedical Engineer? | Yes, CMS confirms that as long as the collective team of experts is working with and lead by a fully dedicated Biomedical Engineer. |
| 43 | SOW | 19 | B.6 | BioMedical Engineer | Regarding the Biomedical Engineer position, it is well recognized in the discipline that electrical and mechanical engineers serve as biomedical engineers in academic and industry bioengineering positions. Will Bachelor’s degree or higher in traditional engineering such as Electrical, Mechanical, or Chemical Engineering be accepted with the three or more years of experience in bioengineering or biomedical engineering? Reference: http://theinstitute.ieee.org/career-and-education/career-guidance/what-it-takes-to-be-a-bioengineer | No, the individual must have specific education and training as a Biomedical Engineer. |
| 44 | SOW | 23 | C.1.1.2 | Cutover Project Plan | This section states that “The incoming PDAC contractor shall submit the initial Cutover Project Plan at least six weeks before the OSD…” There is no mention in this section nor in RFP Tab 2 that states that this plan shall be submitted as a part of the Offeror’s proposal. Please confirm our understanding that this plan is not required as part of proposal submission. | CMS confirms this plan is not requred as part of the proposal submission. |
| 45 | Attachment J.01 Statement of Work | 31 | D.2.1.1 | Administer Security Program | Section D.2.1.1 states "As previously stated in Section B.3.5 of this SOW, the CIO and SSO need not be fully dedicated to this contract." Should this reference be toSection B.7.3, instead of B.3.5? | CMS confirms this reference should be B.7.3. CMS has updated the SOW (J.01). |
| 46 | Attachment J.01 Statement of Work | 36 | D.3 | Change Mgmt Process Requirements | Section D.3 of the SOW, on page 36, states that, ?The Contractor shall promptly notify CMS, in accordance with the terms and conditions of this contract, if it believes that any CMS Change Request will cause an increase or decrease in its costs or otherwise affect any other term or condition of this contract.? With respect to this SOW requirement, please confirm that an increase or decrease in the costs to perform the contract will be processed in accordance with the Changes clause of the contract, 52.243-1 Changes?Fixed-Price, and any equitable adjustment to the firm-fixed price of the contract will be made in accordance with the terms of that clause. | Please refer to B.5 Task Directive of the RFP. |
| 47 | Attachment J.01 Statement of Work | 36 | D.3 | Change Mgmt Process Requirements | Section D.3 of the SOW, on page 36, states that, "The Contractor shall provide a level of effort per contract period to (1) Participate in the POC Review process, and (2) Implement CMS Change Requests. In addition, the Contractor shall also assist CMS in preparing HCPCS-related CMS Change Requests under Section E.1.5 of this SOW". With respect to this SOW requirement: |
a. What does it mean to "provide a level of effort per contract period"
b. Is an offeror required to include this work in the firm-fixed price of the contract? If so, can CMS provide the level of effort required for this work?
| c. If the firm-fixed price for this work is not included in the firm-fixed price of the contract, how will the firm-fixed price of the contract be adjusted for this work? | Offerors should refer to SOW section D.3 for direction relative to level of effort. The Government Provided Proposal Assumptions document (J.06) provides workload estimates for proposal purposes. | ||||||
| 48 | SOW | 45 | E.2.5.1 | Telephone Standards, Toll Free Network Services | This section states that all inbound telephone service shall be handled over Networx with the designated network service provider, Verizon and the contractor shall not maintain its own local inbound lines. Is there a requirement or a limitation on the type of circuits that can be acquired? | CMS will provide toll-free service for telephone inquiries handled by the PDAC. The Contractor provides all other telephone services needed to fulfill the requirements of the contract. There are no requirements or limitations on the type of circuits that may be used. | |
| 49 | SOW | 45 | E.2.5.1 | Telephone Standards, Toll Free Network Services | This section states that all inbound telephone service shall be handled over Networx with the designated network service provider, Verizon and the contractor shall not maintain its own local inbound lines. If telecommunications services are purchased through this channel, the actual local inbound lines will be delivered and still have to be maintained by someone. Did the government mean to say that these lines are simply not to be purchased through any other channel or should the contractor engage Verizon in professional/managed services to maintain the actual lines once they are purchased? | CMS confirms that voice services are maintained by the Netwox provider. Networx is the General Services Administration (GSA) contract vehicle from which CMS procures it’s voice and data services. Networx services can only be procured by and billed to CMS. Contractors cannot purchase services off Networx as it is a government only vehicle. | |
| 50 | SOW | 45 | E.2.5.1 | Toll Free Network Services | This section is labeled as "Toll Free Network Services" but the paragraph describes phone lines. Toll free services are generally purchased separately from phone lines. Does this paragraph apply to phone lines, toll free services, or both? | CMS confirms section E.2.5.1 applies to both phone lines and too free service. | |
| 51 | SOW | 45 | E.2.5.2 | Written Correspondence | This section states that "The contractor shall stamp all written inquiries with the date of receipt in its mailroom and control them until a final answer is sent." May the contractor to scan such written inquiries into a unquely created date stamped electronic file, electronicall store files indefinitely, and destroy the original paper copies immediately following electronic file creation? | CMS confirms the contractor may dispose of the original paper inquiry documents after 30 days provided its imaging and quality assurance processes comply with the requirements of CMS’s Internet-Only Manual (IOM) 100-01, Chapter 7, Section 30.30. This manual may be found at https://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Downloads/ge101c07.pdf. Further, the contractor must retain the electronic copies of such routine correspondence and inquiries for a minimum period of three years; CMS may direct a longer retention period in the event of a litigation hold or other program need.” | |
| 52 | SOW | 46 | E.3.2 | NDC-HCPCS Crosswalk | This section states that the files shall be available for download via NDM or Connect:Direct. Shall the contractor procure NDM/Connect:Direct licenses or can the contractor use a license already procured by CMS? | CMS confirms the contractor will need to procure a NDM/Connect: Direct license. | |
| 53 | Attachment J.01 Statement of Work | 46 | HCPCS - 855S Crosswalk | Collaboration | What involvement will the contractor have with accrediting organizations (AOs) in order to maintain the HCPCS - 855S crosswalk? If any, will JOAs be required? | CMS confirms the PDAC Contractor will have no involvmenet with the accrediting organization for the HCPCS-855S Crosswalk. Subsequently no JOA will be required. | |
| 54 | SOW | 47 | E.4 | Conduct DMEPOS-Related Statistical Analysis Activities | This Section states that the contractor shall provide statistical support to various parties. Will CMS provide the successful offeror a license to use SAS for this activity or shall the contractor acquire his/her own license? | CMS confirms that offerors must propose their technical approach to meeting the SOW requirements, including any proposed analytical software, in keeping with section L of the RFP. Offerors must include costs required to support their technical approaches, including any software licensing costs, in their business proposal pricing. | |
| 55 | SOW | 47 | E.4.1.1 | Daily Activities | Please explain the purpose of the Daily Receipt of electronic transmissions of Medicare FFS DMEPOS claims records as opposed to monthly Final Action feeds from CMS of the Medicare FFS DMEPOS claims records. The SOW calls for monthly, quarterly and annual reporting and various Data Analytics identifying billing and coverage trends and patterns. Those analyses would rely on final action claims over longer periods of time than single daily claims and/ or adjustments. Is there a specific use for daily Medicare FFS DMEPOS claim records by the PDAC? | CMS confirms the reason for a daily receipt of electronic submissions of Medicare FFS DMEPOS claims is to ensure accurate loading of that information into the data warehouse. | |
| 56 | SOW | 47 | E.4.1.1 | Daily Activities | What specifically is the source of the daily feed of DME Data? | CMS confirms the daily feed of DME claims data comes from the Common Working File (CWF). | |
| 57 | SOW | 47 | E.4.1.1 | Daily Activities | Must the offeror must have access to the DME data sources prior to contract award? | No, CMS confirms the offeror will not have access prior to contract award. | |
| 58 | SOW | 53 | E.6.2 | Data Warehouse | How many tables and how many rows are currently in this data warehouse. | CMS confirms this information shall be different for each contractor responsible for the data warehouse. | |
| 59 | SOW | 53 | E.6.2 | Data Warehouse | How large is the aggregate size (in bytes) of the nightly download of DMEPOS claims from CMS? | CMS confirms the size of the nightly download varies, therefore the amount can not be provided. | |
| 60 | SOW | 53 | E.6.2 | Data Warehouse | What is the format of files of the current nightly download of DMEPOS claims from CMS? | CMS confirms the file format is a flat file. | |
| 61 | SOW | 54 | E.6.3 | Web Technology | How many unique visitors and how many unique hits does the current web site get per month? | No response be provided. |
File details come from the government source that posted it.