<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="P0b002ee18037f445">
<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">1999-04-14</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>21 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-99-144</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-144</identifier>
<identifier type="local">P0b002ee18037f445</identifier>
<identifier type="former package identifier">f:ai99144t</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-T-AIMD-99-144</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-T-AIMD-99-144</accessId>
 <reportNumber>T-AIMD-99-144</reportNumber>
 <subject>Y2K</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Information resources management</subject>
 <subject>Data integrity</subject>
 <subject>Computer software</subject>
 <subject>Computer software verification and validation</subject>
 <subject>State-administered programs</subject>
 <subject>Schedule slippages</subject>
 <subject>Systems conversions</subject>
 <subject>Systems compatibility</subject>
 <identifier>Y2K</identifier>
 <identifier>FAA National Airspace System Plan</identifier>
 <identifier>FAA Automated Radar Terminal System</identifier>
 <identifier>FAA Year 2000 Program</identifier>
 <identifier>IHS Resource and Patient Management System</identifier>
 <identifier>DOD Global Command and Control System</identifier>
 <identifier>DOD Defense Switched Network</identifier>
 <identifier>DOD Theater Battle Management Core Systems</identifier>
 <identifier>Air Force Contingency Theater Automation Planning System</identifier>
 <identifier>Medicaid Management Information System</identifier>
 <identifier>Medicare Program</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <accountNo>I99144</accountNo>
</extension>
<titleInfo>
 <title>Year 2000 Computing Challenge: Federal Government Making Progress But Critical Issues Must Still Be Addressed to Minimize Disruptions</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the remaining year
2000 computing challenges facing the federal government, focusing on
the: (1) actions that the federal government has taken to improve its
year 2000 approach; (2) status of the federal government&apos;s remediation
of its mission-critical systems, with a particular focus on those that
are not yet compliant; (3) reported status of state-administered federal
programs; and (4) remaining challenges facing the government in ensuring
the continuity of business operations, namely end-to-end testing and
contingency planning.&lt;p/&gt;GAO noted that: (1) since February 1997, action taken to address the
year 2000 threat has intensified; (2) in response to a growing
recognition of the challenge and urging from congressional leaders and
others, the administration strengthened the government&apos;s year 2000
preparation; (3) in February 1998, the President took a major step in
establishing the President&apos;s Council on Year 2000 Conversion; (4) the
Office of Management and Budget (OMB) has taken more aggressive action
on year 2000 matters over the past year and a half and has been
responsive to GAO&apos;s recommendations; (5) OMB&apos;s most recent reports show
improvement in addressing the year 2000 problem; (6) many key tasks,
however, remain to be completed to ensure the continuity of critical
services; (7) end-to-end testing and business continuity and contingency
planning are not yet complete and, in some cases, are in the beginning
stages; (8) not all of the systems reported as compliant have completed
an independent verification and validation process; (9) in some cases,
independent verification and validation of compliant systems have found
serious problems; (10) the Federal Aviation Administration has
identified 26 of its mission-critical systems as posing the greatest
risk to the National Airspace System should its year 2000 repairs
experience schedule delays or should the systems not be operational on
January 1, 2000; (11) the Health Care Financing Administration relies on
78 external mission-critical systems operated by contractors throughout
the country to process Medicare claims; (12) the Department of Health
and Human Services (HHS) reported that 23 of these external
mission-critical systems were not deemed year 2000 compliant as of March
31, 1999; (13) according to an official at the Coast Guard, three
mission-critical systems used in maritime search and rescue missions did
not meet the March 1999 implementation goal; (14) HHS reported that the
Indian Health Service&apos;s Resource and Patient Management System is
scheduled to be compliant by June 30, 1999; (15) GAO testified that
while the Department of Defense had recently made progress by providing
the controls and guidance needed to fix and test systems, it was behind
schedule; (16) one federal system that did not make the March
implementation target is critical to the implementation of several
federal human services programs; and (17) this system, HHS&apos;s Payment
Management System, processes billions of dollars in grant payments to
states and other recipient organizations for vital programs.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-144/html/GAOREPORTS-T-AIMD-99-144.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-144/pdf/GAOREPORTS-T-AIMD-99-144.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-144</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-144</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-144; Year 2000 Computing Challenge: Federal Government Making Progress But Critical Issues Must Still Be Addressed to Minimize Disruptions;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Information resources management</topic>
 <topic>Data integrity</topic>
 <topic>Computer software</topic>
 <topic>Computer software verification and validation</topic>
 <topic>State-administered programs</topic>
 <topic>Schedule slippages</topic>
 <topic>Systems conversions</topic>
 <topic>Systems compatibility</topic>
 <topic>Y2K</topic>
 <topic>FAA National Airspace System Plan</topic>
 <topic>FAA Automated Radar Terminal System</topic>
 <topic>FAA Year 2000 Program</topic>
 <topic>IHS Resource and Patient Management System</topic>
 <topic>DOD Global Command and Control System</topic>
 <topic>DOD Defense Switched Network</topic>
 <topic>DOD Theater Battle Management Core Systems</topic>
 <topic>Air Force Contingency Theater Automation Planning System</topic>
 <topic>Medicaid Management Information System</topic>
 <topic>Medicare Program</topic>
</subject>
</mods>