J-01A MAC Shared System BaseNonbase.doc
DOC document 82 KB Posted
- Attached to
- DME MAC Jurisdiction A Federal contract opportunity
- Solicitation number
- RFP-CMS-2010-0004
About this file
J-01A MAC Shared System BaseNonbase.doc
View the file
Other files for this federal contract opportunity
Show all 50
DME MAC Jurisdiction A has more files on GovTribe.
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
CMS-RFP-2010-0004
Attachment J-01A
CMS-RFP-2010-0004
Attachment J-01A
MAC Shared System Base and Non-Base Functions
| Function |
| Shared System Provided |
| EDC Provided … |
| Security |
| Application security via a personnel file containing user authorization flags to control access to specific functions. |
| Creation and maintenance of network/environment security rules, via RACF. |
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, NGD, Sequential Terminals and FEPI.
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.
| EMC |
| VMS accepts files from the Common Electronic Data Interchange (CEDI) pre-pass editing and reporting front-end. |
VMS accepts NCPDP transmission format to be translated and processed. This also includes NCPDP responses. Although this is a current process as of June 2009, it will be replaced with a feed from CEDI for NCPDP files similar to X12 files by December 2009.
VMS transfers NCPDP claims in their flat file format that are sent to the wrong processing region (misdirected claims). CEDI performs the misdirected claims process for claims received in the X12 format. By December 2009, CEDI will perform misdirected claim routing for claims received in either X12 or NCPDP formats.
The EDC creates and maintains the jobs necessary to transmit CMS approved files from the EDC to any other location.
Direct Data Entry (DDE) application for provider on-line inquiry of claims information (VPIQ.PINQ).
| Claims Entry |
| Bene Update and Display System(BUDS) |
Automated Development System (ADS), including a base letter file selected from an existing user.
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. Several reference files are sent to CEDI to support edits selected by each DME MAC to address their local medical policies. |
| Creation and execution of the jobs to retrieve data from the CMS data center and transmit it to the EDC. |
CMS Maintenance (VDME)
On-line claims entry and work scheduler (VMON/APEX)
Weekly QA sampling
| Comprehensive Error Rate Testing (CERT) processing |
| Creation and execution of the jobs to transmit the base output to CMS’ CERT contractor. |
| Correspondence and Customer Service |
| Correspondence application that provides ability to track telephone and written correspondence. |
Letter-writing application, including a base letter file selected from an existing shared system user (ALGS).
| Pricing/ Profiles |
| Maintenance capability for the, customary, prevailing, DMEPOS/PENS fee schedule, the drug fee schedule and competitive bid fee schedule 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
Express Adjustments
| Medicare Secondary Payer (MSP) |
| Medicare Secondary Payer (MSP) validation through a base set of edits |
MSP automated payment calculation
Receipt and installation of ECRS software.
| Reporting |
| Provide data used to complete the required CMS reports such as the: |
· Workload and Performance reports;
· Appeals;
· Medical Review Workload;
· Medical Review Savings;
· PIMR;
· MSP Savings;
· CFO;
CEDI performs claims receipt, control and balancing for inbound claims from providers and the delivery to the EDC for processing. VMS provides reports to track processed claims.
Creation and execution of the jobs to transmit the PIMR data to CMS’ PIMR 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 |
| Allows online provider maintenance for the data not received from the NSC. |
Telecommunications mechanism between the EDC and the NSC.
Retrieval of the Daily Export Extract file from the NSC.
| Interface to Finalist zip code cleansing software to cleanse provider addresses. |
| Receipt and installation of Finalist software and database updates. |
| CWF Interaction |
| Creation of CWF transmits files for claims, CMNs, MSP, and eligibility data. |
| Creation and execution of the jobs to transmit the data to the CWF host. |
| Accepts CWF response files for claims, CMNs, MSP and eligibility data. |
| Receipt of CWF response files from CWF Host. |
| Interaction with HIMR Eligibility and Claim Data on a subset of VMS screens. |
| Receipt and installation of HIMR software. Provides support of CICS FEPI. |
| Accounting/ Financial |
| DME MAC Specific 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 —
Produce image file that could be used to produce another format.
Creation and execution of the jobs to transmit the image file 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 using the CCD+ format and pre-notification 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. |
| Electronic Data Interchange (EDI) |
| Creation of electronic remittance advices in one of the CMS-mandated flat file formats. |
Creation of electronic claim status response transactions on one of the CMS-mandated flat file formats.
Creation and execution of the jobs to transmit the data to the contractor data center.
Creation of crossover data for the COBC in the mandated flat file format.
Support of telecommunications with trading partners/COBC.
Creation and execution of the jobs to transmit the crossover data to the COBC.
| 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. |
| Allow PSCs/ZPICs to have the base jobs listed in attachment A. Report listing shall be updated monthly. |
| Facilitate the retrieval of outputs from the jobs in CA View or equivalent capability. |
| File Purges |
| Standard purge logic |
Source Selection Information – See FAR 2.101 and 3.104 Page | 1 Source Selection Information – See FAR 2.101 and 3.104 Page | 4
File details come from the government source that posted it. Updated .