J-01A_Fee-for-Service-Shared-System-Base-Functions.doc
DOC document 169 KB Posted
- Attached to
- Solicitation RRB11R001 - RRB Specialty MAC
- Solicitation number
- RRB11R001
- Issued by
-
Railroad Retirement Board
About this file
Solicitation RRB11R001 Attachment J01A
View the file
Other files
Show all 50
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
RFP – RRB-11-R-001
Attachment J-01A: Fee-for-Service Shared System Base Functions
| Function |
| Shared System Provided |
| EDC Provided … |
| Security |
| Application password security via a personnel file containing user authorization flags to control access to specific functions |
| Creation and maintenance of network/environment security rules, via ACF2 |
Data Center security ID and password that controls access into the data center, access into the CICS regions, access to CICS transactions, and read/write access to files.
Data Center security Machine-ID and non-expiring password that controls access into the data center for functions such as IVR and NGD.
Tele-communications
Works with CMS-approved contractors as necessary to establish batch and interactive connectivity between the data centers.
File Transfers
The EDC creates and maintains the jobs necessary to transmit CMS-approved files from the EDC to any other location.
The EDC receives files transmitted from CMS approved contractors.
| Electronic Data Interchange (EDI) |
| MCS and FISS accept CMS’ X12 flat files for HIPAA EDI transactions created from the translation of ANSI ASC X12N version 4010A.1 format, and other EDI transactions as directed by CMS. (There are currently no 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 support a single version of the HIPAA EDI standards. 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.
MCS furnishes the Professional Provider Telecommunication Network (PPTN) application for provider inquiry of claims status information via a DDE-type screen and a link to the CWF maintained DDE screen established to request and receive beneficiary eligibility information.
| Creation of electronic remittance advices in the HIPAA mandated Format |
| Creation and execution of the jobs to produce the remittance advice flat files for translation into compliant HIPAA standard remittance advice transactions by the 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 COBC
Creation and execution of jobs to transmit the crossover flat file claims data to the COBC via the Medicare telecommunications network.
FISS furnishes the Direct Data Entry (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.
| 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 IBM AFP mixed mode or Xerox JDL/JDE print file containing development letters (English or Spanish) that support use of contractor-maintained OMR marks or 3 of 9 barcodes Creation and execution of the jobs to transmit the base print output to the contractor local data center
| A base set of reference files and tables selected from an existing shared system user |
| Creation and execution of the jobs to retrieve the CCI data from the CMS data center and transmit it to the EDC |
On-line work scheduler
Suspense document print file
Weekly EOLQA sampling
| Comprehensive Error Rate Testing (CERT) processing |
| Creation and execution of the jobs to transmit the base output to CMS’ CERT contractor |
| Existing CMS Standard ARU interface in the form of an on-line transaction |
| Ability to connect to the FFS application at the EDC |
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 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 EDC 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 |
| GUI-based MCS Desktop Tool (MCSDT), if desired |
| Ability to connect to the FFS application at the EDC |
Letter-writing application, including a base letter file selected from an existing shared system user
| Generation of standard IBM AFP mixed mode or Xerox JDL/JDE print file for correspondence response letters (English or Spanish) that support use of contractor-maintained OMR marks or 3 of 9 barcodes |
| Creation and execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the JCL) |
| Pricing/ Profiles |
| Maintenance capability for the MPFSDB, customary, prevailing, ambulance fee schedule and zip code file and other relative pricing files |
| Creation and execution of the jobs to retrieve the fee schedule data from the CMS data center and transmit it to the EDC |
Creation and execution of the jobs to extract the contractor-specific fee schedule data
Standard provider profile build logic
Automated pricing of claims
Automated “mass” adjustments capability
Express Adjustments
| Limiting Charge processing |
| Creation and execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the JCL) |
| Medicare Secondary Payer (MSP) |
| Medicare Secondary Payer (MSP) validation through a base set of audits |
MSP automated payment calculation
Identification of MSP recovery claims via IRS/SSA Data Match and retroactive recovery with automated history searching
| Systematic MSP Automated Recovery Tracking (SMART) system |
| Creation and execution of the jobs to retrieve the Data Match files and transmit them to the EDC |
Demand packages in a basic AFP mixed mode or Xerox DJDE print file, along with mailing label print files for certified and non-certified mail
Associated folder label print file Creation and execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the JCL)
Receipt and installation of ECRS software.
| Reporting |
| Provide data used to complete the required CMS reports such as the: |
· Workload and Performance/PULSE file;
· Appeals;
· Medical Review Workload;
· Medical Review Savings;
· PIMR;
· MSP Savings;
· CFO;
· PSOR
· PS&R
Creation and execution of the jobs to transmit the PIMR data to CMS’ PIMR contractor
Creation and execution of the jobs to transmit the CCI report to CMS’ CCI contractor
Creation and 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 |
| Creation and execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the JCL) |
| Provide the base data files for use in contractor-specific Ad-Hoc Reporting and Data Extracts |
| Execution of the jobs to create ad-hoc reports or data extracts (with CMS approval) |
| 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 EDC 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 Creation and execution of the jobs to retrieve the Mammography Quality Standard Act (MQSA) File from the CMS data center
MCS creates weekly tapes for the 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 to create ad-hoc reports or data extracts (with CMS approval) |
| Provide access to the data required to produce the 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.) |
| Creation and execution of the jobs to transmit the extracted data to contractor data center |
| CWF Interaction |
| Creation of CWF transmits files for claims, MSP, and eligibility data |
| Creation and 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 HIMR Eligibility and Claim Data on a subset of MCS screens. |
| Receipt and installation of HIMR software |
Bridge between the FISS DDE System and the CWF ELGA screen for eligibility inquiries by providers
Receipt and installation of CWF ELGA software.
| Bridge between the Professional Provider Telecommunication Network (PPTN) and the CWF ELGB screen for eligibility inquiries by providers |
| Receipt and installation of CWF ELGB software |
| Accounting/ Financial |
| Standard interface for bank issues/clears |
| Support of telecommunications with bank or contractor data center |
Creation and execution of bank-specific interfaces for Issues file (optional, with CMS approval)
Creation and 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)
Creation and execution of bank-specific interfaces for Clears file (optional, with CMS approval)
Stale date processing
Mailroom-ready output document files, suitable for printing on IBM equipment, that have:
· Basic AFP mixed mode print file;
· Parameters to control additional mail finishing marks;
· OMR coding or 3 of 9 barcodes for outgoing financial documents;
· Separate checks, MSNs, and remittance with AFP mixed mode formatted print streams;
· English language printed output for all documents, and Spanish language for the beneficiary Medicare Summary Notice (MSN);
· Base Presort processing Creation and execution of the jobs to transmit the base print output to the contractor’s print site (if routing is not done via the 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 Creation and 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 ACH EFT records, pre-notification records, and X12 835 records |
| Support of telecommunications with bank |
Creation and 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 |
| Creation and execution of the jobs to transmit the 1099 records to the contractor data center |
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 HPAA bonus is being paid
| National Change of Address (NCOA) |
| Creation of a standard format file for NCOA processing |
Accept standard format NCOA file used to update beneficiary address data Support of telecommunications with vendor
Creation and execution of vendor-specific interfaces for NCOA file (with CMS approval)
Creation and 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. |
| Creation and 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. |
| Creation and execution of the jobs to extract the data and transmit the data to the data storage location (with 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 and DME contractors (PIMB) |
| 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) |
| National Provider Identifier Crosswalk |
| Access to NPI Crosswalk during claims processing as well as a claim by claim basis by contractor staff. |
File details come from the government source that posted it. Updated .