<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="P0b002ee18039c1ad">
<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-01-20</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>23 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-99-49</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-49</identifier>
<identifier type="local">P0b002ee18039c1ad</identifier>
<identifier type="former package identifier">f:ai99049t</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-23</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-T-AIMD-99-49</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-49</accessId>
 <reportNumber>T-AIMD-99-49</reportNumber>
 <subject>Y2K</subject>
 <subject>Systems conversions</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Information resources management</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Computer software</subject>
 <subject>Data integrity</subject>
 <identifier>Medicare Program</identifier>
 <identifier>Medicaid Program</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <accountNo>I99049</accountNo>
</extension>
<titleInfo>
 <title>Year 2000 Computing Challenge: Readiness Improving, But Critical Risks Remain</title>
</titleInfo>
<abstract>The federal government, with its dependence on large-scale, complex
computer systems to deliver vital public services, faces an especially
enormous and difficult task in overcoming the Year 2000 computing
problem. Unless adequately addressed, Year 2000 problems could seriously
disrupt key federal operations--from national defense to benefits
payments to air traffic control. Although the government&apos;s preparedness
to deal with the Year 2000 problem has improved markedly during the past
two years, significant challenges remain and time is running out.
Complete and thorough Year 2000 testing is essential to ensure that new
or modified systems are able to process dates correctly and that
technology-dependent services operate reliably after the turn of the
century. Moreover, adequate business continuity and contingency plans
must be in place throughout government. The scope of the Year 2000
problem extends well beyond federal operations, however, affecting both
the U.S. and the global economies. In concert with GAO&apos;s
recommendations, the President&apos;s Council on Year 2000 Conversion has
been reaching out to the private sector, state and local governments,
and other countries to increase awareness of the problem. The Council
has also begun to address the readiness of specific economic sectors,
including power, water, telecommunications, health care, and emergency
services. At this juncture, however, a comprehensive picture of the
nation&apos;s readiness is lacking. Much more needs to be done--both
domestically and internationally--to determine readiness and prepare
contingency plans.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-49/html/GAOREPORTS-T-AIMD-99-49.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-99-49/pdf/GAOREPORTS-T-AIMD-99-49.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-99-49</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-99-49</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-99-49; Year 2000 Computing Challenge: Readiness Improving, But Critical Risks Remain;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Systems conversions</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Information resources management</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Computer software</topic>
 <topic>Data integrity</topic>
 <topic>Medicare Program</topic>
 <topic>Medicaid Program</topic>
</subject>
</mods>