<mods xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" ID="P0b002ee1803917f9">
<name type="corporate">
 <namePart>United States Government Publishing Office</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">publisher</roleTerm>
  <roleTerm authority="marcrelator" type="code">pbl</roleTerm>
</role>
 <role>
  <roleTerm authority="marcrelator" type="text">distributor</roleTerm>
  <roleTerm authority="marcrelator" type="code">dst</roleTerm>
</role>
</name>
<name type="corporate">
 <namePart>United States</namePart>
 <namePart>Government Accountability Office</namePart>
 <namePart>Accounting and Information Management Division</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">author</roleTerm>
  <roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
 <description>Government Organization</description>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">government publication</genre>
<language>
 <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<extension>
 <collectionCode>GAOREPORTS</collectionCode>
 <category>Legislative Agency Publications</category>
 <waisDatabaseName>gao</waisDatabaseName>
 <branch>legislative</branch>
 <dateIngested>2010-08-12</dateIngested>
</extension>
<originInfo>
 <publisher>U.S. Government Printing Office</publisher>
 <dateIssued encoding="w3cdtf">1998-09-28</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>53 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-98-284</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-284</identifier>
<identifier type="local">P0b002ee1803917f9</identifier>
<identifier type="former package identifier">f:ai98284</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-28</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-98-284</recordIdentifier>
 <recordOrigin>machine generated</recordOrigin>
 <languageOfCataloging>
  <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</languageOfCataloging>
</recordInfo>
<accessCondition type="GPO scope determination">fdlp</accessCondition>
<extension>
 <docClass>REPORT</docClass>
 <accessId>GAOREPORTS-AIMD-98-284</accessId>
 <reportNumber>AIMD-98-284</reportNumber>
 <subject>Claims processing</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Systems compatibility</subject>
 <subject>Data integrity</subject>
 <subject>Information resources management</subject>
 <subject>Internal controls</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Systems conversions</subject>
 <identifier>HCFA Medicare Transaction System</identifier>
 <identifier>Medicare Program</identifier>
 <identifier>Y2K</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Medicare Computer Systems: Year 2000 Challenges Put Benefits and Services in Jeopardy</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed the extent to which
the Health Care Financing Administration (HCFA) is: (1) making progress
in renovating its Medicare systems to be year 2000 (Y2K) compliant; (2)
directing and overseeing the Y2K effort; (3) ensuring that all data
exchanges necessary for processing Medicare claims are identified,
renovated, tested, and validated; and (4) developing and initiating
business continuity and contingency plans for key business processes.&lt;p/&gt;GAO noted that: (1) HCFA and its contractors are severely behind
schedule in repairing, testing, and implementing the mission-critical
systems supporting Medicare; (2) HCFA has recently begun improving its
management of Y2K matters, including establishing a Y2K organization and
hiring independent contractors to assist in overseeing the Y2K work; (3)
in August HCFA reported that as of June 30, 1998, less than a third of
Medicare&apos;s 98 mission-critical systems had been fully renovated, and
none had been validated or implemented; (4) compounding this difficult
task is HCFA&apos;s lack of key management practices necessary to adequately
direct and monitor its Y2K project; (5) to date, HCFA has not: (a)
developed an adequate overall schedule and a critical path that
identifies and ranks Y2K tasks, and helps ensure that they can be
completed in a timely manner; (b) implemented risk management processes
necessary to highlight potential technical and managerial weaknesses
that could impair project success; and (c) planned for or scheduled
end-to-end testing to ensure that Medicare-wide renovations will work as
planned; (6) HCFA has also not been effectively managing the
identification and correction of its electronic data exchanges; (7)
neither has HCFA determined whether needed agreements with data exchange
partners have been made; (8) this increases the risk that Y2K errors
will be transferred through data exchanges from one organization&apos;s
computer systems to another&apos;s; (9) given the magnitude of the task and
risks ahead, and the limited time remaining, it is highly unlikely that
all of the Medicare systems will be compliant in time to ensure the
delivery of uninterrupted benefits and services into the year 2000; (10)
it is more critical than ever that HCFA have sound business continuity
and contingency plans in place, which can be implemented should systems
failures occur; (11) HCFA is late in establishing its business
continuity and contingency plans; (12) HCFA is relying on its Medicare
contractors to develop plans for their own systems; several contractors
told GAO they do not plan to begin developing their individual plans
until 1999; (13) also, HCFA has not yet developed a Medicare-wide
business continuity and contingency planning framework; and (14) HCFA
has only recently completed drafting a set of contingency planning
guidelines, and does not plan to have its Medicare-wide plan completed
and tested until June 20, 1999.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-284/html/GAOREPORTS-AIMD-98-284.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-284/pdf/GAOREPORTS-AIMD-98-284.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-98-284</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-284</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-98-284; Medicare Computer Systems: Year 2000 Challenges Put Benefits and Services in Jeopardy;
            </searchTitle>
</extension>
<subject>
 <topic>Claims processing</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Systems compatibility</topic>
 <topic>Data integrity</topic>
 <topic>Information resources management</topic>
 <topic>Internal controls</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Systems conversions</topic>
 <topic>HCFA Medicare Transaction System</topic>
 <topic>Medicare Program</topic>
 <topic>Y2K</topic>
</subject>
</mods>