Medicare Computer Systems: Year 2000 Challenges Put Benefits and Services in Jeopardy

Front Cover
DIANE Publishing, Jun 1, 1998 - 49 pages
0 Reviews
Reviews progress in addressing the Year 2000 issue for the Medicare claims processing systems. Time is running out to correct Medicare systems that could malfunction or produce incorrect information when the year 2000 is encountered. This report assesses the extent to which Medicare is: making progress in renovating its Medicare systems to be Y2K compliant; directing & overseeing the Y2K effort; ensuring that all data exchanges necessary for processing Medicare claims are identified, renovated, tested, & validated; & developing & initiating business continuity & contingency plans for key business processes.
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Selected pages

Common terms and phrases

Popular passages

Page 23 - The purpose of end-to-end testing is to verify that a defined set of interrelated systems, which collectively support an organizational core business area or function, will work as intended in an operational environment.
Page 1 - The Honorable Charles E. Grassley Chairman The Honorable John B. Breaux Ranking Minority Member Special Committee on Aging United States Senate The Honorable John D.
Page 4 - Assess the Year 2000 impact on the enterprise. Identify core business areas and processes, inventory and analyze systems supporting the core business areas, and prioritize their conversion or replacement. Develop contingency plans to handle data exchange issues, lack of data, and bad data. Identify and secure the necessary resources. Renovation Convert, replace, or eliminate selected platforms, applications, databases, and utilities.
Page 1 - Thomas Chairman Subcommittee on Health Committee on Ways and Means House of Representatives This report responds to your request that we review the Health Care Financing Administration's (HCFA) progress in addressing the Year 2000 issue for its Medicare claims processing systems. The Year 2000 problem, commonly referred to as Y2K, results from the inability of computer systems to interpret the century correctly when only two digits are used to indicate the year in recorded or calculated dates. In...
Page 4 - Year 2000 program team and develop an overall strategy. Ensure that everyone in the organization is fully aware of the issue. Assessment - Assess the Year 2000 impact on the enterprise. Identify core business areas and processes, inventory and analyze systems supporting the core business areas, and prioritize their conversion or replacement. Develop contingency plans to handle data exchange issues, lack of data, and...
Page 32 - Comments From the Food and Drug Administration Note: GAO comments supplementing those in the report text appear at the end of this appendix. DEPARTMENT OF HEALTH & HUMAN SERVICES Public Health Sarvk* Food and Drug Administration Hockville MD 20667 07)998 Mr.
Page 19 - ... systems can properly exchange data with other systems and are protected from errors that can be introduced by external systems. For example, agencies that administer key federal benefits payment programs, such as the Department of Veterans Affairs, must exchange data with the Department of the Treasury which, in turn, interfaces with financial institutions, to ensure that beneficiary checks are issued.
Page 4 - Develop contingency plans to handle data exchange issues, lack of data, and bad data. Identify and secure the necessary resources. RENOVATION: Convert, replace, or eliminate selected platforms, applications, databases, and utilities. Modify interfaces.
Page 12 - System (MTS), the project was intended to be a single government-owned system that would replace the existing, two standard part A and five standard part B claims processing systems currently being used by Medicare contractors. HCFA intended to develop MTS as a Y2K-compliant system and have it in place and operational before 2000. However, the MTS project encountered problems from the very beginning. It was plagued with schedule delays, cost overruns, and the lack of effective management and oversight....
Page 27 - Medicare-wide claims processing contingency plan developed and tested until June 20, 1999, thus potentially leaving insufficient time for implementation. For example, HCFA may include in its business continuity and contingency plan an approach to transfer the workload of any contractor not Y2K compliant by July 1, 1999, to a contractor certified as Y2K compliant. However, both contractor and HCFA officials told us that, at a minimum, it requires 6 months to a year to transfer the claims processing...

Bibliographic information