J.1.C Fee-For-Service Shared System Base Functions.docx

DOCX document 69 KB Posted

Attached to
Part A/B Medicare Administrative Contractor, Jurisdiction E
Solicitation number
75FCMC19R0023
Issued by

About this file

This document outlines the base functions required of a Medicare Administrative Contractor for Jurisdiction E. The contractor shall perform numerous claims processing and payment services in support of the Medicare Fee-For-Service Program for California, Hawaii, Nevada, American Samoa, Guam, and Northern Mariana Islands. Required functions include claims adjudication, provider enrollment and data exchange, beneficiary eligibility verification, financial accounting and reporting. The contractor must comply with all applicable laws, regulations and CMS requirements to ensure program integrity. CMS intends to issue a solicitation on September 4, 2019 for these services with a proposal due date of November 4, 2019 and anticipated award by August 4, 2020. The contract term includes a one year base period and six one-year options.

RFP Attachment

View the file

Other files

File Type Posted
75FCMC19R0023_Amendment_2.pdf PDF
Amendment_2,_Attachment_1_-_RFP_Question_Responses.xlsx XLSX spreadsheet
JE_Amendment_1_CLEAN_Attachments_UPDATED.zip ZIP file
Amendment_1,_Attachment_1_REDLINE_Backpages.pdf PDF
JE_Amendment_1_REDLINED_Attachments_UPDATED.zip ZIP file
JE_RFP_Questions_and_Responses_Amendment_1.xlsx XLSX spreadsheet
75FCMC19R0023_Amendment_1.pdf PDF
J.23 Government Provided Proposal Assumptions —
J.39 CLIN 0006 Cost Proposal Template - Option Year 2 —
J.1.G AB MAC Performance Requirements Summary.docx DOCX document
J.22 Basis of Estimate.xlsx XLSX spreadsheet
J.42 CLIN 0009 Cost Proposal Template - Option Year 3 —
J.34 CLIN 0001 Cost Proposal Template - Implementation.xlsx XLSX spreadsheet
J.1 Statement of Work —
J.40 CLIN 0007 Cost Proposal Template - Option Year 2 —
J.28 Product Accessibility Template.docx DOCX document
J.5 Government Systems Provided For Use.docx DOCX document
J.46 CLIN 0013 Cost Proposal Template - Option Year 5 —
J.37 CLIN 0004 Cost Proposal Template - Option Year 1 —
J.45 CLIN 0012 Cost Proposal Template - Option Year 5 —
J.49 CLIN 0016 Cost Proposal Template - Outgoing Contractor Workload Transition Activities.xlsx XLSX spreadsheet
J.10 Contractor Business Ethics COI and Compliance Program Requirements.docx DOCX document
J.1.A List of Key Definitions.docx DOCX document
J.23.A Government Provided Proposal Assumptions Audit and Reimbursement Tables.xlsx XLSX spreadsheet
J.33 Cost Template Summary Sheet.xlsx XLSX spreadsheet
J.23.B Government Provided Proposal Assumptions CSR-Handled Telephone Inquiries Tables.docx DOCX document
75FCMC19R0023.pdf PDF
J.11 Personal Conflicts of Interest Financial Disclosure.docx DOCX document
J.2 Deliverable Schedule.docx DOCX document
J.1.D Cash Collections Worksheet For HIGLAS Users.xlsx XLSX spreadsheet
J.44 CLIN 0011 Cost Proposal Template - Option Year 4 —
J.24 Attestations.docx DOCX document
J.47 CLIN 0014 Cost Proposal Template - Option Year 6 —
J.3 Small Business Subcontracting Plan Template.docx DOCX document
J.35 CLIN 0002 Cost Proposal Template - Base Year —
J.32 Systems of Records.docx DOCX document
J.48 CLIN 0015 Cost Proposal Template - Option Year 6 —
J.7 AB MAC Award Fee Plan and Self Assessment Template.docx DOCX document
J.25 Past Performance Questionnaire.docx DOCX document
J.4 HHS Contracting Guide for Contract of Government Property.docx DOCX document
J.41 CLIN 0008 Cost Proposal Template - Option Year 3 —
J.43 CLIN 0010 Cost Proposal Template - Option Year 4 —
J.9 Non-Disclosure Statement.docx DOCX document
J.1.B List of Key Acronyms.docx DOCX document
J.36 CLIN 0003 Cost Proposal Template - Base Year —
J.38 CLIN 0005 Cost Proposal Template - Option Year 1 —
J.8 MAC Security Incident and Reportable Event Reporting and Response.docx DOCX document
J.6 Contractor Furnished Property.docx DOCX document
Show all 48

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

Attachment J.1.C Fee-for-Service Shared System Base Functions – Appendix C to SOW

RFP # 75FCMC19R0023

Function
Shared System Provided
VDC Provided
Security
Application password security via a personnel file containing user authorization flags to control access to specific functions
· Maintenance of network/environment security rules, via Resource Control Facility (RACF) at the Virtual Data Centers (VDCs).

· Maintenance and operation of non-z/OS platforms’ security needs, i.e., Windows, Unix/Linux, etc.

· Data Center security ID and password that controls access into the data center system – including Time Sharing Option (TSO)/ Interactive System Productivity Facility (ISPF) access, Network Data Mover (NDM)/file transfer systems’ user id’s and file access controls, access into the Customer Information Control System (CICS) regions, access to CICS transactions, and read/write access to files.

· Coordinate with other datacenters, for needed security accesses, such as real-time accesses for CICS-to-CICS systems transactions (across different datacenters).

· Guarantee the access separation and other user and batch process’ access restrictions, between different companies’ data being stored and processed at the VDC.

· Data Center security Machine-ID and non-expiring password that controls access into the data center for functions such as Interactive Voice Response (IVR), Next Generation Desktop (NGD), and various Medicare Administrative Contractor (MAC) provider and supplier portals.

Telecommunications

· Works with Centers for Medicare & Medicaid Services (CMS) approved contractors and Maintainers as necessary to establish batch and interactive connectivity between the data centers.

· Implement and maintain firewalls, data connectivity with outside vendors and other entities, and other network management systems supporting the Virtual Data Center (VDC) functions and services.

· Implement and maintain secure connectivity into the VDC via Virtual Private Network (VPN) and two-factor authentication services.

· Provision and mitigate for such risks and events as: disasters (recovery), network and power outages, work-site outages, and test/drills for such events. Prepare and support other organizations that we connect with, with their risks, events, and testing efforts.

File Transfers
The Shared System maintainer’s software creates Reference Files to be incorporated into the execution of the Common Edits and Enhancement Module (CEM) software used at the Contractor’s Local Data Center (LDC).
· The Virtual Data Center (VDC) executes the jobs necessary to transmit Centers for Medicare & Medicaid Services (CMS)-approved files from the VDC to any other CMS approved contractors, Baltimore Data Center (BDC), Maintainers and 3rd Party Vendors.

· The VDC receives files transmitted from CMS approved contractors, BDC, Maintainers, and 3rd Party Vendors.

Electronic Data Interchange (EDI)
The Shared System Maintainer’s Common Edits and Enhancement Module (CEM) software for Part A Fiscal Intermediary Standard System (FISS) and Part B Multi-Carrier System (MCS) work in conjunction with the Contractor’s Commercial Off The Shelf (COTS) software for electronic data interchange (EDI) (inbound and outbound) transactions in Accredited Standards Committee (ASC) X12 Version 005010. This includes transactions adopted under the Health Insurance Portability and Accountability Act (HIPAA) regulations and those the Centers for Medicare & Medicaid Services (CMS) has chosen to adopt prior to being named in any HIPAA or other regulatory statue.

MCS and FISS accept CMS’ X12 flat files for HIPAA EDI transactions created from the translation of ANSI ASC X12N version 4010A.1 format, as well as other EDI transactions as directed by CMS. (There are currently no ASC X12 version 0041010/004010A1 EDI transaction formats supported other than those implemented per the HIPAA requirements, but CMS could direct at some point that supplemental EDI transaction standards not yet adopted under HIPAA be supported as well.)

At present, MCS and FISS software support a path for each single version of the ASC X12 HIPAA EDI standards. Specifically the 00410/004010A1 and the 005010 EDI transactions do not process in the same set of programs. When a subsequent version is adopted as a national standard under HIPAA, it will be necessary for the Contractor to support both the new and the old versions until all users are required to use the new version exclusively.

Perform pre-pass editing and reporting for the Version 00410/004010A1. This activity is separate and distinct from the 005010 activity. The Contractor shall continue to support all versions until appropriate sun setting notice has been provided.

· The Virtual Data Center (VDC) executes the jobs necessary to back up the Interface files to any recreate instances for the MAC.

· The Virtual Data Center (VDC) executes the jobs necessary to create INIT Files so that the System can run without Issues in an event when the file is not transmitted by the CMS approved contractors, Baltimore data Center (BDC), Maintainers and 3rd Party Vendors.

MCS furnishes the Professional Provider Telecommunication Network (PPTN) application for provider inquiry of claims status information via a Direct Data Entry (DDE) type screen and MCS also furnishes a link to the Common Working File (CWF) via a maintained DDE screen established to request and receive beneficiary eligibility information.

Creation of electronic remittance advices in the HIPAA mandated Format. This also includes the ability to send “Production Parallel” Health care Claim Payment/Advice in current and minus one versions of the ASC X12 835 transaction.
Execution of the jobs to produce the remittance advice flat files for translation into compliant HIPAA standard remittance advice transactions by the Medicare Administrative Contractor (MAC) or a contractor data center subcontracted to perform this function pending later implementation of a standard front end

Creation of crossover data for the Benefits Coordination & Recovery Center (BCRC)

Execution of jobs to transmit the crossover flat file claims data to the BCRC via the Medicare telecommunications network.

FISS furnishes the DDE application for provider on-line claim entry, correction of institutional claims, determination of claim status and a link to the CWF maintained DDE screen established to request and receive beneficiary eligibility information.
The VDC executes the jobs necessary to initiate the Transaction provided by the Maintainer to process the Front End Pre-Edit of the Claims.
Claims Entry
Activations and Claims Inquiry System (ACIS)

· Automated Development System (ADS), including a base letter file selected from an existing user

· Generation of standard International Business Machines (IBM) Advanced Function Presentation (AFP) mixed mode or Xerox JDL/JDE print file containing development letters (English or Spanish) that support use of contractor-maintained optical mark recognition (OMR) marks or 3 of 9 barcodes

· Execution of the jobs to transmit the base print output to the contractor local data center.

· Transmit the Base Prints for Meta Data to the Next Generation Desktop (NGD).

A base set of reference files and tables selected from an existing shared system user
Execution of the jobs to retrieve the Correct Coding Initiative (CCI) data from the Centers for Medicare & Medicaid Services (CMS) data center and transmit it to the Virtual Data Center (VDC)

On-line work scheduler

Suspense document print file

Weekly EOLQA sampling

Comprehensive Error Rate Testing (CERT) processing
Execution of the jobs to transmit the base output to CMS’ CERT contractor
Existing CMS Standard Automated Response Unit (ARU) interface in the form of an on-line transaction
Ability to connect to the Fee-for-Service (FFS) application at the VDC

Correspondence application that provides ability to track telephone and written correspondence

Maintenance of screens for manual keying of data contained on paper claims, translation of that data into a flat file for processing, issuance of a claim control number and indicator that identifies the claim as having been submitted on paper (for later claim payment floor and Contractor Reporting of Operational and Workload Data (CROWD) reporting purposes), front end editing to assure that required fields have been included and there are no obvious errors in the data prior to transfer to the VDC and rejection of claims with appropriate error messages that do not pass that editing
Execution of the jobs to complete adjudication of the paper claim data, apply appropriate Medicare program edits, reject claims that do not pass those edits with appropriate reason and remark codes for the 835 flat file, produce data with appropriate reason and remark codes for the 835 flat file when the claim is approved and deposit of the adjudication information on the payment floor when payment is due.
Map between paper claims and the system flat file to enable paper claims electronically read and entered using optical character recognition (OCR) technology to be electronically processed, have a claim control number issued, record that the claim was received on paper, perform front end edits and issue appropriate error messages if applicable
Execution of the jobs to complete adjudication of the paper claim data, apply appropriate Medicare program edits, reject claims that do not pass those edits with appropriate reason and remark codes for the 835 flat file, produce data with appropriate reason and remark codes for the 835 flat file when the claim is approved and deposit of the adjudication information on the payment floor when payment is due.
Correspondence and Customer Service
Graphic User Interface (GUI) based MCS Desktop Tool (MCSDT), if desired
Ability to connect to the Fee-for-Service (FFS) application at the Virtual Data Center (VDC)
Letter-writing application, including a base letter file selected from an existing shared system user
The VDC hosts the Client Letter web hosting software for letter generation for Durable Medical Equipment (DME) customer service.
Generation of standard International Business Machines (IBM) AFP mixed mode or Xerox JDL/JDE print file for correspondence response letters (English or Spanish) that support use of contractor-maintained optical mark recognition (OMR) marks or 3 of 9 barcodes
Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the Job Control Language(JCL))
Pricing/ Profiles
Maintenance capability for the Medicare Physician Fee Schedule Data Base (MPFSDB), customary, prevailing, ambulance fee schedule and zip code file and other relative pricing files
· Execution of the jobs to retrieve the fee schedule data from the Centers for Medicare & Medicaid Services (CMS) data center and transmit it to the Virtual Data Center (VDC).

· Execution of the jobs to extract the contractor-specific fee schedule data.

· Execution of the Fiscal Intermediary Standard System (FISS) Health Care Common Procedure Coding (HCPC) Jobs at the VDC with all the extracted files and effective dates to load the HCPC File as the files become available in a Technical Direction Letter (TDL)/Change Request (CR).

· Work with the Medicare Administrative Contractor (MAC)/Maintainer on an agreed upon scheduled to run Jobs in order to load during Quarterly and Off Quarterly schedule. Work with MAC to transmit the file and reports to review.

Standard provider profile build logic
Support and process the annual Profile Build updates & modifications (Multi Carrier System [MCS]).
Automated pricing of claims
Execution of online Family and Social Services Administration (FSSA) transactions to adjudicate claims
Automated “mass” adjustments capability
· Work with the MAC on the criteria that can pull a large volume of claims and degrade the performance of the system.

· Work with the MAC on timing of running the Mass Adjustments.

· Execution of jobs to create adjustments from the Expert Claims Processing System (ECPS)

Express Adjustments
· Work with the MAC on the criteria that can pull a large volume of claims and degrade the performance of the system.

· Work with the MAC on timing of running the Mass Adjustments.

Limiting Charge processing
Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the Job Control Language (JCL))
Medicare Secondary Payer (MSP)
Medicare Secondary Payer (MSP) validation through a base set of audits
Execution of jobs to generate MSP maintenance transactions and transmit to Common Working File (CWF)

MSP automated payment calculation

Identification of MSP recovery claims via Internal Revenue Service (IRS)/Social Security Administration )SSA) Data Match and retroactive recovery with automated history searching

Systematic MSP Automated Recovery Tracking (SMART) system
Execution of the jobs to retrieve the Data Match files and transmit them to the Virtual Data Center (VDC)

· Demand packages in a basic AFP mixed mode or Xerox Dynamic Job Descriptor Entry (DJDE) print file, along with mailing label print files for certified and non-certified mail

· Associated folder label print file Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the Job Control Language (JCL))

Receipt and installation of Electronic Correspondence Referral System (ECRS) software.

Reporting
Provide data used to complete the required Centers for Medicare & Medicaid Services (CMS) reports such as the:

· Workload and Performance/ Production Performance Monitoring System (PULSE) file;

· Appeals;

· Medical Review Workload;

· Medical Review Savings;

· Program Integrity Management Reporting System (PIMR);

· Medicare Secondary Payer (MSP) Savings;

· Chief Financial Officer (CFO)

· Execution of the jobs to transmit the Program Integrity Management Reporting System (PIMR) data to CMS’ PIMR contractor

· Execution of the jobs to transmit the Correct Coding Initiative (CCI) report to CMS’ CCI contractor

· Execution of the jobs to transmit the data to CMS’ PULSE contractor

Numerous reports to track and control inventory and production. Refer to report documentation for specifics
Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the Job Control Language (JCL))
Provide the base data files for use in contractor-specific Ad-Hoc Reporting and Data Extracts
Execution of the jobs for ad-hoc reports or data extracts (with CMS approval)
Provide long-term electronic storage and retrieval of job reports and batch job history, not otherwise sent out by file transfer.
Virtual Data Center (VDC) supports reporting function via hosting CA-View (report management system) and JHS (Job History System) software platforms.
Provider
Processes claims using provider enrollment data from the Provider Enrollment Chain Ownership System (PECOS)Accepts the PECOS Daily Export Extract file of provider information, used to merge PECOS data with provider data for claims processing
· Telecommunications mechanism between the Virtual Data Center (VDC) and the PECOS

· Retrieval of the Daily Export Extract file from the PECOS (one per Contractor number)

Creation of yearly participating (PAR) provider counts

· Creation of a weekly mammography report

· Validation of certification numbers for mammography facilities Execution of the jobs to retrieve the Mammography Quality Standard Act (MQSA) File from the CMS data center

Multi Carrier System (MCS) creates weekly tapes for the Railroad Retirement Board (RRB) containing provider extract data

Interface to Finalist zip code cleansing software to cleanse provider addresses
Receipt and installation of Finalist software and database updates
Provider file accessor
Execution of the jobs for ad-hoc reports or data extracts (with Centers for Medicare & Medicaid Services (CMS) approval)
Provide access to the data required to produce the Medicare Participating Physician Supplier Directory (MEDPARD)
· Execution of the jobs to extract provider data (with CMS approval)

· Creation and execution of the jobs to transmit the extracted data to contractor data center

Desktop Label and Reporting database application (PIN Support (PSUP) Query appl.)
Execution of the jobs to transmit the extracted data to contractor data center
Common Working File (CWF) Interaction
Creation of CWF transmits files for claims, Medicare Secondary Payer (MSP), and eligibility data
Execution of the jobs to transmit the data to the CWF host
Accepts CWF response files for claims, MSP and eligibility data
Receipt of CWF response files from CWF Host
Interaction with Health Insurance Master Record (HIMR) Eligibility and Claim Data on a subset of Multi Carrier System (MCS) screens
Receipt and installation of HIMR software
Bridge between the Fiscal Intermediary Standard System (FISS) Direct Data Entry (DDE) System and the CWF Eligibility Inquiry Screen in CWF (ELGA, ELGH, HIQA, HIQH, and HUQA) screen for eligibility inquiries by Medicare Part A providers
Receipt and installation of CWF provider queries software.
CWF application software and changes to the CWF Host
Receipt and installation of CWF software

Virtual Data Center (VDC) also supports the following:

· Beneficiary Data Services (BDS) process

· Fraud Prevention System (FPS)

· New Medicare Card processes

· CWF Host Implementation and Correction Requests (HICR)

Accounting/ Financial
Standard interface for bank issues/clears
· Support of telecommunications with bank or contractor data center

· Execution of bank-specific interfaces for Issues file (optional, with Centers for Medicare & Medicaid Services (CMS) approval)

· Execution of the jobs to transmit the issues file to the bank or contractor data center

· Receipt of the Clears file from the bank (optional)

· Execution of bank-specific interfaces for Clears file (optional, with CMS approval)

Stale date processing

Mailroom-ready output document files, suitable for printing on International Business Machines (IBM) equipment, that have:

· Basic Advanced Function Presentation (AFP) mixed mode print file;

· Parameters to control additional mail finishing marks;

· Optical Mark Recognition (OMR) coding or 3 of 9 barcodes for outgoing financial documents;

· Separate checks, Medicare Summary Notices (MSNs), and remittance with AFP mixed mode formatted print streams;

· English language printed output for all documents, and Spanish language for the beneficiary MSN;

· Base Presort processing Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the Job Control Language (JCL))

— OR —

Mailroom-ready output document files, suitable for printing on Xerox equipment that have:

· Xerox print file;

· Parameters to control additional mail finishing marks;

· OMR coding or 3 of 9 barcodes for outgoing financial documents;

· MSNs and remittance with Xerox JDL/JDE formatted print streams;

· English language printed output for all documents, and Spanish language for the beneficiary MSN;

· Base Presort processing Execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the JCL)

Interface to Finalist zip code cleansing software
Receipt and installation of Finalist software and database updates

Cash receipts processing

Accounts receivable processing

Accounts payable processing

Creation of Automated Clearing House Electronic Funds Transfer (ACH EFT) records, pre-notification records, and X12 835 records
· Support of telecommunications with bank

· Execution of the jobs to transmit the ACH records to the bank or the contractor data center.

Accumulation of monthly, quarterly, and yearly financial data to create a 1099 database reflecting annual provider and beneficiary earnings
Execution of the jobs to transmit the 1099 records to the contractor data center

Health Professional Shortage Area (HPSA) processing which includes:

· Incentive checks in the same format as other special checks;

· Incentive payment reports;

· HPSA guideline monitoring reports;

· Suppression of HPSA checks for violators

· Notification of providers of those claims for which the HPSA bonus is being paid

National Change of Address (NCOA)
· Creation of a standard format file for National Change of Address (NCOA) processing

· Accept standard format NCOA file used to update beneficiary address data

· Support of telecommunications with vendor

· Execution of vendor-specific interfaces for NCOA file (with Centers for Medicare & Medicaid Services (CMS) approval)

· Execution of the jobs to transmit the NCOA records to the NCOA vendor or the contractor data center.

Interface to Finalist zip code cleansing software to cleanse NCOA address data
Receipt and installation of Finalist software and database updates for all contractors
File layouts to support the extract of data.
Execution of the jobs to extract the data and transmit the data to the data storage location (with CMS approval)
Payment Safeguards
File layouts to support the extract of data.
Execution of the jobs to extract the data and transmit the data to the data storage location (with Centers for Medicare & Medicaid Services (CMS) approval)

Automated history search capability to interface with ARGUS

Sampling capability in support of focused medical review (online history plus 4 years of purged history)

Standard interface to Program Integrity Sampling Module for Part B (PIMB) and Durable Medical Equipment (DME) contractors
Receipt and installation of PIMB software
File Purges
Standard purge logic

Capability to retrieve information by beneficiary from purged history

Other Add-on Software
Image request transaction files (RQ screen)

Pioneer Accountable Care Organization Model (ACO)

Execution of the jobs to extract the data and transmit the data to the data storage location (with Centers for Medicare & Medicaid Services (CMS) approval)

Recovery Audit Contractor (RAC)

· Establish connection and Resource Control Facility (RACF) to send and accept files from these 3rd Party entities.

· Execution of the jobs to extract the data and transmit the data to the data storage location (with Centers for Medicare & Medicaid Services (CMS) approval)

The Provider Statistical and Reimbursement (PS&R)

· Establish connection and Resource Control Facility (RACF) to send and accept files from these 3rd Party entities.

· Execution of the jobs to extract the data and transmit the data to the data storage location (with Centers for Medicare & Medicaid Services (CMS) approval)

January 10, 2019 Page 1 of 19

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