D -- Medicare Enrollment Database and Direct Billing Initiatives

The Centers for Medicare & Medicaid Services (CMS) intends to award a contract to Data Computer Corporation of America (DCCA) on a sole source basis using the Federal Supply Service Information Technology Schedule. CMS maintains an enrollment database (EDB) containing records of all beneficiaries ever entitled to Medicare. The EDB contains beneficiary identifying information, Medicare Part A and B entitlement dates, demographic data information, Medicare managed care enrollment information, direct billing information, third party payer information, and data identifying the reason for Medicare entitlement. The implementation of the new Direct Billing System (DBS) was effective August 30, 1996. As part of that redesign, the EDB began housing data for those beneficiaries who are being directly billed. Current efforts will build on the EDB to satisfy additional user requirements and legislative requirements for enrollment, entitlement and direct billing processes. In addition, efforts to streamline those processes and provide support for other DBS applications will be done simultaneously. DCCA is currently providing routine maintenance support and the continued updating support of the ongoing operational functionalities of the Enrollment Database, Direct Billing System and Third Party System to accommodate legislative and regulatory changes. DCCA has begun to convert the large EDB from a Model 204 environment to a DB2 environment. This contract will be awarded on a sole source basis, using the Federal Supply Service Information Technology Schedule, to DCCA as they have been solely responsible for the conversion since June 2001. The contract will also include maintenance support for all of the current M204 systems of this database and the conversion of those systems. This contract will be awarded for a period of 26 months. Contracting for the conversion and maintenance services is an interim strategy not expected to exceed July 31, 2004. It is being done to ensure maximum results in the development and integration of these two databases, to ultimately form one, until the MBD2 is complete and fully implemented.